请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。
器件型号：MSPM0G1106 主题： SysConfig 中讨论的其他器件
工具/软件：
您好、
我们目前正在尝试在设计中实现 MSPM0G1106。 该器件通过 I2C 与我们的主 MCU 连接。
我们使用的是 MSPM0 SDK 2.4.0.06、SysConfig 1.21.1和 TI-CLANG 4.0.2 LTS。
我们需要更改 BSL 的 I2C 地址、因为已经有另一个总线器件使用默认 I2C 地址0x48。
我们还需要通过 BSL 读取应用版本、这需要我们在配置 NVM 中设置相应的值。
我们在 SysConfig 中有以下设置：
NONMAIN.nonmainWarning = true; NONMAIN.bslAppVersion = 0xC0; NONMAIN.i2cSlaveAddress = 0x50;
通过我们的 J-Link 刷写器件似乎可以正常工作一次、但在尝试第二次闪存后、闪存失败、并导致器件完全无响应。 仅更改了第二个闪存的应用程序代码、BSL 配置尚未更改。
刷写过程中报告以下错误：
CORTEX_M0P: Trouble Writing Memory Block at 0x41c00100 on Page 0 of Length 0x58: Flash download failed! ... CORTEX_M0P: File Loader: Verification failed: Target failed to write 0x41C00100 CORTEX_M0P: GEL: File: XXXXXXXXXXX.out: Load failed.
现在、在尝试连接到器件时仅报告以下情况：
Device "MSPM0G1106" selected. Connecting to target via SWD Found SW-DP with ID 0x6BA02477 DPIDR: 0x6BA02477 CoreSight SoC-400 or earlier Scanning AP map to find all available APs AP[0]: Stopped AP scan as end of AP map has been reached Iterating through AP map to find AHB-AP to use Attach to CPU failed. Executing connect under reset. DPIDR: 0x6BA02477 CoreSight SoC-400 or earlier Scanning AP map to find all available APs AP[0]: Stopped AP scan as end of AP map has been reached Iterating through AP map to find AHB-AP to use Could not find core in Coresight setup Found SW-DP with ID 0x6BA02477 DPIDR: 0x6BA02477 CoreSight SoC-400 or earlier Scanning AP map to find all available APs AP[0]: Stopped AP scan as end of AP map has been reached Iterating through AP map to find AHB-AP to use Attach to CPU failed. Executing connect under reset. DPIDR: 0x6BA02477 CoreSight SoC-400 or earlier Scanning AP map to find all available APs AP[0]: Stopped AP scan as end of AP map has been reached Iterating through AP map to find AHB-AP to use Could not find core in Coresight setup Cannot connect to target.
尝试与 XDS110一起使用 DSSM 恢复出厂设置工具无法正常工作。 该线程 e2e.ti.com/.../mspm0l1305-dssm-commands-to-factory-reset-without-xds110中的 JlinkScripts 也不 使用我们的 J-Link。
这是通过2个器件中的2个器件发生的。
虽然我确实明白、错误配置 NONMAIN 区域可能会使器件砖化、但我有点不明白为什么在这种情况下会发生这种情况。
我们是否遗漏了一些东西？ 是否有机会恢复设备？
