We inherited a CC8520 wireless speaker design, Purepath Configurator 1.4.1.38034, and shortly after our client started shipping products we got complaints about the volume up and changing itself randomly. In the receiver, the CC8520 talks to a TAS5717 audio amplifier via I2C, and by monitoring the I2C with an Aardvark tool when the malfunction occurs, we capture I2C transactions that are the same as a device power-up, or a reset, with one exception: the headphone/speaker register 05 in the TAS5717 is set to headphone, then to speaker the next command. When the receiver is reset or powered up, it only writes to register 05 once, with the headphone bit cleared (speaker mode).
This error occurred 9 times over this last weekend at my home, with the volume set to -40dB, and when it occurs it resets to -16dB, our default volume. I monitored the 3.3V supply and the reset input to the CC8520 with a scope on single sweep, trigger set on 2.8V, and no triggers were observed.
On the top of page 29 of swru250l.pdf, the CC8520 Family Users Guide, it talks about 'system resets'. This is what seems to be occuring, however there is no I2C error that is causing it. I could not find any reference to a error status register or such in the CC8520 to try and figure it out.
We tried pulling the crystal in the transmitter, input a sine wave from a rf signal generator, and took it out of spec, over the 50 ppm accuracy for the frequency. The audio dropped out, and then the lock led, but when restored to frequency the lock and audio just returned. When we cycle power on the transmitter, the receiver sends 03ff mute commands, and then restores the existing volume to the TAS5717.
Suggestions? Our client's production shipping is stalled now due to this. Thanks, Jim