Deadlock of Microzed

Have you tried reprogramming the QSPI with the image stored in Tutorial "Open Source Linux In System QSPI Programming Tutorial?"

You could also try the solutions from Tutorial 04.

Bryan

Hi Bryan

Thanks for the input. I tried to reprogram the QSPI with the suggested Tutorial "Open Source Linux In System QSPI Programming Tutorial" now. Unfortunately there is still no terminal output (not a single character).

I also followed the Tutorial 04. I can successfully program the QSPI (it states "Flash Operation Successful" in the Program Flash Console) but I can still not receive any signal via the terminal.

The terminal setup is working. I can double-check it (with same USB-cables, terminal settings, etc) a Zedboard and there I receive all the messages on the serial terminal.

Can you provide a boot-file (BOOT.mcs) with a hello world program for a Microzed 7020 which I could program to the QSPI Flash?

Nicolas

Hello Nicolas,

If I understand correctly you have not been able to see any output from the MicroZed USB-UART interface. Before trying to tackle the QSPI issue please verify that you can make the USB-UART connection, as that is completely separate from the QSPI. The MicroZed USB-UART device is different than the one on the ZedBoard and requires a different driver on your host PC. Please make sure that you have installed the SiLabs CP210x USB-to-UART driver as described in tutorials mentioned above. Also make sure that you determine which 'Comm Port' to use for your TeraTerm or Putty terminal program.

Once the USB-UART driver is set up then I would either download a known good microSD Card image for your MicroZed 7020 and program onto a microSD Card or perform one of the tutorials (such as tutorial 02 for the MicroZed) that loads the application program via JTAG. Either of these should produce an output to your serial terminal program.

Once you have established communications with the MicroZed USB-UART then we can start to test the QSPI issue.

-Gary

Hi Gary

The driver installation is correct and the comm port selection also (its named "COM13: Silicon Labs CP210x USB to UART Bridge" in TeraTerm). I was able to download the Mem_Test with Vivado 2015.2 and get the messages on the serial terminal. (Soruce files: https://zedboard.org/content/vivado-20152-version-microzed-7020) I was also able to debug this program successfully on the Zynq.

Is it possible that the MicroZed Board Definition files for Vivado2014.2 Zedboard 7Z020 are somehow corrupted? I had to install them following the installation guide for "MicroZed Board Definition Install for Vivado 2014.2, 2014.3, and 2014.4": http://zedboard.org/content/board-definition-files-0. My system requirements are all correct (64-bit Win-7, Xilinx Vivado 2014.2). I installed it as described in Option 1: Install into the Vivado installation.
After that I always set this board definition files as my project device and in the Vivado block design I set the processing_system7_0 to its Microzed Preset. Is that a possible source of failure?

Regards
Nicolas

Hi Gary

I compared a design run for a Microzed (MZ) 7010 and 7020 today where I did exactly the same for one board and then for the other. With the result that on MZ 7010 I successfully download and even debug the helloworld program. On MZ 7020 I can successfully download the program without any results on serial terminal. When I try to debug on MZ 7020 it doesn't start at the beginning of main (as it does on MZ 7010 or Zedboard).

I proceeded as follows for MZ 7010 and MZ 7020:
1) create new project with vivado2014.2 with MZ_70x0 as project device
2) in block design: processing_system7_0 settings: preset Microzed
3) Block Automation, create HDL wrapper, create bitstream
4) export hardware (with bitstream), launch SDK
5) create Hello World app project (with bsp and default Hello World template)
6) power MZ, start TeraTerm (with correct settings)
7a) download Hello World (reset entire system and prog. FPGA)
7b) debug Hello World (dito)

Comparing the results I must conclude that either the MicroZed Board Definition files for MZ 7020 or my MZ 7020 is corrupted. Or do you have another conlusion? Can you send me an RMA for my MZ 7020 or support me in another way?

Regards
Nicolas

Hello Nicolas,

Your results do not seem be consistent. It may be that you have a corrupt board definition file. I would suggest that you upgrade to a more recent version of the Xilinx tools, Vivado 2015.x, as the version you are using is a little dated, and download a fresh version of the current board definition files.

You could also take a look at the MicroZed 7020 solutions for the Tutorials 01-04 for Vivado 2015.1 or 2015.2 available here:

http://microzed.org/support/design/1519/10

or try the pre-built platform in the PetaLinux BSP for 2015.2, or one of the earlier versions.

And, just to make sure it is not the issue, be aware that the SiLabs USB-UART device on each MicroZed has a unique ID and will enumerate with a different Comm port for a given host PC. So the TeraTerm Comm port for your MicroZed 7010 will be different than the one for your MicroZed 7020 on the same host PC.

-Gary

Hello Gary

I upgraded to Vivado2015.2 and followed the tutorial 01-02 of the MicroZed 7020 for Vivado 2015.1 or 2015.2.
I can program the FPGA successfully but when I try to download the HelloZed project an error window appears with the message details:
An internal error occurred during: "Launching HelloZed Debug".
No Target with ID 64 in the System

The two MicroZed have UART ID 13 and 14. Of course I can only choose the one that is pluged in on host PC when I configure my terminal.

I also tried to boot from the pre-built platform on sd card with the files from "microzed_7010_7020_petalinux_SD_images" without success (means no serial output).

Does this give a more consistant picture of the failure behaviour?
All I can say is that I had no issue with the ZynqHW and ZynqSW tutorials as well as the CTT tutorial on Zedboard. Since I work with the MZ 7020 I wasn't able to set up an own hardware with a running helloworld program on it. In contrast I was able to set up an own hardware and run the helloworld successfully with the MZ 7010. This leads me to the assumption that my MZ 7020 is corrupt. Or do you disagree?

If you agree please send me an RMA for my MZ 7020. The fault finding is quite cost intensive on our side.

Kind regards
Nicolas

Hello Nicolas,

Please send me a private email with the information on where and when you purchased the board, sales order etc., along with your 'use case' (is the board used in the lab or as a part of another product).

-Gary

Hi Gary

How do I know your private email address?

Nicolas

If you click on the name or 'picture' to the left of a post a user has made it will show you the 'userID'. In my case it is 'Troutchaser'.

You can use the 'messages' link at the top right of the forum thread to send a message, in this case to Troutchaser.

-Gary