cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
crwhite
Visitor
Visitor
216 Views
Registered: ‎03-31-2021

CPU Reset Loop with Petalinux Package Groups

Using Petalinux 2018.3, when any of the package groups are included the following message appears when attempting to boot:

Uncompressing Kernel Image ... OK
Loading Ramdisk to ffffffffff163000, end 07fff6d1 ... "Synchronous Abort" handler, esr 0x96000044
ELR: 100fb7d4
LR: 100a0488
x0 : 0000000000000002 x1 : 00000000106d8074
x2 : 0000000008e9c6d1 x3 : 0000000000e9cfff
x4 : 00000000106d8074 x5 : 0000000000000031
x6 : 000000007fe62250 x7 : ffffffffff163000
x8 : 000000007dd9b480 x9 : 0000000000000008
x10: 00000000ffffffd8 x11: 000000007ff00000
x12: 000000007fe9e070 x13: 000000007dd9a600
x14: ffffffffff163000 x15: 0000000000000008
x16: 0000000000000002 x17: 0000000007fff6d1
x18: 000000007dd9bdf8 x19: 0000000008e9c6d1
x20: 0000000008000000 x21: 00000000106d8074
x22: 000000007fe9dfd0 x23: 000000007fe9dfa8
x24: 000000007fe9dfa0 x25: 0000000010000108
x26: 0000000000000001 x27: 0000000000000000
x28: 0000000000080000 x29: 000000007dd9b5c0

Resetting CPU ...

resetting ...

 

This continues indefinitely. How can I fix this, so I am able to use the packagegroups?

The rootfs size is < 1GB, so it is not a RAM size issue (I have 2GB).

0 Kudos
4 Replies
stephenm
Xilinx Employee
Xilinx Employee
189 Views
Registered: ‎09-12-2007

Looks like a memory issue. you say you have 2GB. However, are they on the relevant partition?

0 Kudos
crwhite
Visitor
Visitor
164 Views
Registered: ‎03-31-2021

I am loading onto the on-board RAM. The board is a ZCU104, which has 2GB contiguous onboard RAM, and hosts the filesystem. Without adding the packagegroups I can successfully boot to that same memory region.

I attempted to increase CONFIG_SYS_BOOTM_LEN to 0x40000000 and undefined CONFIG_SYS_BOOTMAPSZ (per https://forums.xilinx.com/t5/Embedded-Linux/Booting-Error-Reading-Image-but-not-successful/m-p/894893/highlight/true#M28979) but that results in Kernel Panic (log attached).

Any ideas?

0 Kudos
watari
Teacher
Teacher
157 Views
Registered: ‎06-16-2013

Hi @crwhite 

 

Since there is memory location issue, you are facing this issue.

Refer the following log message.

 

Would you make sure memory setting, memory location and parameter of poetalinux-config ?

 

<snip>

## 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: 0x106d8058
Data Size: 273488375 Bytes = 260.8 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: 9241c2c915a23574cd9c1fc6e9ac89228a579a4c
Verifying Hash Integrity ... sha1+ OK

<snip>

[ 1.706312] Trying to unpack rootfs image as initramfs...
[ 6.705003] rootfs image is not initramfs (write error); looks like an initrd
[ 6.706527] /initrd.image: incomplete write (-28 != 273488375)
[ 6.783363] Freeing initrd memory: 267076K

<snip>

 

Best regards,

0 Kudos
crwhite
Visitor
Visitor
152 Views
Registered: ‎03-31-2021

The config is set to initramfs, the memory base is set to 0x0, with a size of 0x80000000. Kernel base is 0x0, u_boot text offset is 0x00100000.

I've attached my config file (formatted to txt) for reference.

0 Kudos