• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 620 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.

MSPM0G3507: CCS Theia seems to search for header file in the wrong folder

Matze
Intellectual 453 points

Part Number: MSPM0G3507
Other Parts Discussed in Thread: , SYSCONFIG

Tool/software:

Hi TI-Experts,

I'm using CCS Theia with example project "secondary_bsl_uart_LP_MSPM0G3507_nortos_ticlang".

Now I'm trying to include the software BSL invoke and would like to make the Invokation visible by turning an LED on the Launchpad on.

I put my

DL_GPIO_setPins(GPIO_LEDS_PORT, GPIO_LEDS_USER_LED_1_PIN);

into the secondary_bsl.c

and the #defines for the GPIOs

/* Port definition for Pin Group GPIO_LEDs */
#define GPIO_LEDs_PORT                                                   (GPIOA)

/* Defines for USER_LED_1: GPIOA.0 with pinCMx 1 on package pin 33 */
#define GPIO_LEDs_USER_LED_1_PIN                                 (DL_GPIO_PIN_0)
#define GPIO_LEDs_USER_LED_1_IOMUX                                (IOMUX_PINCM1)
/* Port definition for Pin Group GPIO_GRP_0 */
#define GPIO_GRP_0_PORT                                                  (GPIOB)

/* Defines for PIN_0: GPIOB.13 with pinCMx 30 on package pin 1 */
#define GPIO_GRP_0_PIN_0_PIN                                    (DL_GPIO_PIN_13)
#define GPIO_GRP_0_PIN_0_IOMUX                                   (IOMUX_PINCM30)

into the ti_msp_dl_config.h

and the inits

DL_GPIO_initDigitalOutput(GPIO_LEDs_USER_LED_1_IOMUX);

    DL_GPIO_initDigitalOutput(GPIO_GRP_0_PIN_0_IOMUX);

    DL_GPIO_setPins(GPIO_LEDs_PORT, GPIO_LEDs_USER_LED_1_PIN);
    DL_GPIO_enableOutput(GPIO_LEDs_PORT, GPIO_LEDs_USER_LED_1_PIN);
    DL_GPIO_clearPins(GPIO_GRP_0_PORT, GPIO_GRP_0_PIN_0_PIN);
    DL_GPIO_enableOutput(GPIO_GRP_0_PORT, GPIO_GRP_0_PIN_0_PIN);

into the ti_msp_dl_config.c

And when I try to build my Project I get the following error messages:

[0]**** Build of configuration Debug for project secondary_bsl_uart_LP_MSPM0G3507_nortos_ticlang ****
[1]"C:\\ti\\ccstheia141\\ccs\\utils\\bin\\gmake" -k -j 4 all -O
 
[2]Building file: "../secondary_bsl.c"
[3]Invoking: Arm Compiler
[4]"C:/ti/ccstheia141/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/bin/tiarmclang.exe" -c -march=thumbv6m -mcpu=cortex-m0plus -mfloat-abi=soft -mlittle-endian -mthumb -Oz -I"C:/Users/m#########/Documents/GIT/WiPro3_facelift/Sandbox.wiproiii_facelift.sw.LP-MSPM0G3507/secondary_bsl_uart_LP_MSPM0G3507_nortos_ticlang" -I"C:/Users/m#########/Documents/GIT/WiPro3_facelift/Sandbox.wiproiii_facelift.sw.LP-MSPM0G3507/secondary_bsl_uart_LP_MSPM0G3507_nortos_ticlang/Debug" -I"C:/ti/mspm0_sdk_2_01_00_03/source/third_party/CMSIS/Core/Include" -I"C:/ti/mspm0_sdk_2_01_00_03/source" -D__MSPM0G3507__ -DUART_Plugin -gdwarf-3 -MMD -MP -MF"secondary_bsl.d_raw" -MT"secondary_bsl.o"   -o"secondary_bsl.o" "../secondary_bsl.c"
[5]subdir_rules.mk:9: recipe for target 'secondary_bsl.o' failed
[6]../secondary_bsl.c:222:21: error: use of undeclared identifier 'GPIO_LEDS_PORT'
[7]    DL_GPIO_setPins(GPIO_LEDS_PORT, GPIO_LEDS_USER_LED_1_PIN);
[8]                    ^
[9]../secondary_bsl.c:222:37: error: use of undeclared identifier 'GPIO_LEDS_USER_LED_1_PIN'
[10]    DL_GPIO_setPins(GPIO_LEDS_PORT, GPIO_LEDS_USER_LED_1_PIN);
[11]                                    ^
[12]2 errors generated.
[13]gmake: *** [secondary_bsl.o] Error 1
[14]Building file: "../ti_msp_dl_config.c"
[15]Invoking: Arm Compiler
[16]"C:/ti/ccstheia141/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/bin/tiarmclang.exe" -c -march=thumbv6m -mcpu=cortex-m0plus -mfloat-abi=soft -mlittle-endian -mthumb -Oz -I"C:/Users/m#########/Documents/GIT/WiPro3_facelift/Sandbox.wiproiii_facelift.sw.LP-MSPM0G3507/secondary_bsl_uart_LP_MSPM0G3507_nortos_ticlang" -I"C:/Users/m#########/Documents/GIT/WiPro3_facelift/Sandbox.wiproiii_facelift.sw.LP-MSPM0G3507/secondary_bsl_uart_LP_MSPM0G3507_nortos_ticlang/Debug" -I"C:/ti/mspm0_sdk_2_01_00_03/source/third_party/CMSIS/Core/Include" -I"C:/ti/mspm0_sdk_2_01_00_03/source" -D__MSPM0G3507__ -DUART_Plugin -gdwarf-3 -MMD -MP -MF"ti_msp_dl_config.d_raw" -MT"ti_msp_dl_config.o"   -o"ti_msp_dl_config.o" "../ti_msp_dl_config.c"
[17]Finished building: "../ti_msp_dl_config.c"
 
