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

HI,

It seems odd that it is stopping at that location.  The first thing that comes to my mind is to reseat the SOM on the carrier.  The connectors are rather stiff due to the signal integrity they were designed for.  Make sure to carefully disconnect the SOM.  Then after aligning it, press it back in following the perimeter of the board pressing every 1 inch or so.  Visually look along the edge of the connector and ensure that the top and bottom are mating properly.

Of course follow all ESD safety when doing this as you will be touching the bare board during this process.

--Dan

HI,

It seems odd that it is stopping at that location.  The first thing that comes to my mind is to reseat the SOM on the carrier.  The connectors are rather stiff due to the signal integrity they were designed for.  Make sure to carefully disconnect the SOM.  Then after aligning it, press it back in following the perimeter of the board pressing every 1 inch or so.  Visually look along the edge of the connector and ensure that the top and bottom are mating properly.

Of course follow all ESD safety when doing this as you will be touching the bare board during this process.

--Dan

Thanks @Daniel Rozwood 

It is indeed odd, I must say. There is however one unresolved question about this on the Xilinx furum.  XLNX_FORUM: https://forums.xilinx.com/t5/Embedded-Linux/Petalinux-2017-1-Uboot-stuck-at-quot-I2C-quot-with-ZCU102/td-p/796958

I did remount the SOM onto the carrier board, but things are the same. It is worth mentioning i'm doing a build for an SD card an the on-board emmc images boots fine. We need to however add some extras at a later stage so mastering the boot process is very important for us.

Deville

Deville,

Thanks for trying the re-seating.  It seems silly, but often we see that correct a lot of funny issues.  Again, mostly due to the mechanical forces - most people do not squeeze hard enough.

Which SDCARD are you using?

--Dan

It is a Samsung 32GB EVO Plus card ( SDHC ), We never had a problem, as far as we could recognize, with this card. The Zynq US+ should be able to handle SDXC cards.

Edit: It has been working on the ZCU102 board from Xilinx.

Deville

Have you tried with the included SDCARD?

--Dan

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

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

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

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..

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.