Actions
Forum Thread Details
  • State Verified Answer
  • Replies 14 replies
  • Subscribers 329 subscribers
  • Views 2169 views
  • Users 0 members are here
Related

U-boot picoZed 7030 doesn't recognize neither eth nor sd.

oscargomezf

Hi everyone,

 

I'm new working on Zynq platform. I'm trying to boot u-boot from SD card.

I've created my BOOT.bin file, using bootgen and u-boot init perfectly, but it doesn't recognize neither eth nor Sd Card, so I'm stucked. This is the u-boot init:

 

U-Boot 2016.07-03720-g95e11f6 (Oct 04 2016 - 09:07:12 +0200)

Model: Zynq PicoZed Board
Board: Xilinx Zynq
DRAM:  ECC disabled 1 GiB
MMC:   
Using default environment
 
In:    serial@e0001000
Out:   serial@e0001000
Err:   serial@e0001000
Model: Zynq PicoZed Board
Board: Xilinx Zynq
Net:   No ethernet found.
MMC Device 0 not found
** Bad device mmc 0 **
Hit any key to stop autoboot:  0 
No MMC device available
Zynq>

 

Could anyone help me?

 

I'm using u-boot from:

https://github.com/Xilinx/u-boot-xlnx.git

 

And then I compile it with: make zynq_picozed_defconfig && make

 

The HW is the picoZed Board with the Zynq 7030 and the PicoZed FMC Carrier V2

 

