Armbian Issue with USB (C4)

[rooted]

I've been using a Pi 3B running OctoPi to drive my 3D printer and figured I would break out the C4 which should be better in every way but unfortunately I can't even get through one print without losing serial connection to the printer and my print failing.

Log: http://ix.io/2E2n

Code: Select all

BOARD=odroidc4
BOARD_NAME="Odroid C4"
BOARDFAMILY=meson-sm1
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=f2756e3b-dirty
DISTRIBUTION_CODENAME=focal
DISTRIBUTION_STATUS=supported
VERSION=20.08.22
LINUXFAMILY=meson64
BRANCH=current
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image

@igorpec Any idea

[igorpec]

@igorpec Any idea

Yesterday one asked the same, but by using Orange pi Zero and we confirmed its not Armbian specific problem. It seems to be a problem in modern kernels:
https://www.facebook.com/groups/1483270 ... 579198636/ (probably you need to join this group)

Solution unknown ATM.

[tobetter]

@rooted, I am running ODROID-N2 to run OctoPi on top of Debian Buster with Linux kernel 4.9, I've not noticed USB issue and stable.

Code: Select all

Linux buster 4.9.205-odroidn2-arm64 #1 SMP PREEMPT Wed, 01 Apr 2020 14:55:39 +0000 aarch64
 _   _               _ _                        _ 
| | | | __ _ _ __ __| | | _____ _ __ _ __   ___| |
| |_| |/ _` | '__/ _` | |/ / _ \ '__| '_ \ / _ \ |
|  _  | (_| | | | (_| |   <  __/ |  | | | |  __/ |
|_| |_|\__,_|_|  \__,_|_|\_\___|_|  |_| |_|\___|_|
                                                  
  ___  ____  ____   ___ ___ ____        _   _ ____  
 / _ \|  _ \|  _ \ / _ \_ _|  _ \      | \ | |___ \ 
| | | | | | | |_) | | | | || | | |_____|  \| | __) |
| |_| | |_| |  _ <| |_| | || |_| |_____| |\  |/ __/ 
 \___/|____/|_| \_\\___/___|____/      |_| \_|_____|
                                                    

Welcome to Debian GNU/Linux 10 (buster)
Saturday, 14 November 2020, 12:37:36 PM
Up time:     6 days, 16:03:55
Free memory: 3159664 / 3799260 kB
IP:          192.168.0.12

[!] Please visit 'https://launchpad.net/odroid-image' to report a bug

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Nov  7 20:33:56 2020 from 192.168.0.100
tobetter@buster:~$ ps aux | grep Octo
tobetter  1253  0.0  0.0   2824   660 pts/1    S+   12:37   0:00 grep Octo
tobetter  2184  0.7  3.4 2178956 131792 ?      S<l  Nov07  74:00 /home/tobetter/OctoPrint/venv/bin/python2 /home/tobetter/OctoPrint/venv/bin/octoprint serve --config /home/tobetter/.octoprint/config.yaml --basedir /home/tobetter/.octoprint --port=5000

[rooted]

@igorpec Any idea

Yesterday one asked the same, but by using Orange pi Zero and we confirmed its not Armbian specific problem. It seems to be a problem in modern kernels:
https://www.facebook.com/groups/1483270 ... 579198636/ (probably you need to join this group)

Solution unknown ATM.

Do you not provide a less modern kernel? Just saying it's not Armbian specific is not helping.

[rooted]

@rooted, I am running ODROID-N2 to run OctoPi on top of Debian Buster with Linux kernel 4.9, I've not noticed USB issue and stable.

Thanks for the information, if I can't get some support for Armbian I will definitely switch, second time running Armbian and second time I've had issues to start with.

*edit*
I am trying Ubuntu, when I tried to switch to the older meson64 kernel on Armbian it didn't boot.

[igorpec]

Thanks for the information, if I can't get some support for Armbian I will definitely switch, second time running Armbian and second time I've had issues to start with.

You got attention and I point you to the source of the problem. You can say thanks or not https://www.armbian.com/donate If you want that we provide you a solution of your problem, than this is called a professional service. Which you will never get just like that under your existing support contract. Besides there is long list of people that doesn't understand their support contracts.

