I would like to ask this time your view on what aspects would you consider to tickle when a strategic component like memory is replaced (in embedded system).

Basically, the main goal is to ensure that the software/firmware can run smoothly without any problems, but due to drivers changes, memory partitions, memory access time or even memory technology replacement can lead to large change in the software/firmware infrastructure, so in cases like these what approach would you choose to validate the software/firmware?

closed as too broad by alecxe, IAmMilinPatel, NarendraC, Bharat Mane, Kevin McKenzie Jun 22 '17 at 1:34

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • too board, need to be more specific – Yu Zhang Jan 25 '17 at 20:19
  • I think that the answer should issue two types of embedded systems: 1. With embedded OS 2. without embedded OS – Nir Rozen Jan 26 '17 at 17:18
  • Voting to close; partly due to being too broad, and partly due to me not understanding why changing hardware wouldn't require a full regression test. – Kevin McKenzie Jun 22 '17 at 1:34