Running TSS/8... missing something...

232 views
Skip to first unread message

Augusto Baffa

unread,
Apr 20, 2021, 10:46:11 AM4/20/21
to PiDP-8
Hi, 
 I'm trying to boot using TSS/8 image and I've followed the steps: IF switches to octal 2 and toggle Sing_Step... so far so good but after that It's not appearing "LOAD, DUMP, START" on ssh session.

Sem título.png

Also, when I try to connect telnet on port 4000, I get only a message "Connected to the PDP-8 simulator TTIX device, line 0" and no prompt. And when I trying some LOGIN, for example: "LOGIN 2 LXHE", everything looks the same.
Sem título2.png
What am I doing wrong?

Best,
Augusto Baffa



AndyB

unread,
Apr 21, 2021, 4:41:16 PM4/21/21
to PiDP-8
Hey - can you show the contents of your 2.script?

Augusto Baffa

unread,
Apr 21, 2021, 6:13:40 PM4/21/21
to AndyB, PiDP-8
It's default... I've reinstalled raspbian and got the same result :(  
(I followed the instructions from https://obsolescence.wixsite.com/obsolescence/2016-pidp-8-building-instructions to create my SDCard)
Is it necessary to use ETH0? I'm using only wifi (wlan0) with dhcp.

2.script: 
---------
; This script initializes a populated TSS/8 environment on an
; RS08 fixed-head hard disk drive (384 kB!) controlled by the
; RF08 disk controller.
;
echo Loading TSS/8 from the RS08 fixed-head disk...
; The IF + SING_STEP toggle feature allows switching among boot scripts,
; so reset simulator in case we're switching from one script to another.
reset

; Standard PDP-8 config for all scripts.
set cpu 32k
set cpu noidle
set df disabled

; Standard CPU throttling behavior.  See README-throttle.md.
deposit int-throttle THROT_DELAY 3
set nothrottle

; The software was configured with either --lowercase=auto or =pass,
; so send all text input to the simulator as 7-bit ASCII, including
; lowercase.  Lowercase output from the simulator will be sent to the
; console unchanged, as will non-printing chars.
set tti 7b

; Common shutdown behavior
set on
on SIGTERM exit

set rf enabled


load /opt/pidp8i/share/media/tss8/tss8_init.bin
attach rf /opt/pidp8i/share/media/tss8/tss8_rf.dsk
attach ttix 4000
run 24200

:end
------------------------

Augusto Baffa

--
You received this message because you are subscribed to the Google Groups "PiDP-8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-8+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-8/c5db163a-0654-4f42-93a4-93e05b066bfbn%40googlegroups.com.

AndyB

unread,
Apr 21, 2021, 7:53:26 PM4/21/21
to PiDP-8
Yep I have the same default set up.  The only difference is I use wired ethernet (not wifi).. although I am not sure how that factors into things....

Augusto Baffa

unread,
Apr 21, 2021, 9:27:52 PM4/21/21
to AndyB, PiDP-8
yeah... same behavior with eth0 :(
Do I need to follow another steps? or just set octal to 2 and single_step?
Lights keep blinking (seems to be normal)

Warren Young

unread,
Apr 23, 2021, 3:55:37 PM4/23/21
to PiDP-8
On Tuesday, April 20, 2021 at 8:46:11 AM UTC-6 augb...@gmail.com wrote:
It's not appearing "LOAD, DUMP, START"

I ended up tracing this to some SIMH change made between the last stable release and the one we updated to just prior to making the current stable release. Needless to say, checking whether TSS/8 still runs isn't one of our pre-release test steps. For it to be so, those of us doing the release work would have to have some TSS/8 expertise, so we'd be able to evaluate whether it's still working properly.

...Which is one reason I sent out that message a week before the release, for people to test the new software with their workloads...

Anyway, tip-of-trunk is updated with the fix for this. At least, the boot sequence specified by 2.script seems to get past whatever hung it up on the stable version.

Augusto Baffa

unread,
Apr 23, 2021, 4:29:39 PM4/23/21
to Warren Young, PiDP-8
Gr8... I'll update to the trunk version and test it. Thank u so much


   

--
You received this message because you are subscribed to the Google Groups "PiDP-8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-8+un...@googlegroups.com.

Augusto Baffa

unread,
Apr 23, 2021, 5:38:23 PM4/23/21
to Warren Young, PiDP-8
Thanks Warren. Now it's running with the trunk version.

William Cattey

unread,
Apr 23, 2021, 6:02:38 PM4/23/21
to PiDP-8
Nicely done, Warren!

I just scanned the deltas for the updated SIMH version.  An obvious smoking gun did not present itself to me.

Would you care to say a bit about how you chased down "update SIMH" as a fix?

-Bill

Warren Young

unread,
Apr 23, 2021, 6:34:47 PM4/23/21
to PiDP-8
On Friday, April 23, 2021 at 4:02:38 PM UTC-6 bill....@gmail.com wrote:

An obvious smoking gun did not present itself to me.

Several of the PDP-8 specific tape and disk devices were changed, plus the usual assortment of generic-level changes.  That stuff down in pdp8_sys.c looks like a fair candidate for changing how simulated instructions affect the simulator.
 
> Would you care to say a bit about how you chased down "update SIMH" as a fix?

Bisection, the regression tester's best friend.

When fossil bisect pointed out the problem appeared on one side of the SIMH update merge point and not the other, I browbeat Git into updating my clone of the upstream SIMH source tree, built a fresh pdp8 simulator, and tried running our 2.script with it. When the reported symptom didn't recur, I was virtually certain a call to tools/simh-update would fix it, and it did.

To go further and find out which of the ~10 weeks of changes upstream fixed it, one sufficiently interested could try using my tools/simh-bisect script. But I am not one so interested. :)

I did visually scan the upstream commit list since Feb 3, but nothing really jumped out at me as an obvious culprit.
Reply all
Reply to author
Forward
0 new messages