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.

CC8531 + AIC34 - Strange Network LED status indication

Other Parts Discussed in Thread: CC8531

Hi Kristoffer,

I have attached the schematics the schematics of the AIC34 and CC8531 integrated for 4 microphone operation.

The Problem with present configuration is that.

1. I am able to program the CC8531 through purepath configurator.

2. As soon as the programming is completed, the network status LED starts to blink(Alone LED pattern).

3. In both Master and Slave CSN button is clicked to pair after this - Active LED pattern should occur, but instead we are receiving a different LED pattern, which is shown in the attachment image.

Steps taken so far,

1. Programmed CC8531 with "DSP" selected as CODEC and checked the LED and pairing  -  Test success ( Active LED indication occurs.

2. Programmed CC8531 with AIC34 selected as CODEC and this time integrated AIC34DK through I2C lines instead of our on board AIC34 IC and checked the LED status while pairing - Test success ( Active LED indication occurs )

Ruled out so far,

1. with the above steps we have confirmed that CC8531 is not the problem creator.

2. with oscilloscope reading we could find that the MCLK, BCLK and WCLK signals are not as espected.

3. RESET Line seems to be okay 

Problem:

1. Unexpected LED indication.

2. we have removed and replaced the AIC34 asic for almost 8 times, but same unexpected LED indication !

Solution required to solve the above issues.

Hope the issues were clear and understandable now :)

expecting your support towards this issue.

Thanks & regards,

Winnefred K

  • Hi Winnefred,

    That pattern looks very similar to the pairing pattern (shown in the first figure below), only inverted..

    Just to rule out that it's not, try changing the pairing pattern to for example this:

    Does this change the LED behaviour?

    I find it a bit strange that you are actually able to see the ALONE pattern, because this means that the I2C interface is working as it should, and that doesn't add up to the fact that changing to DSP makes it all work. If you had some I2C errors you should not have been able to reach the ALONE state... Try changing the ALONE pattern to this:

    Are you able to see the solid LED in the ALONE state now?

    -Kristoffer

  • Hi Kristoffer,

    I have tried your suggestions with the configuration of AIC34 and DSP as well,

    1. with AIC34 configured - for network status LED, Alone LED pattern is not continuously glowing, instead it provides an output with short turnoff (see attachment)

    - During pairing -> It provides a 50% turn off and 50% turn on.

    ( Note : Even @ slave board the same network LED pattern occurs during pairing )

    2. with DSP configured -  everything seems normal - Alone LED pattern is as configured (100% turn on)

    - During pairing -> it provides three short pulses as configured.

    Any suggestions ?

  • Winnefred,

    Are you saying that the slave board (which is a headset board using the aic3204) shows a 50% ON, 50% OFF blinking pattern when you press the pairing button on this headset? Even though it is not configured with such a pairing pattern in the configurator?

    -Kristoffer

  • Hi Kristoffer,

    When i try to pair the slave with the master, The network LED in Master seems to go strange & in the slave board also its showing a pattern which is not configured ( instead of 100% Active LED, it shows a short pulse continued with a long pulse eg:-(2, 16, 82, 0) ).

    But this happens only when i try to configure it with AIC34 , if i configure it as DSP, Slave pairs with master as it should happen.

    Also, i have tried to pair the slave with CC85XX-DK, it has no problem with pairing.

    The Slave LED ir-regularity is just a symptom that i have mentioned, thinking that it could help you to figure me out of this problem.

  • Hi Kristoffer,

    To be precise, Yes, the slave board is showing a pattern which is not configured.

    But the problem is not in the slave for sure, since i have tried this with other Design Kits of TI. It works well.

  • Hi Winnefred,

    I believe what we are seeing is not the paring process acting strange. The slave is actually paired to the master and when the master is repeatedly resetting itself this shows up on the slave LED as well since the network is constantly enabled and disabled and the slave joins and looses connecion, joins and looses connection... So there are still I2C errors on the master which is causing this. Do you by any chance have the ability to look at the I2C trafic on a logic analyser or a scope?

    -Kristoffer

  • Hi Kristoffer,

    I could tap the signals through oscilloscope, i will send you the pictures of I2C signals asap.

  • Hi,

    i received my CC85XX-DK on Monday and am having the same Problem with one of the Wireless EBs. The CC8531 seems to be fine, i can put it on the working board and everthing functions properly.

    Has there be a solution to this problem?

  • I have just measured 3V3_IO and 3V3_SEC. On the working board 3V3_IO is 5V and 3V3_SEC is 3.3V, on the other board 3V3_IO is 4.5V with heavy spikes and 3V3_SEC is 3.3V. My WirelessEB is Version 1.2 but does not fit to schematics (Version 1.2.2). E.g. resistors R38 and R54 (Power supply to CC8531) are not assembled.