UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Newbie sauron3145
Newbie
2,421 Views
Registered: ‎07-17-2017

After Increase the QT5 library,the image.ub size becomes larger,and boot failed.petalinux2016.4 zcu102

Hi 

    I choose petalinux-config -c rootfs  Filesystem Packages-->mics-->packagegroup-petalinux-qt, and petalinux-build. In <petalinux-project-path>/images/linux/ the image.ub size is 179M.Then I copy BOOT.BIN and image.ub to SD card.the boot info is :

   

Xilinx Zynq MP First Stage Boot Loader
Release 2016.3 Mar 8 2017 - 11:38:43
Platform: Silicon (3.0), Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
SD1 with level shifter Boot Mode
Bitstream download to start now
XPFW: Calling ROM PWRUP Handler..Done
XPFW: Calling ROM Isolation Handler..Done
PL Configuration done successfully
XPFW: Calling ROM PWRUP Handler..Done
XPFW: Calling ROM PWRUP Handler..Done
Initializing TCM ECC
PMUFW: PmInit:
NODE_APLL #3:
acpu #1 { NODE_APU }
gdma #1 { NODE_GDMA }
dp_dma #1 { NODE_DP }
dbg_tstmp #0 { }
NODE_VPLL #1:
dp_audio #1 { NODE_DP }
NODE_DPLL #2:
ddr #1 { NODE_DDR }
pcie #1 { NODE_PCIE }
NODE_RPLL #5:
dp_video #1 { NODE_DP }
dp_stc #1 { NODE_DP }
sdio1 #1 { NODE_SD_1 }
pcap #0 { }
pl2 #1 { NODE_PL }
pl3 #1 { NODE_PL }
timestamp #0 { }
NODE_IOPLL #29:
dbg_trace #0 { }
dbg_fpd #0 { }
gpu #1 { NODE_GPU }
sata #1 { NODE_SATA }
gtg_ref0 #0 { }
usb3_dual #0 { }
gem0 #1 { NODE_ETH_0 }
gem1 #1 { NODE_ETH_1 }
gem2 #1 { NODE_ETH_2 }
gem3 #1 { NODE_ETH_3 }
usb0_bus #1 { NODE_USB_0 }
usb1_bus #1 { NODE_USB_1 }
qspi #1 { NODE_QSPI }
sdio0 #1 { NODE_SD_0 }
uart0 #1 { NODE_UART_0 }
uart1 #1 { NODE_UART_1 }
spi0 #1 { NODE_SPI_0 }
spi1 #1 { NODE_SPI_1 }
can0 #1 { NODE_CAN_0 }
can1 #1 { NODE_CAN_1 }
cpur5 #1 { NODE_RPU }
iou_switch #0 { }
csu_pll #0 { }
lpd_switch #0 { }
lpd_ls_bus #0 { }
dbg_lpd #0 { }
nand #1 { NODE_NAND }
adma #1 { NODE_ADMA }
pl0 #1 { NODE_PL }
pl1 #1 { NODE_PL }
gem_tsu #4 { NODE_ETH_3, NODE_ETH_2, NODE_ETH_1, NODE_ETH_0 }
dll #2 { NODE_SD_1, NODE_SD_0 }
ams #0 { }
i2c0 #1 { NODE_I2C_0 }
i2c1 #1 { NODE_I2C_1 }
 ATF running on XCZU9EG/silicon v3/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE: BL31: Secure code at 0x0
NOTICE: BL31: Non secure code at 0x8000000
NOTICE: BL31: v1.2(release):f2b7927
NOTICE: BL31: Built : 11:39:03, Mar 8 2017


U-Boot 2016.07 (Mar 08 2017 - 11:50:54 -0800)

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

