to debugging: you can use a serial cable connected to the 2.5" jack (something like FTDI based one for osmocom motorola phones if you have one) - that's the debugging interface. I'm currently travelling and don't have my usb->serial cable with me so I will check back at home.

On Mon, Oct 3, 2011 at 8:29 PM, Peter Stuge <peter@stuge.se> wrote:

Holger Hans Peter Freyther wrote:
> > Mac OS is really really strict about USB descriptors being correct,
> > where both Windows and Linux are more lenient. But the error messages
> > say the device would not even accept the address it was assigned, so
> > there is some more fundamental problem with the USB firmware. :\
>
> any debug hints? it will be my first real adventure into the USB
> land. Right now I would just play trial and error to see how far in
> the setup things go.

The device address being assigned by the PC is very very early in the
USB enumeration (device discovery after plug-in) process, so
something goes wrong pretty early.

I understood that the firmware is based on an example firmware from
Atmel, so maybe look around their developer resources for any info
about known problems with Mac OS.

I would probably add some serial output to the firmware in main() and
in the USB interrupt handler, and try to see what differs between Mac
OS and other systems during enumeration.

I recall Harald mentioned an interrupt storm in some circumstances,
this could also cause the device address assignment to fail if it
isn't fixed already.

//Peter