does rtems 5.1 support create a core dump file when accessing a invalid address or other fatal errors?

[smallphd at aliyun.com]

Flash disk is used in our normal procedure. We use qspi interface to read and write data from/to a flash disk in order to record our logs.
The flash disk is parted to several parts. In such case, a new part could be allocated to save the crash data.



smallphd at aliyun.com
 
From: Sebastian Huber
Date: 2020-09-18 12:42
To: smallphd at aliyun.com; devel
Subject: Re: does rtems 5.1 support create a core dump file when accessing a invalid address or other fatal errors?
On 18/09/2020 03:24, smallphd at aliyun.com wrote:
 
> It is a good starting place to handle the crash problem. Especially 
> the records could be packed to send to a host computer using TCP/IP.
> One of the question for us is there is no network interface. But we 
> have a flash disk. So we should modify the send flow using file system 
> instead of network.
> Moreover, we need expand the recorded data to get more information of 
> the crash.
Saving crash data to a flash disk is normally a bit too complex and 
involves interrupts and DMA. I would save the crash data to a volatile 
memory area which survives a soft reset. After the soft reset, check if 
crash data is available and save it to the disk.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200919/31a01089/attachment.html>