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.

TPS65987D: TPS65987D programming Overflow issue

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS65987

Hello,

I'm trying to program the TPS65987DDH through the FTDI FT4232 (the same used on EVM Board)

As you can see below, i can correctly sweep and recognize the I2C address of the TPS which is 0x21, i can also make a SPI Read (both SPI and I2C1 are connected between the FTDI and the board)

The flash erase also works correctly 

But when i'm trying to save the Binary file inside the flash or on my computer to program the SPI Flash with it after, i have the message below

If needed, you can see my schematic as attachment and also the binary file saved in Zip

Schematic_Bidirectionnal USB_C Charger_2022-04-19.pdf

TPS65987.zip

  • Hi Alan,

    Can you please reattach the error message? It did not load correctly. Typically an issue like this may occur with the FTDI adapter due to the drivers on your PC. I suggest redownloading the drivers or installing the latest GUI to get them. Which GUI version do you have?

    Regards,

    Taylor

  • Hello Taylor,

    See below the exception issue, 

    the FTDI works correctly for me because when i'm trying  to sweep I2C address or to make SPI Read it works correctly 

    But when i'm trying to save the binary I have this issue even if i don't use the FTDI and if i try to save the Binary directly on my computer

    Do you have any idea ?

    Btw, if i try to upload the binary from my current project i have the error below: 

    but when i'm uploading the flash from a binary files it seems to work (but since i cannot change/save a binary files i can't use this solution)

    thank you,

    Alan

  • Hi Alan,

    It looks like you have likely gone over the allocated application configuration size shown below. If your number of used bytes exceeds the allocated bytes, you will be going over the limit and not allow the binary to save off due to this. Typically this size will grow due to adding virtual configuration sets or too many I2C commands that you can check if you can optimize the project settings better to avoid.

    Regards,

    Taylor

  • Ok thank you, 

    I updated the application and i started with new files it seems to work correctly