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.

CC1350STK: Application run only in CCS8.0 deubgging mode

Part Number: CC1350STK
Other Parts Discussed in Thread: CC1350, , CC-DEBUGGER, LAUNCHXL-CC1350

Hi.
I have CC1350 SensorTag revision 1.5.1 and DEBUGGER-DEVPACK revision 1.3.0 and LCD-DEVPACK.
I have a custom application based on code from rfWsnNodeExtFlashOadClient_CC1350STK_tirtos_ccs. The application transmits data to a central device listening to packets.
When I debug the application using Code Composer 8.0 I use the debugger and the application works ok and I see the packets arrive.
When I try to burn the image using Flash Programmer 2.0, the flashing succeeds, but no packets arrive. When I remove debugger and insert battery (new battery) it is the same, no packets arrive.
What can be the cause for this? When I use debugging from CCS 8.0 I can run the application successfully, but when I run it not from CCS 8.0 (and without the DEBUGGER board) the application does not run.

I have 2 questions:

  1. Can I debug the CC1350STK using CCS 8.0 when it is NOT connected to the DEBUGGER-DEVPACK? using cc1350launchxl? or using cc-debugger? or using SMARTRF-06?
    Which of these debugger can be used to debug CC1350 without need for DEBUGGER-DEVPACK? Can it be debugged when the battery is used?
  2. What are the differences between the burning the image using debugging feature in CCS 8.0 and burning using Flash Programmer 2.0? Why it works in one and doesn't work in the second one? The .out file is use is exactly the same.

Kind Regards

  • 1. CC-DEBUGGER is for CC254x and CC253x which are 8051 based code and not for CC1350 which is based on ARM core. You can use LAUNCHXL-CC1350 or SmartRF06 to debug CC1350STK without problem
    2. I suppose you can make it work with CCS but not Flash Programmer 2, right? If so, that is due to BIM has to be downloaded to CC1350STK when you use Flash Programmer 2.
  • If the example works when running from the debugger but not when running stand-alone, it might be problems related to power modes. Running code from the debugger prevents the device from entering standby (even if it is supposed to from the application point of view). I would strongly recommend that you start by testing some of our examples (unmodified) and have the up and running, with and without the debugger running, before starting to make changes to the code.
  • How do I burn the BIM without using OAD? I tried compiling rfWsnNodeExtFlashOadClient_CC1350STK_tirtos_ccs as-is and burning the .out file using Flash Programmer 2.0 and exactly same happened (works in CCS, doesn't work when burnt from Flash Programmer). In both not working scenarios there is a red LED on constantly, so I guess it is the same issue.
    How do I corretly burn the .out file? Project 0 page only describes how to do OAD image which I am not interseted in as I don't have BLE or OAD functionality
  • I am seeing the same thing as you do and have contacted the team responsible for these examples. I will keep you updated.

    BR

    SIri
  • Hi

    I have just got confirmed that you cannot load the rfWsnNodeExtFlashOadClient file to the launchpad without the BIM.

    Since CCS will automatically jump to the main function, the application can be ran using the debugger. To run the example without the debugger, you will need the Boot Image Manager to verify the image and jump to the right location.

    You will find instructions in the the README on how to properly create and load an OAD file.

    BR
    Siri