วีดีโอ

How?

What type of monitor were you using?

'Promo sm' 😣

In the transcript it is unclear how scrolling is drive. Why not give the 6502 access to the registers of the video card? Is this it? So the video card sends an interrupt at a line ( like in C64 ) and 6502 sets the address. Just reset the address right at the end of the frame, but allow interrupts on all lines, even in the flyback to the top.

Hi, I‘m very much liking the direction where you are going with your version of the BE6502 and following your series since you started and would like to help and give tips here and there if I can. Do you have a GitHub or webpage where you document your code and schematics as a reference so it’s easier to check for errors and give advice? I’ve built several similar incarnations of this style of computer on vero board 30 years ago as z80 versions and like to respin one of those as a 6502 sbc which would be pretty much like the one you do. My plan was to have it run at 12.6 MHz ( so 1/2 std. vga resolution) with 64/128k RAM but 16bit datapath for video ( got plenty of 10/12 ns old cache SRAM chips from old 486s )

Thanks for the mention!

Awesome work. Enjoying the series!

Great video, love watching them, keep them coming

I've used your script to generate a bin file for an image that is 200x150 for a faster access chip, but I'm looking at it in HEX like Ben did, but I'm not seeing zeroes for the blanking time. I'm not confident I understand how all this works, but if I'm correct, the first 200 bytes should have values, then the next 64 should be 00 but I only get two bytes of 00 before I start seeing other values again.

Those buttons made me laugh lol

Great videos, but still no decoupling caps anywhere. Might solve the random bit errors and improve performance at 10MHz...

insane project dude. Keep it up please!

A Platypus computer channel?

I envy your video production skills. Well done. I also modified Ben's design to include a 39SF010A but I also added an Arduino Nano clone for in-circuit ROM programming (28C256 or 39SF010A). If interested, please check it out. Search "r/beneater mods: 1/2/4/8 mhz" for a brief description.

This channel is taking breadboards to the limit. Debugging and or moving this monster must be a nightmare!

Interesting video, kerel. En een goed accent!

Very cool. Would it be possible to output a very small animation?

I remember watching the original video so long ago. But its amazing you didn't abandon it. Good job.

What in the god's name is this?! My man you are incredible xD

Bad Apple when?

The image is scrolling left, the viewport is going to the right.

very cool

This is an incredible project. Amazing seeing it working!!

oh I Now Subber 404,,HAHAHAHAAAAAA

Interesting, but I immediately red-flagged the lack of decoupling capacitors - nothing digital is guaranteed to work without them, you run on luck alone... 100nF ceramic for each chip is a good starting point.

I might be imaginnig it, but the further your videos go on the more your voice reminds me of Ben Eater's.

Very nice

This really needs a circuit diagram with address lines and control signals being labelled, rather than just pointing at chips and wires on the prototyping boards. You clearly understand what you've designed very well, but without a clearer picture of the connectivity, it's hard for the viewer to follow what you're describing, especially if they're not familiar with some of the chips. Thanks.

And move the mouse cursor off-screen before recording

Too much ‘er’ and ‘um’ and correcting yourself. Maybe a script will help.

Informative one! Wondering if any custom PCBs may help for any upcoming content or project build? Would love to sponsor and reach any collab together! (PCBWay zoey)

Hi Ben! I can´t believe you are using a LCD display!!!! It adds delays you have to wait during writes. You know it... I´d suggest you use a parallel FIFO and have an Arduino read the FIFO and write the LCD, or use a dual-port RAM. The FIFO is a sequential memory, you could have special codes in 0x80 .. 0xFF range to command a clear screen, home, goto line 0/1 etc. and use like a the FIFO like a serial port device. The Dual-Port RAM is a... Random Access Memory! you can write anywhere you want, anytime, so you can have 20 bytes for line 0 and 20 bytes for line 1, and write on these addresses. The Arduino would continuously read, compare to local copy and update the LCD when needed. I did something quite similar in the past, using only software and a 500ns interrupt. The interrupt would drive a state machine that continuously writes to the LCD. So the main program did not have to wait the LCD, it would write a memory buffer (zero delay) and then sometime later the buffer would be updated on physical LCD (with a little lag)

Your channel is underrated. Keep up the good work

This really makes me feel like I need to get back to my own huge messy computer+video display breadboard project. Using a flash chip to compact the video timing signal generation is a really interesting approach as an alternative to "smart" programmable logic. (And a cool throwback to how fast PROMs were often used for this sort of job before PALs/GALs became common.) I'm interested to see how this is going to progress. The approach I'm taking with my own project is using an ATMEL 8-bit MCU as a CRTC, because I want to be able to support multiple video modes with different addressing strategies (while keeping the actual pixel generation and shared VRAM access "real hardware", vs. the now common approach of using a hulking powerful MCU as a complete graphics coprocessor/video generator), but it is serious overkill for a lot of applications.

I have to get back to my board. I have yet to get the second chip to blink the lights lol appreciate your videos to add on

If there's one thing I really don't like about the 6502 compared to the Z80 (or intel 808x family) it is the phased clock timing voodoo. I mean, don't get me wrong, the 6502's predictable 50/50 bus duty cycle makes it really "easy" to do hitless shared memory between video refresh and CPU (as long as you don't mind your CPU clock being tightly coupled to video timing), but for the simple case the Intel/Zilog bus timing is *so* much more forgiving. (If the timing diagrams in the Z80 manual are to be believed you get basically a whole half-clock of slop after /WR rises for your memory device to latch the data.)

There's a trick called "trampolines" that you could use to avoid the need to ever set your vectors. Put at the top of your ROM assembler file (say 0x8000) the instructions: jmp irq; jmp nmi; jmp reset. Then put the vectors at the top pointing to 0x8000, 0x8003, 0x8006 (and write those into the EEPROM). After that, in your usual dev cycle you write normally your code under the irq:/nmi:/reset: labels. No matter which piece of code changes, the jmp instructions at the top of your rom will be reassembled with the correct target addresses and will be uploaded to your EEPROM on the next update. The only cost for those is 9 bytes, and you no longer need to worry about having forgotten to update your vectors.

Interesting that there are no visible decoupling decapacitors.

nice

Maybe a script would help? I noticed a little of ums.

Hi Scott, first one thing: stop using the Eh when you need time to think. I did it myself and I stopped with it when I was attended to it. By the way, why is your logo a duck with hat while your name is The Fox? I love the 6502 and I am thinking about it to make one on my own, I was thinking on a clock-generator that is going to the max when possible and when the processor is addressing slower RAM / ROM that then the clock is reduced in speed. On the dark side of computing they do the same, high speed RAM for doing calculations and low speed RAM for storage of data. Why would the evil empire have all good ideas. It becomes time that all 6502 owners stand up for their rights.

Soon I'll also build mine just waiting for few parts to arrive. Great vid subbed your channel

Great video. Thanks for sharing.

I love how you implemented the debug function on the LCD, all the while being able to use the LCD to display messages

I love the Mad Max reference :D I'm gonna start using it in my "hello world" messages :D

Also, FWIW, the TAX at line 180 is unneeded and has been removed from the most recent version of the code.

FWIW, the B (or BRK) flag is used to tell the IRQ routine that it was called by the BRK opcode rather than by a hardware interrupt.

That's very interesting! Subscribed for more 6502 videos! :)

The ‘-L <listfile>’ option will create a listing with the address, opcode, operands, and source for each line of code. Much easier than interpreting the a.out.

Nice work!