The main uses of this tool are:


     - Starting debugger software with/without startup options

     - Selecting the device debugger software is connected to when more than one device can be connected

     - Sending a software macro to the debugger once already running



You can specify the following options as command line arguments at startup.


     - You can code a macro after "macro=". Use semicolons in place of newlines.
      The macro coded here is saved in "%NW4C_ROOT%\temp\DebuggerMacro.MCR" and loaded at startup.
       If debugger software connected to the target device already exists, "%NW4C_ROOT%\temp\DebuggerMacro.MCR" is loaded into that debugger software.

     - You can specify the macro file name to be loaded after "mcrfile=".
       If you specify a macro file here, the macro coded using "macro=" is ignored.
       If debugger software connected to the target device already exists, it is loaded into that debugger software.

     - You can specify start up options for the debugger software after "option=".
       This is ignored if debugger software connected to the target device already exists.
       You can also specify a macro file without this specification by using "mcffile=", described above.

     - You can use "noconfirm" to set operations so that no check is made whether to execute a macro for debugger software already running.
       If this setting is not made, a check will be made if it's really okay to execute a macro, when executing one for debugger software already running, but if this option is specified, the macro will be executed without checking.

     - You can specify the device to connect to using "device=".
       You can specify the device using its device ID (E.g. G0612445) or simply using the numbers 0, 1, 2...
       You can check which device the number 0, 1, 2... correspond to by executing without specifying this option.


Usage Example

       "%NW4C_ROOT%\tools\DebuggerLauncher\DebuggerLauncher.exe" macro="L %NW4C_ROOT%\\sources\\tools\\Viewer\\Viewer-TS.cci; G;" device=0 noconfirm

       Result -> The debugger software connected to the 0th device will start, and Viewer.cci will be loaded and executed.
               If there is already debugger software connected to the 0th device, Viewer.cci will be loaded and executed for that debugger software.
               Since the options device and noconfirm are specified, neither a connection check nor confirmation on whether to execute the macro will be performed.