element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Avnet Boards General UZ3EG_IOCC: kernel hangs at memory init
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 353 subscribers
  • Views 1093 views
  • Users 0 members are here
  • Using Xilinx Tools
  • ZedBoard General Questions
  • Zedboard Hardware Design
  • Zedboard Training
Related

UZ3EG_IOCC: kernel hangs at memory init

mahadeva.hn
mahadeva.hn over 4 years ago

I am using UZ3EG IOCC board. For some reason, I'm not using petalinux tool to build the binaries. So building image independently.

 

My SDCARD image:

     BOOT.bin

     kernel_image=Image

     devicetree_image=devicetree.dtb

     ramdisk_image=uRamdisk.image.gz

 

bootargs

       console=ttyPS0,115200 rw earlycon clk_ignore_unused root=/dev/ram0 earlyprintk uio_pdrv_genirq.of_id=xlnx,generic-uio cma=512M cpuidle.off=1

 

uEnv.txt

# uramdisk filesystem

uz3eg_sdboot=echo Copying Linux from SD to RAM... && fatload mmc 0:1 0x2A00000 ${kernel_image} && fatload mmc 0:1 0x2000000 ${devicetree_image} && fatload mmc 0:1 0x6000000 ${ramdisk_image} && booti 0x2A00000 0x6000000 0x2000000

 

 

 

Xilinx Zynq MP First Stage Boot Loader

Release 2018.3   Mar 21 2021  -  07:31:44

PMU Firmware 2018.3     Mar 21 2021   07:32:08

PMU_ROM Version: xpbr-v8.1.0-0

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.5(release):xilinx-v2018.2-919-g08560c36

NOTICE:  BL31: Built : 07:30:08, Mar 21 2021

PMUFW:  v1.1

 

 

 

 

U-Boot 2018.01-dirty (Apr 06 2021 - 07:35:05 +0530) Xilinx ZynqMP ZCU102 rev1.0

 

 

I2C:   ready

DRAM:  2 GiB

EL Level:       EL2

Chip ID:        zu3eg

MMC:   sdhci@ff170000: 0 (SD)

*** Warning - bad CRC, using default environment

 

 

In:    serial@ff000000

Out:   serial@ff000000

Err:   serial@ff000000

Bootmode: SD_MODE1

Net:   ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id

Error, wrong i2c adapter 1 max 1 possible

I2C EEPROM MAC address read failed

 

 

Warning: ethernet@ff0e0000 (eth0) using random MAC address - 06:85:d1:f0:d1:9f

eth0: ethernet@ff0e0000

Hit any key to stop autoboot:  0

switch to partitions #0, OK

mmc0 is current device

Device: sdhci@ff170000

Manufacturer ID: 58

OEM: 4444

Name: DDINC

Tran Speed: 50000000

Rd Block Len: 512

SD version 3.0

High Capacity: Yes

Capacity: 14.9 GiB

Bus Width: 4-bit

Erase Group Size: 512 Bytes

reading uEnv.txt

933 bytes read in 14 ms (64.5 KiB/s)

Loaded environment from uEnv.txt

Importing environment from SD ...

Running uenvcmd ...

Copying Linux from SD to RAM...

reading Image

14497800 bytes read in 991 ms (14 MiB/s)

reading devicetree.dtb

34792 bytes read in 20 ms (1.7 MiB/s)

reading uRamdisk.image.gz

168923073 bytes read in 11264 ms (14.3 MiB/s)

## Loading init Ramdisk from Legacy Image at 06000000 ...

   Image Name:  

   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)

   Data Size:    168923009 Bytes = 161.1 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 02000000

   Booting using the fdt blob at 0x2000000

   Loading Ramdisk to 33da5000, end 3debdf81 ... OK

   Loading Device Tree to 000000000fff4000, end 000000000ffff7e7 ... OK

 

 

Starting kernel ...

 

 

[    0.000000] Booting Linux on physical CPU 0x0

[    0.000000] Linux version 4.14.0-xilinx-v2018.3 (mahadeva@mahadeva-OMEN-Laptop1

[    0.000000] Boot CPU: AArch64 Processor [410fd034]

[    0.000000] Machine model: Avnet UltraZed-3EG

[    0.000000] earlycon: cdns0 at MMIO 0x00000000ff000000 (options '115200n8')

[    0.000000] bootconsole [cdns0] enabled

[    0.000000] cma: Reserved 256 MiB at 0x0000000023c00000

[    0.000000] psci: probing for conduit method from DT.

[    0.000000] psci: PSCIv1.1 detected in firmware.

[    0.000000] psci: Using standard PSCI v0.2 function IDs

[    0.000000] psci: MIGRATE_INFO_TYPE not supported.

[    0.000000] random: fast init done

[    0.000000] percpu: Embedded 20 pages/cpu @ffffffc83ff79000 s44312 r8192 d29410

[    0.000000] Detected VIPT I-cache on CPU0

[    0.000000] CPU features: enabling workaround for ARM erratum 845719

[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 517120

[    0.000000] Kernel command line: console=ttyPS0,115200 rw earlycon clk_ignore_1

[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)

[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)

[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)

 

 

My kernel is hanging at memory init stage.

  • Sign in to reply
  • Cancel
  • drozwood90
    0 drozwood90 over 4 years ago

    Hi there,

     

    Have you taken a look at our build flow?  Looking at what we are doing with the image might help you see what you are missing.  We use the normal build tools and scripted flow.

    If you would like to, I can post links to a few resources that will help you see what the build flow Avnet recommends, which again, might help you out with your flow.

     

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • mahadeva.hn
    0 mahadeva.hn over 4 years ago in reply to drozwood90

    Hi Daniel,

     

    Yes, It will be helpful for me. Please share the flow.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • drozwood90
    0 drozwood90 over 4 years ago in reply to mahadeva.hn

    Hi there,

     

    A few are a little on the older side, but I suggest you start with 2020.1 for our repositories regardless.  The blogs should help you get through a build.

    Once you get through, you should be able to take a look at what we did and what - if anything - you might be missing or need.  Sometimes the order matters in building these projects.

     

    If you are using Vitis, you can use the make commands in the vitis repo to drive all of the other build flows.

    Avnet HDL git HOWTO (Vivado 2020.1 and earlier)

    Using Avnet Build Scripts to Build a PetaLinux BSP (2019.2 and earlier)

    Accelerating PetaLinux BSP Build Time

    2020.1 Vitis Repo Changes!

    https://www.hackster.io/AlbertaBeef/vitis-ai-1-3-flow-for-avnet-vitis-platforms-cd0c51

     

    I hope this helps you!

     

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube