Flasher/Glossary

From SEGGER Wiki
Revision as of 12:58, 11 December 2023 by Michael (talk | contribs) (F)
Jump to: navigation, search

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)

B

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 configurations 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 configuration or a tool sending commands via the #Command Line Interface (CLI).
Configuration
The #Configuration Project as well as some other files like the Flasher.ini, Serial.txt, etc. required by the Flasher to carry out an operation like programming the connected target.
Configuration Program
The program (U-Flash or J-Flash) used to generate the #Configuration Project.
Configuration Project
The files generated by the #Configuration Program required for a standalone #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 the 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.

E

F

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.

G

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.

J

K

L

M

N

O

P

PC-controlled Mode
See #Host-based Mode.

Q

R

S

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.

U

V

W

X

Y

Z