[mbedmicro/pyOCD] Auto-detection of STLink targets (#631)
Chris Reed
This brings in support for auto-detection of the target associated with on-board STLinkV2-1 probes, so it works just as transparently as with DAPLink. Also brought in the list of ST board IDs from mbed-os-tools.
You can view, comment on, or merge this pull request online at:
https://github.com/mbedmicro/pyOCD/pull/631
Commit Summary
- MbedBoard accepts the board ID as a constructor parameter.
- Auto detection of associated board for STLink.
- Added STM32 board IDs from mbed-os-tools platform database.
File Changes
- M pyocd/board/board_ids.py (63)
- M pyocd/board/mbed_board.py (5)
- M pyocd/probe/cmsis_dap_probe.py (2)
- A pyocd/probe/stlink/detect/__init__.py (15)
- A pyocd/probe/stlink/detect/base.py (169)
- A pyocd/probe/stlink/detect/darwin.py (212)
- A pyocd/probe/stlink/detect/factory.py (47)
- A pyocd/probe/stlink/detect/linux.py (177)
- A pyocd/probe/stlink/detect/windows.py (516)
- M pyocd/probe/stlink_probe.py (26)
Patch Links:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Chris Reed
/morph test
Jerome Coutant
Hi
It seems that this re-implements mbedls ?
Can we imagine that pyOCD reuse mbedls board id table ?
Chris Reed
Merged #631 into master.
Chris Reed
Yes, it uses a highly stripped-down version of the mbed-ls (aka mbed-os-tools) code. The main reason for not reusing the original code was because it does a lot of other checks, and supports other probes. By removing these features we can make it simpler and faster.
Unfortunately we can't reuse the mbed-ls platform table because it doesn't contain the target type or test binary name that pyOCD needs. However, we're looking at adding this information to the Mbed platforms database, so pyOCD (and mbed-ls) can download it at runtime.
Chris Reed
Fyi, the only CI tests that failed were known issues with STM32 devices, like #579.