[18]gmake: Target 'all' not remade because of errors.
[19]**** Build Finished ****

And when I press CTRL + Left klick on "GPIO_LEDs_PORT" in ti_msp_dl_config.h I see the following references.

There are two references to files named "ti_msp_dl_config.h". one is in the root folder, one is in the Debug folder.

But when I look into the Debug folder there is no "ti_msp_dl_config.h". It is only in the root folder.

And when I search my project with notepad++ for ti_msp_dl_config.h I find 3 files in "C:\Users\m#########\Documents\GIT\WiPro3_facelift\Sandbox.wiproiii_facelift.sw.LP-MSPM0G3507\secondary_bsl_uart_LP_MSPM0G3507_nortos_ticlang\Debug\.clangd\.cache\clangd\index" that contain the text/path "/Debug/ti_msp_dl_config.h".

their names are:

boot_config.h.1667296CE236B965.idx

ti_msp_dl_config.c.F4FE0E1FE98BC6AB.idx

ti_msp_dl_config.h.32203948910323DA.idx

My guess is that there might be anything wrong about the linker as I don't use the sysconfig generation because the example project for secondary bsl is implemented without sysconfig generation.

I hope I gave you the full information that you need to help me.

Thanks a lot in advance!

Regards

Matze

  • +1
    TI__Genius 14350 points

    Hello Matze,

    You use "LEDs" in the .h file but you use "LEDS" in your .c file. Please pay attention to the capitalization of letters.

    Best Regards,

    Janz Bai

  • 0 in reply to Janz Bai
    Intellectual 453 points

    Thanks Janz,

    Now I can build without errors!

    But I get the following warnings:

    #10247-D: creating output section ".text" without a SECTIONS specification

    ...

    Do I have to anything about that warnings?

    When I try to flash/debug to my Launchpad I get the following errors:

    Flash Programmer: Error in image size. Length of block is 4862, but it should be divisible by 8 since Flash Programmer writes in 64-bits
    Flash Programmer: Error in image size. Length of block is 20, but it should be divisible by 8 since Flash Programmer writes in 64-bits
    Flash Programmer: Error in image size. Length of block is 268, but it should be divisible by 8 since Flash Programmer writes in 64-bits
    Flash Programmer: Error in image size. Length of block is 84, but it should be divisible by 8 since Flash Programmer writes in 64-bits
    Error: (Error -1001 @ 0x0) Requested operation is not supported on this device. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Error: (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD  request. Clear the error the condition, and try the SWD request again. (Emulation package 12.7.0.00130)
    Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)
    Unable to determine target status after 20 attempts
    Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
    Breakpoint Manager: Remove job failed: Register/memory write failure[22005]
    Breakpoint Manager: Remove job failed: Register/memory write failure[22005]

    Can anyone help? Thanks a lot in advance!

    Regards

    Matze

  • 0 in reply to Matze
    TI__Genius 14350 points

    Hello Matze, 

    1). Please update your CCS Theia to the latest version;

    2). Take a look at the linker command file (.cmd) in your project and make sure that the section mentioned in the warning is explicitly allocated to a memory region;

    3). Check your hardware connection;

    4). Disconnection and re-connection and try again.

    Best Regards,

    Janz Bai