I figured one of y’all would just know seeing how ubiquitous the 6502 is. I’m not following any tutorial at the moment and it has been too long since I last mucked around in assembly. I have the programming manual but it is convoluted between the 6502 and 65C816 stuff.
I’m messing with the little Easy 6502 emulator (Flatpak/FlatHub). I want to nest a couple of loops. I should probably just use the stack, but I went down this rabbit hole and damn it I want to find the rabbit!
I want something like (crude):
define lineL $1000
define lineH $1001
LDA $00
STA $lineL
LDA $02
STA $lineH
Hopefully I have that endian right… So now I have a 2 byte word starting at address 0×1000 and loaded with 0x0200. I want to increment this value as a 16 bit variable up to 0x05FF. What I am struggling with is which addressing mode indexes like this or if this must be manually implemented (– which does not seem right to me).
I’ll figure it out on my own in the next couple of hours regardless. It is more fun to chat and see the spectrum of knowledge here, or maybe not, either way, ya don’t know if ya don’t try. Skool me Woz
FORTH, and as a stepping stone into more complex hardware… again. I kinda did this once before and am getting back into it.
I am just goofing around with the emulator. I would actually like to try breadboarding something without any external connection and build it up into an interpreter. Basically try to build my own basic FORTH like threaded language from scratch. It is ambitious for my skill level. I actually have the chips to build this with a 6502, 65C816, Z80, 6809, 68010, 68008, and 8085, along with a bunch of peripherals. I also have several chips running various embedded versions of FORTH. I never managed to pick up stack programming well enough. I got so caught up in just getting FORTH onto the various chips and then getting a sensor or two working, but never built anything complex or beyond tutorial scopes. Now I am thinking in terms of the fundamentals without all the extra overhead… or trying to. There are a bunch of questions in the back of my head that I would like to answer with a functional understanding. Like what are the real limits of fuzzing for unknown hidden instructions and registers, how some red team exploits work in practice, or reasons bare metal programming is uncommon on current CPU hardware… and several other lingering curiosities.
I wish I could just jump into some 3k page documentation for a modern SoC and have a chance of doing anything useful, but it seems one needs to understand a great deal of implied context and methodologies. So I go to the source of the hardware that the present leaders played with as kids, figuring I might follow the breadcrumbs to understand them.