• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 80 subscribers
  • Views 638 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.

Original question:

MSP430FR2675: Custom BSL vs Application Project Configuration

MSP430FR2675: Compatible BSL Source Code

pcpro178
Intellectual 365 points

Part Number: MSP430FR2675
Other Parts Discussed in Thread: MSPBSL, , MSP430FR2676

After downloading the MSPBSL_CustomBSL430, I'm trying to get the CCS_v7_MSP430F522x_I2C example to compile, but I'm getting a number of errors:

#20 identifier "TZ_CLK_SEL" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 146 C/C++ Problem
#20 identifier "TZNCCR_RX" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 323 C/C++ Problem
#20 identifier "TZNCCR_TX" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 369 C/C++ Problem
#20 identifier "TZNCCTL_RX" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 320 C/C++ Problem
#20 identifier "TZNCCTL_TX" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 145 C/C++ Problem
#20 identifier "TZNCCTL_TX" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 377 C/C++ Problem
#20 identifier "TZNCCTL_TX" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 390 C/C++ Problem
#20 identifier "TZNCTL" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 146 C/C++ Problem
#20 identifier "TZNR" is undefined BSL430_PI_TA.c /BSL_bootloader/Peripheral_Interfaces line 369 C/C++ Problem
gmake: *** [Peripheral_Interfaces/BSL430_PI_TA.obj] Error 1 BSL_bootloader C/C++ Problem
gmake: Target 'all' not remade because of errors. BSL_bootloader C/C++ Problem

How/where are these unidentified labels supposed to be defined?  Where can I find custom BSL source code (to use as a starting point) that is compatible with the MSP430FR2675?

  • 0 in reply to Eason Zhou
    Intellectual 365 points

    Thanks, but I'm getting a different error now:

    #1965 cannot open source file "PHY_DataLink\TI_MSPBoot_CI_PHYDL.h" TI_MSPBoot_CI.h /BSL_bootloader/Comm line 45 C/C++ Problem
    gmake: *** [Comm/NWK_APP/TI_MSPBoot_CI_NWK_APP_BSL.obj] Error 1 BSL_bootloader C/C++ Problem
    gmake: *** [Comm/PHY_DataLink/TI_MSPBoot_CI_PHYDL_eUSCI_I2C_slave.obj] Error 1 BSL_bootloader C/C++ Problem
    gmake: *** [main.obj] Error 1 BSL_bootloader C/C++ Problem
    gmake: Target 'all' not remade because of errors. BSL_bootloader C/C++ Problem

    This doesn't make sense because I've updated my project include paths as shown.

  • 0 in reply to pcpro178
    Intellectual 365 points

    There's something weird with CCS in that it can't seem to find include files at relative paths.  I added the subdirectories to the project include paths, removed them from the include directives in TI_MSPBoot_CI.h, and the build is getting past that.

    The problem I'm facing now is that when I do a build CCS is processing lnk_msp430fr2676.cmd, even though the project settings are configured to use lnk_msp430fr2675.cmd.

    Is excluding the unwanted file from the build the best way to handle this?  I want to leave it in the project because some on our team have dev boards with the FR2675 and others have the FR2676.

  • 0 in reply to pcpro178
    TI__Mastermind 40195 points

    Sorry, I don't know how any other solution except excluding the unwanted file from the build.

    If you want to know about about CCS setting, I can help you to move this thread to another team.

  • 0 in reply to Eason Zhou
    Intellectual 365 points

    Yes, thank you.  If there is another option, I would like to know.

  • +1 in reply to pcpro178
    TI__Guru**** 477491 points
    pcpro178 said:

    The problem I'm facing now is that when I do a build CCS is processing lnk_msp430fr2676.cmd, even though the project settings are configured to use lnk_msp430fr2675.cmd.

    Is excluding the unwanted file from the build the best way to handle this?  I want to leave it in the project because some on our team have dev boards with the FR2675 and others have the FR2676.

    If you change the project settings to use a different cmd file, it should include that cmd file to the project and "exclude form build" the other cmd file automatically. You should not have to exclude it explicitly unless the original cmd file was manually added. If it was manually added, then yes, you would need to also manually exclude it yourself.

    Thanks

    ki

**Attention** This is a public forum