Re: Latest SheevaPlug u-boot
NO,
It does not work:
Marvell>> tftpboot 0x0800000 u-boot-my.kwb
Using egiga0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.200
Filename 'u-boot-my.kwb'.
Load address: 0x800000
Loading: ###########################
done
Bytes transferred = 386820 (5e704 hex)
Marvell>> go 0x800200
## Starting application at 0x00800000 ...
Stuck here...
Someone on u-boot mail list told me that it is not supposed to work from RAM.
I tired the same trick with known good image already installed in the
Flash and it also did not work.
On Wed, Nov 7, 2012 at 11:42 AM, DrEagle <dreagle@doukki.net> wrote:
> Le 07/11/2012 10:30, Dimax a écrit :
>> Thanks.
>>
>>> You can load it from uboot and test it before flashing it.
>>> Just add an offset of 0x200 (the header) to you loaded uboot address.
>>> then jump to this address with the uboot command "go 0x....."
>>
>> Can you please explain it.
>> The make generated following for the image I have:
>
> # Notice that we load the image at 0x800000 but start running it from 0x800200.
> This is because the first 0x200 bytes of are the kirkwood image header, and the real executable starts after the header.
>
>>> ext2load usb 0 0x800000 u-boot.kwb
>>> go 0x800200
>
> You can also, as said on the wiki page given, load the uboot.elf file directly with the JTAH using OpenOCD.
>
> The SheevaPlug in mainly unbrickable.
> You may only take care to not corrupt your ubifs filesystem by overlapping with flashing !
>
>> Image Type: Kirkwood Boot from NAND Flash Image
>> Load Address: 00600000
>> Entry Point: 00600000
>>
>> So I'm not sure where to add the 0x200 ?
>> Should I load a new image into RAM or Flash?
>>
>>
>> On Wed, Nov 7, 2012 at 11:19 AM, DrEagle <dreagle@doukki.net> wrote:
>>> Hi,
>>>
>>> Le 07/11/2012 07:25, Dimax a écrit :
>>>> HI,
>>>>
>>>> I'm trying to build the very latest u-boot version for SheevaPlug.
>>>> The reason is the below thread:
>>>> http://lists.denx.de/pipermail/u-boot/2012-October/138533.html
>>>>
>>>> In short u-boot fails to mount ubifs partition after power short. If I
>>>> boot from USB stick debian kernel manage to recover the partition.
>>>> People from u-boot stuff suggested me to apply a number of patches to
>>>> u-boot. They sad that it should let u-boot to be able to mount broken
>>>> ubifs partition after that.
>>>>
>>>> I have build latest u-boot main line using native GCC on one of my
>>>> running SheevaPlug boards.
>>>
>>> You can cross build your uboot also from a linux box.
>>>
>>>> Before I tun it and potentially brick my board I'd like to ask if
>>>> someone did it.
>>>
>>> You can load it from uboot and test it before flashing it.
>>> Just add an offset of 0x200 (the header) to you loaded uboot address.
>>> then jump to this address with the uboot command "go 0x....."
>>>
>>>> I was in contact with Martin Michlmayr and Clint who maintain Debian
>>>> port of the u-boot for Marvell boards. Martin told me:
>>>>
>>>>> There are some but not many; e.g. there are some patches to add SD
>>>>> support on the SheevaPlug.
>>>>> You can download the source code from the Debian repo and check it out;
>>>>> the Debian patches are split out.
>>>>
>>>> Actually I do not care about SD support and want to try main line
>>>> u-boot. Should it work?
>>>
>>> Yes, it might work.
>>> Save your env settings because mainline will be different.
>>> Take care also of the size of uboot binary when loading, mainline may be bigger.
>>>
>>>> If not what is the procedure to build Debian one?
>>>
>>> $ apt-get source ...
>>> $ cd uboot
>>> $ dpkg-buildpackage -rfakeroot -aarmel
>>>
>>>> Thanks.
>>>
>>> Some more advice at https://doukki.net/doku.php?id=wiki:tutoriels:uboot.howto
>>>
>>>
>>
>
>
Reply to: