Kvass

Yea, the old method is deprecated and doesn't work past Vivado 2019. On the bright side, the newer way explained here https://www.instructables.com/Flashing-a-MicroBlaze-Program works well, and gets both your embedded SW and your FPGA programmed. -K

The CMOD is programmable just with a USB-MicroUSB cable. I believe the Basys 3 is the same, only needs a microusb cable to be programmed by your PC.

As far as I know, as long as you made the JTAG interface on your custom board to match the HS2 pinout, the Adept 2 should recognize the HS2 chip as the "hardware server" and you should be able to see your FPGA and configure it. I use the HS2 programmer to program boards with FPGA parts not from Digilent all the time.

Oh man, I've ran into this issue many times over, and with multiple versions of vivado. One thing I found at some point is that if you have a microblaze program in your design, it likes to be the release version, not the debug one. Which version of Vivado/Vitis are you using? https://forum.digilent.com/topic/23536-storing-program-in-flash-on-cmod-a7-in-2022/ https://forum.digilent.com/topic/26483-microblaze-program-not-starting-on-powerup-cmod-a7/ https://forum.digilent.com/topic/25802-cmod-a7-35t-spi-memory-programming

hmmm, I've double checked the QSPI IPcore and my device settings, everything is set to Quad mode. I am also using Micron memory on my CMOD a7 35T, so our setups are quite similar. I'll try to made the barebones Hello World project and expand from there, I'll post an update if I get it working and find the issue that was causing it not to launch. Thanks, Kvass

Ugh, I feel as thought I'm at my wits end here. I have a project on my CMOD A7 35T, and I can't get it to boot the Microblaze on startup. Whenever I program the device through VITIS using the debugger, my program starts and everything is well. I added my .ELF file to my Microblaze using the "associate elf file" function, and am storing my bin file via the "Configuration Memory Device" through the hardware manager. When I powercycle my board, I can see that the bitstream loaded and the clock is running based on my observations on the ILA. However my C program stored on the Microblaze isn't starting up for some reason. I've tried both release and debug versions of my C code, and I verified that I followed all steps when configuring my QSPI core and other related settings based on this post from before : What are possible reasons why the Microblaze isn't launching on startup, but works every time when programming the board through Vitis or the hardware manager? Vivado version is 2021.2 Thanks, ~Kvass

I ran into this issue recently, and that tutorial is now outdated as of vivado 2020. The newer tutorial is here I believe. https://www.instructables.com/Flashing-a-MicroBlaze-Program/

So "time.h" doesn't work on zynq and microblaze processors as far as I know. There is a xilinx specific library called "xtime_l.h" that implements time measurement functions.

I think all of their boards are on the Digilent Github: https://github.com/Digilent/vivado-boards

It should be as easy as setting the Rx and Tx pins of the UARTlite IP core to output pins and assign them to the Pmod pins in your constraints file.

Have you configured your SD card settings correctly on the ZYNQ? I had the same issue for the longest time on a Genesys ZU 7EV until I read that the SD card had to be 3.0 and neither eMMC nor 2.0. https://digilent.com/reference/programmable-logic/genesys-zu/reference-manual#microsd_boot_mode

Hi Sarvan, Ok, that clears it up a bit. Check out https://digilent.com/reference/programmable-logic/genesys-zu/reference-manual for the reference manual of the board. Try setting the Programming mode to USB on JP3 when using the USB port to upload your program. The JTAG mode should be used when you have a HS# connector used to connect to the JTAG header. I had an HS1 module that came with my board, so maybe you also have one in the box somewhere? Good luck, -K

Hi Sarvan, So does it not connect to the board when attempting to launch the hardware server? When you say you connect to the board via microusb, are you connecting to the microusb port, or to the JTAG pins using the JTAG-HS# connector? Also, do you have anything connected to the FMC connector on the board? -K

Take a look at the errors it gives you at the bottom tab of the interface. This should have the reasons why the bitstream generation failed. It looks like you didn't assign non-default pins in your project. Even if the "default" setting is the one you want, you need to manually assign the pin I/O Standard in the xdc file, or in the pin planner. ~Kvass

Hi JColvin, I did end up using the Instructables guide to flash the memory. This seems to be a much easier way than creating the bootloader and using the SREC. No issues with the Macronix memory either. Thank you very much! One thing about the guide that wasn't clear and may be worth noting is that in the guide, the .ELF file is built as a debug configuration. In practice, the MicroBlaze did not immediately run the .elf file if it was built as a debug .elf. Once I built it as a release, it worked right away. Thanks again, -Kvass