Re: u-boot-omap fails to boot panda-es
On Mon, Apr 20, 2015 at 2:59 PM, Neil Williams <codehelp@debian.org> wrote:
> On Mon, 20 Apr 2015 12:21:22 -0700
> Vagrant Cascadian <vagrant@aikidev.net> wrote:
>
>> On 2015-04-20, Neil Williams wrote:
>> > On Mon, 20 Apr 2015 09:21:52 -0500
>> > Robert Nelson <robertcnelson@gmail.com> wrote:
>> >
>> >> On Mon, Apr 20, 2015 at 9:10 AM, Robert Nelson
>> >> <robertcnelson@gmail.com> wrote:
>> >> > On Mon, Apr 20, 2015 at 7:49 AM, Neil Williams
>> >> > <codehelp@debian.org> wrote:
>> >> >> These instructions: https://wiki.debian.org/PandaBoard don't
>> >> >> give a bootable SD card for the panda-es:
>> >> >>
>> >> >> U-Boot SPL 2014.10+dfsg1-5 (Apr 07 2015 - 22:19:50)
>> >> >> OMAP4460 ES1.1
>> >> >> SPL: Please implement spl_start_uboot() for your board
>> >> >> SPL: Direct Linux boot not active!
>> >> >> reading u-boot.img
>> >> >> spl_load_image_fat: error reading image u-boot.img, err - -1
>> >> >> ### ERROR ### Please RESET the board ###
>> >> >>
>> >> >> There's no u-boot.img in the package.
>>
>> You might try with the omap4_panda/MLO file rather than
>> x-loader-omap4-panda. It's my understanding that the MLO file shipped
>> in u-boot-omap can be used instead of x-loader.
>
> I am using the MLO from the omap4_panda directory of the package, sorry
> - should have made that clear.
>
>> If that works, the instuctions probably should be updated on the wiki.
>>
>
> The instructions need updating whichever way this finally gets to a
> u-boot prompt.
>
>> >> >> Is there specific support for panda-es or is there an issue in
>> >> >> the u-boot-omap package for panda/panda-es?
>> >> >
>> >> > and u-boot.img can be generated via:
>> ...
>> >> mkimage -A arm -T firmware -C none -O u-boot -a 0x80008000 -e
>> >> 0x80008000 -n "u-boot" -d ./u-boot.bin ./u-boot.img
>> >
>> > Image Name: u-boot
>> > Created: Mon Apr 20 16:01:59 2015
>> > Image Type: ARM U-Boot Firmware (uncompressed)
>> > Data Size: 210468 Bytes = 205.54 kB = 0.20 MB
>> > Load Address: 80008000
>> > Entry Point: 80008000
>> >
>> > That gets me a little further, but then it hangs at:
>> >
>> > U-Boot SPL 2014.10+dfsg1-5 (Apr 07 2015 - 22:19:50)
>> > OMAP4460 ES1.1
>> > SPL: Please implement spl_start_uboot() for your board
>> > SPL: Direct Linux boot not active!
>> > reading u-boot.img
>> > reading u-boot.img
>>
>> Could you try the prepared images for debian-installer:
>>
>> http://d-i.debian.org/daily-images/armhf/daily/hd-media/SD-card-images/
>> http://d-i.debian.org/daily-images/armhf/daily/hd-media/SD-card-images/README.concatenateable_images
>>
>> I believe these images have u-boot written directly to the raw boot
>> media, rather than as files on the filesystem. They also use the MLO
>> file shipped with u-boot rather than x-loader. That *might* work
>> better.
>
> Those files get me back to:
> U-Boot SPL 2014.10+dfsg1-5 (Apr 07 2015 - 22:19:50)
> OMAP4460 ES1.1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> ### ERROR ### Please RESET the board ###
>
> Based on the output of mkimage -l from an older (working) u-boot setup
> for panda, I did try:
>
> sudo mkimage -A arm -T firmware -C none -O u-boot -a 0x80e80000 -e 0 -n
> "u-boot" -d /usr/lib/u-boot/omap4_panda/u-boot.bin /mnt/image/u-boot.img
>
> Image Name: u-boot
> Created: Mon Apr 20 20:37:52 2015
> Image Type: ARM U-Boot Firmware (uncompressed)
> Data Size: 220960 Bytes = 215.78 kB = 0.21 MB
> Load Address: 80e80000
> Entry Point: 00000000
>
> That fails too (I've also tried u-boot-omap:armhf from experimental.
>
> U-Boot SPL 2015.04-rc5+dfsg1-1 (Apr 07 2015 - 23:00:30)
> OMAP4460 ES1.1
> SPL: Please implement spl_start_uboot() for your board
> SPL: Direct Linux boot not active!
> reading u-boot.img
> reading u-boot.img
>
> The only u-boot I have which actually boots is one from Trusty.
>
> What I'm *trying* to achieve is support for bootz. Before I go much
> further, can I check that bootz is supported by the current u-boot in
> jessie or should I stop here?
bootz is enable on the omap4_panda target by default in u-boot
"v2014.10", the debian patches didn't patch that out..
http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/ti_armv7_common.h;h=85171dbb4c4fb9e13e6a9e9766f98c9820da2490;hb=c43fd23cf619856b0763a64a6a3bcf3663058c49#l176
Regards,
--
Robert Nelson
https://rcn-ee.com/
Reply to: