Add Reset Pin to Debug Probe
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Read board_debug_probe_config.h and board_pico_config.h, then inspect commit d47b308 and the firmware uses of GPIO 0 and GPIO 1, especially UART0 RX/TX. Compare those uses with the schematic connections at J4, TP23, and TP25. Done means determining whether a reset pin can be defined for the debug probe and documenting or implementing a compatible choice.
Written by the indexing model from the issue text.
Description
Is there a reason the board_debug_probe_config.h does not define a reset pin while board_pico_config.h does?
The debug probe schematic shows GPIO pins 0 and 1 being connected to J4 as well as TP23 and TP25 respectively and the pins don't appear to be used in firmware.
Extra Context
Commit d47b308 changed the reset pin from GPIO 0 to GPIO 1. The commit message in part was "The reset pin must move otherwise uart0 tx is squashed". That makes me wonder if it being GPIO 1 would mess with uart0 rx but I haven't dug into it.
- Dominant language
- C
- Stars
- 1.3k
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from raspberrypi/debugprobe
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
raspberrypi/debugprobe#206 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
raspberrypi/debugprobe#202 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
raspberrypi/debugprobe#196 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
raspberrypi/debugprobe#185 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
raspberrypi/debugprobe#177 · 1 reaction ·
All issues in raspberrypi/debugprobe
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LedgerHQ/app-bitcoin-legacy#306 ·
-
[issue]: Ventoy2Disk.sh can leave the end of VTOYEFI unwritten (xzcat | dd without iflag=fullblock)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
prusa3d/Prusa-Firmware-Buddy#5629 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Issue PRL on WindowsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day