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.

CC2642R: Developed on CC2642R-Q1 but production is CC2642R. Works with Q1 but not CC2642R: [ERROR] IcePick_C: Error connecting to the target: (Error -2131 @0x0)

Part Number: CC2642R
Other Parts Discussed in Thread: , UNIFLASH, CCSTUDIO, LAUNCHXL-CC26X2R1

I have developed a custom wearable device that due to part availability was prototyped with the CC2642R-Q1. For production ramp up we are using the CC2642R and currently experiencing errors in UniFlash. In UniFlash I'm seeing [ERROR] IcePick_C: Error connecting to the target: (Error -2131 @0x0). I've tried everything recommended in JTAG debugging here -> https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#device-register 

We received a very large qty of the CC2642R and are seeing the error across all of them. At what point can I say that these devices were received dead on arrival since everything works when I use the CC2642R-Q1? 

Thank you,

Randy 

  • Hi Randy,
    If there is an Error by UniFlash, you can try Flash Programmer 2.

  • Hi Randy,

    Other than trying Flash Programmer 2 and CCStudio as well, can you send some of the CC2642R device markings for us to review?  Where did you purchase the devices from?  Have you had your board design reviewed by TI?  https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS 

    Regards,
    Ryan

  • Hi Ryan,

    It's looking more like there could be an issue with the received CC2642R1s. Currently, the first 20 on the reel are all failing. When we swap in a CC2642R-Q1 and the CC2652R1 from a LAUNCHXL-CC26X2R1 they both work as expected.  

    Monitoring the VDDR pin (45) on the problem CC2642R1 starts at 3.28V and then goes down. The DCOUPL pin 23 starts at less than 1.0V and goes down.

    I've attached an image of the device with the marking below. 

    I'll also begin the process for a design review but given that everything works as expected with other CC26x2 devices I feel like it's probably not the issue. I'm working on determining the origin of the components but it was through our buyer. Once I get more details I'll upload them here. 

    Thank you,

    Randy 

  • Have you tried swapping one of the defunct CC2642R1F devices onto a LAUNCHXL-CC26X2R1?  Regardless this is sounding more like a quality issue from the provider, please supply more details when able.

    Regards,
    Ryan

  • That's in process, I will update shortly. Are you able to determine anything from the device markings?

    Thank you

  • Nothing outside of ordinary expectations.

    Regards,
    Ryan

  • Hi Ryan,

    I believe we may be dealing with some fakes. Comparing the CC2642 from the supplier in question and the working ones from digikey the fonts are different. 

    The working CC2652R1 and CC2642R-Q1 are san-serif and the CC2642R1 is serif. The CC2642R1 in question which I'm now fairly confident is a fake is the san-serif shown above. How consistent is the font or does that depend on each batch? 

    Thank you,

    Randy 

  • Randy,

    Please apologize for the delay; this thread slipped under my radar.

    I am checking with someone more experienced in the part marking to gather his experience, but I just want to confirm one detail: the photo of the working unit above is for a CC2642 non-Q1. Does the CC2642-Q1 look the same?

    The part marking is mentioned in the Packaging information section of the CC2642-Q1 datasheet.

    Regards,

    Rafael