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.

TAS2560: ASI CLK error1 and Brownout error

Part Number: TAS2560
Other Parts Discussed in Thread: , TAS2555

Our customer is using TAS2560 with Snapdragon, MCK input is 9.6MHz, Fs is 48KHz and register setting is following.

Power supply is 5V adopter which is included in EVM box.

 

At 1st time music playback works well, after that BCK and WCLK are stopped from DSP then second trial of playback, sound does not come out even BCK and WCLK are present.

"Power Up Control 2" showed 0x05=1, PWR_ERR is detected.

"Interrupt Detected 1 Field Descriptions" showed 0x26=2a. It is ASI CLK error1, Brownout error and SAR complete error.

Because of BCK and WCLK are stopped.

 

Here are questions.

1.To recover this condition, should we assert soft reset and reload all of register when move to playback everytime?

We had tried "CLK_ERR_1 Register" 0x21 to 82, It will "Reload defaults on restart",but not improved.

 

2.What is threshold voltage value to detect PWR_ERR and Brownout? How can we ignore those flags?

0x04 Class G or H setting did not make difference.

 

Regards,

Mochizuki

 

 

R B[0]P[0]R[0]=0x0

R B[0]P[0]R[1]=0x0

R B[0]P[0]R[2]=0x1

R B[0]P[0]R[3]=0x20

R B[0]P[0]R[4]=0x7

R B[0]P[0]R[5]=0x0

R B[0]P[0]R[6]=0x0

R B[0]P[0]R[7]=0x40

R B[0]P[0]R[8]=0x81

R B[0]P[0]R[9]=0x83

R B[0]P[0]R[a]=0x2

R B[0]P[0]R[b]=0x0

R B[0]P[0]R[c]=0x0

R B[0]P[0]R[d]=0x8

R B[0]P[0]R[e]=0x10

R B[0]P[0]R[f]=0x41

R B[0]P[0]R[10]=0x5

R B[0]P[0]R[11]=0x0

R B[0]P[0]R[12]=0xc

R B[0]P[0]R[13]=0xb

R B[0]P[0]R[14]=0x0

R B[0]P[0]R[15]=0x2

R B[0]P[0]R[16]=0x0

R B[0]P[0]R[17]=0x0

R B[0]P[0]R[18]=0x0

R B[0]P[0]R[19]=0x0

R B[0]P[0]R[1a]=0x1

R B[0]P[0]R[1b]=0x40

R B[0]P[0]R[1c]=0x0

R B[0]P[0]R[1d]=0x8

R B[0]P[0]R[1e]=0x8

R B[0]P[0]R[1f]=0x0

R B[0]P[0]R[20]=0x0

R B[0]P[0]R[21]=0x02

R B[0]P[0]R[22]=0x3f

R B[0]P[0]R[23]=0x21

R B[0]P[0]R[24]=0x0

R B[0]P[0]R[25]=0x0

R B[0]P[0]R[26]=0x2

R B[0]P[0]R[27]=0x3

R B[0]P[0]R[28]=0x0

R B[0]P[0]R[29]=0x0

R B[0]P[0]R[2a]=0xf0

R B[0]P[0]R[2b]=0x32

R B[0]P[0]R[2c]=0x3

R B[0]P[0]R[2d]=0xd7

R B[0]P[0]R[2e]=0xc0

R B[0]P[0]R[2f]=0x3d

R B[0]P[0]R[30]=0x0

R B[0]P[0]R[31]=0x11

R B[0]P[0]R[32]=0x4

R B[0]P[0]R[33]=0x44

R B[0]P[0]R[34]=0x4

R B[0]P[0]R[35]=0x0

R B[0]P[0]R[36]=0x2

R B[0]P[0]R[37]=0x10

R B[0]P[0]R[38]=0x0

R B[0]P[0]R[39]=0x0

R B[0]P[0]R[3a]=0x0

R B[0]P[0]R[3b]=0x20

R B[0]P[0]R[3c]=0x30

R B[0]P[0]R[3d]=0xa

R B[0]P[0]R[3e]=0x0

R B[0]P[0]R[3f]=0x0

R B[0]P[0]R[40]=0x0

R B[0]P[0]R[41]=0x0

R B[0]P[0]R[42]=0x0

R B[0]P[0]R[43]=0x0

R B[0]P[0]R[44]=0x0

R B[0]P[0]R[45]=0x0

R B[0]P[0]R[46]=0x0

R B[0]P[0]R[47]=0x0

R B[0]P[0]R[48]=0x5

R B[0]P[0]R[49]=0x0

R B[0]P[0]R[4a]=0x0

R B[0]P[0]R[4b]=0x2

R B[0]P[0]R[4c]=0x13

R B[0]P[0]R[4d]=0x0

R B[0]P[0]R[4e]=0x0

R B[0]P[0]R[4f]=0x0

R B[0]P[0]R[50]=0x21

R B[0]P[0]R[51]=0x0

R B[0]P[0]R[52]=0x0

R B[0]P[0]R[53]=0x0

R B[0]P[0]R[54]=0x8c

R B[0]P[0]R[55]=0x3

R B[0]P[0]R[56]=0x1

R B[0]P[0]R[57]=0x0

