Issue with SKR3EZ and a EBB36 V1.2

General Discussion
1

I have a SKR3EZ (with stm32h723) and a EBB36 V1.2.
Have been trying to get them to work together and play nice for weeks now.
However most i can manage is to get the SKR and EBB to talk to each other.
I can see only one canbus_uuid. This appears to be the EBB board. If i disconnect this, there is no uuid found.

With EBB connected:
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Found canbus_uuid=fffe1dfc5654, Application: Klipper
Total 1 uuids found

Without EBB:
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Total 0 uuids found

Please help, thanks in advance!

2

Hello @Jurre !

This thread is almost a year old. Things have changed. I made a new Thread from it.

Please attach the klippy.log to your next post.

1 Like
3

Hi @EddyMI3D,

Thanks for splitting this of in an new thread.
I currently don’t have access to the hardware.
I will post my log files and screenshots of the ‘make config’ i used for both the EBB and SKR as soon as possible.

1 Like
4

Hi here,
here i am again.

My SKR and EBB36 firmware is made with the following settings:

SKR:
[*] Enable extra low-level configuration options
Micro-controller Architecture (STMicroelectronics STM32) —>
Processor model (STM32H723) —>
Bootloader offset (128KiB bootloader (SKR SE BX v2.0)) —>
Clock Reference (25 MHz crystal) —>
Communication interface (USB to CAN bus bridge (USB on PA11/PA12)) —>
CAN bus interface (CAN bus (on PB8/PB9)) —>
USB ids —>
(500000) CAN bus speed

EBB:
[*] Enable extra low-level configuration options
Micro-controller Architecture (STMicroelectronics STM32) —>
Processor model (STM32G0B1) —>
Bootloader offset (No bootloader) —>
Clock Reference (8 MHz crystal) —>
Communication interface (CAN bus (on PB0/PB1)) —>
(500000) CAN bus speed
() GPIO pins to set at micro-controller startup

This is what i see when trying to detect the EBB and SKR.

Jurre@raspberrypi:~/klipper $ ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Found canbus_uuid=fffe1dfc5654, Application: Klipper
Total 1 uuids found

I figured the detected device is the EBB, since when i unplug is i have ‘0 uuids found’

I have attached my klippy.log here:
klippy.log (27.0 KB)

Hopefully this helps.

5

I could not get it to work after multiple attempts and different solutions.
In the end i decided to buy a U2C board, installed the candlelight firmware on it and now everything works!

1 Like
6

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