Simple measurements of software trace data using Sourcery Analyzer
My last post covered how to import data into Sourcery Analyzer that didn’t come from the Linux Trace Toolkit. In this post I’ll show you a few simple tools you can use to inspect the data in more detail. If you are using Sourcery Analyzer its because you want to explore the software behavior or performance of your design. This task is really three parts in one:
- Data collection: Gathering up information from the target. Sourcery Analyzer helps by providing automated data collection for Linux and Nucleus systems and a means to import data of any type that can be expressed in a text file.
- Data analysis: Turning this raw data into useful answers. Sourcery Analyzer has a pre-stocked library of analysis routines or you can add your own if need be.
- Making comparisons and form conclusions: This is the part that is up to you and the spongy grey matter you’ve got! Sourcery Analyzer does have some tools to help, though.
In the next post I’ll introduce you to the advanced measurements which can be accomplished using the other measurement tools offered by Sourcery Analyzer. If you would like to try some of this on your own please consider picking up an evaluation copy of Sourcery Analyzer. If you have questions feel free to leave a comment or drop into the Sourcery Tools forum and ask.
- Model Vehicles
- A Deep Dive: Safety and Security on the Xilinx UltraScale+ MPSoC
- Testing Autonomous Vehicles by Throwing Digital Rocks
- Converging Systems: The how, the why and the implications for graphics & UI
- RISC-V and The Birth of the New Computer Architecture Ecosystem
- Designing with Automotive Audio Bus (A2B) Technology
- Saving money and improving safety with image sensors
- SWaPing Autonomous Vehicle Designs
- How to avoid Cyberattacks in your Embedded OS
- The Blurring of Safety and Security