On the B003-fm:2.5.2 I have these choices in u-boot:
Code:
uboot> ?
? - alias for 'help'
autoscr - run script from memory
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootf - boots from either of the selected kernels. depending on mode and settings.
bootm - boot application image from memory
bootp - boot image via network using BootP/TFTP protocol
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
echo - echo args to console
erase - erase FLASH memory
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
flinfo - print FLASH memory information
go - start application at address 'addr'
help - print online help
iminfo - print header information for application image
imls - list all images found in flash
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing)
mtest - simple RAM test
mw - memory write (fill)
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
pmic - PMIC utility commands
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sleep - delay execution for some time
sspi - SPI utility commands
tftpboot- boot image via network using TFTP protocol
version - print monitor version
uboot>
So if I can't find what I need in the "Recovery Menu" -
It doesn't have a "Recovery Menu", it has a "Developer Menu"
Code:
Developer Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
And "Q" does not give the option to open a shell in the initrd system, it just, well, quits (reboots).
Maybe u-boot is the best choice -
I can still copy a system image from the B002, load and run it from a network connection (or so it seems).
Maybe the easiest to do from u-boot would to be forcing a: "rdinit=/bin/sh" into the kernel's command line. **maybe**
Hmm...
"Diagnostics Mode" does not seem to be much help either -
Code:
Turing-WW Diagnostic Services, version 3.27
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1) Video
2) LED
3) Buttons
4) Keyboard
5) 5-Way
6) USB Device Mode
7) Power
8) Gas Gauge
9) Audio
0) WAN
M) MoviNand
N) Run Modes
S) Device Settings
F) FCT
G) Operator Test Suite
D) Disable auto-run of diagnostics
X) Exit Diagnostic Services