Share via

CeLogFlush.exe (Compact 2013)

  • Article

3/28/2014

This tool automatically empties the contents of the RAM-based log buffer for the CeLog event tracking subsystem.

Syntax

celogflush.exe [Parameters]

Parameters

  • -addr <hex address>
    BufferAddress (for example, 0x8022000)
  • -autoerase <0 or 1>
    AutoEraseMode (either 0 or 1)
  • -buf size
    BufferSize (for example, 0x100000)
  • -flags hexflags
    FileFlags (for example, 0x00000001)
  • -filesize hex size
    FileSize (for example, 0x00020000)
  • -n filename
    FileName
  • -pri priority
    ThreadPriority (for example, 248)
  • -syncbuf <hex size>
    SyncBufferSize (for example, 0x1000)
  • -time timeout
    FlushTimeout (for example, 10000)
  • -trans transport
    Transport (for example, LocalFile)
  • -ui <0 or 1>
    UseUI (either 0 or 1)
  • -z hexzones
    ZoneCE (for example 0x000043E3)

Remarks

The parameters for this tool override the CeLog registry values and program defaults. For more information, see CeLog Registry Settings.

To include CeLogFlush.exe in a run-time image

  1. In Platform Builder, on the Project menu, click Properties.

  2. In the Property Pages window, click Configuration Properties, and then click Build Options.

  3. In the Build Options window, select Flush tracked events to Release Directory (IMGAUTOFLUSH=1).

    CeLogFlush.exe is added to ROM, and the OS launches it during the next boot. Tracked events are flushed to Celog.clg in the Release directory. Celog.dll is also added to the run-time image.

  4. (Optional) To load CeLog.dll at an earlier point of the boot process, select Enable Event Tracking During Boot (IMGCELOGENABLE=1).

    CeLog.dll is added to the MODULES section of the run-time image, which causes the kernel to load it early in the boot process.

  5. Click OK.

  6. Build the run-time image.

This tool writes the data to a file. Because it runs automatically, you can use it to gather data collected at any time in device execution, including during boot-up.

Important

Do not include CeLog on a shipping device because the logging that it performs can reduce system performance. Also, omitting CeLog reduces the attack surface through which a malicious user could try to compromise the system.

See Also

Other Resources

CeLog Event Tracking