Best regards.

  • 0

    What revision PicoZed module do you have?

    Which SD Card are you using?

    Have you already tried using the pre-built images that Avnet provides for U-boot and PetaLinux?

     

    Bryan

  • 0

    Hi Oscar,

      I think the problem here is some out of date configuration files in the latest u-boot hierarchy.  I am able to replicate your error.

      To get you moving, I think for the moment you can build u-boot from the Petalinux BSP for the PicoZed 2016.2.  That one will work while we figure out exactly what the differences are.   Unfortunately, it's not as straightforward as substituting some files, as the methods used to build u-boot vary slightly between the build environments.

    Ron

  • 0 in reply to bhfletcher

    Hi Bryan,

     

    1º.- I'm using the picoZed Z7030: BD-Z7PZP-7Z030-G REVC04

    2º.- The SD is a micro SD SanDisk Ultra 16GB Class10.

    3º.- According to the pre-build images for U-boot... Where can I download them? I only have a micro SD with WIND RIVER PULSAR LINUX but I tried to boot (With the SW1 in uSD boot mode) and It doesn't work.

    The SD card snf the FAT parition have to be ok, because I boot perfectly u-boot cross compiled from git:

    https://github.com/Xilinx/u-boot-xlnx.git

     

    Best regards.

  • 0 in reply to Former Member

    Ok Ron,

     

    Then you know the problem. I don't have any experience with Petalinux, but I'm going to try to compile everything whereas you try to fix the bug.

    Do you have an estimation of how much you will take to solve the bug?

    For a first stage, I can get u-boot from petalinux BSP, but I'm going to need to have access to u-boot because I have to change a few things to my project.

    Best regards.

     

    P.S.: Please, keep me informed about the progress.

  • 0 in reply to oscargomezf

    Hold on Oscar,

      I'm able to replicate the u-boot issue using the 2016.07 version from mainline, which is the same used in Petalinux 2016.2.  However, the Wind River Pulsar Linux image on the uSD card should work right out of the box - there are no known issues booting that on PicoZed.

    If there is somehow an issue with the image on the uSD card, you can look at this document to download a fresh copy and replace it on the uSD you have.  

    http://microzed.org/sites/default/files/documentations/Pulsar-SoM-Image-Creation_Customer.pdf

    Most of the boards ship with an 8GB uSD, but I know a few shipped with teh 16 GB SanDisk card you mentioned.  Although that should not cause any issue at all, just the fact that it's different than the norm and you are having a problem makes me a little suspicious.

    Ron

  • 0 in reply to oscargomezf

    Hold on Oscar,

      I'm able to replicate the u-boot issue using the 2016.07 version from mainline, which is the same used in Petalinux 2016.2.  However, the Wind River Pulsar Linux image on the uSD card should work right out of the box - there are no known issues booting that on PicoZed.

    If there is somehow an issue with the image on the uSD card, you can look at this document to download a fresh copy and replace it on the uSD you have.  

    http://microzed.org/sites/default/files/documentations/Pulsar-SoM-Image-Creation_Customer.pdf

    Most of the boards ship with an 8GB uSD, but I know a few shipped with teh 16 GB SanDisk card you mentioned.  Although that should not cause any issue at all, just the fact that it's different than the norm and you are having a problem makes me a little suspicious.

    Ron

  • 0 in reply to Former Member

    Hi Ron,

     

    The SD CARD tagged with WInd Driver Pulsar Linux, is a SAMSUNG 16GB EVO  HC-I, (But I'm using another uSD card to do my test, a micro SD SanDisk Ultra 16GB Class10.) and I can confirm you that It doesn't work, but it doesn't matter.

    Finally I've achived to compile petalinux and I can log on the Zynq. I would like to know: Do you have an estimation of how much you will take to solve the bug?

    Best regards.

  • 0 in reply to oscargomezf

    Oscar,

    No, I do not have an estimation of the time it will take to resolve this.  It depends on whether is is our problem, an incompatiblity with the latest open-source code and Zynq, or if there are issues in Xilinx-specific modifications.  As you can appreciate, the first step to solving this is to isolate the issue,  which can often be difficult when working across the boundaries of different organizations.   Most open-source development done by commercial vendors is also done mostly in spare-time, so it can be difficult getting dedicated resources assigned.

    That's the reason our first goal is to create a work-around to get a customer moving forward, while the contributors can work in the background to address the root cause.  The reality is that often times in short release cycles a problem is not corrected until the next release comes out several months later.

    I'm not saying this is optimal, I'm just saying that's the way things are when working with open-source solutions.

    Having said that, we recognize that there is an issue with the 2016.2 u-boot in certain circumstances, and we are working to address it.

    Ron

  • 0 in reply to Former Member

    Hi hockeyman,

    I was trying to find out why it doesn't work my Sd Card. And it was my fault.

    As you can see in the OVERCBOOT partition:

    /media/OVERCBOOT$ ls -la
    total 63864
    drwx------  5 root       root    16384 ene  1  1970 .
    drwxr-xr-x+ 5 root       root    4096 oct 10 09:03 ..
    -rw-r--r--  1 root       root    2462528 nov 23  2015 BOOT-PZ7010.BIN
    -rw-r--r--  1 root       root    3889436 nov 25  2015 BOOT-PZ7015.BIN
    -rw-r--r--  1 root       root    4424284 nov 25  2015 BOOT-PZ7020.BIN
    -rw-r--r--  1 root       root    6358684 nov 24  2015 BOOT-PZ7030.BIN
    -rw-r--r--  1 root       root    8048 dic 10  2015 dtb
    drwx------  2 root       root    4096 feb  4  2016 .fseventsd
    -rw-r--r--  1 root       root    13299887 dic 10  2015 initrd
    -rw-r--r--  1 root       root    13299887 dic 10  2015 initrd-3.14.39ltsi-pulsar-standard.gz
    drwx------  4 root       root    4096 feb  4  2016 .Spotlight-V100
    drwx------  2 root       root    4096 feb  4  2016 .Trashes
    -rw-r--r--  1 root       root    4096 feb  4  2016 ._.Trashes
    -rw-r--r--  1 root       root    5076248 dic 10  2015 uImage
    -rw-r--r--  1 root       root    5076248 dic 10  2015 uImage-3.14.39ltsi-pulsar-standard 
    -rw-r--r--  1 root       root    5076248 dic 10 2015 uImage_bakup
     
    I forgot to copy the BOOT-PZ7030.BIN to BOOT.BIN to boot properly. So the Sd Card is fine and after copying the BOOT-PZ7030.BIN to BOOT.BIN the Sd Card boots perfectly.
     
    Best regards.
  • 0

    Hi,

     

    I was trying to find out where the picoZed began to stop worlking:

    master -> fail
    e1c155592b935519c49bc1fb877487e81a145830 refs/tags/xilinx-v2016.2 -> fail
    76b24a37e2a464e6da2f374d199ca2171d634ed1 refs/tags/xilinx-v2016.1 -> fail
    fc7779a363fb927440107a4d6f12f206d1abff36 refs/tags/xilinx-v2015.4 -> detect the NET
     
    So it seems to be the jump from xilinx-v2015.4 to xilinx-v2016.1 was the problem.
     
    I would like to use the tag xilinx-v2015.4 but it doesn't work fine the access to the SD Card, so I'll have to wait.
     
    I hope this will be helpful.
     
     
    Best regards.