Hi, I’ve started implementing support for core dump generation. Core would be generated on assert() and on unhandled exceptions. This would be placed somewhere on flash, and then you can download it from target and use it together with the built binary to look at system state at the time of the fault.
For the initial implementation, I was going to dump all the RAM present in the system, and just assume that there would be enough flash space to keep it. The info about memory ranges could come from BSP(?) in form of an array. I assume BSP would be the right owner for this data. Unless there are countering opinions? The 2nd rev of coredumping would then allow user to have an option for smaller dump. This would not contain all RAM, but rather a subset. I was thinking of only including the stack of the currently running task in it. Of course, this would be for later. — M
