EBB42problem

General Discussion
1

Basic Information:

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

…

Since the last update, I’ve been getting these warning messages. When I reflash the EBB firmware, it’s no longer recognized at all. Fortunately, I still have the old firmware, which works, but with error messages.
What can I do now?

Schermafbeelding 2026-02-25 201733
Schermafbeelding 2026-02-25 2017331272×1043 188 KB

2

Please attach the requested klippy.log to your next post.

1 Like
3

As a side note, I have two printers: one with a Raspberry Pi3 running Linux Bullseye firmware and an MKS SgenL motherboard, and the other with a Raspberry Pi3 running Linux Bookworm firmware and an MKS Robin nano motherboard. Both are experiencing the same issue.

4

Here also the klippy log.

klippy (3).log (917.9 KB)

5

This is your old configuration.
It looks like a CAN device to me, not the USB.

Loaded MCU 'EBBCan' 120 commands (v0.12.0-310-gef7534686-dirty-20241001_205200-raspberry 
MCU 'EBBCan' config: ADC_MAX=4095 BUS_PINS_i2c1_PA9_PA10=PA9,PA10 BUS_PINS_i2c1_PB6_PB7=PB6,PB7 BUS_PINS_i2c1_PB8_PB9=PB8,PB9 BUS_PINS_i2c2_PB10_PB11=PB10,PB11 BUS_PINS_i2c2_PB13_PB14=PB13,PB14 BUS_PINS_i2c3_PB3_PB4=PB3,PB4 BUS_PINS_i2c3_PC0_PC1=PC0,PC1 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi2_PB2_PB11_PB10=PB2,PB11,PB10 BUS_PINS_spi2a=PC2,PC3,PB10 BUS_PINS_spi3=PB4,PB5,PB3 CANBUS_FREQUENCY=1000000 CLOCK_FREQ=64000000 MCU=stm32g0b1xx PWM_MAX=255 RECEIVE_WINDOW=192 RESERVE_PINS_CAN=PB0,PB1 RESERVE_PINS_crystal=PF0,PF1 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1

I assume, there is actual CAN BRIDGE somewhere.

This is your new configuration (from ========= Last MCU build config =========):

[*] Enable extra low-level configuration options
    Micro-controller Architecture (STMicroelectronics STM32)  --->
    Processor model (STM32G0B1)  --->
    Bootloader offset (8KiB bootloader)  --->
    Clock Reference (8 MHz crystal)  --->
    Communication interface (USB to CAN bus bridge (USB on PA11/PA12))  --->
    CAN bus interface (CAN bus (on PB0/PB1))  --->
    USB ids  --->
(1000000) CAN bus speed
[*] Optimize stepper code for 'step on both edges'
()  GPIO pins to set at micro-controller startup

Have you decided to connect EBB by the USB cable right after the update?

-Timofey

6

No, it is connected again just as it was, so via the CAN bus, it should be fine.