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.

CCS/CC2652R: Problem with simple peripheral program on custom board

Part Number: CC2652R

Tool/software: Code Composer Studio

Hello!

I have created a custom board with a battery on it utilizing the CC2652R. 

Using the XDS110 and cJTAG connectors on the board, I was able to download the simple peripheral program and connect the custom board to my phone. When I however disconnected all the cJTAG wires and the probe from the board and tried again, several ''simple peripherals'' showed up in the BLE scanner and new ones showed up every second and I could not connect to any of them.

Any suggestion why this would happen and how I can resolve this?


  • Hello Lauk,

    Which SDK and which project did you use?

    0) Have you gone through the CC13xx/CC26xx Hardware Configuration and PCB Design Considerations (Rev. D) ?

    1) First try a complete erase of the flash using the latest version of the Flash Programmer 2 (forced mass erase). Then reload you code.  

    2) Is there pull-up resistor and decoupling capacitor on the Reset line on your custom board (copy from ref design)?

    3)

    a) What kind of 32 kHz crystal and load caps are used?

    b) Have you verified the 32 kHz clock accuracy by 

    You can take a look at our TRM chapter 13.3.4 to Map the 32-kHz System Clock (LF Clock) to DIO. As stated in our TRM, it outputs the LF system clk signal in all power modes except for shut down.

    Following is all you need to do :

    IOCPortConfigureSet(IOIDn, IOC_PORT_AON_CLK32K, IOC_STD_OUTPUT);
    AONIOC32kHzOutputEnable();

    c) You can also test to use internal RCOSC_LF as sclk_lf source to partially verify if 32 kHz external XTAL is the issue. 
    You can follow the application note below to configure device using RCOSCLF
    www.ti.com/.../swra499

  • Hey!

    I am using simplelink_cc13x2_26x2_sdk_4_10_00_78 and the project 

    0) I have gone through and followed the hardware configuration as closley as possible.

    1) I tried that, still not working

    2) Yes, a 100k ohm pull up resistor and a 1uF capaciotr

    3 A) I am using two 12pF capacitor with the following crystal : 

    ABS07-32.768KHZ-7-T

    B) I'll try all the crystal tests and update with a result

  • Ok, also can you check all relevant power lines using a oscilloscope and be sure that they are clean and at the correct level? There is a possibility that your custom board isn't being powered properly when the debugger isn't connected.

  • Hey!

    Some updates;

    The simple peripheral program already has the external oscillator disabled. I tried to remove the codes in the program so that I use the onboard oscillator but the problem still persists.

    I will try to measure the power lines using an oscilloscope later today and get back to you. I have however measured VDDR and DCOPUL lines as stated in the datasheet with a multimeter and measured the following values:

    VDDR= 1.68 V
    DCOUPL = 1.27 V 


    One problem that I noticed however is that the capacitor on the nRESET pin line is not grounded, could this be the issue? I will resolder that capacitor and try again!

    Kind regards

    Lauk

  • An update again!

    I resolved the issue, turned out to be as you said a bad case of power not really getting to the MCU. Turns out that I had a bad case of soldering on the inductor on the DCDC pin, I resoldered the inductor and now it works! Thanks for all the help!

    kind regards

    Lauk