• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 78 subscribers
  • Views 406 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/MSP430FR5994: How do I run the debugger for an application built for MSP430FRBoot?

Bryan Evenson24
Intellectual 540 points
Part Number: MSP430FR5994

Tool/software: Code Composer Studio

I'm using the MSP430FRBoot example bootloader as a starting point for OTA firmware upgrade for my project.  I've been able to build the example projects and step through the firmware upgrade process as described in the MSP430FRBoot app note (SLAA721B).  Now I'm trying to use the debugger while running either App1 or App2 prior to updating the linker and address space for my application.  However, I can't debug either App1 or App2 with Code Composer Studio.  I think what happens is the debugger erases all flash (including the previously loaded MSP430FRBoot) and when I start code execution it jumps to the start of where the MSP430FRBoot used to be.

If I have a project setup for the application space for MSP430FRBoot, what special things do I need to do so I can debug the application with Code Composer Studio?  I'm assuming there may need to be some different Run/Debug settings, but I haven't found the right combination yet.  Is there anything else I need to change also?

  • 0
    TI__Genius 9570 points
    Hi Bryan,

    If you want to debug App1 or App2, you have to replace the .cmd file with default .cmd file.

    Ling
  • 0 in reply to Ling Zhu2
    Intellectual 540 points

    Ling,

    OK, that makes sense.  However, I can't seem to find where in these projects it's setting the linker command file.  I'm working with the example project App2 from the MSP430FRBoot examples.  I created a new configuration based upon "BSL_Based_DualImg" that I called "BSL_Based_DualImg_Debug".  In my new configuration under Properties->CCS General, I noticed the "Linker Command File" setting was blank.  I updated it to the path of the default MSP430FR5994 linker command file.  When I built the project, I received a bunch of linker errors about memory ranges already being specified.  Then I noticed in the build output that the linker command referenced both lnk_msp430fr5994_UART_4KB_Dual_App.cmd and the linker command file I specified.  I can't seem to find anywhere how the project is still including lnk_msp430fr5994_UART_4KB_Dual_App.cmd in my new configuration.  I've even done full-text searches for lnk_msp430fr5994_UART_4KB_Dual_App.cmd in the project, and the only references I can find to lnk_msp430fr5994_UART_4KB_Dual_App.cmd are in auto-generated files.

    For this project, how do I setup a new configuration to use only my new linker command file and not use lnk_msp430fr5994_UART_4KB_Dual_App.cmd? 

  • 0 in reply to Bryan Evenson24
    Intellectual 540 points
    Ling,

    I just found it. For the specific configuration, go to Properties->C/C++ General->Paths and Symbols. Under the "Source Location" tab, expand the folder and there is a exclusion filter. For my new debug configuration, added the path to the lnk_msp430fr5994_UART_4KB_Dual_App.cmd. Now when I build I it only includes the default linker command file and not the specially built one meant to work with MSP430FRBoot.

    I still have a problem with App2 due to the shared callbacks with MSP430FRBoot. At first build, there were unresolved symbols for _BOOT_APPVECTOR, PassWd and StatCtrl. I think I need to make sure SHARED_PI is undefined for my debug configuration and I need to block out some more sections when SHARED_PI is not defined. But, my original problem is not fixed.

**Attention** This is a public forum