This is the mail archive of the ecos-devel@sources.redhat.com mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
For some RAM constrained targets it would be nice not have to load a redboot ram image (or running romram) and the new redboot rom image because they might not both fit. Even if they would it's nice to have such a feature for when you don't want to store a ram image permanently in flash or download it via serial. And in fact it might be useful for all targets which normally run redboot from flash. It's done by adding a do_update redboot command along with a helper function which runs out of RAM and erases the flash under redboot and rewrites it, than hangs (optionally reset?). This is a sketch of what the final patch would look like but I thought I'd ask if people think it's worth doing differently or worth including at all in CVS or point out things I might have not considered. I know it uses the flash device directly without going through io/flash but those functions live in ROM. thanks Jani
Attachment:
f.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |