• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 46 subscribers
  • Views 432 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TSW14J57EVM: TSW14J57EVM not recognized by High speed data converter Pro

Sunset
Genius 13385 points
Part Number: TSW14J57EVM

Hello Team,

I faced the problem that High speed data converter Pro could not recognize the TSW14J57EVM.

I have followed the section 4 but I could not make it work.

The driver was visible and installed.

Comparing the jumper setting with a working board I have seen that JP2 was not connected on the working board while on mine the jumper was closing pin 1-2. JP4 on my board was open, while on the working one it was between pin 2-3.

In the used guide is written that JP2 must be open but is a single line in the user guide.

I'm not sure if this jumper came close directly from production, since the card was brand new, same story for JP4.

JP2 and JP4 change some programming modes, but without schematic is difficult to judge the jumper functions.

I think it would help if in section 4 you would add that if PMODEx are not properly set, the driver is seen but board may not be recognized by the GUI.

This may help the troubleshooting.

Beside that challenge, the TSW14J57EVM and the ADC board are now working.

Thanks,

SunSet

  • 0
    TI__Guru* 91947 points

    Sunset,

    There were a few boards shipped that had these jumpers in the wrong location by accident. We are working on making sure this does not happen again. The jumper location should be as follows:

    JP1 1-2

    JP2 open

    JP4 2-3

    JP5 2-3 

    The board manufacturing house was placing the jumpers into USB3.0 EEPROM programming mode after test by accident.  We are looking into adding more comments in the User's Guide per your suggestion.

    Regards,

    Jim

  • 0 in reply to jim s
    TI__Genius 13385 points
    Thanks for the confirmation and follow up.

    I was assuming that this could have been a result of a production step.

    I think that updating the user guide to cover this scenario in the troubleshooting section, will make the starting experience better.

    Ciao,

    SunSet