<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hi Mark, in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Intel-System-Trace-fall/m-p/1158199#M80368</link>
    <description>&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;what's the target platform /&amp;nbsp;decode use-case combination on which you're seeing&amp;nbsp;the issue? If you can share the input STP data&amp;nbsp;that'd&amp;nbsp;be perfect, but the API and TDE logs will also help.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 13 Mar 2019 10:22:37 GMT</pubDate>
    <dc:creator>Frank_P_Intel</dc:creator>
    <dc:date>2019-03-13T10:22:37Z</dc:date>
    <item>
      <title>Intel System Trace fall</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-System-Trace-fall/m-p/1158198#M80367</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are using Intel System Trace to trace hardware signals (ODLA, VISA)&amp;nbsp;for modern SOCs and PCHs.&amp;nbsp;We've found a bug in Trace Decode Library (TDE) of the System Trace Tool: when&amp;nbsp;MIPI STP data from ODLA contain the Global Trigger signal in active state, MIPI packets&amp;nbsp;decoder encounters the following exception:&lt;/P&gt;&lt;P&gt;Error: An exception was encountered during the execution of&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; decoder instance: mipi&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Engine Null Pointer Exception:&lt;BR /&gt;&amp;nbsp;location: NPK::EngineHandle::getChannelRecord&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; line: 63&lt;BR /&gt;&amp;nbsp;variable: d_rec&lt;/P&gt;&lt;P&gt;We can send extended NPK API log if we need it to resolve the problem.&lt;/P&gt;&lt;P&gt;We've started observing the problem from Intel System Studio Update 1 (2018.1.051) version. The previous (2018.0.040) version of System Studio doesn't contain the error and perfectly displays the Trigger in VCD output&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Feb 2019 13:50:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-System-Trace-fall/m-p/1158198#M80367</guid>
      <dc:creator>ermolov__mark</dc:creator>
      <dc:date>2019-02-22T13:50:58Z</dc:date>
    </item>
    <item>
      <title>Hi Mark,</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-System-Trace-fall/m-p/1158199#M80368</link>
      <description>&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;what's the target platform /&amp;nbsp;decode use-case combination on which you're seeing&amp;nbsp;the issue? If you can share the input STP data&amp;nbsp;that'd&amp;nbsp;be perfect, but the API and TDE logs will also help.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 10:22:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-System-Trace-fall/m-p/1158199#M80368</guid>
      <dc:creator>Frank_P_Intel</dc:creator>
      <dc:date>2019-03-13T10:22:37Z</dc:date>
    </item>
  </channel>
</rss>

