• Please review our updated Terms and Rules here

What are the Steps for getting TU58 Running ??

Marty

Veteran Member
Joined
Jul 26, 2009
Messages
3,141
Location
Boulder , Colorado USA
Hi all;
I have the following two ports, one at com5 for the PDP 11/45 terminal Monitor, and a
Second port at com6 for the TU 58 ..
I have down loaded TU58 v1.4i from AK6DN.. I tried to run it on my PC (Windows XP)..
It told me there was no file or could not open 1123_1.dsk..
I copied the commands from the other thread by SMP, and I have no idea if what I typed was correct or not..
And the Order of what needs to be Done..
While waiting for an answer, I put into Core at '001000 the code for Booting the TU58..
So, what do I do next ??
I Think I got it, the TU58em is dotting across the Screen..
I had to close my TeraTerm on port 6, then it worked..
About How Long Does it take for the "Dotting" to complete, in the -i and -z states ??
THANK YOU Marty
 
Last edited:
Marty, you would want to use a command that looks something like the first line in this code box:

Code:
E:\> tu58em -v -p 6 -s 9600 -r 11xxdp.dsk
info: unit 0 r    file '11xxdp.dsk'
info: serial port 6 at 9600 baud
info: TU58 emulation start
info: R restart, S toggle send init, V toggle verbose, D toggle debug, Q quit
info: emulator started

The bootable XXDP utility file '11xxdp.dsk' can be downloaded from here: http://www.ak6dn.dyndns.org/PDP-11/TU58/11xxdp.dsk

The -w -z -i -c options are not really useful for you at this point. You need to use a preexisting bootable image.

And yes you have to close any other program that is accessing the serial port BEFORE starting tu58em. Serial ports can only be opened by one application in windows.

Once you start tu58em it should print something like above, and then it will print dots. This indicates it is ready and waiting for communication from your PDP-11 to initiate the tu58 protocol. So at this point you should start the TU58 boot code you previously loaded into your PDP-11.

Code:
info: <INIT><INIT> seen, sending <CONT>
info: read     unit=0 sw=0x00 mod=0x00 blk=0x0000 cnt=0x0400

Once the PDP-11 and tu58em 'see' each other the above lines should be printed, indicating your CPU sent a boot request for unit zero. If all you continue to see is dots, it means your PDP-11 tu58 bootstrap is not running correctly, or you have some communication link error (wrong baud rate, not 8b mode, etc).

Don
 
Hi All;
Thank You, Don for Your reply..
As where I had downloaded from I didn't see any instructions, and in the postings by SMP it looked like He had already obtained the necessary files..
So, I was at a loss as to what to do.. I had gone to do other things and it had been "Dotting" for over an hour, and I thought something must be wrong here..
Where do I copy the file I just downloaded from you to ?? In the same Directory as I have TU58 .. I just want to make sure, I am doing it correctly..
I will unpack the file and move it, while awaiting an answer..
THANK YOU Marty
 
Hi All;
Don, It gives me an ERROR after I try to boot from the PDP 11/45..
It says Unknown Packet Flag 0X80 (.)
Info: Boot Unit =0 blk= 0X0000 cnt =0X0200
I found a Problem the Board (M7800) was set for 2 stop Bits.. I am changing this, to 1 Stop Bit..
That didn't change anything..
THANK YOU Marty
 
Last edited:
Hi All;
Don, After I start the TU58em and have the settings in place..
It never gives me any Dots..
It does say " Info: Emulator Started ''
THANK YOU Marty
 
Hi All;
Don, After I start the TU58em and have the settings in place..
It never gives me any Dots..
It does say " Info: Emulator Started ''
THANK YOU Marty

Can you capture a text log of the console session with tu58em starting from the command line you issued?

Without being able to see what you are doing, it is hard to comment on what to do next.

Don
 
Hi All;
Don, It gives me an ERROR after I try to boot from the PDP 11/45..
It says Unknown Packet Flag 0X80 (.)
Info: Boot Unit =0 blk= 0X0000 cnt =0X0200
I found a Problem the Board (M7800) was set for 2 stop Bits.. I am changing this, to 1 Stop Bit..
That didn't change anything..
THANK YOU Marty

Stop bits really should not matter. What is important is that the baud rate is correct, and you have the SLU setup in 8bit mode (not 7bit). The tu58 protocol requires 8b binary mode transfers.

Don
 
Hi All;
Don, I will try, but I don't know How to capture the "Dos Box"..
I got the "Dots" after Turning on the Debug Flag..
I will Recheck the Documentation and make sure it is set for 8 Bits, So I know for sure..
Other Wise I will need to switch the settings between the M7800 and the M7856..
THANK YOU Marty
 
