Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 322 subscribers
  • Views 2877 views
  • Users 0 members are here
Related

New zed board is not booting from SD card despite jumper configuration.

fluxinduction

I've been following this guide for initial setup of the zedboard: 

GS-AES-Z7EV-7Z020-G-V7-1.pdf (avnet.com)

I cannot get past step 8 of section 5.  The zedboard never successfully boots.  I do have another SD card, and that doesn't boot either.  

I've also been referencing the hardware guide:

 ZedBoard_HW_Users_Guide (digilent.com)

What is causing this?  This board is brand new, just unwrapped.  

Parents
  • 0

    Double-check your device tree entries for sdhci1.  I don't recall the exact entries, no-1v8 (or something like that) and disable-wp are required.  It seems there is something else.  Anyways, a very quick google search will turn up the right entries to add.

    Secondly.make sure you are connected to the appropriate micro-USB port for the console.  I don't recall on the ZEDBoard, but if the serial port has two devices (ttyUSB0 and ttyUSB1), try the second device.  Also, make sure your terminal emulation is set for 115200N8.

    Try selecting a different mode, such as eMMC (sdhci0) for your boot device and see what happens.

    Lastly, make sure you have power.  Check the power LEDs on the board.

  • 0 in reply to dyessgg

    The unit shows up in device manager and the uart usb light, ld 11 illuminates.  The device driver shows that its the latest.  The connection settings are as you say.  

    I can boot from the on board flash just fine by switching jumper settings.  I cannot get the sd flash to boot no matter what.   I just tried a linux image made for the zedboard and did not work.  

Reply Children
  • 0 in reply to fluxinduction

    OK, so we're making progress. This tells me the board is most likely not damaged and you have the correct terminal connections and settings.

    Does the board even come up to U-Boot? 

    If no, did you partition the uSD card correctly with a FAT32 partition 1 and then copied BOOT.BIN (generated by petalinux-package) and the image file (don't recall the file name for Zynq-7000 devices) into that partition?

    You're doing this on a Windoze host?  Make sure you're trying to copy an image made for the uSD card, not the eMMC or SPI flash.  If it is truly an image, make sure it is used to write to the raw uSD cart.  Balena Etcher is good to use on crippled Windoze hosts as it will write the raw image to the flash and verify it is written properly.

    Make sure the uSD card is not damaged.  The writer program should verify the image is written properly.

    Check the uSD socjket to make sure nothing is jammed in the connector and none of the pins are damaged.

    Try another uSD card, even if your other card reads back correctly.

    Did you double-check your device tree entries sor sdhci1 as I suggested earlier?

  • 0 in reply to fluxinduction

    If it did not work with a canned Linux image on the SD card I would suspect the console port.  There are three micro-usb connectors on the Zedboard. Only one can work as the console port, J14.  115200 baud, 8 bit data, no parity, 1 stop bit (8N1).  I use Putty as the terminal program.

    To test things out, you could connect to the JTAG debug port on J17 and run the hardware manager.  You should be able to see the part and plot it's temperature. You could also use Vitis to create a simple bare-metal Hello program, but Vitis is an adventure of its own.

  • 0 in reply to padudle

    I see that you can boot from QSPI.  I assume that means you see text from the console.  That does point to the SD card.

    The text you see should first come from the First Stage BootLoader, then U-Boot, then after a delay it will try to start the kernel.  If you are not even getting the FSBL  text then it is unable to read any kind of boot image on the SD card.

    You can check the card itself by putting it in an SD card reader and plugging into your desktop computer.  If you are running Linux on the desktop, you should see two partitions mount, normally a fat32 partition called BOOT and an ext4 partition called rootfs.

    Occasionally, I do almost everything on my Zedboard while running Linux on it.  I think your problem is low-level but I can share my Petalinux and filesystem notes from here, github.com/.../petazed.git