• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 595 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.

TPS65982-EVM: Recovery Problems with Configuration 12

Graham Haddock
Prodigy 80 points
Part Number: TPS65982-EVM

I have several TPS65982-EVM (Rev 1.0) that when running the originally supplied (factory) firmware work as expected in configuration ID 12 (Mid Power Charger Adaptor).

If I try to either recover after software experiments, or just update using TPS6598x Application Customizer 2.12, Configuration 12 no longer works.

Using an Aardvark, I can load directly from TPS6598x Application Customizer 2.12, Device/Reflash EVM Firmware (Recovery). The firmware loads and verifies.

Or, I can use the Aardvark FlashCenter and the EVM recovery binary supplied with 2.12, and the firmware loads and verifies.

In both cases, Configuration ID12 no longer functions. By that I mean, the power LED is ON, but when connected to a Dell tablet, instead of lighting the 5V LED and PVDR LED as expected, it only lights the CONS LED, and no current flows in the Vbus, although the EVM is powering the Vbus at 5 Volts.

Is there something else I need to do to recover these modules? Such as reload a different version Low Region Binary to go with the firmware?

Is there a way to find out what version firmware is loaded on an EVM?

  • 0
    TI__Mastermind 36756 points
    Hi Graham,

    The firmware image provided with the Application Customization Tool is the same image that is loaded onto the EVMs from the factory. Please ensure that the switch setting on the TPS65982EVM is correct for your application. These settings can be found on page 13 of the EVM user manual:
    www.ti.com/.../slvuaf8c.pdf

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    Prodigy 80 points
    Hi Eric:

    Thanks for the fast reply.

    Unfortunately, I can pretty much guarantee that the recovery file in the Application Customization Tool is NOT identical with what you are shipping from the factory.

    I verified that the switch settings are correct.

    When I try to use the Configuration 12 (mid power charger adaptor) with a factory new EVM, just out of the box, it works as expected.

    When I use the Application Customization Tool with Aardvark to recover or update the firmware, it does not charge the Dell tablet.

    When I use the Flash-Center GUI with Aardvark to recover or update the firmware, with the ".bin" file from the Customization Tool, it does not charge the Dell tablet.

    When I use the Flash-Center GUI with Aardvark to extract a firmware image from a factory new EVM, just out of the box, and then use that image to recover an EVM that had been reprogrammed, then the EVM works as expected, and duplicates the behavior of the factory new unit.

    I conclude that the recovery firmware load is NOT identical (or complete) to what you are shipping from the factory, and that it is not a hardware or switch configuration problem.

    I would recommend that you take a working new unit, use an Aardvark to erase all, to make sure that you are not depending on some residual code in the memory space, then try to recover it using your published procedure, and make it work on Configuration 12.
    Hint: Make an image/copy of what is in the factory EVM before you erase it.

    --- Graham

    ==
  • 0 in reply to Graham Haddock
    TI__Mastermind 36756 points
    Hey Graham,

    We did do an update to the firmware a while back. It could be that you ordered a board that had the older build on it. Verify that the EVM can do the first and last switch setting. That would ensure that the image is correct.

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    Prodigy 80 points
    Eric:

    I have about eight of these EVM modules, so this is not an isolated hardware problem. They all come from Mouser, over a six month period, and are all marked EM400706 REV 1.0.

    I solved my own problem, by coming up with my own alternate recovery solution, which is to make a copy of the firmware that came from the factory with the module, to recover them.

    I think TI has a problem, in that the recovery software that is provided with Application Customizer 2.8, 2.10, and 2.12 does not work in all instances. I have recovered one module using it, but, if you erase the EEPROM with the Aardvark programmer first, your recovery software DOES NOT WORK.

    I interpret this to mean that you are only taking a snapshot of a portion of the memory space in your recovery software, and if the customer has modified any of the rest of the (required) software, that the recovery software no longer works, because it is not complete.

    But my interpretation could be wrong.

    --- Graham

    ==