the ELEGOO Uno R3 does not want to connect to my Arduino IDE. oh and the amount of times i've tried to connect to the USB port and lsusb and modprobe ch340
i don't understand how i cannot find a single person with this same problem? it's been difficult because when i installed ubuntu 24 all the USB devices i had plugged in worked but the ones i plugged in after that just refused to identify that it is plugged in
one thing the board does do however is light up "ON" and flash "L", clearly executing code from "Blink"
i really don't have much else to say, trying to extend this and give as much info as possible but that's really all i have
dmesg does not show anything other than "failed to send h2c command" and "firmware failed to leave lps state" and there is no sound or visual telling that a USB device is plugged in, and i also recently tried this on another computer and it did not work
I would call that a bad (ftdi/ch340). Maybe you want to try your hand at multi-lead de-soldering? Understand, this will be practice, and you will destroy the chip and board.
I buy the CH340 Arduino (Nano) because of the price, if one or a few die. I have not had a bad one yet (out of six, maybe I am due?) and they have been controlling things for months at a time (until I add new code) on battery, "charge cube" and A/C power-supply. I also get ATtiny88 for cheap and use them in one-pin projects... they are cheaper than ATtiny85.
Elegoo normally ship good parts. Give them a call/email.
Sounds familiar! Are you a member of the dialout group? Try this:
Type 'groups', is 'dialout' there ?
sudo usermod -a -G tty yourUserName - sudo usermod -a -G tty gil
sudo usermod -a -G dialout yourUserName
Log off and log on again for the changes to take effect.
The last step is most important!
Disconnect the board.
Run dmesg -w; the program will not close.
Connect the board and check if there is any change in the output of (2) above.
Stop dmesg -w using ctrl+C.
yes, ok for some reason it let me add myself to it and i rebooted and it still does not work, here is some more info:
running lsusb says
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1532:005c Razer USA, Ltd DeathAdder Elite (mouse)
Bus 001 Device 007: ID 0951:16dd Kingston Technology HyperX Alloy Core RGB (keyboard)
Bus 001 Device 008: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 1058:25e1 Western Digital Technologies, Inc. My Passport (WD20NMVW) (USB external SSD)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
and running 'groups' after adding myself to dialout lists it: oscey adm tty dialout cdrom sudo dip plugdev users lpadmin
My Linux Mint 21 shows the same lsusb but my groups shows most of what you show, but does not show users. dmesg shows activity when I insert my CH340 Nano.
[27532.104473] usb 7-2: new full-speed USB device number 2 using uhci_hcd
[27532.293515] usb 7-2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.32
[27532.293528] usb 7-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[27532.293534] usb 7-2: Product: USB Serial
[27532.756552] usb 7-2: USB disconnect, device number 2
[27532.976520] usbcore: registered new interface driver usbserial_generic
[27532.976554] usbserial: USB Serial support registered for generic
[27533.047461] usbcore: registered new interface driver ch341
[27533.047498] usbserial: USB Serial support registered for ch341-uart
Searching on my exact vendor/product/device shows one user who simply had an intermittent cable.
It does not look like your board is in that list. Is there any difference in that list if you have your board connected and if you don't have it connected?
As mentioned by @xfpd, dmesg might reveal something.
Disconnect the board.
Run dmesg -w. The application will not close.
Connect the board.
Any reaction in the dmesg output?
Close dmesg using CTRL+C.
Is this a new kit or have you done projects with it before? Did your board ever work?
Do you have an option to test the board detection on another PC? You don't need the IDE for that.
You did not answer the question if this was a new board or that you used it before with success? And if you have the option to test board detection on another PC?
If dmesg does not give any reaction I can think of two reasons:
oh yeah sorry it's a new board and i tested it on another PC and it also did not work. i was suspicious of the cable so i'll probably just get a new cable and see if that works out