Difference between revisions of "FlasherControl"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "==== Purpose ==== FlasherControl.exe provides access to the _command line interface_ (CLI) of the Flasher via USB. It is primarily intended for use with Flasher Compact in sol...")
 
(Purpose)
Line 1: Line 1:
 
==== Purpose ====
 
==== Purpose ====
FlasherControl.exe provides access to the _command line interface_ (CLI) of the Flasher via USB. It is primarily intended for use with Flasher Compact in solitaire mode (without FLasher Hub) or generally for troubleshooting when the CLI of Flasher products is not available via Ethernet or serial port.
+
FlasherControl.exe provides access to the ''command line interface'' (CLI) of the Flasher via USB. It is primarily intended for use with Flasher Compact in solitaire mode (without FLasher Hub) or generally for troubleshooting when the CLI of Flasher products is not available via Ethernet or serial port.
 
Since the Flasher Compact has neither an Ethernet nor a serial interface in solitary operation - these are provided centrally by the Flasher Hub for all connected devices - control by an automation or test computer is not always easy.
 
Since the Flasher Compact has neither an Ethernet nor a serial interface in solitary operation - these are provided centrally by the Flasher Hub for all connected devices - control by an automation or test computer is not always easy.
 
One obvious possibility is to use the Flasher Compact in host-controlled mode in conjunction with J-FLash. In this case, the connected flasher is controlled directly by J-Flash.
 
One obvious possibility is to use the Flasher Compact in host-controlled mode in conjunction with J-FLash. In this case, the connected flasher is controlled directly by J-Flash.

Revision as of 08:57, 14 April 2023

Purpose

FlasherControl.exe provides access to the command line interface (CLI) of the Flasher via USB. It is primarily intended for use with Flasher Compact in solitaire mode (without FLasher Hub) or generally for troubleshooting when the CLI of Flasher products is not available via Ethernet or serial port. Since the Flasher Compact has neither an Ethernet nor a serial interface in solitary operation - these are provided centrally by the Flasher Hub for all connected devices - control by an automation or test computer is not always easy. One obvious possibility is to use the Flasher Compact in host-controlled mode in conjunction with J-FLash. In this case, the connected flasher is controlled directly by J-Flash. For MCUs that are only supported by U-Flash, this option is not available, since direct control of a Flasher via U-FLash is not (yet) supported. For each connected flasher a separate instance of the controlling program must be started in any case, in case of "simultaneous" programming of several targets, in parallel. FlasherControl is a simple way of integrating Flasher Compact into an automation system via scripts in stand-alone operation.