Unable to detect CYW9P62S1_43012EVB_01
- Dominant language
- Python
- Stars
- 49
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
`mbed-tools detect` can't detect CYW9P62S1_43012EVB_01 (detection code: 1903). The target database is based on https://os.mbed.com/api/v4/targets which doesn't include this target.
The fix would be updating the online database then making a new mbed-tools release.
**To Reproduce**
Connect CYW9P62S1_43012EVB_01 to a PC, ensure it's in the right mode (KITPROG3 STATUS LED blinking) and detected by Mbed CLI 1 (mbed detect):
```
$ mbed detect
[mbed] Detected CYW9P62S1_43012EVB_01, port /dev/tty.usbmodem14103, mounted /Volumes/DAPLINK, interface version 0254:
```
Mbed CLI 2 is unable to detect it:
```
$ mbed-tools detect
ERROR: Could not identify a board with the product code: '1903'.
```
**Expected behavior**
Target detected
**Screenshots**
**Desktop (please complete the following information):**
- OS: macOS
- Version: 11.5.2
**Mbed (please complete the following information):**
- Device: CYW9P62S1_43012EVB_01
- Mbed OS Version: mbed-os-6.14.0
- Mbed CLI 2 Version: 7.32.0
**Additional context**
Contributor guide
Research direction
Start by running `mbed-tools detect` with the CYW9P62S1_43012EVB_01 board and compare it with the documented `mbed detect` output. Read the target database at the linked Mbed targets API and the detection entry point; done means product code 1903 identifies the target and the resulting change is included in a new mbed-tools release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100