@allObjects did you mean to post that last post here, and not just under the EEPROM/MRAM/FRAM discussion?
I don't test the Espruino board with all the external components each time - that'd end up being an insane amount of work. Having said that I guess having one of two of the obvious ones wired up might be helpful.
There's a test suite that gets run with a linux compile of the software, which is able to figure out most language errors. Also the builds I do for myself have a bunch of assertions in, so if none of them get hit in everyday use you can be relatively sure nothing is going too badly wrong.
I also have two espruinos connected together, which I use for flashing and benchmarking various commits on a variety of benchmarks. If those break then you know something is up as well!
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@allObjects did you mean to post that last post here, and not just under the EEPROM/MRAM/FRAM discussion?
I don't test the Espruino board with all the external components each time - that'd end up being an insane amount of work. Having said that I guess having one of two of the obvious ones wired up might be helpful.
There's a test suite that gets run with a linux compile of the software, which is able to figure out most language errors. Also the builds I do for myself have a bunch of assertions in, so if none of them get hit in everyday use you can be relatively sure nothing is going too badly wrong.
I also have two espruinos connected together, which I use for flashing and benchmarking various commits on a variety of benchmarks. If those break then you know something is up as well!