MIMXRT1050_EVK goes to "No cores were discovered!" state
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
After few flash rounds the board goes to "No cores were discovered!" state and has to be restored with DIP switch altering and erase.
Steps:
pyocd flash -Oconnect_mode=under-reset -vvv -u 02270b0341114e45005d300ac207003692d1000097969900 -t mimxrt1050_hyperflash printer_MIMXRT1050_EVK.hexpyocd flash -Oconnect_mode=under-reset -vvv -u 02270b0341114e45005d300ac207003692d1000097969900 -t mimxrt1050_hyperflash payload_MIMXRT1050_EVK.hexpyocd flash -Oconnect_mode=under-reset -vvv -u 02270b0341114e45005d300ac207003692d1000097969900 -t mimxrt1050_hyperflash payload_null_MIMXRT1050_EVK.hex- "No cores were discovered!" occurs and board is unusable without manual restore.
Using pyoCD version mbedmicro/pyOCD@fdc69fac102880de4b845bcedf540dbd0c43d7b5.
binaries.zip
daplink.txt
no_cores_were_discovered_trace.txt
cc: @mmahadevan108 @maclobdell
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 three pyocd flash commands against the MIMXRT1050_EVK using the provided binaries.zip, then inspect daplink.txt and no_cores_were_discovered_trace.txt. Compare the behavior with the reported pyOCD revision; done means repeated flashing no longer leaves the board in the "No cores were discovered!" state or requiring manual restoration.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100