USB problems on Arduino UNO with MacOSX?

[stefski66]

Basically, when plugged directly on my macbook pro, my arduino UNO is
powered, but does not show up: no dialog box for a new network device,
nothing in /dev/tty* etc. Same behavior with my USBtinyISP: nothing
in /dev, in "Usb Prober.app", console.app, dmesg etc.

After a lot of research on various forums, I ended up to this page:
http://mightyohm.com/blog/2010/09/improved-firmware-for-usbtinyisp-fixes-usb-issues-in-virtualbox/
. Basically, the USBTinyISP was not working when connected directly to
a USB port. But it would work if it were connected through a USB 1.1
device, such as a keyboard or a hub. I tried to connect the devices
through a keyboard connected to my mac: both the USBTinyISP and
arduino worked as expected.

I started a thread over at arduino forum that explains that:
http://arduino.cc/forum/index.php/topic,88195.0.html

My guess is that the problem and the solution for the arduino are the
same than the ones exposed in the above page: the USB stack on ISP and
on the arduino is faulty.

My question are: what do you think ? Have you heard about this kind of
problems before ? Do you think it can come from the USB stack ?

I can start to see if the last version of LUFA is better. But I'm not
sure to have understand everything. If I compile the sources in LUFA/
Bootloaders/DFU, can I burn the .hex directly onto my arduino ?

Best regards,

stephane

[Dean Camera]

Stephane,

I hope you don't mind me answering you here, rather than via email -
this way we keep a public record of problems and solutions (which is
then Google searchable) and allows others to chime in with their own
experiences and thoughts.

The USBTinyISP appears to be based around the ATMEGA2313, with the USB
protocol emulated in software, probably using the V-USB project. This
means that your programmer has nothing to do with LUFA, and thus any
similarities between the problems you have with your Arduino Uno (with
uses LUFA) and the USBTinyISP (which does not) is purely coincidental.

Unfortunately, not owning a mac, I can't really give you much guidance
there; with a kernel log output with the devices directly plugged in
and plugged in through a hub I might be able to guess where the issue
is, but I'm not sure what the command for this is on MacOS X (on
linux, it's "dmesg" from the terminal). This sounds like a
compatibility issue with the Macbook's hardware - do other full speed
(NOT high speed) USB devices work when plugged in directly?

Cheers!
- Dean

On Jan 24, 9:20 pm, stefski66 <conve...@gmail.com> wrote:
> Basically, when plugged directly on my macbook pro, my arduino UNO is
> powered, but does not show up: no dialog box for a new network device,
> nothing in /dev/tty* etc. Same behavior with my USBtinyISP: nothing
> in /dev, in "Usb Prober.app", console.app, dmesg etc.
>

> After a lot of research on various forums, I ended up to this page:http://mightyohm.com/blog/2010/09/improved-firmware-for-usbtinyisp-fi...

[I.T. Daniher]

Stephane,

The following commands, when run from terminal, will upload information about your computer to a pastebin and give you a link to share with the list.

system_profiler SPUSBDataType | curl -F 'sprunge=<-' http://sprunge.us

-> that's the equivalent of "lsusb" for OSX

dmesg | curl -F 'sprunge=<-' http://sprunge.us

-> that'll dump the kernel log which should report any failed attempts to enumerate your Uno.

I've had the occasional problem with the Uno on OSX, but never bothered to debug them, and I currently don't have an Uno available. 

Best,

--

Ian 

 

--
You received this message because you are subscribed to the Google Groups "LUFA Library Support List" group.
To post to this group, send email to lufa-s...@googlegroups.com.
To unsubscribe from this group, send email to lufa-support...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lufa-support?hl=en.

[Conversy Stéphane]

Le 29 janv. 2012 à 17:01, Dean Camera a écrit :

Stephane,

I hope you don't mind me answering you here, rather than via email -
this way we keep a public record of problems and solutions (which is
then Google searchable) and allows others to chime in with their own
experiences and thoughts.

No pb of course, thank you, I did not know that this forum exists. And I apologize for my first message: I copied/pasted it and forgot to say "hello".

The USBTinyISP appears to be based around the ATMEGA2313, with the USB
protocol emulated in software, probably using the V-USB project. This
means that your programmer has nothing to do with LUFA,

Yes I agree.

and thus any
similarities between the problems you have with your Arduino Uno (with
uses LUFA) and the USBTinyISP (which does not) is purely coincidental.

