I cannot connect to either my Arduino UNO or my Arduino 101.
What is happening?
During upload of the sample Blink sketch, my USB ports appear to drop out twice with the pinging sound.
Do not get the verification light that bootload is present on the board.
When does it happen?
on a PC with Windows 10 on both UNO and 101, with two different USB cables (with separate battery pack power supply the error message is a bit different, but USB cycles on and off continuously)
on a laptop with Windows 10 on both UNO and 101, with two different USB cables (with separate battery pack power supply the error message is a bit different, but USB cycles on and off continuously)
What have I done?
read troubleshooting guides, forums, and web posts
tried resetting boards after compiling and then during upload
changed power settings on ports
updated drivers for ports, but system says they are latest by searching both online and on system
Used (2) different USB cables, the "BLUE" cable is known to work from previous Arduino experiments
IT dept was supposed to "turn-on" USB on laptop (not sure if this is fully turned-on)
My experience:
Used my Arduino UNO for force sensor operation and writing data back to a txt file.
This feels like something I am missing as a Windows 10 issue on both my PC and laptop.
The continuous Windows 10 updates are wreaking havoc on my work computer and systems, so I wonder if there is something I have missed on port configuration.
I hope you can help point me in the right direction.
The 101 is a very fussy animal when it comes to USB and should only be used on a USB 2.0 port.
It also needs a more reliable USB lead in most instances as cheaper ones are subject to noise which can also affect it's upload ability. For this board it is not unusual to see the port drop out and a new one appear as it does use two seperate ports with the second called "bootloader"
You can FORCE the bootloader mode by quickly double tapping the reset button which is a documented feature.
The UNO is much more reliable in that aspect but can still be prone to USB 3.0 problems on occasion.
It should not display any changes to the port in the way the 101 does.
If you only have USB 3.0 ports then very often a suitable "powered" USB 2.0 hub will help resolve many of the issues.
As you are also on a corporate system there may be other issues that need to be resolved via your IT team.
The applications / IDE's you are using may need to be white-listed / excluded from any extra security measures.
Working with IT Dept and trying to verify USB ports are "pushed for data" with multiple gpupdate /force and restarts. Not sure if they listed the UNO as "OK."
Now I have success with UNO blinking after uploading Blink sketch on COM5.
However, 101 board still drops out right after connecting, and only shows up as COM4.
I even tried the loop-back test on the 101 board without success (with and without IDE open), and continuously getting the USB device-removal tone every 5 seconds. Jumpered GND to Reset, and jumpered pin 0(TX) to 1(RX), then connected USB, received a USB_insertion tone initially, then get a continuous USB-Removal tone every 5 seconds. Same response after pressing Master Reset in this loop-back test.
When I try to burn bootloader, I receive this error: Error while burning bootloader.
Here is one of the error messages from the 101 board:
Sketch uses 3958 bytes (13%) of program storage space. Maximum is 28672 bytes.
Global variables use 149 bytes (5%) of dynamic memory, leaving 2411 bytes for local variables. Maximum is 2560 bytes.
An error occurred while uploading the sketch
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
Found programmer: Id = "�"; type = �
Software Version = i.
Not sure why you are trying to burn a bootloader onto it ?
What are you using to burn the bootloader because it has a JTAG and an ISCP set of headers ?
So if I understand correctly your UNO is now OK and your problems are just with the 101 ?
UNO is now functional and system identifies it on COM5.
101 is not working and still only connects on COM4 using same cable and USB Port after verifying UNO is functional without moving cable from USB port. Regarding bootloader, since i did not have a light indicating the board was functional, just kept trying any configuration to establish communication. Bootloader attempt is pure ignorance on my part, but I have found Serendipity can yield priceless dividends. While quarantined and needing the functionality of the 101, I am trying to make progress while locked-out of my labs and access to our makers' mother-lode of supplies and kits.