search

FYSETC / FYSETC-ERB

This is dedicated controller board for VORON ERCF (EnragedRabbitProject)
40 stars 6 forks source link

Menuconfig options missing from documentation #3

Open JoaquinBerrios opened 1 year ago

JoaquinBerrios commented 1 year ago

The current documentation for building the klipper firmware for the MCU on this board does not indicate values for the build options available in the current version of klipper. Could you please update the documentation to specify the values needed to build a current version?

Currently, make menuconfig prompts for the following values when RP2040 is selected as the micro-controller architecture:

[*] Enable extra low-level configuration options Micro-controller Architecture (Raspberry Pi RP2040) ---> Bootloader offset (No bootloader) ---> Flash chip (W25Q080 with CLKDIV 2) ---> Communication interface (USB) ---> USB ids ---> () GPIO pins to set at micro-controller startup (NEW)

matthewj301 commented 1 year ago

Same issue here

matthewj301 commented 1 year ago

Just a follow up, I just ended up trying a few options, and what seemed to work for me was: [*] Enable extra low-level configuration options Micro-controller Architecture (Raspberry Pi RP2040) ---> Bootloader offset (No bootloader) ---> Flash chip (W25Q080 with CLKDIV 2) ---> Communication interface (USB) ---> USB ids ---> () GPIO pins to set at micro-controller startup (NEW)

Haven't actually tried using it yet, but Klipper (RatOS) now recognizes it (using https://github.com/moggieuk/ERCF-Software-V3). You'll still have to connect it to a PC initially and copy over the binary to the ERB

JoaquinBerrios commented 1 year ago

Just to confirm that I have done builds with the options set to what I posted above and they have worked fine. At least I was able to get through all the testing and calibration steps. I settled on the flash chip after looking at the components on the board, so it would be nice if the officially recommended options were included in the documentation to save future users some grief either worrying that they are going to brick their board or having to look up components on the boards to figure out how to build.

Still having the issue where I have to reset the board on every boot for the MCU to connect. See the workaround in #2 if you run into that issue.