This topic outlines several Windows CE logging tasks, diagnostics logging, and the Watson dump features of Microsoft RoundTable.

RoundTable writes to the CE Log for hardware functional tests and critical system issues. This section identifies several tasks that are related to the CE log, that you can perform.

• Open a command prompt, and execute the following command line.
  
  

rtmanage.exe -m:diag -l:flush

The CE log for the device is written to a directory on the share. The directory name is the product ID of the device.

The CE log file name has the form YYYYMMDDHHMMSS-CELOG n.clg, where nis 0 or 1. An example CE log file name is 20070501170926-CELOG0.clg.

Note:
The file name might change based on the implementation of Office Communications Server 2007 Update Service.

You must use the Readlog.exe that is included with Windows CE Platform Builder to interpret the .clg file. Alternatively, you can send the file to Microsoft Customer Service and Support for investigation. For information about Readlog Command-Line Options, see http://go.microsoft.com/fwlink/?linkid=147112 .

To extract the contents of the .clg file to a text file, use the -v (verbose) print option when you run Readlog.exe. For example, Readlog.exe -v CE_log_file output_file.txt.

The CE log contains the results of the hardware functional tests and critical system errors.

The following is an example of the contents of a CE log.

Copy Code

0:00:01.523.868 : Raw data 31 (wchar), ,,,FIRMWARE REV,,NA,1.0.3528.0 0:00:01.524.306 : Raw data 31 (wchar), ,,,FIRMWARE CURRENT REV,,NA,,, 0:00:01.524.769 : Raw data 41 (wchar), ,,,FIRMWARE FACTORY REV,,NA,1.0.3528.0,, 0:00:01.525.254 : Raw data 27 (wchar), ,,,OS REV,,NA,1.0.3528.0,, 0:00:01.525.674 : Raw data 26 (wchar), ,,,POST Version,,NA,1.0,, 0:00:01.526.107 : Raw data 30 (wchar), ,,,CPU STATUS,,PASS,0x10000,, 0:00:01.526.557 : Raw data 36 (wchar), ,,,ETH0 TEST,,NOT DONE,0xFFFFFFFF,, 0:00:01.527.109 : Raw data 36 (wchar), ,,,ETH1 TEST,,NOT DONE,0xFFFFFFFF,, 0:00:01.527.626 : Raw data 36 (wchar), ,,,VDSP ENUM STATUS,,PASS,0x30000,, 0:00:01.528.088 : Raw data 36 (wchar), ,,,USBF ENUM STATUS,,PASS,0x30001,, 0:00:01.528.539 : Raw data 36 (wchar), ,,,USBH ENUM STATUS,,PASS,0x30002,, 0:00:01.528.965 : Raw data 30 (wchar), ,,,RTC VERIFY,,PASS,0x40001,, 0:00:01.529.756 : Raw data 35 (wchar), ,,,TOUCHCTL VERIFY,,PASS,0x40000,, 0:00:01.530.221 : Raw data 38 (wchar), ,,,NORFLASH VERIFY,,FAIL,0xFFFFFFFF,, 0:00:01.530.671 : Raw data 36 (wchar), ,,,NANDFLASH VERIFY,,PASS,0x60000,, 0:00:01.531.213 : Raw data 30 (wchar), ,,,LCD VERIFY,,PASS,0x70000,, 0:00:01.531.646 : Raw data 30 (wchar), ,,,SDRAM TEST,,PASS,0x80000,, 0:00:01.532.087 : Raw data 32 (wchar), ,,,System Cable,,PASS,0x90000,, 0:00:01.532.540 : Raw data 39 (wchar), ,,,UFN1: Initialize,,PASS,0x00000000,, 0:00:01.532.989 : Raw data 39 (wchar), ,,,HCD1: Initialize,,PASS,0x00000000,, 0:00:01.533.518 : Raw data 39 (wchar), ,,,HCD3: Initialize,,PASS,0x00000000,, 0:00:01.534.027 : Raw data 53 (wchar), ,,,Display Hardware,,PASS,Initialized Successfully,, 0:00:07.754.119 : Raw data 31 (wchar), ,,,PSTN,,FAIL,Initialization,, 0:00:08.737.588 : Raw data 31 (wchar), ,,,PSTN,,FAIL,Initialization,, 0:00:08.738.118 : Raw data 33 (wchar), ,,,ADSP Microphone Test,,PASS,,, 0:00:46.745.599 : Raw data 29 (wchar), ,,,Camera ID,,PASS,723308F,, 0:00:46.746.059 : Raw data 22 (wchar), ,,,Restarts,,PASS,0,, 0:00:46.746.553 : Raw data 40 (wchar), ,,,Video Port,,PASS,0 Frames Dropped.,, 0:00:46.747.036 : Raw data 35 (wchar), ,,,Camera Video,,PASS,Y Y Y Y Y ,, 0:00:46.747.496 : Raw data 29 (wchar), ,,,I2C Status,,PASS,OK 0 C,, 0:00:46.747.936 : Raw data 26 (wchar), ,,,Calibration,,PASS,OK,, 0:00:46.749.127 : Raw data 28 (wchar), ,,,White Balance,,FAIL,NO,, 0:00:46.749.719 : Raw data 19 (wchar), ,,,POST,,PASS,OK,, 0:00:46.750.187 : Raw data 27 (wchar), ,,,Stack Health,,PASS,OK,,

A hardware failure can be identified by a FAIL in the following entries:

Copy Code

