MCU connection issues after update

General Discussion
1

Basic Information:

Printer Model:
MCU / Printerboard:
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:

…
After updating klipper on my Pi to V0.12, my MCUs were not connecting due to them still being on V0.11, I then recompiled and flashed the firmware for the Octopus MCU, the U2C and the SB2209 MCU, all were successful, and I can see the Otopus MCU when I run lsusb, and the SB2209 reports a UUID when I query the Canbus. All jumpers on boards back to normal, all boards connected as before. Power cycled a couple of times, but I am still getting an Error for unable to connect to EEBCAN when I reboot. Config files are unchanged and all UUIDs and USB serials remained unchanged and can be queried from the PI. What am I still missing to get the SB2209 back online? klippy.log attached.
klippy (1).log (3.7 MB)

2

Likely your EBBCan is not correctly flashed or connected.

3

Hi thanks, I will flash it again. But it is currently responding to a canbus query and will display the UUID, so I am not sure if the problem is with the firmware.

4

Something that bit me during the v11 to v12 upgrade was that I didn’t realize the canboot.bin now compiles to katapult.bin…

The instructions and ‘convenience’ script I usually use in my klipper/canbus rough notes were still referencing the old filename, and mistakenly flashing the old binary to the EBB36 and Octopus :man_facepalming:

5

This is indeed not an issue. For backwards compatibility, katapult currently compiles both canboot.bin and katapult.bin

6

Not for me…

image

Maybe things changed since I upgraded ~wk ago. Pulling, and rebuilding… Now I see both…

image

Double checking the instructions I normally follow…

7

Just tested:

grafik
grafik757×840 22.8 KB

klipper@bigtreetech-cb1 ~/katapult $ ll ./out/
total 352K
drwxr-xr-x 5 klipper klipper 4.0K 2024-01-29 19:39:48 .
-rw-r--r-- 1 klipper klipper 4.7K 2024-01-29 19:39:48 canboot.bin
-rw-r--r-- 1 klipper klipper 4.7K 2024-01-29 19:39:48 katapult.bin
-rw-r--r-- 1 klipper klipper  26K 2024-01-29 19:39:48 katapult_payload.c
-rwxr-xr-x 1 klipper klipper 4.7K 2024-01-29 19:39:48 katapult.work
-rwxr-xr-x 1 klipper klipper 186K 2024-01-29 19:39:48 katapult.elf
-rw-r--r-- 1 klipper klipper  66K 2024-01-29 19:39:45 compile_time_request.o
-rw-r--r-- 1 klipper klipper  209 2024-01-29 19:39:45 compile_time_request.d
-rw-r--r-- 1 klipper klipper 2.4K 2024-01-29 19:39:45 compile_time_request.c
-rw-r--r-- 1 klipper klipper 1.1K 2024-01-29 19:39:44 compile_time_request.txt
drwxr-xr-x 4 klipper klipper 4.0K 2024-01-29 19:39:44 src
-rw-r--r-- 1 klipper klipper 5.9K 2024-01-29 19:39:36 autoconf.h
drwxr-xr-x 2 klipper klipper 4.0K 2024-01-29 19:39:24 board-generic
lrwxrwxrwx 1 klipper klipper   34 2024-01-29 19:39:24 board -> /home/klipper/katapult/src/lpc176x
drwxr-xr-x 3 klipper klipper 4.0K 2024-01-29 19:39:24 lib
-rw-r--r-- 1 klipper klipper   27 2024-01-29 19:39:24 board-link
drwxr-xr-x 7 klipper klipper 4.0K 2024-01-29 19:39:24 ..
klipper@bigtreetech-cb1 ~/katapult $

I’d be surprised that your katapult does something different to mine

1 Like
8

I see building legacy canboot.bin has been around for 6mths…

image
image1379×140 15.2 KB

State of my dir must’ve been a result of the instructions/scripts/notes I was following…

9

Thanks for this! I will try it in the morning and feedback.

10

You’re welcome, but @Sineos correctly pointed out my theory about canboot.bin not being built was wrong.

Whatever issue(s) I faced during the PITA upgrade was probably due to something else I did wrong. Updated my notes, and will proceed more mindfully during future similar upgrade.

good luck!

11

I dont know exactly what it was, but following your notes step by step with some slight deviation resolved my issues, so thank you!

2 Likes
12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.