in progress.
This commit is contained in:
parent
9f4c317274
commit
1f9e35d503
|
@ -39,9 +39,12 @@ cross referencing the schematic with the elite-pis [usage guide](https://docs.ke
|
||||||
One stumbling block is that the Ferris sweep ran out of pins to use full-duplex UART, and therefore only uses half-duplex.
|
One stumbling block is that the Ferris sweep ran out of pins to use full-duplex UART, and therefore only uses half-duplex.
|
||||||
To solve this, RMK supports (only on the RP2040) a PIO driver for half duplex, gated behind a crate feature in `cargo.toml`.
|
To solve this, RMK supports (only on the RP2040) a PIO driver for half duplex, gated behind a crate feature in `cargo.toml`.
|
||||||
With it, we can set our Tx and Rx pins to the same pin.
|
With it, we can set our Tx and Rx pins to the same pin.
|
||||||
|
In order to do this, however, I had to set the `rmk` dependency to a direct link to the Github repo,
|
||||||
|
because as of the time of writing, the `rp2040_pio` feature had not made it into a release.
|
||||||
|
|
||||||
After the painstaking process of tracing all the pins and putting them in the matrix, we can define the keymap.
|
After the painstaking process of tracing all the pins and putting them in the matrix, we can define the keymap.
|
||||||
My [keymap](https://github.com/gabevenberg/qmk_firmware/blob/personal/keyboards/ferris/keymaps/almost_default/keymap.json)
|
My [keymap](https://github.com/gabevenberg/qmk_firmware/blob/personal/keyboards/ferris/keymaps/almost_default/keymap.json)
|
||||||
is a bit complex, so it took some time to port.
|
is a bit complex, so it took some time to port.
|
||||||
|
It was mostly tedium rather than anything truly headscratching, however.
|
||||||
|
|
||||||
The final file looked like [this](https://github.com/gabevenberg/ferris-sweep-rmk/blob/main/keyboard.toml)
|
The final file looked like [this](https://github.com/gabevenberg/ferris-sweep-rmk/blob/main/keyboard.toml)
|
||||||
|
|
Loading…
Reference in a new issue