Well at least it had plenty of address lines to make up for that ;) And I guess the designers thought that if you need all the address lines and an RW line that bad, you can just detect if the data bus is being driven :D On a serious note - amazing the hoops 2600 devs had to go through!
@@AndersNielsenAA yeah no kidding. That method was used. I think the supercharger did it. And some modern-day Solutions do it. I have written code for that little box and it is crazy.
I would like to see how the io and timers work for the 6532. This video came up at the perfect time as I was playing with the 6532 from an old 2600 to see if I could use it to diagnose 16k/64/256x1 dram in circuit. It has been a pain trying to test dram without using stack or zpage. I need to find which chips are bad and currently can find one chip only if bad. Replace it then run for find the next. This might be enough ram to do the job and has io to show which line(s)/chip(s) it might be!
It has a great name for an IC. Personally I have never used one, but 128 bytes seems really crowded. Plus you have to choose between page zero or page one. That's a tough choice.
I once used a 'support chip' providing RAM, FlashROM, glue logic and some I/O, it would have been the dream for all people using 8-Bitter but I forgot the name.
Or to handle hot swapping cartridges - control could be passed over to a tiny program in RAM which would turn control over to the cart ROM when inserted.
There was no read / write signal on the 2600 cartridge interface.
The designers felt 128 bytes was enough!
Well at least it had plenty of address lines to make up for that ;)
And I guess the designers thought that if you need all the address lines and an RW line that bad, you can just detect if the data bus is being driven :D
On a serious note - amazing the hoops 2600 devs had to go through!
@@AndersNielsenAA yeah no kidding. That method was used. I think the supercharger did it. And some modern-day Solutions do it. I have written code for that little box and it is crazy.
I would like to see how the io and timers work for the 6532. This video came up at the perfect time as I was playing with the 6532 from an old 2600 to see if I could use it to diagnose 16k/64/256x1 dram in circuit. It has been a pain trying to test dram without using stack or zpage. I need to find which chips are bad and currently can find one chip only if bad. Replace it then run for find the next. This might be enough ram to do the job and has io to show which line(s)/chip(s) it might be!
Like the video, but I think the pacing could be faster. Expecting more videos from you!
Very good very nice
A 6502 microcontroller with just 2 chips would have been wonderful.
Nice
It has a great name for an IC. Personally I have never used one, but 128 bytes seems really crowded. Plus you have to choose between page zero or page one. That's a tough choice.
Actually, what most systems did was to mirror page one and two in the address map - that way the choice of how much for each was in software :)
@@AndersNielsenAA Interesting! Since the stack works backwards 64 might be enough for each.
@@johnsaller2481 I dont think you would use 64 bytes of stack, that equals 32 subsequent subroutine calls, 16 would do in most scenarios.
I once used a 'support chip' providing RAM, FlashROM, glue logic and some I/O, it would have been the dream for all people using 8-Bitter but I forgot the name.
Maybe the 6508? Impossible to get though
The RIOT's ram could be used as a cache, but I don't know how that'll work.
Or to handle hot swapping cartridges - control could be passed over to a tiny program in RAM which would turn control over to the cart ROM when inserted.
How about a project with the TMS9918?
I have one and I have to try it out at some point - maybe a three/four chip thing would be possible.
What application are you using at 8:52?
KiCAD!
Is ESP32 better?
“Better” is very subjective :)
Better? No. FAR more powerful? Absolutely.
Yes timer coding.
I think you'll find that in my "Serial bootloader" video :)