[gentoo-user] [OT?]: CH340 working/not working with ESP286 Node MCU

[gentoo-user] [OT?]: CH340 working/not working with ESP286 Node MCU

[Meino.Cramer]

Hi,

I have bought an ESP8266 Lua NodeMCU board, which has 
an FTDI-like chip on board to map USB to serial and
vice versa. It is an CH340 one.
There is an according module in the driver (compiled
and - to get shure - loaded by hand).

When I connect the ESP8266 board to my Gentoo PC
nothing happens (dmesg shows nothing).
When pressing RST on the board, I see this sometimes:

[ 4340.105221] usb 7-4: new full-speed USB device number 9 using ohci-pci
[ 4340.630234] usb 7-4: device not accepting address 9, error -62

(both lines are printed right after another - no delay...)

or this:

[ 4473.567739] usb 7-4: new full-speed USB device number 11 using ohci-pci
[ 4473.712306] usb 7-4: New USB device found, idVendor=1a86, idProduct=7523
[ 4473.712316] usb 7-4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 4473.712321] usb 7-4: Product: USB2.0-Serial
[ 4473.763259] usbcore: registered new interface driver ch341
[ 4473.763278] usbserial: USB Serial support registered for ch341-uart
[ 4473.763295] ch341 7-4:1.0: ch341-uart converter detected
[ 4473.786463] usb 7-4: ch341-uart converter now attached to ttyUSB1
[ 4473.888987] usb 7-4: USB disconnect, device number 11
[ 4473.889485] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
[ 4473.889511] ch341 7-4:1.0: device disconnected
[ 4474.292773] usb 7-4: new full-speed USB device number 12 using ohci-pci

there is no new device under /dev/.

Do I miss something seriously important here related to using the
CH340 driver...or is this board simply demaged ???

Thank you very much in advance for any help!

Best regards,
Meino

Re: [gentoo-user] [OT?]: CH340 working/not working with ESP286 Node MCU

[Corbin Bird]

On 07/07/2016 10:22 PM, Meino.Cramer@gmx.de wrote:
> Hi,
>
> I have bought an ESP8266 Lua NodeMCU board, which has
> an FTDI-like chip on board to map USB to serial and
> vice versa. It is an CH340 one.
> There is an according module in the driver (compiled
> and - to get shure - loaded by hand).
>
> When I connect the ESP8266 board to my Gentoo PC
> nothing happens (dmesg shows nothing).
> When pressing RST on the board, I see this sometimes:
>
> [ 4340.105221] usb 7-4: new full-speed USB device number 9 using ohci-pci
> [ 4340.630234] usb 7-4: device not accepting address 9, error -62
>
> (both lines are printed right after another - no delay...)
>
> or this:
>
> [ 4473.567739] usb 7-4: new full-speed USB device number 11 using ohci-pci
> [ 4473.712306] usb 7-4: New USB device found, idVendor=1a86, idProduct=7523
> [ 4473.712316] usb 7-4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
> [ 4473.712321] usb 7-4: Product: USB2.0-Serial
> [ 4473.763259] usbcore: registered new interface driver ch341
> [ 4473.763278] usbserial: USB Serial support registered for ch341-uart
> [ 4473.763295] ch341 7-4:1.0: ch341-uart converter detected
> [ 4473.786463] usb 7-4: ch341-uart converter now attached to ttyUSB1
> [ 4473.888987] usb 7-4: USB disconnect, device number 11
> [ 4473.889485] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
> [ 4473.889511] ch341 7-4:1.0: device disconnected
> [ 4474.292773] usb 7-4: new full-speed USB device number 12 using ohci-pci
>
> there is no new device under /dev/.
>
> Do I miss something seriously important here related to using the
> CH340 driver...or is this board simply demaged ???
>
> Thank you very much in advance for any help!
>
> Best regards,
> Meino
>
>
>
>
>
>
>
>
If memory serves, udev/eudev generates the nodes/devices in /dev now.
To get the correct hardware ID, it uses a specific database.

The hardware ID's database may need to be updated ( or supplemented ).
The package "sys-apps/pciutils" has the hardware database included in it.

I have a 990FX chipset MB that is constantly ID as a 880 chipset board.
No info on 990FX chipsets found in the hardware ID's database.
The kernel keeps applying a 880 chipset workaround for the PCI bus, 
every boot.

Same problem I think, different hardware.

[gentoo-user] Re: [OT?]: CH340 working/not working with ESP286 Node MCU

[James]

Corbin Bird <corbinbird <at> charter.net> writes:

> The hardware ID's database may need to be updated ( or supplemented ).
> The package "sys-apps/pciutils" has the hardware database included in it.

looking at the ebuild for 'pci-utils' we see::

RDEPEND="${DEPEND}
sys-apps/hwids

So if you want the latest data on hwids, install::
'sys-apps/hwids-99999999'

> I have a 990FX chipset MB that is constantly ID as a 880 chipset board.
> No info on 990FX chipsets found in the hardware ID's database.
> The kernel keeps applying a 880 chipset workaround for the PCI bus, 
> every boot.
> 
> Same problem I think, different hardware.

