1:04 - "In hindsight I should have done this differently" - can you elaborate? Seems that in the end, things worked out nicely, so I wonder what your apparent regret is rooted in.
Sure! Everything worked out fine for the at28c256 which was the chip I was really targeting. I don't really show it in the video but the data and address pins are out of order in the DIP package. The way that I assigned the pins from the AVR to the socket was specific to how that chip would sit in the programmer which meant it was easier to write software for that chip specifically. Just putting the data on port A means code is pretty straightforward, but if I were to program a different chip with other pin configurations the convenience is lost. I could have talked more about the firmware code in the video but I couldn't think of a way to do so that wouldn't have been boring. Had I been aiming for a more universal programmer or one that could target I2C ROMs I should have laid things out differently or put a lot more thought into the software side of things. TLDR: I was lazy and could have done things smarter but it does what I wanted it to.
2:22 I have a AT28C64B EEPROM and I went through this same problem, good that you mentioned it, so I know I wasn't the only one that happened to it
Le sigh. I always wanted an EPROM programmer in the 80s on my BBC. Had to make do with loading ROM-Images from floppy disk into Sideways-RAM.
What! you even built your own EEPROM programmer too! We've done almost exactly the same stuff. Mine is based off of an Arduino Mega.
Are you going to make more videos?
I like what I've seen so far.
I plan on making more videos in this style in the near future.
Subscribed instantly! Waiting for more content
Must say it's a nice video. Thank you. Wondering if you could push the limits to work something out to write on MCU.
You gor a new subscriber man
Pretty slick!
1:04 - "In hindsight I should have done this differently" - can you elaborate? Seems that in the end, things worked out nicely, so I wonder what your apparent regret is rooted in.
Sure! Everything worked out fine for the at28c256 which was the chip I was really targeting. I don't really show it in the video but the data and address pins are out of order in the DIP package. The way that I assigned the pins from the AVR to the socket was specific to how that chip would sit in the programmer which meant it was easier to write software for that chip specifically. Just putting the data on port A means code is pretty straightforward, but if I were to program a different chip with other pin configurations the convenience is lost. I could have talked more about the firmware code in the video but I couldn't think of a way to do so that wouldn't have been boring. Had I been aiming for a more universal programmer or one that could target I2C ROMs I should have laid things out differently or put a lot more thought into the software side of things.
TLDR: I was lazy and could have done things smarter but it does what I wanted it to.
@@AidanJennings Thanks for elaborating!
Great video, thanks
That is just awesomme.... What exact eeprom can be burned?
I build it and wrote the firmware with the AT28C256 in mind. Theoretically, any Dual In-line chip that fits within the programmer could be programmed.
@@AidanJennings Sweet. Thanks for the info. 🙂
Nice, maybe make a winforms app to flash and read (c#)
Can I get EEPROM PROGRAMMER pcb files pls
Are the board files open source?
Very interesting, however it's over my head, as I have no background knowledge or training in programming.