Is there any existing tool that could be applied to a hardware-in-the-loop QA system to capture information like the stack trace heading into the hardfault? And ideally, the equivalent of the the full output of the FreeRTOS view from Ozone. Beyond that, maybe even the stack unwinding for each of the tasks, too.
The application here is that we have a QA agent doing very labor intensive testing, and in the case of hardfaults, it would be great to grab all that information at the time of failure, where presently we only have the serial terminal log.
At a glance, it looks like SystemView might cover some of this need, by the ability to continuously log data.
But will it also give emit and log the call stack trace (if possible) at the moment of the hardfault? And the state of all the other tasks?
The ideal format for this tool would be a daemon that runs in the background, uses an existing JLink connection, and would capture and dump that information to a file based on certain conditions, maybe a specific number breakpoint or by checking a fault is active at the time of hitting a breakpoint.
I am looking into what can be mechanized via gdb ... but I almost never use command line GDB, since Ozone works well for my normally debugging.
It also occurs to me that it might be possible to do this via Ozone by writing a plugin that uses the Javascript engine, too?
The application here is that we have a QA agent doing very labor intensive testing, and in the case of hardfaults, it would be great to grab all that information at the time of failure, where presently we only have the serial terminal log.
At a glance, it looks like SystemView might cover some of this need, by the ability to continuously log data.
But will it also give emit and log the call stack trace (if possible) at the moment of the hardfault? And the state of all the other tasks?
The ideal format for this tool would be a daemon that runs in the background, uses an existing JLink connection, and would capture and dump that information to a file based on certain conditions, maybe a specific number breakpoint or by checking a fault is active at the time of hitting a breakpoint.
I am looking into what can be mechanized via gdb ... but I almost never use command line GDB, since Ozone works well for my normally debugging.
It also occurs to me that it might be possible to do this via Ozone by writing a plugin that uses the Javascript engine, too?