??? 10/20/06 16:06 Read: times |
#126808 - Big Flash - coda and data! Responding to: ???'s previous message |
The idea of having the flash mappable to XDATA space is an excellent one!
Normally, constants, strings, etc just waste CODE space; so significant CODE space can be freed-up by moving them into XDATA - provided you can have some flash in XDATA space. Keil support this with their XCONST option. I worked on a project that did this with a Triscend TE5 (now Zylogic ZE5) - you might want to take a look at the way they did it. Triscend had a 32-bit external address bus, and SFRs that could map any of it into anywhere in CODE and/or XDATA space(s). Another use for lots of flash (even if you're not doing code banking) is for in-application firmware updates - you load the spplication into a "spare" flash "page", and only switch to executig from that page once you're certain that the new image is complete & correct. We had this planned on the Triscend, and I did some tests with it, but it was never fully deployed. Triscend had a couple of application notes on it. |