Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 325 subscribers
  • Views 2022 views
  • Users 0 members are here
Related

Booting from the SD-card: Uboot stuck at I2C:

deville

Hi Everyone,

 

I'm doing a manual build for the Ultrazed-EV-SOM board and When I try to boot the message queue stops at I2C:

By absence of the defconfig of the board I used the  Xilinx ZynqMP ZCU102 revA defconfig like I've encountered on the old Avnet forums.

 

 

Xilinx Zynq MP First Stage Boot Loader

 

Release 2018.2 Feb 6 2019 - 12:16:26

NOTICE: ATF running on XCZU7EV/silicon v4/RTL5.1 at 0xfffea000

NOTICE: BL31: Secure code at 0x0

NOTICE: BL31: Non secure code at 0x8000000

 

NOTICE: BL31: v1.4(release):93a69a5a

NOTICE: BL31: Built : 12:25:57, Feb 5 2019

 

PMUFW:\0x09v1.0

 

U-Boot 2018.01-dirty (Feb 06 2019 - 12:11:01 +0100) Xilinx ZynqMP ZCU102 revA

I2C:

 

Has someone an idea how to get past this or what might be wrong?

 

Deville

Parents Reply Children
  • 0 in reply to drozwood90

    Good idea Daniel, I forgot about this option because the original SD got corrupted somehow.

     

    After testing with some files which came pre-build ( uz7ev_evcc_sd_oob_2017_4_bsp ) I got past this message, but this only clears the hardware.

     

    Meanwhile I'm trying to extract the U-boot sources from the Petalinux BSP source files which where provided by Avnet. This is quite the hassle.

     

    Deville

  • 0 in reply to deville

    Deville,

     

    Can you post the model number of the card you were using?  It is possible it is the model, not the type.  ZU+ does support SDHC, but we also know that the controllers in SDCARDS are not always 100% to the standards and thus are not necessarily compatible.  As such, we have actually partnered with Delkin to verify / test their SDCARDS over temperature (chart of testing in the document listed below).

     

    There is a SDCARD Advice document that has pointers to the manuals where all the details of what is supported for the various Xilinx products.

    http://avnet.me/sdcard_advicev2

    See page 5.  Those came straight from the linked documentation, see appendix c.

     

    As far as I know, we do not typically have / manipulate the sources for U-Boot.  We leverage what is on the Xilinx GIT regarding the boot loaders at each level of boot.  Typically we only mess with the OS level stuff (drivers / resourcing, etc.).  Have you checked out their GIT for the sources?

     

    --Dan

  • 0 in reply to drozwood90

    Hi Dan, Thanks for sticking with me for this.

     

    The Card product number is: MB-MC32GA/EU : https://sg.rs-online.com/web/p/sd-cards/1449017/

    But I used the same card to get passed the original "IC: " message so I assume my problem is due to something else.

     

    Yes, I do checkout the Xilinx repositories and build from there as i've done for the ZCU102 board. It is good to know I should continue to use my original Xilinx boot process files because it's needs some hacking to extract the original sources from the Petalinux build environment.   

     

    Deville

  • 0 in reply to deville

    I got past this message by extracting the correct source files from the Petalinux project && I like to add how I extracted the Petalinux source files.

     

    1.First make a backup directory:

    mkdir ~/rsync-peta-project

     

    2.then create and build the project

    #for this example uz7ev_evcc_2018_2.bsp

    petalinux-create -t project -s /home/user/uz7ev_evcc_2018_2.bsp

     

    cd ~/uz7ev_evcc_2018_2

     

    #This starts the build of the project.

    petalinux-build

     

    3.In another terminal run following command

    while true; do rsync -av ~/uz7ev_evcc_2018_2/  ~/rsync-peta-project/  ; sleep 30; done

     

    There you can search the backup directory for the the source files:

    .config, platform-auto.h, platform-top.h, system-top.dtb, etc..

  • 0 in reply to deville

    Hi Deville,

     

    I've recently encountered the exactly same problem you had done.

    I'm using buildroot with Xilinx uboot and Linux. It has no defconfig file, device tree files, and header files for ultrazed-ev.

    So I used "zcu102 defconfig" and encountered the same issue.

     

    I'm now learning the process of building embedded Linux package. I'm wondering whether you would share your finding.

     

    Thank you for your consideration.

     

    Thanks - S.Y.