cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
siddh4nt
Adventurer
Adventurer
3,276 Views
Registered: ‎08-01-2017

Booting Error : Reading Image but not successful

Jump to solution

After building Image, I created BOOT.BIN and image.ub, and copied to SD card, When I am trying to boot the ZCU102, I am getting following error:

 

 

ZynqMP> boot
Device: sdhci@ff170000
Manufacturer ID: 3
OEM: 5344
Name: SU08G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 7.4 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
160364920 bytes read in 10410 ms (14.7 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
Using 'conf@system-top.dtb' configuration
Trying 'kernel@1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x100000f8
Data Size: 6937389 Bytes = 6.6 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: d6b7fbbfc7501264de7503648e96cf12722a8f1b
Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 10000000 ...
Using 'conf@system-top.dtb' configuration
Trying 'ramdisk@1' ramdisk subimage
Description: petalinux-user-image
Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x106a9384
Data Size: 153378913 Bytes = 146.3 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: c266b1fecfacf60fb6ea8607086fd3b90abd8d7b
Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 10000000 ...    
Using 'conf@system-top.dtb' configuration
Trying 'fdt@system-top.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x1069dd2c
Data Size: 46484 Bytes = 45.4 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 82737560d9591d004466da53607f6d743baf063a
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x1069dd2c
Uncompressing Kernel Image ... OK
Loading Ramdisk to fffffffffedb9000, end 07fff061 ... "Synchronous Abort" handler, esr 0x96000044
ELR: 8083fc4
LR: 8020878
x0 : 0000000000000083 x1 : 00000000106a9384
x2 : 0000000009246061 x3 : 0000000001246fff
x4 : 00000000106a9384 x5 : 0000000000000031
x6 : 000000007fe5ec68 x7 : fffffffffedb9000
x8 : 000000007dd8f2b0 x9 : 0000000000000008
x10: 00000000ffffffd8 x11: 000000007ff00000
x12: 000000007fe9ddc8 x13: 000000007dd8e430
x14: fffffffffedb9000 x15: 0000000000000008
x16: 0000000000000002 x17: 0000000007fff061
x18: 000000007dd8fdf8 x19: 0000000009246061
x20: 0000000008000000 x21: 00000000106a9384
x22: 000000007fe9dd28 x23: 000000007fe9dd00
x24: 000000007fe9dcf8 x25: 00000000100000f8
x26: 0000000000000001 x27: 0000000000000000
x28: 0000000000080000 x29: 000000007dd8f3f0

Resetting CPU ...

resetting ...                   // after this it is running in loop
Xilinx Zynq MP First Stage Boot Loader
Release 2018.2 Oct 1 2018 - 14:59:42
NOTICE: ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000
NOTICE: BL31: Secure code at 0x0
NOTICE: BL31: Non secure code at 0x8000000
NOTICE: BL31: v1.4(release):xilinx-v2018.1-4-g93a69a5a
NOTICE: BL31: Built : 09:30:14, Oct 1 2018
PMUFW: v1.0


U-Boot 2018.01 (Oct 01 2018 - 14:56:47 +0530) Xilinx ZynqMP ZCU102 rev1.0

I2C: ready
DRAM: 4 GiB
EL Level: EL2
Chip ID: zu9eg
MMC: sdhci@ff170000: 0 (SD)
SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment

In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
Bootmode: LVL_SHFT_SD_MODE1
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for eldaas_linux

Hit any key to stop autoboot: 0

 

 

What is wrong here? is there anything else I should copy on SD-card?

 

Thanks & Regards

-Siddhant

0 Kudos
1 Solution

Accepted Solutions
sandeepg
Moderator
Moderator
3,232 Views
Registered: ‎04-24-2017

Refer UG1144 page 52.

 

If kernel or rootfs size increases and is greater than 128 MB, you need to do the following:
1. Mention the Bootm length in platform-top.h
#define CONFIG_SYS_BOOTM_LEN <value greater then image size>
2. Undef the CONFIG_SYS_BOOTMAPSZ in platform-top.h

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------

View solution in original post

0 Kudos
6 Replies
trigger
Voyager
Voyager
3,253 Views
Registered: ‎09-14-2016
maybe the ramdisk is too big...
0 Kudos
sandeepg
Moderator
Moderator
3,233 Views
Registered: ‎04-24-2017

Refer UG1144 page 52.

 

If kernel or rootfs size increases and is greater than 128 MB, you need to do the following:
1. Mention the Bootm length in platform-top.h
#define CONFIG_SYS_BOOTM_LEN <value greater then image size>
2. Undef the CONFIG_SYS_BOOTMAPSZ in platform-top.h

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------

View solution in original post

0 Kudos
siddh4nt
Adventurer
Adventurer
3,211 Views
Registered: ‎08-01-2017

Hi Sandeepg,

 

Thanks for reply,  it will certainly help me.


I too read it in user guide, but I could not trace the location of platform-top.h.

Could you please tell me, in which directory this file is located?

 

 

Thanks &  Regards

-Siddhant

0 Kudos
siddh4nt
Adventurer
Adventurer
3,210 Views
Registered: ‎08-01-2017
Thanks Trigger for the hint : ), I shall look into this.
0 Kudos
siddh4nt
Adventurer
Adventurer
3,205 Views
Registered: ‎08-01-2017

Hi,
under this directory
<plnxproj_root>/project-spec/meta-plnx-generated/recipes-bsp/u-boot/configs

 

I do have two files in configs directory : config.cfg and platform-auto.h 


I dont see platform-top.h file,
as per user guide
platform-top.h
located at <plnxproj_root>/project-spec/meta-user/recipes-bsp/
u-boot/files/.

But, in my project directory there is no "files" directory available.

Any pointer to this?

Thanks.

0 Kudos
siddh4nt
Adventurer
Adventurer
3,186 Views
Registered: ‎08-01-2017
Thanks sandeep, Smart Work! it resolved the issue.
0 Kudos