Carlo

I tried to modify configuration but unlucky it's not sufficient and I got error that I'm unable to fix. LD spl/u-boot-spl OBJCOPY spl/u-boot-spl-nodtb.bin CAT spl/u-boot-spl-dtb.bin COPY spl/u-boot-spl.bin MKIMAGE u-boot-spl.kwb CFGCHK u-boot.cfg [ error ] ERROR in function compile_uboot [ functions/cli/cli-entrypoint.sh:108 -> functions/main/default-build.sh:55 -> functions/compilation/uboot.sh:145 -> functions/logging/traps.sh:0 ] [ error ] U-boot file not found [ u-boot-sata.kwb ] [ o.k. ] Process terminated

Thanks, I'll give it a try as soon as possible. I will let you know.

Helios4 can boot directly from the sata disk nr 1, without the need to switch from the SD or the eMMC. I personally tried setting SW1 to 11100 and using u-boot-sata for Clearfog, which shares the same uSOM and the system booted regularly, obviously the system didn't recognize many devices being u-boot for another board. I tried to compile a version of u-boot for sata trying to integrate the changes present in https://solidrun.atlassian.net/wiki/spaces/developer/pages/287212134/A38X+U-Boot in the U-boot build instruction and sources for Helios4 present in the Kobol Wiki but my skills are not sufficient for such a job. In the binaries available for Helios4 at https://imola.armbian.com/beta/pool/main/l/linux-u-boot-helios4-current/ there are only u-boots for uart, flash and mmc. Would it be possible to have the sata version in future releases? Thanks in advance and for all the work done.

No, usb sticks work fine, I connect and reconnect many time, without trouble. I had investigate a little more and maybe I find a logic. I tried all my usb serial devices, CH34x, PL2303, FT232RL and I discovered that don't matter the chipset but the first device connected. I connect the first device then on second usb I connect and reconnect all the device I want and all the times I want without troubles but when I disconnect the first device, it's crash and then, on second usb, if I reconnect the other device, after a couple of times, it crash too.

Hi, yes, all these sticks work fine on my desktop PC, which run Artix Linux, maybe not very similar due to it's an Arch Linux derivate without systemd. I use very often, from more than a couple of years the desktop PC to flash, reprogram and debug them. Could be a different ch34x sources ? Previous this distribution, on the helios4, I tried the ubuntu versione whitout the ch34x compilated and I had a lot of trouble to find a compiling myself a working .ko but I had the same problem of the no detection after the first connection. I tried with an usb hub without luck.

Hi, I have a problem with ch341 USB serial adapter, I tried to search on forum and on internet without luck. I'm runnig a Linux helios4 4.19.84-mvebu #19.11.3 on an helios4 board, off course. When I connect a CH341 device, like NodeMCU, serial adapter or an Arduino Mega Pro Mini, etc, for the first time or I boot the system with the device connected, it is enumerated correctly and I have it listed on dmesg and I give a /dev/ttyUSBx, but if I disconnect and reconnect it, the system, sometimes at the first time, sometimes after few times, give me these errors and didn't detects the usb adapter until the next boot. What's wrong ? What can I do, other usb device, link stick, works fine. Sotty for my english, I hope that my message is comprensible. Bye, Carlo [dom gen 12 23:28:15 2020] usb 2-1: new full-speed USB device number 7 using xhci-hcd [dom gen 12 23:28:15 2020] usb 2-1: New USB device found, idVendor=1a86, idProduct=5523, bcdDevice= 3.04 [dom gen 12 23:28:15 2020] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [dom gen 12 23:28:15 2020] ch341 2-1:1.0: ch341-uart converter detected [dom gen 12 23:28:15 2020] usb 2-1: ch341-uart converter now attached to ttyUSB0 [dom gen 12 23:28:26 2020] usb 2-1: USB disconnect, device number 7 [dom gen 12 23:28:26 2020] usb 2-1: ch341_read_int_callback - usb_submit_urb failed: -19 [dom gen 12 23:28:31 2020] xhci-hcd f10f0000.usb3: xHCI host not responding to stop endpoint command. [dom gen 12 23:28:31 2020] xhci-hcd f10f0000.usb3: xHCI host controller not responding, assume dead [dom gen 12 23:28:31 2020] xhci-hcd f10f0000.usb3: HC died; cleaning up [dom gen 12 23:28:31 2020] usb 2-1: failed to send control message: -19 [dom gen 12 23:28:31 2020] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [dom gen 12 23:28:31 2020] ch341 2-1:1.0: device disconnected