Part Number: Launchpad CC2652-R7
Tool/software: CODECOMPOSER
Hello,
I am new to TI and have a couple general "getting started" questions with Code Composer Studio v12.8.1. I developed a simple application on the Launchpad CC2652-R7 development board that is based off a "DMM ZR Light" demo application that uses Zigbee and Bluetooth. When I debug the program, it runs fine the first time. But after that:
1. If I click the "Restart" button, the application doesn't restart properly. From what I can tell, it appears to assert. Is this expected behavior for a sample application, or is it possible I broke something? Why would it assert on a restart? Is there anything I need to configure to get the "Restart" debugger option to work correctly?
2. During development, I have occasionally hit an assert for one reason or another. When that happens, on other platforms, I can inspect the callstack or registers and get an idea of what code was running when the assert happened. However, on this platform, the callstack and registers are not helpful. There are about 5 different functions that were all part of the assert, so there is no clue where the assert was called from, as shown in the image below. Is there any good way to figure out what function called the assert?
3. If I power cycle the board, it runs an old (default) application that is not the application I was debugging with. Similarly, if I load the compiled .out image using Uniflash, then my application runs fine. But if I click the "Verify Image" button in UniFlash, or power cycle the target, then it runs the default application - not my compiled and loaded application. Does the Launchpad come installed with a Boot Image Manager? Could that be loading the default application? When I run the debugger or flash the .out file, is it running the image out of RAM and not flash? Is there something I need to change in my project so it can work with the bootloader, and run after a power cycle?
Thanks in advance!