Use Armbian with kernel 4.9.y and it will work. We keep it solo for the reason that you can't say "Armbian is not working" ... it uses Hardkernel / stock hardware interface.

If you want to run modern kernel or if you want some random R&D, invest your own time or money. Support on our costs is limited and certainly doesn't cover expensive debug or development per request. You should know that.

I already saved you weeks by narrowing the problem down, but I don't need this function. You do.

[igorpec]

I am trying Ubuntu, when I tried to switch to the older meson64 kernel on Armbian it didn't boot.

Ofc you didn't read warning - switching kernels can break and especially in this case since boot loader is different, we need to have fat boot partition for C4 due broken FAT support in u-boot ... we will drop legacy asap since we have no intention to waste time there.

Download image or ... go on the path of making older mainline kernel (perhaps 5.4.y) image by adding support for C4. Its possible to make a custom kernel custom rootfs with help of https://github.com/armbian but its some work ... and you your image will need to have frozen kernel.

[tobetter]

@rooted, I am running ODROID-N2 to run OctoPi on top of Debian Buster with Linux kernel 4.9, I've not noticed USB issue and stable.

Thanks for the information, if I can't get some support for Armbian I will definitely switch, second time running Armbian and second time I've had issues to start with.

*edit*
I am trying Ubuntu, when I tried to switch to the older meson64 kernel on Armbian it didn't boot.

I think you should try Debian, not Ubuntu, since OctoPi and its plugins are pretty much developed for RPi and package dependencies. I've tried Ubuntu 19.04 earlier with no luck even I just use the simple functions.

[rooted]

I am trying Ubuntu, when I tried to switch to the older meson64 kernel on Armbian it didn't boot.

Ofc you didn't read warning - switching kernels can break and especially in this case since boot loader is different, we need to have fat boot partition for C4 due broken FAT support in u-boot ... we will drop legacy asap since we have no intention to waste time there.

Download image or ... go on the path of making older mainline kernel (perhaps 5.4.y) image by adding support for C4. Its possible to make a custom kernel custom rootfs with help of https://github.com/armbian but its some work ... and you your image will need to have frozen kernel.

If you can't speak to me without condescending overtones then I would appreciate if you didn't respond at all. Unless you use your armbian tool you wouldn't see the warning now would you!

[rooted]

@rooted, I am running ODROID-N2 to run OctoPi on top of Debian Buster with Linux kernel 4.9, I've not noticed USB issue and stable.

Thanks for the information, if I can't get some support for Armbian I will definitely switch, second time running Armbian and second time I've had issues to start with.

*edit*
I am trying Ubuntu, when I tried to switch to the older meson64 kernel on Armbian it didn't boot.

I think you should try Debian, not Ubuntu, since OctoPi and it plugins are pretty much developed for RPi and package dependencies. I've tried Ubuntu 19.04 earlier no luck even I just use the simple functions.

When you used Ubuntu did you have USB issues or issues with OctoPrint? My issues seem to stem from the kernel not OctoPrint.

Do you have a link to the minimal debian image you are using? I flashed the latest Hardkernel Ubuntu (ubuntu-20.04-4.9-minimal-odroid-c4-hc4-20201015.img.xz) and installed OctoPrint without issues and the first short print I did actually finished but it was just a 200x200 layer test I made. But my next actual print failed on the second layer with this:

Code: Select all

