konsumer / konsumer/beatstep-cli
Custom Firmware
- Dominant language
- C++
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
It would be cool to program the Beatstep to mostly work like it does with regular firmware, but also have some of my sequencer ideas in the firmware itself. This would allow you to keep using the MIDI manager or CLI, but also use it as a beat-sequencer without a computer. Maybe some magic button-combo could change the built-in sequencer to work differently.
This will require:
- Reverse-engineering the led format (see #6)
- work out how to compile my own code for the device: figure out the chip they are using, etc
- write all the current device features (update mode, all the mapping sysex, send midi messages, etc)
- add new sequencer modes to code
- encode my custom firmware as led file
- upload to device
I think a first step would be getting it to just run simple custom code (blink lights, etc), that allows led-file updates (so I can put it back, and dev easier (no JTAG header needed, etc.)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with issue #6 to understand the LED format, then inspect the existing CLI and device update path. Determine how simple custom code could be compiled for the device and uploaded as an LED file, with restoring the original firmware as the initial completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100