0:00:01.526.107 : Raw data 30 (wchar), ,,,CPU STATUS,,FAIL,0x10000,, 0:00:01.527.626 : Raw data 36 (wchar), ,,,VDSP ENUM STATUS,,FAIL,0x30000,, 0:00:01.528.088 : Raw data 36 (wchar), ,,,USBF ENUM STATUS,,FAIL,0x30001,, 0:00:01.528.539 : Raw data 36 (wchar), ,,,USBH ENUM STATUS,,FAIL,0x30002,, 0:00:01.528.965 : Raw data 30 (wchar), ,,,RTC VERIFY,,FAIL,0x40001,, 0:00:01.529.756 : Raw data 35 (wchar), ,,,TOUCHCTL VERIFY,,FAIL,0x40000,, 0:00:01.530.671 : Raw data 36 (wchar), ,,,NANDFLASH VERIFY,,FAIL,0x60000,, 0:00:01.531.213 : Raw data 30 (wchar), ,,,LCD VERIFY,,FAIL,0x70000,, 0:00:01.531.646 : Raw data 30 (wchar), ,,,SDRAM TEST,,FAIL,0x80000,, 0:00:01.532.087 : Raw data 32 (wchar), ,,,System Cable,,FAIL,0x90000,, 0:00:01.532.540 : Raw data 39 (wchar), ,,,UFN1: Initialize,,FAIL,0x00000000,, 0:00:01.532.989 : Raw data 39 (wchar), ,,,HCD1: Initialize,,FAIL,0x00000000,, 0:00:01.533.518 : Raw data 39 (wchar), ,,,HCD3: Initialize,,FAIL,0x00000000,, 0:00:01.534.027 : Raw data 53 (wchar), ,,,Display Hardware,,FAIL,Initialization failed,,

Note:
The CE logs are not localized because they are required for debugging by Microsoft developers.

The CE log contains a harmless incorrect entry, similar to the following:

	Copy Code
0:00:01.530.221 : Raw data 38 (wchar), ,,,NORFLASH VERIFY,,FAIL,0xFFFFFFFF,,

The NORFLASH VERIFY test is not run and does not have to be run. If there is a NORFLASH failure, the RoundTable device will not start.

If the Log to the serverfield is checked in the Loggingsection of the RoundTable device configuration, the device writes self-diagnostic data to the Microsoft Office Communications Server 2007 Update Service. For the file name and location of the log, see the documentation for Office Communications Server 2007 Update Service.

The following table lists the column names and their data types by column number. Data in the diagnostics log is comma-delimited.

Diagnostic log schema names by column number

The RoundTable diagnostics logs fall into three LoggingType categories: POST, Health, and Image Update. Power-on self-test (POST) diagnostics consist of information generated when the device is powered on. Health diagnostics relate to the health of the device, with regard to either system performance or resource usage. Image update diagnostics relate to updating the device firmware.

RoundTable powers on and performs a POST. The following table shows the columns that are used, together with the values that are logged. The three values of Component represent the system, audio digital signal processor, and video digital signal processor.

Columns and values used in POST logging

When Component = System, only the Property, Value2, and Value3 columns are used.

The Property column contains the name of the test. The Value2 column contain the status (PASS | FAIL | NOT DONE | NA). The Value3 column contains the detailed status code. These entries indicate the general health of the system. Note that some entries are reserved for system use.

The following table shows the possible values in the Property, Value2, and Value3 columns when the Component value is System.

Properties and values for POST logging, Component == System

When component = VDSP, only the Property, Value2, and Value3 columns are used.

The Property column contains the name of the test. The Value2 column contains the status (PASS | FAIL | NOT DONE | NA). The Value3 column contains the detailed status code. These entries indicate the general health of the video subsystem.

The following table shows the possible values in the Property, Value2, and Value3 columns when the Component value is VDSP.

Properties and values for POST logging, Component == VDSP

When Component = ADSP, only the Property, Value2, and Value3 columns are used.

The Property] column contains the name of the test. The Value2 column contain the status (PASS | FAIL | NOT DONE | NA). The Value3 column contains the detailed status code. These entries indicate the general health of the initialization phase of the audio sub-system.

The following table shows the possible values in the Property, Value2, and Value3 columns when the Component value is ADSP.

Property and values for POST logging, Component == ADSP

There are two types of health logging: system performance and usage. This section discusses system performance logging. Usage logging is discussed in the next section.

System performance refers to memory usage, system uptime, and health of the audio digital signal processor.

The following table shows the columns used and values logged in health logging.

Columns and values that are used in system performance logging

For performance logging, only the Component, Subcomponent, Property, and Value1 columns are used.

The following table shows the possible values of these columns for System (either memory usage or uptime) and for audio digital signal processor (ADSP) health.

Possible values for Component, Subcomponent, Property, and Value1 Columns

This section discusses usage logging.

The following table shows the columns and values that are used when LoggingType == Health and Property == Usage.

Columns used in usage logging

The following table shows the columns and values that are used in usage logging. This type of usage logging uses the Component, Property, Value1, Value2, Value3, Value4, and Value5 columns. The Value3 value is the session type, which can be one of PcAudio, PcVideo, or PstnCall. When VoIP is used with Microsoft RoundTable, a PcAudio usage entry is logged with the start time and end time. When video streams are used in Microsoft RoundTable, a PcVideo usage entry is logged with the start time and end time. When Microsoft RoundTable is used as an analog phone, a PstnCall usage entry is logged with the start time, end time, originating phone number (configured in the RoundTable device configuration), and the first digit of the dialed phone number.

Values used in usage logging when Component == System

Note:
To create a report about usage, import the diagnostics log on to a database and create a view of all records where Component = System and Property = Usage.

The following table shows the columns used and values logged when LoggingType == Image Update.

Columns and values that are used in Image UpdateLogging