The MIPI Alliance released MIPI System Software Trace (MIPI SyS-T), a common data format for transmitting software trace and debug information between a test system and a device, such as a system-on-chip (SoC) or platform. The specification is publicly available to developers, and an accompanying example implementation library is accessible via GitHub.
Other available methods have been vendor-specific or based on major operating systems and there has been no independent format for exchanging debug information across software, firmware or hardware implementations. This fragmentation has been challenging for developers because devices typically incorporate software and components from different vendors, which increases debugging complexity and drives up development costs. The MIPI SyS-T specification also complements and strengthens the MIPI Alliance debug and test portfolio because it can be used with any MIPI Alliance debugging tool or transport protocol.
MIPI SyS-T Scalability, Instrumentation Library and APIs
MIPI SyS-T is scalable, applicable when debugging resource-constrained devices or robust, complex systems. Industries expected to benefit from the specification include wearables, smartphones, tablets and laptops as well as augmented reality/virtual reality (AR/VR), automotive systems and many other devices and applications.
The specification includes the trace formatting method as well as an optional MIPI SyS-T Instrumentation Library, which includes APIs and documentation that developers can use to jumpstart their use of the specification rather than starting from scratch.
Should you be anxious to get started, you can access MIPI SyS-T now. MIPI Alliance encourages developers to use, modify and share the example SyS-T library, provide feedback and interact with others in the user community. To discover more about visit the MIPI Alliance.