Cannot obtain mcu serial following firmware update

General Discussion
1

Basic Information:

Printer Model: CUSTOM
MCU / Printerboard: MELLOW FLY DP5
Host / SBC: RPi 2b
klippy.log
console.txt - a snip of the output at my ssh terminal
klippy (1).log (46.9 KB)
console.txt (2.5 KB)

Cannot obtain mcu serial following mcu firmware update to include CAN bridge

Firstly the FLY-DP5 board has been working with the RPi. I recently obtained the FLY-SHT36V3 tool board and it requires the mcu is flashed with the USB Bridge to CAN Firmware

The console.txt attached shows that i complete compilation of the new klipper.bin.

Then with the DP5 in flashing mode which is confirmed with a call to lsusb which shows, ID 1d50:6177 OpenMoko, Inc. stm32f072xb which is what i want to see according to the documentation linked above.

I then flash the device, receive some information i dont understand, but nothing suggesting failure. Then you can see i call lsusb again, the device is no longer in flashing mode FLYDP5 now appears as,

Bus 001 Device 030: ID 1d50:606f OpenMoko, Inc. Geschwister Schneider CAN adapter

which incidentally is what i will later want to see when i eventually get to install the SHT36.

However the problem is that calling ls /dev/serial/by-id/* to retrieve my serial doesn’t work which means I get a start-up error in mainsail too of course.
ls: cannot access '/dev/serial/by-id/*: No such file or directory

Does anyone have suggestions about what to try?

Thanks in advance.
…

2

You were successful with flashing the board as a USB2CAN adapter, not as a USB2TTL.
So, there is no more serial.
There is a can0 network device in the system, which would be used for all communications.

Hope that helps.

1 Like
3

Thanks and possibly helps, the following shows two CAN bus devices attached to the RPI, the mcu running Klipper firmware and SHT36 tool board running the Katapult (CanBoot) firmware.

In this regard im right where i want to be, ready to install the klipper firmware onto the SHT36V3 tool board

The issue remains printer.cfg needs a “serial” id for the motherboard to initialise for printing. So im still at a loss currently.

aps@raspi:~/klipper $ ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Found canbus_uuid=2f737b084154, Application: Klipper
Found canbus_uuid=b83afb2a58b6, Application: CanBoot
Total 2 uuids found
4

You just need to define MCU differently.

[mcu]
canbus_uuid: ...
canbus_interface: can0
1 Like
5

Ah ha

So simply removing serial and setting canbus_uuid to my mcu uuid (2f737b084154) works.

Ive sucessfully flashed klipper to the toolboard now as well, so next step is add it to printer.cfg and sort out the wiring to the various peripherals!

Thanks so much for the nudge in the right direction!

1 Like