Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 102 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.

TPS2HCS10-Q1: Efuse Standby behavoiur - I2T - Inrush current

Oz Kocoglu
Intellectual 270 points
Part Number: TPS2HCS10-Q1

Tool/software:

Hi there ,

I have some question s on the fueses. this is not only relates to TPS2HCS10-Q1, but in generakl for the HCS -Family. I have following questions:

Standby - Active Mode of MCU

  1. eFuses must be active even when „Mother-ECU“ or the MCU  is in sleep-mode. Is that possible ? How does the device work? Is the current limitation working and does the device wake-up the MCU
  2. InRush-Current-limitation for first charging of SuperCaps via eFuse would be helpful. This would be required even when the MCU is is in sleep-mode. Does that work ?

 

I2T

  1. For I2T, is this one time programmable or need to be done each time?  

Inrush current

  1. Currently  a 21A current requirement we currently use a headroom and a fuse for 30A. How is it with HCS- devices, how much inrush is allowed? 0A

Thanks, 

Oz 

  • 0
    TI__Mastermind 22780 points

    Hi Oz,

    1. This device and all TI HCS devices can be active when the MCU is in sleep, as long as the device has been enabled. All protections are integrated into the HCS device, and if thermal shutdown, overcurrent, or eFuse tripping occurs the device will assert the FLT pin which can wake the MCU.

    2. Yes, the device can be programmed to charge large capacitors with either a constant current or a constant output slew rate. The inrush period length can also be configured. This capacitor charging/inrush period occurs when the respective device channel is enabled.

    3. The I2T curve (and all register settings) will need to be programmed each power-on reset of the device or each time the device is put into sleep mode. During Low Power Mode (LPM), the register values are retained.

    4. Increments between 10A and 70A are supported for inrush overcurrent protection. Otherwise, the I2T nominal value, curve, and software overcurrent value can be scaled with the SNS resistor.

    Thanks,

    Patrick