So.

I acquired some W24512AK RAMs following a previous recommendation in this thread, and installed one in Wren. But it doesn't seem to work. I'll test another one on a breadboard with an arduino, because it's entirely possible that they're all dead on arrival, seeing as I got them on aliexpress ...

Unfortunately I only have a Pi 1 model B with the 26 pin header, which reduces me to 15 pins, two of which are for the UART, which I kinda need. However, I should be fine with just data bus and control line logging. I'm already well into yak shaving with Forth so don't expect me to be analysing any ...

For the moment I'll probably be having the Pi drive the 6502's clock, which solves the timing issues.

The main thing to keep in mind is that my sole motivation for this is boredom. The more problems I have, the better. Even if all I get out at the end is a better Forth for the Pi and the knowledge ...

First off, hello, long time no see, university happened, a ram chip exploded, etc etc etc. But I have new parts on the way and a whole lot of spare time - and a Raspberry Pi sat on my desk doing nothing.

As mentioned in the main Wren Prototype post, I currently have the machine set up with an AVR ...

YouTube will win in the end - they have the power and technology to force them upon you

There will always be a way to watch youtube videos without ads, unless google manage to seize control of all computers and entirely eradicate user-written code. Which doesn't seem to far out of their ...

Yes, two spaces.

Line break after every sentence!

Jokes aside, I (being probably a good 20-30 years younger than most people here) type very differently outside of this forum. My website has about three capital letters and none of them are at the start of sentences. You could write an entire ...

Only tangentially related to 6502, but it's such a clever design that I couldn't not share it.

https://www.youtube.com/watch?v=V6XnSvB34y8

I've tested all the control pins with a multimeter, and they're definitely connected to the stuff that produces those control signals. Unless there's something disconnected internally, it's not that.

Except now it doesn't. It worked for a few minutes but now all reads are returning nonsense. I didn't touch the board at all in that time.

I think I might be haunted.

First off, I have no idea how the 43256 (figuratively) exploded. I was running the board on 5v from a USB-UART adaptor, so there shouldn't have been anything more than 5v on the board. It could have been ESD, but I didn't go anywhere near it. Who knows.

Secondly, I put ...

And now the RAM has somehow exploded. This basically kills the computer because (as already mentioned earlier in the thread) the 62256s I have don't play nicely with the 6502 for whatever reason, and the 43256 worked for some reason.

Looking at it, I might just put it on the bus and use it in 8 bit mode. I only have one VIA, and port B is already reserved for SPI data in.

However I do it, physically connecting it will be very awkward, because the module I have just has an 8*2 pin header on, which I'm connecting to by jamming ...

I think my next goal will be talking to a character LCD I have (HD44780, of course). I'm currently thinking of using the 4-bit interface to save on IO pins.

No, I was just being stupid and forgot to reset the monitor before testing the speed. It seems closer to 60khz, which is still way better than 8.

And if I remove some unnecessary sleeps in the code, I can get it all the way up to 100khz. Result!

Looks like my earlier maths was completely off, because I just doubled the AVR's clock speed (from 4mhz to 8mhz) and now it's clocking the 6502 at about 330khz. That's a much more acceptable speed, so I think I'll leave the monitor as it is for a while.