- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We are using Intel System Trace to trace hardware signals (ODLA, VISA) for modern SOCs and PCHs. We've found a bug in Trace Decode Library (TDE) of the System Trace Tool: when MIPI STP data from ODLA contain the Global Trigger signal in active state, MIPI packets decoder encounters the following exception:
Error: An exception was encountered during the execution of
decoder instance: mipi
Engine Null Pointer Exception:
location: NPK::EngineHandle::getChannelRecord
line: 63
variable: d_rec
We can send extended NPK API log if we need it to resolve the problem.
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
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mark,
what's the target platform / decode use-case combination on which you're seeing the issue? If you can share the input STP data that'd be perfect, but the API and TDE logs will also help.
Frank
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page