• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 32 subscribers
  • Views 2397 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.

TLV320AIC3254EVM-U - EEPROM Writer?

Dean Anderson
Prodigy 90 points


I have been using the TLV320AIC3254EVM-U for a week.  Everything was going great with PurePath Studio.  While changing fs, I did something that has caused Windows to no longer recognize this USB device.  I believe I need to reload the EEPROM.  After reading the other posts, I downloaded AIC3254EVM-U_CS_v_1_2_1.  When running this program, it says: "EVM disconnected...".  I also can't seem to find "Tools > EEPROM Writer".  Could someone give me detailed instructions to bring the unit back to the "as shipped" EEPROM programming?

Thanks!

  • 0
    TI__Mastermind 46195 points

    Hi Dean,

    If it is not recognized by AIC3254EVM-U CS, then it is possible that the EEPROM image got corrupted.

    This update procedure is only valid in Windows XP since the DFUUSB.sys driver is not compatible with Windows 7. However, after you re-write the EEPROM on a WinXP machine, you can use the AIC3254EVM-U CS in Windows 7 by running in Windows XP compatibility mode (right click AIC3254EVM-U CS shortcut for this setting).

    Let's try to revive the board step-by-step:

    1. Disconnect the EVM and place a temporary conductor between pins 5 and 6 of U3 to short both pins. You can use one end of a through hole resistor ... its diameter is typically wide enough to short both pins. Connect the EVM to the USB port and after ~3 seconds you can remove the short. The whole point of this is to make the TAS1020B USB controller boot in DFU mode (which will happen because no valid EEPROM is found (SCL/SDA are shorted).

    2. A "Found new hardware" wizard will appear in Windows XP. Leave the window open for now.

    3. Open AIC3254EVM-U CS. Double-click the Tools > EEPROM Writer category as highlighed below.

     4. Click on the second tab "Upgrading the EEPROM....". Start from STEP 4 (in "Page 2: DFU driver"). Page 1 is only used if you have an EVM-K (which basically does what you already did by shorting the SCL/SDA pins). Also, ignore the "insert EEPROM" statement in STEP 7.

     

     Regards,

    J-

     

  • 0 in reply to J-
    Prodigy 90 points

    Hi J-,

    Thank you for your detailed instructions.  

    I ordered and received a 2nd AIC3254EVM-U.  I am now using a Windows XP computer and this new module is functioning.  Your AIC3254 CS software appears to function with the new EVM.

    I am still having problems with the first EVM...

    I followed the instructions as you indicated on this same Windows XP computer, found the DFUEE.bin, and Clicked Open.  During the process I received an error message.

    I rebooted the computer.

    Now, when I short pin 5 and 6 of the EEPROM and then plug in the USB, I do not get the "Found New Hardware Wizard".

    When I simply plug the module into the USB, I get a Windows message: "USB Device Not Recognized...One of the USB devices attached to the computer has malfunctioned, and Windows does not recognize it."

    The LED lights up when plugged in and the pins are not shorted.  The LED remains off when the EVM is plugged in with the pins shorted.  

    Sorry I did not write down the exact point when I received the error the first time.

    -Dean

  • 0 in reply to Dean Anderson
    TI__Mastermind 46195 points

    Hi Dean,

    Please try the following with the failing EVM:

    1. Use the image below to downgrade the EEPROM (version V0202) using the same steps as before. If you have errors with the upgrade procedure (e.g. DFUTEST says that no device is found), uninstall the device in device manager and try again. Whenever it says wait for 3 seconds, you need to wait until Windows recognizes the device (even up to 10 seconds).

    http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/64/2605.USBMODEVM0202_5F00_441KHZ.BIN

    2. If the 2.02 firmware was installed correctly and the device is recognized by the control software, go to Tools>EEPROM Manager and uncheck all fields and click WRITE SETTINGS.

    3. Disconnect and connect the EVM to USB.

    4. Upgrade the EEPROM with V2.03 with the simpler procedure found in Tools>EEPROM Writer (under "EEPROM Writer" tab).

    Regards,

    J-

  • 0 in reply to J-
    Prodigy 90 points

    Hi J-,

    Success!  

    Thank you so much for helping me!

    -Dean

  • 0 in reply to Dean Anderson
    TI__Mastermind 46195 points

    Hi Dean,

    Glad you got it working!

    What solved the problem? Was it going back to 2.02, setting EEPROM Manager and upgrading to 2.03?

    Thanks,

    J-

  • 0 in reply to J-
    Prodigy 90 points

    Hi J-,

    I can't say for sure what solved the problem but I suspect that uninstalling the TI USB drivers in the Windows Device Manager seemed to open the way.

    Thank you again for your excellent support!

    -Dean