You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could not get binaries built from this repo built to work on my Cartographer, which is connected via Canbus.
It took much trial and error, but I was able to build, flash, and communicate with my Cartographer after I built the binary using these menuconfig options:
The key was adding "Set pin PA1 at microcontroller startup." I also had to add this to the menuconfig for Katapult.
Note: if you want to build Katapult from source you will need to use Cartographer's Katapult fork. The required 24MHz crystal clock speed option is not present in mainline Katapult.
I don't know yet if eddy-ng works on a Canbus Cartographer, but I was at least able to build the binary, flash it, and communicate with the MCU.
The text was updated successfully, but these errors were encountered:
Yeah, apologies -- Cartographer needs to be much better documented. It's also a very tiny device (stm32f042) that requires some hacks. Specifically, there's hard-pwm support for the f042 that's not present in mainline Klipper that's required -- you can get them from this commit (the changes in the stm32 directory).
I could not get binaries built from this repo built to work on my Cartographer, which is connected via Canbus.
It took much trial and error, but I was able to build, flash, and communicate with my Cartographer after I built the binary using these menuconfig options:
The key was adding "Set pin PA1 at microcontroller startup." I also had to add this to the menuconfig for Katapult.
Note: if you want to build Katapult from source you will need to use Cartographer's Katapult fork. The required 24MHz crystal clock speed option is not present in mainline Katapult.
I don't know yet if eddy-ng works on a Canbus Cartographer, but I was at least able to build the binary, flash it, and communicate with the MCU.
The text was updated successfully, but these errors were encountered: