Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flasher should write 'okok' only after verifying the flash contents. #4

Open
darconeous opened this issue Feb 24, 2013 · 1 comment

Comments

@darconeous
Copy link
Contributor

Currently, the flasher program simply writes the image directly to the SPI flash, starting with 'okok'. If the flash process goes bad for some reason, the chip must be erased before the flasher program can be executed again. The flasher app should be modified to write these bytes last, preferably after doing a checksum or CRC check.

@malvira
Copy link
Owner

malvira commented Mar 7, 2013

Ack.

The whole flasher program is due for a real re-write. It would be nice to have a little protocol there where you can just manipulate the flash with serial commands. Do things like erase the whole thing, erase certain pages, write arbitrary bytes, verify blocks etc..

Along those lines, people are starting to use the nvm for run-time configuration now (including myself). 6lbr has https://github.com/cetic/6lbr/wiki/Nvm-Tool and I'm doing a simple structure mapped thingy in contiki. Might be nice to try to unify all of this.

I dream about having just a monolithic program that 'just do the right thing' instead of the hodgepodge of cobbled together stuff...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants