Topic: .xdc for VC709 - FMC150  (Read 17046 times)

mCezar October 10, 2014, 12:19 PM

  • Member
  • *
  • Posts: 14
Hello, everybody,

I have an FMC150 and need to make it work on a VC709 evaluation board. The 4FM Get Started Guide (r.4.11, p.66) talks about a .bit generated for such a board. How could I get the xdc file used for the VC709-FMC150 combination?

Even better, is there an IP core that wraps this specific interface? Where to get it?

Kind regards,
mC

arnaudNL October 13, 2014, 05:33 AM (#1)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Sir,


The VC709-FMC150 firmware does not come free of charge because it uses PCIe and the PCIe does not come free when buying a FMC150.. Plus we do not support Vivado on Xilinx development boards yet, only on our VP780/FM780 with large FPGAs (1140t). In other words, I am not able to provide you with the XDC file for Vivado.


The BSP free of charge works on Ethernet and there you can use ML605, KC705, VC707, ZC702, ZEDBOARD, ZC706, etc..


Best Regards,
Arnaud

arnaudNL October 16, 2014, 09:34 AM (#2)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Sir,


Please let me know if there is anything I can do before to close this topic!


Best Regards,
Arnaud

mCezar October 17, 2014, 01:53 PM (#3)

  • Member
  • *
  • Posts: 14
Hello, Arnaud,


My only question would be: how to port to VC709 a FMC150 design made for VC707?


Thank you.
mCezar

arnaudNL October 20, 2014, 01:56 PM (#4)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Sir,


You can easily find both VC707 and VC709 schematics on the internet. As soon you will start porting you will encounter a major issue; There is no Ethernet on VC709.


Then you would need to replace the Ethernet engine star with a PCIe star. Implementing PCIe is not a straightforward task so unless you really know what you do I would recommend you to purchase a PCIe star from 4DSP. This will cut you down months of development/debugging because the porting will be straightforward.


Do you want me to get sales to contact you or do you want to initiate the process on your hand directly?


Best Regards,
Arnaud

arnaudNL October 22, 2014, 04:20 AM (#5)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Sir,


Please let me know if I should get you in touch with sales or if you are going to that that on your side.


I will close this topic in 24 hours if I don't get update from you until then.


Best Regards,
Arnaud

mCezar October 22, 2014, 12:36 PM (#6)

  • Member
  • *
  • Posts: 14
Hello,


I first tried to use the reference design for VC707. Hence I followed the steps presented in CD242 VC707+FMC150 r1.0 , I managed to have Stellar IP generete an ISE project, then I could launch the simulation. Unfortunately I can find no output.txt file in the ISE project folder.


I used ISE 14.7 and Stellar IP 1.2.7.0.


I need to be able to simulate this before deciding to continue with the 4DSP FMC150 card. I am looking forward for your help.


Best,
mCezar

iklink October 23, 2014, 06:24 AM (#7)

  • 4DSP Staff (EU)
  • Member
  • *
  • Posts: 153
Dear,


After you have launched the simulation you have to Run the simulation. If you enter "run 400 us" in the Isim Console window the simulation will run for 400us. When the testbench is ended you should find the output.txt file.


Best regards,
Ingmar van Klink
4DSP

mCezar October 23, 2014, 07:38 AM (#8)

  • Member
  • *
  • Posts: 14
Hello,


I had done that, but no output.txt. Moreover, the signals displayed on the ISim screen do not change, they have constant values.


Best,
mCezar

mCezar October 24, 2014, 12:43 PM (#9)

  • Member
  • *
  • Posts: 14
More details about the my failed simulation attempt:
  • While generating the ISE project with Stellar IP, I got this error:
Code: [Select]
TclTasksC:project_028: Unknown property value "Virtex7" specified for "PROP_DevFamily" while executing
    "project set family Virtex7" (file "C:\4dsp\Common\Firmware\Extracted\242_vc707_fmc150\output\VC707_fmc150\VC707_fmc150.xtcl" line 101)
Xtclsh returned exit code 1
and this warning:
Code: [Select]
The star 'sip_i2c_master' has a duplicate file '../vhdl/pulse2pulse.vhd' already included in 'sip_cid'...
  • The ISE project was still generated. But running the simulation (with a specific run 4000 us) produces nothing on screen (except a trigger at 80 us) and no output.txt.
Looking forward for some insight.
Best,
mCezar
  • « Last Edit: October 24, 2014, 12:44 PM by mCezar »

iklink October 27, 2014, 09:54 AM (#10)

  • 4DSP Staff (EU)
  • Member
  • *
  • Posts: 153
Dear,


The fact that you have an error with StellarIP generation is probably the root cause that your simulation is not running properly. The error is generated by ISE because the ISE version you are using doesn't support the Virtex7. Two potential causes are:
- the Virtex7 device support is not installed as part of your ISE installation
- there is no valid Virtex7 device license detected by ISE


Best regards,
Ingmar van Klink



arnaudNL October 29, 2014, 07:18 AM (#11)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Sir,


Was the information sufficient, can we go ahead and close this topic?


Best Regards,
Arnaud

arnaudNL November 03, 2014, 11:18 AM (#12)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Sir,


I will lock this topic in 24 hours without news from your side within 24 hours.


Best Regards,
Arnaud

mCezar November 03, 2014, 12:23 PM (#13)

  • Member
  • *
  • Posts: 14
Hello,

It turned out not to be a license problem. Indeed, I managed to get a working ISE project (and later output.txt) after I run the all the lines of VC707_fmc150.xtcl in ISE's tcl console.

You may close this topic.

Cheers,
mCezar

arnaudNL November 11, 2014, 07:56 AM (#14)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
This topic is being closed because the issue is considered as resolved by 4DSP. Feel free to create a new topic for any further inquiries.