Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Instructions for flashing Pi 500 keyboard? #4

Open
1 of 4 tasks
geerlingguy opened this issue Dec 10, 2024 · 6 comments
Open
1 of 4 tasks

[Feature Request] Instructions for flashing Pi 500 keyboard? #4

geerlingguy opened this issue Dec 10, 2024 · 6 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@geerlingguy
Copy link

Feature Request Type

  • Core functionality
  • Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
  • Alteration (enhancement/optimization) of existing feature(s)
  • New behavior

Description

I would like to know if and how I could re-flash my Pi 500's keyboard with a new key layout. Or if I could use the graphical configurator to do so? It'd be great to remap some keys easily, without resorting to Linux-y stuff.

@geerlingguy geerlingguy added enhancement New feature or request help wanted Extra attention is needed labels Dec 10, 2024
@timg236
Copy link

timg236 commented Dec 10, 2024

Please see the releases.zip for reflashing the .uf2 file

@nbuchwitz
Copy link

https://github.com/raspberrypi/QMK/blob/pi500/keyboards/rpi/pi500/README.md#programming-the-keyboard

@geerlingguy
Copy link
Author

Thanks! Is it worthy of adding a section to the top-level README file in this fork, or is that intended to match upstream?

@timg236
Copy link

timg236 commented Dec 11, 2024

Once the dust has settled I think we look at upstreaming the Pi500 QMK support and creating a minimal APT package for this. Although that will also require an APT package for picotool.

@timg236
Copy link

timg236 commented Dec 11, 2024

Thanks! Is it worthy of adding a section to the top-level README file in this fork, or is that intended to match upstream?

At a guess, we will have a downstream fork of the QMK repo containing just the pending patches. Pi500 specific instructions and tools will likely be in a separate repo / package.

I've added a unified SD card recovery image to the release e.g. if someone flashes a non functional QMK image to their Pi500 then they would need either SSH / UART / spare-keyboard to flash an alternate image. The SD image resets both the BCM2712 and firmware and RP2040 firmware to factory defaults.

https://github.com/raspberrypi/QMK/releases/tag/pi500-v1.0

@geerlingguy
Copy link
Author

@timg236 - All good to hear! I think it may even be adequate to have a dedicated 'Pi 500 Keyboard' section in the Docs, if the instructions could live there. Especially if the stuff is upstreamed into QMK (which would be ideal IMO).

A package install would be convenient, as would GUI-based remapping/tweaks, which are so fun for keyboard enthusiasts with all those fancy Keychrons and such!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants