# Getting orange pi 3 lts + klipper working with anycubic kobra 2 neo

**URL:** <https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278>\
**Category:** General Discussion\
**Created:** [October 31, 2023, 8:47am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278 "2023-10-31T08:47:21Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [October 31, 2023, 8:47am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/1 "2023-10-31T08:47:22Z")

</div>

### Basic Information:

Printer Model: Anycubic kobra 2 neo  
 MCU / Printerboard: Not sure, but microcontroller lablings are GD32F303 RGT6  
 `klippy.log` [klippy.log](https://klipper.discourse.group/uploads/short-url/tVnrvt091CxSqKIFxMTDF63Po9i.log) (169.9 KB)

I use lts raspbian minimal installation on my board. Tried to search for this problem for 2 days straight. Everything works, except MCU. I get the same error everytime.

 ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/0/0913d7c0cca5335ee17e5be8856756f7fa07160b.png)  
Yesterday i was working on this problem till 3am and found almost nothing. I hope that smart people can help me with this issue. 😅

Edited: You can find working configs and make requests and suggestions in the link below.  
[Anycubic kobra 2 neo configs](https://klipper.discourse.group/t/anycubic-kobra-2-neo-v0-7-1-configs-less-unstable-now/13009)

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [October 31, 2023, 10:48am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/2 "2023-10-31T10:48:12Z")

</div>

See [CR6SE printer firmware installation has consistently failed - #2 by Sineos](https://klipper.discourse.group/t/cr6se-printer-firmware-installation-has-consistently-failed/11188/2)

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [October 31, 2023, 10:49am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/3 "2023-10-31T10:49:58Z")

</div>

i think i’ve already added mine to dialout, but not tty. Let me reboot and double check

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [October 31, 2023, 10:56am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/4 "2023-10-31T10:56:10Z")

</div>

okay, the error is the same. Here are the new logs  
[klippy.log](https://klipper.discourse.group/uploads/short-url/5RMmvmlmJ90K5tBuwv4HYygG8vg.log) (233.5 KB)

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [October 31, 2023, 11:41am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/5 "2023-10-31T11:41:37Z")

</div>

No, the error is not the same.

First log:

```auto
mcu 'mcu': Unable to open serial port: [Errno 13] could not open port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0: [Errno 13] Permission denied: '/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0'

```

Second log:

```auto
mcu 'mcu': Timeout on connect
MCU error during connect
...
serialhdl.error: mcu 'mcu': Unable to connect

```

Which would indicate that the board is not correctly flashed. Check with [How-To Trouble-Shoot](https://klipper.discourse.group/t/how-to-trouble-shoot/6326#linux-dmesg-5) to see if and how the board registers to the Linux OS

As for the Kobra 2 Neo, I would not be aware of an existing config file and build instructions, so I do not know on which reference you build it.

From your log

```auto
========= Last MCU build config =========
CONFIG_LOW_LEVEL_OPTIONS=y
# CONFIG_MACH_AVR is not set
# CONFIG_MACH_ATSAM is not set
# CONFIG_MACH_ATSAMD is not set
# CONFIG_MACH_LPC176X is not set
# CONFIG_MACH_STM32 is not set
# CONFIG_MACH_HC32F460 is not set
# CONFIG_MACH_RP2040 is not set
# CONFIG_MACH_PRU is not set
# CONFIG_MACH_AR100 is not set
# CONFIG_MACH_LINUX is not set
CONFIG_MACH_SIMU=y
CONFIG_BOARD_DIRECTORY="simulator"
CONFIG_CLOCK_FREQ=20000000
CONFIG_SERIAL=y
CONFIG_SIMULATOR_SELECT=y
CONFIG_SERIAL_BAUD=115200
CONFIG_USB_VENDOR_ID=0x1d50
CONFIG_USB_DEVICE_ID=0x614e
CONFIG_USB_SERIAL_NUMBER="12345"
CONFIG_WANT_GPIO_BITBANGING=y
CONFIG_WANT_DISPLAYS=y
CONFIG_WANT_SENSORS=y
CONFIG_WANT_LIS2DW=y
CONFIG_WANT_SOFTWARE_SPI=y
CONFIG_CANBUS_FREQUENCY=1000000
CONFIG_INITIAL_PINS=""
CONFIG_HAVE_GPIO=y
CONFIG_HAVE_GPIO_ADC=y
CONFIG_HAVE_GPIO_SPI=y
CONFIG_HAVE_GPIO_HARD_PWM=y
CONFIG_INLINE_STEPPER_HACK=y

```

These `make menuconfig` parameters definitively are wrong, but since I do not have better ones, I cannot provide further guidance.

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 7, 2023, 5:08pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/6 "2023-11-07T17:08:00Z")

</div>

Ok, i was not sure about klipper, cause flashing my very new 3d printer is pretty scary. But now i think that i could try. I have read discussions about installing klipper on the board with the same microcontroller as mine [(here)](https://klipper.discourse.group/t/installing-klipper-on-ender-3-4-2-2-board-and-gd32f303-chip/8165) but i am not sure how to do it properly. Do you have any instructions for configuring and flashing a firmware to my board?  
Thank you in advance for any help.

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 7, 2023, 9:42pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/7 "2023-11-07T21:42:47Z")

</div>

also i’ve found the board model. It is TriGorilla Gen V4.0.1

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 8, 2023, 8:11am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/8 "2023-11-08T08:11:59Z")

</div>

Ok. I tried flashing it with SD card by putting firmware.bin file on it but after several tries of powering on and onn my printer doesn’t flash.  
I tried flashing it with “normal” method in kiauh but got this error:

```auto
Failed to flash to /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0: Error running dfu-util

If the device is already in bootloader mode it can be flashed with the
following command:
  make flash FLASH_DEVICE=1eaf:0003
  OR
  make flash FLASH_DEVICE=1209:beba

If attempting to flash via 3.3V serial, then use:
  make serialflash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

make: *** [src/stm32/Makefile:111: flash] Ошибка 255

```

I am pretty much stuck. Can you help me with that, please?

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 8, 2023, 9:14am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/9 "2023-11-08T09:14:36Z")

</div>

```auto
zamonary1@orangepi3-lts:~/klipper$ make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
  Flashing out/klipper.bin to /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
Entering bootloader on /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
Device reconnect on /sys/devices/platform/soc/5101400.usb/usb5/5-1/5-1:1.0/ttyUSB0
sudo dfu-util -p 5-1 -R -a 2 -D out/klipper.bin

dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
dfu-util: No DFU capable USB device available

Failed to flash to /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0: Error running dfu-util

If the device is already in bootloader mode it can be flashed with the
following command:
  make flash FLASH_DEVICE=1eaf:0003
  OR
  make flash FLASH_DEVICE=1209:beba

If attempting to flash via 3.3V serial, then use:
  make serialflash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

make: *** [src/stm32/Makefile:111: flash] Ошибка 255

```

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [November 8, 2023, 11:02am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/10 "2023-11-08T11:02:02Z")

</div>

Unfortunately, I do not know the board or if it has any peculiarities.

_Theoretically_ the instructions here [https://github.com/Klipper3d/klipper/blob/9e765daeedb2adf7641b96882326b80aeeb70c93/config/printer-creality-ender3-v2-neo-2022.cfg](https://github.com/Klipper3d/klipper/blob/9e765daeedb2adf7641b96882326b80aeeb70c93/config/printer-creality-ender3-v2-neo-2022.cfg) should allow you to flash the board.

Make sure to copy only the `klipper.bin` to the SD card and rename it to something random like blabla.bin

Even if you then manage to flash the board, the real challenge will be the `printer.cfg` with the relevant pin mapping.

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 8, 2023, 11:06am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/11 "2023-11-08T11:06:59Z")

</div>

also, look what i found [How to install Klipper on Anycubic Kobra 2 - Function3D](https://function3d.xyz/en/how-to-install-klipper-on-anycubic-kobra-2/)  
it is for kobra 2 (not neo) but i should try

[config.zip](https://klipper.discourse.group/uploads/short-url/ixeOBltGCRk3r52rmit2apVWQWe.zip) (4.0 KB)  
(downloaded from here)

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [November 8, 2023, 11:12am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/12 "2023-11-08T11:12:59Z")

</div>

Yes, this is what I found as well. The big issue is that this is based on a HC32F460 MCU and according to your description the board has GD32F303.

I do not know if both chips are pin-compatible, but I would doubt it. If you are lucky, and they are pin-compatible, the cfg could be used.

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 8, 2023, 11:56am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/13 "2023-11-08T11:56:59Z")

</div>

i’m really frustrated because i just cannot make this work. The board constantly boots to marlin instead. I reformatted the sd card 2 times and it gave me nothing. I gues i’ll go and rest a little.

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [November 8, 2023, 1:14pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/14 "2023-11-08T13:14:27Z")

</div>

Have you tried to rename the `klipper.bin` file to `firmware.bin`?

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 8, 2023, 1:15pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/15 "2023-11-08T13:15:33Z")

</div>

I used klipper.bin, kipper1.bin 123.bin, firmware.bin and firmware1.bin. No result.

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 13, 2023, 11:40am UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/16 "2023-11-13T11:40:19Z")

</div>

Ok. I got in contact the anycubic support. They said that installing klipper on my printer will ruin the official warranty and sent me the only official firmware that they currently have. I think i should share it to you guys and other people looking for anycubic kobra 2 neo firmware. 😁  
[Link to google drive that they sent to me (click)](https://drive.google.com/drive/folders/1TNi5x2rCg4tpmZITlUiWC4calGwWwqNz)

[ak2neo-1.5.6.3.zip](https://klipper.discourse.group/uploads/short-url/3uaGlZo8ZcqN7RFOXeeUGE7Jty9.zip) (154.8 KB)

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [November 13, 2023, 3:27pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/17 "2023-11-13T15:27:06Z")

</div>

??? Did they say why it would void the official warranty?

I would think that the only (valid) reasons for making a statement like this is because there is danger of damaging the product or could cause personal harm to the user.

I would suspect that they are making this statement because they don’t want to support Klipper but what level of support do they give if you want to do something like add a filament runout sensor, which would require a firmware change or wanted to change the print surface.

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 13, 2023, 3:29pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/18 "2023-11-13T15:29:33Z")

</div>

he said)

[image](https://i.imgur.com/B1SkSJm.png)

---

<div class="post-metadata">

**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\
**Post date:** [November 13, 2023, 3:57pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/19 "2023-11-13T15:57:25Z")

</div>

Not helpful.

I’m curious as to what other people here think.

EDIT

Sorry, @zamonary1 I didn’t mean to imply that you weren’t being helpful, just that Anycubic wasn’t giving a reasonable or helpful answer.

---

<div class="post-metadata">

**Author:** ![zamonary1](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/zamonary1/32/8275_2.png) [@zamonary1](https://klipper.discourse.group/u/zamonary1)\
**Post date:** [November 13, 2023, 4:00pm UTC](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278/20 "2023-11-13T16:00:42Z")

</div>

idk, i suggest that kobra 2 neo is unpopular model and this raises a problem with making configs and testing them. I really want to get klipper working on my board but i’ve never used it before. If you have any ideas then please let me know.

[Next page](https://klipper.discourse.group/t/getting-orange-pi-3-lts-klipper-working-with-anycubic-kobra-2-neo/11278.md?page=2)
