Quote:
Originally Posted by rastik
No, not really. I used bist just to activate fastboot. I could use idme to change bootmode and restart. I found bist useful so far only in activating fastboot and activating file storage mode (fstor) command. With that I was able to charge the device while in uboot. It seems that KT is charging only when in USB mass storage mode - either via fstor (where you cannot do anything else apart from restart) or when framework is booted, usbnet is not active and KT is plugged to the computer.
Code:
uboot > ?
? - alias for 'help'
bist - start Built In Self Test
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
go - start application at address 'addr'
help - print online help
idme - idme - Set nv ram variables
log - manipulate logbuffer
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
setenv - set environment variables
version - print monitor version
bist offers quite a lot of functionality:
Code:
bist > help
? - alias for 'help'
autoscr - DEPRECATED - use "source" command instead
base - print or set address offset
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
check - perform MMC CRC32 check
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
diag - perform board diagnostics
echo - echo args to console
fail - fail blink fail pattern on LED
fastboot- Fastboot
fstor - File Storage
go - start application at address 'addr'
halt - halt board
help - print online help
i2c - I2C sub-system
idme - idme - Set nv ram variables
iminfo - print header information for application image
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
loopw - infinite write loop on address range
md - memory display
mm - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - mmcinfo <dev num>-- display MMC info
mtest - simple RAM read/write test
mw - memory write (fill)
nm - memory modify (constant address)
ocotp - OCOTP sub system
panic - panic halt
pass - pass blink pass pattern on LED
pmic - pmic - PMIC utility commands
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
setenv - set environment variables
sleep - delay execution for some time
source - run script from memory
sspi - SPI utility commands
version - print monitor version
|
Wow! Thanks for this. Now I know it is possible to reflash the kernel/bl from uboot.