I have following question about code banking. There's some small tests, that uses one big library. So, how can I put this library to different code banks? Ofc, I can include this tests right in library project, but are there any other solutions?
Your question is based on rather complete misunderstanding of what a library is for. There's nothing to be gained from forcing its code into a particular bank.
"There's nothing to be gained from forcing its code into a particular bank."
Surely that depends upon the intra-bank call overhead and the hardware logic used for bank selection?
Calling a (library) function contained within the same bank does not require that overhead and could therefore have a significant speed advantage.
Only in just how bad, exactly, the effect is.
Which is exactly why it's a bad idea to fight the linker over where the best place for each object module is.
Indeed - and code banking is always a fight against the fundamental limitations of the architecture.
The fight might have been worth it years ago when there was little alternative - but, nowadays, why not just use an architecture which doesn't impose these restrictions in the first place??!
View all questions in Keil forum