Print

[NewITMalcolm]

It may be very tempting to reflash the uboot on the Dreamplug but we strongly recommend you do NOT try this. Doing so will void your Warranty and there is NO recovery procedure at present.

NewIT Technical

[Rzkphy]

Is it possible to reflash the uboot of the dreamplug to the factory default?
I have somehow set an environment variable which I cannot remove by

setenv [variable]

It does not affect the boot process - anymore - since I use another variable instead but it would be nice to see that variable removed...

[NewITMalcolm]

Hi Rzkphy,

setenv [variable] should get rid of unwanted variables.

Can you post your uboot variables please.

NewITJames

[Rzkphy]

Code: [Select]

Marvell>> printenv
bootdelay=3
baudrate=115200
x_bootcmd_ethernet=ping 192.168.2.1
x_bootargs=console=ttyS0,115200
ethact=egiga0
ethaddr=F0:AD:4E:00:7F:85
eth1addr=F0:AD:4E:00:7F:86
x_bootcmd_usb=usb start; fatload 1 1000000 script; source 1000000;
bootcmd=usb start; fatload usb 1 100000 script; source 100000; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
filesize=BA
x_bootcmd_kernel=fatload usb 1 0x6400000 uImage
x_bootargs_root=root=/dev/sdb2 rootdelay=10
stdin=serial
stdout=serial
stderr=serial

Environment size: 530/4092 bytes
The problem appears in variable x_bootcmd_usb

The funny thing is that I also can have a new variable with the same name:

Code: [Select]

Marvell>> setenv x_bootcmd_usb funny things happen
Marvell>> printenv
bootdelay=3
baudrate=115200
x_bootcmd_ethernet=ping 192.168.2.1
x_bootargs=console=ttyS0,115200
ethact=egiga0
ethaddr=F0:AD:4E:00:7F:85
eth1addr=F0:AD:4E:00:7F:86
x_bootcmd_usb=usb start; fatload 1 1000000 script; source 1000000;
bootcmd=usb start; fatload usb 1 100000 script; source 100000; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
filesize=BA
x_bootcmd_kernel=fatload usb 1 0x6400000 uImage
x_bootargs_root=root=/dev/sdb2 rootdelay=10
stdin=serial
stdout=serial
stderr=serial
x_bootcmd_usb=funny things happen

Environment size: 564/4092 bytes

Unfortunately I do not remember the exact command I used to create that first variable as it seems that the name is somehow different from what I expect it to be...

Thank you for your help

[Confusticated]

This was a known bug in older versions of uboot
You could try clearing the memory space used by the environment (wiping everything),
or reflashing just the environment, BUT in either case you had better be sure you get it right !!!
Safer just to use 'y_bootargs_usb' instead 

[Rzkphy]

Okay, that was my second guess but I didn't check for bugs of uboot. Next time I will do better ;-)

I guess wiping the memory used by the environment would involve some kind of memload operation within uboot?! And I should be quite sure about the maths here...

Right know I am just avoiding the variable anyway so I think it should be fine.


Thank you and I hope that won't happen with the real bootcmd variable ?! ;-)

[Confusticated]

Er..Pretty Pretty Please, I need a DreamPlug u-boot.img.

Two obvious ways I can think of to get at it:
Build a modern kernel with the Marvell SPI\Flash support and cat it from the /dev/???.
Write a little tcl and dump it to file with OpenOCD (after reading it into RAM at the u-boot prompt).

[Fletch]

Er..Pretty Pretty Please, I need a DreamPlug u-boot.img.

You can get the one from the dream_burn_spi on the googlecode site.  Not sure what version it is.

[Confusticated]

Thanks Fletch,
Hexdump wil tell me everything I need to know

EDIT: All I can find there are kernel\rootfs images, still need a u-boot.img
EDIT: Found it, it is in the sheevaplug tree (but the Marvell prompt gives the game away)!