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.

TLV320AIC3256EVM-U: Firmware was erased - EVM disconneted

Part Number: TLV320AIC3256EVM-U


I start to learn a TLV320AIC3256EVM-U and when i try to write another image to EEPROM the board not response, its seems that the firmware erased.

in AIC3256EVM-U CS program have red led and write "EVM disconnected"

 i try to do extraction in this link but its not resolved, 

i work on WIN 10 OS.

can you help me to resolve this problem? 


  • Hi, Kobi,

    The steps mentioned on the E2E post you are referring to are actually the right ones to follow to get the board re-programmed. I think the issue is that the link for the necessary tools are broken. Please refer to This post to download the required tools to re-program the EVM's EEPROM. Please consider that in order to work properly, only the provided images should be used. 

    Best Regards,

      -Diego Meléndez López
       Audio Applications Engineer

  • Hi Diego,
    Thanks for your quickly answer,
    but this pdf its the same extraction that have in E2E post,
    i in this level:
    6. Run DFUTEST.exe. If a "No DFU devices found" window appears, then that means that steps 2-5 were not followed properly. Close DFUTEST.exe and repeat steps 2-6.

    i do 2-6 steps again and again but the same result occur yet.

  • Kobi,

    Thanks for the feedback. The steps on the pdf are almost the same but the links in the document points to the latest software. If no DFU device is found, it is suggested that the DFU driver was not installed properly. Can you verify in device manager of your computer that the EVM is recognized as DFU device after connection?. Another possibility for the device firmware update to fail is that the EEPROM in the EVM is damaged. 

    Best Regards,

      -Diego Meléndez López
       Audio Applications Engineer

  • Hi Diego,
    the problem resolved, you are right the DFU driver was not installed properly,
    I choose the folder "dfu_driver" automatically and the windows choose the default driver that its not DFU so i update driver again but now i choose DFU driver manually from the list