Flasher/Glossary

Welcome to the glossary section, where key terms related to SEGGER's Flasher portfolio are defined for easy reference.

This glossary is a living article and will be updated regularly with additional terms and definitions.

A

Access Protocol

The interface and communication protocol used by the Flasher to communicate with the target and perform the flash algorithm.

ASCII Command Interface

See #Command Line Interface (CLI)

C

Command Instance

See #Command Program.

Command Line Interface (CLI)

A text-based interface to interact with the Flasher remotely. Beside commands to carry out common operations like programming the connected target, further commands, like selecting one of the #Flasher Project's stored on the Flasher, are available.

Command Program

A tool that can be used for the standalone mode to trigger operations on the Flasher. This can be, for instance, a tool that generates a positive pulse (5V–30V) on pin 1 of the SUBD9 male connector that starts the #AUTO command for the currently selected #Flasher Project or a tool sending commands via the #Command Line Interface (CLI).

Configuration Program

The program (U-Flash or J-Flash) used to generate the #Project Configuration.

Control Instance

See #Control Program.

Control Program

An application used to provides information like the data from the target image and the steps to execute the flash algorithm to a programmer. This is comparable to J-Flash if it is being used in host-based aka. PC-controlled mode. When the Flasher is used in standalone mode, a control program is not required.

Control Program Package

D

Device Definition File (DDF)

Device definition files are XML files used with U-Flash to define support, device properties, and configuration including dialog elements for devices.

F

File Access Mode

The mode in which the Flasher acts as a mass storage USB device. This mode is entered by connecting the Flasher while the PROG button is pressed. For more information, please refer to UM08022 Flasher#File access mode.

Functional Circuit Test (FCT)

The last test for fully assembled PCBs, assessing overall functionality by subjecting the device to input signals and evaluating corresponding output responses.

Flasher Configuration

The Flasher Configuration consists of all #Flasher Project's and the #Flasher Settings located on the Flasher.

Flasher Project

A project located on the Flasher consisting of the #Project Configuration and the #Project Operation Data. This project is able to carry out operations like programming the connected target. Please note that changes made to the Flasher Project located on the Flasher will be overwritten if the master #Flasher Configuration is sent to the Flasher again.

Flasher Settings

Files that belong to the Flasher Settings are the Flasher.ini, which specifies the currently active #Flasher Project, the Secure.ini, the Flasher.log and the Firmware.bin used to update the Flasher firmware.

H

Handshake Control

A remote control interface to trigger the #AUTO Flasher operation and to get OK and BUSY status using 3 lines of the serial interface (SUBD9 male connector).

Host-based Mode

The counterpart of the #Standalone Mode which requires a #Control Program to carry out an operation like programming the connected target.

I

In-Circuit Test (ICT)

An electronic testing method that verifies individual components and connections on a printed circuit board during manufacturing, detecting defects like short circuits and incorrect values.

M

Mass Storage Device (MSD)

A device that can be used as a storage medium. The Flasher supports a mode in which it acts as a USB MSD (see #File Access Mode) to manage the standalone #Flasher Projects stored in its internal file system.

P

PC-controlled Mode

See #Host-based Mode.

Project Configuration

The files generated by the #Configuration Program that are sent to the Flasher plus the SNList.txt. Once the Project Configuration is on the Flasher, it is part of the #Flasher Project and can't be used to restore the Project Configuration, because the Project Configuration in the #Flasher Project might have been modified by the user.

Project Operation Data

The Serial.txt, Patches.txt and Cntdown.txt located in a #Flasher Project.

Public Area

A volume in the Flasher's file system where a #Flasher Configuration can be stored and accessed by everyone. See also #Secure Area.

S

Secure Area

A volume in the Flasher's file system where a Flasher configuration can be stored that can't be read out anymore. For more information, please refer to UM08022_Flasher#Authorized flashing.

Standalone Mode

A mode in which all required files are located on the Flasher and no additional #Control Program is required to carry out an operation like programming the connected target.

T

Target Encrypted Link Package (TELP)

A package, used with the Flasher Secure and Flasher Secure Server, providing an encrypted transfer of the firmware from the Flasher Secure to the target.

Target Image

The file containing the firmware to be programmed into the target. A target image can be stored using a variety of different file types. The Flasher uses a special file type for the target image with .DAT extension, which is generated by the #Configuration Program.