I got some PCBs made a couple of years ago from JLCPCB and it wasn't that expensive, with shipping, 5 boards of small size (cheapest ones, not suitable for every project) was about €10 or €12.
Of course for hobbyists who are going to need several tries it makes it expensive, still it's a lot cheaper than before where I could only get PCBs for a much higher price.
Well, one can try repairing faulty pcbs and save some €€€. I do it always for expensive pcbs. For 2 layers it is not hard, more layers require small drills to break connections in vias.
I've been prototyping for some time now and never really focused on getting my projects into PCBs.
But yeah I guess you're right I can't really argue with you, I should improve my electronic design skills.
A Mister uses a more powerful FPGA + ARM CPU board along with extra SDRAM (I believe) to simulate known retro systems.
This was a personal project to make a custom video game console in this case using an FPGA, a couple of years back I finished one using microcontrollers and an actual CPU.
This project uses just enough SRAM and external components and a just enough powerful FPGA to be a retro-styled video game console.
I wanted to learn how to use FGPAs and continue to learn how video game consoles worked while building something unique.
So in a way, in terms of the technology, they're similar, except of course a Mister is something a lot more useful, I would say, as it simulates "real devices" and has a huge game library and this is just an educational project.
Just so you know, the exta SDRAM on MiSTeris only needed for some of the bigger emulated systems (e.g. CPS2). You can emulate a fair number of systems without it.
Like I've said in a few other comments (I've been trying to answer some of the comments, everyone has been really nice and really interested), one book that got me started was "Make: Electronics", I believe there's a second one now, I really like how the book explains the very basics in a pratical way.
Other than that there's a lot of info online nowadays. EEVblog aside from the forums has a nice youtube channel with videos with topics that range from beginner to advanced, GreatScott! is another one that explains things really well. Ben Eater has also a very interesting channel.
Also check other people's projects similar to things you would like to make.
As for kits, I started with the Arduino starter kit, it comes with a project book and a few varied components, after that I started buying components locally or from major international component shops and going towards the things that interested me the most in electronics.
I hope this helps :).
Actually they are still being manufactured to this day, that's one thing I didn't mention in the blog post is that you can get a brand new Zilog Z80 today, the 6502 (the CMOS version, 65C02) is also available.
You can probably get them from all the major electronic components stores (Digikey, Mouser, etc).
First of all thanks :)
And if you do find some time that project seems really cool, I never really got to work with the STM32 micros, but they are really powerful and cool.
Answering your question, well, even thought this is an electronics engineering project, I don't feel qualified to work with electronics professionally, for example, there's a lot of knowledge I lack.
I do work as a software engineer and I have done a couple of interviews myself to hire people and I do believe this helps when applying to a job, I'm not saying it completely replaces your qualifications but it might at least give you an edge. I'm seeing this as someone who would want to hire someone skillful. A technical project certainly is on the very least a nice thing to have in a CV. Of course this is just my opinion.
And if you are feeling like applying for a job based on your projects, just give it a go.
One advice I can give is: if you do have projects of your own, big or small, don't do it like me and keep them to yourself for years :P.
I really had no idea so many people would appreciate my pet project.
Yeah I did put more memory than the old school consoles had, absolutely, however the RAM in those days was only used for data mostly because they also had the cartridge ROM (or ROMs) to store the code. In my case I need to load the code to RAM, so I would always need a larger RAM.
But yeah, they also had less colors to work with and palettes (which were costier to implement in a software renderer). And this CPU is also faster than of those consoles.
I did give myself a more confortable system in terms of RAM and computational power.
But my aim was for a machine that would sit somewhere between the 3rd and 4th generation.
The double buffering I understand as well, if I was working with an FPGA I would not have gone with frame buffers, for sure, but that was the solution I found at the time using the components I was using and it worked.
The attention this has gotten, especially here in HN is still a bit unbelievable to me (and amazing of course). I don't want people to think this is an optimal console design or anything.
This is by no means a perfect project or "the way to go" in terms of homebrew video game consoles, it's just the way I found to do one while learning electronics along the way.
I am considering doing a series of blog posts, I don't know how often I could write them or if I could keep them going, but I will try.
I'm not big in social media and I have never written any posts or anything like before this one, which is weird, I'll admit it, so all this is kind of new, but I think I'll give it go.
Old systems used line-buffers like the Neo Geo or no buffers like the NES, for example.
So yeah, going with a frame-buffered approach was definitely easier, but this was not the only reason I chose this way.
I had a lot of restrictions, I was learning a lot of stuff, I didn't know how to work with FPGAs and I stuck with DIP package ICs that I could put on breadboards and experiment. And that's why I picked the AVR microcontrollers, which are awesome but have their disavantages. They have good performance (20Mhz), but not many pins and I had to bit-bang things like external RAM access (actually the PPU accesses 3 RAMs with only 32 IO pins available), which meant that it takes "some time" to access external memory.
That's why I chose 2 microcontrollers for video instead of just one, one of them could take "all the time in the world" (one frame) to fetch information and write a frame to the frame buffer while the other would generate the video signal and dump the a frame to the TV. Connecting the two, I felt a double buffer was better.
I definitely would have preferred doing a more "traditional" non-buffered render system, but this was the solution I found with what I had to work with.
I hope serves as a good explanation and maybe I'll get to explain these details better in another post :).
