<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 27 Jun 2016, at 15:01, Deniz Erbilgin <<a href="mailto:deniz.erbilgin@gmail.com" class="">deniz.erbilgin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi Joseph,<br class=""><br class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">One approach would be first finding a situation where the EEPROM write
of the key behaves correctly when writing the key (which may be on say, a
dev board), and then changing variables in the test of the real system
aiming to make everything the same as the working case until it starts
working, then we know what breaks it<br class=""></blockquote>I guess this is similar to Adrian's suggestion?<br class=""><br class=""></div></div></div></blockquote>Yes, very similar. (Adrian's suggestion is a good first step on this process.)</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">I've gone through the docs and
tried to figure out what is the simplest reproducible situation where
the key is lost. I'm not sure if that is documented in the wiki or not,
but couldn't see it, perhaps you can share your thoughts?<br class=""></blockquote>So far, with our current firmware release, writing the key and waiting a bit is enough. I'm still working on finding anything more specific.<br class=""><br class=""></div></div></div></blockquote><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">By the way, I'm not really sure how to structure this properly (as you may have noticed) so I'd be grateful if anyone can point me to a good example to go on, or suggest other things that should be included.<br class=""></div></div></div></blockquote></div><br class=""><div class="">I'd just focus on keeping the very latest understanding clear. I think an iterative debug approach is inevitable. I'd hope that each time you perform a new test you end up with new information that rules out a number of possible causes. (If you can't figure out what possible cause a particular test rules out, don't bother doing the test!)</div><div class=""><br class=""></div><div class="">Joseph</div><div class=""><br class=""></div></body></html>