JEVM Running

Now you can already run JEVM using the loader. While you can execute the JEVM Loader tool directly, it is strongly advisable to use one of the supplied .bat files depending on the DSK you have set up. For instance, if you have the DSK6416 board, you should use the jevm6416.bat file.

The loader is called by its name jevmload.exe (note you should have the path c:\fadata\jevm\bin into your PATH environment variable), the option -f specifies the board data file, dsk6416.dat in our case (note you should have the JEVM_DIR environment variable set to c:/fadata/jevm), the option -d specifies the driver file (that you have copied) and the JEVM executable name is jevm6416.out. The other command line options instruct the loader to initialize the EMIF on board (-c options), to reset the DSP (-r option) and to support CIO and wait for completion (-i option).

Example (use a CommandPrompt Window) with DSK6416, analogous for the other DSK:

Make sure c:\fadata\jevm\bin is in the PATH.
Make sure SUN Java SDK bin is in the PATH, e.g. c:\jdk1.6.0\bin. 
Make sure you have JEVM_DIR environment variable set to c:/fadata/jevm.
Make sure you have TI_DIR environment variable set to your CCS installation folder, e.g. c::/CCStudio_v3.2.
Change to c:/fadata/jevm/dsk/dsk6416
Execute
    make clean
Execute
    make
Execute
    set CLASSPATH=c:/fadata/jevm/java/Bytecodes
Execute
    jevm6416 TestAll

Now you should see lots of output at the CommandPrompt window, because JEVM6416 is executing a test. After the test finishes, JEVM completes and control returns to the shell.

Note: If you start JEVM without any arguments it displays a message requesting for Java class file name and optional arguments. You can enter test name here.

Note: The current directory of your CommandPrompt window is the JEVM current directory when JEVM is executing. If you include '.' (dot) in your CLASSPATH, JEVM will be able to execute Java class files from this directory. Also, all relative paths in the tests will be relative to this directory.