• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 46 subscribers
  • Views 475 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.

TSW1400EVM: EEPROM rewriting

Thibaut C
Prodigy 30 points
Part Number: TSW1400EVM


Hello,

I am currently working with TSW1406EVM and TSW3070EVM.

While trying to solve a problem with 3070EVM, I followed the instructions to rewrite its EEPROM (here : https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/85288/dac5682z-evm-drivers-problem). But I carelessly let the 1406EVM plugged-in, and I guess the software wrote to the wrong EEPROM. So now my TSW1406 appears as a TSW3070.

Would it be possible to rewrite the correct parameters into the EEPROM ?

The software that I used in the link above was made in Labview, and included many different configuration from TI devices (see image) but does not include TSW1406 configuration. Maybe this could be added to the list ?

Thank you in advance for your anwsers.

Thibaut

  • +1
    TI__Mastermind 23880 points

    Hi Thibaut,

    I think all that is needed to resolve this is to reprogram the FTDI eeprom using FT_PROG. Please save the following xml template file. tidrive.ext.ti.com/.../b0d5fee8-3444-4e3e-9fbc-fafe0fd8b24d

    Install the FT_Prog software from FTDI at this link: ftdichip.com/.../FT_Prog_v3.12.19.634-Installer.zip

    Connect a USB cable between the host PC and the TSW1406EVM. To be safe, unplug all other TI EVMs from their USB connections. Run FT_Prog.exe, which will be used to enumerate the TSW1406EVM. Do the following steps in this order:

    1. Click on the magnifying glass to scan the USB (yours will read as the TSW3070 board).

    2. Apply tsw1406.xml template – Right click on the device, then select “Apply Template from File” and browse to the file called “tsw1406.xml”.

    3. Right click on the lightning bolt then select “Program”.

    4. Right click on the device then select “Cycle Port Rescan” – it should read TSW1406. The EEPROM should be reprogrammed to the correct name. Close FT_Prog. 

  • 0 in reply to Chase W
    Prodigy 30 points

    Hi Chase,

    Thank you for your answer.

    I installed FT_PROG as you recommended, but the board is not detected ("No devices" when I click "Scan and Parse")

    In my Windows device manager, I see two devices "DAC 5682" (I said it appeared as TSW3070 in my previous message, that was a mistake), but no proper driver are installed. I believe the FTDI chip is FT2232H but I can't seem to find correct drivers (I can find FT 4222H, FTDI Serial Converter, ... but no FT 2232H)

    Thank you

  • 0 in reply to Thibaut C
    TI__Mastermind 23880 points

    Hmm. Strange how no devices are shown in FT_PROG, I was not expecting this. Try to reinstall the FTD2XX drivers from here: https://ftdichip.com/wp-content/uploads/2021/08/CDM212364_Setup.zip

  • 0 in reply to Chase W
    Prodigy 30 points

    No luck on that. I tried reinstalling the driver but by default it does not show in FT_PROG.

    I tried to install other FT drivers instead from the device manage(FT4222H) and then the device shows in FT_PROG, but when I try to apply your template, I have this error message "Failed to load a valid template. This is not a valid device type".

    Oddly, I still manage to overwrite the EEPROM with USBSerializer (from my first message) without a problem.

    If this software is still available in development, may I suggest to add the parameters for TSW 1406 ?

  • 0 in reply to Thibaut C
    Prodigy 30 points

    Hello Chase,

    I managed to solve my issue.

    From the Windows device manager, I installed FTDI USB Serial Converter drivers. Then, I could see the device in FT_PROG.

    At first, I could not program the EEPROM : I had to erase it totally before.

    I then used your template file successfully but I had to modify it a bit : "chip details" was changed from "FT4232H" to "FT2232H". Also, from FT_PROG, I changed settings in "Hardware Specific" : both ports were set to "Opto isolate", I changed that to "RS232", otherwise that would not work for me.

    After that, the board was successfully detected by the HSDC Pro software and worked as expected.

    Thank you again Chase for your help, have a nice day.

    Thibaut