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:成功构建后无法查看内存分配

Guru**** 1799260 points
请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1392994/mspm0g3507-cant-view-memory-allocation-after-a-successful-build

器件型号:MSPM0G3507

工具与软件:

[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 *

构建似乎成功?  现在、我想看看使用了多少内存。  我使用"内存分配"和 GET

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

我感到困惑。  我想我成功构建了它。  我 在构建期间收到一条神秘的"信息"消息、即"用户必须在迁移后选择器件。 用户必须确保选择与 CCS 启动器件设置相同的器件才能进行正确配置。"  我假定消息的严重性会变为 INFO、WARNING、ERROR、所以"info"消息肯定不会破坏构建?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    Chris、您好!

    很抱歉、CCS 给您带来了糟糕的用户体验。 理论上,"信息"不会影响建筑。 通常、关闭分配窗口、再次编译项目、然后再次打开分配窗口可以解决这个问题。 顺便说一下、您能否告诉我您使用的 CCS 版本和 SDK 版本?

    此致、

    Janz Bai

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    [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 ****
    

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    关闭和重新启动内存分配工作正常、谢谢!

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    听起来不错、您很受欢迎。