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.

TAS6424-Q1: TAS6424-Q1

Part Number: TAS6424-Q1
Other Parts Discussed in Thread: TAS6424

Hello,

I'm starting to configuere TAS6424-Q1 by I2C.

Could you please, tell me, if there is a prefered  start up sequence for setting all needed registers?

I'm using a PIC microcontroller.

Best Regards

Brenno Diegoli

  • Hi Brenno,

    Thank you for reaching out to us. I am currently looking into this and will let you know of any preferred startup sequence as soon as possible.

    Are you using an EVM or your own board for your current setup?

    Thank you,

    Brian Angiel

  • Hi Brian,
    many thanks for your quick replay.
    I'm using my own board and my micro is a microchip pic.

    Best Regards

    Brenno

    Il 08/03/2017 14:55, Brian Angiel ha scritto:

     

    A Message from the TI E2E™ Community

     

    Brian Angiel replied to TAS6424-Q1: TAS6424-Q1.

    Hi Brenno,

    Thank you for reaching out to us. I am currently looking into this and will let you know of any preferred startup sequence as soon as possible.

    Are you using an EVM or your own board for your current setup?

    Thank you,

    Brian Angiel

     

     

    You received this notification because you subscribed to the forum.  To unsubscribe from only this thread, go here.

    Flag this post as spam/abuse.



    --
      Brenno Diegoli K-array

    K-array

    Brenno Diegoli
    R&D
    brenno.diegoli@k-array.com


    srl Unipersonale

    Ph  +39 0558487222
    Fax  +39 0558487238

    Via Paolina Romagnoli 17
    50037 - San Piero a Sieve
    Firenze - Italia
    info@k-array.com

    www.k-array.com

  • Hello,

    did you find a prefered strart-up sequence for TAS6424_Q1?

    Best Regards

    Brenno

  • Hi Brenno,

     

    I apologize for the delay in my response. Thank you for your patience.

     

    There is no particular start-up sequence for TAS6424-Q1. I will however provide a list of I2C reads/writes that I perform whenever working with the device.

     

    Format:

    W (ADDR) (REG) (VAL)

    R (ADDR) (REG) (BYTES)

     

    w D4 00 80  // this clears the registers

    w D4 21 80  // this clears all faults

    r D4 10 04  // read faults and verify that all registers are 0x00

     

    Following these commands, I write to any other registers that need editing based on the application (I set my gain, I turn on whichever channel(s) I am testing, etc.). Then I perform one final read on the FAULT registers. After that, the device should be good to go!

     

    Regards,

    Brian Angiel

  • Hi brian,

    many thanks for your replay.

    I followed your instructions and I read the same value from #0x10 reg.

    But no pwm is present on any output !

    What do you think about?

    Regards

    Brenno

  • Hi Brian,
    I'm reading at 0x13 register the value of 0xCF, it means:
    bits [7:6] 1 1 reserved
    bit [5] 0 No VDD POR has occurred
    bit [4] 0: No global overtemperature warning

    bit [3] 1: Overtemperature warning on channel 1
    bit [2] 1: Overtemperature warning on channel 2
    bit [1] 1: Overtemperature warning on channel 3
    bit [0] 1: Overtemperature warning on channel 4

    How it's possible? No global overtemperature warning and Overtemperature warning on each channel ?

    No pwm runs on outputs!
    What do you think about?
    Regards
    Brenno
  • Hi Brenno,

    If you clear the FAULTS and WARNS (w D4 21 80), do the OTW(i) (channel-dependent over-temperature) warnings immediately reappear? I would not expect the device to stay in HI-Z mode unless the OTSD(i) (channel-dependent over temperature shutdown) fault was triggered. But you're reading 0x00 on register 0x12, correct?

    What value do you have written to register 0x01? Bits d6-5 control the OTW(i) settings.

    And what value do you have written to register 0x04?

    Any information you could provide regarding your application/setup would be helpful in debugging this issue (schematics, layouts, power levels, load values, etc). Could you also tell me where you are probing the outputs and not seeing the PWM?

    Regards,

    Brian Angiel

  • Hi Brian, many thank for your replay.
    I cleared FAULTS and WARNS (w D4 21 80) and immediatly I read (r D4 13 CF) and WARN pin (27) goes low.
    Yes (r D4 12 00)
    I wrote (w D4 01 32) Temp limit =130°
    My chip now is cool because no loads are connected to outputs.
    As shown in datasheet I wrote (w D4 04 55) All Chs in Hi-Z but at the end of the setting up the registers, I wrote (w D4 04 00),all Chs play.
    I'm working at 96KHz fs, so I wrote (w D4 03 84) but after reading it the new value is (r D4 03 62)! It seems not to accept 96KHz bu only 48KHz
    I'm probing the the outputs on each output inductor, where I'm expecting to see the PWM.

    If by my micro set low STANDBY\ pin, WARN\ pin goes high, may be correct.

    I'm usigng TAS6424-Q1 for driving CH1-CH2 in PBTL mode, CH3 and CH4 in BTL mode.
    Where can I send you my schematics?

    Hoping this could help you.
    Regards
    Brenno
  • Hi Brian
    another strange behaviour is the following.
    After (w D4 04 00), all CHs play, when I read (r D4 0F 20) --> All CHs play except CH2, that is muted!

    Bye
    Brenno
  • Hi Brian,
    I found that 3.3V (Vdd) and GND I have a resistance of only 45ohms!
    I insulated the TAS6424-Q1 pin 19 and there is 45ohms between pin 19 and gnd.
    Is it the problem?
    Should I change the TAS?

    Bye
    Brenno
  • Hi Brenno,

    I sent you an E2E connection request, so you can send me your schematic privately.

    In order to begin using the device in PBTL, please follow the process below:

    1. Set all channels to Hi-Z (w D4 04 55)
    2. Place the device in STANDBY
    3. Set the appropriate channels to PBTL
      1. With Ch3-4 in BTL and Ch1-2 in PBTL - w D4 00 10
    4. Take the device out of STANDBY
    5. Set channels to PLAY - w D4 04 00

    That should allow the device to successfully run in PBTL mode.

    I'm still perplexed by your problems with the 96kHz I2C write and the OTW(i) readings. But let's see if this process can at least get all of your outputs running.

    What are your other clock frequencies, besides fs?

    Regards,

    Brian Angiel

  • Hi Brenno,

    I didn't see your last post about VDD until I had already replied.

    Do you have another board that you could work with and measure PVDD-GND, VBAT-GND, and VDD-GND resistances? You should be seeing a resistance on the order of Meg-ohms between the supply pins and GND. If there is a short present on the board you are currently using, it's possible that the device could have been damaged by the short.

    And regarding the 96kHz fs, have you tried getting one channel to operate at a time? Is it possible that you are running into current limits with the power supply you are using? Faster switching frequencies require higher currents and using only one channel at a time would lessen the current drawn to allow you to see if that is, in fact, a problem.

    Regards,

    Brian Angiel