JVM error
I get these kinds of errors on occasion:
[noparse][[/noparse] Error IDE-0042] Unknown unhandled exception in JVM (736).
Any good way to go about troubleshooting these?
Dan
[noparse][[/noparse] Error IDE-0042] Unknown unhandled exception in JVM (736).
Any good way to go about troubleshooting these?
Dan
Comments
it occur, and then after you reset the javelin it sometimes does not occur ?
Are you using a Board of Education USB ?
regards peter
It's in a breadboard. I've created my own interface to use it with my serial port.
As I was running the test again I got these errors:
[noparse][[/noparse] Error IDE-0015] Stack trace is corrupt.
[noparse][[/noparse] Error IDE-0024] Unknown bytecode in the JEM file (dup_x2).
I'm curious why you ask. Do you think my serial connection is flaky?
Thanks,
Dan
sometimes present on a USB connection.
What brand/type of PC do you use? There were 3 threads recently
reporting serial port issues on Dell PC's.
Can you use the function Terminal.getChar?
Try attached program.
regards peter
What am I doing with this program? It appears to work. When I type a character it prints "received character {0xXX}"
Dan
help· clear· bell cmd· flash
followed by enter.
If the javelin receives the command correctly it will perform the function.
See this thread about the Dell PC's.
http://forums.parallax.com/showthread.php?p=702197
regards peter
Dan
Does that mean you have the javelin in the breadboard, then use wires
from javelin pin1-pin4 to a DB9 connector, then a straigth DB9 cable to your
PC com port?
I have read in several post on the propeller forum that breadboards
have quite a capacitance on their connection holes. This, or a bad
connection, can cause these occasional errors. If possible, put in
a DIL24 socket first, with wires soldered to its pins 1-4 that
go to the DB9 connector. Then at least you know the
connections to your PC com port are ok. Then put the
javelin in the DIL24 socket.
regards peter
I'm not sure I could buy the capacitance thing. If there was any it's probably down in the picofarads. With a maximum possible frequency of ~38kHz, the reactance would be no less than 600k. I could be wrong but I would consider this sufficient enough to keep the lines separate.
But, since you bring up serial line corruption, I did have a problem with RF interference at the beginning of the project that I thought I had nailed, I can try an experiment to eliminate that possibility.
Thanks again for the info, the original error message didn't mean anything to me, at least I have something to work off of.
Dan
Even if I get an unhandled exception, do you have a list of the error numbers, and would it be of any use to me? I just received an 812, I get several different numbers.
Dan
http://forums.parallax.com/showthread.php?p=550606
The number specified by Unhandled exception is the address at which
a class header should be located but isn't, which makes me believe
the error received is not the right value. This kind of errors
can occur with a bad serial connection,· even if download and Identify
appear to work.
Do you have a parallax usb2ser cable that you can try?
This at least solved the serial port problems on Dell PC's for other users.
regards peter
Dan