-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when flashing klipper on EBB36 v1.2 (STM32G0B1) #67
Comments
Your can interface device is having trouble receiving data. Is it a U2C v2? |
It is Waveshare RS485 CAN HAT |
Make sure your device is configured with the correct settings for its crystal. You may also want to try reducing your can speed (this will require a rebuild and reflash of CanBoot). The CAN Hats have a tendency to drop can frames when the throughput is high. The gs_usb based devices (Canable, U2C, Klipper running USB-CAN bridge) are the most reliable. |
I ran at 500 000 I will reduce it to 250 000. crystal shall be ok at 12MHz |
I changed the speed to 250k.
|
That is because the hat is still dropping frames, however it isn't doing it on 5 consecutive attempts (which is the maximum number of tries the |
In the future, I plan to use the can interface of octopus 1.1. |
I don't really have a good answer for that, 250000 should be sufficient for one node. There is also the issue of the max speed you reach, when depends on the length of your wiring. You might get better answers on the Klipper Discourse or perhaps the Discord. |
Thanks |
I managed to flash CanBoot on the device and it is visible
I performed menueconfig in klipper and when I try to upload the klipper fw to the device I get following output:
I google'd around and did not get any hint on how to solve this issue
When querying the can again I can see klipper under the save uuid:
The text was updated successfully, but these errors were encountered: