13 Mar
2015
13 Mar
'15
11:12 p.m.
Hi All,
Long time reader, first time poster.
I am in need of some assistance in trying to revive an IBM 5100. It is a
Basic 32k version that was in rough shape. You can see pics here:
http://vintagecomputer.ca/ibm-5100-before/
I've been able to clean it up but when I fire it up I see a single "A" on
screen. I can't seem to get into any diagnostic modes. The single "A"
indicates an issue with the F2 Base I/O card. Some of the ICs do have some
rust on them but I'm wondering if it might be the "bridge connectors"
between the Base I/O and Controller (CPU) card. Are they directional or
can then be swapped or turned around? I may have not kept them in the
correct orientation but I don't see any mention in the Maintenance manual.
I, pretty much, need someone who has one to take a picture of the top of
their Base I/O and Controller cards.
Any help is much appreciated. If someone happens to know a common issue
that would make the "Bring up Program" stop at A, I'd love to hear about
it.
Thanks in advance,
Santo
14 Mar
14 Mar
5:09 a.m.
Santo,
This is the first time I am seeing the "5106". Is that an external tape drive
for the 5100?
-Ali
7:37 a.m.
Congrats, Santo - and my best wishes for your project.
I feel like I can speak for many of us, when I say "Thank you" for taking
interest in this old machine. Please do your best to document your
experience with it, and I'm sure that we'll all (including posterity)
appreciate your efforts!
On Sat, Mar 14, 2015 at 12:09 AM, Ali <cctalk at fahimi.net> wrote:
Santo,
This is the first time I am seeing the "5106". Is that an external tape
drive for the 5100?
-Ali
2:12 p.m.
Thank you but no need for thanks. If I did that for every wonderful
restoration project I've read about, we would need a listserv just for that
(not to mention great websites with helpful tips for us hobby restorers) :)
For this particular project, thanks should go out to those archiving
documentation like the IBM 5100 Maintenance manual that gives me the proper
tools to even attempt this.
Santo
On Sat, Mar 14, 2015 at 3:37 AM, drlegendre . <drlegendre at gmail.com> wrote:
Congrats, Santo - and my best wishes for your
project.
I feel like I can speak for many of us, when I say "Thank you" for taking
interest in this old machine. Please do your best to document your
experience with it, and I'm sure that we'll all (including posterity)
appreciate your efforts!
On Sat, Mar 14, 2015 at 12:09 AM, Ali <cctalk at fahimi.net> wrote:
Santo,
This is the first time I am seeing the "5106". Is that an external tape
drive for the 5100?
-Ali
2:03 p.m.
Yes, it is an external tape drive that is very similar to the internal
drive. I'm guessing it was touted as doubling the "mass storage" for the
5100 but it was probably used for backups. Unfortunately, I don't have any
tapes or documentation and thee is supposed to be a supplemental tape that
had the utility to make backup tapes.
I'll take some more pics when I clean it up. I've only ever seen a picture
of the front online.
There are a few examples out there but it is not common.
On Sat, Mar 14, 2015 at 1:09 AM, Ali <cctalk at fahimi.net> wrote:
Santo,
This is the first time I am seeing the "5106". Is that an external tape
drive for the 5100?
-Ali
15 Mar
15 Mar
7:12 p.m.
Yes, it is an external tape drive that is very similar
to the internal
drive. I'm guessing it was touted as doubling the "mass storage" for
the
5100 but it was probably used for backups. Unfortunately, I don't have
any tapes or documentation and thee is supposed to be a supplemental
tape that had the utility to make backup tapes.
That is very cool. As far as tapes are concerned any std. DC300 or DC600 tape should work.
However, make sure to check for gooified insides on both tape drive mechanisms. I did some
googlefu and found the following which may help you:
http://computermuseum.informatik.uni-stuttgart.de/dev/ibm_5110/technik/en/5…
Not much but a starting point.
I'll take some more pics when I clean it up. I've only ever seen a
picture of the front online.
That would be great. Even if you can't get it up and running at least we would have
some records for posterity.
Congrats on your find! Those machines are rare and when they come up they always sell for
way more than I am ready to spend!
-Ali
17 Mar
17 Mar
12:45 p.m.
Update: Unfortunately, I think I'm at a dead end. After cleaning
everything up, I am still at the "A" in the "Bring Up" program that
isn't
very far but it's better than garbage. I removed both memory cards and get
garbage so the memory cards might be working (I have two and tried both
individually). I think my problem is in the "Basic I/O" card as indicated
in the Maintenance manual. I am also not able to get into the Diagnostics
screen because it must be failing too early. Either that or my keyboard
isn't working. It's hard to tell.
I'd be happy to try to replace some of the logic chips but IBM uses their
own numbering scheme. Does anyone know of a way to read them? I assume
they are normal logic chips but with IBM numbering in most cases?
Ali, thanks for the link. I did look over that document a while ago but
the Maintenance manual is also very thorough in regards to the 5106 tape
drive both internally and as an external unit. The rollers look great and
hard in both the internal and external unit but I obviously can't test out
either at this point.
Anyway, I did clean it up and took some more pictures to document where
the cards go. Thanks to Dave Dunfield's IBM 5100 site, I was able to
figure it out. Much appreciated Dave! I have also taken pictures of my
cards and where they go.
You can find new pictures here:
http://vintagecomputer.ca/ibm-5100-in-pictures/
On Sun, Mar 15, 2015 at 3:12 PM, Ali <cctalk at fahimi.net> wrote:
Yes, it is an
external tape drive that is very similar to the internal
drive. I'm guessing it was touted as doubling the "mass storage" for
the
5100 but it was probably used for backups. Unfortunately, I don't have
any tapes or documentation and thee is supposed to be a supplemental
tape that had the utility to make backup tapes.
That is very cool. As far as tapes are concerned any std. DC300 or DC600
tape should work. However, make sure to check for gooified insides on both
tape drive mechanisms. I did some googlefu and found the following which
may help you:
http://computermuseum.informatik.uni-stuttgart.de/dev/ibm_5110/technik/en/5…
Not much but a starting point.
I'll take some more pics when I clean it up. I've only ever seen a
picture of the front online.
That would be great. Even if you can't get it up and running at least we
would have some records for posterity.
Congrats on your find! Those machines are rare and when they come up they
always sell for way more than I am ready to spend!
-Ali
8:36 p.m.
On Tue, Mar 17, 2015 at 08:45:49AM -0400, Santo Nucifora wrote:
Update: Unfortunately, I think I'm at a dead end.
After cleaning
everything up, I am still at the "A" in the "Bring Up" program that
isn't
very far but it's better than garbage.
Well, you've gotten farther than I ever did. I've had one of these, or a
similar model, for a couple of decades or so. I was at a friend's house one
day and saw it out on their front porch. They were tossing it. They said
one of their kids picked it up somewhere. They also claimed that they had
it checked at Radio Shack and it only needed an inexpensive part. Anyway, I
saved it and its printer from being tossed. It wouldn't power up at all.
I'm not a hardware person, and never found the right tools to open it up.
Sadly it got left at my parents place along with some other stuff when I
moved up to the area I'm in now. When I went to collect said stuff I found
the computer and its printer outside in a wheel barrel, with its power cord
cut off. My father claims I told him it was "junk." Aaaaaarrrrrrrrggggggg!!
It had been rained on, and there was standing water in the wheel barrel.
The printer was so rusted up I tossed it. I wish now I'd kept it even if it
was too far gone to save. I still have the 5100, or whatever model it is.
In case the previous torture it endured wasn't enough it's been out in my
garage for years. I probably don't want to know what shape it's in
internally.
--
Kevin
http://www.RawFedDogs.net
http://www.Lassie.xyz
http://www.WacoAgilityGroup.org
Bruceville, TX
What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
9:59 p.m.
On Tue, Mar 17, 2015 at 03:36:52PM -0500, Kevin Monceaux wrote:
I've had one of these, or a similar model, for a
couple of decades or so.
I just got home and checked. What I have is a similar model - a 5110. Mine
appears to be a model 2 without internal tape or floppy drives.
--
Kevin
http://www.RawFedDogs.net
http://www.Lassie.xyz
http://www.WacoAgilityGroup.org
Bruceville, TX
What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
18 Mar
18 Mar
10:50 a.m.
I wonder if the cards are interchangeable with a 5100...
Santo
On Tue, Mar 17, 2015 at 5:59 PM, Kevin Monceaux <Kevin at rawfeddogs.net>
wrote:
On Tue, Mar 17, 2015 at 03:36:52PM -0500, Kevin
Monceaux wrote:
I've had one of these, or a similar model,
for a couple of decades or so.
I just got home and checked. What I have is a similar model - a 5110.
Mine
appears to be a model 2 without internal tape or floppy drives.
--
Kevin
http://www.RawFedDogs.net
http://www.Lassie.xyz
http://www.WacoAgilityGroup.org
Bruceville, TX
What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
12:25 p.m.
On Wed, Mar 18, 2015 at 06:50:13AM -0400, Santo Nucifora wrote:
I wonder if the cards are interchangeable with a
5100...
The Wikipedia 5110 article says the 5110 is partially incompatible with the
5100. Unfortunately that's the extent of my knowledge on the subject. I
don't know if any of its cards are interchangeable with a 5100 or not.
--
Kevin
http://www.RawFedDogs.net
http://www.Lassie.xyz
http://www.WacoAgilityGroup.org
Bruceville, TX
What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
10:27 a.m.
On Tue, 17 Mar 2015, Santo Nucifora wrote:
Update: Unfortunately, I think I'm at a dead end.
After cleaning
everything up, I am still at the "A" in the "Bring Up" program that
isn't
very far but it's better than garbage. I removed both memory cards and get
garbage so the memory cards might be working (I have two and tried both
individually). I think my problem is in the "Basic I/O" card as indicated
in the Maintenance manual. I am also not able to get into the Diagnostics
screen because it must be failing too early. Either that or my keyboard
isn't working. It's hard to tell.
What you don't say is whether the machine just halts, or stops with a
machine check.
Here's the relevant part of the Bring Up test 'A' from the 5110. Since I
still haven't got a 5100 I can't verify what the 5100 does, but I suspect
that it must be quite similar at this point.
[...]
; --- Test A ---
; Bus In bit test
0078 251E MOVE R5, $3C
007A 81C1 LBI R1, #'A'
007C 7150 MOVB (R5)+, R1
007E 8FFF LBI R15, #$FF
0080 00FE GETB R15, $0
0082 CF04 SS R15
0084 0000 HALT
[...]
So essentially, the routine reads the byte from I/O device 0 (the
processor or display adapter card) and halts if it isn't $FF.
You should be able to check what R15 contains after the halt by switching
to the register display.
According to the 5100 MIM, the 'A' routine is described as "Test bus in
for the ability to turn all bits on". So apparently you have a stuck bit.
Are you shure that you don't have any external devices attached to the
machine? And check the top connectors and all the jumpers.
Then you might find the stuck bus in bit with a scope/logic probe by
probing the external connector A2.
I'd be happy to try to replace some of the logic
chips but IBM uses their
own numbering scheme. Does anyone know of a way to read them? I assume
they are normal logic chips but with IBM numbering in most cases?
The normal "black" TTL ICs, yes, they are standard ICs. For a (incomplete)
list, have a look at our FTP server at /pub/cm/ibm/ibmparts.txt
You can find new pictures here:
http://vintagecomputer.ca/ibm-5100-in-pictures/
One note: the terminator box is only needed when you use the 5106 drive
*without* the 5103 printer, because the printer has a terminator built in
and thus must be the last device in the chain.
Christian
10:58 a.m.
Hi Christian,
Thank you for the reply. I think I mentioned the machine halts or my
keyboard doesn't work or it's not far enough in the Bring Up test to allow
the Diagnostics to come up with the special key sequence. This is new
territory for me so I'm not sure if input is accepted at that point.
Where did you find the code for the Bring Up tests? I would love to have a
look. The 5100 Maintenance manual is not very specific and certainly
doesn't have code in it (unless I missed it).
My registers looks like this:
You'll notice that the first two characters in second line is not right.
Sadly, it's gotten a little worse after taking this picture so lines 5 and
6 have some garbling of the dots. Since I was seeing text, I didn't suspect
the display card right away (again, not knowing the machine) but it may be
bad RAM on the display card.
I'll refer to your IBMparts.txt file and see what is on that card. If you
do see anything else in the registers, I'd be very happy to hear your
thoughts.
Thank you! I now have renewed hope.
Santo
On Wed, Mar 18, 2015 at 6:27 AM, Christian Corti <
cc at informatik.uni-stuttgart.de> wrote:
On Tue, 17 Mar 2015, Santo Nucifora wrote:
Update: Unfortunately, I think I'm at a dead
end. After cleaning
everything up, I am still at the "A" in the "Bring Up" program that
isn't
very far but it's better than garbage. I removed both memory cards and
get
garbage so the memory cards might be working (I have two and tried both
individually). I think my problem is in the "Basic I/O" card as indicated
in the Maintenance manual. I am also not able to get into the Diagnostics
screen because it must be failing too early. Either that or my keyboard
isn't working. It's hard to tell.
What you don't say is whether the machine just halts, or stops with a
machine check.
Here's the relevant part of the Bring Up test 'A' from the 5110. Since I
still haven't got a 5100 I can't verify what the 5100 does, but I suspect
that it must be quite similar at this point.
[...]
; --- Test A ---
; Bus In bit test
0078 251E MOVE R5, $3C
007A 81C1 LBI R1, #'A'
007C 7150 MOVB (R5)+, R1
007E 8FFF LBI R15, #$FF
0080 00FE GETB R15, $0
0082 CF04 SS R15
0084 0000 HALT
[...]
So essentially, the routine reads the byte from I/O device 0 (the
processor or display adapter card) and halts if it isn't $FF.
You should be able to check what R15 contains after the halt by switching
to the register display.
According to the 5100 MIM, the 'A' routine is described as "Test bus in
for the ability to turn all bits on". So apparently you have a stuck bit.
Are you shure that you don't have any external devices attached to the
machine? And check the top connectors and all the jumpers.
Then you might find the stuck bus in bit with a scope/logic probe by
probing the external connector A2.
I'd be happy to try to replace some of the logic chips but IBM uses their
own numbering scheme. Does anyone know of a way
to read them? I assume
they are normal logic chips but with IBM numbering in most cases?
The normal "black" TTL ICs, yes, they are standard ICs. For a (incomplete)
list, have a look at our FTP server at /pub/cm/ibm/ibmparts.txt
You can find new pictures here:
One note: the terminator box is only needed when you use the 5106 drive
*without* the 5103 printer, because the printer has a terminator built in
and thus must be the last device in the chain.
Christian
11:54 a.m.
On Wed, 18 Mar 2015, Santo Nucifora wrote:
Where did you find the code for the Bring Up tests? I
would love to have a
look. The 5100 Maintenance manual is not very specific and certainly
doesn't have code in it (unless I missed it).
I disassembled it myself. You can find the disassembly on our FTP server,
too: ftp.informatik.uni-stuttgart.de/pub/cm/ibm/ibm5100/execros.asm
But as mentioned, all information refer to the 5110.
My registers looks like this:
I don't see anything... was that an attachement or inline picture?
You'll notice that the first two characters in
second line is not right.
They are absulutely right! This means that the processor is running
(executing a halt instruction that in reality is a jump to itself). What
you are seeing is the program counter (register R0) changing. I you put
the machine into single-step mode (there's a switch in the machine under
the cover) you can step the instructions one-by-one.
Sadly, it's gotten a little worse after taking
this picture so lines 5 and
6 have some garbling of the dots. Since I was seeing text, I didn't suspect
If all other characters are ok, what you describe as garbling are just
changing data bytes.
the display card right away (again, not knowing the
machine) but it may be
bad RAM on the display card.
I wouldn't suspect the display card, too.
I'll refer to your IBMparts.txt file and see what
is on that card. If you
do see anything else in the registers, I'd be very happy to hear your
thoughts.
Could you put the picture on your web site or send me an email? And please
also make the following readable screenshot:
1. Put the machine into single-step mode
2. Press RESTART
3. Switch to DISPLAY REGISTERS
4. Make photo
This is the hex dump of the first 512 bytes of the Executable ROS. At
least that's how it works on the 5110.
Christian
12:05 p.m.
Sorry about that. Here's the registers:
http://vintagecomputer.ca/wp-content/uploads/2015/03/IBM-5100-Register-disp…
It was an inline image and I can still see it when I look a the email I
sent :) That's a direct link.
The display of registers is consistent from first start up and through
restarts.
I did want to thank you also for the terminator clarification. I changed
my page. I also looked at the IBMparts.txt reference chart. That's
exactly what I needed. I do have some rusty logic chips that cleaned up
decently but I don't trust them exactly since the previous owner turned
this computer on with the rust bridging pins. He claimed it worked with
the Register screen on. I knew otherwise. All of the "cans" looked good
though.
Thanks again. I do need to look at the Maintenance manual when I get home
to line up the registers and see if $FF is in the right one but you can
probably tell that pretty quickly with the picture.
Thanks for looking.
Santo
On Wed, Mar 18, 2015 at 7:54 AM, Christian Corti <
cc at informatik.uni-stuttgart.de> wrote:
On Wed, 18 Mar 2015, Santo Nucifora wrote:
I don't see anything... was that an attachement or inline picture?
You'll notice that the first two characters in second line is not right.
They are absulutely right! This means that the processor is running
(executing a halt instruction that in reality is a jump to itself). What
you are seeing is the program counter (register R0) changing. I you put the
machine into single-step mode (there's a switch in the machine under the
cover) you can step the instructions one-by-one.
Sadly, it's gotten a little worse after taking this picture so lines 5 and
> 6 have some garbling of the dots. Since I was seeing text, I didn't
> suspect
If all other characters are ok, what you describe as garbling are just
changing data bytes.
the display card right away (again, not knowing the machine) but it may be
> bad RAM on the display card.
I wouldn't suspect the display card, too.
I'll refer to your IBMparts.txt file and see what is on that card. If
> you
> do see anything else in the registers, I'd be very happy to hear your
> thoughts.
Could you put the picture on your web site or send me an email? And please
also make the following readable screenshot:
1. Put the machine into single-step mode
2. Press RESTART
3. Switch to DISPLAY REGISTERS
4. Make photo
This is the hex dump of the first 512 bytes of the Executable ROS. At
least that's how it works on the 5110.
Christian
Where did you find the code for the Bring Up
tests? I would love to have
a
look. The 5100 Maintenance manual is not very specific and certainly
doesn't have code in it (unless I missed it).
I disassembled it myself. You can find the disassembly on our FTP server,
too: ftp.informatik.uni-stuttgart.de/pub/cm/ibm/ibm5100/execros.asm
But as mentioned, all information refer to the 5110.
My registers looks like this:
3:43 p.m.
Hi Christian,
execros.asm
<http://ftp.informatik.uni-stuttgart.de/pub/cm/ibm/ibm5100/execros.asm> doesn't
exist on the ftp server. If you could send it to me off-line, I would
appreciate it. I know it's different but it should be similar enough to
that point, I would think.
Thanks,
Santo
On Wed, Mar 18, 2015 at 7:54 AM, Christian Corti <
cc at informatik.uni-stuttgart.de> wrote:
On Wed, 18 Mar 2015, Santo Nucifora wrote:
I don't see anything... was that an attachement or inline picture?
You'll notice that the first two characters in second line is not right.
They are absulutely right! This means that the processor is running
(executing a halt instruction that in reality is a jump to itself). What
you are seeing is the program counter (register R0) changing. I you put the
machine into single-step mode (there's a switch in the machine under the
cover) you can step the instructions one-by-one.
Sadly, it's gotten a little worse after taking this picture so lines 5 and
> 6 have some garbling of the dots. Since I was seeing text, I didn't
> suspect
If all other characters are ok, what you describe as garbling are just
changing data bytes.
the display card right away (again, not knowing the machine) but it may be
> bad RAM on the display card.
I wouldn't suspect the display card, too.
I'll refer to your IBMparts.txt file and see what is on that card. If
> you
> do see anything else in the registers, I'd be very happy to hear your
> thoughts.
Could you put the picture on your web site or send me an email? And please
also make the following readable screenshot:
1. Put the machine into single-step mode
2. Press RESTART
3. Switch to DISPLAY REGISTERS
4. Make photo
This is the hex dump of the first 512 bytes of the Executable ROS. At
least that's how it works on the 5110.
Christian
Where did you find the code for the Bring Up
tests? I would love to have
a
look. The 5100 Maintenance manual is not very specific and certainly
doesn't have code in it (unless I missed it).
I disassembled it myself. You can find the disassembly on our FTP server,
too: ftp.informatik.uni-stuttgart.de/pub/cm/ibm/ibm5100/execros.asm
But as mentioned, all information refer to the 5110.
My registers looks like this:
4:23 p.m.
On Wed, 18 Mar 2015, Santo Nucifora wrote:
execros.asm
<http://ftp.informatik.uni-stuttgart.de/pub/cm/ibm/ibm5100/execros.asm>
doesn't
exist on the ftp server. If you could send it to me off-line, I would
Sorry, there's a typo: .../ibm/ibm5110/... (instead of 5100). And use FTP
as I said, so just change http:// with ftp:// or use a FTP client.
BTW I had a look at your screen shot. The register contents is as follows:
R0 - varying around $0090
R1 - $0090
R2 - $0000
R3 - $0600
R4 - $0006
R5 - $0202
R6 - $0005
R7 - $05C0
R8 - $00C0
R9..R14 - $0000
R15 - $0005
R13L1 - $7FFF (last RWS address? Do you have 32kB in your machine?)
If your machine really halts at stop 'A', then this is strange. R5 should
contain the screen address for the next character. $0202 should be for the
'C', so the machine might hang at stop 'B'. R15 should contain $00FF.
Having R1 with $0090 implies a negative test instruction at $008C with the
halt instruction at $008E. (R1 is used as link register with conditional
skip instructions. If no skip occurs, the next instruction can be a jump
to a subroutine, and R1 contains the address of the instruction following
that jump. This is automatically done by the CPU).
R3 and R4 might contain the end values after the screen clear routine
(just before the 'A' routine). The 5110 version looks like this:
; Clear display
006C 8F40 LBI R15, #' '
006E 0FFD MLH R15, R15
0070 8D06 LBI R13, #$06
0072 5F51 MOVE (R5)+, R15
0074 C5D7 SBSH R5, R13
0076 F005 BRA $0072 ; -> -$06(R0)
And the 5100 version could be something like this:
8200 LBI R2, #' '
022D MLH R2, R2 ; R2 <- $0000
8406 LBI R4, #$06 ; R4 <- $0006
5231 MOVE (R3)+, R2
C347 SBSH R3, R4
F005 BRA $-6
The screen is cleared from $0200 (begin of screen) up to (excluding) $0600
(end of screen). So R3 contains the address of the first byte after the
screen area.
But to find out what the machine did until this point, I need the
Executable ROS hex dump as described in my last post. Address 0090 is well
within the first 512 bytes so we should get the first couple of diagnostic
routines.
Christian
19 Mar
19 Mar
12:22 p.m.
Hi Christian,
Thank you, I did find the dump yesterday and to answer your question, I do
have 32k of memory (two 16k boards).
It is my understanding that if an A gets printed, the A test completed
successfully and it is dying at the B test where the last part of the test
is to print the letter B on screen.
We certainly need a hex dump for the 5100 but I've looked around and found
nothing. I don't suppose I can dump my Executable ROS in the condition my
machine is in.
Is there a list of the Assembler opcodes I can reference?
Thanks again for your help,
Santo
On Wed, Mar 18, 2015 at 12:23 PM, Christian Corti <
cc at informatik.uni-stuttgart.de> wrote:
On Wed, 18 Mar 2015, Santo Nucifora wrote:
execros.asm
<http://ftp.informatik.uni-stuttgart.de/pub/cm/ibm/ibm5100/execros.asm>
doesn't
exist on the ftp server. If you could send it to me off-line, I would
Sorry, there's a typo: .../ibm/ibm5110/... (instead of 5100). And use FTP
as I said, so just change http:// with ftp:// or use a FTP client.
BTW I had a look at your screen shot. The register contents is as follows:
R0 - varying around $0090
R1 - $0090
R2 - $0000
R3 - $0600
R4 - $0006
R5 - $0202
R6 - $0005
R7 - $05C0
R8 - $00C0
R9..R14 - $0000
R15 - $0005
R13L1 - $7FFF (last RWS address? Do you have 32kB in your machine?)
If your machine really halts at stop 'A', then this is strange. R5 should
contain the screen address for the next character. $0202 should be for the
'C', so the machine might hang at stop 'B'. R15 should contain $00FF.
Having R1 with $0090 implies a negative test instruction at $008C with the
halt instruction at $008E. (R1 is used as link register with conditional
skip instructions. If no skip occurs, the next instruction can be a jump to
a subroutine, and R1 contains the address of the instruction following that
jump. This is automatically done by the CPU).
R3 and R4 might contain the end values after the screen clear routine
(just before the 'A' routine). The 5110 version looks like this:
; Clear display
006C 8F40 LBI R15, #' '
006E 0FFD MLH R15, R15
0070 8D06 LBI R13, #$06
0072 5F51 MOVE (R5)+, R15
0074 C5D7 SBSH R5, R13
0076 F005 BRA $0072 ; -> -$06(R0)
And the 5100 version could be something like this:
8200 LBI R2, #' '
022D MLH R2, R2 ; R2 <- $0000
8406 LBI R4, #$06 ; R4 <- $0006
5231 MOVE (R3)+, R2
C347 SBSH R3, R4
F005 BRA $-6
The screen is cleared from $0200 (begin of screen) up to (excluding) $0600
(end of screen). So R3 contains the address of the first byte after the
screen area.
But to find out what the machine did until this point, I need the
Executable ROS hex dump as described in my last post. Address 0090 is well
within the first 512 bytes so we should get the first couple of diagnostic
routines.
Christian
2:51 p.m.
On Thu, 19 Mar 2015, Santo Nucifora wrote:
It is my understanding that if an A gets printed, the
A test completed
successfully and it is dying at the B test where the last part of the test
is to print the letter B on screen.
No, first the letter is printed, then the test is started.
We certainly need a hex dump for the 5100 but I've
looked around and found
nothing. I don't suppose I can dump my Executable ROS in the condition my
machine is in.
Shure you can, please just do what I told you. Make a screenshot with
your camera of the first 512 bytes of the Executable ROS:
> Could you put the picture on your web site or send
me an email? And
> please also make the following readable screenshot:
> 1. Put the machine into single-step mode
> 2. Press RESTART
> 3. Switch to DISPLAY REGISTERS
> 4. Make photo
I don't have any further clue without that screenshot.
Is there a list of the Assembler opcodes I can
reference?
Ehm, you did have a look at our web site, don't you?
http://computermuseum.informatik.uni-stuttgart.de/dev_en/ibm_5110/technik/e…
Navigate to "Programming in machine language --> Opcodes"
Christian
8:21 p.m.
Hi Christian,
Sorry, I missed the "Single Step" mode line and thought you just wanted the
registers.
Screenshot is here:
http://vintagecomputer.ca/wp-content/uploads/2015/01/exeros-5100.jpg
After trying single step mode, I'm in an endless loop and not actually
halted, it seems.
Do let me know what you think.
Santo
On Thu, Mar 19, 2015 at 10:51 AM, Christian Corti <
cc at informatik.uni-stuttgart.de> wrote:
On Thu, 19 Mar 2015, Santo Nucifora wrote:
Ehm, you did have a look at our web site, don't you?
http://computermuseum.informatik.uni-stuttgart.de/
dev_en/ibm_5110/technik/en/5110.html
Navigate to "Programming in machine language --> Opcodes"
Christian
It is my understanding that if an A gets printed,
the A test completed
successfully and it is dying at the B test where the last part of the test
is to print the letter B on screen.
No, first the letter is printed, then the test is started.
We certainly need a hex dump for the 5100 but I've looked around and found
nothing. I don't suppose I can dump my
Executable ROS in the condition my
machine is in.
Shure you can, please just do what I told you. Make a screenshot with your
camera of the first 512 bytes of the Executable ROS:
Could you put the picture on your web site or
send me an email? And
I don't have any further clue without that screenshot.
Is there a list of the Assembler opcodes I can reference?
please also make the following readable
screenshot:
1. Put the machine into single-step mode
2. Press RESTART
3. Switch to DISPLAY REGISTERS
4. Make photo
8:38 p.m.
Transcribed but not proofread:
00001f800202805380c4f08408807868c0a18808807868c0a08c08807868c008
0400ff202d343821423707808d8088141c0b808d8088141c0d808d808814148d
c0001f1f038a038280078f8001830001800202818053c4f0318c098858c08ea1
840000ff523a3d40757d7f141d162304202d3432462137058d708480919c9f90
09c7f0758f0fc0007531a08f318031800101e3a8730163e403d3f7530663d353
9d820d50ff0ef400505c031f1f111e101d300d323121430d46535f5453768788
07d3b00367e505530ae2d3e90967099508eb30f0200d0c0b0085cfcf00cfcff0
27987778a80fa9a82a0e980c9bb88c8ab50c3cc2d7e4e8e8f4f6eae200e1e901
cfcff0c0c000c0c000cfcf00c5c500cccc002121847580a031c1f921c0fa8075
e8e001e3eb00e4ec00ede500eee600e7ef002e5c502812202e28073f330a5350
8001858102835113007580018b31a132a43315858105848200a000a0cb807ea0
111d10202d2028000050141d1a1017101b100450dae4e0b5a4adc4d0dad1d8a3
8f0a0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c0f0c
ff040e041e042e043e044e045e046e047e048e049e04ae04be04ce04de04ee04
0f807e75121d1f7515a0c0f01175218a8004808001830001a02531131f800580
fed0d850faf5ff5040f0f40542507d3a465d40141d16230403141d04ff525d59
20 Mar
20 Mar
9:37 a.m.
On Thu, 19 Mar 2015, Santo Nucifora wrote:
Screenshot is here:
http://vintagecomputer.ca/wp-content/uploads/2015/01/exeros-5100.jpg
Ok, here we go:
0000 0004 DW 0004 ; R0L0
0002 0000 DW 0000 ; R1L0
; ----------------------------------------------------------------------
; Clear memory from $0008 to $01FF
0004 1FFF CTRL $F, #$FF ; Reset all devices
0006 8200 LBI R2, #$00
0008 022D MLH R2, R2 ; R2 <- $0000
000A 0324 MOVE R3, R2
000C 8308 LBI R3, #$08 ; R3 <- $0008
000E 5231 MOVE (R3)+, R2
0010 8402 LBI R4, #$02
0012 C347 SBSH R3, R4
0014 F007 BRA $000E ; Loop
; R3 contains now $0200
; Size installed memory in increments of 16 kbytes
; The last usable memory location will be in R8
; Check if memory at $4000 is present
0016 8840 LBI R8, #$40
0018 088D MLH R8, R8
001A 8800 LBI R8, #$00 ; R8 <- $4000
001C 7888 MOVB (R8), R8 ; ($4000) <- $00
001E 6184 MOVB R1, (R8)-
0020 C10C SNS R1 ;
0022 A01B BRA $0040 ; no memory here, jump
; Check if memory at $8000 is present
0024 8880 LBI R8, #$80
0026 088D MLH R8, R8
0028 8800 LBI R8, #$00
002A 7888 MOVB (R8), R8
002C 6184 MOVB R1, (R8)-
002E C10C SNS R1
0030 A00D BRA $0040 ; no memory here, jump
; Check if memory at $C000 is present
0032 88C0 LBI R8, #$C0
0034 088D MLH R8, R8
0036 8800 LBI R8, #$00
0038 7888 MOVB (R8), R8
003A 6184 MOVB R1, (R8)-
003C C104 SS R1 ; no memory here, skip
003E 088D MLH R8, R8 ; last location is $FFFF
0040 C804 SS R8
0042 0000 HALT ; error, low byte not $FF
0044 10F0 CTRL $0, #$F0
0046 1FFF CTRL $F, #$FF ; Reset all devices
0048 0532 INC R5, R3 ; R5 <- $0201
004A 83AA LBI R3, #$AA
004C 033D MLH R3, R3 ; R3 <- $AAAA
004E 8420 LBI R4, #$20
0050 8705 LBI R7, #$05
0052 077D MLH R7, R7
0054 87FF LBI R7, #$FF ; R7 <- $05FF
0056 8104 LBI R1, #$04
0058 011D MLH R1, R1
005A 8136 LBI R1, #$36 ; R1 <- $0436
005C 0203 INC2 R2, R0
005E 0014 RET R1 ; call $0436
; Clear memory from R9L0 to end of display
0060 8200 LBI R2, #$00
0062 022D MLH R2, R2 ; R2 <- $0000
0064 0324 MOVE R3, R2
0066 8312 LBI R3, #$12 ; R3 <- $0012
0068 8406 LBI R4, #$06
006A 5231 MOVE (R3)+, R2
006C C347 SBSH R3, R4
006E F005 BRA $006A ; loop
0070 381D MOVE $3A, R8 ; last memory location to
R13L1
; Put 0000, 1111, 2222, ... into locations $0080-00BF
; This is an aid to locate the registers in display
; register mode
0072 87C0 LBI R7, #$C0
0074 0894 MOVE R8, R9
0076 8880 LBI R8, #$80 ; R8 <- $0080
0078 5981 MOVE (R8)+, R9
007A C90C SNS R9
007C 89EF LBI R9, #$EF
007E A910 ADD R9, #$11
0080 099D MLH R9, R9
0082 C872 SE R8, R7
0084 F00D BRA $0078 ; -> -$0E(R0)
; --- Test A ---
; Bus In bit test
0086 7550 MOVB (R5)+, R5 ; write 'A' to $0201
0088 8FFF LBI R15, #$FF
008A 00FE GETB R15, $0
008C CF04 SS R15
008E 0000 HALT
; --- Test B ---
; Op Code test
0090 7550 MOVB (R5)+, R5 ; write 'B' to $0202
0092 351C MOVE $38, R5 ; save R5 to R12L1
0094 A003 BRA $009A
0096 81FF LBI R1, #$FF
0098 311F MOVE $3E, R1
009A 8101 LBI R1, #$01
[...]
So everything looks perfect, except that test 'A' fails. R15 should
contain $00FF after the 'GETB R15, $0', but instead it contains $0005.
Now, that's many bits stuck at zero... (the Bus In lines are active high).
Is there any difference in the value if you run the machine with
terminator (directly attached to the computer) and without terminator?
Are all power cables correctly seated? Somehow I have the impression that
the internal terminator or pullups on the Bus In lines don't work as they
should. Or the input receivers (whatever they are) are toast for 6 out of
8 lines.
According to the 5100 MIM page C-9, a GETB with address 0 is not used, so
should read $FF. Hmm, another thought: Maybe there's an addressing error,
and instead of addressing device 0, it addresses e.g. device 1. You should
definitely also check the DA (device address) lines.
Christian
5:24 p.m.
First off, thank you for disassembling the 5100 Executable ROS.
I just saw the link to your website and I can say I lived there for a
while. I first saw this 5100 for sale back in April 2014 and I agreed to
buy from the seller at that time, During that time I looked for any
information I could find on the 5100 and read every word of your site. It
didn't make much sense to me because you have to experience the true
hardware first but I appreciated it anyway. It took me just under a year
of patience to get the seller to complete the deal (I think he was worried
about shipping to another country) but it's here now so thank you for your
site. If I can get mine to work, maybe I can help make a 5100 version of
your emulator :)
Early on I tried with the terminator but my I/O cable driver card had
severely rusted ICs. I will try again with the terminator and see if there
is a difference.
I am writing this down for what I am going to check when I get home:
1. Check with terminator
2: Check bus lines as indicated in the IBM 5100 Maintenance manual
Page 3-14:
*Halt code: A*
*Test: Turns all bus in bits on*
*Area tested: A2*, F2, G2, H2*
*Service Aids: Probe the 'bus in' lines on the F2 card. All bus in bits
should be up or pulsing.*
Note: F2 = Base I/O board (525 - 528)
Page 5-22 to 5-25 = Base I/O card F2 logic and wiring
Page 5-24 bottom has references to Bus In lines but I wouldn't know where
to begin probing them.
Your site mentions the A2 connector which is referred to on page 5-15 at
the bottom. I can check that.
Thank you once again and if you can post the full disassembly, I would
appreciate that. If I am able to get past this, I'm fairly certain I won'
t be sailing through the rest of the tests.
Santo
On Fri, Mar 20, 2015 at 5:37 AM, Christian Corti <
cc at informatik.uni-stuttgart.de> wrote:
On Thu, 19 Mar 2015, Santo Nucifora wrote:
Screenshot is here:
http://vintagecomputer.ca/wp-content/uploads/2015/01/exeros-5100.jpg
Ok, here we go:
0000 0004 DW 0004 ; R0L0
0002 0000 DW 0000 ; R1L0
; ----------------------------------------------------------------------
; Clear memory from $0008 to $01FF
0004 1FFF CTRL $F, #$FF ; Reset all devices
0006 8200 LBI R2, #$00
0008 022D MLH R2, R2 ; R2 <- $0000
000A 0324 MOVE R3, R2
000C 8308 LBI R3, #$08 ; R3 <- $0008
000E 5231 MOVE (R3)+, R2
0010 8402 LBI R4, #$02
0012 C347 SBSH R3, R4
0014 F007 BRA $000E ; Loop
; R3 contains now $0200
; Size installed memory in increments of 16 kbytes
; The last usable memory location will be in R8
; Check if memory at $4000 is present
0016 8840 LBI R8, #$40
0018 088D MLH R8, R8
001A 8800 LBI R8, #$00 ; R8 <- $4000
001C 7888 MOVB (R8), R8 ; ($4000) <- $00
001E 6184 MOVB R1, (R8)-
0020 C10C SNS R1 ;
0022 A01B BRA $0040 ; no memory here, jump
; Check if memory at $8000 is present
0024 8880 LBI R8, #$80
0026 088D MLH R8, R8
0028 8800 LBI R8, #$00
002A 7888 MOVB (R8), R8
002C 6184 MOVB R1, (R8)-
002E C10C SNS R1
0030 A00D BRA $0040 ; no memory here, jump
; Check if memory at $C000 is present
0032 88C0 LBI R8, #$C0
0034 088D MLH R8, R8
0036 8800 LBI R8, #$00
0038 7888 MOVB (R8), R8
003A 6184 MOVB R1, (R8)-
003C C104 SS R1 ; no memory here, skip
003E 088D MLH R8, R8 ; last location is $FFFF
0040 C804 SS R8
0042 0000 HALT ; error, low byte not $FF
0044 10F0 CTRL $0, #$F0
0046 1FFF CTRL $F, #$FF ; Reset all devices
0048 0532 INC R5, R3 ; R5 <- $0201
004A 83AA LBI R3, #$AA
004C 033D MLH R3, R3 ; R3 <- $AAAA
004E 8420 LBI R4, #$20
0050 8705 LBI R7, #$05
0052 077D MLH R7, R7
0054 87FF LBI R7, #$FF ; R7 <- $05FF
0056 8104 LBI R1, #$04
0058 011D MLH R1, R1
005A 8136 LBI R1, #$36 ; R1 <- $0436
005C 0203 INC2 R2, R0
005E 0014 RET R1 ; call $0436
; Clear memory from R9L0 to end of display
0060 8200 LBI R2, #$00
0062 022D MLH R2, R2 ; R2 <- $0000
0064 0324 MOVE R3, R2
0066 8312 LBI R3, #$12 ; R3 <- $0012
0068 8406 LBI R4, #$06
006A 5231 MOVE (R3)+, R2
006C C347 SBSH R3, R4
006E F005 BRA $006A ; loop
0070 381D MOVE $3A, R8 ; last memory location to
R13L1
; Put 0000, 1111, 2222, ... into locations
$0080-00BF
; This is an aid to locate the registers in display
; register mode
0072 87C0 LBI R7, #$C0
0074 0894 MOVE R8, R9
0076 8880 LBI R8, #$80 ; R8 <- $0080
0078 5981 MOVE (R8)+, R9
007A C90C SNS R9
007C 89EF LBI R9, #$EF
007E A910 ADD R9, #$11
0080 099D MLH R9, R9
0082 C872 SE R8, R7
0084 F00D BRA $0078 ; -> -$0E(R0)
; --- Test A ---
; Bus In bit test
0086 7550 MOVB (R5)+, R5 ; write 'A' to $0201
0088 8FFF LBI R15, #$FF
008A 00FE GETB R15, $0
008C CF04 SS R15
008E 0000 HALT
; --- Test B ---
; Op Code test
0090 7550 MOVB (R5)+, R5 ; write 'B' to $0202
0092 351C MOVE $38, R5 ; save R5 to R12L1
0094 A003 BRA $009A
0096 81FF LBI R1, #$FF
0098 311F MOVE $3E, R1
009A 8101 LBI R1, #$01
[...]
So everything looks perfect, except that test 'A' fails. R15 should
contain $00FF after the 'GETB R15, $0', but instead it contains $0005. Now,
that's many bits stuck at zero... (the Bus In lines are active high).
Is there any difference in the value if you run the machine with
terminator (directly attached to the computer) and without terminator?
Are all power cables correctly seated? Somehow I have the impression that
the internal terminator or pullups on the Bus In lines don't work as they
should. Or the input receivers (whatever they are) are toast for 6 out of 8
lines.
According to the 5100 MIM page C-9, a GETB with address 0 is not used, so
should read $FF. Hmm, another thought: Maybe there's an addressing error,
and instead of addressing device 0, it addresses e.g. device 1. You should
definitely also check the DA (device address) lines.
Christian
21 Mar
21 Mar
11:53 p.m.
Quick update.
I tried with/without the terminator and no difference.
I also checked the "bus in" lines with a logic probe on the rear A2
connector and they were all high with no pulsing. I'm going to try to
break out the scope tomorrow and see if there's any pulsing in them as I
start the computer.
Santo
On Fri, Mar 20, 2015 at 1:24 PM, Santo Nucifora <santo.nucifora at gmail.com>
wrote:
First off, thank you for disassembling the 5100
Executable ROS.
I just saw the link to your website and I can say I lived there for a
while. I first saw this 5100 for sale back in April 2014 and I agreed to
buy from the seller at that time, During that time I looked for any
information I could find on the 5100 and read every word of your site. It
didn't make much sense to me because you have to experience the true
hardware first but I appreciated it anyway. It took me just under a year
of patience to get the seller to complete the deal (I think he was worried
about shipping to another country) but it's here now so thank you for your
site. If I can get mine to work, maybe I can help make a 5100 version of
your emulator :)
Early on I tried with the terminator but my I/O cable driver card had
severely rusted ICs. I will try again with the terminator and see if there
is a difference.
I am writing this down for what I am going to check when I get home:
1. Check with terminator
2: Check bus lines as indicated in the IBM 5100 Maintenance manual
Page 3-14:
*Halt code: A*
*Test: Turns all bus in bits on*
*Area tested: A2*, F2, G2, H2*
*Service Aids: Probe the 'bus in' lines on the F2 card. All bus in bits
should be up or pulsing.*
Note: F2 = Base I/O board (525 - 528)
Page 5-22 to 5-25 = Base I/O card F2 logic and wiring
Page 5-24 bottom has references to Bus In lines but I wouldn't know where
to begin probing them.
Your site mentions the A2 connector which is referred to on page 5-15 at
the bottom. I can check that.
Thank you once again and if you can post the full disassembly, I would
appreciate that. If I am able to get past this, I'm fairly certain I won'
t be sailing through the rest of the tests.
Santo
On Fri, Mar 20, 2015 at 5:37 AM, Christian Corti <
cc at informatik.uni-stuttgart.de> wrote:
On Thu, 19 Mar 2015, Santo Nucifora wrote:
Screenshot is here:
http://vintagecomputer.ca/wp-content/uploads/2015/01/exeros-5100.jpg
Ok, here we go:
0000 0004 DW 0004 ; R0L0
0002 0000 DW 0000 ; R1L0
; ----------------------------------------------------------------------
; Clear memory from $0008 to $01FF
0004 1FFF CTRL $F, #$FF ; Reset all devices
0006 8200 LBI R2, #$00
0008 022D MLH R2, R2 ; R2 <- $0000
000A 0324 MOVE R3, R2
000C 8308 LBI R3, #$08 ; R3 <- $0008
000E 5231 MOVE (R3)+, R2
0010 8402 LBI R4, #$02
0012 C347 SBSH R3, R4
0014 F007 BRA $000E ; Loop
; R3 contains now $0200
; Size installed memory in increments of 16 kbytes
; The last usable memory location will be in R8
; Check if memory at $4000 is present
0016 8840 LBI R8, #$40
0018 088D MLH R8, R8
001A 8800 LBI R8, #$00 ; R8 <- $4000
001C 7888 MOVB (R8), R8 ; ($4000) <- $00
001E 6184 MOVB R1, (R8)-
0020 C10C SNS R1 ;
0022 A01B BRA $0040 ; no memory here, jump
; Check if memory at $8000 is present
0024 8880 LBI R8, #$80
0026 088D MLH R8, R8
0028 8800 LBI R8, #$00
002A 7888 MOVB (R8), R8
002C 6184 MOVB R1, (R8)-
002E C10C SNS R1
0030 A00D BRA $0040 ; no memory here, jump
; Check if memory at $C000 is present
0032 88C0 LBI R8, #$C0
0034 088D MLH R8, R8
0036 8800 LBI R8, #$00
0038 7888 MOVB (R8), R8
003A 6184 MOVB R1, (R8)-
003C C104 SS R1 ; no memory here, skip
003E 088D MLH R8, R8 ; last location is $FFFF
0040 C804 SS R8
0042 0000 HALT ; error, low byte not $FF
0044 10F0 CTRL $0, #$F0
0046 1FFF CTRL $F, #$FF ; Reset all devices
0048 0532 INC R5, R3 ; R5 <- $0201
004A 83AA LBI R3, #$AA
004C 033D MLH R3, R3 ; R3 <- $AAAA
004E 8420 LBI R4, #$20
0050 8705 LBI R7, #$05
0052 077D MLH R7, R7
0054 87FF LBI R7, #$FF ; R7 <- $05FF
0056 8104 LBI R1, #$04
0058 011D MLH R1, R1
005A 8136 LBI R1, #$36 ; R1 <- $0436
005C 0203 INC2 R2, R0
005E 0014 RET R1 ; call $0436
; Clear memory from R9L0 to end of display
0060 8200 LBI R2, #$00
0062 022D MLH R2, R2 ; R2 <- $0000
0064 0324 MOVE R3, R2
0066 8312 LBI R3, #$12 ; R3 <- $0012
0068 8406 LBI R4, #$06
006A 5231 MOVE (R3)+, R2
006C C347 SBSH R3, R4
006E F005 BRA $006A ; loop
0070 381D MOVE $3A, R8 ; last memory location to
R13L1
; Put 0000, 1111, 2222, ... into locations
$0080-00BF
; This is an aid to locate the registers in
display
; register mode
0072 87C0 LBI R7, #$C0
0074 0894 MOVE R8, R9
0076 8880 LBI R8, #$80 ; R8 <- $0080
0078 5981 MOVE (R8)+, R9
007A C90C SNS R9
007C 89EF LBI R9, #$EF
007E A910 ADD R9, #$11
0080 099D MLH R9, R9
0082 C872 SE R8, R7
0084 F00D BRA $0078 ; -> -$0E(R0)
; --- Test A ---
; Bus In bit test
0086 7550 MOVB (R5)+, R5 ; write 'A' to $0201
0088 8FFF LBI R15, #$FF
008A 00FE GETB R15, $0
008C CF04 SS R15
008E 0000 HALT
; --- Test B ---
; Op Code test
0090 7550 MOVB (R5)+, R5 ; write 'B' to $0202
0092 351C MOVE $38, R5 ; save R5 to R12L1
0094 A003 BRA $009A
0096 81FF LBI R1, #$FF
0098 311F MOVE $3E, R1
009A 8101 LBI R1, #$01
[...]
So everything looks perfect, except that test 'A' fails. R15 should
contain $00FF after the 'GETB R15, $0', but instead it contains $0005. Now,
that's many bits stuck at zero... (the Bus In lines are active high).
Is there any difference in the value if you run the machine with
terminator (directly attached to the computer) and without terminator?
Are all power cables correctly seated? Somehow I have the impression that
the internal terminator or pullups on the Bus In lines don't work as they
should. Or the input receivers (whatever they are) are toast for 6 out of 8
lines.
According to the 5100 MIM page C-9, a GETB with address 0 is not used, so
should read $FF. Hmm, another thought: Maybe there's an addressing error,
and instead of addressing device 0, it addresses e.g. device 1. You should
definitely also check the DA (device address) lines.
Christian
3571
days inactive
3579
days old
23 comments
6 participants
participants (6)
-
cc＠informatik.uni-stuttgart.de -
cctalk＠fahimi.net -
drlegendre＠gmail.com -
Kevin＠RawFedDogs.net -
santo.nucifora＠gmail.com -
spacewar＠gmail.com