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.

TAS2563: Current Consumption in active state

Part Number: TAS2563
Other Parts Discussed in Thread: TAS2X63EVM,

Tool/software:

Hello,

I'm using the TAS2653 QFN chip in a battery powered application and need to minimize power consumption.

 

The maximum rating I can find in the datasheet states:

“Current consumption during active operation with IV sense enabled”

 - fs = 48 kHz, VBAT 4.6 mA

 - fs = 48 kHz, VDD, QFN Package 13.3 mA

 

 In my setup I measure the total increase in consumption compared to pulling the SDZ low.

  - fs = 16 kHz. Normal mode: 31.1 mA

 - fs = 16 kHz. ROM mode: 22.5 mA

 So, even in ROM mode, the consumption is above the value stated in the datasheet.

 

 We have also conducted measurements on the TAS2x63EVM board which shows even higher current draw:

 ROM mode

  •  VBAT: 12.3 mA
  •  VDD: 19.4 mA

 

Normal mode

  •  VBAT: 12.3 mA
  •  VDD: 41.0 mA

In general, when activating the DSP, VDD increases to around 40 mA. We do not measure much difference when enabling/disabling different functionalities in the "Tuning Mode". The current consumption is also not affected by the signal level being played. Only when having "Idle channel Detection" enabled and playing silence, the VDD drops to 14.8 mA - so even lower than in ROM mode.

The text on the two TAS2563 chips are different:

  • TAS2x63EVM: TAS2X63 TI 188 AEYN G4
  • Our board: TAS2X63 TI 448 A48K G3

 

So - the questions :-)

  1. Are there any other "Typical Current Consumption" data available apart from what is listed in the TAS2563 datasheet?
  2. The values listed above from the datasheet, are they with the DSP running?
  3. Any input to the generally much higher current consumption on the TAS2x63EVM board?
  4. Any input on how we can minimize the current consumption in active mode?

 

Best regards,

Ove

  • Hi Ove,

    1. No other data available.
    2. These numbers are in ROM mode, so DSP is not running.
    3. Depending on how and where you measured the current, you may be including the power consumed by other components/circuits on the EVM.
      1. To measure VBAT, you should remove J7 and J15 and power VIN and VBAT separately. Measure current to VBAT J6 only.
    4. Once DSP is being used (Tuning Mode), disabling or enabling features does not affect the overall consumption. VBAT consumption would depend on the output level.

    Regarding your other thread, I assume the difference in consumption was overcome by enabling the idle channel detection feature?

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • Hi Ivan,

    Thank you for this information. I will revisit the measurements on the TAS2x63EVM board to ensure we have followed the steps you describe.

    Concerning my other thread, this is only related to the current consumption in Software Shutdown mode, and I have not seen that this should be affected by Idle Channel Detection...

    Best regards,

    Ove

  • Hi Ove,

    Understood, let us know if the active VBAT consumption is correct after checking your measurement setup.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • Hi Ivan,

    We still measure the same for VBAT active. However, this is most likely because we use a 4 ohm loudspeaker - the values in the datasheet are measured with a 8 ohm load.

    It is however still a mystery why the TAS2x63EVM uses approx. 20 mA more than our own board. But since it is not the other way around, it is currently not of great concern.

    Best regards,

    Ove

  • Hi Ove, 

    are you using a different Inductor value in your system compared to the TAS2x63EVM? a higher inductance with the same saturation current should be providing lower power consumption.

    is the current result OK, Can we close the thread?

    Regards,

    Arthur

  • Hi Arthur,

    We are using the same inductor value compared to the EVM board.

    Yes - thank you - we can close this thread.

    Best regards,

    Ove