I am looking at a development project that will require code banking. The target processor will most likely be the Triscend E5 family. I am wondering what effect code banking has on overall efficiency. I have searched the Keil web-site, but there is surprisingly little information available. The code will naturally break up into tasks that, in general, only require to make calls and references to code memory within the same code bank. Although I use the word task, the code will almost certainly be single threaded apart from some ISRs. Is it possible to advantageously place such tasks of code into one bank? Can common code such as library functions and ISRs be placed in common memory? The objective here is to minimise the frequency of bank switches. Does anybody have any advice based on practical experience?
You can freely choose where to locate your functions. Well, actually, source modules containing your functions. With carefull planing, you can minimize inter-bank calls. Also, you can locate frequently called functions and library code in the common area. I did several banked projects and it all worked surprisingly well. regards Dejan
I am looking at a development project that will require code banking. .... I am wondering what effect code banking has on overall efficiency. If you worry about the efficiency of code banking, why not avoid it alltogether. Why not just use a 23bit address chip. Philips has the MX and 669, Dallas has some and I'm sure there are others. Erik
Take a look at the following knowledgebase article for a lot of tips and ideas. http://www.keil.com/support/docs/158.htm Jon
If you worry about the efficiency of code banking, why not avoid it altogether. As so often happens, the whole point of the development is to use existing hardware. So I am stuck with the Triscend E5.
on or off the subject? Graham, You are making a new development with the E5. Do you have any knowledge of the future of this chip after the takeover?. Everything I have read is that ARM is all excited about the E7 - no mention of the E5 whatsoever. Erik
Eric: It is a software development supported on existing hardware so I am stuck on E5. Word from our distributor is that there will be no problem getting E5s in the future.