The JVM reset will invoke the executive reset for that JVM which includes the initialization of all software drivers and threads. (The
prior instance of the JVM is TOTALLY forgotten and its memory space is reused in the same way as the first instance. Hence the created objects
will end up at the same address.) The setup of the aJ-100 and its configuration registers remains untouched.

Attached is a very simple example of how to invoke this JVM reset: restart.java.

There are also 3 buildtime txt files in" C:\ajile\Runtime_cldc\txt" that need to be modified to get access to this instruction. The files included here are from from the 3.14 release and you will need to make the modification to the file in 3.16.09 -- among others, change the path for the native methods as follows:

1. startup.txt - Search for "trap26" in this file and you will find the path for the trap26 handler I used for the example. You'll need to replace the path with your own.
2. replace.txt - Again, search for "trap26" in this file and you will find the path for the trap26 handler I used for the example. You'll need to replace the path with your own. In addition, you will need to replace the path for the halt method immediately following the trap26 entry.
3. jemcodes.txt - you will need to use this modified file but you don't have to make any changes.