Tracealyzer version 4.8.2 has just been released. This version mainly fixes bugs, such as custom state machine models not being remembered on trace reload, and eliminates a number of compiler warnings in the Recorder source code. In addition, the update features improved streaming over UDP, and the bundled SSH library SSH.NET has been updated to the latest version. Users with a current maintenance contract can upgrade to Tracealyzer 4.8.2 from within the application, or by visiting the update page.

DevAlert 2.0, which is now immediately available from Percepio, is a major upgrade to our edge observability platform. The upgrade provides much improved diagnostic capabilities, including core dumps for Arm Cortex-M devices. This allows remote inspection of crashes, errors or security anomalies in full detail, including the function call stack, parameters and variables and with source code display.

As the first segment of a three-part series on JTAG, this post will give an overview of JTAG to set up some more in-depth discussions on debugging and JTAG Boundary-Scan. We will dive into the intricacies of the interface, such as the Test Access Port (TAP), key registers, instructions, and JTAG’s finite state machine. Like Interrupt? Subscribe to get our latest posts straight to your inbox.

Every developer wants universally applicable tools for their embedded development. However, hardware (processor type) and software (RTOS) architecture can limit the choice, making it a decision for the second-best rather than the best tool – even if you are in the mainstream. This is one of the reasons why Software Development Kits (SDKs) are becoming increasingly popular – even more so if they are easy to use and deploy.

If you’ve ever wanted to plot data acquired on your embedded target, this article is for you. It explores common use cases for real-time data visualization using STMViewer. Say goodbye to manual, time-consuming, and error-prone data collection and display methods to speed up your debugging process.

The Internet of Medical Things (IoMT), a subset of Internet of Things (IoT) technologies, comprises inter-networked devices and applications used in medical and healthcare information technology applications. IoMT devices connect patients, doctors and medical devices — including hospital equipment, diagnostic gear, and wearable technology — by transmitting information over a secure network.

A little more than a month ago, we released the free Tracealyzer SDK – a toolkit that allows other embedded software vendors to integrate Tracealyzer recording in their own software. At that time, the development team at PX5 in California were already hard at work combining Tracealyzer with their PX5 RTOS, and yesterday they released the integration. Built with Percepio’s SDK, in a just a few weeks.

The first step to making reliable IoT devices is understanding that they are inherently unreliable. They will never work 100% of the time. This is partially because we firmware engineers will never write perfect code. Even if we did, our devices need to operate through various networks and gateways, such as cellular modems, mobile phone Bluetooth applications, Wi-Fi routers, cloud backends, and more, and each of these may introduce unreliability.

The industrial automation landscape is evolving rapidly, driven by a fundamental shift in how software solutions are developed and deployed. In the past, many factories had in-house IT expertise to build and maintain their basic software stacks, the present reality is quite different. Small-scale factories often lack the IT know-how to manage their increasingly complex digital infrastructure, and they often rely on contractors to set up and maintain their systems.

Industrial IoT (IIoT) machines and sensors generate valuable time series data. It’s impossible to derive the insights necessary to inform decisions as a company to produce or operate more efficiently without sending operational technology (OT) data to informational technology (IT) systems.