Previous Thread
Next Thread
Print Thread
Joined: Feb 2010
Posts: 20
Likes: 1
P
Person Offline OP
Member
OP Offline
Member
P
Joined: Feb 2010
Posts: 20
Likes: 1
I am getting to a point in my research of these machines, to where I was planning to start adding them to MAME. Just some questions regarding the organization of things.

The TDV-2114 and TDV-2124 are to a large extent the same machine, with only the floppy drive and controller being different. It has to be mentioned that the two controllers are not cross-compatible, so the boot ROM needs to match which variety is being used. I guess it's still within reason to have the two machines as different configurations of the same machine?

For the TDV-2114, there is extensive documentation available at: https://www.technikum29.de/de/geraete/Siemens_6610/Siemens_6610_PDFs/
(Note: Siemens 6.610 is an OEM version of the Tandberg machine, the inside hardware is identical)

As of the TDV-2124, I have reverse-engineered the floppy disk drive controller card to get an overview of how to interface with it. I don't think I want to implement the microcode-processor on the card just yet, but I have decoded enough of it to have everything from a functional perspective documented.

The last question is, these machines were designed for Tandberg OS, and for the TDV-2124 in particular it's meant to run version 2. Now, TOS-2 is also cross compatible with the later TDV-2324, of which there already is a skeleton driver implemented in MAME. However the TDV-2324 uses a very different architecture altogether and is only backwards-compatible through the choice of CPU and software abstraction-layers. Should I need to care about this, or just start as if there was no connection between it and the TDV-21xx series?

Joined: Feb 2004
Posts: 2,561
Likes: 263
Very Senior Member
Offline
Very Senior Member
Joined: Feb 2004
Posts: 2,561
Likes: 263
If the hardware is different, just implement it as a separate driver_device implementation in a separate source file. If there are significant common parts, encapsulate them as devices. Separate machines can share the same software lists if it’s useful to do so.

Joined: Feb 2010
Posts: 20
Likes: 1
P
Person Offline OP
Member
OP Offline
Member
P
Joined: Feb 2010
Posts: 20
Likes: 1
The terminal module in TTY mode, as used in the TDV-2115 dumb-terminal, is now complete.

I added the TDV-2115L as a machine driver for proof-of-concept. The font- and keyboard mapping ROMs needed to run this can be found here: https://github.com/Frodevan/Tandberg/tree/main/TDV-2100/ROM-Files/TDV-2115L%20(no). The next step will be to add a CPU module, then get together the CPU interface on the terminal module and a bus device for the generic expansion part of the backplane. After that I'll be adding a RAM module then a disk module will be the only thing remaining for a working TDV-2114 computer.

Last edited by Person; 12/06/23 11:41 AM.
Joined: Feb 2010
Posts: 20
Likes: 1
P
Person Offline OP
Member
OP Offline
Member
P
Joined: Feb 2010
Posts: 20
Likes: 1
Yesterday I de-soldered and dumped the PROM chips that handles the video-RAM addressing. To add this to the emulated module, I will need to rework the page-roll mechanics and add the roll line-count instead of just simulating it by moving data in RAM.

Should I wait with this until the current machine implementation is merged?


Link Copied to Clipboard
Who's Online Now
2 members (Carbon, 1 invisible), 34 guests, and 2 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics9,293
Posts121,531
Members5,067
Most Online1,283
Dec 21st, 2022
Our Sponsor
These forums are sponsored by Superior Solitaire, an ad-free card game collection for macOS and iOS. Download it today!

Superior Solitaire
Forum hosted by www.retrogamesformac.com