Hi! First time posting here. Hopefully this is not a stupid question. I come mostly from a mobile app development background. But recently looking into a project that involves essnetially a Cortex M, currently prototyping on an Arduino, and considering using FreeRTOS. I am very used to remote crash reporting solutions like Sentry or Crashlytics for mobile development. I am wondering about the same thing for embedded devices. How do one ensure an anomaly free experience once the device gets into the end users’ hands? Or is this somehow not a realistic concern? Please advise. Thanks in advance!
I think the reporting is somewhat more simplistic on a Cortex-M, especially as the RTOS kernel and application are built as a single executable, rather than there being the RTOS running separately from the application. Some tools, such as Atollic, have some minimal crash analysis built into the tool (type of exception, address off offending instruction, register values). If you don’t have such a tools then you can add some basic code as per the following link to help: https://www.freertos.org/Debugging-Hard-Faults-On-Cortex-M-Microcontrollers.html
Hi Richard, Thanks for the tips on Atollic! Yeah I figure we can build a custom tool for field reporting. But we are wondering if there are any turn key solutions or common design patterns around this. Or is this simply not a common problem – detecting issues that end-users might be having in the field without adding user friction in doing error reporting? Thanks! Howard
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.