3 dBUG Boot loader
Linux Software Developers Kit (SDK) User Guide
23
6. Issue a 'reset' at the dBUG prompt for the changes to take effect. Repeat step 3 to get back
to the dBUG prompt.
7. Clear the flash space for the JFFS2 partition using the ‘fl e’ command. The command below
erases 4MB of flash starting at address 0x00400000. This can be mounted as a JFFS2
partition from Linux.
For the MatchPort AR or EDS1100 / 2100
dBUG> fl e 0x00400000 0x00400000
For the XPort Pro
dBUG> fl e 0x00400000 0x00C00000
8. Download the firmware image with ‘dn’ and boot Linux using the ‘go’ command. The target
should now boot Linux via TFTP.
dBUG>dn
dBUG>go
Boot Failure Detection
When enabled, the dBUG boot failure counter (bootfc) parameter is incremented each time dBUG
starts booting, and reset from within Linux after a successful boot. When Linux fails to boot
successfully, bootfc will increment each boot. When bootfc reaches maxbootfc dBUG will stop
trying to boot Linux, and will await manual recovery. To enable the boot failure counter, set the
maxbootfc parameter to the desired numeric value. Set maxbootfc to 0 or ‘off’ to disable the boot
failure counter.
Silent Boot Option
The dBUG silent boot option disables both the display of dBUG boot messages, and the autoboot
countdown. To enable the silent booting perform the following:
dBUG> set silentboot on
When silent boot mode is enabled, it is still possible to break into the dBUG command line. To do
so, reset the target unit by cycling the unit's power (turning the power off and back on).
Immediately upon resetting the device, enter three ^x (Ctrl+x) characters.
Restoring Ethernet Address
To reset the Ethernet address used by dBUG and Linux back to the factory default setting,
perform the following:
dBUG> set ethaddr defaults
Dual Bank
When dual bank is disabled, Linux can use the entire flash memory for the kernel and root file
system.
When dual bank is enabled, flash is divided into two banks. Linux boots using a bank and keeps
another bank unused. The second bank is used automatically during a firmware upgrade and
provides redundant flash storage space that is useful in recovery scenarios when firmware
upgrade fails. For more information about Flash mapping, see Chapter 5
