Mavericks / FTDI / Device not found until unplugged/replugged to USB

I am trying to confirm an issue with the device not showing up in the list of serial devices.

I'm using a Nano but this issue may be common to other USB-powered Arduino models.

Prior to switching to a very fast Macbook Pro, I never had issues with the Nano not appearing in the list of serial devices. Now, it won't appear in the list of serial device listed until I remove it from USB and plug it back in.

My Arduino Nano is getting power from USB and is powered up when booting up the computer. I think the problem has something to do with the FTDI driver being loaded while the Arduino is still in its boot up sequence, but not sure.

I'm hoping there's a way to re-initialize the FTDI driver and recognize the Arduino without having to physically detach and reattach it.

Can anyone else confirm this problem, or have a way to reinitialize the FTDI driver?

I am having the same problem.

The first time I hooked up my Arduino Pro Micro (via Sparkfun) it showed up and I sent a modified blink code to it.

Ever since then... it doesn't even show up in System Information on either of my Macs. I went through the procedures to disable the Mavericks FTDI drivers and re-install the ones from FTDI. Still no go. I then undid the process to go back to Apple's driver only since it HAD worked once. Still no go.

Then I found the way to tie the reset pin to ground to force a reset (no actual button on the board) and reset the Arduino. Later today I'll go back through all the steps for the drivers with the reset board as well.

sigh

http://forum.arduino.cc/index.php?topic=198539.0
http://www.ftdichip.com/Drivers/VCP.htm

Based on your description I don't think you have the same problem, or you are not describing enough detail for readers to know if it's relevant.

Have you tried unplugging the Arduino, plugging it back in (without rebooting) and re-checking if the device is found?

Your post said it never shows up, but you never said if you tried unplugging and plugging it back in.

The process of unplugging and re-plugging it in will cause the USB driver to be re-initialized.

Please post of you have tried that. If you have not tried that, please try and post whether that solves the problem.

If unplugging/replugging solves the problem, then we have the same issue. If unplugging/replugging does not solve the problem, we have different issues.

daveray:
I think the problem has something to do with the FTDI driver being loaded while the Arduino is still in its boot up sequence

The ATmega328 won't have any effect on the FTDI's enumeration process. It is possible the FTDI isn't enumerating correctly until the re-plug.

One thing to watch is open Console or run "dmesg" after plugging in the board to see what happens on 1st and "2nd" plugin.

While I don't think the ATmega328's "boot" is the issue. A culprit could be the condition of the voltage rails at power up. Could be causing an issue with the FTDI.

Another thought is, are you plugging into a USB 3 or USB 2 port? Maybe try a 2.0 hub?

It is possible the FTDI isn't enumerating correctly until the re-plug.

I agree that's may the problem, but something I can't fix; Would require FDTI to update their drivers or Apple to update their OS.

My application is a stand-alone system that needs to come up properly at boot time. Hence the problem.

Is there a way I can unload and re-load the FTDI driver at the command line; That might help determine if the problem lies with the Arduino or the driver. If it works after reloading the driver I can create some kind of startup script to handle that.

daveray:
Is there a way I can unload and re-load the FTDI driver at the command line;

You'll want to look at kextunload and kextload.

"Kernel Extension (Un)Load"

That would be an interesting test to see if resetting the driver "fixes" the problem.

Hi

Just wondering whether anyone has found a solution to this problem?

I have a similar setup, with a mac mini running osx mavericks and an arduino nano 328. It works perfectly if I have the mac running, then plug the arduino in, but if I have the arduino already plugged in when the mac is switched on, the serial does not appear to be connected.

I have tried re-installing the drivers and disabling the existed mac ones but no luck.

It's frustrating as the mac and arduino are located inside a box that makes access a little awkward.

Has anyone successfully fixed the problem by unloading and reloading the driver? If so, could you describe the steps you took to achieve this?

I've noticed that quite a number of people have reported this problem with mac osx mavericks.

Hope it can be resolved for everyone.

Cheers

Hi,
I have recently upgrade my system to Mavericks (10.9.3); since that moment connection to Arduino is becoming a nightmare.
After plugging / unplugging the Arduino, the serial usb driver disappear, the only solution to get it back is to reboot the system (The Microsoft solution!)

Development is nearly impossible in these conditions!!!!!!!!!!!

Does someone clearly identified this problem and what is the actual solution?
If not Arduino should clearly indicate that it is NOT COMPATIBLE with MAC OSX.

Thanks in advance

Robert

I run on an iMac latest Maverick ide 1.0.5

No problem at all

Suggestions...

Some USB hubs change the USB port names.
When Mac goes to sleep and then wakes up, USB ports are enumerated with an different name.

Use terminal to get
USB port name ls /dev/tty.usbmodem*

This should identify if anything else has the port, also if the port has been left Locked..

Hi,
In fact the device name doesn't change its clearly disappear (ls /dev/tty.usb* doesn't show any such device anymore), however this might be a tip. After power off/on the USB hub, the device went back.
Unfortunately I can't reproduce :~ the problem for the moment, but I will certainly verify that as soon it comes back (by the way I never had such issue with Snow Leopard over 3 years)
I will confirm that once I will reproduce it, if this is the solution it may helps other people.

Anyway thanks

Robert

My apologies,

Yes the problem is related to my USB HUB and has nothing to do with Mavericks.

Sorry about that
Robert