• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 63 subscribers
  • Views 189 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.

TPS546D24A: USER_DATA_01 writing fails

Kazuki Itoh
Genius 10820 points
Part Number: TPS546D24A

Hi team,

Could you please help me to address the issue below?

[Status]
(B1h)USER_DATA_01 (Datasheet P.127) programming fails
[Detail]
・Other settings programmed via PMbus is OK (e.g. frequency, UV/OV threshold)
・USER_DATA_01 programming was done with below procedure
- EN pin goes low
- (01h)OPERATION bit7[ON_OFF] is disabled
- (10h)WRITE_PROTECT is 00h so all commands are valid

I guess some prior setting is needed to write (B1h) USER_DATA_01.

Regards,

Itoh

  • +1
    TI__Guru 56985 points

     

    1) Make sure the data-length and transaction type for USER_DATA_01 is correct.

    USER_DATA_01 (Command Code B1h - COMPENSATION_CONFIG) is a 5-byte BLOCK data value, so the transaction needs to look like:

    Start // Target Address + Write Bit / Ack / Command Code = B1h / A / Block Count = 05h / A / First Byte / A / Second Byte / A / Third Byte / A / Fourth Byte / A / Fifth Byte / A / PEC Byte (Optional) / A / Stop

    The Byte Order is [Block Count = 05h] [7:0] [15:8] [23:16] [31:24] [39:32] - so the first byte sent after the Block Count is the byte with the GMI / GMV data.

    2) In a Multi-phase STACK, COMPENSATION_CONFIG is only programmable when PHASE = FFh, so check the PHASE command setting before writing COMPENSTION_CONFIG

    Use the READ_BYTE transaction type to read the value of PHASE (Command Code 04h) and if it is not FFh, write PHASE = FFh to set the phase control to "ALL Phases" 

    3) If none of those work for you, check the PMBus signal waveforms to see where in the transaction the failure is occurring.