Re: Issues 179505

2013-06-21 Thread Adrian Chadd
Heh. yes.

I'm just saying. As someone who has hacked on this stuff a bit and
watched a lot of people hack on it, if their projects didn't work in
freebsd/pcbsd, they'd say "fuck it" and reinstall Linux.

If you'd like to further adoption of this stuff on FreeBSD, we have to
work around the brokenness. :(




Adrian


On 21 June 2013 17:34, Mike Meyer  wrote:
> On Fri, Jun 21, 2013 at 4:08 PM, Adrian Chadd  wrote:
>> On 21 June 2013 14:07, Hans Petter Selasky  wrote:
>>> I think I have one of these devices at work. I can have a look if I have
>>> time next week. Possibly the Arduino needs a fix. Look for so-called
>>> spurious VBUS pullup toggling in the software of the Arduino.
>> Considering there's a large number of unfixed Arduinos out there and
>> it works fine on Linux, Windows and FreeBSD, I don't think "fix the
>> arduino" should be the only solution.
>
> Did you mean "OSX" instead of FreeBSD there?
>
> While not really optimal, I'd consider it acceptable if the fix were
> in software, so that the Arduino IDE's "burn bootloader" menu entry
> could be used to fix the thing. But fixing things so it just worked
> would be better.
>
> Thanks,
> http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


Re: Issues 179505

2013-06-21 Thread Mike Meyer
On Fri, Jun 21, 2013 at 4:08 PM, Adrian Chadd  wrote:
> On 21 June 2013 14:07, Hans Petter Selasky  wrote:
>> I think I have one of these devices at work. I can have a look if I have
>> time next week. Possibly the Arduino needs a fix. Look for so-called
>> spurious VBUS pullup toggling in the software of the Arduino.
> Considering there's a large number of unfixed Arduinos out there and
> it works fine on Linux, Windows and FreeBSD, I don't think "fix the
> arduino" should be the only solution.

Did you mean "OSX" instead of FreeBSD there?

While not really optimal, I'd consider it acceptable if the fix were
in software, so that the Arduino IDE's "burn bootloader" menu entry
could be used to fix the thing. But fixing things so it just worked
would be better.

Thanks,
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


Re: Issues 179505

2013-06-21 Thread Adrian Chadd
On 21 June 2013 14:07, Hans Petter Selasky  wrote:


> I think I have one of these devices at work. I can have a look if I have
> time next week. Possibly the Arduino needs a fix. Look for so-called
> spurious VBUS pullup toggling in the software of the Arduino.

Considering there's a large number of unfixed Arduinos out there and
it works fine on Linux, Windows and FreeBSD, I don't think "fix the
arduino" should be the only solution.

Just saying,




Adrian
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


Re: Issues 179505

2013-06-21 Thread Hans Petter Selasky

On 06/21/13 20:17, Mike Meyer wrote:

Sorry 'bout the extra emphasis there.

Anyway, the problem is not *simply* the sketch code. It could be
something in the Arduino bootloader violating a USB spec that Linux
doesn't care about and FreeBSD does. But mucking about with the user
code on the Arudino (i.e. - sketches) doesn't change anything: I get
the same behavior whether it's running a trivial Blink demo (pretty
much no libraries used at all) or a complete interactive shell:

It works as expected when connected to Linux running on a VBox VM,
with the umodem device always being present.

If I don't connect it to the VM, the umodem device appears when the
board is plugged in or reset, then disappears before the sketch starts
running.


Hi,

I think I have one of these devices at work. I can have a look if I have 
time next week. Possibly the Arduino needs a fix. Look for so-called 
spurious VBUS pullup toggling in the software of the Arduino.


--HPS

___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


Re: Issues 179505

2013-06-21 Thread Mike Meyer
Sorry 'bout the extra emphasis there.

Anyway, the problem is not *simply* the sketch code. It could be
something in the Arduino bootloader violating a USB spec that Linux
doesn't care about and FreeBSD does. But mucking about with the user
code on the Arudino (i.e. - sketches) doesn't change anything: I get
the same behavior whether it's running a trivial Blink demo (pretty
much no libraries used at all) or a complete interactive shell:

It works as expected when connected to Linux running on a VBox VM,
with the umodem device always being present.