[ 5233.019022] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 5233.019101] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 7422.988666] usb 1-1.1: new full-speed USB device number 6 using xhci-hcd
[ 7423.138004] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 7423.138010] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7423.138013] usb 1-1.1: Product: USB Serial
[ 7423.167014] ch341 1-1.1:1.0: ch341-uart converter detected
[ 7423.169053] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 8288.835820] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 8288.838594] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 8289.023439] usb 1-1.1: USB disconnect, device number 6
[ 8289.023852] usb 1-1.1: failed to send control message: -19
[ 8289.024064] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 8289.024083] ch341 1-1.1:1.0: device disconnected
[ 8300.556043] usb 1-1.1: new full-speed USB device number 7 using xhci-hcd
[ 8300.705375] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 8300.705382] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8300.705384] usb 1-1.1: Product: USB Serial
[ 8300.735024] ch341 1-1.1:1.0: ch341-uart converter detected
[ 8300.737932] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 8325.415202] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8325.415413] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8325.418947] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8325.419693] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8331.447991] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 8331.448082] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 8354.728517] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8354.729955] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8354.730325] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8354.730463] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8360.758575] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 8360.758653] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 8378.417907] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8378.420279] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8378.420646] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8378.420751] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8379.647314] usb 1-1.1: USB disconnect, device number 7
[ 8379.648959] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 8379.649021] ch341 1-1.1:1.0: device disconnected
[ 8390.668336] usb 1-1.1: new full-speed USB device number 8 using xhci-hcd
[ 8390.819176] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 8390.819182] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8390.819184] usb 1-1.1: Product: USB Serial
[ 8390.846765] ch341 1-1.1:1.0: ch341-uart converter detected
[ 8390.849478] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 9569.535339] usb 1-1.1: USB disconnect, device number 8
[ 9569.535667] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 9569.535695] ch341 1-1.1:1.0: device disconnected
[ 9573.647673] usb 1-1.1: new full-speed USB device number 9 using xhci-hcd
[ 9573.796993] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 9573.796999] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 9573.797001] usb 1-1.1: Product: USB Serial
[ 9573.822738] ch341 1-1.1:1.0: ch341-uart converter detected
[ 9573.824988] usb 1-1.1: ch341-uart converter now attached to ttyUSB0

[tobetter]

@rooted, I am running ODROID-N2 to run OctoPi on top of Debian Buster with Linux kernel 4.9, I've not noticed USB issue and stable.

Thanks for the information, if I can't get some support for Armbian I will definitely switch, second time running Armbian and second time I've had issues to start with.

*edit*
I am trying Ubuntu, when I tried to switch to the older meson64 kernel on Armbian it didn't boot.

I think you should try Debian, not Ubuntu, since OctoPi and it plugins are pretty much developed for RPi and package dependencies. I've tried Ubuntu 19.04 earlier no luck even I just use the simple functions.

When you used Ubuntu did you have USB issues or issues with OctoPrint? My issues seem to stem from the kernel not OctoPrint.

Do you have a link to the minimal debian image you are using? I flashed the latest Hardkernel Ubuntu (ubuntu-20.04-4.9-minimal-odroid-c4-hc4-20201015.img.xz) and installed OctoPrint without issues and the first short print I did actually finished but it was just a 200x200 layer test I made. But my next actual print failed on the second layer with this:

Code: Select all

[ 5233.019022] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 5233.019101] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 7422.988666] usb 1-1.1: new full-speed USB device number 6 using xhci-hcd
[ 7423.138004] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 7423.138010] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7423.138013] usb 1-1.1: Product: USB Serial
[ 7423.167014] ch341 1-1.1:1.0: ch341-uart converter detected
[ 7423.169053] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 8288.835820] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 8288.838594] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 8289.023439] usb 1-1.1: USB disconnect, device number 6
[ 8289.023852] usb 1-1.1: failed to send control message: -19
[ 8289.024064] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 8289.024083] ch341 1-1.1:1.0: device disconnected
[ 8300.556043] usb 1-1.1: new full-speed USB device number 7 using xhci-hcd
[ 8300.705375] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 8300.705382] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8300.705384] usb 1-1.1: Product: USB Serial
[ 8300.735024] ch341 1-1.1:1.0: ch341-uart converter detected
[ 8300.737932] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 8325.415202] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8325.415413] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8325.418947] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8325.419693] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8331.447991] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 8331.448082] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 8354.728517] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8354.729955] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8354.730325] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8354.730463] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8360.758575] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 8360.758653] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 8378.417907] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8378.420279] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8378.420646] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8378.420751] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8379.647314] usb 1-1.1: USB disconnect, device number 7
[ 8379.648959] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 8379.649021] ch341 1-1.1:1.0: device disconnected
[ 8390.668336] usb 1-1.1: new full-speed USB device number 8 using xhci-hcd
[ 8390.819176] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 8390.819182] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8390.819184] usb 1-1.1: Product: USB Serial
[ 8390.846765] ch341 1-1.1:1.0: ch341-uart converter detected
[ 8390.849478] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 9569.535339] usb 1-1.1: USB disconnect, device number 8
[ 9569.535667] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 9569.535695] ch341 1-1.1:1.0: device disconnected
[ 9573.647673] usb 1-1.1: new full-speed USB device number 9 using xhci-hcd
[ 9573.796993] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 9573.796999] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 9573.797001] usb 1-1.1: Product: USB Serial
[ 9573.822738] ch341 1-1.1:1.0: ch341-uart converter detected
[ 9573.824988] usb 1-1.1: ch341-uart converter now attached to ttyUSB0

