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.

TPS53688: BAD DATA LENGTH programming error

Part Number: TPS53688

Tool/software:

Hello,

Customer proto manufacturing needs support on TPS53688 programming error reporting: BAD DATA LENGTH.

This error, is causing TI FUSION DESIGNER software to not able to detect any devices until the TI dongle USB is I reinitialize (unplug/plug)…
Attachined a sample output from the programming and the program file.

 The programming command : FusionConfigWriter --address 119 --project --infile ""C:\NTFW\Load\NTK710CA\TPS53688\TP53688_119d.xml"" --force-write --erase-data-flash-before-importing 0xff --reset-when-done always

Can you please advise

Thank you

 

All 136 valid PMBus parameters records in project file will be written in 'Write_All' mode.
Starting write of 135 parameters ...
Wrote ON_OFF_CONFIG [0x02,Rail #1] 0x18 [0x18] to RAM
Wrote OPERATION [0x01,Rail #2] 0x00 [0x00] to RAM
Wrote ON_OFF_CONFIG [0x02,Rail #2] 0x18 [0x18] to RAM
Wrote OPERATION 0x00 [0x00] to RAM
Wrote PHASE_CONFIG  [0xB3] Pin Enable: PWM1, Page=0, Order=0, Turbo = Yes, Phase=0; Pin Enable: PWM2, Page=0, Order=1, Turbo = Yes, Phase=1; Pin Disable: PWM3, Page=0, Order=6, Turbo = Yes, Phase=0; Pin Disable: PWM4, Page=0, Order=2, Turbo = Yes, Phase=0; Pin Disable: PWM5_, Page=0, Order=5, Turbo = Yes, Phase=0; Pin Disable: PWM6, Page=0, Order=1, Turbo = Yes, Phase=0; Pin Disable: PWM7, Page=0, Order=4, Turbo = Yes, Phase=0; Pin Enable: PWM8, Page=1, Order=0, Turbo = Yes, Phase=0; Pin Disable: PWM9, Page=0, Order=0, Turbo = Yes, Phase=0; Pin Disable: PWM10, Page=0, Order=0, Turbo = Yes, Phase=0; Pin Disable: PWM11, Page=0, Order=0, Turbo = Yes, Phase=0; Pin Disable: PWM12, Page=0, Order=0, Turbo = Yes, Phase=0;  [0x008001810600020005000100040010800000000000000000] to RAM
Wrote TI_ONLY_CONFIG_1 [0xCD] 0x0101010101010101010141012E2A030C0100100000000000600000000000002A [0x0101010101010101010141012E2A030C0100100000000000600000000000002A] to RAM
Wrote VIN_OV_FAULT_LIMIT [0x55] 19 V [0x0013] to RAM
Wrote VIN_OV_WARN_LIMIT [0x57] 19 V [0x0013] to RAM
Wrote VIN_UV_FAULT_LIMIT [0x59] 4.00 V [0xF010] to RAM
Wrote VIN_ON [0x35] 9.25 V [0xF025] to RAM
Wrote VIN_OV_WARN_LIMIT [0x57] 13 V [0x000D] to RAM
Wrote VIN_OV_FAULT_LIMIT [0x55] 14 V [0x000E] to RAM
Wrote VIN_UV_WARN_LIMIT [0x58] 8.50 V [0xF022] to RAM
Wrote VIN_UV_FAULT_LIMIT [0x59] 8.00 V [0xF020] to RAM
Wrote IIN_OC_WARN_LIMIT [0x5D] 4 A [0x0004] to RAM
Wrote IIN_OC_FAULT_LIMIT [0x5B] 80 A [0x0050] to RAM
Wrote IIN_OC_WARN_LIMIT [0x5D] 72 A [0x0048] to RAM
VOUT_MODE [Rail #1] write VID = 01 [0x21] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
VOUT_COMMAND [Rail #1] write 0.700 V [0x005B] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
VOUT_UV_FAULT_LIMIT (Offset only) [Rail #1] write 0.715 V [0x0008] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
VOUT_UV_WARN_LIMIT (Offset only) [Rail #1] write 0.312 V [0x0059] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
OT_WARN_LIMIT [Rail #1] write 90 C [0x005A] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
OT_FAULT_LIMIT [Rail #1] write 150 C [0x0096] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
OT_WARN_LIMIT [Rail #1] write 140 C [0x008C] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
OT_WARN_LIMIT [Rail #2] write 90 C [0x005A] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
OT_FAULT_LIMIT [Rail #2] write 150 C [0x0096] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
OT_WARN_LIMIT [Rail #2] write 140 C [0x008C] on TPS53688 @ PMBus Address 119d error: BAD DATA LENGTH
TPS53688_119d.xml

  • Hi,

    Our expert on device programming and Fusion is currently out of office. I will look at your program file and check with the rest of the team, but we may not be able to provide an answer until they return.

    Regards,

    Troy

  • Understood and thank you for letting me know.

    Best,
    Cosmin

  • Hi Cosmin,

    Since this error first occurs while importing a new configuration, you can try importing a NVM Config File to your device to prevent the error occurring.

    To do this you will need to export the NVM Config File from an online device by first opening the device configuration in Fusion GUI and then going to: File -> Export -> NVM Config File. Then select to import this file, while connected to a new device, in the GUI.

    You may alternatively try adding the following flag to your command: --import-using-nvm-data true, giving:

    FusionConfigWriter --address 119 --project --infile ""C:\NTFW\Load\NTK710CA\TPS53688\TP53688_119d.xml"" --force-write --erase-data-flash-before-importing 0xff --reset-when-done always --import-using-nvm-data true

    Additionally, please find the NVM Programming Guide for VR13 Controllers at the following link, for your reference: https://www.ti.com/lit/an/slua888/slua888.pdf 

    Regards,

    Troy