cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Newbie
Newbie
74 Views
Registered: ‎09-15-2020

ZCU102 Petalinux: ramdisk - allocation error

Jump to solution

Hello,

When my Petalinux image size increases above a certain size (~128 MB), I get the following ramdisk allocation error:

 

Xilinx Zynq MP First Stage Boot Loader
Release 2018.3 Sep 11 2020 - 13:50:55
NOTICE: ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000
NOTICE: BL31: Secure code at 0x0
NOTICE: BL31: Non secure code at 0x10080000
NOTICE: BL31: v1.5(release):xilinx-v2018.2-919-g08560c36
NOTICE: BL31: Built : 14:40:05, Sep 15 2020
PMUFW: v1.1


U-Boot 2018.01 (Sep 15 2020 - 14:40:35 +0000) Xilinx ZynqMP ZCU102 rev1.0

I2C: ready
DRAM: 4 GiB
EL Level: EL2
Chip ID: zu9eg
MMC: mmc@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

Warning: ethernet@ff0e0000 MAC addresses don't match:
Address in ROM is 00:0a:35:04:c5:41
Address in environment is 00:0a:35:00:22:01
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2018_3

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete...... done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.1.147 (644 ms)
Hit any key to stop autoboot: 0
Device: mmc@ff170000
Manufacturer ID: 3
OEM: 5344
Name: SB16G
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
126809192 bytes read in 8262 ms (14.6 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: 0x10000108
Data Size: 7083891 Bytes = 6.8 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: 03f12d24796e119ad47e5aa03663aa4f7d3fb4b1
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: 0x106cc074
Data Size: 119680611 Bytes = 114.1 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: d7fd0342e4dab8c8de054952c640e3d355a9ad38
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: 0x106c1980
Data Size: 42544 Bytes = 41.5 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 7271a8e3898280e951ddeb1a7829ae3e4ec212c7
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x106c1980
Uncompressing Kernel Image ... OK
ERROR: Failed to allocate 0x7222e63 bytes below 0x8000000.
ramdisk - allocation error
bootm - boot application image from memory

 

I initially thought it has to do with the "System Memory Size" that I set in the hardware settings via petalinux-config, however the size is multiple gigs while my image size is under a gig. Any thoughts on how to take care of this problem?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
33 Views
Registered: ‎02-07-2018

HI @elk84 

If kernel or rootfs size increases and is greater than 128 MB, you need to do the following changes  & build again.


1. Mention the Bootm length in platform-top.h
#define CONFIG_SYS_BOOTM_LEN <value greater then image size>
2. Undef CONFIG_SYS_BOOTMAPSZ in platform-top.h

 

Thanks & regards

Aravind

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
---------------------------------------------------------------------------------------------

 

View solution in original post

1 Reply
Highlighted
Moderator
Moderator
34 Views
Registered: ‎02-07-2018

HI @elk84 

If kernel or rootfs size increases and is greater than 128 MB, you need to do the following changes  & build again.


1. Mention the Bootm length in platform-top.h
#define CONFIG_SYS_BOOTM_LEN <value greater then image size>
2. Undef CONFIG_SYS_BOOTMAPSZ in platform-top.h

 

Thanks & regards

Aravind

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
---------------------------------------------------------------------------------------------

 

View solution in original post