Unfortunately, not owning a mac, I can't really give you much guidance
there; with a kernel log output with the devices directly plugged in
and plugged in through a hub I might be able to guess where the issue
is, but I'm not sure what the command for this is on MacOS X (on
linux, it's "dmesg" from the terminal). This sounds like a
compatibility issue with the Macbook's hardware - do other full speed
(NOT high speed) USB devices work when plugged in directly?

I'm not sure to know the difference between the two. What works: USB sound monitors, hard drive, thumb driver, mouse.

Le 29 janv. 2012 à 17:36, I.T. Daniher a écrit :

Stephane,

The following commands, when run from terminal, will upload information about your computer to a pastebin and give you a link to share with the list.

system_profiler SPUSBDataType | curl -F 'sprunge=<-' http://sprunge.us

-> that's the equivalent of "lsusb" for OSX

http://sprunge.us/hNVj

dmesg | curl -F 'sprunge=<-' http://sprunge.us

-> that'll dump the kernel log which should report any failed attempts to enumerate your Uno.

http://sprunge.us/GiKG

I've had the occasional problem with the Uno on OSX, but never bothered to debug them, and I currently don't have an Uno available. 

thanks for helping me !

Cheers,

stéphane

Cheers!
- Dean

On Jan 24, 9:20 pm, stefski66 <conve...@gmail.com> wrote:

Basically, when plugged directly on my macbook pro, my arduino UNO is

powered, but does not show up: no dialog box for a new network device,

nothing in /dev/tty* etc. Same behavior with my USBtinyISP: nothing

in /dev, in "Usb Prober.app", console.app, dmesg etc.

After a lot of research on various forums, I ended up to this page:http://mightyohm.com/blog/2010/09/improved-firmware-for-usbtinyisp-fi...

. Basically, the USBTinyISP was not working when connected directly to

a USB port. But it would work if it were connected through a USB 1.1

device, such as a keyboard or a hub. I tried to connect the devices

through a keyboard connected to my mac: both the USBTinyISP and

arduino worked as expected.

I started a thread over at arduino forum that explains that:http://arduino.cc/forum/index.php/topic,88195.0.html

My guess is that the problem and the solution for the arduino are the

same than the ones exposed in the above page: the USB stack on ISP and

on the arduino is faulty.

My question are: what do you think ? Have you heard about this kind of

problems before ? Do you think it can come from the USB stack ?

I can start to see if the last version of LUFA is better. But I'm not

sure to have understand everything. If I compile the sources in LUFA/

Bootloaders/DFU, can I burn the .hex directly onto my arduino ?

Best regards,

stephane

--
You received this message because you are subscribed to the Google Groups "LUFA Library Support List" group.
To post to this group, send email to lufa-s...@googlegroups.com.
To unsubscribe from this group, send email to lufa-support...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lufa-support?hl=en.

Stéphane Conversy

Enseignant Chercheur en IHM - ENAC

http://lii-enac.fr/~conversy

+33 5 62 17 40 19

[Dean Camera]

Darn - neither of those logs gives anything I can go on. Was the
kernel log produced directly after inserting the failing device? If
not, please give two more logs; one just after plugging your LUFA
device straight into the faulty port, and one just after plugging it
into the hub where it works. Don't forget to label which is which for
me :).

Is there someone else on the list with access to a MacOS machine to
test this with? It would be helpful to know if this is a hardware
issue, or a OS issue.

Cheers!
- Dean

On Jan 30, 8:33 pm, Conversy Stéphane <stephane.conve...@enac.fr>
wrote:

> > For more options, visit this group athttp://groups.google.com/group/lufa-support?hl=en.
>
> Stéphane Conversy
> Enseignant Chercheur en IHM - ENAChttp://lii-enac.fr/~conversy

[Conversy Stéphane]

Le 12 févr. 2012 à 14:59, Dean Camera a écrit :

> Darn - neither of those logs gives anything I can go on. Was the
> kernel log produced directly after inserting the failing device?

yes

> If
> not, please give two more logs; one just after plugging your LUFA
> device straight into the faulty port, and one just after plugging it
> into the hub where it works.

the hub only:
system_profiler: http://sprunge.us/gRij
dmesg: http://sprunge.us/CafB

after having plugged in the arduino into the hub:
system_profiler: http://sprunge.us/jbVO
dmesg: http://sprunge.us/eEaL

I prefer to precise again that the LUFA stuff on my arduino may not be up-to-date, as I do not know how to do that exactly. Maybe a fresher driver already solves this issue.
Are the binary produced from the source tree of LUFA directly uploadable into the arduino ?
if so, how can I do that ?