My issues was Python, some packages/plugins are not able to be installed due to incompatbile version.

I use my Netboot Installer, flash this image to SD card and boot from your ODROID-C4 after changing the file preseed.ini. Then bare minimal Debian will be installed.
http://ppa.linuxfactory.or.kr/installer ... etinst.img

For the USB issue, I would suggest trying OTG cable to connect your USB-to-Serial converter. But I wonder if your controller does not have USB port? I am using SKR v1.3 board with ODROID-N2, have tried ODROID-C4 as well without an issue.

[rooted]

@rooted, I am running ODROID-N2 to run OctoPi on top of Debian Buster with Linux kernel 4.9, I've not noticed USB issue and stable.

Thanks for the information, if I can't get some support for Armbian I will definitely switch, second time running Armbian and second time I've had issues to start with.

*edit*
I am trying Ubuntu, when I tried to switch to the older meson64 kernel on Armbian it didn't boot.

I think you should try Debian, not Ubuntu, since OctoPi and it plugins are pretty much developed for RPi and package dependencies. I've tried Ubuntu 19.04 earlier no luck even I just use the simple functions.

When you used Ubuntu did you have USB issues or issues with OctoPrint? My issues seem to stem from the kernel not OctoPrint.

Do you have a link to the minimal debian image you are using? I flashed the latest Hardkernel Ubuntu (ubuntu-20.04-4.9-minimal-odroid-c4-hc4-20201015.img.xz) and installed OctoPrint without issues and the first short print I did actually finished but it was just a 200x200 layer test I made. But my next actual print failed on the second layer with this:

Code: Select all

[ 5233.019022] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 5233.019101] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 7422.988666] usb 1-1.1: new full-speed USB device number 6 using xhci-hcd
[ 7423.138004] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 7423.138010] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7423.138013] usb 1-1.1: Product: USB Serial
[ 7423.167014] ch341 1-1.1:1.0: ch341-uart converter detected
[ 7423.169053] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 8288.835820] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 8288.838594] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[ 8289.023439] usb 1-1.1: USB disconnect, device number 6
[ 8289.023852] usb 1-1.1: failed to send control message: -19
[ 8289.024064] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 8289.024083] ch341 1-1.1:1.0: device disconnected
[ 8300.556043] usb 1-1.1: new full-speed USB device number 7 using xhci-hcd
[ 8300.705375] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 8300.705382] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8300.705384] usb 1-1.1: Product: USB Serial
[ 8300.735024] ch341 1-1.1:1.0: ch341-uart converter detected
[ 8300.737932] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 8325.415202] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8325.415413] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8325.418947] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8325.419693] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8331.447991] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 8331.448082] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 8354.728517] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8354.729955] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8354.730325] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8354.730463] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8360.758575] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 38400
[ 8360.758653] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 38400 to 250000
[ 8378.417907] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 250000
[ 8378.420279] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 250000 to 115200
[ 8378.420646] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8378.420751] meson_uart ffd24000.serial: ttyS1 use xtal(24M) 24000000 change 115200 to 115200
[ 8379.647314] usb 1-1.1: USB disconnect, device number 7
[ 8379.648959] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 8379.649021] ch341 1-1.1:1.0: device disconnected
[ 8390.668336] usb 1-1.1: new full-speed USB device number 8 using xhci-hcd
[ 8390.819176] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 8390.819182] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8390.819184] usb 1-1.1: Product: USB Serial
[ 8390.846765] ch341 1-1.1:1.0: ch341-uart converter detected
[ 8390.849478] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
[ 9569.535339] usb 1-1.1: USB disconnect, device number 8
[ 9569.535667] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 9569.535695] ch341 1-1.1:1.0: device disconnected
[ 9573.647673] usb 1-1.1: new full-speed USB device number 9 using xhci-hcd
[ 9573.796993] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
[ 9573.796999] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 9573.797001] usb 1-1.1: Product: USB Serial
[ 9573.822738] ch341 1-1.1:1.0: ch341-uart converter detected
[ 9573.824988] usb 1-1.1: ch341-uart converter now attached to ttyUSB0

