Unable to connect to printer

[DIYLAB-DE]

First, thank you for clipping the SV06 and investing time.

Unfortunately, no connection is possible.
The USB connection is shown with ls /dev/serial/by-id/ as /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0, but Mainsail/Klipper does not connect.
I tried your firmware and created some custom versions, no success.
I'm not even sure if the firmware was flashed correctly, since the display doesn't show anything.
The Marlin firmware from the Sovol site I can flash without problems and the display then also shows something again.
In my opinion, it can not be due to my Mainsail/Klipper installation, since it worked perfectly with the Ender-3 S1 PRO.

Can you help me?

[chrizzo84]

The display cannot show anything if printer isn't connected.
I also used this bin and cfg and it worked like a charm.
Are you sure that your usb connection is setup correctly?

[DIYLAB-DE]

I am relatively sure that the MCU section in printer.cfg is correct.
But I am not sure if the flash process was executed correctly with your firmware.
I used a FAT32 freshly formatted SD card with 8GB and renamed your file to firmware.bin
Where else could I look?
Baud rate is 250000?

I have a MCU from Gigadevice on the printer board.
Can you please take a screenshot with your configurations for the firmware?
So the menu that you have set in make menuconf?

[chrizzo84]

I just took the bin file from this repo.
Do you get any errors in Mainsail, if yes, what does it tell you?

[schoubi]

what is saying /tmp/klippy.log ?

[spinixguy]

I am relatively sure that the MCU section in printer.cfg is correct. But I am not sure if the flash process was executed correctly with your firmware. I used a FAT32 freshly formatted SD card with 8GB and renamed your file to firmware.bin Where else could I look? Baud rate is 250000?

I have a MCU from Gigadevice on the printer board. Can you please take a screenshot with your configurations for the firmware? So the menu that you have set in make menuconf?

you do not need to make the firmware again, that is why I posted it here. Try naming it something like todays date i.e 120320220700.bin and then place the file on an sd card by itself. These boards wont let you flash the same file over again so the name has to change each time you flash it.

[mutlubasdas]

You're definitely on point! I was so used to octopus boards and kept naming it "firmware.bin" over and over again. But I just changed the name and it worked.
Appreciate your work with this! Saved me a good deal of time.
Thanks.