Column: Embedded design
Figure 2: Project-appropriate icons in the main Tracealyzer window
“meta-mab-percepio”, and its directory structure is as follows:
Figure 3: Trace View graph
• conf consists of the layer configuration, a standard Yocto practice.
• recipes-images/packagegroups contains “
packagegroup-custom.bb”, a file that contains the necessary LTTng packages that we will need in the resulting images.
• recipes-images/images/ contains “phytec-headless-
image.bbappend”, my own customisation to the Phytec Linux image. It simply adds “packagegroup- custom” to the image.
• recipes-kernel/linux/ contains a recipe to add the necessary customisation to the Linux kernel to support LTTng.
With these customisations, the Linux image can simply be built, loaded on an SD card, booted on the development kit, and run through the instructions on Percepio’s “Getting Started with Tracealyzer for Linux” page to collect the appropriate traces. Once the necessary commands have run and there’s a “lttng-traces” directory in the home root directory, we can copy it over to the x86(_64) machine for analysis in Tracealyzer. Tis can be done by powering off the Phytec development kit, and copying the directory from the SD card over to the PC. Another way is to transfer the trace data over a network connection, managed with Tracealyzer’s integrated features.
Figure 4: The threads and processes executed during the entire duration of the capture
www.electronicsworld.co.uk February 2021 11
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44
