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.

TSW1400EVM FPGA Source Code Change Settings for ini File

Other Parts Discussed in Thread: AFE5851EVM, AFE5851, ADS5294

Hello,

Our team now is using TSW1400EVM and AFE5851EVM to implement a system.

And I have got FPGA source code(Quartus II project). (ver,1.00 and 1.11)

I also know there is .ini file for AFE5851EVM in HSDC Pro.

Now I want to let the source code working with 5851 perfectly.

How to change the setting parameters in source code and "define.vh"  according to the .ini file?

I know there are "Channel Pattern", "Channel Mapping Index",  "Number of bit clks in a fclk period", "Number of bits in Output format", "Number of channels in output format"...etc which are different to other ADC.

And in "define.vh"  there are CONFIGxx_DEFAULT, CHANNELxx_DEFAULT and other parameters.

So how to change the source code parameters that I can work perfectly with AFE5851EVM, rather than using HSDC Pro firmware?

I have asked this question for a long time.

If there is anyone can reply me as soon as possible, I would very appreciate.

Best regards,

JhinCi.

  • JhinCi,

    I do not understand what you are trying to do. Is your setup working with an AFE5851EVM? If not, what is wrong. If it is working, what exactly would you like to change?

    Regards,

    Jim 

  • Hi Jim,

    Thanks you for your reply.

    In our implement, we would use TSW1400EVM to capture ADC data from AFE5851EVM and transfer to PC.
    And we would also use 1400 to control our PCB MUX circuit and control other digital outputs.

    So we will use source code and add some our modules in it.
    Even in our final purpose, we might develop our GUI and our communication between TSW and PC replacing the HSDC Pro.

    But first we have to confirm source code for FPGA capturing ADC data is correct and would let 1400 work perfectly with 5851.

    For now, we get source code which generic to ADC but haven't modified it according to AFE5851EVM.
    And I don't know how to modify it in "define.vh".

    Our way to download firmware is using Quartus II to convert verilog source code to ".rbf" file and using HSDC Pro to download this to FPGA.

    According to AFE5851_12X.ini, I tried some tests that changing "define.vh" which can let TSW capturing AFE,
    but I do not know it is work correctly or not.

    (and in my test sometimes there is a error show as bellow)

    So basically I need TI engineer help to confirm it.

    Kind regards,

    JhinCi

  • The AFE5851_12X.ini and define.vh which i have modified are in the link below.

    AFE5851_12X.ini   (in HSDC Pro) 

    define.vh

  • JhinCi,

    I've moved this thread to the medical devices forum as this ultrasound AFE5851 belongs to that group and they can support this device better.

    Both links in your post are for define.vh, can you relink the ini file? Or is the ini file the standard one that comes with HSDC Pro?

    In general we are not staffed appropriately to support custom firmware questions as we generally have the FPGA firmware and GUI software work done by a contractor team. However we will help where we can.

    The AFE5851 INI indicates that the interface name is ADC_FIRMWARE. This also aligns with the TSW1400_IID_Lookup.csv file in the 1400 Details folder which shows the ADC_FRIMWARE is assigned a IID of 127. If you look at the define file, it should be by default defined for IID of 127 (the comments list the ADS5294, but it is valid for any ADC that uses ADC_FIRMWARE) . This should generate the same firmware file (ADC_FIRMWARE) as needed by the AFE5851 INI. If you compile this and convert it to rbf it should work with the AFE5851. If you use the same name ADC_FIRMWARE.rbf you could just replace this in the firmware folder and it would be loaded when you pick the AFE5851 in HSDC Pro.

    This generic ADC_FIRMWARE is used by many of the newer ADCs and just stores the binary data in DDR memory, the channel pattern within the device INI then specifies how these bits are formated into samples specific to that particular device. This was done to simplify the firmware for our evaluation platform so that we did not have a device specific firmware as we did for some of the older ADCs. You can see this custom firmware in some of the other older INI and also in the define.vh and the look up iid file. If you use the default settings the IID should be 127 and the firwmare should work fine as the HSDC Pro doesn't know any different.

    If you need more in depth support for the firmware and software I will have to get you in touch with our contractor team. We can do that offline if needed.

    Ken.