Flasher - Log file

From SEGGER Knowledge Base
Jump to navigation Jump to search

The Flasher.log file logs every programming attempt and is used for quality tracking purposes (e.g., serial number, result, duration).
It is stored in the root folder of the Flasher file system. For information on how to access it, refer to the Flasher file management page.

General structure

Log entries in Flasher.log differ depending on whether the project consists of a single or multiple jobs, and whether the operation completed successfully or resulted in an error.

Key fields

Parts in square brackets are optional and only appear if the corresponding option is enabled. The brackets themselves are not part of the log.

Field Description
<Timestamp> Timestamp that shows either real-time date or time since boot at time of execution. See Timestamp format chapter for additional information.
<Counter> Execution counter that starts at 1 after boot and is incremented for each programming operation.
<Project> Project name.
[ - SN: <SN>] Serial number (if serial number programming is enabled).
[ - DAT file CRC-32: <CRC-32>, CRC-32-C: <CRC-32-C>] Checksums of the DAT file (if show DAT CRC after programming is enabled).

Timestamp format

Structure

The Flasher <Timestamp> field has the following structure:

 YYYY-MM-DD HH:mm:ss:fff
 |    |  |  |  |  |  |
 |    |  |  |  |  |  +- 3 digits [ms]
 |    |  |  |  |  +---- 2 digits [s]
 |    |  |  |  +------- 2 digits [min]
 |    |  |  +---------- 2 digits [hour]
 |    |  +------------- 2 digits [day]
 |    +---------------- 2 digits [month]
 +--------------------- 4 digits [year]

Timestamp reference

If available, Flasher uses it's real-time reference to generate a corresponding timestamp for log entries.

If Flasher has no real-time reference, the timestamp format is based on the time elapsed since boot.
In that case, a period of 31 days is treated as one month.
Example:
0000-01-02 00:10:09:008
This does not represent January 2nd. It should be interpreted as follows:

  • 0000 → 0 years +
  • 01 → 1 month (== 1 * 31 days) +
  • 02 → 2 days +
  • 00:10:09:008 → 0 hours, 10 minutes, 9 seconds and 8 milliseconds

... elapsed since boot.

Single-job project

Successful execution

<Timestamp> - <Counter> - <Project>[ - SN: <SN>][ - DAT file CRC-32: <CRC-32>, CRC-32-C: <CRC-32-C>]
  OK (<Time> ms)

Failed execution

<Timestamp> - <Counter> - <Project>[ - SN: <SN>][ - DAT file CRC-32: <CRC-32>, CRC-32-C: <CRC-32-C>]
  Error[ <Err msg>]

Multi-job project

Successful execution

<Timestamp> - <Counter> - <Project>
  <Job>[ - SN: <SN>][ - DAT file CRC-32: <CRC-32>, CRC-32-C: <CRC-32-C>]
  [...]
  <Job>[ - SN: <SN>][ - DAT file CRC-32: <CRC-32>, CRC-32-C: <CRC-32-C>]
  OK (<Time> ms)

Failed execution

<Timestamp> - <Counter> - <Project>
  <Job>[ - SN: <SN>][ - DAT file CRC-32: <CRC-32>, CRC-32-C: <CRC-32-C>]
  [...]
  <Job>[ - SN: <SN>][ - DAT file CRC-32: <CRC-32>, CRC-32-C: <CRC-32-C>]
  Error[ <Err msg>]


Note:
For multi-job projects, there is an initial line at project start and a final summary line with the overall result. Detailed error messages appear directly below the specific job that encountered the issue.

Error details

If available, the log file contains detailed error messages. For example:

ERROR: Programming failed @ address 0x00000000 (1)
ERROR: Cannot connect to CPU. Target interface speed too high?
ERROR: Failed to apply patch data. Invalid address range.

Example log

0000-00-00 02:00:09:325 - 1 - Project_1
  OK (10 ms)
0000-00-00 03:14:15:314 - 2 - Project_2 - SN: 11260001 - DAT file CRC-32: 0xB1668F81
  OK (6121 ms)
0000-00-00 04:57:43:774 - 3 - Project_2 - SN: 11260001 - DAT file CRC-32: 0xB1668F81
  Error
0000-00-00 00:23:00:735 - 1 - Project_3
  Job_0
  Job_1
  Job_2
  OK (18381 ms)
0000-00-00 00:36:21:289 - 2 - Project_3
  Job_0 - DAT file CRC-32: 0xC7CE187F
  Job_1 - DAT file CRC-32: 0xC7CE187F
  Job_2 - DAT file CRC-32: 0xC7CE187F
  OK (18389 ms)
0000-00-00 00:50:16:598 - 3 - Project_4
  Job_0 - SN: 11261002 - DAT file CRC-32: 0xC7CE187F
  Job_1 - SN: 11262002 - DAT file CRC-32: 0x1D10E795
  ERROR: Failed to apply patch data. Invalid address range.
  Error

Limitations

The log file has a maximum size of 1 MB. When the log reaches this size, it is automatically truncated to zero bytes and logging continues from the beginning, meaning older log entries are lost once the limit is exceeded.

Legacy

Key fields

The general structure of log entries for legacy (unmanaged) projects is the same as for managed projects (see Key fields chapter for reference). The only difference is in the project name:

  • <Project>: For a legacy project, the name of the corresponding configuration file is shown as the project name.

Example log

0000-00-00 02:38:26:199 - 1 - FLASHER.CFG
  OK (6085 ms)
0000-00-00 02:59:09:063 - 2 - Project_1.CFG - SN: 0001 - DAT file CRC-32: 0x2CE35877
  OK (6091 ms)
0000-00-00 03:08:55:660 - 3 - Project_2.UNI - DAT file CRC-32: 0x2CE35877
  Error