I have a similar problem. In my environment:
bootcmd=cp.b c004 ${loadaddr} 28;bootm ${loadaddr}
mtdparts=mtdparts=mxc_nor_flash.0:256k(U-Boot),2560k(kernel),29312k(rootfs),512k(config),128k(env1)
bootargs=noinitrd console=ttymxc0,115200 root=/dev/mtdblock2
init=linuxrc rw ${mtdparts}
But
On Monday 26 October 2009 03:44:41 javier Martin wrote:
I have a similar problem. In my environment:
bootcmd=cp.b c004 ${loadaddr} 28;bootm ${loadaddr}
mtdparts=mtdparts=mxc_nor_flash.0:256k(U-Boot),2560k(kernel),29312k(rootfs)
,512k(config),128k(env1) bootargs=noinitrd
On Friday 23 October 2009 08:25:00 David Collier wrote:
If I put the following line in my board.h file
#define CONFIG_RAMBOOTCOMMAND \
ping ${serverip} tftp bootm ${fileaddr}
start with the binary. run `strings` on your u-boot.bin (or whatever
If I put the following line in my board.h file
#define CONFIG_RAMBOOTCOMMAND \
ping ${serverip} tftp bootm ${fileaddr}
then when I do PRINTENV I see
ramboot=ping ${serverip} tftp bootm 0x1040
so clearly at some point the text ${fileaddr} has
4 matches
Mail list logo