CC8531 + AIC34 -- 4 microphone operation

Hi Winnefred, 

With regards to item 1 then this can be easily fixed setting hardware platform to 'Custom Design' instead of 'PurePath Wireless EB' for the master receiver configuration.

For item 2. Have you enabled power toggle button in the Power Management panel?

Regards,

Kjetil 

Dear Kjetil,

Thank you for your answer,

1. I will work on the answer provided by you for question 1 and come back.

2. regarding the power toggle button, - Yes, I have enabled the power toggle button functionality in the power management panel and flashed the cc8531 with this functionality (ie, Holding power button should power on), but when i hold i could see the clock is generating through the crystal, when i release the button the clock dies.

I changed the power button functionality from HOLD to CLICK through IO mapping and tried again. Result is again the same.

Is there any background code which is malfunctioning ?

let me know.

Regards,

Winnefred

Best regards,

Winnefred K

Hi Winnefred, 

With regards to item 2, it might be that this post reveals what might be going wrong:
http://e2e.ti.com/support/low_power_rf/f/382/p/265566/942099.aspx

Remember to force the MOSI high while driving CSn in order to not enter boot loader (you can see the MOSI signal as the one with 2V per div in the picture below).

Can't think of anything else and will have to consult some of the developers if this does not solve the issue,.

Regards,
Kjetil 

Hi Kjetil,

The above solution does not solve my problem,

Herewith i have attached the circuit and the SW ppwconfig that i am configuring for.

Please have a four eye review on the same and let me know if i have to make any hardware changes to make it work.

After your suggestion, I have configured and tested the board, still the problem exists.

I could not see the LED blinking, I could not see any voltage at the RF_N and RF_P pins,

but the clock signal is running ( since i have disabled the power button config, if i enable the power button config to CSN - the clock dies out soon after i release the button, ie - when the CSN is pulled to ground - clock generates, soon after the button is released -- CSN open -- clock dies)

It would be really helpful if you could contact some developers and get my issue solved.

Probably, if we have to take this discussion private, i am also willing to do the same. may be a telecon & webex with a developer would suffice our need.

Kindly let me know your feasibility.

Best regards,

Winnefred

Hi Winnefred,

You have not enabled the power toggle button. You only have a pairing button. These are not the same. Pairing button is for pairing a master to a slave. Please see the picture below for how to enable a power toggle button.

That being said, if you have no power toggle button the device should be automatically turned on when applying power, and then you should see some activity on the status LED on GIO12. Since you are not seeing this I guess that there is some problems with the I2C interface, i.e. CC85xx does not get ack from the aic and then it is continuously reset for retry. What if you select DSP instead of AIC34 in your Audio Interface panel? Do you see the LED blinking then?

Best regards

Kristoffer

Hi Kristoffer,

Good to hear from you again.

I have enabled the power toggle button, with AIC34 connected and checked the led at GIO12 but no network LED

again as you suggested i have selected the DSP and reflashed the CC8531, now the LED is blinking.

As you have mentioned, there should be a problem with I2C. In the hardware we have identified one problem that is,  the WCLK of CC8531 is connected to WCLKB of AIC34 and not connected to WCLKA of AIC34. would this be a the root cause of the problem ?

Let me know your suggestions over the same.

I will check in lab for the I2C part and let you know the details.

Thanks,

Best regards,

Winnefred K

Hi Kristoffer,

Good Morning,

In AIC34,  i would like to use the GPIO1_A(J2) as the WCLK_A, could this be done through the CC8531 programming code you have provided above ?

If possible please send me a new code that invokes GPIO1_A as WCLK_A in AIC34.

Thank you,

Best regards,

Winnefred K

Hi Kristoffer,

Good evening,

Today we checked the board again, after replacing AIC34, Now the LED seems to be glowing, but not sure why the battery is getting drained too quick,

also, the clock signals and RF_N and RF_P signals seems to be strange. I have tapped the SCL and SDA data lines also.

Attached are the signals tapped from scope. (pls lgnore the label names).

Could you please check the attachment and let me know your inputs.

Thanks,

Hi Winnefred,

Your RF_N/P signals look somewhat strange, and if you have the same volts per div on both scope channels in your XTAL meassurements they look strange as well. Are you using the same crystal as in the TI ref design? If you have a DK laying around you could swap the crystals as a test. Your I2C signals look normal.

-Kristoffer

Hi Kristoffer,

Yes, I am using the same crystam as in the TI reference design. If i configure CC8531 to DSP and check the clock signals, it appears normal. I believe then its not the XTAL problem.

How about at low voltage conditions, how does the CC8531 behave ?

