LPC1768: Timeout waiting for gdb server to start
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
I am using MBED Studio 1.4.1 to try to debug a problem with an LPC1768 processor and every time I try to start the debugger I get the message "Timeout waiting for gdb server to start". Yet, when I start the debugger with "pyocd gdb --target lpc1768" it starts and keeps running. I looked up the problem and there was some discussion around 1.11.1 but nothing for 1.4.1.. They suggested that that person run pyocd with a supplied pyocd.yaml file, which I did and got the following: pyocd_jlink_log.txt
Can you help me get the debugger working?
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 by reviewing pyocd_jlink_log.txt and comparing MBED Studio 1.4.1's debugger launch with the working pyocd gdb --target lpc1768 command. Reproduce the timeout and determine why the gdb server is not detected; done means the LPC1768 debugger starts successfully from MBED Studio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100