• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 148 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.

CC2340R5: Not entered in

Divyani Rathod
Intellectual 290 points

Part Number: CC2340R5
Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG

We are using the CC2340R5 IC for a BLE application along with the LIS2DE12TR motion sensor. When the motion sensor is removed, the basic BLE example works correctly. However, when the sensor is connected, the firmware does not enter the main function. The application only runs if we manually restart the device in debug mode. Even when flashing the firmware with UniFlash, the system does not start.

To investigate the issue, I paused the CPU in CCS and checked the Program Counter (PC). The execution is repeatedly jumping among the following ROM addresses:

0x0F0024F8
0x0F0024F0
0x0F0024F4

These addresses appear to be inside the CC2340 Boot ROM, indicating that the device is stuck in a reset loop before reaching the application. When the sensor is disconnected, the application starts normally.

Kindly help us understand why connecting the LIS2DE12TR sensor prevents the CC2340R5 from exiting the Boot ROM and entering main(), and what configuration or hardware changes are required to resolve this issue.
Screenshot (406).pngScreenshot (404).pngScreenshot (405).pngScreenshot 2025-11-17 163818.pngScreenshot (403).pngScreenshot (407).png

 

 

  • 0
    TI__Guru**** 222287 points

    Hi Divyani,

    This is a common issue likely related to the default backdoor bootload pin from the SysConfig Device Configuration settings.

    The Default FCFG bootloader settings are in the TRM:

    So likely your hardware has DIO21 (pinTriggerDIO) pulled to ground (pinTriggerLevel).  To resolve this, you can disable the Bootloader in SysConfig ("Any bootloader forbidden"), use a custom CCFG settings ("Default FCFG bootloader, with CCFG settings"), or move your hardware away from using DIO21 entirely.

    Regards,
    Ryan

    Regards,
    Ryan