Laikulo
commented
9 months ago Currently, I have a machine named fakeprinter running a KIAUH-based klipper install on rPI os 64 legacy.
It has the following MCUs:
| MCU | Hardware | connectivity | flash method | bootloader |
|---|---|---|---|---|
| hostmcu | linux-process | pty | make (cp) | n/a |
| ebb36 | ebb36 | usb-cdc | katapult-usb | katapult |
| stamp | rp2040-zero | usb-cdc | rpiboot | none |
| katastamp | rp2040-zero | usb-cdc | katapult-can | katapult |
| canstamp | rp2040-zero | usb-canbridge | rpiboot | none |
| katacanstamp | rp2040-zero | usb-canbridge | katapult-can | katapult |
| serialstamp | rp2040-zero | uart(3v3) | katapult-uart | katapult |
TODO:
- [x] Add udev rules to keep the canbridge interfaces from swapping
- [ ] Add UTOC and move ebb36 to real can, and katapult over can
- [ ] Find another stm32 board to use for flashing with dfu, doesn't need to actually work
- [x] Set up another rp2040-zero for tty+canboot.
- [x] Check if rpiboot supports tty-based firmware loads
- [x] Find a better powered USB hub for this setup
I need a way to be able to test combinations of flashing methods and bootloaders.