Ender 3 V3 SE GD32F303RET6 the firmware won't flash

Basic Information:

Printer Model: Creality Ender 3 V3 SE
MCU / Printerboard: CR4NS200320C13 on GD32F303RET6
Host / SBC: ThinClient HP T520
klippy.log

klippy.log (167.9 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Greetings.
Printer: Creality Ender 3 V3 SE CR4NS200320C13 on GD32F303RET6
I installed KLIPPER according to the manual using KIAUH on a ThinClient HP T520 on Debian 12. I receive the following messages: “Printer is not ready
The klippy host software is attempting to connect. Please
retry in a few moments.” and “mcu ‘mcu’: Unable to connect
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer”.
When connecting to the USB printer host, the device sees the path as in printer.cfg.
It seems that my Creality Ender 3 V3 SE CR4NS200320C13 with GD32F303 printer is not flashed. I’ve used different memory cards, different settings when creating the firmware, renamed the firmware name, but the printer still won’t flash, and the printer screen always displays blue wallpaper.
I can flash the stock firmware, but not the klipper firmware. I’ve tried flashing the firmware from this forum on a similar board, but it didn’t work.

The output of the command ls /dev/serial/by-id/*
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

Its from printer.cfg:

serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 #ls /dev/serial/by-id/*

Welcome common,

indeed it looks like your printerboard is not running Klipper properly.

Could you please describe your Klipper installation in detail. What were your first settings (processor model, bootloader offset, communication interface, etc…)?

Greetings.
Thank you for responding.
Printer Ender 3 V3 SE, board CR4NS200320C13 on GD32F303RET6
When creating the firmware, I followed the standard steps:

(SSH)

cd ~/klipper

make menuconfig

Settings:

Micro-controller Architecture - (X) STMicroelectronics STM32

Processor model - (X) STM32F103

[*] Disable SWD at startup (for GigaDevice stm32f103 clones)

Bootloader offset - (X) 28KiB bootloader

Communication interface - (X) Serial (on USART1 PA10/PA9)

Q Quit (promts for save) → (Y)es

make

Copy and rename klipper.bin on SD card.

Flash.

You have a light hand. Now I have re-created the firmware and was able to flash the printer. Two weeks of suffering are over. I didn’t do anything new, just repeated what I did earlier.

Today, a miracle happened. I was able to flash the klipper to my printer. I didn’t do anything new, I just repeated the process again.
Previously, I had used different settings when creating the firmware, reinstalled the software on the host several times, changed the memory cards, and connected different USB cables. However, it didn’t work.

The settings I used today for creating the firmware are standard for the GD32F303RET6:

The microcontroller architecture is (X) STMicroelectronics STM32

Processor model - (X) STM32F103

[*] Disable SWD at startup (for GigaDevice stm32f103 clones)

Bootloader offset - (X) 28 KB bootloader

Communication interface - (X) serial (on USART1 PA10/PA9)

Reformatted the SD card into a FAT32 file system with a 4096-byte cluster size.

Renamed klipper.bin to the name with the current date and time, inserted the card into the printer, turned on the printer, waited 30 seconds, restarted the printer, connected the printer to the host using a USB cable, restarted the services on the host, clicked on “FIRMWARE_RESTART”, and the printer’s temperature data appeared on the fluidd screen.

I also received the following message: " Unable to open temperature file ‘/sys/class/thermal/thermal_zone0/temp’ "
I simply commented out the lines in printer.cfg
If I understand correctly, this is the temperature from the host’s sensors. I have it called “temperature_sensor Host”, but it may have a different name or be missing.
#[temperature_sensor Host]
#sensor_type: temperature_host
#min_temp: 10
#max_temp: 100

Congrats.

If you need help with

please post a fresh klippy.log.

attached

klippy (1).log (1.0 MB)

When I uncommented the above lines, the host’s connection to the printer was interrupted.

I think your printer.cfg (regarding your last klippy.log) is correct.

I stumbled about this thread Unable to open temperature file '/sys/class/thermal/thermal_zone0/temp when host reboots - #3 by TreoWayne, you might read the thread from the beginning.

You use Debian 12 which is Bookworm. So I think you may be a victim of this probable bug.

Thanks @TreoWayne and @Sineos.

Thanks for the link.

I’ve tried this before. In my case, the problem is that as soon as I uncomment the “temperature_sensor Host” lines, the printer immediately loses connection with the host. I’ll avoid this for now.

This host has passive cooling and low heat generation.

What do you see with

cat /sys/class/thermal/thermal_zone0/temp

cat: /sys/class/thermal/thermal_zone0/temp: No such file or directory