My issues was Python, some packages/plugins are not able to be installed due to incompatbile version.

I use my Netboot Installer, flash this image to SD card and boot from your ODROID-C4 after changing the file preseed.ini. Then bare minimal Debian will be installed.
http://ppa.linuxfactory.or.kr/installer ... etinst.img

For the USB issue, I would suggest trying OTG cable to connect your USB-to-Serial converter. But I wonder if your controller does not have USB port? I am using SKR v1.3 board with ODROID-N2, have tried ODROID-C4 as well without an issue.

It's not a serial convertor, it's USB plugged from the printer to the C4. I have a high quality USB cable as well and using the Hardkernel 12v 2A power supply. I restarted the print and so far I've not had any errors and it's printing, if it errors out again I will try OTG as I have a cable handy and if that doesn't work I will give your netboot image a try.

Thank you for the help, I really appreciate it.

I want to create an image so the C4 can be easily used by others who want to run OctoPrint. It would be good for Hardkernel I believe as it's very popular software and most people use Raspberry both for the Pi Camera and because of the OctoPi image.

[mad_ady]

Is the 3d printer controlled exclusively via serial? (I'm a printer noob so I don't know). If possible, a more stable solution would be to use the gpio uart and bypass usb alltogether (if voltage permits).

[tobetter]

Thank you for the help, I really appreciate it.

Happy talk about 3D print thing in this forum, even my skill is not good.

I want to create an image so the C4 can be easily used by others who want to run OctoPrint. It would be good for Hardkernel I believe as it's very popular software and most people use Raspberry both for the Pi Camera and because of the OctoPi image.

I had the same idea to create the OctoPrint and had written short installation guide. But later what I reallize is that RPi is better than ODROID to use OctoPrint, since many or most plugins are written to support RPi specifically that uses GPIO pins and some refer the path /home/pi or so.
I am happy to use OctoPrint with ODROID-N2 and I have not experienced GCODE buffering issue for my printings.

[rooted]

Is the 3d printer controlled exclusively via serial? (I'm a printer noob so I don't know). If possible, a more stable solution would be to use the gpio uart and bypass usb alltogether (if voltage permits).

No you can control it via the screen with the models on SD card as well. I can't use gpio as I would need something to go from GPIO to Type A on the printer.

[rooted]

Thank you for the help, I really appreciate it.

Happy talk about 3D print thing in this forum, even my skill is not good.

I want to create an image so the C4 can be easily used by others who want to run OctoPrint. It would be good for Hardkernel I believe as it's very popular software and most people use Raspberry both for the Pi Camera and because of the OctoPi image.

I had the same idea to create the OctoPrint and had written short installation guide. But later what I reallize is that RPi is better than ODROID to use OctoPrint, since many or most plugins are written to support RPi specifically that uses GPIO pins and some refer the path /home/pi or so. :)
I am happy to use OctoPrint with ODROID-N2 and I have not experienced GCODE buffering issue for my printings.

I think your skill is better than you let on, I've seen that cool printer you built :)

I would need to at least have the filament runout sensor plugin work with odroid as a lot of people use that, not sure what other plugins people use that need gpio but it would be up to them to change the mappings or request the developer of the plugin do it.

[igorpec]

If you can't speak to me without condescending overtones then I would appreciate if you didn't respond at all.

Likewise.