Maple disconnects under Windows and Linux when uploading program

LeafLabs Garden » Support » Maple Hardware Support

Maple disconnects under Windows and Linux when uploading program

(19 posts) (5 voices)

Started 5 years ago by coreyfro
Latest reply from poslathian

12 Next »

coreyfro
Member

I just got my Maple in the mail and I cannot get it to operate on any platforms at my disposal. I have exhausted my capabilities trying to get my board up and running. I have tried ONLY with the IDE releases for Maple (haven't tried SVN checkout yet) and I have tried under 64bit Ubuntu 10.4, Windows XP 32bit, and Windows Vista 64bit. I have tried under USB power and under Lipo power (just in case the USB power was blacking out.) I did not try Lipo power until I had tested the board under all OS's available to me.

Specific results

Windows XP 32
* Board is detected
* Diver installs fine
* IDE loads
* When I upload Blink to the board
- The board resets
- Disconnects from the system
- the IDE returns "Lost Device after reset, assuming prod_id was incremented by one - No DFU capable USB device found"
- bootloader on maple completes
- Instead of user code running, the LED stays on solid
- Board does NOT redetect

Windows Vista 64
* Board is detected
* Diver installs fine
* IDE loads
* When I upload Blink to the board
- The board resets
- Disconnects from the system
- the IDE returns "Lost Device after reset, assuming prod_id was incremented by one - No DFU capable USB device found"
- bootloader on maple completes
- Board runs usercode
- Board is redetected

Ubuntu 10.4 64
* Board is detected
* IDE loads
* When I upload Blink to the board
- The board resets
- Disconnects from the system
- the IDE returns "No DFU capable USB device found"
- bootloader on maple completes
- Board runs usercode
- Board is redetected

I have put the board under the "Indefinite Wait" state as well, but in that state the board does not detect.

Here's the output from dmesg on my system after device is plugged into system, upload commend is issued, and error is returned:
[26815.660071] usb 4-2: new full speed USB device using ohci_hcd and address 77
[26815.896462] usb 4-2: configuration #1 chosen from 1 choice
[26815.899257] cdc_acm 4-2:1.0: ttyACM0: USB ACM device
[26836.083075] usb 4-2: USB disconnect, address 77
[26836.870140] usb 4-2: new full speed USB device using ohci_hcd and address 78
[26837.100472] usb 4-2: configuration #1 chosen from 1 choice
[26840.475012] usb 4-2: USB disconnect, address 78
[26841.260090] usb 4-2: new full speed USB device using ohci_hcd and address 79
[26841.506461] usb 4-2: configuration #1 chosen from 1 choice
[26841.509262] cdc_acm 4-2:1.0: ttyACM0: USB ACM device

How else can I help you help me help you?

Posted 5 years ago #
sbeckman
Member

Hi coreyfro;

I just got my board today too! After a bit of struggling with what turned out to be the wrong IDE (somehow I got hold of a "Custom Build" IDE which gave me compile problems) things are working fine.

I've seen the same error message you've reported on occasion. It will happen if I manually reset the board prior to trying a download. I've been able to clear the error, however, by manually resetting the board again, and letting it and the PC get through both USB enumeration steps -- DFU, then Serial, and then downloading the code again.

Hope this helps!

Posted 5 years ago #
bnewbold
Ex-Leaflabs

Hi coreyfro!

It sounds like you /did/ get usercode uploaded and running from Windows Vista 64 and Ubuntu 10.4 64 despite a lot of DFU errors in the IDE? Or when you say "Board runs usercode" do you mean that it's running the default usercode that we flashed before shipping?

Thanks so much for debugging, i'll read you message more carefully and reply again in a couple hours when I get back to the office!

Posted 5 years ago #
bnewbold
Ex-Leaflabs

Hi coreyfro, i'm not going to have time to really dig in to this with you for another day or two; in the short term you could try tweaking the "Delay after reset" parameter in the preferences window of the IDE (or editing the preferences.txt file by hand if there's a problem).

Posted 5 years ago #
coreyfro
Member

sbeck: Alas, I wouldn't be surprised if I've done this 100 times. The board has plenty of time. It just resets on upload, and then disconnects.

bnewbold: I speak of the default usercode. The blinking sketch that looks like it blinks 4 times a second? My sketch would have been once every other second.

Posted 5 years ago #
poslathian
LeafLabs

