Just finished building my usbtinyisp. Plugged it into my Powerbook running Mac OS X 10.4.11. Green light on the usbtinyisp is on.
Problem: no device is showing up on /dev.
If I use the very same cable to plug it into an Arduino, a device shows up as /dev/cu.usbserial-A4001ttB, so it's not the cable or the USB port.
I thought that the Mac doesn't need any additional drivers to be installed, but maybe I'm mistaken.
I looked over the board for any obvious soldering problems, and checked a few key voltages. Any further diagnostic tips would be much appreciated.
Thanks for your help,
Steve
usbtinyisp not showing up as a Mac OS X device
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- rglenn
- Posts: 20
- Joined: Thu Oct 04, 2007 10:36 pm
-
- Posts: 3
- Joined: Sun Jan 27, 2008 1:44 pm
Thank for the reply, rglenn.rglenn wrote:The USBtinyISP doesn't act as a serial port, and thus won't show up in /dev. You'll need to use avrdude to access it through the libusb library (which, I admit, might be an overly technical way to describe it).
How are you trying / intending to program with the USBtinyISP?
I was intending to use avrdude to program an ATmega168 on a breadboard, per the tutorial on the Sparkfun site, but using the usbtinyisp:
http://www.sparkfun.com/commerce/presen ... BEE-2-Code
But what do I enter for the -P parameter of avrdude? All of the Mac AVR tutorials out there talk about finding the USB device by just doing an "ls /dev/cu.*". Nothing looks obvious to me as the USB device.
I'm using the OSX-AVR toolset plus the 5.4 version of avrdude.
Thanks,
Steve
Last edited by Wawona on Mon Jan 28, 2008 5:15 pm, edited 1 time in total.
-
- Posts: 472
- Joined: Tue Jan 08, 2008 12:43 am
You don't specify anything for the -P
It's hard to describe, but libusb basically allows an application to interact directly with the USB stack. (In some ways, it's a USB-only variant of the "drivers in userspace" projects that have recently been integrated into the Linux kernel.)
avrdude will use libusb to look for a specific USB Vendor/Product ID and interact directly with it. As a result, the USBTinyISP will never show up as a regular device in /dev - All that matters is that it shows up with the correct VID/PID in lsusb on Linux or whatever the equivalent is in OSX.
All you need to supply avrdude is "-c usbtiny" plus the other programming options. No need for -P.
It's hard to describe, but libusb basically allows an application to interact directly with the USB stack. (In some ways, it's a USB-only variant of the "drivers in userspace" projects that have recently been integrated into the Linux kernel.)
avrdude will use libusb to look for a specific USB Vendor/Product ID and interact directly with it. As a result, the USBTinyISP will never show up as a regular device in /dev - All that matters is that it shows up with the correct VID/PID in lsusb on Linux or whatever the equivalent is in OSX.
All you need to supply avrdude is "-c usbtiny" plus the other programming options. No need for -P.
Please be positive and constructive with your questions and comments.