OK, so both of you guys should use serial sniffers and usb sniffers and log
those sessions on a separate machine for rigorous analysis. Commercial
sniffers are very user friendly. Some cheap embedded boards can sniff usb
readily (but you'll have to search them out yourself).

For a usb sniffer, you may need special hardware to intercept those singnals
from the actual communications link. sniffing from inside
of a host is sometime problematic on catching every charcter, timings,
and other such critical signal information. sniffing RS-232 is well
documented around the net. When I sniff usb, I try to first use usb-1.0
or 1.1, as the slower speeds are easier to watch and collect critical data.

good-hunting.

hth,
James

Re: [gentoo-user] Re: [OT?]: CH340 working/not working with ESP286 Node MCU

[Meino.Cramer]

James <wireless@tampabay.rr.com> [16-07-10 14:05]:
> Corbin Bird <corbinbird <at> charter.net> writes:
> 
> > The hardware ID's database may need to be updated ( or supplemented ).
> > The package "sys-apps/pciutils" has the hardware database included in it.
> 
> looking at the ebuild for 'pci-utils' we see::
> 
> RDEPEND="${DEPEND}
> sys-apps/hwids
> 
> So if you want the latest data on hwids, install::
> 'sys-apps/hwids-99999999'
> 
> > I have a 990FX chipset MB that is constantly ID as a 880 chipset board.
> > No info on 990FX chipsets found in the hardware ID's database.
> > The kernel keeps applying a 880 chipset workaround for the PCI bus, 
> > every boot.
> > 
> > Same problem I think, different hardware.
> 
> OK, so both of you guys should use serial sniffers and usb sniffers and log
> those sessions on a separate machine for rigorous analysis. Commercial
> sniffers are very user friendly. Some cheap embedded boards can sniff usb
> readily (but you'll have to search them out yourself).
> 
> For a usb sniffer, you may need special hardware to intercept those singnals
> from the actual communications link. sniffing from inside
> of a host is sometime problematic on catching every charcter, timings,
> and other such critical signal information. sniffing RS-232 is well
> documented around the net. When I sniff usb, I try to first use usb-1.0
> or 1.1, as the slower speeds are easier to watch and collect critical data.
> 
> good-hunting.
> 
> hth,
> James
> 
> 

Hi James,

thanks for joining the problem party :)

I think I got either a lemon (faulty board) or this 
board was sent to me without any firmware.
If latter is the case I may have a chance with an ISP
programmer (I have one) ... will see.
See my previous post of just a moment ago answering Corbins
post.

Best regards
Meino

Re: [gentoo-user] [OT?]: CH340 working/not working with ESP286 Node MCU

[Meino.Cramer]

Corbin Bird <corbinbird@charter.net> [16-07-10 14:03]:
> 
> On 07/07/2016 10:22 PM, Meino.Cramer@gmx.de wrote:
> >Hi,
> >
> >I have bought an ESP8266 Lua NodeMCU board, which has
> >an FTDI-like chip on board to map USB to serial and
> >vice versa. It is an CH340 one.
> >There is an according module in the driver (compiled
> >and - to get shure - loaded by hand).
> >
> >When I connect the ESP8266 board to my Gentoo PC
> >nothing happens (dmesg shows nothing).
> >When pressing RST on the board, I see this sometimes:
> >
> >[ 4340.105221] usb 7-4: new full-speed USB device number 9 using 
> >ohci-pci
> >[ 4340.630234] usb 7-4: device not accepting address 9, error -62
> >
> >(both lines are printed right after another - no delay...)
> >
> >or this:
> >
> >[ 4473.567739] usb 7-4: new full-speed USB device number 11 using 
> >ohci-pci
> >[ 4473.712306] usb 7-4: New USB device found, idVendor=1a86, 
> >idProduct=7523
> >[ 4473.712316] usb 7-4: New USB device strings: Mfr=0, Product=2, 
> >SerialNumber=0
> >[ 4473.712321] usb 7-4: Product: USB2.0-Serial
> >[ 4473.763259] usbcore: registered new interface driver ch341
> >[ 4473.763278] usbserial: USB Serial support registered for ch341-uart
> >[ 4473.763295] ch341 7-4:1.0: ch341-uart converter detected
> >[ 4473.786463] usb 7-4: ch341-uart converter now attached to ttyUSB1
> >[ 4473.888987] usb 7-4: USB disconnect, device number 11
> >[ 4473.889485] ch341-uart ttyUSB1: ch341-uart converter now 
> >disconnected from ttyUSB1
> >[ 4473.889511] ch341 7-4:1.0: device disconnected
> >[ 4474.292773] usb 7-4: new full-speed USB device number 12 using 
> >ohci-pci
> >
> >there is no new device under /dev/.
> >
> >Do I miss something seriously important here related to using the
> >CH340 driver...or is this board simply demaged ???
> >
> >Thank you very much in advance for any help!
> >
> >Best regards,
> >Meino
> >
> >
> >
> >
> >
> >
> >
> >
> If memory serves, udev/eudev generates the nodes/devices in /dev now.
> To get the correct hardware ID, it uses a specific database.
> 
> The hardware ID's database may need to be updated ( or supplemented ).
> The package "sys-apps/pciutils" has the hardware database included in 
> it.
> 
> I have a 990FX chipset MB that is constantly ID as a 880 chipset board.
> No info on 990FX chipsets found in the hardware ID's database.
> The kernel keeps applying a 880 chipset workaround for the PCI bus, 
> every boot.
> 
> Same problem I think, different hardware.
> 

Hi Corbin,

Thanks for your help, Corbin! :)

