• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 46 subscribers
  • Views 336 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TSW14J50EVM: TSW14J50EVM

Robert Bernier
Prodigy 10 points
Part Number: TSW14J50EVM
Other Parts Discussed in Thread: ADS54J60EVM, TSW14J59EVM, ADS54J60

I am currently using a 32 bits C example in HSDC Automation DLL examples in order to control the acquisition by a ADS54J60EVM. We have recently understood that the TSW14J50EVM was not the appropriate choice for the ADS54J60EVM. It should have been the TSW54J57EVM. Can you confirm this?

Will the version of HSDC Pro have to be changed too?

Also, I have received many times the same error message as you will find in the following FAQ case : https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1303566/tsw14j50evm-tsw1400-lvlib-is-missing .. The response by your engineers was to install the version 5.20 of HSDC Pro but this is what I have and it does not solve the problem though I have uninstalled and reinstalled twice.

Weirdly, I have found that, by using my C application executable to connect to the board, even though it causes an error, after that I can use again the HSDC Pro and the error above does not appear. 

Is this error due to not using the appropriate TSW card?

With the set of TSW14J50EVM and ADS54J60EVM cards, I am very far from meeting the 177E6 bits per second acquisition/saving specification. I hope that the TSW54J57EVM will do the job. Please, confirm that it is the good number to choose since we had, back in January, found TSW14J50EVM instead and, more recently, TSW14J56EVM .

I look forward to reading from you at my company email.

Robert Bernier

Les instruments optiques

du Saint-Laurent inc.

  • 0
    TI__Mastermind 38690 points

    Hi Robert,

    Unfortunately, the TSW14J56 & J57EVM s are obsolete.

    Correct, the TSW15J50EVM is the appropriate data capture solution either.

    The best alternative is to use the TSW14J59EVM or use a Xilinx development kit in order to capture data.

    Do you have the ADS54J60 EVM already? Are you open to other ADC device considerations for your application?

    Please advise.

    Thanks,

    Rob 

  • 0 in reply to Rob Reeder
    Prodigy 10 points
    The answer does not resolve my issue.
    The answer states: the TSW15J50EVM is the appropriate data capture solution either. 
    What we have is the TSW14J50EVM , not the TSW15J50EVM, which probably does not exist. We also already have the ADS54J60 EVM.
    What started my questions are two facts: 
    1. with the HSDC Pro and the above boards, we were supposed to have access to the possibility of Auto Re-Arm Trigger but it was never available, button always greyed;
      I have tried multiple times to download firmware tsw14j56revd_adc_ddr_dac_bram_256kb_xcvr_firmware but it failed to download.
      Address of the FAQ where they said to download tsw14j56revd_adc_ddr_dac_bram_256kb_xcvr_firmware: https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1104534/tsw14j56evm-re-arming-trigger-with-hsdc. 
      I need to use this option of Auto Re-Arm Trigger
    2. The second point is that I was never able to achieve the rapidity of data acquisition which is claimed for this acquisition board: only 2.59E6 bits per second while I have seen a document claiming 177E6 bits per second with USB 2.0.
  • 0 in reply to Robert Bernier
    TI__Mastermind 38690 points

    Hi Robert,

    Sorry for the mis-typed numbers on my end. My bad.

    Unfortunately, we cannot support this request. The TSW14J50EVM is not the recommended data capture solution as per the ADS54J60EVM.

    The TSW14J56EVM is the recommended data capture board as per the user guide. Also, for both TSW boards, all the FW was developed by an outside contractor that we no longer work with.

    Regards,

    Rob