Can 0 crashes when adding [Probe] pin

General Discussion
1

Basic Information:

Printer Model: Voron SwitchWire
MCU / Printerboard: SKR 3 Mini E3 V3 and EBB SB2209
Host / SBC : Raspberry Pi 3+ running Dietpi 10
klippy.log

klippy(5).log (31.8 KB)

Describe your issue:

I am building a new Switchwire running an SKR Mini E3 V3 with a BTT EBB SB2209 toolhead via CANbus. The system is stable and the EBBCan UUID (99de70523e3f) is visible until I define a [probe] section.As soon as [probe] is active in the config, the Klipper service fails to initialize the MCU, the can0 interface on the Raspberry Pi goes down (OSError 19), and the UUID disappears from canbus_query. This happens regardless of the pin assigned (tried PC13 and PB6 ) and occurs even with the physical probe unplugged from the toolhead.

Thank you for any help in advance,

2

I guess, it is this board:

So, there is no PC14

[probe]
pin = PC14
x_offset = 1
y_offset = 25
z_offset = 1

This is a wrong pin, PC14 is the OSC-IN.

We actually have safeguards, but they are configured for PF0, PF1, which are absent on this package, and PC14/PC15 are used instead.
https://www.st.com/resource/en/datasheet/stm32g0b1cc.pdf

And we can’t block them, they are used at least on Manta M8P V1.
That’s is unfortunate.

3

Thanks for the reply nefelim4ag ,That is the correct toolhead board I’m using. Then the Can0 connector goes to a big tree tech U2C v2 . I was just using PC14 for testing at one point along with PB6 to see if I I could get it to work.
I just set it back to

probe

pin = ^EBBCan: PC13
x_offset = 0
y_offset = 25
z_offset = 0

and uploaded the new klippy log. Its just strange I can define everything else in the printer.cfg up to that point before it crashes the Pi 3 or Can0

klippy(5).log (31.8 KB)

4

Alas, idk, log is cut, but regardless, it should work.
IDK, why your MCU is missing every time, you can try to connect the ebb by usb temporary, maybe it would help to get the idea, maybe even with USB power.