Good news everyone! I was gritting my teeth waiting for this problem to be reported because I am well familiar with it and its solution.

TLDR: Go to preferences menu, set the "program delay" to about 1000, or fiddle with it. On older java builds, this part of the dialogue has been reported malrendered, in which case, hit the "edit preferences.txt" at the bottom and find the programDelay field, mod a restart the ide.

The actual story:
Read http://leaflabs.com/docs/maple-bootloader/ for some info on how the bootloader works. Unlike arduino and maple r1, where the DFU driver (or FTDI serial driver in arduino's case) is always loaded, Maple r3 only loads the DFU driver temporarily during startup. In user mode, Maple runs as a CDC ACM virtual COM device, which uses a different driver.

Thus, during the upload process, the board resets, unloading the CDC ACM driver, then reboots as a DFU device, loading a different driver. The unloading and reloading process takes different amounts of time depending on machine configuration/OS and operating load. Thus it was tricky business to minimize this delay and still have it work out of the box. Clearly we were too aggressive here. In the later builds, the delay will default to 1000 instead of 600 (ms).

Whats really annoying, is that the internal bootloader time-to-live has to be long enough to allow for all this nonsense and the first DFU transaction request. Which is why its set for so long right now (6 seconds).

Weve been toying with different solutions to this problem, please do offer your feedback on the proposals, the leaders are:

1) If the board is reset via the serial DTR pulse (that is, reset from the IDE for programming), make the bootloader live longer...really long, like 7 seconds. Otherwise, make the bootloader quick..maybe 800ms, enough to put it perpetual mode.
The downside here is that wed have to link libmaple and the bootloader codewise through some runtime pointers, which is pretty hairy, although we did it in R1, where the bootloader provided all of the usb support to the user lib via a runtime library.

2) Add some hook into the IDE to call DFU util immediately AFTER PROVING that the device's drivers have loaded up. This would be ideal, but has the downside of being different on every platform. Also it doesnt solve the fact that some OS's really do take a while to load the drivers and so the bootloader delay is still long.

Sorry for the hassle, we tested on a bunch of machines to arrive at the 600 number, but I guess that just wasnt enough.

Posted 5 years ago #
poslathian
LeafLabs

Good news everyone! I was gritting my teeth waiting for this problem to be reported because I am well familiar with it and its solution.

TLDR: Go to preferences menu, set the "program delay" to about 1000, or fiddle with it. On older java builds, this part of the dialogue has been reported malrendered, in which case, hit the "edit preferences.txt" at the bottom and find the programDelay field, mod a restart the ide.

The actual story:
Read http://leaflabs.com/docs/maple-bootloader/ for some info on how the bootloader works. Unlike arduino and maple r1, where the DFU driver (or FTDI serial driver in arduino's case) is always loaded, Maple r3 only loads the DFU driver temporarily during startup. In user mode, Maple runs as a CDC ACM virtual COM device, which uses a different driver.

Thus, during the upload process, the board resets, unloading the CDC ACM driver, then reboots as a DFU device, loading a different driver. The unloading and reloading process takes different amounts of time depending on machine configuration/OS and operating load. Thus it was tricky business to minimize this delay and still have it work out of the box. Clearly we were too aggressive here. In the later builds, the delay will default to 1000 instead of 600 (ms).

Whats really annoying, is that the internal bootloader time-to-live has to be long enough to allow for all this nonsense and the first DFU transaction request. Which is why its set for so long right now (6 seconds).

Weve been toying with different solutions to this problem, please do offer your feedback on the proposals, the leaders are:

1) If the board is reset via the serial DTR pulse (that is, reset from the IDE for programming), make the bootloader live longer...really long, like 7 seconds. Otherwise, make the bootloader quick..maybe 800ms, enough to put it perpetual mode.
The downside here is that wed have to link libmaple and the bootloader codewise through some runtime pointers, which is pretty hairy, although we did it in R1, where the bootloader provided all of the usb support to the user lib via a runtime library.

2) Add some hook into the IDE to call DFU util immediately AFTER PROVING that the device's drivers have loaded up. This would be ideal, but has the downside of being different on every platform. Also it doesnt solve the fact that some OS's really do take a while to load the drivers and so the bootloader delay is still long.

Sorry for the hassle, we tested on a bunch of machines to arrive at the 600 number, but I guess that just wasnt enough.

Posted 5 years ago #
poslathian
LeafLabs

Oh, and additionally:

