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.

AIC3100 EVM USB corrupt

Hi all.

I've been testing AIC3100 EVM by some time. Everything was ok, I could reprogram the codec via scripts. My last test was to program the codec via external MCU connecting it through the tests points of the EVM. I could program the complete initialization of codec via I2C.

Problem.

I don't know why, a day after I finished programing the codec via external MCU, the built in EVM MCU (TAS1020) didn't work. My PC didn't know it as a USB device. It's very strange for me that USB port of TAS MCU has been corrupted by I2C communication.

I think a possible solution would be to reprogram TAS MCU. Does somebody can help me?

  • Hi Gerardo,

    To re-flash a TLV320AICxxxx, TLV320DACxxxx or TLV320ADCxxxx EVM follow the steps below.

    1. First obtain the latest firmware files from http://www.ti.com/lit/zip/slac563.
    2. Follow the steps in the attached document (below). This guide was meant for the AIC3254EVM-K, but can be applied to any EVM by replacing some steps as below.  
      1. In step STEP 2.1.2, instead of "removing EEPROM jumper", short SCL and SDA together before connecting the EVM for the first time and then plug the USB cable. After 5 seconds, remove the short. The short can be any conductor between the on-board EEPROM SCL and SDA pins like the tip of a resistor held momentarily between the EEPROM SCL and SDA pins.
      2. Ignore STEP 2.1.3.
      3. In step STEP 2.3.3, ignore the "insert EEPROM jumper" statement. This is because we achieved the same by removing the short as described above.

    4572.TLV320xxxEVM-K Firmware Programming_v1_1_1.pdf

    Let me know if this helps.

    Additional Information: http://e2e.ti.com/support/data_converters/audio_converters/f/64/t/218025.aspx

    Thanks,

    J-  

  • Hi J Arbona

    I apologize by my late answer. Just today I can test your steps. After a few tries it works.

    Thank you very much.

    Regards

  • Hi Gerardo,

    Good to hear you got it working!

    Regards,

    J-

  • I also encountered the same problem with my USB-MODEVM board (for my TLV320AIC3106EVM).
    But then, re-flashing the the firmware seems not to work for my board.
    After completing, as reconnect the USB-MODEVM, the USB Active LED (D2) is still off. Though it was detected by my PC as DFUUSB in my device manager, instead of USB-MODEVM.

    I also installed the windows7 driver (SLAC521), but still, it didn't work.
    Are there any steps in the process that I missed?

    Hoping for your quick response. Tnx!

    Addition inquiry:
    As I plug the USB-MODEVM to other PC, it was detected as an unknown device, unlike on the PC that I used for re-flashing the firmware.

  • Hi Rechie,

    For AIC3101, AIC3104, AIC3106, AIC3107, AIC34, AIC31, AIC33, DAC32 EVMs, a different F/W should be used. Follow the steps above, but use the image below instead. Make sure that the SW2 switch on the motherboard and the EEPROM jumper on the daughtercard are correctly configured.

    http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/64/8267.USBMODEVM105.BIN

    Regards,

    J-

  • Hi Sir J Arbona,

    Should the TLV320AIC3106EVM (daughter) connected on the USB-MODEVM(main)? If so, what should be the Jumper setting of JMP18 of the daughter board?

    Regards,

    Rechie

  • Hi Rechie,

    Yes, the two boards should be attached per the EVM User Guide.

    By default, JMP18 is removed. This is because, for the devices I mentioned (like AIC3106 EVM), the USB firmware image resides in the motherboard (USB-MODEVM). But it really does not matter where the firmware image is burned into, the important thing is that only one eeprom can have the 0xA0 I2C address. So you can follow the procedure I described for AIC3254, but using the USB-MODEVM0105.bin file instead.

    Regards,

    J-

  • Sir J,

    The board is finally working. Thank you for the support. :)

    Regards,

    Rechie

  • Great! Thanks for the follow-up.

  • i did the procedure for same explanied above, but after that my board is getting heated up badly, what shall i do, what may be the problem