Cheeath board can't communcate with Klipper

[vale gull]

Hello community.

I'm desperately trying to get klipper to work with my ender 3 with a cheetah 1.1b card. I tested first with LXC but to see if everything worked I went with an RPI 3
Everything is installed with KIAUH, created the klipper.bin with the correct settings that I found at cheetah.

Then I put my printer on my windows. it is well detected. and I flash it with stm32flash
Everything goes without a problem in view of the end message in screenshot.

I modified in the printer.cfg file the MCU field by putting what I had with the command ls /dev/serial/by-id/* (I only have one connected)

[mcu]
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
restart_method: cheetah

I reconnect it to the RPI but in the klippy.log always the same error which repeats itself again and again.

mcu 'mcu': Starting serial connect
webhooks client 1966164456: New connection
client webhooks 1966164456: Client info {'program': 'Moonraker', 'version': 'v0.8.0-41-g348b7f5'}
mcu 'mcu': Timeout on connect
mcu 'mcu': Wait for identify_response
Traceback (most recent call last):
File "/home/pi/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
params = self.send_with_response(msg, 'identify_response')
File "/home/pi/klipper/klippy/serialhdl.py", line 261, in send_with_response
return src.get_response([cmd], self.default_cmd_queue)
File "/home/pi/klipper/klippy/serialhdl.py", line 318, in get_response
self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
File "/home/pi/klipper/klippy/serialhdl.py", line 253, in raw_send_wait_ack
self._error("Serial connection closed")
File "/home/pi/klipper/klippy/serialhdl.py", line 61, in _error
raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'mcu': Serial connection closed
I checked the chip on my card and it is indeed an STM32F103 as I put in the firmware settings.

Frankly, I don't see what I can do wrong. If anyone can help me it will be a great pleasure.
THANKS

[stiff turret]

So what I needed to do for my set up, was included in a pdf let me see if I can link it.

Essentially I flashed klipper based on the printer settings, then I had to build the Linux side of things

And then in the raspberry pi configs you have to enable it

Let me go grab my laptop rq

Building the micro-controller code
To compile the Klipper micro-controller code, start by conguring it for the "Linux process":
cd ~/klipper/
make menuconfig

In the menu, arrow down to "Microcontroller Architecture" use right arrow to open, arrow down to "Linux process,"
press the spacebar then Q and Y to save and exit.

To build and install the new micro-controller code, run:

sudo service klipper stop
make flash
sudo service klipper start

Optional: Enabling SPI
Make sure the Linux SPI driver is enabled by running and enabling SPI under the "Interfacing
options" menu. Arrow down and press enter.
Arrow down to P4 SPI and press enter

sudo raspi-config

I had hunted for DAYS to get my printer connected but these steps got me going

The first screen for building the microcontroller code

[vale quiver]

@stiff turret have you got a link to these instructions at all?

Damn, didn't work for me - same issue, posted in another ticket.

[vale quiver]

OK - after following the above, I also rebuilt the printer firmware and re-flashed. My printer is connecting now! @stiff turret @vale gull

[stiff turret]

It was a YouTube video let me find it really quick

[stiff turret]

It’s here in the description! It’s the pdf

https://youtu.be/d0xTtVwTtc4?si=epCanDPK6JbsxCkU

[vale quiver]

Legend, thanks man - I got it working in the end - reflashing firmware after your steps was the go. Although now I have a klipper update pending in the Mainsail interface saying I will need to reflash firmware again... reluctant!

[stiff turret]

Awesome! Yeah I don’t know how I missed it, but I’ve been fighting with it for a couple weeks now, but now my extruder won’t calibrate

One step forward at a time

[vale gull]

@stiff turret but I don’t have a creality 4.2.7 but a cheetah 1.1b.

[stiff turret]

I think your most important piece is building the Linux part for the raspberry pi

You would follow the build instructions for your board, then the Linux/Rpi section afterwards, enabling the spi in the config

[vale quiver]

That was more for me I think - apologies for hijacking your thread, bad etiquette.

I followed the instructions further up, then rebuilt/reflashed my firmware and it started working.

Just take a screen shot of the makeconfig screen before you change it to the Linux flash settings, then you don't have to go hunting for the settings for your board again (like I did!)

[spiral solar]

Well without checking the video or the pdf (won’t load right now) the Klipper linux mcu has nothing to do with your board connecting to Klipper. The Linux mcu / process makes Interfaces of your rpi available inside Klipper. Like i2c, gpio pins and what not.

I’ve heared a couple of time now people have trouble with flashing the cheetah board.

Check the fysetc wiki for the correct flashing instructions. https://wiki.fysetc.com/Cheetah_Board/#load-usb-driver

[vale gull]

@rick I have already see this page, but when i compile the firmware with klipper i have a klipper.bin and not a file in hex extension

[vale gull]

@stiff turret So i've done all but the problem is still here 😥.

I'm starting to believe that the cheetah 1.1b just isn't compatible with klipper. It may be impossible to get them to communicate

i have this webhooks client 548293956752: Client info {'program': 'Moonraker', 'version': 'v0.8.0-41-g348b7f5'} so i think that my printer has the firmware in version 0.8.0 no ?

[spiral solar]

That’s your moonraker connecting to Klipper

The .hex file is for marlin. Which is a hole different firmware to Klipper

https://github.com/Klipper3d/klipper/blob/master/config/generic-fysetc-cheetah-v1.1.cfg

This is the example Klipper config for the cheetah 1.1 at the top of the file you can see the needed parameters and how to flash

Which is further described in the upload firmware (Linux) section in the fysect wiki

[vale gull]

After hundreds of tries I finally got it.

My procedure:

• create the firmware with the parameters as in the image
• recover it to have it on my pc
• flash it with stm32flash like this
  stm32flash -w klipper.bin -v -i rts, -dtr -b460800 /dev/ttyUSB0
• turn off the printer and restart it.
• restart the RPI

Thanks for your help all !