thanks,

stephane

> For more options, visit this group at http://groups.google.com/group/lufa-support?hl=en.

[Dean Camera]

Stéphane,

Urgh, I am not keeping up with my email and support list responses as
much as I would like recently, and this one slipped me by. My
apologies.

> I prefer to precise again that the LUFA stuff on my arduino may not be up-to-date, as I do not know how to do that exactly. Maybe a fresher driver already solves this issue.
> Are the binary produced from the source tree of LUFA directly uploadable into the arduino ?
> if so, how can I do that ?

You could recompile the Projects/USBtoSerial/ demo with the makefile
adjusted for the Arduino UNO, but that may be missing some Arduino-
related changes to the code. Instead, you may wish to pull from the
official Arduino repository instead:

https://github.com/arduino/Arduino/tree/master/hardware/arduino/firmwares/arduino-usbserial/

And just compile that against the latest LUFA (which may require some
small changes due to renamed APIs). You can then reprogram the USB AVR
on the Arduino UNO board through the DFU bootloader preloaded onto the
chip - there are guides online on how to do this.

Cheers!
- Dean

On Feb 12, 4:04 pm, Conversy Stéphane <stephane.conve...@enac.fr>

[Conversy Stéphane]

Le 4 mars 2012 à 14:37, Dean Camera a écrit :

> Stéphane,
>
> Urgh, I am not keeping up with my email and support list responses as
> much as I would like recently, and this one slipped me by. My
> apologies.

Dean,

my turn to apologize, I did not give news.
Actually, I asked a friend-in-the-know to upgrade the arduino with latest firmware, and it works as expected now.

Here is what he did (for archival purpose in case someone finds out this thread) :

get the arduino-1.0 binary on their web site.
set arduino in dfu mode: http://hunt.net.nz/users/darran/weblog/faf5e/http://arduino.cc/forum/index.php/topic,52447.msg374201.html#msg374201
bash (root) :
$ cd arduino-1.0/hardware/arduino/firmwares
$ dfu-programmer at90usb82 erase
$ dfu-programmer at90usb82 flash --suppress-bootloader-mem --debug 1 UNO-dfu_and_usbserial_combined.hex
$ dfu-programmer at90usb82 reset
$ cd ../../..
unplug-replug
$ ./arduino

> For more options, visit this group at http://groups.google.com/group/lufa-support?hl=en.

[Dean Camera]

That's great news! Must have been a glitch corrected by the Arduino
team (or by myself in a newer LUFA distribution than the one used for
the shipping firmware).

Cheers!
- Dean

On Apr 3, 9:44 pm, Conversy Stéphane <stephane.conve...@enac.fr>
wrote:

> Le 4 mars 2012 à 14:37, Dean Camera a écrit :
>
> > Stéphane,
>
> > Urgh, I am not keeping up with my email and support list responses as
> > much as I would like recently, and this one slipped me by. My
> > apologies.
>
> Dean,
>
> my turn to apologize, I did not give news.
> Actually, I asked a friend-in-the-know to upgrade the arduino with latest firmware, and it works as expected now.
>
> Here is what he did (for archival purpose in case someone finds out this thread) :
>
> get the arduino-1.0 binary on their web site.

> set arduino in dfu mode:http://hunt.net.nz/users/darran/weblog/faf5e/http://arduino.cc/forum/...

> bash (root) :
> $ cd arduino-1.0/hardware/arduino/firmwares
> $ dfu-programmer at90usb82 erase
> $ dfu-programmer at90usb82 flash --suppress-bootloader-mem --debug 1 UNO-dfu_and_usbserial_combined.hex
> $ dfu-programmer at90usb82 reset
> $ cd ../../..
> unplug-replug
> $ ./arduino
>
>
>
>
>
>
>
>
>
>
>
> >> I prefer to precise again that the LUFA stuff on my arduino may not be up-to-date, as I do not know how to do that exactly. Maybe a fresher driver already solves this issue.
> >> Are the binary produced from the source tree of LUFA directly uploadable into the arduino ?
> >> if so, how can I do that ?
>
> > You could recompile the Projects/USBtoSerial/ demo with the makefile
> > adjusted for the Arduino UNO, but that may be missing some Arduino-
> > related changes to the code. Instead, you may wish to pull from the
> > official Arduino repository instead:
>

> >https://github.com/arduino/Arduino/tree/master/hardware/arduino/firmw...