Differences
This shows you the differences between the selected revision and the current version of the page.
| howto:uboot 2010/07/05 16:03 | howto:uboot 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== U-BOOT Monitor ====== | ====== U-BOOT Monitor ====== | ||
| - | * See also [[http://wiki.dns323.info/hardware:serial|serial connections]]. | + | * See also [[http://dns323.kood.org/hardware:serial|serial connections]]. |
| ===== Monitor Mode ===== | ===== Monitor Mode ===== | ||
| * Type the two keys **SPACE** and **1** before the monitor 3 second timeout. | * Type the two keys **SPACE** and **1** before the monitor 3 second timeout. | ||
| + | |||
| + | ===== Enabled Commands ===== | ||
| + | |||
| + | The standard U-Boot on my B1 hardware has the following commands enabled: | ||
| + | |||
| + | Marvell>> ? | ||
| + | ? - alias for 'help' | ||
| + | bootm - boot application image from memory | ||
| + | cp - memory copy | ||
| + | echo - echo args to console | ||
| + | erase - erase FLASH memory | ||
| + | loadb - load binary file over serial line (kermit mode) | ||
| + | md - memory display | ||
| + | printenv- print environment variables | ||
| + | run - run commands in an environment variable | ||
| + | setenv - set environment variables | ||
| + | Marvell>> | ||
| + | |||
| + | It is pretty limited, but is enough to recover a failed firmware installation. | ||
| + | |||
| + | There is mention made of additional commands which may be enabled through setting the environment variable "enaMonExt" to "yes" ("setenv enaMonExt yes" at the U-Boot prompt). Examination of the Marvell sources confirm this variable name, and what it is supposed to do. | ||
| + | |||
| + | Unfortunately, it simply results in the following output for any "advanced" commands: | ||
| + | |||
| + | Marvell>> tftpfs | ||
| + | Unknown command 'FSrun' - try 'help' | ||
| + | Marvell>> blah | ||
| + | Unknown command 'FSrun' - try 'help' | ||
| + | Marvell>> | ||
| + | |||
| + | As you can see, the command is being translated to "FSrun", which indicates that the "enaMonExt" code path is being followed, but unfortunately, the version of U-Boot that I have was compiled without support for the "FSrun" command, which means that this has no meaningful effect on this hardware. | ||
| ===== Exploring U-Boot ===== | ===== Exploring U-Boot ===== | ||
| Line 76: | Line 108: | ||
| The address 0x100000 is the default address used by "loadb". If your "loadb" uses a different address, you should update the "bootm" command above. | The address 0x100000 is the default address used by "loadb". If your "loadb" uses a different address, you should update the "bootm" command above. | ||
| - | Now the new image should execute, and return you to a boot prompt, with a fully featured U-Boot loader ready to obey your commands, without having to run the risk of flashing something that may not boot, and have to recover using JTAG. | + | Now the new image should execute, and return you to a boot prompt, with a fully featured U-Boot loader ready to obey your commands, without having to run the risk of flashing something that may not boot, and having to recover using JTAG. |
| + | |||
| + | Current U-Boot now includes network support for Orion5x chips, and can easily be configured in a dns323 board config to enable DHCP, TFTP, etc. Work is under way to support booting from SATA as well as USB on the LaCie ED Miniv2, which is a very similar device to the DNS323. | ||
| + | |||
| + | Flash support is still lacking. Anyone who knows how to properly address the Spansion flash chip as used in the DNS323, and who would like to get this working in U-Boot is invited to post to the U-Boot list. | ||
