Actions
Forum Thread Details
  • State Not Answered
  • Replies 6 replies
  • Subscribers 348 subscribers
  • Views 1257 views
  • Users 0 members are here
Related

picozed 7030 does not boot

droman

We are trying to generate a bootable image using yocto but we had some problems. After generating the system configured for the picozed-zynq7 machine ( provided by meta-xilinx-bsp) it doesn't boot. The next error is shown in the console:

 

U-Boot SPL 2020.07 (Jul 06 2020 - 19:22:53 +0000)

Trying to boot from MMC1

MMC: no card present

spl: mmc init failed with error: -123

SPL: failed to boot from all boot devices

### ERROR ### Please RESET the board ###

 

I doesn't shows an u-boot shell neither. Which steps could we take to debug this and fix it?

 

Thank you very much

Parents
  • 0

    Hi there,

     

    Is there a reason you are using meta-xilinx instead of meta-avnet?

    Can you validate that your SDCARD has been written properly?  It seems there has been some challenges recently with sdcards not being setup properly.

     

    --Dan

  • 0 in reply to drozwood90

    Thank you for your response.

     

    The only reason to use meta-xilinx is that it supported the different boards we used in the past. I took a look to meta-avnet and seems it has support for the fmc2 carrier board but we use a custom carrier, I don't know if it will at least boot if the carrier is not the same? Just in case I will try with meta-avnet.

     

    If I copy the binary boot.bin provided by the picozed bsp file it boots properly, so It seems it writes correctly, the problem only appears with the boot.bin generated by yocto. I have been trying different u-boot versions and seems that before version 2020.07 it doesn't print anything to the serial port. With the 2020.07 version of u-boot it prints the MMC error. I also tried to apply a device-tree patch that enables sdhci0 but it didn't worked.

     

    Regards

  • 0 in reply to droman

    Hi there,

     

    I'll run this by one of our PetaLinux experts.  Maybe they can see something in your response that might help them help you.

     

    --Dan

  • 0 in reply to drozwood90

    Some more info, after applying the attached patch to u-boot_2019.07 it shows the next message

     

    U-Boot SPL 2019.07 (Jan 15 2021 - 15:08:00 +0000)

    mmc boot Trying to boot from MMC1

    sdhci_set_clock: Internal clock never stabilised.

     

    Playing around with the dts I found that removing the "u-boot,dm-pre-reloc;" line from the sdhci node it shows a different message (all of the referenced files where in the sdcard, I've also tried to switch the sdhci1 and sdhci0 and it was the same)

     

    U-Boot SPL 2019.07 (Jan 15 2021 - 15:12:43 +0000)

    mmc boot Trying to boot from MMC1

    spl_load_image_fat_os: error reading image system.dtb, err - -2

    spl_load_image_fat: error reading image u-boot.img, err - -2

    SPL: failed to boot from all boot devices

    ### ERROR ### Please RESET the board ###

    Attachments:
    picozed.patch.txt.zip
Reply
  • 0 in reply to drozwood90

    Some more info, after applying the attached patch to u-boot_2019.07 it shows the next message

     

    U-Boot SPL 2019.07 (Jan 15 2021 - 15:08:00 +0000)

    mmc boot Trying to boot from MMC1

    sdhci_set_clock: Internal clock never stabilised.

     

    Playing around with the dts I found that removing the "u-boot,dm-pre-reloc;" line from the sdhci node it shows a different message (all of the referenced files where in the sdcard, I've also tried to switch the sdhci1 and sdhci0 and it was the same)

     

    U-Boot SPL 2019.07 (Jan 15 2021 - 15:12:43 +0000)

    mmc boot Trying to boot from MMC1

    spl_load_image_fat_os: error reading image system.dtb, err - -2

    spl_load_image_fat: error reading image u-boot.img, err - -2

    SPL: failed to boot from all boot devices

    ### ERROR ### Please RESET the board ###

    Attachments:
    picozed.patch.txt.zip
Children
  • 0 in reply to droman

    Avnet does not contribute to meta-xilinx and we use PetaLinux instead of native yocto for Linux development for PicoZed and our other SOMs and SBCs, so I don't know why the picozed-zynq7.conf machine definition is failing to boot now.  I do know that starting with the u-boot built with the PetaLinux 2020.1 tools, a u-boot.scr file is required to help u-boot boot the system.  This file is required to be same location as the boot.bin file (that has the u-boot binary embedded inside).  Is this perhaps what you are missing?  I have seen similar sorts of strange boot errors when I forget to include this boot.scr file in the boot partition.

     

    For a known-good Linux OS for the PicoZed you may want to start with one of the Avnet provided PetaLinux BSPs:

    http://avnet.me/zedsupport

     

    --Tom

  • 0 in reply to narrucmot

    I also copied the boot.scr file, but seems that, because boot.bin doesn't even work, it doesn't execute the boot.scr script file. Our current workaround is to use the boot.bin provided by the BSP (not the one from yocto) and then use the boot.scr file provided by yocto.

     

    Thank you.