This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DDC11XEVM-PDK: Code Support: FPGA VHDL or Verilog Code also Code (VB Application) to exchange data via USB...

Part Number: DDC11XEVM-PDK
Other Parts Discussed in Thread: DDC112

Hello I want to use this EVAL-Board to develop the frontend for a new kind of THz-sensor.
I did a lot of work with Xilinx SpartanII and the old toolchain is still available. In order to speed-up the development in our research I want to ask for the fpga source code as a frame to modifiy and "functionalize" the nice DDCBM-board.

In order to visualize our data I want to write a python-GUI and I need also your support/ code of the small VB-App to re-engineer the data exchange via the USB port...

The EVAL-Board seems to be very flexible and thanks to the reconfigurable fpga hardware a lot more is thinkable. I was wondering that no CD was included!

Every help will be appreciated!

Thank You in advance !

Ritchie

  • Hi Richard,

    After talking with my team, we could not pin down a customer version of the FPGA code for the 11X. We have an internal one but it is not shareable. What I can give is the 264 FPGA Code. They share similar FPGAs, and we've had customers successfully using the 264 GUI code with 11X parts. Let me know if this can help.

    /cfs-file/__key/communityserver-discussions-components-files/1023/3858.7384.FPGA-Firmware.zip

  • Dear Matt,

    thanks for the fast reply! After some confusing I realized while comparing the schematics that the DDC264EVAL and DDC11XEVAL share a *lot*. Funny also that the '264-GUI has more options for data representation and is also more intuitve regarding the graphical representation of the timing - good work :)

    I never worked with verilog but at a first glance it looks like I have to modifiy a few pins in the ucf-file and adapt the timing model (for DDC112/4). But it looks like it uses an op-coded dictionary to interact with the driver on the computer side - something right?! Is the op-code the same for the DDC11X?

    Is the EZ-USB FX2LP-interface and firmware you use the standard "out-of-box" stuff cypress provide? (regarding C-firmware)

    Computer side:I want to write a ctypes-wrapper in python in order to get data in/out of the win10.DLL you use in your GUI. A few hints and tips here would also help much. Because in the first step I want to exchange data through the existing driver-usb-controller-fpga-path to control the DDC112/114...

    Please give big thanks to your team - I put me forward. But a few more questions raise :))

    Regards,

    Richard 

    PS: when I start modifying the DDCMB-board I need some original bit-files for the fpga otherwise as a back-up...

    PS2: you mention the GUI-code of the '264: I will look around to find it - thx

    1. edit: I found the "USB_IO_for_VB6.dll’ User Guide" - the DLL I need to communicate to the DDC. Question: Are the register addresses the same? Or similar? I need the registers for the DDC112/114...

  • Hi Richard,

    I am closing this thread for now due to inactivity.
    If you still have any questions, please send email to praveen.aroul@ti.com and mendez@ti.com