TAS5805M: Automute state behavior...

Hi Ramsey,

Thank you for your reply. It will help for customer and I sent your message to the customer.

But please allow some days to get further related question from customer side.

Regards,
Ernest

Hi Ramsey,

This is Lee Ye-Ri from LG Electronics.

I have a question related to the issue.

I make a patch to read whether the register was written normally when playing sound, and then rewrite register if the value is different.

During the test, the register 0x35 was not written as 0x11, so we rewrote it.

After that, a very loud sound as if distortion occurred in Speaer, when playing sound.

The volume could not be adjusted in the Android UI, and after turning the robot off and on, it returned to normal.

The issue of registers not being written normally occurred 1-2 times of 100,

and we confirmed that the sound was good after rewriting.

However, a very loud sound continued to occur once.

I would like to ask for your opinion on this.

[ 1248.564373 / 08-29 16:00:48.981][1][1585][writer] tas5805m_unmute
[ 1248.581399 / 08-29 16:00:48.998][1][1585][writer] tas5805m read unmute REG_0x0 = 0x0
[ 1248.581592 / 08-29 16:00:48.998][1][1585][writer] tas5805m read unmute REG_0x7f = 0x0
[ 1248.581765 / 08-29 16:00:48.998][1][1585][writer] tas5805m read unmute REG_0x3 = 0x3
[ 1248.581951 / 08-29 16:00:48.998][1][1585][writer] tas5805m read unmute REG_0x35 = 0x0
-> When playing sound(unmute), the 0x35 register was written as 0x11, but read as 0x0
[ 1248.581974 / 08-29 16:00:48.998][1][1585][writer] tas5805m rewrite REG_0x35
-> the 0x35 register is rewritten
[ 1248.582251 / 08-29 16:00:48.999][1][1585][writer] tas5805m read unmute REG_0x0 = 0x0
[ 1248.582438 / 08-29 16:00:48.999][1][1585][writer] tas5805m read unm ute REG_0x7f = 0x0
[ 1248.582603 / 08-29 16:00:48.999][1][1585][writer] tas5805m read unmute REG_0x3 = 0x3
[ 1248.582764 / 08-29 16:00:48.999][1][1585][writer] tas5805m read unmute REG_0x35 = 0x11
-> the 0x35 register is normal (0x11)

Regards,

Yeri Lee.

Hi Yeri,

I would recommend disabling the auto mute feature and seeing if the issue persists. Other debug steps could be reading the digital volume and analog gain of the device as well as looking at the output and seeing the shape of the wave form. This can help determine if the characteristics of the problem. The error could be not going to the correct book/page at some point in the controlling of the device. Is register 0x35 read as 0x00 on startup, during play, or at some other time?

Regards,

Ramsey

Hi Ramsey,

When playback starts, register 0x35 is written as 0x11, and when read immediately, the value is 0.

The register below is written when playback starts and ends, and book/page is written every time.

The digital volume and analog gain once at boot time and are not written again.

REG_0x00 = 0x00 //PAGE
REG_0x7F = 0x00 //BOOK
REG_0x00 = 0x00 //PAGE
REG_0x03 = 0x03 //CTRL_2 : Normal volume, ctrl state : play
REG_0x35 = 0x11 //SAP_CTRL3 :data path L&R
<start>

REG_0x00 = 0x00
REG_0x7F = 0x00
REG_0x00 = 0x00
REG_0x03 = 0x0b // Mute on, ctrl state : play
REG_0x35 = 0x00 // zero data(mute)
<end>

The issue occurred where sound started but could not be heard,

I read the registers and found that 0x03 or 0x35 register was not written.

And when 0x35 register was not written, 0x69 was also triggered.

I don't know what the cause is, so I added a part that reads the register after writing.

If the value is different when read, it is written again.

Regards,

Yeri Lee.

Hi Yeri,

When sound was started but not heard, how long was there before the sound started? Can you also read registers 0x70, 0x71, 0x72, and 0x73 when the issue occurs?

Regards,

Ramsey