ioiodude hangs on latest Mac OSX

[Xing Hu]

Symptom: after typed "./ioiodude --port=/dev/tty.usbmodem1411 versions", nothing happens no matter how long I wait.

"./ioiodude" works OK with usage instructions.

Tried:

1. Different micro usb lines (look like this so I suppose they are Micro-B)

2. Different usb ports (identified as usbmodem1411 at left side port while usbmodem1421 at right side port)

3. Different Macbook (mine and my wife's, however, both at El Capitan)

4. Different JDK versions, from 6 to 8, all 64bits.

5. Host switch at "A" and at "H".

6. CHG at different position (yes I'm desperate...).

7. Boot in bootloader mode and application mode 

8. sudo

9. "./ioiodude --port=/dev/tty.usbmodem1411 --reset write xxxx.ioioapp" (desperate)

None working....

Any suggestion? 

Thanks!

 

[Xing Hu]

Tried HelloIOIOConsole.jar from the App 330 package (since I'm running an IOIO with 3.30 firmware):

[D/IOIOConnectionRegistry] Successfully added bootstrap class: ioio.lib.pc.SerialPortIOIOConnectionBootstrap

[D/SerialPortIOIOConnectionBootstrap] Adding serial port /dev/tty.Bluetooth-Incoming-Port

[D/IOIOImpl] Waiting for IOIO connection

[V/IOIOImpl] Waiting for underlying connection

[V/IOIOImpl] Waiting for handshake

And hangs all the time at there. Seems to me that I can not establish connection with IOIO board.

[Ytai Ben-Tsvi]

Does the IOIO enumerate correctly, i.e. does the usbmodem file appear when you connect? If so, can you try to open this virtual file using a terminal program such as 'screen' and let me know whether you get any output? It's possible that the new version of osx changed something that's causing the PJC library that's used by the IOIO libraries and tools to access the virtual serial port from java to break.

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ioio-users+...@googlegroups.com.
To post to this group, send email to ioio-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.

[Xing Hu]

The usbmodem file does appear. How exactly to use "screen" for that purpose? I understand it is for multi-terminal management...

[Xing Hu]

Well it is very likely to relate with some changes in the latest OSX. IOIO was successfully connected and upgraded to the 5.06 firmware with my Raspberry pi. So it rules out the doubt on the board itself and related software. The only obvious variant in this experiment is operating system.

On Wednesday, December 23, 2015 at 12:21:29 PM UTC-8, Ytai wrote:

[Ytai Ben-Tsvi]

One experiment you can do is to try an build HelloIOIO yourself, but override the purejavacomm dependency to use the latest version.
Otherwise, I'll look at it in a few days.

[Xing Hu]

Tested purejavacomm 0.28 and 0.29 (latest), still not working. Also tried upgrading JNA to latest 4.2.1, not helping. 

Lol...

[Ytai Ben-Tsvi]

And did you try with screen?

[Xing Hu]

Yes. I tried "screen /dev/tty.usbmodem1421" and got:

IOIOSPRK0020IOIO0400IOIO0506

Best Regards,

Xing

--
You received this message because you are subscribed to a topic in the Google Groups "ioio-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ioio-users/E5IOcANUVAs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ioio-users+...@googlegroups.com.

[Ytai Ben-Tsvi]

Cool. Then it's almost certainly a PJC issue. You can check with them regarding El Capitan compatibility, or I will as soon as I get back from vacation :)

[Xing Hu]

PJC stands for "Pluggable Java Components" right? A little out of my knowledge range lol... Googled "Pluggable Java Components El Capitan" and got no related news.

Reading about PJC now...

Best Regards,

Xing

[Ytai Ben-Tsvi]

Purejavacomm

[Xing Hu]

Oh, yeah, right... Still no related search results popped out... Should we open an issue to them? 

Best Regards,

Xing

[Ytai Ben-Tsvi]

You can either do this yourself or wait a few days until I'm back home.

[Xing Hu]

I'd like to do it myself lol but still need some pointers from you... Any suggestion to do next?

Best Regards,

Xing

[Ytai Ben-Tsvi]

The developer of pjc is familiar with the IOIO and you can reach him on his mailing list and tell him that El Capitan seems to have broken something. If you end up getting to many questions that you can't answer, send me a link to the thread and I'll chime in.
Thanks!

[Xing Hu]

Great. Thank you!

Best Regards,

Xing

[Xing Hu]

Submitted an issue to PJC at here: https://github.com/nyholku/purejavacomm/issues/78

[Ytai Ben-Tsvi]

This turned out to be an issue with the IOIO side of things. I'll push a fix soon.

[Ytai Ben-Tsvi]

This turned out to be an issue with the IOIO side of things. I believe I have fixed it and will publish a new release soon. Thanks for reporting the issue!

[Xing Hu]

Just got back home. Verified working! Great work Ytai! Thanks.

Actually, I suspected this setDTR because of the comment saying it only works for Windows, and at my side ioio only worked on Windows, so I commented it out and got no luck. Lol, so close!

Best Regards,

Xing

[Xing Hu]

Well. Hope it didn't ruin your Christmas mood, lol

[Ytai Ben-Tsvi]

Hey Xing,

Can you please test IOIOLib 5.07 and IOIODude 1.03 on El Capitan and Ubuntu 14.04 and let me know if there are still any issues?

In addition, can you provide some feedback about whether or not you needed some special udev rule to disable modem-manager messing with the IOIO to get it working? I cannot reproduce this on a VM.

Thanks!

[Xing Hu]

Hi Ytai,

Both IOIOLib 5.07 and IOIODude 1.03 verified on my latest El Capitan (10.11.2).

Also verified working on Ubuntu 14.04 (running on Parallels), and YES, I do need the special udev rule to disable modem-manager interfering with IOIO. Otherwise still not be able to establish connection.

Well, two more things:

1) The latest wiki page describing IOIO with PC somehow deleted the part of "modem manager interference". I managed to find it in Google's cache.

2) Seems like you used Java 8 to build the latest IOIOLib and IOIODude. It's totally fine for me (already using it for a year) but I'm not sure about others...

Best Regards,

Xing

[Ytai Ben-Tsvi]

I deleted the section from the wiki and instead updates the udev rules file. Can you test it? Also, I've noticed that Ubuntu would not release DTR when the app exits, which sucks, but I'll try to at least set it to false whenever the app exits cleanly...

[Xing Hu]

Well it does not work for me...I still need to create a dedicated rule 78-mm-usb-device-blacklist-local.rules as your previous instruction. Not sure why yet...

Best Regards,

Xing

[Ytai Ben-Tsvi]

Are you sure? Have you tried restarting udev, unplugging the IOIO, etc? The rules should be equivalent, the file name should not matter.

[Xing Hu]

My mistake. Somehow I didn't to add the last line "ATTRS{idVendor}=="1b4f", ATTRS{idProduct}=="0008", ENV{ID_MM_DEVICE_IGNORE}="1"" into the rules file...So yes 1) still need this line to disable modem manager, and 2) it works with ioio udev rules.

Best Regards,

Xing

[Ytai Ben-Tsvi]

Just to verify: you're saying that the new rules file now available on the downloads page works without any further modifications, right?

[Xing Hu]

Yep, that's right.

Best Regards,

Xing

[Mohnish Kumar]

 found this thread from Google, and IOIODude 1.03 does give me an output when the board is plugged in Application Mode. But when I plug it in using the bootloader sequence, I am not getting any output from  ./ioiodude --port=/dev/tty.usbmodem1411 versions. (The board is being detected by OSX - El Capitan on  /dev/tty.usbmodem1411 in this case). 

Xing seems to have got it working. Where am I going wrong here? 

screen /dev/tty.usbmodem1411 output (in bootloader mode): 

BOOTSPRK0020IOIO0400IOIO0030

I havent done anything with udev rules, since the documentation only mentions that it is needed for Linux, not OSX. Should I do that? 

[Xing Hu]

Hi Mohnish,

I just tested mine in Bootloader mode, didn't work either :(

Previously I only tested it in Application mode because it wouldn't work even in Application mode. And when I found out it worked on Windows, I upgraded the application firmware on Windows so I never thought about testing it in Bootloader mode on El Capitan again...

So to sum up:

1) 1.02 IOIODude (and client-side software version 5.06 or earlier) won't be able to establish connection with IOIO board on El Capitan.

2) 1.03 IOIODude (and client-side software version 5.07) fixed "half of" the problem and it is able to establish connection with IOIO board in Application mode on El Capitan. But still won't connect in Bootloader mode.

Best Regards,

Xing

[Mohnish Kumar]

Thanks for the update Xing.. Good to know I wasnt missing something.. Borrowed a windows laptop to flash the updated firmware, sorted it for me.. 

[Ben]

No update. It seems not to work on newer Sierra either. Do I have to switch to PC?

B.

Best Regards,

Xing

Yep, that's right.

Best Regards,

Xing

Best Regards,

Xing

Visit this group at <a href="https://groups.google.com/group/ioio-users" rel="nofollow" target=