#kim1 — Public Fediverse posts

It's time to release the #RAMpager! An MTU banked RAM expansion card for the #KIM1 computer.

This board allows up to 1MB of memory via a 4KB banked window (with different read/write controls, so you can write to a page while reading from another!).

https://codeberg.org/hkzlab/KIM-1_RAMpager

As usual, thanks to #PCBWay for sponsoring the project via PCB production.

If you wish to donate even small amounts, it's always appreciated and you can do so via ko-fi.com/hkzlab
I use that mainly to pay components for these projects.

Enjoy!

It's time to release the #RAMpager! An MTU banked RAM expansion card for the #KIM1 computer.

This board allows up to 1MB of memory via a 4KB banked window (with different read/write controls, so you can write to a page while reading from another!).

https://codeberg.org/hkzlab/KIM-1_RAMpager

As usual, thanks to #PCBWay for sponsoring the project via PCB production.

If you wish to donate even small amounts, it's always appreciated and you can do so via ko-fi.com/hkzlab
I use that mainly to pay components for these projects.

Enjoy!

It's time to release the #RAMpager! An MTU banked RAM expansion card for the #KIM1 computer.

This board allows up to 1MB of memory via a 4KB banked window (with different read/write controls, so you can write to a page while reading from another!).

https://codeberg.org/hkzlab/KIM-1_RAMpager

As usual, thanks to #PCBWay for sponsoring the project via PCB production.

If you wish to donate even small amounts, it's always appreciated and you can do so via ko-fi.com/hkzlab
I use that mainly to pay components for these projects.

Enjoy!

It's time to release the #RAMpager! An MTU banked RAM expansion card for the #KIM1 computer.

This board allows up to 1MB of memory via a 4KB banked window (with different read/write controls, so you can write to a page while reading from another!).

https://codeberg.org/hkzlab/KIM-1_RAMpager

As usual, thanks to #PCBWay for sponsoring the project via PCB production.

If you wish to donate even small amounts, it's always appreciated and you can do so via ko-fi.com/hkzlab
I use that mainly to pay components for these projects.

Enjoy!

It's time to release the #RAMpager! An MTU banked RAM expansion card for the #KIM1 computer.

This board allows up to 1MB of memory via a 4KB banked window (with different read/write controls, so you can write to a page while reading from another!).

https://codeberg.org/hkzlab/KIM-1_RAMpager

As usual, thanks to #PCBWay for sponsoring the project via PCB production.

If you wish to donate even small amounts, it's always appreciated and you can do so via ko-fi.com/hkzlab
I use that mainly to pay components for these projects.

Enjoy!

Here is the fully assembled #KIM1 #RAMpager, and no bodges in this revision (for now)!

Here is the fully assembled #KIM1 #RAMpager, and no bodges in this revision (for now)!

Here is the fully assembled #KIM1 #RAMpager, and no bodges in this revision (for now)!

Here is the fully assembled #KIM1 #RAMpager, and no bodges in this revision (for now)!

Here is the fully assembled #KIM1 #RAMpager, and no bodges in this revision (for now)!

Testing the new revision of the #RAMpager with my #KIM1 clone plus MTU motherboard!

If you are observant, the lit 7 segs indicate that the KIM-1 reset successfully, which means that the logic on this board correctly handles internal/external memory decoding.

This board can (optionally) live alone on the MTU bus, if one so desires!

Testing the new revision of the #RAMpager with my #KIM1 clone plus MTU motherboard!

If you are observant, the lit 7 segs indicate that the KIM-1 reset successfully, which means that the logic on this board correctly handles internal/external memory decoding.

This board can (optionally) live alone on the MTU bus, if one so desires!

Testing the new revision of the #RAMpager with my #KIM1 clone plus MTU motherboard!

If you are observant, the lit 7 segs indicate that the KIM-1 reset successfully, which means that the logic on this board correctly handles internal/external memory decoding.

