Renesas FLASH Development Toolkit 3.07, User Manual

Page: 57 / 146

43
Chapter 4 Wait For Script
4.1 Wait For Script Overview
This mode allows FDT to be automated and controlled by a text file containing a script of commands. Once
in this mode FDT acts as a server which polls for the existence of a file in a predetermined location. Once
this file is found, FDT executes each command in order and can then optionally delete or move the script
file upon completion, so that FDT is ready to look for the next script file. This allows FDT to connect,
program, erase, blank check etc, under the control of an external application, via the use of a simple text
file.
The messages in the output window can optionally be echoed to a log file for later analysis and traceability.
Additionally, a status file can be created, which holds information about the state of the current and
previous script processes. This status file can be used by the external application to determine whether the
script has been processed successfully.
To set up FDT Wait For Script, a configuration file needs to be created to specify the search path for the
script file and other parameters such as the settings for the log and status files, and how to handle errors.
4.2 Wait For Script – New Configuration
This is invoked from the Tools, Wait For Script, New Configuration... menu.
4.2.1 Script File Page
Figure 4-1 Script File Page
This is the only essential page in the wait for script configuration.