The TINI Software
In this chapter we are going to examine in detail the various software programs and Application Program Interface (API) packages you will be using to program the TINI microcontroller. To make full use of this chapter you should already have the TINI up and running and be familiar with the TINI hardware. We will discuss all of the software that you can download from Dallas Semiconductor for your TINI and even a few other programs that will help you with program development
We briefly mentioned JavaKit in Chapter 5. JavaKit is a program that is supplied by Dallas Semiconductor for communicating with the TINI over a serial port connection. JavaKit is used to download applications to TINI, run programs on TINI and config- ure TINI’s network and server settings.
JavaKit is written in Java and the source can be downloaded from the TINI web site, should you find a reason for studying the source or modifying it. Because JavaKit communicates with your TINI through a serial port, it requires the Java Communications API that you installed in Chapter 3. JavaKit will run on any platform to which the Communications API has been ported (Windows 95/98/NT/ 2000/XP, Linux).
You can run JavaKit from Windows with the following command line:
java -cp \opt\jdk\lib\comm.jar;\opt\tini\bin\tini.jar JavaKit
where \opt\jdk is the installation directory for the Java SDK and \opt\tini is the installation directory for the TINI API.
You can run JavaKit on Linux with the following command:
java -cp /opt/jdk/lib/comm.jar:/opt/tini/bin/tini.jar JavaKit
For the remainder of this book we will be showing only Windows commands unless there is a significant change for the Linux commands (such as in the case where we make a c-shell script or something that does not translate as easily).
JavaKit will tell you what command line options it will take if you ask. Type JavaKit
-help (actually any unrecognized option will have JavaKit dump its options). This is
c:> javakit -help
Unknown option: -help
You can see from these commands and from the menus in JavaKit that it is possible to automate the various tasks for which you might use JavaKit. For the most part we will be using JavaKit for loading the TINI API and then configuring it. All the rest of our work on TINI will be done through network programs such as Telnet and FTP. JavaKit can record the commands and actions you issue and save them to a macro file so you can rerun the exact session again. This is useful if you are configuring a number of TINI boards with like settings. To do this you will use the macro feature. To enable that, you must switch JavaKit from “Dumb Terminal” to “JavaKit Terminal” using the selection box on the upper right of the JavaKit window. You can start or stop recording a macro using the macro pull-down menu, and you can save or load macros using the file pull-down menu. JavaKit will leave a JavaKit.tmp file in the directory from which you ran it. This contains the communication settings you used for that session. If you changed them from the defaults, they will be restored from this file the next time you run JavaKit. If you run JavaKit from a number of different directories, then you will have a number of these JavaKit.tmp files hanging around.
If you simply need to connect to your TINI to run various programs and you don’t have a network connection, you can use any terminal program to connect to your TINI over a serial line instead of JavaKit. In the following figures, you can see a Hyperterm terminal window and a Linux Eterm window (running minicom) with an active TINI connection. Notice the settings dialogs. You will need to configure your terminal emulator for 115,200 bits per seconds, 8 data bits, no parity, 1 stop bit, no hardware or software flow control. Also note that if you are using an E10 or E20 socket from Dallas Semiconductor, you will need to remove the solder bridge on jumper J1 on the back of the socket board. This jumper, when removed, prevents the DTR line on the serial port from resetting your TINI board. This is explained in Chapter 9.