MSPM0L1105 No cores were discovered
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
pyOCD detects MCU-Link CMSIS-DAP and enumerates MSPM0L1105 APs:
DPIDR 0x6ba02477
AP0 IDR 0x84770001
AP1–AP4 IDRs 0x002e000x
But target initialization fails with:
No cores were discovered
Target: mspm0l1105
Pack: TexasInstruments.MSPM0L_DFP 1.2.1
Probe: MCU-Link CMSIS-DAP V3.172
OpenOCD works with same hardware and can mass erase/program.
Here is what I typed:
PS C:\dev\tools\openocd_mspm0> pyocd cmd -t mspm0l1105 -v
0000991 I Target type is mspm0l1105 [board]
0001101 I DP IDR = 0x6ba02477 (v2 rev6) [dap]
0001109 I AHB-AP#0 IDR = 0x84770001 (AHB-AP var0 rev8) [discovery]
0001110 I AP#1 IDR = 0x002e0001 (AP var0 rev0) [discovery]
0001110 I AP#2 IDR = 0x002e0000 (AP var0 rev0) [discovery]
0001111 I AP#3 IDR = 0x002e0003 (AP var0 rev0) [discovery]
0001111 I AP#4 IDR = 0x002e0002 (AP var0 rev0) [discovery]
0001112 E Error while initing target: No cores were discovered! [commander]
PS C:\dev\tools\openocd_mspm0>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with target mspm0l1105, the TexasInstruments.MSPM0L_DFP 1.2.1 pack, and the reported MCU-Link CMSIS-DAP probe. Start with pyOCD target initialization and AP discovery, comparing the reported IDs with OpenOCD's working behavior. Done means pyOCD initializes the target and discovers its core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100