[CC8520+AIC3204] Weird problem of using ONE button for 'Power Control' and 'Volume Mute'.

Ji Jason,

Lower the "Maximum hold time" for "Click" functionality. You do this by enabling Custom setup for Button timing in the User Interface panel, and then adjust the arrow buttons (see picture below). The default is 100x10ms = 1 second, meaning that you can hold the button for 999 ms and it will still be registered as a click. If you hold it longer than one second it will not be a click. So what is happening is this:

You hold the button to power on. When the device powers on a new timer starts, and if you release the CSN before it has gone 1 second it will be registered as a click, and then you get a mute. If you lower the Maximum hold time for click to for example 20x10 ms = 200 ms you will have to release the button within 200 ms after the device has powered up. For a human being I would say it's difficult to react this fast. Try it out :)

Best regards

Kristoffer

Kristoffer,

Thank you so much. I've just tried and it works fine by lowering the "Maximum hold time" for "Click" as you said!

But there are still two questions left:

1. A lower maximum hold time can avoid unexpected muting at power on, but it also affects other buttons' behavior, eg. it requires a faster "click" action for volume control. This may brings on some "click-missing". Is it possible to modify just one certain button?

2. In the preloaded demo, the CSN pin is used for Network Paring by "Click" action, with "Maximum hold time" default setting of 100x10ms. But I never saw any unexpected paring occured. What is different?

Jason Wu,

1. Yes it will affect all the buttons that is assigned with C (click). That being said, you should click pretty slow to hold the button for more than 200 ms.

2. I talked to the firmware team, and there is actually a bug here. So thanks for reporting. Pairing and mute toggle is implemented differently. Ideally all the functionalities should behave like pairing does, and this will be implemented in the next firmware release.

One advise though: Why do you need a mute in the first place? If you only have a power toggle button and you assign it as click you will achieve both muting AND power saving in one click. It's also better from an operator point of view because the operator could be uncertain whether he really turned the mic off or whether he just muted it.

Best regards

Kristoffer

Kristoffer,

I hope the bug will be fixed later.

Actually, I need the Mute and Power-toggle to assign to different button actions. In my design, the CC8520 runs in autonomous mode, and I need the local MICPGA and Headphone Amplifier keep running for local headphone output, even when muting the remote master's output (by muting the local ADC's output).

So if I mute the slave by power down, I cannot get the headphone output.