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!

Showing results for 
Search instead for 
Did you mean: 
Observer htran17
Registered: ‎01-23-2019

booting keep resetting

I am using petalinux 2018.2. I add so much packages. When I boot the ultrazed-eg IOCC from the SD card. It has the problem like this 

Loading Ramdisk to fffffffff5d30000, end 07fffa88 ... "Synchronous Abort" handler, esr 0x96000044
ELR: 8084024
LR: 80208d0

I went to /project-spec/meta-user/recipes-bsp/u-boot/files/platform-auto.h to modifiled #define CONFIG_SYS_BOOTM_LEN from 0xF000000 to 0xFF00000. unfortunaly it didn't solve the problem.

this is the blog form TERA TERM


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: 0x106b9f78
Data Size: 304937608 Bytes = 290.8 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: d62d1194a1c19374be87d0fd1f0b0b51bddc1d45
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: 0x106b1c60
Data Size: 33363 Bytes = 32.6 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 4b7857c5ff6ecaba735e3154ebe656b3f065f642
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x106b1c60
Uncompressing Kernel Image ... OK
Loading Ramdisk to fffffffff5d30000, end 07fffa88 ... "Synchronous Abort" handler, esr 0x96000044
ELR: 8084024
LR: 80208d0
x0 : 000000000000003e x1 : 00000000106b9f78
x2 : 00000000122cfa88 x3 : 000000000a2cffff
x4 : 00000000106b9f78 x5 : 0000000000000038
x6 : 000000007fe61b18 x7 : fffffffff5d30000
x8 : 000000007dd92470 x9 : 0000000000000008
x10: 00000000ffffffd8 x11: 000000007ff00000
x12: 000000007fe9d788 x13: 000000007dd915f0
x14: fffffffff5d30000 x15: 0000000000000008
x16: 0000000000000002 x17: 0000000007fffa88
x18: 000000007dd92de8 x19: 00000000122cfa88
x20: 0000000008000000 x21: 00000000106b9f78
x22: 000000007fe9d6e8 x23: 000000007fe9d6c0
x24: 000000007fe9d6b8 x25: 0000000010000104
x26: 0000000000000001 x27: 0000000000000000
x28: 0000000000080000 x29: 000000007dd925b0

Resetting CPU ...

resetting ...
Xilinx Zynq MP First Stage Boot Loader
Release 2018.2 Feb 27 2019 - 17:51:15
NOTICE: ATF running on XCZU3EG/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 : 22:50:37, Feb 27 2019
PMUFW: v1.0

U-Boot 2018.01 (Feb 28 2019 - 10:35:15 -0500) Xilinx ZynqMP ZCU102 rev1.0

I2C: ready
EL Level: EL2
Chip ID: zu3eg
MMC: sdhci@ff160000: 0 (eMMC), sdhci@ff170000: 1 (SD)
SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
*** Warning - bad CRC, using default environment

In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Board: Xilinx ZynqMP
Net: ZYNQ GEM: ff0e0000, phyaddr 9, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for uz3eg-iocc-2018-2

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete..................



0 Kudos
1 Reply
Registered: ‎06-03-2015

Re: booting keep resetting


From error log :

"Synchronous Abort" handler itslef is saying that

"trying to access the memory area which does not have permissions" 

Memory address is not avalible,  still we are tryign to access or

your instruction is not having permissions to access the area , still you are tryign the same

& there are two things Prefetch abort or Data abort , one is regards to Instruction & other is Data access.

For Resolving issue:  

Remove existing packages which you have add, start add each package again & chcek booting each time, u will come to know exact issue where it is hitting out of memory access area.

Provide Kudos is the post is helpful

Thanks & Regards

Satish G

G Satish Kumar
0 Kudos