Hello!
I have two mega2650's. One is not detected by windows or linux. I can check that my computer and USB ports are working properly with the 2nd mega - so it's definately a problem with the board.
I believe the problem may be some errant serial code flooding serial0. It stopped working when I was working on some data collection code, which involved Serial.println("no data") inside loop(), and I'm not sure if I had a delay in there at all. It's also possible that I've just hit the upload limit... but I'd be very surprised if I've uploaded to it more than 2000 times, and I'd imagine the device would still be detected. Almost more likely that a wire inside the USB connector is broken.
- It was working for months (and an hour before), swapping between an externally powered application and usb power/connection to program it
- I uploaded slightly different code (removing a delay perhaps; the code was to read bytes from Serial2 and print them to Serial), successfully I believe; it is possible this upload failed due to forgetting to disattach an Xbee shield
- I moved the board to my application (external power, connected to some Serial devices and possibly LEDs), it didnt perform as expected (I dont' remember if it was getting data from the serial devices)
- when I returned the board to USB power to change the code again, it was no longer detected by the computer (within a 1 minute period from when I uploaded the previous code)
- It hasnt been detected since
This was a few months ago, I'm sorry if I'm a little uncertain about the details, it was very busy at the time.
I've tried putting it into DFU mode (using Fixing Linux firmware issues on Arduino Mega 2560 | Wayne and Layne this lovely picture to assist) and it does not respond to either Flip (though I'm not sure I was using Flip correctly) on Windows, or dfu-programmer 0.5.1 on linux Ubuntu2.6.28-11-generic (Flip says "No USB Device" or something similar, dfu-programmer says "dfu-programmer: no device present."; I couldnt get 0.5.4 to compile on Ubuntu, something about missing a LIBUSB_1_0 declaration). It's also not showing up in the USB Hardware device list on Windows (neither XP or 7) or through lsusb or dmesg on linux (dmesg output below), ie no difference with it plugged in or not, and it makes no difference if it's in DFU mode either.
When I plug it into any USB port (I've tried 5 computers or so) the ON led comes on, and pin13 LED flashes twice and then remains on in this pattern: ---- -- ---------------------...... The other working mega2560 pin 13 flashes like this, turning off at the end: ---- -- --------
On Ubuntu, lsusb shows
Bus 002 Device 007: ID 2341:0010
when the good mega is plugged in, nothing similar for the bad one.
The pins all look normal. The board reacts to a reset button as if power has been cycled. When I try to put it in DFU mode, and touch the two small pads for HWB and GND together (green in this picture Fixing Linux firmware issues on Arduino Mega 2560 | Wayne and Layne ) with a wire, the board acts as if power has been cycled (lights flash); interestingly though, no lights flash when I touch reset and ground (the larger pads closest to the USB, red in the picture).
Anyone have any ideas for other things to check? Or ideas on what I did to get it into this state? Right now my mega is a very nice paperweight
Thanks everybody
Chris
$ dmesg | grep usb
[ 0.416538] usbcore: registered new interface driver usbfs
[ 0.416538] usbcore: registered new interface driver hub
[ 0.416538] usbcore: registered new device driver usb
[ 1.996076] usb usb1: configuration #1 chosen from 1 choice
[ 1.996363] usb usb2: configuration #1 chosen from 1 choice
[ 1.996568] usb usb3: configuration #1 chosen from 1 choice
[ 1.996769] usb usb4: configuration #1 chosen from 1 choice
[ 1.996968] usb usb5: configuration #1 chosen from 1 choice
[ 1.997078] usbcore: registered new interface driver libusual
[ 1.997100] usbcore: registered new interface driver usbserial
[ 1.997119] usbcore: registered new interface driver usbserial_generic
[ 1.997121] usbserial: USB Serial Driver core
[ 2.508510] usb 4-1: new low speed USB device using uhci_hcd and address 2
[ 2.694796] usb 4-1: configuration #1 chosen from 1 choice
[ 7.040234] usbcore: registered new interface driver hiddev
[ 7.053894] input: GenesysLogic USB Mouse as /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input5
[ 7.054128] generic-usb 0003:05E3:1205.0001: input,hidraw0: USB HID v1.10 Mouse [GenesysLogic USB Mouse] on usb-0000:00:1d.2-1/input0
[ 7.054144] usbcore: registered new interface driver usbhid
[ 7.054161] usbhid: v2.6:USB HID core driver
Directly after putting in DFU mode (I plugged in my functioning mega first), I noticed a difference:
$ dmesg | grep usb
[ 0.416538] usbcore: registered new interface driver usbfs
[ 0.416538] usbcore: registered new interface driver hub
[ 0.416538] usbcore: registered new device driver usb
[ 1.996076] usb usb1: configuration #1 chosen from 1 choice
[ 1.996363] usb usb2: configuration #1 chosen from 1 choice
[ 1.996568] usb usb3: configuration #1 chosen from 1 choice
[ 1.996769] usb usb4: configuration #1 chosen from 1 choice
[ 1.996968] usb usb5: configuration #1 chosen from 1 choice
[ 1.997078] usbcore: registered new interface driver libusual
[ 1.997100] usbcore: registered new interface driver usbserial
[ 1.997119] usbcore: registered new interface driver usbserial_generic
[ 1.997121] usbserial: USB Serial Driver core
[ 2.508510] usb 4-1: new low speed USB device using uhci_hcd and address 2
[ 2.694796] usb 4-1: configuration #1 chosen from 1 choice
[ 7.040234] usbcore: registered new interface driver hiddev
[ 7.053894] input: GenesysLogic USB Mouse as /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input5
[ 7.054128] generic-usb 0003:05E3:1205.0001: input,hidraw0: USB HID v1.10 Mouse [GenesysLogic USB Mouse] on usb-0000:00:1d.2-1/input0
[ 7.054144] usbcore: registered new interface driver usbhid
[ 7.054161] usbhid: v2.6:USB HID core driver
[ 6597.592015] usb 2-1: new full speed USB device using uhci_hcd and address 2
[ 6597.792335] usb 2-1: configuration #1 chosen from 1 choice
[ 6597.840092] usbcore: registered new interface driver cdc_acm
[ 6602.176041] usb 2-1: USB disconnect, address 2
[ 6603.904015] usb 2-1: new full speed USB device using uhci_hcd and address 3
[ 6604.105308] usb 2-1: configuration #1 chosen from 1 choice
[ 6609.864041] usb 2-1: USB disconnect, address 3
[ 6611.344016] usb 2-1: new full speed USB device using uhci_hcd and address 4
[ 6611.543802] usb 2-1: configuration #1 chosen from 1 choice
[ 6613.088043] usb 2-1: USB disconnect, address 4
[ 6615.756012] usb 2-1: new full speed USB device using uhci_hcd and address 5
[ 6615.956209] usb 2-1: configuration #1 chosen from 1 choice
[ 7285.416036] usb 2-1: USB disconnect, address 5
and
$ dmesg | grep cdc_acm
[ 6597.837230] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
[ 6597.840092] usbcore: registered new interface driver cdc_acm
[ 6597.840096] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[ 6604.116606] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
[ 6611.548016] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
[ 6615.959079] cdc_acm 2-1:1.0: ttyACM1: USB ACM device