Every crash, caught and explained.
It’s like having a debugger attached to every device in the field. NoxCrash captures the fault, keeps the evidence through the reboot and reports it home through FleetNox, so a crash turns into a bug with a line number.
“It just reset” is not a bug report.
Devices in the field crash, reboot and carry on, and the evidence disappears with the reboot. Without a stack trace, teams guess, add logging, ship another build and wait for it to happen again.
NoxCrash keeps the evidence, so the first crash is the last time you have to guess.
A debugger on every device. No cable required.
Captures the moment
Registers, stack trace and fault reason saved the instant a hard fault, assert or watchdog hits.
Survives the reboot
Crash data is kept in retained RAM or flash until it’s been sent.
Points to the line
Addresses mapped back to functions and source lines using your build’s symbols.
Reports itself
Crash reports upload through FleetNox on the next connection, over Wi-Fi, cellular or a phone app.
Fleet-wide view
See which crash hits the most devices and which firmware version introduced it.
Tiny overhead
Zero cost until something goes wrong.
Specifications
- Reporting
- Through FleetNox
- Operating systems
- NoxOS, Zephyr
