Fazecast / jSerialComm

Platform-independent serial port access for Java
GNU Lesser General Public License v3.0
1.35k stars 287 forks source link

Doesn't work with ACME arietta board / ARM AT91SAM9G25 #267

Closed bpinochet closed 4 years ago

bpinochet commented 4 years ago

The error message is:

A fatal error has been detected by the Java Runtime Environment:

SIGILL (0x4) at pc=0xb000f828, pid=664, tid=0xafd2e460

JRE version: Java(TM) SE Embedded Runtime Environment (8.0_211-b12) (build 1.8.0_211-b12) Java VM: Java HotSpot(TM) Embedded Client VM (25.211-b12 mixed mode linux-arm ) Problematic frame: C [1167609999799-libjSerialComm.so+0x3828] Java_com_fazecast_jSerialComm_SerialPort_configPort+0x458

Core dump written. Default location: /mnt/dump/core or core.664

If you would like to submit a bug report, please visit: http://bugreport.java.com/bugreport/crash.jsp The crash happened outside the Java Virtual Machine in native code. See problematic frame for where to report the bug.

The system is composed with:

I manage to make it working by using the ARM 5 / linux .so library from the .jar file. I unzip jar file and copy the arm5 .so file into the arm6 .so location.

So the jserialcomm had chosen the bad .so binary to deploy.

My /proc/cpuinfo gives the following:

processor : 0 model name : ARM926EJ-S rev 5 (v5l) BogoMIPS : 198.76 Features : swp half thumb fastmult edsp java CPU implementer : 0x41 CPU architecture: 5TEJ CPU variant : 0x0 CPU part : 0x926 CPU revision : 5

Hardware : Atmel AT91SAM9 Revision : 0000 Serial : 0000000000000000

Is it possible to add this CPU to the main class loading processus ?

hedgecrw commented 4 years ago

Sorry for the delay! Please try the following version and see if it works for you:

https://www.dropbox.com/s/2dny6rvpvpa3fi5/jSerialComm-2.5.4-test.jar?dl=0

hedgecrw commented 4 years ago

This change was actually released as part of the new official library version (2.6.0). Please try the newest version and see if that works for you!

hedgecrw commented 4 years ago

Closing this issue as fixed/resolved. Please re-open if you experience further similar problems.

bpinochet commented 4 years ago

Thank you. Now it works. I included the 2.6.2 version.

(Sorry for my late answer)