• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 359 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: Cant view memory allocation after a successful build

Chris HOOGENBOOM
Intellectual 281 points
Part Number: MSPM0G3507

Tool/software: 

[0]**** Build of configuration Debug for project i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang ****
[1]"C:\\ti\\ccstheia141\\ccs\\utils\\bin\\gmake" -k -j 8 all -O 
 
[2]gmake[1]: 'i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang.out' is up to date.
[3]**** Build Finished *

Build appears to be successful?  Now I want to see how much memory was used.  I use "memory Allocation" and get

Project 'i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang'
ℹ️ The project must be successfully built first.

I am confused.  I think I successfully built it.  I get one mysterious  "info" message during build which is "User must select a device after migration. User must make sure to select the same device as the CCS Launch Device setting for proper configuration.".  I assume the severity of messages goes info, warning, error so surely a "info" message would not break the build?

  • 0
    TI__Genius 10490 points

    Hello Chris,

    I am sorry that CCS has caused you a bad user experience. In theory, the "info" won't affect the building. In general, closing the allocation window, building the project again and then open the allocation window again can resolve this issue. By the way, can you tell me the CCS version and SDK version you used?

    Best Regards,

    Janz Bai

  • 0 in reply to Janz Bai
    Intellectual 281 points 

    [0]**** Build of configuration Debug for project i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang ****
[1]"C:\\ti\\ccstheia141\\ccs\\utils\\bin\\gmake" -k -j 8 all -O 
 
[2]Building file: "../i2c_to_uart_bridge.syscfg"
[3]Invoking: SysConfig
[4]"C:/ti/sysconfig_1.19.0/sysconfig_cli.bat" --script "C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang/i2c_to_uart_bridge.syscfg" -o "." -s "C:/ti/mspm0_sdk_2_01_00_03/.metadata/product.json" --compiler ticlang
[5]Running script...
[6]Validating...
[7]info: /ti/project_config/ProjectConfig deviceSpin: Note: User must select a device after migration. User must make sure to select the same device as the CCS Launch Device setting for proper configuration.
[8]Generating Code (i2c_to_uart_bridge.syscfg)...
[9]Writing C:\Users\choogenboom\Documents\GitHub\OmniSense\SW\i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang\Debug\device_linker.cmd...
[10]Writing C:\Users\choogenboom\Documents\GitHub\OmniSense\SW\i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang\Debug\device.opt...
[11]Writing C:\Users\choogenboom\Documents\GitHub\OmniSense\SW\i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang\Debug\device.cmd.genlibs...
[12]Writing C:\Users\choogenboom\Documents\GitHub\OmniSense\SW\i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang\Debug\ti_msp_dl_config.c...
[13]Writing C:\Users\choogenboom\Documents\GitHub\OmniSense\SW\i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang\Debug\ti_msp_dl_config.h...
[14]Writing C:\Users\choogenboom\Documents\GitHub\OmniSense\SW\i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang\Debug\Event.dot...
[15]Finished building: "../i2c_to_uart_bridge.syscfg"
 
[16]Building file: "C:/ti/mspm0_sdk_2_01_00_03/source/ti/devices/msp/m0p/startup_system_files/ticlang/startup_mspm0g350x_ticlang.c"
[17]Invoking: Arm Compiler
[18]"C:/ti/ccstheia141/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/bin/tiarmclang.exe" -c @"device.opt"  -march=thumbv6m -mcpu=cortex-m0plus -mfloat-abi=soft -mlittle-endian -mthumb -O2 -I"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang" -I"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_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" -gdwarf-3 -MMD -MP -MF"startup_mspm0g350x_ticlang.d_raw" -MT"startup_mspm0g350x_ticlang.o"  @"./device.opt"  -o"startup_mspm0g350x_ticlang.o" "C:/ti/mspm0_sdk_2_01_00_03/source/ti/devices/msp/m0p/startup_system_files/ticlang/startup_mspm0g350x_ticlang.c"
[19]Finished building: "C:/ti/mspm0_sdk_2_01_00_03/source/ti/devices/msp/m0p/startup_system_files/ticlang/startup_mspm0g350x_ticlang.c"
 
[20]Building file: "../i2c_to_uart_bridge.c"
[21]Invoking: Arm Compiler
[22]"C:/ti/ccstheia141/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/bin/tiarmclang.exe" -c @"device.opt"  -march=thumbv6m -mcpu=cortex-m0plus -mfloat-abi=soft -mlittle-endian -mthumb -O2 -I"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang" -I"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_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" -gdwarf-3 -MMD -MP -MF"i2c_to_uart_bridge.d_raw" -MT"i2c_to_uart_bridge.o"  @"./device.opt"  -o"i2c_to_uart_bridge.o" "../i2c_to_uart_bridge.c"
[23]Finished building: "../i2c_to_uart_bridge.c"
 
[24]Building file: "ti_msp_dl_config.c"
[25]Invoking: Arm Compiler
[26]"C:/ti/ccstheia141/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/bin/tiarmclang.exe" -c @"device.opt"  -march=thumbv6m -mcpu=cortex-m0plus -mfloat-abi=soft -mlittle-endian -mthumb -O2 -I"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang" -I"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_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" -gdwarf-3 -MMD -MP -MF"ti_msp_dl_config.d_raw" -MT"ti_msp_dl_config.o"  @"./device.opt"  -o"ti_msp_dl_config.o" "ti_msp_dl_config.c"
[27]Finished building: "ti_msp_dl_config.c"
 
[28]Building target: "i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang.out"
[29]Invoking: Arm Linker
[30]"C:/ti/ccstheia141/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/bin/tiarmclang.exe" @"device.opt"  -march=thumbv6m -mcpu=cortex-m0plus -mfloat-abi=soft -mlittle-endian -mthumb -O2 -gdwarf-3 -Wl,-m"i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang.map" -Wl,-i"C:/ti/mspm0_sdk_2_01_00_03/source" -Wl,-i"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang" -Wl,-i"C:/Users/choogenboom/Documents/GitHub/OmniSense/SW/i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang/Debug/syscfg" -Wl,-i"C:/ti/ccstheia141/ccs/tools/compiler/ti-cgt-armllvm_3.2.2.LTS/lib" -Wl,--diag_wrap=off -Wl,--display_error_number -Wl,--warn_sections -Wl,--xml_link_info="i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang_linkInfo.xml" -Wl,--rom_model -o "i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang.out" "./i2c_to_uart_bridge.o" "./ti_msp_dl_config.o" "./startup_mspm0g350x_ticlang.o" -Wl,-l"./device_linker.cmd"  -Wl,-ldevice.cmd.genlibs -Wl,-llibc.a 
[31]Finished building target: "i2c_to_uart_bridge_LP_MSPM0G3507_nortos_ticlang.out"
 
[32]**** Build Finished ****

  • 0 in reply to Chris HOOGENBOOM
    Intellectual 281 points

    closing and restarting memory allocation worked, thanks!

  • +1 in reply to Chris HOOGENBOOM
    TI__Genius 10490 points

    It sounds good and you are welcome.