Ben Eater's design-and-build videos are very popular, and I imagine a lot of people have followed his lead and built a first 6502 system. Some people might have started, and got stuck, and some might have finished, but find things don't work, and some will have been completely successful and then wanted to go further.
All 6502 related questions and projects are welcome here, in all those categories and more.
This post aims to put down a few pointers for how to use this forum and how to make progress.
First off, we're all friendly and prefer politeness, so please be family-friendly. It's better to say that you're struggling with something than to say that thing is terrible and ill-conceived. You might well find that the inventor is among your readers - no need to cast aspersions.
Second, there are many helpful and experienced people here, who are not all of exactly the same mind. So you will see some variety in preferences and approaches, and that's fine. There's usually no one right way to do things, and if some ways are fast but risky and others are slow but sure, it is a matter of preference which way to go.
But we have learnt a few things, in the projects we've personally built and in those whose progress we've followed.
One is, that enthusiasm is helpful and discouragement is to be avoided. As a consequence, it's better not to be too ambitious, and to proceed step by step. It's common enough to want to build a fully featured system and to get bogged down in adding new ideas, before building a solid core as a foundation. Your first system, or your second system, isn't likely to be your final system, so long as you don't get discouraged, so there's no need to try to do everything all at once.
Another, is that debugging is something of an art, or at least a craft, which benefits from experience. Taking care is a good way to proceed: take care to know what it is you've made, and what it is you've seen. Take care to describe your problem: what you expected to see, and what you did see. And take care to double-check your work, even if you think it's all correct. If everything seems right, but the thing doesn't work, well, evidently something is in fact wrong! So, doubt everything, generate hypotheses, take notes, and change one thing at a time.
When you're stuck, start a thread, describe what you're doing and what you see. When you get responses, read them carefully. Skipping over text is a big cause of things taking longer than they need to.
Skipping over text is a big cause of things taking longer than they need to. (Just testing.)
Also, there are thousands of topics here already, and others may have seen what you've seen or be trying to do what you're trying to do. Be sure to search, either using the forum search or using your favourite search engine.
We, the regulars and existing members, want to see you succeed, whether it's a hardware build, an extension, or a software problem. Ideally you'll find this is a good place to be, and will get ideas for further projects.
There are some major topics on this forum which will be of interest, which I might add here as links or others may give links in this thread. I'll give just two or three pointers here:
Login
Register
FAQ
Search
