Serial Ports

[rbtwas]

I'm trying to find the right way to connect to a mame pseudo terminal.

Most methods I've found make use of "-rs232" and "-modem" command line options, none of which show up as valid
options to mame 0.274.

Did I not compile in some option or is there a new way to do this?

Thanks

rwas

[startaq]

Systems can freely define what their serial ports are called, so what are trying to connect?

You can list the available slot options with -listslots.

[rbtwas]

Thanks for replying. I'm trying to setup my sim to use a pseudo port so I can use an external terminal emulator. One of several examples I found use this as an example: "mame -biospath path/to/firmware/dir -window -nomouse -vol -15 vt102 -rs232 pty" Note the "rs232 pty". My sim has these devices: ***@***.***% mamed mvme162 -listslots SYSTEM SLOT NAME SLOT OPTIONS SLOT DEVICE NAME ---------------- ---------------- ---------------- ---------------------------- mvme162 rs232trm dec_loopback RS-232 Loopback (DEC 12-15336-00) ie15 IE15 Terminal keyboard Serial Keyboard loopback RS-232 Loopback mockingboard Sweet Micro Systems Mockingboard D msystems_mouse Mouse Systems Non-rotatable Mouse (HLE) nss_tvi Novag Super System TV Interface null_modem RS-232 Null Modem patch RS-232 Patch Box printer Serial Printer pty Pseudo Terminal rs232_sync_io RS-232 Synchronous I/O rs_printer Radio Shack Serial Printer scorpion Micro-Robotics Scorpion Intelligent Controller sunkbd Sun Keyboard Adaptor swtpc8212 SWTPC8212 Terminal terminal Serial Terminal Outside of examples I've found on the web, I can't find any procedure in the docs for accomplishing this. Thanks. Robert W.

…

On Thu, Feb 20, 2025 at 6:12 AM Dirk Best ***@***.***> wrote: Systems can freely define what their serial ports are called, so what are trying to connect? You can list the available slot options with -listslots. — Reply to this email directly, view it on GitHub <#184 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7GFQGP2PX3Z75HVPUOKST2QXIFXAVCNFSM6AAAAABXQXL272VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRWGMZTAOI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[holub]

That's another example which can be helpful: https://blog.thestateofme.com/2022/05/25/attaching-a-terminal-emulator-to-a-mame-serial-port/

[sairuk]

You can start your machine then connect to the created pty with the correct properties, check Machine Configuration in the ui to confirm for this 9600 8N1

mame -window -nomouse -v -ui_active mvme162 -rs232trm pty

this creates /dev/pts/1 for me, however it may not be the same for you but you can view this under the Psuedo Terminals entry in the ui

i use minicom to connect to the pty for testing

minicom --baudrate 9600 -8 --term=vt102 --ptty=/dev/pts/1 --noinit

which outputs

Copyright Motorola Inc. 1988 - 2000, All Rights Reserved

MVME162 Debugger/Diagnostics Release Version 4.0 - 05/18/00
COLD Start

Local Memory Found =01200000 (&18874368)

WARNING: Configuration Data Failure (Invoke 'ENV' Command)

WARNING: Board Configuration Data Failure

MPU Clock Speed =32Mhz

162-Bug>

[rbtwas]

This works, Thanks! my pty was 21 btw. I had to hunt around for it. My executable is "mamed". Not sure why. This is what I ended up using: <mamed -window -nomouse -v -ui_active mvme162 -rs232trm pty> < minicom -p /dev/pts/21 --noinit> It's not clear to me why you'd use "-p/--ptty=" and not "-D". Both seem to work Robert W.

…

On Thu, Feb 20, 2025 at 11:40 PM sairuk ***@***.***> wrote: You can start your machine then connect to the created pty with the correct properties, check Machine Configuration in the ui to confirm for this 9600 8N1 mame -window -nomouse -v -ui_active mvme162 -rs232trm pty this creates /dev/pts/1 for me, however it may not be the same for you but you can view this under the Psuedo Terminals the ui i use minicom to connect to the pty for testing minicom --baudrate 9600 -8 --term=vt102 --ptty=/dev/pts/1 --noinit which outputs Copyright Motorola Inc. 1988 - 2000, All Rights Reserved MVME162 Debugger/Diagnostics Release Version 4.0 - 05/18/00 COLD Start Local Memory Found =01200000 (&18874368) WARNING: Configuration Data Failure (Invoke 'ENV' Command) WARNING: Board Configuration Data Failure MPU Clock Speed =32Mhz 162-Bug> — Reply to this email directly, view it on GitHub <#184 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7GFQDE5UCORIE3YMCIUG32Q3C7TAVCNFSM6AAAAABXQXL272VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRXGIYTOOI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[cuavas]

my pty was 21 btw. I had to hunt around for it.

Isn’t there a way to see that in the menus? I thought there was a menu in MAME that would show you the assigned PTY numbers for any PTY devices in the running system.

My executable is "mamed". Not sure why.

Because you have assertions enabled (DEBUG=1) – it automatically appends a “d” suffix.

[sairuk]

my pty was 21 btw. I had to hunt around for it.

Isn’t there a way to see that in the menus? I thought there was a menu in MAME that would show you the assigned PTY numbers for any PTY devices in the running system.

yeh there is, it is called "Pseudo Terminals"

[rbtwas]

Thanks holub. I actually found this the other night. One thing that confused me is why his executable is named "rc2014". He's also making use of the bitbang device, which should'nt be necessary in my case with the mvme162. The other thing that was'nt obvious to me was that the options seem to be dynamic based on the *machine*, and the option named needed match *exactly* that listed for that machine. All the examples I found used "-rs232" so I was a bit confused. I had figured this out last night but could'nt find the right pty being used. I also made use of the vt102 machine for a confidence test but again, I could'nt find the right pty and assumed there was something wrong. Sairuk's post gave me enough confidence to look harder, and I found a working pty. Robert W.

…

On Thu, Feb 20, 2025 at 7:00 AM holub ***@***.***> wrote: That's another example which can be helpful: https://blog.thestateofme.com/2022/05/25/attaching-a-terminal-emulator-to-a-mame-serial-port/ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[cuavas]

One thing that confused me is why his executable is named "rc2014".

He’s used the SUBTARGET option when building to create a binary with a subset of supported systems and a non-default name.

He's also making use of the bitbang device, which should'nt be necessary in my case with the mvme162.

The (poorly-named) bitbanger device can be used as an alternative to the PTY device if you want to use a TCP socket rather than a PTY.

The other thing that was'nt obvious to me was that the options seem to be dynamic based on the machine, and the option named needed match exactly that listed for that machine. All the examples I found used "-rs232" so I was a bit confused.

Yes, available slot devices depend entirely on the emulated system. It wouldn’t work otherwise considering the variety of expansion options in different systems. That’s why there’s a convenient -listslots verb (as well as the -listmedia verb).