Does history matter to embedded developers - and what do ETM have to do with it anyway? [whitepaper series]

Posted by Magnus Unemyr on Aug 19, 2016 8:30:00 AM

Have you too spent days trying to find the bug that just can't happen, but still do? And found no evidence whatsoever as to why it happened? By using the methods and tools outlined in our free ETM/ETB tracing whitepaper, you can easily record and analyze execution history, and solve that "million dollar bug" in popular Cortex-M microcontrollers such as STM32, Kinetis, LPC, EFM32, XMC, etc.

Our free whitepaper on ETM/ETB instruction tracing describes how to record and analyze execution history using Cortex-M microcontrollers, using trace-enabled debugger probes like SEGGER J-Trace for ETM or any debugger probe for ETB on compatible devices. Read the whitepaper now!




ARM® Cortex® microcontrollers continue to push the price/performance ratio to unprecedented levels. This allows more complex embedded systems to be designed, comprising more software. And hence, the problem of debugging complex error situations is increased too.

Our free white paper outlines how the ETM and ETB instruction tracing technology can be used for advanced debugging of Cortex-M applications (in for example, STM32, Kinetis, LPC, XMC or EFM32 devices). Instruction tracing enables developers to record execution history for later analysis, which can be a great help in certain situations. 

Get the whitepaper here:

Read our ETM/ETB instruction tracing whitepaper!

Topics: Debugging