Thanks, guys, what a timely (for me) refresher on interfacing the 6502!

Although the conversation reminds me of the days of butting heads with a teenage son... When I asked him to do simple things in a straightforward, experience-proven way -- be it wash dishes or vacuum the rug, I was not really ...

Sometime in the late 90's I was moving yet again with many kids in tow, and got so overwhelmed with stuff that I ordered a dumpster and got rid of pretty much everything non-essential, including every issue of Byte magazine from 1979 to early 90's and a lot of Compute, Dr. Dobbs and various Amiga ...

willeye, I don't think you did anything wrong! Garth's site is full of circuits and tips, for all of us to use and enjoy!

I am just venting frustration at Mr. Eater for not giving credit where it's due.

I think there is a big difference between making hard-to-find modules available at or near cost vs. marketing a kit of few Chinese breadboards and parts for $299. There is nothing wrong with getting paid for your work, but if you are copying a schematic that someone else had shared with the ...

Welcome!

A quick note on attribution, in case you haven't realized it: the so-called 'Ben Eater' computer is a shameless, direct copy of Garth Wilson's design.

Garth Willson has been making 6502 machines for decades, and has shared everything with our community , without peddling merch or asking ...

Installing Gowin V1.9.11.01 Education (Linux x64), and of course it does not run -- some libraries missing. So,
Giving up for now after dorking around with qt and libraries and paths until sick.

If you have it working, please let me know

Also, somehow lost my Nano20K, so ordered another from ...

That pretty much covers the implementation issues!

Also, top memory is a good place for a temporary symbol table for local symbols, which are very similar to what the assembler needs and you can probably reuse most of the code. That is precisely what I was talking about a few posts back (and how I've implemented it a couple of times in the past ...

Funny you should say that... Chuck was indeed annoyed when I tried to discuss manual control of the datastack (which is kind of necessary for any multi-register practice), and I gave up trying to get him excited about that. And in those early days of ColorForth he did not want to think about ...

As an aside, after briefly experimenting with a multi-stack forth 20 or so years ago, I also tried a curious take on ColorForth with multiple TOS registers , mapping 7 colors to ARM7 registers for local computation and using a single datastack for manually spilling/filling registers.

_ _ 100 ...

"Keeping a device for resolving names to stack offsets" means it would have to be kept somewhere, and define the primitives for managing it...
It's been a while, but it was minimal and contained (pretty much a temporary 48-byte array of 16 hashes/offsets and a 2 extra primitives to create and ...

Careful, Michael, you may start sounding like a PIC or Arduino salesman!

By 'local symbol table' I mean that during the compilation of a word, I keep a device for resolving names to stack offsets, and clear/disable it at the end of a compilation.

Having a different stack does not change the fact that you need to resolve local names to offsets into _that_ stack. If you ...

Why not use the return stack for locals? Since you have to close the scope prior to returning, it is absolutely natural to use it. Managing an extra stack does not seem worth it.

I've added locals to a few Forth-like languages by keeping a local 'symbol table' that tracks offsets into rstack, and ...

I always try to match the 'official' address and data pinning designations (for debugging and the archeologists), but it really does not matter... Sometimes you can make the layout work much better by picking whatever works.