27 Dec
2015
27 Dec
'15
1:29 a.m.
Hi Mike,
Here are the options to attach 3340 DASD emulation to an IBM System/3
1) direct connect to the internal channel of the S/3. Some disk OEM's did
this.
Requires a FPGA with at one side MST-1 interface logic and at the other side
IDE or SCSI interface.
The availabe IBM documentation is complete enough to finish this project.
You need good IBM HW & VHDL knowledge.
2) direct connect to the BUS/TAG interface connector.
This needs a 8+P bit stream. You have to do some reverse engineering to
figure out what the exact format is.
I have no idea if the HW must be implemented in a FPGA (for timing reasons)
or if an AVR processor will do the job.
Advantage is that you don't have to modify anything inside the S/3.
3) IBM has implemented an IOP (I/O Processor) between the S/3 CPU and the
3340 drives.
This IOP is a modified version of the ones used in the IBM 370/115 & 125. It
is a powerfull multi thread capable beast.
With small HW modification you can connect an IDE or SCSI drives to it.
The difficult part is modifying the firmware of the IOP. This requires a
special assembler (to be written) and very good assembler skill's.
All options requires quite alot of time to implement.
My 2 cents
Henk
27 Dec
27 Dec
3:19 p.m.
On Sun, Dec 27, 2015 at 10:29 PM, Henk Stegeman <h.j.stegeman at hccnet.nl> wrote:
Hi Mike,
Here are the options to attach 3340 DASD emulation to an IBM System/3
1) direct connect to the internal channel of the S/3. Some disk OEM's did
this.
Requires a FPGA with at one side MST-1 interface logic and at the other side
IDE or SCSI interface.
The availabe IBM documentation is complete enough to finish this project.
You need good IBM HW & VHDL knowledge.
Oh interesting - I had no idea! Do you have names and product numbers
for those OEMs? Any more info? Ever seen one?
If they were sold commercially by OEMs then the project already IS
finished so to speak; it's just a question of *finding* one! Or
finding the documentation and using that as a basis for re-creating
the OEM solution.
It doesn't require any hard-to-perform or reverse changes to the S/3?
No backplane rework or wire wrap? It was just a case of plugging OEM
cards into appropriate slots?
2) direct connect to the BUS/TAG interface connector.
This needs a 8+P bit stream. You have to do some reverse engineering to
figure out what the exact format is.
I have no idea if the HW must be implemented in a FPGA (for timing reasons)
or if an AVR processor will do the job.
Advantage is that you don't have to modify anything inside the S/3.
And the other advantage is that it could be part of a more
generalizable device that could be used to replace other Bus/Tag
peripherals on other IBM systems... if some of us were to start a
home-brew project that might be the best approach to take.
3) IBM has implemented an IOP (I/O Processor) between
the S/3 CPU and the
3340 drives.
This IOP is a modified version of the ones used in the IBM 370/115 & 125. It
is a powerfull multi thread capable beast.
With small HW modification you can connect an IDE or SCSI drives to it.
The difficult part is modifying the firmware of the IOP. This requires a
special assembler (to be written) and very good assembler skill's.
If IBM have already implemented it then ready to use IOPs exist or at
one time existed out there in the wild... your reference to modifying
IOP firmware... do you mean to connect to the S/3 - or to attach IDE
or SCSI? Or both? Does this IOP have an IBM model number? Was it a
separate box or a set of cards and backplane that could be installed
in the 370? I hope to be getting a 370/125 next year...
Fascinating info Henk; I had no idea any of this stuff existed. I
thought the only options for S/3 5415 were real hardware 3340s or
nothing.
Mike
http://www.corestore.org
'No greater love hath a man than he lay down his life for his brother.
Not for millions, not for glory, not for fame.
For one person, in the dark, where no one will ever know or see.'
3066
days inactive
3066
days old
1 comments
2 participants
participants (2)
-
h.j.stegeman＠hccnet.nl -
tmfdmike＠gmail.com