In: serial
Out: serial
Err: serial
Bootmode: LVL_SHFT_SD_MODE1
Net: ZYNQ GEM: ff0e0000, phyaddr 12, interface rgmii-id
eth0: ethernet@ff0e0000
Hit any key to stop autoboot: 0
Device: sdhci@ff170000
Manufacturer ID: 3
OEM: 5344
Name: SL16G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 14.8 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
186856520 bytes read in 12271 ms (14.5 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
Using 'conf@1' configuration
Trying 'kernel@0' kernel subimage
Description: Linux Kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x100000d8
Data Size: 14404608 Bytes = 13.7 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: 67753c85d7b99303c2c673e6195fdd8f334c09b3
Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 10000000 ...
Using 'conf@1' configuration
Trying 'ramdisk@0' ramdisk subimage
Description: ramdisk
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x10dc5884
Data Size: 172414926 Bytes = 164.4 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: 01dd9fbcfe084bc4d82a45d8ae1d06800dcc6ae0
Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 10000000 ...
Using 'conf@1' configuration
Trying 'fdt@0' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x10dbcdd0
Data Size: 35327 Bytes = 34.5 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 349030d0b6f649df3138f8f4ec1b4d139bf8591c
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x10dbcdd0
Loading Kernel Image ... OK
Loading Ramdisk to fffffffffdb92000, end 07fff7ce ... "Synchronous Abort" handler, esr 0x96000044
ELR: 7ff57ed0
LR: 7ff239ec
x0 : fffffffffdb92000 x1 : 0000000010dc5884
x2 : 000000000246dfff x3 : 0000000000000009
x4 : 0000000000000000 x5 : 0000000000000006
x6 : 0000000000000001 x7 : 000000000000000f
x8 : 000000007dec83d0 x9 : 0000000000000008
x10: 000000007dec7c71 x11: 0000000000000021
x12: 0000000000000008 x13: 00000000ffffffff
x14: fffffffffdb92000 x15: 0000000000000002
x16: 0000000007fff7ce x17: ffffffffffffffff
x18: 000000007dec8de8 x19: 000000007ff8abc0
x20: 0000000010dc5884 x21: 0000000008000000
x22: 000000000a46d7ce x23: 000000007ff8abc8
x24: 000000007ff8abf0 x25: 000000007ff7e810
x26: 00000000100000d8 x27: 000000007ff0bae4
x28: 0000000000080000 x29: 000000007dec8520

Resetting CPU ...

resetting ...
PMUFW: PmSystemShutdown: (1)
PMUFW: PmInitSuspendCb: of NODE_RPU (203, 4294967295, 0, 0)

 

 

 

 

 

    It seems to be due to the size of ramdisk is too large, what can be the way to increase the size of the guide rootfs or ramdisk?

   In addition, I use the reference design imag.ub the boot information is not the same, the reference design image and no load ramdisk the process, what is the reason?

0 Kudos
4 Replies
Highlighted
Visitor grass_be
Visitor
1,677 Views
Registered: ‎07-14-2015

Re: After Increase the QT5 library,the image.ub size becomes larger,and boot failed.petalinux2016.4 zcu102

Were you able to solve this problem?
I just included QT5 in Petalinux and experience the same thing.

0 Kudos
Explorer
Explorer
1,673 Views
Registered: ‎03-22-2016

Re: After Increase the QT5 library,the image.ub size becomes larger,and boot failed.petalinux2016.4 zcu102

I ran into this issue as well. I'm not sure exactly what the ramdisk size limit is, but my root filesystem got to be something like 600MB when I added qt, and that was never going to work.

 

I was able to switch to using an SD card partition as my root filesystem without issue, however. Is that a possibility for you?

 

I found this command in my notes from when I last did this: gunzip -c rootfs.cpio.gz | pax -r -c

 

I believe my process was:

- Reconfigure the petalinux project to use SD second partition for root filesystem.

- Partition SD card so that partition 1 is FAT (fdisk type 0x06, 0x0B, 0x0C, etc) and partition 2 is "linux" (type 0x83).

- Format the first partition vfat, second partition as something linux can use (I used ext3 for simplicity).

- Mount both partitions.

- Put BOOT.BIN and image.ub on the first partition.

- Change into the mount directory for the second partition.

- Extract the root filesystem image with the command (gunzip -c rootfs.cpio.gz | pax -r -c)

- sync and unmount

0 Kudos
1,667 Views
Registered: ‎04-20-2017

Re: After Increase the QT5 library,the image.ub size becomes larger,and boot failed.petalinux2016.4 zcu102

had the same proble when i added full opencv support on my zynq board...but persistent filesystem on sd card is screaming to fail in long term use
i ended up compiling the package with petalinx-build, copin all relevant libs to a sd card, commpling again without the package (so the big libs are not paart of my rootfs)
later after boot i load the libraries from read only memory per initd script that runs on bootup
nice small bootimg, no risk of persistent filesystem
0 Kudos
Moderator
Moderator
1,659 Views
Registered: ‎04-24-2017

Re: After Increase the QT5 library,the image.ub size becomes larger,and boot failed.petalinux2016.4 zcu102

Hi @sauron3145,

 

FIT image(image.ub) is not recommend to use when you have large rootfs instead you can use ext4 partition on SD boot.

 

When your image.ub size is large undefine the BOOTMAPSIZE in <plnx-proj-root>/project-spec/meta-user/recipes-bsp/u-boot/files/platform-top.h

 

#undef CONFIG_SYS_BOOTMAPSZ
Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

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