nexys video olead problem

[sosso]

hi everyone, 

        Here is a screenshot of a microblaze based system using nexys video, controlling the OLed, when I validate and generate output products, I get this message : 

 [IP_Flow 19-4965] IP PmodOLED_axi_gpio_0_0 was packaged with board value 'digilentinc.com:arty:part0:1.1'. Current project's board value is 'digilentinc.com:nexys_video:part0:1.1'. Please update the project settings to match the packaged IP

        If I ingnore this , the systhesis works well, but during the implementation a bunch of errors and warnings appear? could anyone help me?

[jpeyron]

Hi @sosso,

Here is a project that matches the ips in your block design done in Vivado 2017.4 for the Nexys Video. I have gone as far a step 3.1 in the How To Store Your SDK Project in SPI Flash tutorial since i do not have a Nexys Video where i am at.

cheers,

Jon

[jpeyron]

Hi @sosso,

I completed the project this afternoon. Here is the complete project in vivado 2017.4.

thank you,

Jon

 

[jpeyron]

Hi @sosso,

I was not able to finish the sdk portion of the project. You will need to continue from section 3.1 of the How To Store Your SDK Project in SPI Flash tutorial since i did not have a Nexys Video where i was at.

thank you,

Jon

[sosso]

Hi jpeyron, 

        I tried to use the sdk, the functions used in vivado sdk of 2016.4 are different from 2017.4 ?

[JColvin]

Hi @sosso,

You can click the grayed out check mark box on the left hand side of the post that you feel was the "Best answer"; this will help show the thread has been answered. Otherwise, there isn't another formal way of showing this (aside from editing your original question title to include the word "solved").

Thanks,
JColvin

[sosso]

hi jpeyron,  

       I removed vivado 2017.4 and replaced it with 2016.4, it works perfectly , no errors, no latency during synthesis nor in implementation, much faster than 2017.4, I think I dindn't install very well the 2017.4, and it was so slow,  so thank you so much for you precious help , do I have to put this subject as solved?

[sosso]

hi jpeyron, 

        4 GB of ram, now i tried the small tuto you adviced me , without oled without qspi implemented, It's been an hour since I runned the synthesis, 

It didn't finish yet 

[jpeyron]

Hi @sosso,

It can take some time for synthesis especially if you are using an I3. How much ram do you have?

thank you,

Jon

[sosso]

hi jpeyron, 

          Is it normal that the synthesis take too much time, sometimes more than an hour, I have an i3 intel processor, ?

 

[jpeyron]

Hi @sosso,

You will need to change the ip repository to the path of vivado library on your PC if you are wanting to open the block design in vivado. I attached a block design below. Once in sdk start on 3.1 of the tutorial. 

cheers,

Jon

 

[sosso]

Hi jpeyron, 

         thanks a lot, I'm downloading it now, is there any difference I have to be aware of ?

[sosso]

Hi jpeyron, 

         i'm using vivado 2017.4, I'm following the exact same steps but it does not generate the same block design as shown on the tuto

[jpeyron]

Hi @sosso,

Looking at your block design you should remove the sys_rst  connected to the mig and run connection automation.  you should look at the block designs in the getting started tutorial i linked above as a reference. 

thank you,

Jon

 

 

 

[sosso]

hi jpeyron, 

     here is the block design : 

 

I tried both, when implementation to parameter some feature concerning the bitsream, the frequency of 33 mhz .. , and I tried also not doing anything but it doesn't work?

 

                                                                                        thank you 

 

[jpeyron]

Hi @sosso,

This type of error is with you xdc. Could you attach a screen shout of block design and your xdc file?

thank you,

Jon

[sosso]

hi jpeyron

thank you so much that helped   a lot, the implementation works , but now I get problems in the bitsream, i get errors while generating bitstream ?

here is one of the messages:

  [DRC NSTD-1] Unspecified I/O Standard: 1 out of 66 logical ports use I/O standard(IOSTANDARD) value "Default", instead cause I/O contentiojn or incompatibilty with the board power or connectivity affecting performance .....

[jpeyron]

Hi @sosso,

It looks like your mig is connected wrong. For using the QSPI i usually follow this old tutorial with a few changes for the vivado portion. On step 3.3 i do not select the interrupt controller. On step 4.4 i also add a 3rd output clk at 50 MHz.which is connected to the ext_spi_clk on the qspi ip core. On step 5 i would also add the qspi ,oled and led's based on you block design. On step 9, make sure your mig is connected as it is shown in the image in regards to the reset and output clk 2 of the clocking wizard. Once you have generated a bitstream and exported the hardware/launched sdk then i follow this tutorial. Instead of using the hello world template you will select empty and add the main.c from the examples of the oled ip core to the scr folder of the application. If you are also wanting to use the uart and gpio-leds you will need to alter the main.c that you added to the scr folder for the gpio and uart to work.

thank you,

Jon

[sosso]

hi jpeyron,

             --[Vivado_Tcl 4-16] Error(s) found during DRC. Router not run.

               --[DRC PDRC-43] PLL_adv_ClkFrequency_div_no_dclk: The computed value 400.000 MHz (CLKIN1_PERIOD, net clk_out1) for the VCO operating frequency of the PLLE2_ADV site PLLE2_ADV_X1Y3 (cell design_1_i/mig_7series_0/u_design_1_mig_7series_0_0_mig/u_ddr3_infrastructure/plle2_i) falls outside the operating range of the PLL VCO frequency for this device (800.000 - 1600.000 MHz). The computed value is (CLKFBOUT_MULT_F * 1000 / (CLKINx_PERIOD * DIVCLK_DIVIDE)). Please adjust either the input period CLKINx_PERIOD (10.000000), multiplication factor CLKFBOUT_MULT_F (4) or the division factor DIVCLK_DIVIDE (1), in order to achieve a VCO frequency within the rated operating range for this device.

 

         ---[DRC PDRC-34] MMCM_adv_ClkFrequency_div_no_dclk: The computed value 400.000 MHz (CLKIN1_PERIOD, net pll_clk3) for the VCO operating frequency of the MMCME2_ADV site MMCME2_ADV_X1Y3 (cell design_1_i/mig_7series_0/u_design_1_mig_7series_0_0_mig/u_ddr3_infrastructure/gen_mmcm.mmcm_i) falls outside the operating range of the MMCM VCO frequency for this device (600.000 - 1200.000 MHz). The computed value is (CLKFBOUT_MULT_F * 1000 / (CLKINx_PERIOD * DIVCLK_DIVIDE)). Please run update_timing to update the MMCM settings. If that does not work, adjust either the input period CLKINx_PERIOD (20.000000), multiplication factor CLKFBOUT_MULT_F (8.000000) or the division factor DIVCLK_DIVIDE (1), in order to achieve a VCO frequency within the rated operating range for this device.

[jpeyron]

Hi @sosso,

The warning about the Arty board would not cause the design to fail. Please post the errors you are getting.

thank you,

Jon

[sosso]

hi jpeyron,

     That's the problem, the synthesis works perfectly, but the implementation is full of errors and warnings, so I can't generate the bitstream without passing by the implementation

                 is this related to the warning of the arty board?

                                       

[jpeyron]

Hi @sosso,

That warning shows that the Pmod OLED IP core was made with the Arty board and not the Nexys Video. You can ignore this warning.  Are you able generate a bitstream with your project?

thank you,

Jon