Closed akuhtz closed 6 years ago
Looks like it is JVM side thing not serialpundit. Are you debugging something using a debugger.
http://bugs.java.com/view_bug.do?bug_id=6476706 https://stackoverflow.com/questions/27500398/debugging-java-in-eclipse-error https://www.eclipse.org/forums/index.php/t/1069715/
Hi Rishi,
Even from commandline it throws the same error:
D:\github\serial-communication-manager\prebuilt-release>java -classpath sp-core.jar;sp-tty.jar;. test23.Test23
com.serialpundit.core.SerialComException: The parameter is incorrect.
at com.serialpundit.serial.internal.SerialComPortJNIBridge.setRTS(Native Method)
at com.serialpundit.serial.SerialComManager.setRTS(SerialComManager.java:1505)
at test23.Test23.main(Test23.java:65)
Any change in driver or hardware.
Seems like a windows problem https://superuser.com/questions/84977/error-0x8007007a-when-trying-to-schedule-a-task/131310#131310 I saw answers like:
Hi Rishi, Will check on linux.
Hi Rishi, I tested on a raspi 3 and it worked without an exception.
Found one more info https://stackoverflow.com/questions/2225737/error-jdwp-unable-to-get-jni-1-2-environment
Seems like it should have been fixed already by JVM/Windows/IDE etc. Should we close it.
I see a similar exception with SPSW under Windows. Lets close it.
Hi Rishi,
I'm running Test23 under Win7 64bit and it causes an exception when setRTS() is called (scm.setRTS(DTE, true); )