The text file changes.txt lists the new items, which include:

1. Faster file system
2. PPP
3. Sharable native libraries
4. Synchronized methods, wait sets and notification
5. Many additions to the API including Date and Calendar
6. Faster and better 1-wire, CAN and DataPort
7. No more .hex files. There is now 1 binary file (tini.tbin) that contains the firmware and the API.
8. New JavaKit to support loading binary files. You can't use the older JavaKit with 3.0 TINI.
   

Download the TINI Beta 3 files from Dallas Semiconductor. Save the file (named tinibeta03_tar.gz) to a temprary folder. I have an "incoming" folder where I temporarily store such things.

Now expand the file using a utility such as WinZip. It will ask if you want to extract a .tar file within the archive. Yes, we do.

The .tar file includes a number of files and folders:

Click on extract and be sure you have "Use folder names" checked. Click the Extract button. I installed to my drive E, and winzip then created the folder e:\tinibeta3.0 and all the subfolders.

You should have the TINI 3.0 files in a structure that looks like this from Explorer:

Note the readme.txt file. Open it and read it!

Here are the first few lines from the readme file (in red). My remarks are in black.

README.txt (DC, 05.22.00)

========================================================================
IMPORTANT!!! MUST READ!!! NOT READING THIS WILL RESULT IN A DEAD TINI BOARD
========================================================================
This release includes a new TINI bootstrap loader that is required to run the new firmware. Updating the loader is a very precarious operation. A mistake could leave your TINI without a bootstrap loader (rendering your TINI board useless until the loader is restored.) Depending on where the error occurs, recovery will require connecting extra hardware to your TINI board, or even sending the board back to Dallas to have it done there.

Do NOT interrupt this load process. (This means no power cycling or resets unless the instructions explicitly specify them). Doing so will certainly leave your board without a loader. If this unfortunate event happens, here's how to restore a boot loader to a wounded TINI.

Section II will step you through loading the new bootstrap loader and firmware updates.

I won't duplicate everything in the readme file (you have already read the whole file, anyway). What follows is a step by step walk-through as I loaded TINI beta 3 onto a TINI SIMM68 board in a Systronix STEP+ sockets board.

Print out the readme.txt file which came in the TINI .tar archive, and follow along with it as you follow along with me. Yep - I did exactly that (a rare case of practicing what I preach.) I'll hit the high points and areas in which my approach differs from the readme file.

I have e:\tinibeta2.2 already in my system and I don't want to accidentally refer to any beta 2.2 files. I don't want to delete all the beta 2.2 files, not yet, anyway. So to prevent problems and make it obvious when I accidentally refer to the old beta 2.2 folder, I changed its name to e:\tinibeta2.2.obsolete.

I wrote a batch file to execute JavaKit - it's just my preference. The batch file contains one line (it wraps to two lines in this tutorial text box). I call it JavaKit.bat and it's located in e:\tinibeta3.0. Also here's a link to the file JavaKit.bat

E:\JBuilder35\jdk1.2.2\bin\java -classpath E:\JBuilder35\jdk1.2.2\lib\comm.jar;E:\tinibeta3.0\bin\tini.jar; JavaKit

Note: I'm using a Systronix STEP board with the DTR reset jumper installed. Our TILT boards have a similar jumper. This is necessary to enable JavaKit to invoke TINI's loader. If you are using the Dallas SocketPlus board, Rev A, you must have a solder blob on jumper J1, labeled DTR Reset.

OK, I click on the batch file and here's JavaKit. Select COM1 (that's my COM port to TINI), click the Open Port button, then Reset, and I get the loader prompt from TINI:

Note that this is the beta 2.2 loader, since the date is 08-24-99. So we do need to install the new Beta3 loader on this factory-fresh TINI board. Soon, TINIs will be shipped from Dallas with Beta3 or later loader already installed, which will save one part of this procedure.

If you don't see COM1, COM2, etc in the Port Name pulldown list, then the Java commapi is not properly installed on your PC.

Now from the JavaKit file menu, select Load File and browse to (in my case)

e:\tinibeta3.0\ bin\tini.tbin

Note that JavaKit now has a progress indicator just below the main menus. Also, note that you no longer need to manually clear out flash banks like you did in Beta 2.2 and prior. JavaKit and the new loader now do this automatically. Very nice. Tini.tbin is a binary file, hence about 2.5X smaller than an equivalent HEX file, so that much faster to load.

Clear TINI's heap with a

B18

F0

Now, from slush, over TINI's serial port, you must configure TINI's IP address and other options depending on your circumstances, using the slush 'ipconfig' command. Once TINI has a valid and known (to you, at least) IP address, you can send TINI other files via FTP.

You can go to the tutorial home for a tutorial on a simple Java program for TINI, setting up JBuilder, and so forth.

If you are using JBuilder, you need to update it's configuration and options to work with TINI 3.0.

First of all, update the jdk.config file to point to the 3.0 version of tini.jar. Note that in 3.0 the tini.jar file is in a bin folder, not the root tinibeta3.0 folder. Close JBuilder and make the change.