Dear Lazyweb, can someone please tell me what chickens I have to bleed to make macOS 10.14.6 and Arduino IDE 1.8.13 talk to an Adafruit Metro Mini? It says "/dev/cu.ARPT: Resource busy". System Info shows a TUSB3410 connected, but maybe that's something else, I can't tell.

Apparently it has been 4 years since I tried to use an Arduino, because 4 years ago I posted: "Is programming an Arduino from macOS always a nightmarish clusterfuck, or am I just lucky?" and I still have all the same questions as last time.


Tags: , , , ,

9 Responses:

  1. Stormgren says:

    Metro Mini appears to be based on the CP2104 USB/Serial chip, and I recently had to get the drivers direct from Silicon Labs's website to make my NodeMCU boards show up on my Mac (uses the same chip for serial).

    Not sure what that TUSB3410 is for, but adafruit isn't mentioning it on their page.

    • jwz says:

      Do you know where you found that? I tried "CP210x Software package for Mac, includes VCP Drivers v6.7.4" from here but it doesn't seem to have changed anything. The Arduino / Tools / Port menu still only lists /dev/cu.ARPT and /dev/cu.Bluetooth-Incoming-Port and it still can't connect.

      • Big says:

        I used the "CP210x USB to UART Bridge VCP Drivers" from here:

        a few months back to get macOS 10.15 Catalina to work with ESP32 based boards in Arduino IDE. Release notes there say "for 64 bit Intel Macintosh computers running MacOS X 10.11 or greater." so there's a better then even chance they'll work on 10.14 for you...

        (The other thing I often fuck up is grabbing a power only micro USB cable. If you haven't already, double check that cable actually works with some other USB device that expects data connections...)

        • asc says:

          Interesting. The TUSB3410 is a USB/serial bridge as well. What else do you have connected to your USB buses? Otherwise you could try downloading the drivers from
          and see if it worked?

        • Stormgren says:

          What Big says. I got the drivers from the URL they mention, specifically this file.

          Release notes at this link here.

          Apologies for not including the direct link last night, this is what I get for commenting right before I fall asleep.

          "...The other thing I often fuck up is grabbing a power only micro USB cable."

          Had this happen the other night, trying to transfer data off an older android phone that had micro. I really need to flag all the power-only micro cables around here before I make that mistake again and want to feed a device to a wood chipper in frustration.

          • jwz says:

            That did it, thank you!

            I guess what I found on their site last night was a "development kit" which is not the same as "drivers" even though "drivers" is what I searched for...

  2. phule says:

    I cannot remember the last time you actually got a solution by posting a question here. Warms the heart it does.:)

  • Previously