ARMmbed / ARMmbed/DAPLink

interface / dap / swd_init() improvements

Open
#357 2 comments 0 reactions 0 assignees View on GitHub
backlog enhancement
Dominant language
C
Stars
2.8k
Forks
1.1k
Avg merge
3d 12h
Merged PRs (30d)
1

Description

```
uint8_t swd_init(void)
{
//TODO - DAP_Setup puts GPIO pins in a hi-z state which can
// cause problems on re-init. This needs to be investigated
// and fixed.
DAP_Setup();
PORT_SWD_SETUP();
return 1;
}
```
This function is called several times, during the run, for instance as Target Reset mechanism.. maybe we could use simple flag that marks port already initialized so no need to reinitialize.. or use function that could optionally force port reinitialization? :-)

Contributor guide

Open the contributing guide

Research direction

Start at swd_init(), then inspect DAP_Setup() and PORT_SWD_SETUP() to understand the GPIO high-impedance state during repeated initialization. Reproduce the behavior across target-reset calls and determine whether initialization should be skipped or explicitly forced; done means repeated calls no longer cause the reported re-initialization problems.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.