Difference between revisions of "Flasher/Glossary"
(→F) |
|||
| Line 4: | Line 4: | ||
This glossary is a living article and will be updated regularly with additional terms and definitions. |
This glossary is a living article and will be updated regularly with additional terms and definitions. |
||
| − | = A = |
+ | = A = |
| − | ;< |
+ | ;<span id="Access Protocol">Access Protocol</span> |
:The interface and communication protocol used by the Flasher to communicate with the target and perform the flash algorithm. |
:The interface and communication protocol used by the Flasher to communicate with the target and perform the flash algorithm. |
||
| − | ;< |
+ | ;<span id="ASCII Command Interface">ASCII Command Interface</span> |
: See [[#Command Line Interface (CLI)]] |
: See [[#Command Line Interface (CLI)]] |
||
= B = |
= B = |
||
= C = |
= C = |
||
| − | ;< |
+ | ;<span id="Command Instance">Command Instance</span> |
: See [[#Command Program]]. |
: See [[#Command Program]]. |
||
| − | ;< |
+ | ;<span id="Command Line Interface (CLI)">Command Line Interface (CLI)</span> |
| − | :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 |
+ | :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. |
| − | ;< |
+ | ;<span id="Command Program">Command Program</span> |
| − | :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 |
+ | :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)]]. |
| − | ;< |
+ | ;<span id="Configuration Program">Configuration Program</span> |
| + | :The program (U-Flash or J-Flash) used to generate the [[#Project 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. |
||
| − | ;< |
+ | ;<span id="Control Instance">Control Instance</span> |
| − | :The program (U-Flash or J-Flash) used to generate the [[#Configuration Project]]. |
||
| − | |||
| − | ;<b id="Configuration Project">Configuration Project</b> |
||
| − | :The files generated by the [[#Configuration Program]] required for a standalone [[#Configuration]]. |
||
| − | |||
| − | ;<b id="Control Instance">Control Instance</b> |
||
:See [[#Control Program]]. |
:See [[#Control Program]]. |
||
| − | ;< |
+ | ;<span id="Control Program">Control Program</span> |
| − | :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 |
+ | :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. |
| − | ;< |
+ | ;<span id="Control Program Package">Control Program Package</span> |
: |
: |
||
= D = |
= D = |
||
| − | ;< |
+ | ;<span id="Device Definition File (DDF)">Device Definition File (DDF)</span> |
:Device definition files are XML files used with U-Flash to define support, device properties, and configuration including dialog elements for devices. |
:Device definition files are XML files used with U-Flash to define support, device properties, and configuration including dialog elements for devices. |
||
= E = |
= E = |
||
= F = |
= F = |
||
| − | ;< |
+ | ;<span id="Functional Circuit Test (FCT)">Functional Circuit Test (FCT)</span> |
: The last test for fully assembled PCBs, assessing overall functionality by subjecting the device to input signals and evaluating corresponding output responses. |
: The last test for fully assembled PCBs, assessing overall functionality by subjecting the device to input signals and evaluating corresponding output responses. |
||
| + | |||
| + | ;<span id="Flasher Configuration">Flasher Configuration</span> |
||
| + | :The Flasher Configuration consists of all [[#Flasher Project]]'s and the [[#Flasher Settings]] located on the Flasher. |
||
| + | |||
| + | ;<span id="Flasher Project">Flasher Project</span> |
||
| + | :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. |
||
| + | |||
| + | ;<span id="Flasher Settings">Flasher Settings</span> |
||
| + | :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. |
||
= G = |
= G = |
||
= H = |
= H = |
||
| − | ;< |
+ | ;<span id="Handshake Control">Handshake Control</span> |
: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). |
: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). |
||
| − | ;< |
+ | ;<span id="Host-based Mode">Host-based Mode</span> |
:The counterpart of the [[#Standalone Mode]] which requires a [[#Control Program]] to carry out an operation like programming the connected target. |
:The counterpart of the [[#Standalone Mode]] which requires a [[#Control Program]] to carry out an operation like programming the connected target. |
||
= I = |
= I = |
||
| − | ;< |
+ | ;<span id="In-Circuit Test (ICT)">In-Circuit Test (ICT)</span> |
: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. |
: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. |
||
| Line 68: | Line 71: | ||
= O = |
= O = |
||
= P = |
= P = |
||
| − | ;< |
+ | ;<span id="PC-controlled Mode">PC-controlled Mode</span> |
:See [[#Host-based Mode]]. |
:See [[#Host-based Mode]]. |
||
| + | |||
| + | ;<span id="Project Configuration">Project Configuration</span> |
||
| + | :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 [[#Configuration Program]], because the Project Configuration in the [[#Flasher Project]] might have been modified by the user. |
||
| + | |||
| + | ;<span id="Project Operation Data">Project Operation Data</span> |
||
| + | :The Serial.txt, Patches.txt and Cntdown.txt located in a [[#Flasher Project]]. |
||
= Q = |
= Q = |
||
= R = |
= R = |
||
= S = |
= S = |
||
| − | ;< |
+ | ;<span id="Standalone Mode">Standalone Mode</span> |
: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. |
: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 = |
= T = |
||
| − | ;< |
+ | ;<span id="Target Encrypted Link Package (TELP)">Target Encrypted Link Package (TELP)</span> |
: 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. |
: 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. |
||
| − | ;< |
+ | ;<span id="Target Image">Target Image</span> |
: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]]. |
: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]]. |
||
Revision as of 12:27, 13 December 2023
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 #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.
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.
- 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.
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.
- 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 #Configuration Program, 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.
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.
