I have several Nanos that crash my Mac when plugged into the USB port. Anyone else have similar problems? They are probably clones (don't remember where I purchased them). When I connect them to the computer, the computer crashes and restarts. Puzzling.
That's weird because it sounds like something's "blown" and I assume there's no reason for them all to be fried.
Have you tried a different USB cable? Maybe your cable is shorted?
Is anything connected to the board? Something that might be shorted or drawing excess power?
I'm not a Mac user and I've never seen that on a PC. I've seen the port "crash" (or lock-up) from drawing too much power, but the operating system keeps running.
Or, maybe it's the driver... A driver can crash Windows, so maybe it can crash OS-X? or, maybe the wrong driver is getting loaded... Have you been using something else that uses a virtual COM port?
Are you using macOS Sierra? There's a known problem with the driver for the CH340 USB-serial chips used on the clone nanos and Sierra. You need to install a modified driver. More information on this thread:
https://forum.arduino.cc/index.php?topic=428349.0
I think this is the driver you want:
I can't understand why the manufacturer hasn't fixed this in the official driver yet. CH340 became by far the most popular chip after FTDIgate knocked the FT232 off its throne but I've noticed some new boards are using alternative chips, probably due to this issue.
Installing the new driver worked. Thanks!!
pert:
Are you using macOS Sierra? There's a known problem with the driver for the CH340 USB-serial chips used on the clone nanos and Sierra. You need to install a modified driver. More information on this thread:
CH341SER_MAC No longer works in macOS Sierra - IDE 1.x - Arduino ForumI think this is the driver you want:
http://www.mblock.cc/posts/run-makeblock-ch340-ch341-on-mac-os-sierraI can't understand why the manufacturer hasn't fixed this in the official driver yet. CH340 became by far the most popular chip after FTDIgate knocked the FT232 off its throne but I've noticed some new boards are using alternative chips, probably due to this issue.