gdb_test fails on NUCLEO-F429ZI device
Open
Nobody has claimed this yet.
backlog
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
window 10, board:NUCLEO_F429ZI
when run python automated_test.py in pyOCD/test directory, it will give a hint as follows:
it will block in gdbserver and can't execute in a full progress.
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
Start in pyOCD/test with automated_test.py and reproduce the failure on the NUCLEO_F429ZI board under Windows 10. Inspect the gdbserver step where execution blocks and compare the reported behavior with the test's expected flow. Done means gdb_test completes as part of the full automated test run.
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
- 25/100