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.

CC Debugger not resetting correctly with CC2531EMK

Other Parts Discussed in Thread: CC2531, CC2531EMK

I am having a problem with the CC Debugger and the CC2531 SOC device. So that you can better understand the problem, I have to provide some background, so bear with me. I also made a video of myself demonstrating the issue. It can be seen here: http://www.youtube.com/watch?v=DxKWh0Qg7VY

I took the CC2531 EMK dongle design provided by TI (http://focus.ti.com/docs/toolsw/folders/print/cc2531usb-rd.html) and sent it to my own manufacturer. When the manufacturer completed the devices, I compared it with a CC2531EMK dongle that I purchased directly from TI. The two were basically identical, except for some different markings on top of the CC2531 chip itself. On the top of the dongle provided by TI, it says:

CC2531
F256
TI 09J
PLKY

On the device that we manufactured on our own, it says:

CC2531
F256
TI 0AJ
P9LJ

There is also some differences in the way the text itself is applied. On the dongle provided by TI, it appears to be etched and is very faint, but on the devices we manufactured, the text is more readable, but appears to be stamped with ink instead of etched.

Now, everything about the devices that we manufactured appear to be working correctly except for one issue. When I plug our devices into the CC debugger, I never get the green status LED to light up, and when I try to load some firmware from IAR, it won't load.

I did find a workaround, however. If I take the dongle provided by TI, plug it into the CC debugger, push reset, I get the green light. Then, as long as I don't push the reset button on the CC debugger, I can plug in our own manufactured devices and they will accept code loading from IAR. Then, everything works well, and our firmware runs perfectly. But, if I don't have a device provided by TI to reset the CC debugger, I can't get it to give me the green light.


I tried updating the firmware on the CC debugger to version 19, but it still doesn't work. So, for some reason the devices that we manufactured are not clearing some kind of reset check with the CC debugger. Could it be that some kind of boot loader code needs to go on the CC2531's before they will work with the CC debugger? I can't figure out what's happening here.

Thanks for your help.

  • Hi Doughy

    Find this behavior a bit strange and have some questions.

    Are the device label used in your own production correctly spelled?
    Where did you get the samples used in the production lot?
    Content from the devices information pages might help debug this issue.  Procedure to get this information described below.
    To secure correct read out please provide information page content from both production lot and sample bought from TI.  

    Best regards
    Tor-Inge

    Using the SmartRF Flash programmer, the CC2531 information page can be read like this.
    Install the flash programmer
    Open program
    Select program CCxxxx SoC or MSP
    Perform your workaround procedure.
    Now the CC2531 should be detected and the screen should look something like this.

     
    Select the CC2531 and press “View Info Page”
    The resulting screen should look something like this.

     

  • What do you mean by "device label?" If you're talking about the text printed right on top of the CC2531 chip, there are some differences between the "legit" device and the one in question. Please see my original post about this.

    My manufacturer was the one who ordered the chips, so I am not sure where they actually came from. I'm pretty sure it came from a foreign source, but I am contacting my manufacturer to get the exact details.

    I was able to get the information page to pull up, but I'm not able to save the data from the window. Here's a screenshot of the information page for the device in question.

  • Hi Doughy

    This content on this information page is causing the problem.

    We need to know the supplier of these chips to investigate root case for this problem

    Tor-Inge

     

  • Hi! We have similar problem. new delivered chips are not recognised by flash programmer. Logic analyser shows there is FF instead of chip ID. If I remove quickly old chip from programmer and connect new one without reset, than new chip can be programmed and verified Exactly as Doughy shows in his video. Did somebody already solved this problem? Thanks for help. Mirek

  • Hi

    As in case above we need to know the supplier of these chips to investigate this no chip ID. Doughy above never provided his chip supplier.  

    Tor-Inge

  • Hi Tot-Inge,

    At first please excuse my yesterday's mistake:

    Our 2531s (I have 3 samples) is returning zeros, not FF as I wrote yesterday evening. 

    As I can read:

    CC2531

    F256

    TI 09J

    PLL i G4

    Please check attached diagram.

    I will attache photo of the chip in next post

    Thanks a lot 

    Mirek

  • Hi again,

    here is the photo of the my 2531.

    Regards

    Mirek

  • Now I received message from my colegue, that chips are bought from: 

    STRONG EXUBERANT ELECTRONICS (HK) CO., LTD
    25G Building C, Huaqiang Plaza, Huaqiang North, Futian, Shenzhen, China, 518031

    www.see-ic.com


  • As a follow-up to my previous posts... I found out that the manufacturer we used bought the TI parts from some shady supplier called "Bull Electronics" in Asia. I demanded that they get the "real" parts from a certified distributor, and since then, I have not had any issues with my devices resetting in the CC debugger.

  • Hi Doughy,

    I've bought couple of 2531 at Farnell and everything is working fine now.

    I am posting another photo of  bad chips. 

    Mirek