Not a question, but might be helpful to others encountering similar issues.
On Fedora the Mojo USB connection is created at port /dev/ttyACM0 (in my case)
In order to access /dev/ttyACM0 the user needs to be part of the 'dialup' group.
This change was not enough to make the loader stay alive when selecting a port.
The MojoLoader distributed in mojo-loader-1.1.2-linux64.tgz tries to create 'lock' files to regulate port usage.
Fedora does not allow lock files to be created at the location that is used.
I tried the following workaround:
- install package rxtx from the repositories
This package is configured to write locks in the appropriate location (performed by native librxtxSerial.so)
But unfortunately the java RXTXcomm.jar is programmed only to present /dev/ttyS* devices as available (this is the default behavior of the java code in the RXTX project).
I assume the sources of RXTXcomm.jar where modified to also show /dev/ttyACM* devices.
As a workaround I mixed both distributions and replaced the librxtxSerial.so as delivered in the mojo-loader with the library from the Fedora package.
(overwrite the existing library in mojo/lib with the version in /usr/lib64/rxtx/librxtxSerial.so)
This works, but shows a warning about mixing the java code of one version with the native library of the other (smart code).
Hope this helps someone, because it took me a night figuring this one out.
2 posts • Page 1 of 1