You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But essentially, for things like address decoding, you'd write:
// pins and names
Pin 4 = A15;
Pin 5 = A14;
Pin 6 = A13;
Pin 7 = A12;
Pin 8 = A11;
Pin 9 = A10;
Pin 10 = A9;
Pin 11 = A8;
// bundling named pins into a FIELD
FIELD Address = [A15..A00];
// now let compiler figure out the actual pin logic states for this address mapping
ZP_STACK = Address:[0000..01FF];
IO_SHADOW = Address:[0200..02FF];
RAM = Address:[0300...7FFF];
ROM = Address:[8000..FFFF];
Sorry for my slow response - work has left little time for side projects.
Galette doesn't support FIELD - I've only tried for GALasm compatibility, and not looked at WinCUPL. However, now you've mentioned it, this looks like an excellent addition. I doubt I will work on it soon, so don't hold your breath, but I'd like to add this.
Does galette support the
FIELD
nomenclature found in WinCUPL? Great example on this blog post: https://hackaday.io/project/174128-db6502/log/183434-address-decoding-and-how-to-get-it-rightBut essentially, for things like address decoding, you'd write:
This scheme translates to:
The text was updated successfully, but these errors were encountered: