I created https://issues.apache.org/jira/browse/MYNEWT-482 <https://issues.apache.org/jira/browse/MYNEWT-482>
What I usually do is I start ‘newt debug’, and then issue flash erase commands via gdb. Which is not too bad either. > On Nov 10, 2016, at 2:00 PM, David G. Simmons <[email protected]> wrote: > > >> On Nov 10, 2016, at 4:59 PM, Kevin Townsend <[email protected]> wrote: >> >> >>> Backwards-compatiblity-breaking changes have been made to the boot >>> loader. Consequently, before using the latest, you will need to >>> completely erase the boot and images slots in your devices' flash and >>> upload a new boot loader. The latest code may appear to work with an >>> old boot loader, but you will eventually run into issues if you perform >>> image management (image list, upload, etc.). The least painful way >>> forward is to just erase your flash entirely, replace the boot loader, >>> and forget about it. Sorry about this this one; hopefully it is the >>> last time! >> Would an 'erase' command make sense to add to newt? I always end up firing >> up JLinkExe to erase my chips, which is easy enough, but being able to do >> something like 'newt erase' might be useful as a faster solution without >> having to lookup the connection string and part ID every time and for every >> chip. > > +10 :-) > >>> A more comprehensive list of changes will go out soon, but I thought >>> this one deserved special mention. >> This will be very useful. I think we've tackled all the breaking changes in >> our own codebase, but having them all in one place will help make sure we >> didn't miss any interesting new features. 0.10.0 is a really nice >> improvement, though. I'm impressed at how much you guys got into this >> release, and how much it's improved the system overall! >> >> K. > > -- > David G. Simmons > (919) 534-5099 > Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • > Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter > <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> > /** Message digitally signed for security and authenticity. > * If you cannot read the PGP.sig attachment, please go to > * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! > * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/> > **/ > ♺ This email uses 100% recycled electrons. Don't blow it by printing! > > There are only 2 hard things in computer science: Cache invalidation, naming > things, and off-by-one errors. > >