This board can (optionally) live alone on the MTU bus, if one so desires!

Testing the new revision of the #RAMpager with my #KIM1 clone plus MTU motherboard!

If you are observant, the lit 7 segs indicate that the KIM-1 reset successfully, which means that the logic on this board correctly handles internal/external memory decoding.

This board can (optionally) live alone on the MTU bus, if one so desires!

Testing the new revision of the #RAMpager with my #KIM1 clone plus MTU motherboard!

If you are observant, the lit 7 segs indicate that the KIM-1 reset successfully, which means that the logic on this board correctly handles internal/external memory decoding.

This board can (optionally) live alone on the MTU bus, if one so desires!

If all goes according to plan, I'll have two weeks off work at the end of this month.

Was thinking of writing something for the #KIM1 again, as I found the two previous experiments rather fun.
Also I now have a solution in search of a problem: 1MB of RAM on that machine is ridiculous and I'd like to find something to use at least a slice of that expansion.

Would have been easier if I also had the time to design a graphics card for the computer.

If all goes according to plan, I'll have two weeks off work at the end of this month.

Was thinking of writing something for the #KIM1 again, as I found the two previous experiments rather fun.
Also I now have a solution in search of a problem: 1MB of RAM on that machine is ridiculous and I'd like to find something to use at least a slice of that expansion.

Would have been easier if I also had the time to design a graphics card for the computer.

If all goes according to plan, I'll have two weeks off work at the end of this month.

Was thinking of writing something for the #KIM1 again, as I found the two previous experiments rather fun.
Also I now have a solution in search of a problem: 1MB of RAM on that machine is ridiculous and I'd like to find something to use at least a slice of that expansion.

Would have been easier if I also had the time to design a graphics card for the computer.

If all goes according to plan, I'll have two weeks off work at the end of this month.

Was thinking of writing something for the #KIM1 again, as I found the two previous experiments rather fun.
Also I now have a solution in search of a problem: 1MB of RAM on that machine is ridiculous and I'd like to find something to use at least a slice of that expansion.

Would have been easier if I also had the time to design a graphics card for the computer.

If all goes according to plan, I'll have two weeks off work at the end of this month.

Was thinking of writing something for the #KIM1 again, as I found the two previous experiments rather fun.
Also I now have a solution in search of a problem: 1MB of RAM on that machine is ridiculous and I'd like to find something to use at least a slice of that expansion.

Would have been easier if I also had the time to design a graphics card for the computer.

The good news for today is that, at least, rev. 1 of the #KIM1 #RAMpager has been submitted for production at #PCBway.

There, that's it. That's the peak of the day.

And I still have several hours of bullshit to endure.

The good news for today is that, at least, rev. 1 of the #KIM1 #RAMpager has been submitted for production at #PCBway.

There, that's it. That's the peak of the day.

And I still have several hours of bullshit to endure.

The good news for today is that, at least, rev. 1 of the #KIM1 #RAMpager has been submitted for production at #PCBway.

There, that's it. That's the peak of the day.

And I still have several hours of bullshit to endure.

The good news for today is that, at least, rev. 1 of the #KIM1 #RAMpager has been submitted for production at #PCBway.

There, that's it. That's the peak of the day.

And I still have several hours of bullshit to endure.

The good news for today is that, at least, rev. 1 of the #KIM1 #RAMpager has been submitted for production at #PCBway.

There, that's it. That's the peak of the day.

And I still have several hours of bullshit to endure.

@eduardocasino Eduardo, happy to see you here! Thanks for your #KIM1 work, I always wanted one and now I got one thanks to that. I'll also build a few more of your boards in the future (eyeing the floppy controller).

About that feature, my advice is to make it optional behind a jumper, so one can detach from the serial port without resets, if so desired.

@eduardocasino Eduardo, happy to see you here! Thanks for your #KIM1 work, I always wanted one and now I got one thanks to that. I'll also build a few more of your boards in the future (eyeing the floppy controller).

