<div dir="ltr">I am having a devil of a time hooking a physical VT220 into my Raspberry PI Simh VAX. Everything is setup and working beautifully. I can telnet from another computer with no trouble and get a vax login. <div><br></div><div>I have a ttyusb0 connection. I can echo text to the terminal with no problem.<br><div><br></div><div>I can configure Raspian to divert the console to the terminal with no problem. But, I can't telnet to the vax from the Raspberry PI operating system. I can telnet from another PC, but not from within the Raspberry Pi. So, that doesn't give me the Vax login on the terminal.</div><div><br></div><div>So, I tried to create a serial connection to the ttyUSB0 using various means.</div></div><div>Method 1) attach ttix line=0,connect=/dev/ttyUSB0;1200-7n1 - This results in an error that says non-existent device.</div><div>Method 2) attach dz line=0,connect=/dev/ttyUSB0;9600-8n1 - This seemed to run successfully, but showed nothing on the terminal after a reboot.</div><div><br></div><div>Is there a way to connect a physical serial terminal via /dev/ttyUSB0 using SIMh Microvax 3900 simulator?</div><div><br></div><div>Thanks for any advice.</div><div><br></div><div>Kurt</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 19, 2017 at 3:05 AM, <span dir="ltr"><<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Simh mailing list submissions to<br>
<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-edge.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:simh-owner@trailing-edge.com">simh-owner@trailing-edge.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Simh digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: NetBSD 5.1 on MicoVAX 3900 boot error (Bob Supnik)<br>
2. Re: DEC VT emulators on MAME (Johnny Billquist)<br>
3. Re: NetBSD 5.1 on MicoVAX 3900 boot error (Mark Abene)<br>
4. Re: NetBSD 5.1 on MicoVAX 3900 boot error (Mark Pizzolato)<br>
5. Re: DEC VT emulators on MAME (Kevin Handy)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Tue, 18 Apr 2017 16:08:34 -0400<br>
From: Bob Supnik <<a href="mailto:bob@supnik.org">bob@supnik.org</a>><br>
To: <a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
Message-ID: <<a href="mailto:4ee0f9dc-071c-9ea9-fe74-48134c5e979b@supnik.org">4ee0f9dc-071c-9ea9-fe74-<wbr>48134c5e979b@supnik.org</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
You can get a pre-built Windows 32b 3.9 executable without Ethernet (and<br>
therefore, without needing WinPCap) here:<br>
<a href="http://simh.trailing-edge.com/sources/simhv39-0-exe.zip" rel="noreferrer" target="_blank">http://simh.trailing-edge.com/<wbr>sources/simhv39-0-exe.zip</a>. It should run<br>
fine under W10. See if it will boot NetBSD 5.1.<br>
<br>
/Bob Supnik<br>
<br>
On 4/18/2017 3:53 PM, <a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-edge.com</a> wrote:<br>
> You shouldn't need WinPCAP merely to test if the CD image is bootable.<br>
> The point of the boot test exercise is to help determine if the problem is<br>
> in NetBSD or due to recent changes to simh. If changes to simh are at<br>
> fault, I'll track it down and fix the problem.<br>
><br>
>> I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did<br>
>> run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a<br>
>> laptop I have to Win7 in the future and may try that. Until then I'll play<br>
>> with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta.<br>
> The boot test I'm suggesting will be far less work than setting up another<br>
> system.<br>
><br>
> Let me know.<br>
><br>
> - Mark<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 18 Apr 2017 22:39:08 +0200<br>
From: Johnny Billquist <<a href="mailto:bqt@softjar.se">bqt@softjar.se</a>><br>
To: <a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>
Subject: Re: [Simh] DEC VT emulators on MAME<br>
Message-ID: <<a href="mailto:2e3a017d-0166-df35-3b92-11ab3a6912f4@softjar.se">2e3a017d-0166-df35-3b92-<wbr>11ab3a6912f4@softjar.se</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Ok, looked at the schematics now.<br>
<br>
On 2017-04-18 21:53, Timothe Litt wrote:<br>
><br>
><br>
>> Since they're windowless, they are not EPROM (remember what the E<br>
>> stands for), but plain ROMs.<br>
> Nope. I meant exactly what I wrote.<br>
<br>
[...]<br>
<br>
Good point about it being the same chip. I hadn't considered that<br>
possibility. I know that for some 27-series proms, there were certainly<br>
both mask programmable as well as EPROM versions, where the mask<br>
programmable was more persistent safe. EPROMs have a risk of loosing<br>
their content eventually, even if not exposed to UV light.<br>
<br>
> As for which signal you use for what - it doesn't matter. OE puts the<br>
> chip into a low power state just as effectively as CS - assuming that<br>
> the part isn't in programming or ID mode. Since the part is never<br>
> written (in the terminal), this effectively gives you 2 CS pins<br>
> (effectively ANDed), and thus decoding requires at most an inverter.<br>
<br>
Not entirely true.<br>
OE should timing wise be done after CS and addresses have been stable<br>
for a certain time. And power consumption of the chip is related to the<br>
control of CS, and is not related to OE.<br>
<br>
While power consumption might not be a problem, and the timing can be<br>
solve, it does mean that driving CS and OE cannot be done identically.<br>
If you use OE as a CS, you should make make sure the address is stable<br>
some time before you activate OE, and if you use CS, you need to still<br>
drive OE at a point later in time, and not just tie them together or<br>
something.<br>
<br>
> The 27C256 is a 32K x 8 part; it has no A15 (but the cartridge socket does.)<br>
<br>
Yes, that was obvious.<br>
<br>
> Keven pointed out that the odd chip is probably the character generator<br>
> ROM - thus the separate address and data bus - and it doesn't need a CS<br>
> or OE. It's always reading something.<br>
><br>
> As I've written before, rather than guessing, a few minutes with an<br>
> ohmmeter can sort all this out.<br>
><br>
> I'm leaving that - and further exploration - as an exercise to the reader.<br>
<br>
I seriously doubt it's a character generator ROM in the normal sense of<br>
the word. The VT340 do not generate character output in hardware.<br>
It's a graphic terminal, which stores the text in the the bitmap, as far<br>
as I remember (I seem to remember being able to go into graphics mode<br>
and affect text already written). Also, you have soft definable<br>
characters, so the CPU need to have access to the same memory the<br>
character generator would use anyway, and it has to contain some RAM,<br>
minimum. So it needs to be in the normal memory space of the CPU.<br>
<br>
But there is indeed two address and databuses, so I think it's fair to<br>
say the two select lines are only used for a subset of the PROMs.<br>
<br>
There might be data in one ROM that is copied into RAM at startup.<br>
Character definition tables, for example, I could imagine.<br>
<br>
Anyway, most things can be worked out my doing the measurements you<br>
suggest, yes.<br>
<br>
Johnny<br>
<br>
--<br>
Johnny Billquist || "I'm on a bus<br>
|| on a psychedelic trip<br>
email: <a href="mailto:bqt@softjar.se">bqt@softjar.se</a> || Reading murder books<br>
pdp is alive! || tryin' to stay hip" - B. Idol<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 18 Apr 2017 15:07:06 -0700<br>
From: Mark Abene <<a href="mailto:phiber@phiber.com">phiber@phiber.com</a>><br>
To: Bob Supnik <<a href="mailto:bob@supnik.org">bob@supnik.org</a>><br>
Cc: <a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
Message-ID:<br>
<<a href="mailto:CAPCE1iYZrkE19nrcTB-K-ZArhYi0USyAZY0FRFBvCsQwMRw30g@mail.gmail.com">CAPCE1iYZrkE19nrcTB-K-<wbr>ZArhYi0USyAZY0FRFBvCsQwMRw30g@<wbr>mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Should one want winpcap in Windows 10, all one needs is:<br>
<a href="http://www.win10pcap.org/" rel="noreferrer" target="_blank">http://www.win10pcap.org/</a><br>
<br>
-Mark<br>
<br>
<br>
On Tue, Apr 18, 2017 at 1:08 PM, Bob Supnik <<a href="mailto:bob@supnik.org">bob@supnik.org</a>> wrote:<br>
<br>
> You can get a pre-built Windows 32b 3.9 executable without Ethernet (and<br>
> therefore, without needing WinPCap) here: <a href="http://simh.trailing-edge.com/" rel="noreferrer" target="_blank">http://simh.trailing-edge.com/</a><br>
> sources/simhv39-0-exe.zip. It should run fine under W10. See if it will<br>
> boot NetBSD 5.1.<br>
><br>
> /Bob Supnik<br>
><br>
><br>
> On 4/18/2017 3:53 PM, <a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-edge.com</a> wrote:<br>
><br>
>> You shouldn't need WinPCAP merely to test if the CD image is bootable.<br>
>> The point of the boot test exercise is to help determine if the problem is<br>
>> in NetBSD or due to recent changes to simh. If changes to simh are at<br>
>> fault, I'll track it down and fix the problem.<br>
>><br>
>> I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did<br>
>>> run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a<br>
>>> laptop I have to Win7 in the future and may try that. Until then I'll<br>
>>> play<br>
>>> with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta.<br>
>>><br>
>> The boot test I'm suggesting will be far less work than setting up another<br>
>> system.<br>
>><br>
>> Let me know.<br>
>><br>
>> - Mark<br>
>><br>
><br>
> ______________________________<wbr>_________________<br>
> Simh mailing list<br>
> <a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br>
> <a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170418/7481cbde/attachment-0001.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/<wbr>attachments/20170418/7481cbde/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 18 Apr 2017 22:39:48 -0700<br>
From: Mark Pizzolato <<a href="mailto:Mark@infocomm.com">Mark@infocomm.com</a>><br>
To: Mark Abene <<a href="mailto:phiber@phiber.com">phiber@phiber.com</a>>, Bob Supnik <<a href="mailto:bob@supnik.org">bob@supnik.org</a>><br>
Cc: "<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>" <<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
Message-ID:<br>
<<a href="mailto:03006E3FC39B5A48AB9DBCCC101090A82E8242E585@REDROOF2.alohasunset.com">03006E3FC39B5A48AB9DBCCC10109<wbr>0A82E8242E585@REDROOF2.<wbr>alohasunset.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Actually, the latest simh ‘supported’ WinPcap is npcap.<br>
<br>
Npcap is part of the nmap project and directly shares the latest libpcap code.<br>
<br>
Npcap has a BSD license like the original WinPcap did. Win10pcap is a GPL package and is untested and unsupported for use with simh Ethernet devices.<br>
<br>
Npcap is available from: <a href="https://github.com/nmap/npcap/releases" rel="noreferrer" target="_blank">https://github.com/nmap/npcap/<wbr>releases</a><br>
<br>
From: Simh [mailto:<a href="mailto:simh-bounces@trailing-edge.com">simh-bounces@trailing-<wbr>edge.com</a>] On Behalf Of Mark Abene<br>
Sent: Tuesday, April 18, 2017 3:07 PM<br>
To: Bob Supnik <<a href="mailto:bob@supnik.org">bob@supnik.org</a>><br>
Cc: <a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
<br>
Should one want winpcap in Windows 10, all one needs is:<br>
<a href="http://www.win10pcap.org/" rel="noreferrer" target="_blank">http://www.win10pcap.org/</a><br>
<br>
-Mark<br>
<br>
<br>
On Tue, Apr 18, 2017 at 1:08 PM, Bob Supnik <<a href="mailto:bob@supnik.org">bob@supnik.org</a><mailto:<a href="mailto:bob@supnik.org">bob@<wbr>supnik.org</a>>> wrote:<br>
You can get a pre-built Windows 32b 3.9 executable without Ethernet (and therefore, without needing WinPCap) here: <a href="http://simh.trailing-edge.com/sources/simhv39-0-exe.zip" rel="noreferrer" target="_blank">http://simh.trailing-edge.com/<wbr>sources/simhv39-0-exe.zip</a>. It should run fine under W10. See if it will boot NetBSD 5.1.<br>
<br>
/Bob Supnik<br>
<br>
<br>
On 4/18/2017 3:53 PM, <a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-edge.com</a><wbr><mailto:<a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-<wbr>edge.com</a>> wrote:<br>
You shouldn't need WinPCAP merely to test if the CD image is bootable.<br>
The point of the boot test exercise is to help determine if the problem is<br>
in NetBSD or due to recent changes to simh. If changes to simh are at<br>
fault, I'll track it down and fix the problem.<br>
I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did<br>
run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a<br>
laptop I have to Win7 in the future and may try that. Until then I'll play<br>
with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta.<br>
The boot test I'm suggesting will be far less work than setting up another<br>
system.<br>
<br>
Let me know.<br>
<br>
- Mark<br>
<br>
______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><mailto:<a href="mailto:Simh@trailing-edge.com"><wbr>Simh@trailing-edge.com</a>><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170418/0aaa0ccb/attachment-0001.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/<wbr>attachments/20170418/0aaa0ccb/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 19 Apr 2017 01:05:20 -0600<br>
From: Kevin Handy <<a href="mailto:khandy21yo@gmail.com">khandy21yo@gmail.com</a>><br>
To: Johnny Billquist <<a href="mailto:bqt@softjar.se">bqt@softjar.se</a>><br>
Cc: "<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>" <<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>><br>
Subject: Re: [Simh] DEC VT emulators on MAME<br>
Message-ID:<br>
<CANk4W2OuRsR=<a href="mailto:uLH_856YSmrG4hJurJFUkn6tq_%2BHGWsAegh24Q@mail.gmail.com">uLH_<wbr>856YSmrG4hJurJFUkn6tq_+<wbr>HGWsAegh24Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Looking at the schematic of the terminal from<br>
<a href="http://bitsavers.trailing-edge.com/pdf/dec/terminal/vt340/K-TC-VT340_Schematic_Feb87.pdf" rel="noreferrer" target="_blank">http://bitsavers.trailing-<wbr>edge.com/pdf/dec/terminal/<wbr>vt340/K-TC-VT340_Schematic_<wbr>Feb87.pdf</a>,<br>
it appears that there are two 8031 processors. One (E57) uses the 'P1 AA'<br>
bus and has the 51x8 nvrom, the other (E24) uses the 'P2 BA' bus.<br>
<br>
64Kx8 ram seems to be shared between them.<br>
<br>
1st guess, E57 does most of the heavy work (serial, uart, keyboard, etc),<br>
and the other E24 handles the display.<br>
<br>
Also, for chip select,there is a 'P1 AA15 H' and a'P1 AA15 L' on the<br>
connector which should help with the chip selection logic. (ie. the<br>
inverter is inside the terminal, not on the card).<br>
<br>
<br>
<br>
<br>
On Tue, Apr 18, 2017 at 2:39 PM, Johnny Billquist <<a href="mailto:bqt@softjar.se">bqt@softjar.se</a>> wrote:<br>
<br>
> Ok, looked at the schematics now.<br>
><br>
> On 2017-04-18 21:53, Timothe Litt wrote:<br>
><br>
>><br>
>><br>
>> Since they're windowless, they are not EPROM (remember what the E<br>
>>> stands for), but plain ROMs.<br>
>>><br>
>> Nope. I meant exactly what I wrote.<br>
>><br>
><br>
> [...]<br>
><br>
> Good point about it being the same chip. I hadn't considered that<br>
> possibility. I know that for some 27-series proms, there were certainly<br>
> both mask programmable as well as EPROM versions, where the mask<br>
> programmable was more persistent safe. EPROMs have a risk of loosing their<br>
> content eventually, even if not exposed to UV light.<br>
><br>
> As for which signal you use for what - it doesn't matter. OE puts the<br>
>> chip into a low power state just as effectively as CS - assuming that<br>
>> the part isn't in programming or ID mode. Since the part is never<br>
>> written (in the terminal), this effectively gives you 2 CS pins<br>
>> (effectively ANDed), and thus decoding requires at most an inverter.<br>
>><br>
><br>
> Not entirely true.<br>
> OE should timing wise be done after CS and addresses have been stable for<br>
> a certain time. And power consumption of the chip is related to the control<br>
> of CS, and is not related to OE.<br>
><br>
> While power consumption might not be a problem, and the timing can be<br>
> solve, it does mean that driving CS and OE cannot be done identically. If<br>
> you use OE as a CS, you should make make sure the address is stable some<br>
> time before you activate OE, and if you use CS, you need to still drive OE<br>
> at a point later in time, and not just tie them together or something.<br>
><br>
> The 27C256 is a 32K x 8 part; it has no A15 (but the cartridge socket<br>
>> does.)<br>
>><br>
><br>
> Yes, that was obvious.<br>
><br>
> Keven pointed out that the odd chip is probably the character generator<br>
>> ROM - thus the separate address and data bus - and it doesn't need a CS<br>
>> or OE. It's always reading something.<br>
>><br>
>> As I've written before, rather than guessing, a few minutes with an<br>
>> ohmmeter can sort all this out.<br>
>><br>
>> I'm leaving that - and further exploration - as an exercise to the reader.<br>
>><br>
><br>
> I seriously doubt it's a character generator ROM in the normal sense of<br>
> the word. The VT340 do not generate character output in hardware.<br>
> It's a graphic terminal, which stores the text in the the bitmap, as far<br>
> as I remember (I seem to remember being able to go into graphics mode and<br>
> affect text already written). Also, you have soft definable characters, so<br>
> the CPU need to have access to the same memory the character generator<br>
> would use anyway, and it has to contain some RAM, minimum. So it needs to<br>
> be in the normal memory space of the CPU.<br>
><br>
> But there is indeed two address and databuses, so I think it's fair to say<br>
> the two select lines are only used for a subset of the PROMs.<br>
><br>
> There might be data in one ROM that is copied into RAM at startup.<br>
> Character definition tables, for example, I could imagine.<br>
><br>
> Anyway, most things can be worked out my doing the measurements you<br>
> suggest, yes.<br>
><br>
><br>
> Johnny<br>
><br>
> --<br>
> Johnny Billquist || "I'm on a bus<br>
> || on a psychedelic trip<br>
> email: <a href="mailto:bqt@softjar.se">bqt@softjar.se</a> || Reading murder books<br>
> pdp is alive! || tryin' to stay hip" - B. Idol<br>
> ______________________________<wbr>_________________<br>
> Simh mailing list<br>
> <a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br>
> <a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170419/b8562239/attachment.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/<wbr>attachments/20170419/b8562239/<wbr>attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
<br>
------------------------------<br>
<br>
End of Simh Digest, Vol 159, Issue 26<br>
******************************<wbr>*******<br>
</blockquote></div><br></div>