Last edited:
Hi All;
Don, I will try, but I don't know How to capture the "box"..
I got the "Dots" after Turning on the Debug Flag..
THANK YOU Marty

If you are running tu58em in a cygwin (or msdos for that matter) command terminal window, you should be able to copy the text output and paste it here into a post. Once you paste it into the post, select the text and use the '#' option in the menu to put it in a 'code' box.

Don
 
Hi All;
Don, I rechecked it and It is set for 8 Bits, No Parity, 1 Stop Bit, and 9600 Baud..
""(or msdos for that matter) command terminal window, you should be able to copy the text output"" it will NOT let me copy the Text in my Msdos Box, (Command Prompt Box) in Windows XP..
THANK YOU Marty
 
Hi All;
Don, I rechecked it and It is set for 8 Bits, No Parity, 1 Stop Bit, and 9600 Baud..
""(or msdos for that matter) command terminal window, you should be able to copy the text output"" it will NOT let me copy the Text in my Msdos Box, (Command Prompt Box) in Windows XP..
THANK YOU Marty

For your MSDOS command box, right click in the box and 'select all', then hit enter. All the text in the window should have been copied. Paste into a text document (like Notepad), then just copy/paste the relevant stuff to this forum.

I've done this a number of times in XP so I know it can be done.

Don
 
Hi All;
Don, I rechecked it and It is set for 8 Bits, No Parity, 1 Stop Bit, and 9600 Baud..
""(or msdos for that matter) command terminal window, you should be able to copy the text output"" it will NOT let me copy the Text in my Msdos Box, (Command Prompt Box) in Windows XP.
THANK YOU Marty
Right click the little icon at the top left of the window. Choose "Select All"
and then right click the icon again and select "Copy" and then you can paste to a Notepad file.
 
Hi All;
Don, I believe You, But Right Clicking in My "Dos Box" Does Nothing..
I Just figured it out I have to get out of TU58em mode, then I can do a Right Click..
THANK YOU Don !!
I am modifying the Boards so I can Trade them and make the M7856 the tu58 emulator and the M7800 for terminal mode..
THANK YOU Marty
 
Hi All;
Don, and Everyone, It still did the same thing, after trading Boards.. The M7856 is for the TU58em and the M7800 is for the PDP Terminal..
I have checked with "Device Manager" and Both ports are set to 8 bits, 9600 Baud, No Parity, and 1 Stop Bit..
I have also Rechecked the Code in the PDP 11/45, and it is fine..

C:\PDP\tu58>tu58em -v -d -p 5 -s 9600 -r 11xxdp.dsk
info: unit 0 r file '11xxdp.dsk'
info: tu58 tape emulator v1.4i
info: (C) 2005-2013 Don North <ak6dn@mindspring.com>, (C) 1984 Dan Ts'o <Rockefe
ller University>
info: serial port 5 at 9600 baud
info: TU58 emulation start
info: R restart, S toggle send init, V toggle verbose, D toggle debug, Q quit
info: emulator started
................................................................................
......info: flag=0x80 last=0xFF (<-- BOOTED HERE, from PDP)
ERROR: unknown packet flag 0x80 (.)
info: flag=0x00 last=0x80
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x04 last=0x00
info: <INIT> seen
info: flag=0x08 last=0x04
info: <BOOT> seen
info: boot unit=0 blk=0x0000 cnt=0x0200
info: flag=0x00 last=0x08
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen

C:\PDP\tu58>

THANK YOU Marty
 
Last edited:
Code:
C:\PDP\tu58>tu58em -v -d -p 5 -s 9600 -r 11xxdp.dsk
info: unit 0 r file '11xxdp.dsk'
info: tu58 tape emulator v1.4i
info: (C) 2005-2013 Don North <ak6dn@mindspring.com>, (C) 1984 Dan Ts'o <Rockefe
ller University>
info: serial port 5 at 9600 baud
info: TU58 emulation start
info: R restart, S toggle send init, V toggle verbose, D toggle debug, Q quit
info: emulator started
.................................................. ..............................
......info: flag=0x80 last=0xFF (<-- BOOTED HERE, from PDP)
ERROR: unknown packet flag 0x80 (.)
info: flag=0x00 last=0x80
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen

That all looks about as expected, until you 'boot' the PDP. tu58em is not seeing what is expected from the PDP.

What 'boot' code are you using on the PDP side?

