|
|
Post by bjonte on Feb 2, 2017 19:07:14 GMT
It is very easy to accidently run code in the wrong RAM bank or access data in the wrong bank. How do you cope with that? Have you developed some kind of assertions or runtime checks to verify consistency at assemble- or runtime?
|
|
|
|
Post by VDC 8x2 on Feb 6, 2017 17:00:21 GMT
They usually keep data in bank 1 and program in bank 0.
|
|
|
|
Post by bjonte on Feb 6, 2017 18:49:41 GMT
But that will require a lot of switching to access data from code or large part of common RAM. I'm trying to keep data where the code is and have both in both RAM banks. I think I'll prefer this, if I can avoid making too many mistakes.
|
|
