#datapoint2200 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #datapoint2200, aggregated by home.social.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
The key switches I chose for the Datapoint 2200 keyboard required a plate so I made one up. Done as a PCB it’s not cheap but the Matt black finish works really well.
The only issue is that it slightly obstructs a couple of capacitors 🙁
I still need to source the hardware to properly mount it to the keyboard.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
Top row numbers can be shifted and keypad numbers can't. Both share an edge detector circuit and multiplexer 'line'. Top row key short to ground whereas keypad key have an SIO (or S10) signal. The keyboard logic board uses an analogue edge detector with 74121 pulse generator.
On the Pico I'm handling this by driving the SIO line low. When a keypress is detected I drive it high. If the keypress is still detectable then it's a top row key. If not then keypad.
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
The #Datapoint2200 keyboard PCBs have arrived and they look fantastic. Somehow larger than I expected, and very imposing.
#datapoint #ttlcomputer #vintagecomputer #retroconputer #mechanicalkeyboard
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've now added some photos to the repository (link in previous toot). Not the best quality but there's now something to look at.
Here's a couple of those for the Decoder PCB. There are more in the repository itself.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
I've just pushed a very long overdue update to my Datapoint 2200 repository.
New stuff includes schematics for video, keyboard and keyboard logic.
I've added a fair few LEDs to the processor PCB for most of the main registers, but I need to analyse which other signals deserve to have them.
I also need to add some photos and PCB renders to the readme.
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive.
(The old code doesn't use INCLUDE, but I need to import symbols from other files. The easy way is to write public symbols to a file in suitable format for an INCLUDE).
-
Now to get memory writes working in the Datapoint simulator. There's a /MEMORY_WRITE_READY input which needs to be driven. The circuit for this is on the keyboard decoder PCB.
Unconnected to the rest of that board, except for a POR output. Not the first bit of circuit I've found spilled onto a different board.
The circuit drives the /MEM_WRITE_READY line while the hardware bootloader reads data from tape. I can just glue it high for now.
-
Now to get memory writes working in the Datapoint simulator. There's a /MEMORY_WRITE_READY input which needs to be driven. The circuit for this is on the keyboard decoder PCB.
Unconnected to the rest of that board, except for a POR output. Not the first bit of circuit I've found spilled onto a different board.
The circuit drives the /MEM_WRITE_READY line while the hardware bootloader reads data from tape. I can just glue it high for now.
-
Now to get memory writes working in the Datapoint simulator. There's a /MEMORY_WRITE_READY input which needs to be driven. The circuit for this is on the keyboard decoder PCB.
Unconnected to the rest of that board, except for a POR output. Not the first bit of circuit I've found spilled onto a different board.
The circuit drives the /MEM_WRITE_READY line while the hardware bootloader reads data from tape. I can just glue it high for now.
-
Now to get memory writes working in the Datapoint simulator. There's a /MEMORY_WRITE_READY input which needs to be driven. The circuit for this is on the keyboard decoder PCB.
Unconnected to the rest of that board, except for a POR output. Not the first bit of circuit I've found spilled onto a different board.
The circuit drives the /MEM_WRITE_READY line while the hardware bootloader reads data from tape. I can just glue it high for now.
-
Now to get memory writes working in the Datapoint simulator. There's a /MEMORY_WRITE_READY input which needs to be driven. The circuit for this is on the keyboard decoder PCB.
Unconnected to the rest of that board, except for a POR output. Not the first bit of circuit I've found spilled onto a different board.
The circuit drives the /MEM_WRITE_READY line while the hardware bootloader reads data from tape. I can just glue it high for now.
-
'Clear the carry tiggle'.
I think they meant to say 'toggle', although twice suggests it may be intentional.
The documentation usually refers to 'flip-flops' as opposed to 'flags', or 'toggles'.
-
'Clear the carry tiggle'.
I think they meant to say 'toggle', although twice suggests it may be intentional.
The documentation usually refers to 'flip-flops' as opposed to 'flags', or 'toggles'.
-
'Clear the carry tiggle'.
I think they meant to say 'toggle', although twice suggests it may be intentional.
The documentation usually refers to 'flip-flops' as opposed to 'flags', or 'toggles'.
-
'Clear the carry tiggle'.
I think they meant to say 'toggle', although twice suggests it may be intentional.
The documentation usually refers to 'flip-flops' as opposed to 'flags', or 'toggles'.
-
'Clear the carry tiggle'.
I think they meant to say 'toggle', although twice suggests it may be intentional.
The documentation usually refers to 'flip-flops' as opposed to 'flags', or 'toggles'.
-
Episódio 141 – Processadores Lado “C” – Parte A
https://retropolis.com.br/2023/05/10/episodio-141-parte-a/
#Podcast #Datapoint2200 #Fairchild #Intel4004 #Intel8008 #processador #TMX1795