vendredi 5 août 2016

How to stop RAM test destroying its own variables embedded C?

During startup tests I am required to test all RAM locations using a galpat test, I have wrote the function to do this but run into a problem that the functions variables exist in RAM and therefore get mashed as part of the test.

What would be the best way around this?

Aucun commentaire:

Enregistrer un commentaire