Instead of endlessly removing and inserting the EEPROM, you can either obtain a ZIF socket.... or do a double-socket, i.e., put the EEPROM in a decent quality socket and insert the socketed EEPROM into the socket on your test board. That will keep you from possibly bending the pins on the EEPROM... as an extra socket is pretty cheap overall.

Good to hear you unlocked the EEPROM. Also, looks like Bill (plasmo) has made some good progress in his 65C02 based EEPROM programmer.

_________________
Regards, KM
https://github.com/floobydust

Yes, thank you all so much.

Attached are some pictures from this morning. I got my code to work properly to write the correct bytes, etc.

So for future information, I'm going to summarize:

1) When using the Raspberry Pi, don't use Python, use C++, and in particular the "wiringPi" library. Thank you again Gordon.

2) I used 'raspi-config' for it to boot into TTY mode. This also increases the speed. Use 'nano' to code, 'g++' to compile etc. Remember to include the -lwiringPi library while compiling!

3) In order to not fry the Pi, I used 74LS' chips, in particular 2 latches and 1 trans bus.

4) Also included is my code. It's not universal at all, but it at least gets you the idea. I will later go back and make it much more automated, because hand-typing each address is not fun.

Alright, thank you everyone. Sorry for giving up half-way. BigEd, you kept me going with your good ideas. I needed that, thank you.

Chad

EDIT: I also found this webpage super helpful to understand what codes should be sent to the LCD.

https://www.handsonembedded.com/lcd16x2 ... utorial-2/

Glad to be of help! It might even be the number one cause of project failure - to give up. Most projects can be sorted out, given enough attention. It's one reason why you commonly see advice to keep things simple and to proceed by small steps - an overambitious project is more likely to become overwhelming.

You know, that's exactly what I tell folks when I teach them how to program (not that I'm a programming teacher by trade). "Small victories". Just get that *next* line of code to compile, output something cool along the way. In KiCad, I often look at the 3D viewer so that I feel like, "Yep, I'm making progress!" The psychology is real.

So, thanks again, for the reminder, when I needed it most.

Chad