• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 16 subscribers
  • Views 204 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

ESD performance of CC2531

strongleg strongleg
Intellectual 605 points
Other Parts Discussed in Thread: CC2531, CC2530

i made 5 cc2531 dongle and 4 of them can't be detected by cc debugger.

On these boards, the pin40 dcouple is 1.8V, pin30 rbias is 1.2V, just like normal boards.

it dosen't look like the same problem in: http://e2e.ti.com/support/low_power_rf/f/155/t/128589.aspx#460413 , because my 4 boards can't be work around like   do.

the distributor said cc2531 might be destroyed by ESD.

At the same time, i made 5 cc2530 board, they all good.

i'm wondering is cc2531 so fragile to ESD? Any other possible reason? thanks

  • 0
    TI__Expert 3205 points

    Hi

    One explanation might be long debug connection lines between CC2531 board and cc debugger. I have sometimes experienced that long lines make this connection unreliable. If possible a logic analyzer or oscilloscope screen dump showing activity on debug interface lines might be necessary to further debug this issue.

    Replacing the CC2531 device should reveal if problem is device or board related.

    Tor-Inge

     

     

  • 0 in reply to Tor-inge
    Intellectual 605 points

    I don't think it's the cable problem. this cable works well for cc2530 and other cc2531 boards.

    The bad boards still can't work after i change the cable

    Could cc2531 be destroyed during soldering or by human touch? is there any way to determine whether cc2531 failure because of ESD?

    I have no other cc2531 to replace right now...

  • 0 in reply to strongleg strongleg
    TI__Expert 3205 points

    Using normal ESD protection procedures (wrist strap, ..) you are unlucky if one device is damaged. Four damaged devices out of five are unlikely.

    Monitoring debug interface lines should show if CC2531 is responding to the debugger communication attempt or not. This test should also reveal if the signals are corrupted. If current consumed by CC2531 is outside expected range, it can provide a strategy to isolate problem. Sequentially disconnecting parts of your circuit might reveal an area to focus attention.

    Without knowing any design details, monitoring debug interface, current or replacing chip is what I came up with as debug strategies. I believe signal traces from debug interface to be the most revealing information.

    Tor-Inge