Versions Compared

Old Version 3

changes.mady.by.user John Medalen

Saved on

compared with

New Version Current

changes.mady.by.user John Medalen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The XML-formatted SDAT files have an extension of ".xsdat". ". To view the file as XML you need to open the file with your browser or an XML viewer/editor.   For convenience you should associate the .xsdat extension with this application so it will be used during subsequent viewing; see instructions under the "Application File Association" section, found below83268620".

Note:The Style Sheet (sensor_data.xsl) must be at the same folder level as the .xsdat file.

Here are configuration and usage instructions for the most popular Web Browsers.

FireFox

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste security.fileuri.strict_origin_policy and pause while the list is filtered

(3) Double-click the security.fileuri.strict_origin_policy preference to switch the value from true to false

  • Drag-and-drop the .xsdat file in to FireFox.

...

  • Configure IE to display the .xsdat (one-time only).
    • Open IE -> Tools -> Internet Options.
    • Select the "Advanced" tab, and scroll down to the "Security" section.
    • Select "Allow active content to run in files on My Computer".
    • Select "OK", and then restart IE.
  • Drag-and-drop the .xsdat file in to IE.

Chrome

  • Rename the file extension from .xsdat file to .xml.
  • Drag-and-drop the .xsdat file in to ChromeIs currently not supported.
  • Due to security concerns, Google Chrome blocks XML files from accessing local style sheets.

Safari

  • Rename the file extension from .xsdat file to .xml.
  • Right-click the .xsdat file and use "Open With" to select Safari.

...

Overview

In conjunction with the supplied XML "Style Sheet" and a Web Browser or 3rd-party XML viewer/editor, the viewing of SDAT files is greatly enhanced in the XML format.

...

Note that DevWare still supports the original-format ".sdat" files, although support will eventually be removed.It is assumed that the reader of this document has working knowledge of DevWare, the use of SDAT files, and working knowledge of RegDB exporting of DevWare Files.

Application Requirements

The .xsdat file can be viewed in any application that accepts XML-formatted files. The most common and easily available are Web Browsers; IE (Microsoft Internet Explorer), FireFox, Google Chrome, and Apple Safari have all been verified to work with .xsdat files.

Refer to the instructions in the above "Quick Start Viewing Instructions"83268620" for Web Browser configurations. Or if you prefer, you can obtain a 3rd-party XML viewer/editor; Aptina has verified the following free viewer/editor from Microsoft:

...

  • Right-click any .xsdat file and select "Properties".
  • Select the "Change" button next to "Opens with:"
  • Select the application you want to be used to open the .xsdat file. If the application isn't found, use the "Browse…" button to add it to the list.
  • Select "OK" to close the "Opens With" dialog, and "OK" on the Properties dialog.

RegDB and Style Sheet Information

To export a .xsdat file from regDB, follow the same procedure as exporting a .sdat but use the "SDAT XML" options ( [NDA] and [Confidential] ).
The Style Sheet can also be exported by selecting "SDAT XML Style Sheet", or copying the file (sensor_data.xsl) from the standard folder where the SDAT files are located.

...

  • .

Display Information

The Style Sheet has been designed to preset to display the SDAT information in a more readable format.
The "Chip Descriptor" section displays the part's basic configuration information.
The "Address Spaces" section displays the various register pages used by this sensor.
The "Register/Bitfield Definition" section displays the registers and associated bitfields, along with their related information.
Bitfields are indented from their parent registers.
All Confidential items are highlight in Red. This applies to both internal and external .xsdat files. This is especially helpful for internal SDAT files where there was previously no indication of the confidential status of a register or bitfield. For internal .xsdat files, confidential registers and bitfields have their regular name, where as the external .xsdat file those registers and bitfields are renamed to their generic counterparts ( "RESERVED_" for registers, "BIT_" or "BITS_*" for bitfields ).