Post #3 in this thread: http://www.vintage-computer.com/vcforum/showthread.php?39285-Interface-to-TU58EM&highlight=tu58em has known working TU58 bootstrap code copied from the DEC TU58 v4 manual.

Don
 
Last edited:
Hi All;
Don, The Code that You reference IS Exactly the Code that I have in my PDP.. But, I will Recheck it again..

1000/012701
1002/176500
1004/012702
1006/176504
1010/010100
1012/005212
1014/105712
1016/100376
1020/006300
1022/001005
1024/005012
1026/012700
1030/000004
1032/005761
1034/000002
1036/042700
1040/000020
1042/010062
1044/000002
1046/001362
1050/005003
1052/105711
1054/100376
1056/116123
1060/000002
1062/022703
1064/001000
1066/101371
1070/005007

THANK YOU Marty
 
Hi All;
I have rechecked the code on the PDP and it is OK !!!!
I went and started to re-read thru the posing from SMP, that You reference and alot of what He is getting is the Same as what I am getting..
But here is a copy of something I can Try Just to see if it helps --

""What you could do is change the last word of the toggle in boot from 005007 (clr pc; jump to zero) to 000777 (br .; loop forever). Then execute the toggle in boot code sequence to read the boot block into memory. At the end of the process your CPU will 'hang' on the 'br .', and then we can go back to ODT and display memory locations 0 thru 511 to see if the boot block was read in correctly.

Don""
At this point it doesn't Hurt..
Also, Does anyOne have or would be willing to Write for me a Double Echo Program,, Where port 5's input, gets output to port 6, and port 6's input gets output to port 5..
That way I could see If Both are able to Talk to each Other..
At Present at address '000000 I have 000240
000002 000240
000004 000006
000006 000000
000010 000012
000012 000000
000014 000000
000016 000000
THANK YOU Marty
 
Hi All;
I have also Just tried it with port 1 and a straight serial cable, Same thing.. Before I had been using a USB to Serial Converter..
THANK YOU Marty
 
Here is a dump of the first block of the XXDP disk image, which is the boot block. This is what you should see starting at memory location zero.

I note that in location two you show 000240 (NOP) instead of 000440 (BR 104). Is this a typo?

If not, it is wrong and the bootstrap will die when it gets to location 6 which has a 000006 (RTT) in it.

Code:
0000000 000240 000440 000006 000000 000012 000000 000000 000000
0000020 000000 000000 000000 000000 000000 000000 000000 000000
0000040 000000 000000 000000 000000 000000 000000 000000 000000
0000060 000000 000000 000000 000000 005002 000002 000000 000000
0000100 001000 000010 012706 060000 000005 012703 000060 012702
0000120 000003 010123 005721 005302 001374 013746 000004 012737
0000140 000152 000004 005711 010113 000403 016713 177704 022626
0000160 012637 000004 012767 000010 177710 012704 001000 010067
0000200 177672 012746 000010 005003 005277 177650 004767 000350
0000220 005377 177640 012703 002004 005777 177626 004767 000334
0000240 005003 004767 000352 000303 122703 000020 001404 005316
0000260 001352 005726 000530 005726 005267 177606 022767 000050
0000300 177600 001006 016702 177564 016701 177544 000137 001046
0000320 004767 000226 005002 012700 000070 062002 005502 105301
0000340 001374 010210 004767 000202 012700 000070 012003 004767
0000360 000212 105301 100373 004767 000222 122703 000001 001022
0000400 010302 000303 110301 042701 177400 006201 004767 000174
0000420 010324 060302 005502 105301 001371 004767 000156 020302
0000440 001752 000442 122703 000002 001036 010302 000303 110301
0000460 042701 177400 106201 004767 000122 122703 000100 001023
0000500 005703 100421 060302 005502 105301 004767 000076 060302
0000520 005502 105301 001372 005703 100406 004767 000056 020302
0000540 001003 000167 177522 000000 000000 116701 177313 042701
0000560 177400 006201 005201 000207 004717 004717 004717 110377
0000600 177264 000303 105777 177254 100375 000207 005003 004717
0000620 105777 177234 100375 017705 177230 100745 150503 000303
0000640 000207 000000 000000 000000 000000 000000 000000 000000
 
Hi All;
Don, That Could have been a Mis-reading on my part, at location 2 I do have 440..
I have checked down to location '000660, and they all agree with what You have, EXCEPT for locations 60, 62, 64 and 66..
And they are Location '000060 has '177777, '000062 has '176510, '000064 has '176504 and Location '000066 has '176506..
Then Location '000070 '005002 and so on..
I could "zero" them out, and try a Reload..
THANK YOU Marty
 
Last edited:
Back
Top