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/LAUNCHXL-CC1352R1: Code Composer Studio™ forum

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: UNIFLASH,

Tool/software: Code Composer Studio

1. The LauchXL boards (two of them) worked fine out of the box: I was able to test the Bluetooth Project Zero by connecting to the board form my Androind phone, as described in the page (Out of the Box Experiemce):

http://dev.ti.com/tirex/explore/node?node=ADuSIrFg2kUHlTd9Kp0MqQ__pTTHBmu__LATEST

2. Then I wanted to try out the Zigbee Project Zero described in the page. I used Unifash to clear existing firmware on two boards and loaded the coordinator and end device firmware.

http://dev.ti.com/tirex/explore/node?node=AIHpFUnGAZPCyIyMVNwlJA__pTTHBmu__LATEST

3. However,  I ran into trouble connecting to either board using putty. So I tried to restore the firmware to factory setting (using the right button and the reset button). I also tried to flash the hex file of the ble5stack projectzero from 

C:\ti\simplelink_cc13x2_26x2_sdk_3_10_00_53\source\ti\ble5stack\hexfiles\cc13x2r1\ble5_project_zero_cc13x2p2lp_app_FlashROM_Release_unsecure.hex.

4. But the Android app does not seem to recognize the launchpads as BLE devices. My suspicion is that the firmware erase step in the Zigbee Project Zero 9( Step 0) instructions may have erased ket firmware sectors that should not have been erased.

How do I set the boards to their factory setting so that the Bluetooth Out of the Box ProjectZero works?

Thanks,

Siva

  • Hi Siva,
    I'm assigning this thread to one of the experts to comment.
  • Hi Siva,

    The Uniflash clear probably erased the part of the code that does the factory reset.

    To program aian the device with BLE project zero, please follow the steps in the Bluetooth Low Energy Fundamentals lab ( dev.ti.com/.../node ).

    BTW, pleas double-check the chip revision of your chip. The linked resources only support chip revision E. See the FAQ post for more info.
  • The solution provided by Marie did not solve my problem.

    To reproduce,

    1. I took a brand new board (LaunchXL-CC1352R1). The white sticker on the back of the board says Rev 0.4.0 FW: 1.60RC1, 1752

    2. I tried to connect to the board from the SimpleLink Android app. The app identified the ProjectZero device and all tests were successful.

    3. I followed the steps in the Bluetooth Low Energy Fundamentals lab link suggested by Marie H. I ended up with the following screen. After debugging both projects, the firmware no longer responds to the Android App. it fails even when I keep it in debug mode (as opposed to pressing the reset button and running the program from flash). I am attaching the CCS screenshot:

      

    A few facts, observations and possible clues:

    1. I'm running code composer 9.0.1

    2. When I launched the offchip program in debug mode, CCS told me that I needed to update the debugger firmware on the board before proceeding. 

    3. When the program loads, the red led at the edge of the board is lit steady red.

    4. Once the loading is complete, the execution does not go to the main() function and halt.

    5. The lab link is for 26x2, but I worked with 13x2r folder since that is my board.

    Uniflash has the following info about the board:

    Let me know if I can provide any more information. My goal is to get xigbee project zero to work, but there seems to be some problem with flashing even the factory code. So I hesitate to try anything else. I now have three boards that I have broken, but also have a fourth unopened box of the same kit in case you want me to try anything else.

    Thanks for your assiatance.

    Siva

  • SimpleLink CC13x2 SDK v2.30 was successful!