[U-Boot] AM335x Falcon Mode
Hi Everyone,
I'm trying to boot a Beaglebone-Black using Falcon Mode, so far no luck ! I'm using manline u-boot version v2017.01 configured using am335x_boneblack_defconfig and no other source changes. Here are the steps I performed running from an SD card (Fat Partition) :
U-Boot SPL 2017.01-dirty (Apr 18 2017 - 22:57:12) Trying to boot from MMC1MMC partition switch failed *** Warning - MMC partition switch failed, using default environment reading u-boot.img reading u-boot.img U-Boot 2017.01-dirty (Apr 18 2017 - 22:57:12 +0200) CPU : AM335X-GP rev 2.1 I2C: ready DRAM: 512 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 ** First descriptor is NOT a primary desc on 1:1 ** Net: cpsw, usb_ether Press SPACE to abort autoboot in 2 seconds
=> run args_mmc => run loadimage 8942296 bytes read in 610 ms (14 MiB/s) => run loadfdt 58129 bytes read in 56 ms (1013.7 KiB/s) => spl export fdt ${loadaddr} - ${fdtaddr} data abort pc : [<9ff5e4e8>] lr : [<9ff63925>] reloc pc : [<8080c4e8>] lr : [<80811925>] sp : 9df31be8 ip : 9ff8c349 fp : 9ffa124c r10: 9df31c84 r9 : 9df31ed8 r8 : 9ffa124c r7 : 00000007 r6 : 82000000 r5 : 9ffa124c r4 : 00000000 r3 : 00000000 r2 : 9ff8c530 r1 : 82000000 r0 : 9ff90251 Flags: Nzcv IRQs off FIQs on Mode SVC_32 Resetting CPU ...
resetting ...
Aynone could give me some hints?
Thank you !
Best Regards, Ayoub Zaki
Ayoub wrote...
=> run args_mmc => run loadimage 8942296 bytes read in 610 ms (14 MiB/s) => run loadfdt 58129 bytes read in 56 ms (1013.7 KiB/s) => spl export fdt ${loadaddr} - ${fdtaddr}
I have AM335x Falcon mode running with SPI flash (albeit an old 2014.xx U-Boot version) and the commands for settings it up look the same as the ones you have used.
Do you get any more information about where the data abort is coming from if you build and run U-Boot with #define DEBUG?
-Andy.
Hi Andy,
Thanks for the answer, I figured out what the problem is, in the fact I was using a zImage, using an uImage format solve the problem :-) It should maybe added to the documentation ;-)
best regards,
Ayoub Zaki On 20 April 2017 at 16:31:21 +02:00, Andy Pont andy.pont@sdcsystems.com wrote:
Ayoub wrote...
=> run args_mmc => run loadimage 8942296 bytes read in 610 ms (14 MiB/s) => run loadfdt 58129 bytes read in 56 ms (1013.7 KiB/s) => spl export fdt ${loadaddr} - ${fdtaddr}
I have AM335x Falcon mode running with SPI flash (albeit an old 2014.xx U-Boot version) and the commands for settings it up look the same as the ones you have used.
Do you get any more information about where the data abort is coming from if you build and run U-Boot with #define DEBUG?
-Andy.
Hello Ayoub,
Am 20.04.2017 um 16:35 schrieb ayoub.zaki@embexus.com:
Hi Andy,
Thanks for the answer, I figured out what the problem is, in the fact I was using a zImage, using an uImage format solve the problem :-) It should maybe added to the documentation ;-)
Patches are welcome!
;-)
bye, Heiko
best regards,
Ayoub Zaki On 20 April 2017 at 16:31:21 +02:00, Andy Pont andy.pont@sdcsystems.com wrote:
Ayoub wrote...
=> run args_mmc => run loadimage 8942296 bytes read in 610 ms (14 MiB/s) => run loadfdt 58129 bytes read in 56 ms (1013.7 KiB/s) => spl export fdt ${loadaddr} - ${fdtaddr}
I have AM335x Falcon mode running with SPI flash (albeit an old 2014.xx U-Boot version) and the commands for settings it up look the same as the ones you have used.
Do you get any more information about where the data abort is coming from if you build and run U-Boot with #define DEBUG?
-Andy.
U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Heiko wrote...
Thanks for the answer, I figured out what the problem is, in the fact I was using a zImage, using an uImage format solve the problem :-) It should maybe added to the documentation ;-)
Patches are welcome!
I don't know that part of the code well enough to know whether it is a bug that needs fixing so that it will support zImage files or whether, as Ayoub said, we just put in the docs that it doesn't!
-Andy.
participants (3)
-
Andy Pont -
ayoub.zaki＠embexus.com -
Heiko Schocher