35 35
gprovost

Helios4 Support

Recommended Posts

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

 

Share this post


Link to post
Share on other sites
31 minutes ago, Carlo said:

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,


This stick works well on some similar Linux device?

Share this post


Link to post
Share on other sites
15 hours ago, Igor said:


This stick works well on some similar Linux device?

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.

Share this post


Link to post
Share on other sites
13 minutes ago, Carlo said:

Could be a different ch34x sources ?


Possible.

 

15 minutes ago, Carlo said:

it's an Arch Linux derivate


Not relevant. Kernel talks with hardware. To be able to understand, comparing driver sources at both kernels would be an simple start. If you got one for the Linux kernel that works ... if there is nothing suspicious, USB implementation needs to be inspected ... way too much work for us.

Share this post


Link to post
Share on other sites
On 1/13/2020 at 5:35 AM, Carlo said:

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

 

 

A few months ago I enabled some USB-Serial converter driver on the kernel and test it. I used an USB hub then hotplug several USB-Serial (PL2303, FT232, FT2232, CH340G, CH341A, CP2101, CP2102), all detected correctly.
According to your log, it seems something wrong with the USB Host controller driver, could you try with other USB device? maybe USB Flash drive

Share this post


Link to post
Share on other sites
On 1/12/2020 at 8:04 AM, Vodalex said:

When I put the system in standby via web interface of the OMV the fans are quiet and spinning very slow.. I can wake up the system without any problem. But if I shutdown the system in the webinteface I cannot wake it up using WOL. And the NAS remains on and the fans are spinning at full volume. It is the expected way as it should work?

 

This is the expected behavior. You cannot wake-up Helios4 when is halted, only when it's suspended.

Share this post


Link to post
Share on other sites
3 hours ago, gprovost said:

 

This is the expected behavior. You cannot wake-up Helios4 when is halted, only when it's suspended.

Ok,  thank you for the answer! Then it is not really WOL what I want.. Is Helios64 working the same way? Can it be started when the system is halted?

Share this post


Link to post
Share on other sites

I think the problem is, for WOL (Wake on LAN) the devices needs to be networking, so if it is completely halted that does not work -> no WOL. You are probably looking for something to "Boot on Lan". 

You could try to design that on your own, just get another device (which is energy efficient like ESP32 or so) to monitor for WOL request and use it to "push" the physical button on the Helios (via transistor or relay).

 

This way you can halt the Helios completely (maybe even use a relay to disconnect the power) and reboot it from extern.

Share this post


Link to post
Share on other sites
18 hours ago, aprayoga said:

 

A few months ago I enabled some USB-Serial converter driver on the kernel and test it. I used an USB hub then hotplug several USB-Serial (PL2303, FT232, FT2232, CH340G, CH341A, CP2101, CP2102), all detected correctly.
According to your log, it seems something wrong with the USB Host controller driver, could you try with other USB device? maybe USB Flash drive

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.

Share this post


Link to post
Share on other sites
On 1/10/2020 at 12:13 AM, aprayoga said:

Between middle-to end of November 2019, Armbian change the version and branch naming.

Version from something like 5.91 become something like 19.11.x, if i'm not mistaken Year.Month, like Ubuntu versioning.

Then the branch name,

  • DEFAULT become LEGACY
  • NEXT become CURRENT

To upgrade to new version, use armbian-config.


sudo apt-get update
sudo apt-get -y upgrade
sudo armbian-config

armbian-config_main.png.07bfc6c651dd386525f75139ab2b1926.png

 

Select System > Other, to switch to other kernel

armbian-config_system.png.81450d3b2716adb516b43436d83e1c6c.png

 

Confirm the action

armbian-config_other_kernel_confirmation.png.d1ff808ec66794597d81271e039bee53.png

 

And after some process, you will be presented by list of kernels

armbian-config_other_kernel_list.png.ed40b0a7e75e15825c42959f325023af.png

 

Select linux-image-current-mvebu. The system will install the new kernel and automatically reboot.

Confirm the kernel installed correctly and Armbian changed to new branch CURRENT by executing,


uname -a
grep "BRANCH" /etc/armbian-release

 

Thank you for this answer. Makes sense.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
35 35