when in "infinite bootloader mode" the board wont detect. This is OK. This is because the bootloader has no serial port! However, it should show up in your usb devices list as a DFU device, but not in the ide serial port menu.

The board will still program just fine in this mode! The serial port is only used during upload in order to send the reset command. In infinite bootloader mode, no reset is needed, so dfu just proceeds along its merry way. The ide should report this to you.

Happy hacking, sorry for the troubles. Obviously a plug-and-play is what we were going for, I'm very dissapointed we missed that mark because of this issue (that I was keenly aware of as a potential misstep and tried hard to prevent...ugh!)

Posted 5 years ago #
poslathian
LeafLabs

Post post script: this issue should be fixed in 0.0.4, which includes a bump to default program delay to 1000. The program delay is the lag between when the board is reset, and when dfu-util is actually called. During this delay, both the maple bootloader needs to boot and the host OS needs to load the DFU drivers...unfortunately, the latter operation is not a fast process, and highly nondeterministic. 0.0.4 should be posted soon.

Posted 5 years ago #
coreyfro
Member

OK, well that info was enough to get SOMETHING uploaded. It took these tweaks, and some just brute force hammering and button mashing to get it working.

My windows install WILL NOT work here because windows takes all of 10 seconds to go from reset to reenumeration of serial port. By which, I am sure the bootloader window is long gone.

I'll have to look in to the infinite bootlader mode and how to use it. I've seen the message you refer to, but didn't know what to make of it.

Posted 5 years ago #
coreyfro
Member

Recreated success. Under Ubuntu, I just simply hit the reset button TWICE moments before I hit the upload button and by the time the IDE is ready to upload, Linux has had enough time to enumerate the serial port.

Button Mashing 4 teh Win!

Posted 5 years ago #
poslathian
LeafLabs

Heh, great, although im concerned that simple tweaking of the delay was not sufficient. If you really want to get dirty, you can recompile the bootloader with an even longer delay, its in git: maple-bootloader/config.h add to the number of startup blinks. Use bryans instructions elsewhere in the forums for bootloader upgrade issues. However, its pretty long as is, there should be a programDelay that works for you.

Just a point of clarification. It should ALWAYS work in infinite bootloader mode (well, this problem wont exist anyway...). Also, the serial port should not enumerate until AFTER the bootloader has exited. The serial port is compiled into user programs via libmaple. It is not a part of the bootloader. The Bootloader should enumerate as Maple 003, which is a DFU device.

Posted 5 years ago #
coreyfro
Member

Oh, also, I was running as root.

Yeah, if I simply try changing the timers, I get all sorts of interesting errors. There are three outcomes and I cannot determine what invokes which:

No DFU capable USB device found
dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

And unless I run as root

Loading via dfu-util

Resetting to bootloader via DTR pulse

dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x1eaf:0x0003...
Found Runtime: [0x1eaf:0x0003] devnum=0, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Cannot claim interface: could not claim interface 0: Operation not permitted

And this happens about 20% of the time.

Error inside Serial.serialEvent()
java.io.IOException: Invalid argument in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
Error inside Serial.serialEvent()
java.io.IOException: Input/output error in nativeavailable
at gnu.io.RXTXPort.nativeavailable(Native Method)
at gnu.io.RXTXPort$SerialInputStream.available(RXTXPort.java:1596)
at processing.app.Serial.serialEvent(Serial.java:215)
at gnu.io.RXTXPort.sendEvent(RXTXPort.java:772)
at gnu.io.RXTXPort.eventLoop(Native Method)
at gnu.io.RXTXPort$MonitorThread.run(RXTXPort.java:1641)
No DFU capable USB device found
dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Posted 5 years ago #
poslathian
LeafLabs

Yea that last one I have definitely seen before, but oddly its not fatal. In fact, the upload was working for me when I saw it. It started cropping up when we upgraded versions of our java serial libs (librxtx). This upgrade did buy us the ability to list ttyACM0 in the serial port panel, whereas the earlier version did not (you had to symlink it). Its on our bug stack. Let us know if you learn anything.

Posted 5 years ago #
coreyfro
Member

GOOD! I'm glad I have an uninteresting error. It's the interesting ones that leave you with broken hardware for months ;-)

I'll work around it for now. We'll see if it still works when I have a larger piece of code to send it's way.

Posted 5 years ago #

RSS feed for this topic

12 Next »

Reply »

You must log in to post.