If I don't connect it to the VM, the umodem device appears when the
board is plugged in or reset, then disappears before the sketch starts
running.

On Fri, Jun 21, 2013 at 1:10 PM, Mike Meyer  wrote:
> This would help - if I were using the SoftSerial library
>
> The arduino sketch code is *not* the problem. Everything works fine if
> I just connect the board to a VBox runninng Linux, even on a FreeBSD
> host.
>
> On Fri, Jun 21, 2013 at 1:03 PM, Torfinn Ingolfsen
>  wrote:
>> On Fri, 21 Jun 2013 19:55:42 +0200
>> Torfinn Ingolfsen  wrote:
>>
>>> On Fri, 21 Jun 2013 10:28:41 -0500
>>> Mike Meyer  wrote:
>>>
>>> > Any chance I can get someone to look at
>>> > http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/179505? This was
>>> > discussed on the list, but sort of tailed off. There is more
>>> > information in the PR than was ever on the list.
>>>
>>> What code ("sketch") are you running on the Leonardo?
>>> According to thise page: http://arduino.cc/en/Guide/ArduinoLeonardo
>>> the board only has one mikrocontroller, so unless your program ("sketch") 
>>> on the Leo
>>> handles the usb communication, there will be none after the board resets.
>>> (if my understanding is correct)
>>
>> Ok, it seems like there is a bug / misfeature in SoftSerial on the Leo:
>> http://vort.org/2012/05/25/trouble-softserial-arduino-leonardo/
>> --
>> Torfinn Ingolfsen 
>> ___
>> freebsd-usb@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-usb
>> To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


Re: Issues 179505

2013-06-21 Thread Mike Meyer
On Fri, Jun 21, 2013 at 12:55 PM, Torfinn Ingolfsen
 wrote:
> On Fri, 21 Jun 2013 10:28:41 -0500
> Mike Meyer  wrote:
>
>> Any chance I can get someone to look at
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/179505? This was
>> discussed on the list, but sort of tailed off. There is more
>> information in the PR than was ever on the list.
>
> What code ("sketch") are you running on the Leonardo?
> According to thise page: http://arduino.cc/en/Guide/ArduinoLeonardo
> the board only has one mikrocontroller, so unless your program ("sketch") on 
> the Leo
> handles the usb communication, there will be none after the board resets.
> (if my understanding is correct)

I just tried BitLashDemo, which uses the umodem connection to provide
an interactive shell on the Arduino. Except it won't work on the
leonardo talking to FreeBSD, because it disconnects.

The sketch shouldn't matter. If I connect it to Linux running on a
VBox VM on FreeBSD, everything works as expected, no matter what
sketch is running.

I've updated the issue to note this.

 http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


Re: Issues 179505

2013-06-21 Thread Torfinn Ingolfsen
On Fri, 21 Jun 2013 19:55:42 +0200
Torfinn Ingolfsen  wrote:

> On Fri, 21 Jun 2013 10:28:41 -0500
> Mike Meyer  wrote:
> 
> > Any chance I can get someone to look at
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/179505? This was
> > discussed on the list, but sort of tailed off. There is more
> > information in the PR than was ever on the list.
> 
> What code ("sketch") are you running on the Leonardo?
> According to thise page: http://arduino.cc/en/Guide/ArduinoLeonardo
> the board only has one mikrocontroller, so unless your program ("sketch") on 
> the Leo
> handles the usb communication, there will be none after the board resets.
> (if my understanding is correct)

Ok, it seems like there is a bug / misfeature in SoftSerial on the Leo:
http://vort.org/2012/05/25/trouble-softserial-arduino-leonardo/
-- 
Torfinn Ingolfsen 
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"


Re: Issues 179505

2013-06-21 Thread Torfinn Ingolfsen
On Fri, 21 Jun 2013 10:28:41 -0500
Mike Meyer  wrote:

> Any chance I can get someone to look at
> http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/179505? This was
> discussed on the list, but sort of tailed off. There is more
> information in the PR than was ever on the list.

What code ("sketch") are you running on the Leonardo?
According to thise page: http://arduino.cc/en/Guide/ArduinoLeonardo
the board only has one mikrocontroller, so unless your program ("sketch") on 
the Leo
handles the usb communication, there will be none after the board resets.
(if my understanding is correct)

HTH
-- 
Torfinn Ingolfsen 
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"