How are you guys getting your machines running 10.5 to recognize arduino via usb? I can't get my macbook pro to pick up or even show a USB port available, downloaded latest drivers from FTDI today to no avail. Any and all help would be greatly appreciated.
Thanks,
-Nick
It works fine for me.
What kind of Arduino do you have? Does it work on other computers?
Where are you looking for the serial port? What do you see if you do a ls /dev/tty.* in the Terminal?
an arduino decimilia, works on mac os x 10.4 , no such directory exists when I run that in terminal
nick-kinneys-macbook-pro-15:~ Nick$ ls /dev/tty.*
/dev/tty.Bluetooth-Modem /dev/tty.MotorolaQ-Dial-upNetwor-2
/dev/tty.Bluetooth-PDA-Sync /dev/tty.MotorolaQ-GenericSerial-1
nick-kinneys-macbook-pro-15:~ Nick$
from ls /dev/tty.*
If you go to System Profiler and then under USB, do you see anything that could be the Arduino (e.g. FTDI or FT232R)?
nah this is what it shows;
I had performed a clean install of Leopard and had the same issue. I reinstalled Virtual Com Port drivers for the FTDI and I'm back on track.
http://www.ftdichip.com/Drivers/VCP.htm
I was also having a helluva time getting 10.5 to recognize my board. Worked once after installing the drivers, then never again. I found that repairing permissions on my boot volume using Disk Utility, after installing the latest FCPI drivers, made my Arduino happy once more. Hope this helps anyone out there having problems!
I have been having the same problems with OS X 10.5.2 and Arduino0010. I have tried all the remedies suggested by the message boards and from what I've found on google. I'm installing the newest verison of the FTDI drivers for os x, have repaired permissions, I've deleted the kext from /System/Library/Extensions. The odd thing is that it worked fine when I first installed it, then I tried to load a program onto the board, and then it never worked again after that.
I'm getting to the point where I'm going to reinstall 10.5 again... but would rather fix the problem, or create a patch if possible... and ideas for troubleshooting/debugging this problem?
thanks in advance
What behavior do you see? Does the board work on any other computers? If it does, but it doesn't show up as a serial device at all on that one, you might try emailing FTDI support to see if they have any ideas: support1@ftdichip.com
I'm installing the newest verison of the FTDI drivers for os x, have repaired permissions, I've deleted the kext from /System/Library/Extensions.
You probably know this, but if you install a new FTDI driver, or remove one by deleting the kext from /System/Library/Extensions, you should reboot your machine to make sure the changes take effect cleanly.
If you're comfortable deleting the kext, then I would start from scratch by deleting the FTDI kext, restarting your machine, reinstalling the FTDI driver and restarting again.
After the drivers are installed, connect the Arduino to your computer with the USB cable - this should cause the driver to be loaded and the usbserial device to be created. Then, in a terminal window, type
ls /dev/*usb*
to verify that there's a tty.usbserial device. If there isn't, check your system logs for error messages. The following command lets you do that conveniently
bzgrep FTDI /var/log/system.log*
If things are working, then, after connecting the Arduino, the bzgrep command should reveal a message like
/var/log/system.log:Feb 16 07:57:17 teresa kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
If there was a problem loading the driver, I'd expect the system log to contain an error message, instead.
If things still don't work, here's a little shell script you can use to gather information that you can post here on the forums. It includes the commands suggested above and also extracts version information from the kext. To use it, copy the text into a file (like, "ftdi.sh") and then run it by saying "sh ftdi.sh".
#!/bin/sh
#
# Report information about the FTDI USB serial driver
#
echo "[Extensions]"
for KEXT in `ls -d /System/Library/Extensions/*FTDI*` ; do
echo $KEXT
find "$KEXT" -name InfoPlist.strings -exec cat {} \;
done
echo "[Devices]"
ls /dev/*usb*
echo "[System logs]"
bzgrep FTDI /var/log/system.log*
FWIW, I've been using Arduino 0100 successfully with a Diecimila and an old G4 Powerbook under MacOSX 10.4 and 10.5 (now 10.5.2), both with the original FTDI drivers that ship with Arduino 0100 and the latest drivers from FTDI's website.
Hi,
I'm running 10.5.2. on a PPC machine; I also needed to dl the FTDI driver. Now it's working and I see and select /dev/tty-usbserial.... After reading your messages, I hope it will remain this way :-X
what kind of macs are you using with 10.5.2? I noticed that there are two drivers on the FTDI driver download page, the (Intel)-one requires 10.4. ! Maybe that's the reason it stopped working?
btw:
it's surely a good idea to restart after installing a kernel extension, but not really necessary: Just open the terminal and type: sudo kextload /System/Library/Extensions/FTDIUSBSerialDriver.kext
you will be prompted for your admin-pw and then the new driver will be loaded (hopefully). If not, check if the path to the file is correct!
The same can be done to unload extensions with kextunload.
Best,
Michael
HI,
this is what the above "FTDI.sh" gives me back:
[Extensions]
ftdi.sh: line 7: : command not found
ftdi.sh: line 8: : command not found
[Devices]
/dev/cu.usbserial-A6007ZIp /dev/tty.usbserial-A6007ZIp
[System logs]
/var/log/system.log:Apr 24 18:20:50 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 20:37:29 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 20:37:36 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 20:41:42 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 20:47:40 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 20:51:59 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 20:58:02 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 21:09:53 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 21:17:01 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 21:30:00 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log:Apr 24 21:31:12 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log.0.bz2:Apr 17 20:13:03 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log.0.bz2:Apr 17 20:13:45 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log.0.bz2:Apr 17 21:41:46 360pixel kernel[0]: Safari[399] Unable to clear quarantine `FTDIUSBSerialDriver.pkg': 30
/var/log/system.log.0.bz2:Apr 17 21:47:51 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
/var/log/system.log.0.bz2:Apr 17 21:48:44 360pixel kernel[0]: FTDIUSBSerialDriver: 0 4036001 start - ok
How can i determine what port the driver is using? I need to tell that to my software...
Anybody could give me a hint? Thank you!!!
Problem solved (for me):
i had to set the following under the setting for the serial port:
" /dev/tty.usbserial-A6007ZIp" and all was well!
Thank you.
afaik, the last few numbers and chars ("*.usbserial-XXXXXXX") are generated randomly and are unique for each port. Best is, to look it up at the Arduino Menu or any other software that is able to list the available serial ports.
If you're on a *nix system like eg. Mac OS X, you can also open up the Terminal and type:
cd /dev
ls tty.*
cd /dev
ls cu.*
Remember to connect your device, else it won't show up!
Best,
Michael
Hi auco,
yes - i got that answer on the Apple discussion list where i asked too.
Thank you - and again i learned something today 
Is anyone connecting at 115200? I'm able to connect at 9600 (Macbook Pro 10.5) but no faster rate.