Add Reset Pin to Debug Probe

Open
#212 0 comments 0 reactions 0 assignees View on GitHub

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/debugprobe

All issues in raspberrypi/debugprobe

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.