This is close to what the PCB will look like.

Indeed, I am expecting the 6507 to run nicely at 2MHz but the 6532 isn’t rated for it and I haven’t tried any of the fancy tricks to run them at different frequencies.
I guess we’ll see

Hi!

I've given the 65uino an overhaul, removed the clock generation from Rev 0 and 1MHz oscillator, to make room for an 8MHz oscillator and '161 divider for serializers and such - and the option to run the main 6507 clock at 2MHz. Unsure if the 6532 will keep up.
I've also made enough space to ...

One topic that comes to mind that I think will interest you is " Antares 6500 Concept ," and another is " Happy New Year and happy hacking in 2016! " Oh, and note that modern ultrabright LEDs don't need much current at all to be easily visible in normal room lighting. I even used a red chip LED in ...

I've been wanting a 6502 assembly trainer for a while. It's a somewhat silly endeavour, but I'm going to make a RAM-only 6502 computer.

It's going to have the options of either single cycling every instruction from toggle switches or toggling in bytes to RAM.

Lot's of toggle switches, lots of LED ...

Assembled PCB's on the way

https://youtu.be/fASSCp3hDTQ

Thank you! It’s the minority of viewers who enjoy it enough to watch most of it - but that’s the minority I make it for

I hate to toot my own horn but I have to admit I'm happy with how this turned out and I can't wait to get it on a PCB. In here I guess making a ROM burner must be a rite of passage.

Mostly I'm proud of the price - got the BOM down to where it should be affordable for anyone to put one together ...

I actually do the reverse in my Ruby system in that the host MCU translates Acorn codes into ANSI codes to code running on the 6502 can output to an ANSI terminal without any changes... And if you want PDP11 code that translates BBC VDU sequences to ANSI sequences.... or C code.... :)

Sounds cool ...

Alternatively it's possible to make the "dance" by connecting A10->A12->A14 and A11->A13 ... if you're willing to sacrifice even more ROM space of course. It'll look strange if you dump the ROM but you should still have the "full" 4096 bytes of ROM space.. And of course it'll have to be programmed ...

Thought you might enjoy this. I was wondering if it's possible to fit an ICSP (In-Circuit-Serial-Programming) program into the 128 bytes of RIOT RAM on modified 65duino hardware. The attached file contains clumsy, untested, and probably buggy code, and while the ICSP process has a few limitations ...

I think it's interesting that you're essential doing the opposite of what most people do - so rather than having a VT100-compatible terminal connected to your computer for input and output, you're allowing other devices to use your 6502 based computer as an output terminal. I'm curious what these ...

Just don't write/rewrite termcap... That's above & beyond!


If it's supposed to be useful as a quick and dirty terminal to hook up to anything spitting out VT100, I guess it only has to know its own limitations.

And maybe handle as many of these as possible: http://www.braun-home.net/michael ...

The Picocomputer I sent you has a VT-like terminal in it. It's not that bad looking back but getting started was hard. The deepest part of the hole is CSI with multiple arguments. I haven't filled out every command yet, but the state machine logic is complete.

Excitedly waiting for that to arrive ...

So I'm slowly making my little 65uino into a very basic terminal - and so far it has some basic IO, scrolls, has a serial buffer and most recently it got a feel for flow control:

https://youtu.be/pdloxXDJejM

But.. The more I implement, the more I realize making just a 90% VT100 compatible, is ...