From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Andreas_Bie=DFmann?= Date: Mon, 29 Oct 2012 10:11:05 +0100 Subject: [U-Boot] UBIFS fails on SheevaPlug In-Reply-To: References: <201210282354.02300.marex@denx.de> <508E26D3.5030606@googlemail.com> <508E409B.20501@gmail.com> Message-ID: <508E4829.90004@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 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. Best regards Andreas Bie?mann