neither lsusb nor usb-devices do list the device. 

Another CH340 based board do register correctly and ttyUSB is created.
Therefore (I think) the infrastructure of my Gentoo LINUX can handle
such board correctly and this [CENSORED] one ist either send without
any firmware or simply demaged.

I need the help of one who has solved similiar problems
with an NodeMCU v3 Lua (ESP8266)-board...sigh...

Best regards,
Meino

Re: [gentoo-user] [OT?]: CH340 working/not working with ESP286 Node MCU

[Fernando Rodriguez]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/07/2016 11:22 PM, Meino.Cramer@gmx.de wrote:
> Hi,
> 
> I have bought an ESP8266 Lua NodeMCU board, which has 
> an FTDI-like chip on board to map USB to serial and
> vice versa. It is an CH340 one.
> There is an according module in the driver (compiled
> and - to get shure - loaded by hand).
> 
> When I connect the ESP8266 board to my Gentoo PC
> nothing happens (dmesg shows nothing).
> When pressing RST on the board, I see this sometimes:
> 
> [ 4340.105221] usb 7-4: new full-speed USB device number 9 using ohci-pci
> [ 4340.630234] usb 7-4: device not accepting address 9, error -62
> 
> (both lines are printed right after another - no delay...)
> 
> or this:
> 
> [ 4473.567739] usb 7-4: new full-speed USB device number 11 using ohci-pci
> [ 4473.712306] usb 7-4: New USB device found, idVendor=1a86, idProduct=7523
> [ 4473.712316] usb 7-4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
> [ 4473.712321] usb 7-4: Product: USB2.0-Serial
> [ 4473.763259] usbcore: registered new interface driver ch341
> [ 4473.763278] usbserial: USB Serial support registered for ch341-uart
> [ 4473.763295] ch341 7-4:1.0: ch341-uart converter detected
> [ 4473.786463] usb 7-4: ch341-uart converter now attached to ttyUSB1
> [ 4473.888987] usb 7-4: USB disconnect, device number 11
> [ 4473.889485] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
> [ 4473.889511] ch341 7-4:1.0: device disconnected
> [ 4474.292773] usb 7-4: new full-speed USB device number 12 using ohci-pci
> 
> there is no new device under /dev/.
> 
> Do I miss something seriously important here related to using the
> CH340 driver...or is this board simply demaged ???
> 
> Thank you very much in advance for any help!
> 
> Best regards,
> Meino

What's running on the board? I'm not familiar with it or arduinos at all but it looks like it's being
detected and then disconnected. Are you trying to program the board through USB? If so, and since
it's detected when you reset the board, my guess is that it's got some kind of bootloader that is
initializing the UART->USB adapter and passing control to whatever firmware is already loaded, and
that firmware is not driving the UART/USB adapter. If that's the case the board's manual should tell you how
to program it.

Fernan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXgD6zAAoJEPbOFX/5Ulwc7+QP/3q9pQunL9XJiWounkakNjZe
Yb3jNK0D+G50T2/DGzFSMK/sXsEcTAr/w9Dhm2txwutPf3wGibr8O3gdfneRy/Gm
ImMXAqjL9ag3SFT3o5D7t97qKxRBJKOYa9enzBUDQGpUpQYJPRvn9v7PWJFwEHza
jVZJcW4HfnGeTdDgeqOsM8nbi8GITDd+WOV1tnIv573ifs3TCW5nGisEtCqwoVui
knzOc9I+DLY0QEPEEBnZlmiOQR6nsJQNrX3ixs/2odTO/lX10xmdTSy94yWMBuqY
8d8FYyiizjx9rkJamks5P04Q7hvXZos32EgcWq4jKINL4fyOXhfg9uxNs2366Wwh
bOlvt5wJdwH5ABvEcN71jU8pm9UrrdfDnXgRZY/irGWAxsLSWhftVIAlIz4hTSUa
2uowKMvKULXUJLFdVSltAItuXe2WM0pqEzoKPb9iXFZY88aWvGomrZxlbCtBQ3Gg
t2TYSzOYljnzYs+dVm22JBLtgbrxfaJexisJ3O/7h8gs6ACm0M9zi33Rm1df5Cgp
6o9ihJynW9svsJVab72LsRmbe0lVv+HgNfwKr5O3IEIE1Y7BhPx5EAFrgfE6M/SK
2sKR4YzdRgpxM7Td4wHtiCaROCfGsxK4wd69n2H2bp7cYPofYa48C//wZJWV6gmr
X0oZGic3DDPrR+77Hzi6
=eEG4
-----END PGP SIGNATURE-----