
TUTOR HOME |
|
|
|
HELP | BUY | CONTACT | ABOUT |
| Typically, I use JBuilder with the TiniTools plug-in which automatically converts and ftp uploads a .tini program file. However, there are times (such as using the 1-Wire API with TINI 1.01) in which you need to run a build batch file, or you need to deploy multiple files to TINI after a build (a .tini and a matching .startup file for example). I use a combination of DOS path batch files, ftp command files, and command line parameters. Here's an example taken from some 8x1-Wire I/O board sample code. These files are contained in the source code zip files here. |
|
@echo off echo Will ftp to %1 using %2.cmd rem ftp -s:%2.cmd %1 :usage :end |
| This batch file is invoked with the IP address at which to deploy, and the name of the program to deploy. Note that you must use the same name for your .tini file and the .cmd file, as well as the .startup file. In this case, my TINI file is "leds.class", the command file is "leds.cmd" and the .startup file for leds is ".startup.leds" |
|
If you are interested in the Linux script for automating FTP echo "user root tini" > f The command line looks like this goftp myapp.tini 192.168.1.2 This works under Redhat 6.0. Other versions of Linux have
not been - thanks to Tom Chenot - |
| root tini bin put classes/leds.tini put .startup.leds etc/.startup close quit |
| This is the "leds.cmd" file |
| ######## #Autogen'd slush startup file setenv FTPServer enable setenv TelnetServer enable setenv SerialServer enable ## #Add user calls to setenv here: ## initializeNetwork ######## #Add other user additions here: java /leds.tini > leds.txt |
| This is the ".startup.leds" file. Note the spaces surrounding the > redirection character. More tips on redirection. |