I noticed that the Network LED started to glow @ 50% duty cycle, when i connect the battery and USB together.

where as If i connect only battery, network LED is glowing at 25% dutycycle (normal) but if allow it to operate in this state, the battery is getting drained drastically.

If i connect only USB, network LED stays 100%

and in all these conditions, the glow of network LED is not bright.

Hi Kristoffer,

When does the CC8531 enter into standby mode ?

I checked the XTAL signal at lab today, i found it is okay now.

RF_P and RF_N signal remains the same(strange). Do you have any reference signal screenshots available for the RF_P and RF_N @ CC8531 before pairing ?

Let me know.

Hi Winnefred,

What do you mean by:
How about at low voltage conditions, how does the CC8531 behave ?

The fact that the status LED (connected to pin 34 on your CC85xx) is blinking differently depending on how you power your boards really doesn't make sense to me. What if you press the pairing button? Do you then enter pairing state (double blink)? And are you able to program your CC85xx when only the battery is connected?

Are you using the status LED configuration shown in the first picture below? Then you should never see 25% duty cycle on the LED. You should either see:
-1 fast blink per second (2% duty cycle) for ALONE
-1 long blink per second (50% duty cycle) for STANDBY
-Constantly lit (paired)
-2 fast blinks per second for PAIRING state.

The standby state could be entered in numerous cases, but if you are using the config provided in 4Mic.zip you should never be able to enter the standby state...

I have provided some pictures of normal RF_N/P behaviour as well

RF_N/P for a slave in ALONE state:

RF_N/P for a slave in ACTIVE state (joined to a master):

Best regards

Kristoffer

Hi Kristoffer,

Thank you for the pictures,

With only battery connected to the board, I could see the network status LED blinking in the alone pattern ( 1 short blink per second ) but for few seconds only ( say 30 seconds )

within this period, if i press the pairing button, the network LED changes its blinking pattern to pairing mode ( 2 fast blinks per second ) but again its for few seconds only ( say 30 seconds )

After that ( say after 30 seconds ) the network LED is lit constantly, for both conditions above.

Yes, I am able to do the flashing with only battery connected.

The fact i asked you the question regarding the standby stage is, when the battery and usb are connected (i.e Charging condition) the network led blinks fastly ( eg :-  2, 3, 2, 3, 2, 3, 2, 3 etc. / 1sec) and continuosly.

Hi Winnefred,

The fact that the LED pattern changes depending on power connections (battery or USB or both) indicates that you have some issue with the powering of either the AIC or the CC8520 or still problems with the I2C interface (I guess it is the last one). If the I2C connection is not ok the CC85xx will reset itself and try again, and if the I2C is bad all the time you will see repetative fast restting of the CC8520 which will turn on and off the LED equally quickly. If you change back to DSP config (not AIC34) I bet that the LED will not be dependant on power connection anymore...

-Kristoffer

Hi Kristoffer,

You were right, I2C was interfacing was the problem & i rectified it, In one of my other board, there seems to be another strange LED pattern, I could program the master and slave very well. Without pairing both master and slave seems to be normal  when paired the master network LED gives one fast blink and one long blink and this is getting repeated, In the slave i could see the same pattern in the pairing led.

Could you help me to solve over this issue ?

Thanks,

-Winnefred

Hi Winnefred,

Can you provide your ppwcfg files?

-Kristoffer

Hi Kristoffer,

Thanks for your quick reply.

I have attached the PPWCFG files which i am using for flashing cc8531.

Also, as per your previous solution, i have tried to select the DSP instead of AIC34 and do the pairing with slave.

This time, the behaviour is as expected, its normal (both master and slave LED becomes stable).

I have also checked the reset line to see if its a I2C failure but to my surprise the reset is also stable !

0333.4mic Config SW.zip

Hi Kristoffer,

Do you have any suggestions over this error ?

Hi Winnefred,

Seems to be some issues with this thread. The sequence of post gets altered (at least in my browser) and I am no longer sure which problems is fixed and which problems that are still valid. Could you please start a completely new thread where you describe your current issues? Sorry for this. Are you by the way using the CC85XXDK with the AIC34 kit attached on the master side and the CC85XXDK-headset at the slave side?

-Kristoffer

Hi Kristoffer,

Okay, I will start a new thread,

I am using a custom board for the Master side with CC8531 and AIC34 integrated together.

and for the slave i use the CC85XXDK-Headset to pair with master.

Rest details we shall continue in the below thread link attached.

http://e2e.ti.com/support/low_power_rf/f/382/t/295162.aspx

Thank you.

- Winnefred