5.All processes will be halted, and the programming will begin. The progress is shown by a ‘.’ displayed every 4kbytes. An ‘E’ indicates the erasure of a flash sector. When complete, verification will begin automatically. The dimmPCI will reboot automatically upon successful programming and verification. If errors are found, the address will be reported, and another attempt to reprogram the flash will begin (up to three attempts maximum).
Notes:
1.Invoking ‘loader’ with a
loader imagez.bin
2. Invoking ‘loader’with a
loader imagez.bin
3.It is possible to run loader from a telnet session. However, once the programming begins, the progress indication will be sent only to the console. The telnet session can be reconnected once the programming is complete and the dimmPCI reboots.
4.The ‘loader’ program was written to be loaded from a network file system into RAM. Although the ‘loader’ program can be copied into the ROM file system or the journal flash file system, it cannot be run
oops
The following are brief instructions on how to use oops. For more details about how oops works, refer to Appendix D6.
The oops directory contains:
1.The ‘oops’ executable (which must be compiled the first time using gcc on the develop- ment platform. There is a Makefile included in the /opt/boottools/’oops/src’ directory for this purpose)
2.‘init.b’ containing the initialisation sequence for the dragonball VZ
3.‘loader.bin’ containing the program to write and verify the flash
4.‘kernel.bin’ containing the dimmPCI kernel image
44 | www.amctechcorp.com |
