In the case of INGRID, a total of four eeproms need to be prepared. One for the timing board and three for the utility board. The eeprom type is a 5v writable, erasable eeprom, generic part number 28C256. The purpose of the program contained within the eeproms is to provide basic access to the memory space of the relevent dsp's (Utility and Timing) thus allowing application program downloads and basic communication testing to be done. Refer to the software pages for information about boot services available for each version (Interface Control Documents).

In general, the version of the boot ROM code needs to correspond to the major version number of the application programs for the respective boards. Therefore version 3.0 of the boot ROM code for the utility board would support versions 3.0, 3.1, 3.2, etc. of the utility application programs.

If new boot roms need to be generated you must first identify the required version. This can be done by inspecting the UltraDas startup script to determine the version number of the application program currently in use. Having identified the correct version, look and make sure that the required eeprom images (Motorola S code files) for downloading are available. These can usually be found in the dspdev account by following the directory structure down to '/home/dspdev/InfraRed/timing' for the timing board eeprom image and '/home/dspdev/InfraRed/utility' for the utility board eeprom images. As an alternative the software source for the required version can be loaded off the web as a zipped tar file and the boot ROM images extracted. If doubt exists about the validity of the existing eeprom images in dspdev (i.e. desyncronized dates between source and image, bad file size, bad vibes, etc.) you can regenerate the required boot ROM image in the dspdev account space. Do this by making the specified directory for the timing or utility code your working directory then issue the command 'make BOOT'. This will compile the boot source code and result in a new boot ROM image being generated. Follow the instructions in the next paragraphs to download the files to the S4 eprom burner and create the Boot ROMs. There are two S4 Dataman eeprom burners available, one at sea level, one on the mountain top. They are usually left in the respective laboratories, however, if not found there, look in the detector teams offices. The Dataman driver softwar for PC's is kept with the burner and is installed on the detector team members lap top computers (but we'll never lend you one :-).

When handling eeprom devices please exercise due precaution against static damage !!

Generating the Timing Boot ROM.
The timing board eeprom image is called 'timboot.s'. The actual version number is buried within the code and cannot be inspected directly with ease (for those wishing to try, the major version number is at location 0xC017, the minor at 0xC016.). The image needs to be downloaded to the S4 Burner, moved in physical memory space, burned to the eeprom, then checked and labeled. 1. Follow the steps bellow:

• Connect the S4 Dataman Burner to a suitable PC (requires network connection and serial port). If not already installed, install the S4 driver software onto the PC from the diskette.
• Bring up the S4 driver program (a beep should be heard from the burner).
• Type 'FI' (Fill area) in the blue command window, and accept the default fill parameters (00000,07FFF,FF) to purge all internal memory of garbage.
• Click on the top left toolbar icon (Down load file to S4) and select the CORRECT ! Boot image file (timboot.s) from the file system.The download process will proceed and status shown when complete. Accept the status.
• Type 'MO' (Move area) and assure that the parameters are 0C000,0D000,04000 i.e move memory image from locations 0C000 up to 0D000 to lower address of 04000 to 05000.This is necessary to align the physical eeprom address space to the logical dsp address space.
• Type 'BU' (Burn eeprom) to transfer the image from the S4 into the eeprom. During the burn the memory address that is being burned is shown in the S4 window. The return of the command prompt when the burn is complete should show 'SAME'.
• Type 'CR' (checksum on eeprom) and observe that the checksum matches the checksum value listed at the end of this page. If so .... Label the device with the correct identifier and version number (eg. INGRID V3.2 TIMING) and then have yourself a nice day !!

Generating the Utility Boot ROMs.
With regards to the utility eeprom images; These can usually be found in the '/home/dspdev/InfraRed/utility' directory and named as 'ingrid_utility_bootcode.p0', '..p1', and '..p2'.
The images need to be downloaded to the S4 Burner, burned to the eeprom, then checked and labeled. 1. Follow the steps bellow:

Connect the S4 Dataman Burner to a suitable PC (requires network connection and serial port). If not already installed, install the S4 driver software onto the PC from the diskette.

Bring up the S4 driver program (a beep should be heard from the burner).

For each eeprom image file (three of them):

Type 'FI' (Fill area) in the blue command window, and accept the default fill parameters (00000,07FFF,FF) to purge all internal memory of garbage.

Click on the top left toolbar icon (Down load file to S4) and select the CORRECT ! Boot image file (eg. ingrid_utility_bootcode.p0) from the file system.The download process will proceed and status shown when complete. Accept the status.

Type 'BU' (Burn eeprom) to transfer the image from the S4 into the eeprom. During the burn the memory address that is being burned is shown in the S4 window. The return of the command prompt when the burn is complete should show 'SAME'.

Type 'CR' (checksum on eeprom) and observe that the checksum matches the checksum value listed at the end of this page. If so .... Label the device with the correct identifier and version number (eg. INGRID P0 V3.2 UTILITY ) and then have yourself a nice day !!