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/CC1310: CC1310 Clock/ Crystal not running. Migrating from 48 pin package to 32 pin package. Runs in Debug Mode.

Part Number: CC1310

Tool/software: Code Composer Studio

I used the CC1310F128RGZ (48-Pin package) on a previous design, and everything worked well.

I needed to shrink the design into a smaller package, and switched to the CC1310RHBT (32-Pin device, 5x5mm).

With the new 32-pin design the crystal does not oscillate - all circuitry is the same (inductor, crystal, caps, etc).

Does not seem to be a hardware issue, as the device will run in debug mode using CCS and Spectrum Digital XDS100V3 (crystal is oscillating when running in debug mode). 

Tried various hardware resets after power up with no effect. 

Crystal still oscillates when exiting debug mode, but will not oscillate from power up in normal mode. 

Any thoughts or tests you can recommend to isolate this problem? 

I am using the same crystal as was used in the 48-pin design, and have tried several boards. 

Seems that if it runs in debug mode, it would run in standalone mode.

Thanks.

  • - Do you here mean the 24 MHz xtal?
    - The 24 MHz xtal is only used for the radio meaning that a program that does not use RF should be running fine. Is that the case?
    - When the xtal doesn't start, is VDDR and DCOUPL voltages the same as when in debug mode?
  • Thanks for the quick response on this.

    I changed the clock to the internal clock, as you suggested, and it only runs in debug mode also.

    Is there any clue as to why it would run only in debug mode and not stand alone? 

    I think we have taken the 24MHz crystal out of the equation (thanks for the note on the 24MHz only needed for the RF section).

    VDDR is approx 1.75V, DCOUPL is approx 1.25V, double checked the 3.3V power pins - all good. 

    Also tried external RESET-. 

    It does run fine in debug mode from the emulator.

    Any help on this will be appreciated.

    Thanks.

  • The VDDR is slightly higher that expected (1.65 V). Is this voltage the same regardless of if you are running from debugger or not?

    Connecting the debugger should only impact the ability to go down to sleep (not possible with the debugger connected). Here it seems like it impacting something else. I could do a quick review of your design if you like (send a friend request if you don't want to make it public on the forum)
  • I re-measured VDDR with a meter (vs scope), and it is 1.67V, much closer to your expected value.

    Attached is the CC1310 portion of the schematic, I have sent a friend request, and will send the full schematic via that route.

    I checked the values for the boot loader (0x1FD8), and I do not think I am going through that routine.

    Is there any thing else I can check?

    I can still run fine in debugger mode through the XDS100V3.

    Is there any settings that are ignored if running in debug mode?

    Thanks.

    7802.CC1310.pdf

  • Update:

    A boot loader was being used, and the boot loader was driving an LED for diagnostics.

    The LED assignment in the boot loader code was from the original 48-Pin package, and had not been modified for the 32-Pin package.

    It appears this incorrect pin assignment in the boot loader code was causing the CC1310 to hang, and not start up.

    Using debug mode from the emulator, the micro controller was obviously bypassing the boot loader and running fine.

    I re-compiled the boot loader, taking out the LED pin assignments altogether, and now the CC1310 boots and runs. 

    Thanks,