R B[0]P[0]R[58]=0x3

R B[0]P[0]R[59]=0x6

R B[0]P[0]R[5a]=0x7

R B[0]P[0]R[5b]=0x81

R B[0]P[0]R[5c]=0x0

R B[0]P[0]R[5d]=0x80

R B[0]P[0]R[5e]=0x0

R B[0]P[0]R[5f]=0x0

R B[0]P[0]R[60]=0x0

R B[0]P[0]R[61]=0x0

R B[0]P[0]R[62]=0x0

R B[0]P[0]R[63]=0x0

R B[0]P[0]R[64]=0x0

R B[0]P[0]R[65]=0x0

R B[0]P[0]R[66]=0x0

R B[0]P[0]R[67]=0x0

R B[0]P[0]R[68]=0x0

R B[0]P[0]R[69]=0x0

R B[0]P[0]R[6a]=0x0

R B[0]P[0]R[6b]=0x0

R B[0]P[0]R[6c]=0x0

R B[0]P[0]R[6d]=0x0

R B[0]P[0]R[6e]=0x0

R B[0]P[0]R[6f]=0x0

R B[0]P[0]R[70]=0x0

R B[0]P[0]R[71]=0x0

R B[0]P[0]R[72]=0x0

R B[0]P[0]R[73]=0x0

R B[0]P[0]R[74]=0x0

R B[0]P[0]R[75]=0x0

R B[0]P[0]R[76]=0x0

R B[0]P[0]R[77]=0x0

R B[0]P[0]R[78]=0x0

R B[0]P[0]R[79]=0x60

R B[0]P[0]R[7a]=0x0

R B[0]P[0]R[7b]=0x0

R B[0]P[0]R[7c]=0x7

R B[0]P[0]R[7d]=0x0

R B[0]P[0]R[7e]=0x84

R B[0]P[0]R[7f]=0x0

  • Hi Mochizuki-san,

    You could try the sequence explained in the data sheet, section 9.3.16.4

    The minimum brownout voltage is 2.7V, although PWR_ERR is set if a clock error event happens.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators

  • Hi Ivan,

    ASI error:
    Is this correct understanding? If disturb BCK or LRCK input clock when change music file, TAS2560 will detect ASI error then system controller detect and clear INT_CLK1 flag and reload register setting.
    It is not like PCM510x audio DAC automatic input BCK and LRCK clock detection and automatic PLL setting without any system controller assistance.

    Brownout flag:
    Our customer had used Android driver from git.ti.com/.../tas2560-android-driver as a reference.
    And applied some customization, what is "Battery Guard AGC" setting at this android driver? We cannot find register description on the datasheet.
    It seems this setting is not optimal that why Brownout flag is present at very low level playback even 5V 2A DC adopter is used.
    What is your recommended Battery Guard AGC resistor setting?
    We did not expect to use PPC3 register dump function for no processing I2S D-amp, is it impossible to complete SW development?

    Regards,
    Mochizuki
  • Mochizuki-san,

    ASI error: The recovering from clock error is not automatic, the system should follow the sequence explained above to recover from a clocking error event.

    Brownout flag: Battery Guard AGC is explained in data sheet section 9.3.14 (The sections has the same name). As explained in this document, the parameters for the Battery Tracking AGC are part of the DSP core and can be set using the PurePath ™ Console 3 Software TAS2560 Application software for the TAS2560 part under the Device Control Tab.

    Best regards,

    -Ivan Salazar

    Applications Engineer - Low Power Audio & Actuators

  • Hi Ivan,
    Thank you for prompt reply.

    I get you, we have seen several projects just want to use simple boosted I2S D-amp from 3.3V battery to produce 5W output power without complicate register setting like A-in D-amp TPA20xx family. Hope to see ROM mask version of TAS2560.

    I understood, Brownout setting could not complete by using uploaded Android driver and datasheet register map description, we will order TAS2560EVM for our Lab to duplicate the customer situation and find out optimal Brownout setting on PPC3 GUI.
    Keep you updated.

    Regards,
    Mochizuki
  • Hello Ivan,

     

    I have got TAS2560EVM and run it on PPC3.

    How can we dump register header file, like TAS2555 PPC3 function?

     

    Regards,

    Mochizuki

  • Hi Mochizuki-san,

    Currently there is no End System Integration tool for TAS2560. We'll work on this and I can contact you when there is further information about this.
    But another option that you can implement right now is to use PPC3 to configure Audio Mode (ROM Mode 1 or 2) and AGC and then use the I2C tool embedded in PPC3 to record the register writes for your specific configuration. You just need to click the record button on I2C tool and then click on Apply Changes in Device Control panel from PPC3.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators

  • Hi Ivan,

    Finally I could capture all of EVM initialization setting via I2C.

    There are several hidden register need to initialize, it’s in red color fount in attached file.

    How our customer can determine those register value on initialization file?

    Just copy I2C transaction for EVM is good enough?

    Regards,

    MochizukiTAS2560EVM initalization.xlsx

  • Hi Mochizuki-san,

    Yes, I think that copying the I2C transaction should be enough for device initialization.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators
  • Ivan-san,

    Thank you for the confirmation.
    At this time I will close this thread.

    Regards,
    Mochizuki