|
Post by juljus on Feb 12, 2023 13:22:04 GMT
Hello, I am trying to calibrate my eChook telemetry board, but the computer isn't detecting the Arduino nano. The first time (when i was programming it), it worked fine. I programmed it at first on a windows with the CH340 drivers installed. Now when i tried the same, the windows computer said "USB not recognized (driver problem)". I also tried it on Ubuntu 20.04.5 LTS where the CH340 drivers are built-in. It's still not detecting the Arduino (its not showing up when i do 'lsusb' in terminal). When i run 'dmesg -w' and plug in the Arduino nano I get these messages:
usb 1-3: new full-speed USB device number 19 using xhci_hcd usb 1-3: device descriptor read/64, error -71 usb 1-3: device descriptor read/64, error -71 usb 1-3: new full-speed USB device number 20 using xhci_hcd usb 1-3: device descriptor read/64, error -71 usb 1-3: device descriptor read/64, error -71 usb usb1-port3: attempt power cycle usb 1-3: new full-speed USB device number 21 using xhci_hcd usb 1-3: Device not responding to setup address. usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 21, error -71 usb 1-3: new full-speed USB device number 22 using xhci_hcd usb 1-3: Device not responding to setup address. usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 22, error -71 usb usb1-port3: unable to enumerate USB device
Thank you,
Juljus
|
|
|
Post by Rowan on Feb 13, 2023 8:10:41 GMT
Hi Juljus,
You've done a thorough check! Is the arduino otherwise working, lights flashing, sending data over bluetooth etc?
Did you test with the arduino plugged into the eChook board? If so, could you check again with it unplugged - That will check that something on the board isn't pulling the 5v rail down a little too much and upsetting the CH340 chip.
If that was tested with the arduino unplugged it sounds like something has killed the CH340g chip which isn't common but I have seen with another team - we never actually worked out exactly what was causing it, but we went over the eChook board and reflowed all the solder joints and afaik it's not killed an Arduino since.
Unfortunately, it's quite likely you need a new Arduino but it's worth trying to work out what happened to this one before plugging a new one in. If you're handy with soldering and have a reflow station it's possible to swap a new CH340g in.
|
|
|
Post by juljus on Feb 13, 2023 14:29:41 GMT
The arduino is otherwise working, i can connect to it in the app and it sends data. I tested it with the arduino unplugged.
Thanks a lot for the reply!
|
|
|
Post by Rowan on Feb 13, 2023 15:16:01 GMT
That definitely sounds like a dead CH340 chip I'm afraid. For USB programming that arduino is dead unless you can replace the chip. Alternatively if you're determined to use that arduino you can use a second arduino as a programmer/communication bridge for it. docs.arduino.cc/built-in-examples/arduino-isp/ArduinoISPIt's worth checking over your board and trying to find anything that might have caused it before plugging in a new arduino.
|
|
|
Post by juljus on Feb 15, 2023 14:59:37 GMT
I used an Arduino UNO for programming the nano, and it worked really well, thank you!
|
|
|
Post by Rowan on Feb 15, 2023 15:05:20 GMT
Nice! Glad it worked
|
|