Comments: Pro Micro & Fio v3 Hookup Guide


Comments 18 comments

  • You can have issues using the Pro Micro if you are connecting to a USB3 port. The drivers will not install correctly unless they use a computer with USB2.

    There was an issue when a customer was using it on a Windows 7 64-bit OS. When connecting to a USB3 port the Pro Micro can report the hardware ID as:


    When connected to a USB2 port the Pro Micro should report the hardware ID as:


    FioV3 should be

  • Is there any way to get the Pro Micro to work with 64 bit Windows 7? The only drivers I can find are for 32 bit systems.

    • The drivers should work fine on either. I think most machines at SparkFun are 64-bit Windows 7 and we haven’t had any problems. If you are having problems getting the posted drivers to work email and they can help you get it working.

      • When I try to install the drivers suggested I get, “Windows has determined the driver software for your device is up to date.” or “The folder specified doesn’t contain a compatible software driver…”

  • my mac is not recognizing the fio v3. I am running yosemite - any ideas on how I can get it to recognize?

  • There was a customer that had an issue on their Ubuntu Linux preventing them from accessing the enumerated port when a Pro Micro was connected. There is a fix by configurating some settings. Check below for more information:

    “On Ubuntu Linux, the modem manager was grabbing the Pro Micro as soon as it was plugged in, preventing anything else, such as the Arduino IDE from being able to open the port. This is apparently a known issue, but I had to go search it down, as there is no mention of it here…


    sudo echo 'ATTRS{idVendor}=="1b4f", ENV{ID_MM_DEVICE_IGNORE}="1"' > /etc/udev/rules.d/77-arduino.rules

    I found the explanation and fix on"

  • I goofed :-(, excellent tuto !

  • What is the type of the USB connector? There are several types of the mini and micro. Thanks

  • I’m a bit confused on the FIO hookup guide. I was under the impression the I2C connections are on A4 & A5. Though the image shows them on D2 & D3. Which is correct?

    • D2 and D3 is correct for this version of the FIO; it uses the ATmega32U4, which has those pins assigned to I2C.

      You’re right that any Arduino that uses an ATmega328 (like the Uno, Pro Mini, Pro, etc.) would have the I2C pins on A4/A5.

      • So a got a couple of the Sparkfun 32U4 v3 FIOs, imagine my disappointment when I noticed what appeared to be a slam dunk for mounting an Adafruit ADC 16 bit analog board straight on top, only to find the SDA and SCL were swapped!

        Any suggestions for swapping the pins short of artful soldering of a miniature metal helix?

  • bboyho / last year * / 1

    If you have problems uploading code with this error using the Pro Micro on a Linux machine:

     avrdude: ser_recv(): programmer is not responding
     avrdude: butterfly_recv(): programmer is not responding

    try following these instructions from Arduino => They need to change some udev rules. There was a customer had the same problem but got it working after changing the settings.

  • It looks like pins 14 and 17 are swapped on the hookup guide (hopefully not swapped on the board!).

    Can you confirm/deny this is the case?

    • Ahhhh…. The short answer is all the boards work correctly. Somewhere along the line something got mislabled (it might be on the actual part). I think the current boards/schematics are all correct though. On the Fio the ISP header works, on the Pro Micro the SPI pins are all there. Otherwise I suggest ignoring the labels and just seeing what works.

      • I should clarify: the blue pin numbers on the hookup guide (not the board) look swapped. So maybe just needs a photoshop on the image to avoid confusion. Suspect the board is fine and the graphic is just mistaken.

  • As mentioned in this tutorial the Arduino add files on do not work for Arduino V1.5. I have fixed this and put up a set of files that work with Arduino V1.5.5 These are available from

If you've found a bug or have other constructive feedback for our tutorial authors, please send us your feedback!