Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 8
    Wow. This is a great great great answer Commented Jul 9, 2015 at 16:20
  • 1
    That is a wonderful answer sir. Commented Jul 9, 2015 at 17:04
  • 1
    I recently had a problem with the new FTDI drivers that "brick" chinese "FTDI compatible" (well you could say imitation) chips. They put the PID of the device to 0x0000, which will make the drivers invalid. You can choose to change the PID back with the M_PROG tool on FTDI or to change the drivers (and set up windows to allow unverified drivers). Commented Aug 18, 2015 at 20:35
  • 1
    @Nick Gammon I would have put after "Check the comm port" to plug in the arduino on another computer running arduino IDE if that possible. If the arduino is detected and works on another different PC than it still ok. That may save time - if you have multiple PCs or can borrow one- rather than go through your long answer. Commented Nov 6, 2016 at 0:10
  • 1
    Fantastic answer, couldn't be more complete. Commented Jan 25, 2019 at 9:42