• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 148 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Required help with the device requested

Narayani Priyadharshini
Prodigy 10 points
Part Number: TPS546D24A

Hai , I am Narayani from BPM Microsystems. We have a customer request on programming the flash of device TPS546D24ARVF

Initially i am communicating with the device using 0x7F as a slave address. I have the data file where i have set address to be 0x10 using 0xEF command. When I perform a device reset, will the slave address get back to 0X7F?

  • 0
    TI__Guru 50925 points

     

    Narayani Priyadharshini said:
    Initially i am communicating with the device using 0x7F as a slave address. I have the data file where i have set address to be 0x10 using 0xEF command. When I perform a device reset, will the slave address get back to 0X7F?

    It depends on what you do after you set the address to 0x10 using 0xEF.

    0xEF takes immediate affect.  Once the command is received, the TPS546D24A will stop responding  to 0x7F and start responding to 0x10.

    If you take no other actions and remove power from AVIN, none of the changes will be retained and the device will restart with address 0x7F

    If, after changing the address to 0x10, you send command code 0x15 (STORE_USER_ALL) to address 0x10, the changes made will be stored to NVM, and the address will depend on what was written to command 0xEE (PIN_DETECT_OVERRIDE) which determines which commands are loaded from NVM and which commands are loaded from Pin Detection.

    If Bit 8 of Command Code 0xEE is set to 1, the device address will be set by the ADR_SEL pin and will remain 0x7F

    If Bit 8 of Command Code 0xEE is set to 0, the device address will be set by the NVM stored value and will be 0x10

    Note:  Pin Detect Override contains bits for several other commands.  If the changes made are stored to NVM with Command Code 0x15, their values will also depend on the setting of Command Code 0xEE (PIN_DETECT_OVERRIDE)

  • 0 in reply to Peter James Miller
    Prodigy 10 points

    Hi,
    We were initially doing a send byte 0x15 command followed by CLEAR_FAULTS (0x03) and then 0x16 , but we fail to get acknowledgement from the device after the 0x03 command, so RESTORE_USER _ ALL command is not getting executed. The value of 0xEE is set as 0 before reset and after reset it is changed to 0x01, so it means the device address is changed to 0x7F, but still there is a problem with setting the VOUT_WARN _LIMIT. Will there be an effect in VOUT_WARN LIMIT too, when a reset is performed in the device.

  • 0 in reply to Narayani Priyadharshini
    TI__Guru 50925 points
    Narayani Priyadharshini said:
    We were initially doing a send byte 0x15 command

    Is this being sent to device address 0x7F or device address 0x10?

    After writing Command Code EF = 0x10, the device will no longer respond to address 0xEF, but will only respond to address 0x10

    Narayani Priyadharshini said:
    The value of 0xEE is set as 0 before reset and after reset it is changed to 0x01, so it means the device address is changed to 0x7F,

    Command Code 0xEE is a WORD command, not a byte command, it needs 2 bytes of data.

    The 0xEE  value  that matters is the one stored in NVM during the RESTORE.

    Narayani Priyadharshini said:
    there is a problem with setting the VOUT_WARN _LIMIT. Will there be an effect in VOUT_WARN LIMIT too, when a reset is performed in the device.

    The TPS546x24A family of devices allow for different VOUT_MODE settings, and the handling of VOUT_WARN_LIMIT depends on the VOUT_MODE settings. 

    If VOUT_MODE bit 7 = 0, VOUT_WARN_LIMIT is programmed in absolute mode, using the linear 16 voltage setting.

    If VOUT_MODE bit 7 = 1, VOUT_WARN_LIMIT is programmed in relative mode, using the linear 16 format, but as a multiplier to VOUT_COMMAND.  So a value of 0.8 will always be 80% of VOUT, regardless of the VOUT_COMMAND value.

    What are you seeing as the issue on the VOUT warn limits?