About that feature, my advice is to make it optional behind a jumper, so one can detach from the serial port without resets, if so desired.

@eduardocasino Eduardo, happy to see you here! Thanks for your #KIM1 work, I always wanted one and now I got one thanks to that. I'll also build a few more of your boards in the future (eyeing the floppy controller).

About that feature, my advice is to make it optional behind a jumper, so one can detach from the serial port without resets, if so desired.

@eduardocasino Eduardo, happy to see you here! Thanks for your #KIM1 work, I always wanted one and now I got one thanks to that. I'll also build a few more of your boards in the future (eyeing the floppy controller).

About that feature, my advice is to make it optional behind a jumper, so one can detach from the serial port without resets, if so desired.

@eduardocasino Eduardo, happy to see you here! Thanks for your #KIM1 work, I always wanted one and now I got one thanks to that. I'll also build a few more of your boards in the future (eyeing the floppy controller).

About that feature, my advice is to make it optional behind a jumper, so one can detach from the serial port without resets, if so desired.

Here it is, released #MOStermind for the #KIM1:
https://codeberg.org/hkzlab/MOStermind_KIM-1

I really wonder if this works fine on a teletype. Should someone in a near or distant future ever try it there, please let me know.

A video terminal should work fine though, you just need that, a KIM-1 and a RAM expansion that fills at least 2KB (we're using a bit less than 1.5KB) starting from 2000h.

Enjoy!

Here it is, released #MOStermind for the #KIM1:
https://codeberg.org/hkzlab/MOStermind_KIM-1

I really wonder if this works fine on a teletype. Should someone in a near or distant future ever try it there, please let me know.

A video terminal should work fine though, you just need that, a KIM-1 and a RAM expansion that fills at least 2KB (we're using a bit less than 1.5KB) starting from 2000h.

Enjoy!

Here it is, released #MOStermind for the #KIM1:
https://codeberg.org/hkzlab/MOStermind_KIM-1

I really wonder if this works fine on a teletype. Should someone in a near or distant future ever try it there, please let me know.

A video terminal should work fine though, you just need that, a KIM-1 and a RAM expansion that fills at least 2KB (we're using a bit less than 1.5KB) starting from 2000h.

Enjoy!

Here it is, released #MOStermind for the #KIM1:
https://codeberg.org/hkzlab/MOStermind_KIM-1

I really wonder if this works fine on a teletype. Should someone in a near or distant future ever try it there, please let me know.

A video terminal should work fine though, you just need that, a KIM-1 and a RAM expansion that fills at least 2KB (we're using a bit less than 1.5KB) starting from 2000h.

Enjoy!

Here it is, released #MOStermind for the #KIM1:
https://codeberg.org/hkzlab/MOStermind_KIM-1

I really wonder if this works fine on a teletype. Should someone in a near or distant future ever try it there, please let me know.

A video terminal should work fine though, you just need that, a KIM-1 and a RAM expansion that fills at least 2KB (we're using a bit less than 1.5KB) starting from 2000h.

Enjoy!

If wife has no pressing work for me at the #farm, I'll start work on releasing #MOStermind for the #KIM1.

If wife has no pressing work for me at the #farm, I'll start work on releasing #MOStermind for the #KIM1.

If wife has no pressing work for me at the #farm, I'll start work on releasing #MOStermind for the #KIM1.

If wife has no pressing work for me at the #farm, I'll start work on releasing #MOStermind for the #KIM1.

If wife has no pressing work for me at the #farm, I'll start work on releasing #MOStermind for the #KIM1.

If I'm getting the #KIM1 memory decoding right, to have the #RAMpager work as a single card on the MTU bus I need to do two things:
- Assert /DECEN when the address is in the range 0000h-1FFFh. Easy, I already have everything I need on my current card
- Assert K7 when the address is in the FFFxh range (vectors) so that the KIM-1 can react and remap them.

The second point requires at least a 74LS133 for the decoding (plus a diode). Not a problem, but a reroute of the board will be necessary.

So next steps:
1. Work on a rev.1 with bugs fixed but without this feature
2. Add this feature in a rev. 2

If I'm getting the #KIM1 memory decoding right, to have the #RAMpager work as a single card on the MTU bus I need to do two things:
- Assert /DECEN when the address is in the range 0000h-1FFFh. Easy, I already have everything I need on my current card
- Assert K7 when the address is in the FFFxh range (vectors) so that the KIM-1 can react and remap them.

The second point requires at least a 74LS133 for the decoding (plus a diode). Not a problem, but a reroute of the board will be necessary.

So next steps:
1. Work on a rev.1 with bugs fixed but without this feature
2. Add this feature in a rev. 2

If I'm getting the #KIM1 memory decoding right, to have the #RAMpager work as a single card on the MTU bus I need to do two things:
- Assert /DECEN when the address is in the range 0000h-1FFFh. Easy, I already have everything I need on my current card
- Assert K7 when the address is in the FFFxh range (vectors) so that the KIM-1 can react and remap them.

The second point requires at least a 74LS133 for the decoding (plus a diode). Not a problem, but a reroute of the board will be necessary.

So next steps:
1. Work on a rev.1 with bugs fixed but without this feature
2. Add this feature in a rev. 2

If I'm getting the #KIM1 memory decoding right, to have the #RAMpager work as a single card on the MTU bus I need to do two things:
- Assert /DECEN when the address is in the range 0000h-1FFFh. Easy, I already have everything I need on my current card
- Assert K7 when the address is in the FFFxh range (vectors) so that the KIM-1 can react and remap them.

The second point requires at least a 74LS133 for the decoding (plus a diode). Not a problem, but a reroute of the board will be necessary.

So next steps:
1. Work on a rev.1 with bugs fixed but without this feature
2. Add this feature in a rev. 2

If I'm getting the #KIM1 memory decoding right, to have the #RAMpager work as a single card on the MTU bus I need to do two things:
- Assert /DECEN when the address is in the range 0000h-1FFFh. Easy, I already have everything I need on my current card
- Assert K7 when the address is in the FFFxh range (vectors) so that the KIM-1 can react and remap them.

The second point requires at least a 74LS133 for the decoding (plus a diode). Not a problem, but a reroute of the board will be necessary.

So next steps:
1. Work on a rev.1 with bugs fixed but without this feature
2. Add this feature in a rev. 2

Let's write a little thread about the fuckups I made with the #KIM1 #RAMpager.

First, the good news: the board is behaving decently now. I still need to do some heavy testing to hammer it, especially regarding the access to the registers that hold the current read/write pages but, for now, it seems they're fine accessed from the monitor.

Let's write a little thread about the fuckups I made with the #KIM1 #RAMpager.

First, the good news: the board is behaving decently now. I still need to do some heavy testing to hammer it, especially regarding the access to the registers that hold the current read/write pages but, for now, it seems they're fine accessed from the monitor.

Let's write a little thread about the fuckups I made with the #KIM1 #RAMpager.

First, the good news: the board is behaving decently now. I still need to do some heavy testing to hammer it, especially regarding the access to the registers that hold the current read/write pages but, for now, it seems they're fine accessed from the monitor.

Let's write a little thread about the fuckups I made with the #KIM1 #RAMpager.

First, the good news: the board is behaving decently now. I still need to do some heavy testing to hammer it, especially regarding the access to the registers that hold the current read/write pages but, for now, it seems they're fine accessed from the monitor.

Let's write a little thread about the fuckups I made with the #KIM1 #RAMpager.

First, the good news: the board is behaving decently now. I still need to do some heavy testing to hammer it, especially regarding the access to the registers that hold the current read/write pages but, for now, it seems they're fine accessed from the monitor.