Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Remove the old BLE CAN-debug path

Closed
  • Is something wrong?
#23 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
embedded-iot

Research direction

Read the design and open questions in issue #10, then locate can_debug.rs, CAN_DEBUG_RX_CHANNEL, the board taps, MCP2515 debug mask switching, and publish_can_debug_task. Remove the old BLE CAN-debug path and check that SetCanDebugEnabled with bus_id >= 8 can no longer panic a debug build.

Written by the indexing model from the issue text.

Description

Part of https://github.com/OpenCarControls/firmware/issues/10, which has the design and open questions.

Remove can_debug.rs, CAN_DEBUG_RX_CHANNEL, the board taps, MCP2515 debug mask switching and publish_can_debug_task. Until then any bonded phone can panic a debug build with SetCanDebugEnabled and bus_id >= 8.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
12h 49m
Merged PRs (30d)
19

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 OpenCarControls/firmware

All issues in OpenCarControls/firmware

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.