-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot- bounces@lists.denx.de] On Behalf Of Andreas Bießmann Sent: 29 October 2012 14:41 To: Dimax Cc: Marek Vasut; u-boot@lists.denx.de Subject: Re: [U-Boot] UBIFS fails on SheevaPlug
Dear Dimax,
please do not TOFU.
On 29.10.2012 09:50, Dimax wrote:
Hi, What if I compile a new u-boot but to try it I will load and flash
new
created image after original u-boot and will run it from withing original reboot manually just pointing a new image address? Can it
work?
well, you mean to run a u-boot out of a running u-boot? U-Boot is not designed to do so. But some devices may allow you to
It will not work.
just run a newer u-boot from a running one (at91;). You need to know that u-boot set up your SDRAM timings which destroys the content of the DRAM. So if your new u-boot is located there it can not be executed. I dunno if the kirkwood can do so, but I think they can not. You will need a) a JTAG b) another boot device, for example USB, MMC, whichever device the kirwood SoC can read from its ROM code (I do not know) to de-brick it.
Please ask some kirkwood specialist or google, there are a lot of sheevaplug hackers out there, one of them may be able to help you here.
You will need a JTAG key (amontec on any other) and OpenOCD s/w tool. Then you can build and test your code on Kirkwood w/o flashing on the device (i.e. running from RAM)
You may look for developer guidelines on the google or plugcomputer forum.
Regards... Prafulla . . .