-
Notifications
You must be signed in to change notification settings - Fork 5
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
can0 interface issues. #9
Comments
Seems to be related to the source clock frequency of can0. |
still no solution? it looks like the Catalyst will go straight to the trash and I'll replace it with something functional 🤔 |
I really need that one swell. any luck? |
Actually works well at 500k with an ebb36 toolhead but too many errors at 1M. I'm trying to get dts tree from fysetc to build my own kernel (ideally to get more recent armbian kernel) to support 1M. |
Hello,
I'm using an ebb36 toolhead connected to the can0 interface.
It's not possible to complete a print using the catalyst can0 interface at 1M bit rate.
After 10 minutes of printing klipper stop with error :
MCU 'toolhead' shutdown: Timer too close
and dmesg is showing lot of errors related to can0 interface :
I was able to complete a print after modifiying can0 interface to use 500k bit rate but errors are still present :
[Mon Feb 26 23:33:29 2024] rockchip_canfd fe580000.can can0: can_put_echo_skb: BUG! echo_skb 0 is occupied!
I'm using the debian 11 / kernel 5.10.160 image with klipper v0.12.0-114-ga77d0790
The text was updated successfully, but these errors were encountered: