https://cdeever.github.io/atari-vcs/docs/cartridge-hardware/bankswitching/Recent content in Bankswitching on Programming the Atari VCS in AssemblyHugoen-ushttps://cdeever.github.io/atari-vcs/docs/cartridge-hardware/bankswitching/programming-across-banks/Mon, 01 Jan 0001 00:00:00 +0000https://cdeever.github.io/atari-vcs/docs/cartridge-hardware/bankswitching/programming-across-banks/<h1 id="programming-across-banks">Programming Across Banks<a class="anchor" href="#programming-across-banks">#</a></h1> <p><a href="https://cdeever.github.io/atari-vcs/docs/cartridge-hardware/bankswitching/">Bankswitching</a> hands you the hardware: several 4 KB banks and a few hotspot addresses that swap which one the <a href="https://cdeever.github.io/atari-vcs/docs/architecture/rom/">window</a> shows. That much is simple. The hard part is <em>living</em> there — writing code that keeps working while the bytes underneath it change. Because the swap is a silent side effect of touching an address, the program counter doesn&rsquo;t move when a bank flips; only the contents under it do. Two facts follow, and both shape how you lay out a banked game.</p>