Basic Information:
Printer Model: VORON V0.2
MCU / Printerboard: SKR Pico
Host / SBC: BTT Klipper Pi (CB1)
moonraker+klippy-log.zip (2.2 MB)
klippy.log
Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
Hello,
im randomly getting this error mid print. Also the SHAPER_CALIBRATE command randomly stops mid calibrate with no error message. My SKR Pico is configured as a CAN Bridge for the EBB36. I have reflashed the SKR Pico firmware 4 times, compiling the mcu firmware also gave me some errors but when i ran make clean and then make it worked most of the time. Also redid the Klipper install on the CB1 3 times with two diffrent SD-Cards. I have ran 3 diffrent USB cables from the CB1 to the Pico and that did not help either. The USB cables are also not to close to any fans or stepper motors. I dont know how to read these logs, so i could really use some help.
Best regards
Ole
…
1 Like
It seems to me that your original error is “Timeout with MCU”.
And before that, this happens:
b'Got error -1 in can read: (100)Network is down'
b'Got error -1 in can read: (100)Network is down'
My pure guess is that for whatever reason, your main MCU got reset.
I can guess, some power issue.
Hope that helps,
-Timofey
1 Like
Thanks, i will look in to that
This is the error i got while compiling the main mcu firmware. Maybe it is connected to my issue?
*** stack smashing detected : terminated
during GIMPLE pass: slp
src/endstop.c: In function ‘command_endstop_query_state’:
src/endstop.c:102:1: internal compiler error: Aborted
102 | command_endstop_query_state(uint32_t args)
| ^
0x14e7cbb internal_error(char const, …)
???:0
0xffffa761a8ab raise
???:0
0xffffa760747f abort
???:0
0xffffa76dbde7 __fortify_fail
???:0
0xffffa76dbdb3 __stack_chk_fail
???:0
0x1478727 vect_determine_precisions(vec_info)
???:0
0x14666db dr_analyze_innermost(innermost_loop_behavior, tree_node, loop*, gimple const*)
???:0
src/endstop.c:102:1: internal compiler error: Segmentation fault
0x14e7cbb internal_error(char const*, …)
???:0
0x152e873 backtrace_full
???:0
0x14e6867 diagnostic_action_after_output(diagnostic_context*, diagnostic_t)
???:0
0x14e6b93 diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)
???:0
0x14e7cbb internal_error(char const*, …)
???:0
0xffffa761a8ab raise
???:0
0xffffa760747f abort
???:0
0xffffa76dbde7 __fortify_fail
???:0
0xffffa76dbdb3 __stack_chk_fail
???:0
0x1478727 vect_determine_precisions(vec_info*)
???:0
0x14666db dr_analyze_innermost(innermost_loop_behavior*, tree_node*, loop*, gimple const*)
???:0
arm-none-eabi-gcc: internal compiler error: Segmentation fault signal terminated program lto1
Please submit a full bug report, with preprocessed source (by using -freport-bug).
See https://gcc.gnu.org/bugs/ for instructions.
make[1]: *** [/tmp/ccDd15Sa.mk:5: /tmp/ccSUc0aq.ltrans1.ltrans.o] Error 4
make[1]: *** Waiting for unfinished jobs…
lto-wrapper: fatal error: make returned 2 exit status
compilation terminated.
collect2: fatal error: lto-wrapper returned 1 exit status
compilation terminated.
make: *** [Makefile:73: out/klipper.elf] Error 1
make: *** Deleting file ‘out/klipper.elf’
[ERROR] Unexpected error:
Command ‘make PYTHON=python3 KCONFIG_CONFIG=/home/biqu/klipper/.config’ returned non-zero exit status 2.
[ERROR] Command ‘make PYTHON=python3 KCONFIG_CONFIG=/home/biqu/klipper/.config’ returned non-zero exit status 2.
[ERROR] Building Klipper Firmware failed!
Can you please format that code as Preformatted text for it appears that the text is a bit messed up due to the reformatting by markdown.
2 Likes
Thanks, i edited it to preformated text.
1 Like
lost-conectionl-log.zip (338.3 KB)
UPDATE
The compiler error whilst compiling the firmware for the mcu´s came from the V3.0.0. Debian 12 CB1 image. Went back to the V2.3.4 Debian 11 image and now it is working properly, found this out throug this GitHub post The BTT PI 1.2 is unstable with latest V3.0.0 image .
I reconfigured everything, but now I’m losing the connection to the mcu instead of being unable to update it. Maybe the logs have have some insights on what is causing the problem? I still dont know how to read the properly.
Also lost connection to the EBB36 once.
ebb-lost-connection.zip (1.2 MB)
I think the wire from my CAN-tranciver to my ebb36 might be the Problem.
