cc65 VS eeprom-programmer

True. The code generated by https://cc65.github.io/ is pretty decent but there are a few places where hand-rolled assembler will perform much better when you need it. Although I've made things for 6502-based systems in C with this handy compiler (thanks cc65 contributors!).

Is there something intrinsic to how C handles addressing that makes segmented architectures more painful than they ought to be? Or maybe is there a language where segmented addressing is easier?

I hadn't really thought about it in a while. :)

cc65

There's tools like cc65 that let you write C code for the NES.

You can use any text editor for coding and the tutorial uses cc65 for compiling assembly to machine code.

You can use cc65 https://cc65.github.io/ but because you are compiling it in a limit hardware the cc65 has its rules and recommendations to follow in order to get the most optimal binaries, and more specifically I read this when I made the "Pong" game for NES as a practice long time ago https://nesdoug.com/ , I hope it helps, happy coding!

What assembler/tools did you use anyways? Personally I'd recommend ca65 from the cc65 C compiler utility. It's very powerful, open source, and kept updated (unlike a lot of ancient 6502 tools, like WDC's)

It really is a cool project. https://github.com/cc65/cc65

It provides some template configuration files describing different memory layouts. And provides common libraries for input/output.

There's also a LLVM fork for MOS: https://github.com/llvm-mos/llvm-mos

They've got some interesting hacks with ZeroPage memory and register allocation: https://llvm-mos.org/wiki/Code_generation_overview

Interesting if you geek out on that kind of research.

not entirely sure what you're asking, but does this help? https://github.com/beneater/eeprom-programmer

Hello, I have attached the outputs from running this script https://github.com/beneater/eeprom-programmer/tree/master/multiplexed-display

it is in the video description, this is the same link you are going to find there: https://github.com/beneater/eeprom-programmer/blob/master/multiplexed-display/multiplexed-display.ino

I'm having some difficulty with the EEPROM Programmer. As the title describes, the writeEEPROM function is writing the last byte of data to all of the addresses. I am using Ben's code from here, so I think it's pretty safe to say it's a hardware problem.

One reason to use EEPROMS was that you don't need a special programmer to write them. I managed to get away with an Arduino thanks to this project - much cheaper since I didn't already have a programmer.

programming a 28c256 is really easy, have a look at the datasheet. On github you can find a lot of DIY solutions, for example https://github.com/beneater/eeprom-programmer