Hello world does not work on REVF07 board, does on REVF06

Hardware used:

•  

  Windows 10 PC 1 with Vivado 2016.4

•  

  Windows 10 PC 2 with Vivado 2016.3

•  

  PC 1 tried with Digilent HS2 Rev. 2 JTAG adapter

•  

  PC 2 tried with same HS2 and Digilent XUP USB-JTAG Programming Cable

•  

  MicroZed Rev F.06 (working)

•  

  MicroZed Rev F.07 (not working)

Steps to reproduce:

1.  

   Take a REVF07 board and set jumpers to JTAG mode (1-2, 1-2, 1-2)

2.  

   Install Vivado 2016.4 and the MicroZed board support files

3.  

   Create a new Vivado Example project

4.  

   Choose ‘Base Zynq’

5.  

   You’ll have to choose a ZC702 board as the MicroZed board package doesn’t show up with the example projects.. [1]

6.  

   Open Project settings and change the board to ‘MicroZed 7010 Board’

7.  

   Open Block design and delete the leds_4bits’ port as these are not present

8.  

   My project ask to upgrade ip-status. I did, choosing ‘Out of content per IP’->Generate

9.  

   Press ‘Generate Bitstream’ and wait until it’s finished

10.  

    File->Export->Export Hardware, choose defaults and include bitstream

11.  

    File->Launch SDK

12.  

    In the SDK: File->New->Application Project

13.  

    Name it, Choose: standalone, create new BSP

14.  

    Next, choose Hello World, OK

15.  

    Create a breakpoint at the printf(“Hello world\n\r”) in helloworld.c

16.  

    Create a Debug configuration with choose the system debugger.

17.  

    Configure the debug to ‘Reset entire system’, ‘Program FPGA’, ‘Run ps7_init’, ‘Run ps7_post_config’

18.  

    Press Debug

19.  

    I do not see ‘hello world’ and get any of the above error modes

20.  

    Switch out the board for a REVF06, USB-UART and JTAG. Again set jumper to JTAG mode

21.  

    Reconnect SDK Terminal

22.  

    Press Debug and it works

Note 1: Choosing an Empty RTL project and choosing the MicroZed Z7010 board works as well but you have to design the Zynq PS block design yourself as block automation does not build a PS system (with reset block etc). Build this by hand and the problem remains the same though.

Hi Knifer,

So if I am understanding correctly, your RevF06 board is functioning while the Rev F07 board is not. This is true in both cases, when you use an example project and even when you build your own project from scratch(described in note 1) correct? 

To get a base that I can follow along with could you please do Tutorial 01 and Tutorial 02 for your MicroZed(please use Vivado 2016.4).See link: http://zedboard.org/support/design/1519/10

At most the tutorials will take you 30 minutes. In Tutorial 02 you run the Hello World application. Could you please confirm that your RevF06 board is functioning and your Rev07 board is not after completing Tutorial 02.

Thanks,

Josh

Hi JFoster,

I'm sorry for the delay but due to a driver problem with a prolific adapter I had to reinstall windows 10... So I've just completed the tutorials with a newly installed windows 10, vivado, board support files.

Yes, you understand correctly. The RevF06 is working (in my project) and the RevF07 is not, however:

I've taken your suggestion and did both turorials. Almost the same steps as I took in my procedure (which does not show up here in the topic) with the difference of choosing the Z7010 board right away at the beginning while creating the project. 

Now both boards work! I can see "Hello world" and I can debug (breakpoint) the code on both the RevF06 and RevF07 boards.

I'm still investigating the difference but what I can see already is that my previous project has the Micrel mt41j128m16ha-15e memory selected while the new (Z7010) project has the MT41K256M16 RE-125 memory selected. There might be more differences. But it appears that selecting ZC702 and switching out the board (in order to use the example projects!) does not apply the board presets, right?

I've checked those presets and can see a big list of settings (including DDR settings/type) in the z7010 preset.xml while the zc702 preset.xml does a lot less and no memory settings. I will try to copy over the memory settings from the new project and see if it works (the RAS/CAS delays are identical). But this will not ensure me that any other critical settings have not been missed.

Is there anyway to apply these presets again to my current project? Or do I have to start over and choose a Z7010 board right away?

Thank you so far,

Tijs

I forgot to clarify: My old project still has the same behavior: F06 works, F07 doesn't. 

Confirmed. Setting the part to MT41K256M16 RE-125, settings Internal Vref to false, copying DQSx to Clock delays makes both boards work in my previous project too (so far). Not sure which of these three is the cause. Setting the part did not change any of the timings parameters in 'Memory Part Configuration' as these timings are identical for both parts. Is it the Vref?

So I expect that this is the cause: selecting another board and switching back to the Z7010 via project options does not apply board settings (I don't know if this is expected behaviour, but I also didn't get the option). If one wants to do this the board presets should be applied another way. How would I do this? The preset files contain a lot more information then the above settings. Especially DDR trace lengths timings which I could not cannot apply in PS settings manually.

Ill note again that selecting an Example project instead of RTL Project does not allow selecting any other board than ZC702, so I would expect more beginners to run into this problem when they start out using an example.

Hi Knifter,

I am glad to hear it was a board preset issue and not a hardware issue. I don't believe Vref should make a difference. For you Xilinx tools related questions I am going to suggest you ask them over at the xilinx forum as they are best suited in providing you a solution.

https://forums.xilinx.com/

Regards,

Josh

Hello Josh,

Yes, I am too. Although it took me weeks to figure this out. It might be worth mentioning in the tutorial or somewhere else a beginner might run into (that you need to make sure the presets are applied, before bothering what they actually all mean).

For archival purposes, might someone else run in the same problem:

I've made a .tcl file to set all the properties as they're being set in the preset.xml file. Running this file fixes the problem. As a starting point I took the MicroZed_PS_properties_v03.tcl file from http://microzed.org/support/documentation/1519. Although a few settings are missin from this file (as compared to preset.xml), running this file will probably fix the problem as well.

I just want to note that I think it is a but short-cornered to give the problem of applying presets later on to the Xilinx forum as you have provided these files previously: MicroZed_PS_properties_v03.tcl file for vivado 2013.4 I know now that running that file would have solved my problem as well. But you do not provide these files for any later version of Vivado. Maybe it is a good idea to do so.. such that board presets can be applied later.

Thank you again for your help,

Tijs