This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F2800157: Risks of running code from RAM

Part Number: TMS320F2800157

Because of flash operation, we need to run ISR from RAM, but we are questioning if this is as relieable as code that is stored in flash. Microcontroller will not be reset/turned off for longer periods of time (could be months). 

We have checked and this uC has a parity check for local shared RAM, but it does not correct it, just triggers a NMI if a parity error is detected when reading from it. This means that if an EMI causes a memory corruption a reset will be done - this is not a problem unless it will be happening frequently. 

My questions are:

- are there any downsides or risks of running code from RAM?

- does RAM have "data retention" problem or is data retained as long as it is being powered? Does it degrade over time like it does in flash over years/decades?

Best regards, M