CC85XXDK factory reset or paper weight? Maybe bad bebugger.

Konstantin Metelkin

Hello e2e. This is my first post so I'm new to this whole thing. I'll jump straight to my question and issues without waiting much time and ink.

Im using CC85XXDK trying to create a wireless audio system. The EB worked straight out of the box as intended. The "master" and "slave" synced as described in the manual. Next, I decided to connect cc debugger. My pc recognized the debugger and the configurator updated it. When I connected the debugger to my "master" EB the red light does not switch to green meaning that it does not recognize the EB I pressed reset a few times but no change. Also, now my "master" EB is not initializing. The blue led is lit when I power it up but nothing else. As I searched the forum I found a thread that describes similar situation. If I come across it I will attach it. The solution was that it was a bad debugger.

So here are my questions:

Can I factory reset my EB?

Who can I contact to replace the debugger?

over 12 years ago

0 Kristoffer S over 12 years ago

TI__Expert 7160 points

Hi Konstantin,

In order to get a green light in the Debugger it's important to power the EB boards and have the CC85xxEM plugged into the EB. It' also important to have the 10-pin flat cable the correct way on P10 (red wire to the left, towards the blue LED).

-Kristoffer

0 Konstantin Metelkin over 12 years ago in reply to Kristoffer S

Prodigy 70 points

hi Kristoffer. everything you mentioned was done when i first set it up and it worked. however, now one of my EB's is rendered useless. it doesn't initialize the way if should neither with "master" or "slave" CC85xxEM. that's why i need to know if i could reset it to "factory delault".

this is a link to a post that is similar to mine. only thing different now i got a useless EB.

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

0 Kristoffer S over 12 years ago in reply to Konstantin Metelkin

TI__Expert 7160 points

Hi Konstantin,

So the CC Debugger works on one EB, but not the other? We have seen that on some EBs one of the LDOs gets broken. To check whether this is also your problem, can you meassure the voltage on the following signals on P7:

3V3_IO and 3V3_SEC?

Thanks

Kristoffer

0 Konstantin Metelkin over 12 years ago in reply to Kristoffer S

Prodigy 70 points

hi Kristoffer. the CC debugger didn't work. i'm afraid it turned one of my EB's into a paper weight. because the EB it was pluged into doesn't work now. i don't want to risk pluging it into the other EB for that reason. not until i do some research on this issue. I will measure the voltage today. I really need to get it working asap.

Measured the voltage at the points you mentioned. They read 1.7V and 3.3V don't remember which is which that I will post when I get a chance.

0 Kristoffer S over 12 years ago in reply to Konstantin Metelkin

TI__Expert 7160 points

Konstantin,

Meassure these voltages on both EBs please.

Thank you.

0 Konstantin Metelkin over 12 years ago in reply to Kristoffer S

Prodigy 70 points

Finally got time to post. So my findings were. The two EBs I measured call them EB1 the one that works and EB2 the one that doesn't. EB1: 3V3_SEC are both 3.3V EB2: 3V3_IO and 3V3_SEC are 1.7V and 3.3V respectively. When I get a chance i'll plug the debugger into the EB1 and see if it works with it. Maine its a bad EB or I might end up with another paper weight.

0 Kristoffer S over 12 years ago in reply to Konstantin Metelkin

TI__Expert 7160 points

Hi Konstantin,

On EB2 it seems that the LDO creating 3V3_IO (U7) has been damaged (see attached schematic for the EB). To solve your problem remove U7 and solder a wire between testpoints 5 and 7 on P7 to connect 3V3_SEC and 3V3_IO.

-Kristoffer

PurePath_Wireless_AudioEB_1_2_2_Schematic.pdf

0 Konstantin Metelkin over 10 years ago in reply to Kristoffer S

Prodigy 70 points

Thanks Kristoffer that did it. Didn't remove the LDO though. Too tiny for Me to be able to remove.

Audio

Audio forum

CC85XXDK factory reset or paper weight? Maybe bad bebugger.