requirement:
1. using toroidal transformer as power supply instead of SMPS
2. using SRAM instead of DRAM
3. using super I/O chip
this is to replace aging 8088 system, and also used to teach pure 16
bit design.
thank you
I'm sure it can be done. Even I can do it. I'm as sure it will become too
expensive.
The power supply will become too hot and too heavy. You may need a custom
designed toroid or more then one standard type.
It's not clear what super I/O chip you're talking about but I suppose it
will need at least a four layer PCB. Besides those chips are seldom
available in low volume.
You will need a BIOS. There may be an existing one for free. Otherwise it
may become more expensive then the hardware.
There are a lot of decisions to make before you can even start. About speed,
video, types and numbers of I/O channels, type and number of expansion slots
and so on.
So my guess - a wild guess I admit - is a pricetag of several thousend bucks
for a working prototype.
petrus bitbyter
I'm guessing this is homework. The "to teach pure 16 bit
design" is a bit of a give-away. Chances are, that is how
the homework was sold to the students. The SRAM not DRAM
requirement is because the prof doesn't want to grade DRAM
designs -- pain in the ass. Super I/O is a all-in-one that
includes the 8259 interrupt controller and some standard
serial and parallel port items along with floppy control,
that got included into the South Bridge when PCI came along.
Again, it simplifies the student's work and the prof's review
time. I don't the BIOS is required here. Just a presumption
of one. It's school time, again.
Jon
> I don't the BIOS is required here.
I don't _think_ the BIOS is required here.
(...)
>> It's school time, again.
>>
>> Jon
>
> wooowww your so smart. ok this is your assignment, design similar
> thing, powered by single AA battery.
You got it in one try, Jon.
:)
--Winston
The HP200LX design may be of interest to you. It is a bit dated, but
it was a IBM compatible PC (NEC V70) with a PCMCIA slot that was
handheld and operated on 2 AA batteries.
TomC
XT.8086 wrote:
> Could someone design for me a 8086 powered computer which is IBM
> compatible
Sure can. Do you have money?
>
> requirement:
>
> 1. using toroidal transformer as power supply instead of SMPS
> 2. using SRAM instead of DRAM
> 3. using super I/O chip
Long while ago a friend of mine built PC XT 8086 on the breadboard from
discrete parts. That board included I/O and CGA/HGS video. Worked fine.
> this is to replace aging 8088 system, and also used to teach pure 16
> bit design.
For any practical purpose it would be easier to emulate PC XT on a
modern computer.
Vladimir Vassilevsky
DSP and Mixed Signal Design Consultant
http://www.abvolt.com
Correctly interfaced 8086 memory supports both 8 and 16 bit transfers.
The condition is that there are separate write enables for odd and
even bytes. The CPU handles the necessary byte swapping.
--
Tauno Voipio
And COCOM rules were set by lobbyists so that it was a serious criminal
offence to export BBC micros or Compaq PC compatibles to Russia whilst
IBM XTs were OK. It was particularly bad when in the same week an IBM
salesman got an industry award for selling 2000 IBM XTs (with hard
disks) to Moscow University and a West German businessman was jailed
for 5 years for selling 300 tape based BBC micros to East Berlin.
Ollivetti M24 was a full 8086 IBM PC compatible also sold as AT&T 6300.
http://en.wikipedia.org/wiki/Olivetti_M24
It was highly compatible with the IBM design. The earlier M20 (Z8000
based) was not although they produced a daughter board for it.
>
> The IBM PS/2 models 25 and 30 were built with an 8 MHz 8086.
>
> The Tandy 1000 SL-series machines used 8086 CPUs.
Many 8086 machines in that early era were of limited PC compatibility.
Almost everything had better graphics than the rubbish IBM offering.
Regards,
Martin Brown
>ALl "XT" class, and compatibles, were 8086 based. The '186 was rarely used
>for a PC type system because of interrupt (and I/O) conflicts. Using it
>automatically made it non-comparable. Some did it anyway but anything written
>"to the metal" had problems.
You're a fuckin' retard. The 80186 was not introduced for use in the
PCs because the 80286 silicon was already in production, and was a huge
step forward in design. The 80186 was dead before it hit the docks, and
the reason had NOTHING to do with its operation.
The 80186 was then relegated to industrial controls, where it worked
just fine (unlike you), interrupts and all.
STOP making shit up, you retarded twit. If you do not have citations
about "interrupt (and I/O) conflicts, shut the fuck up.
The 80186 was fully compatible, and some were actually used in a PC
design and it was successful in said design.
>
>
>josephkk wrote:
>
>> On Mon, 03 Oct 2011 15:17:31 -0500, Vladimir Vassilevsky
>> <nos...@nowhere.com> wrote:
>
>>>>>The original PC and XT used 8088, which has an 8 bit data bus.
>>>>>For a turbo version, use NEC V20. It can also run 8080 code.
>>>>>
>>>>I want 16-bit CPU running 16-bit bus. that would simplify the design
>>>>alot.
>>>
>>>That complicates the design alot. To be PC compatible, you have to
>>>convert 16 bit bus cycles to 2 x 8 bit cycles and back.
>>>
>> I don't think so. There were 8086 based clones out there. You would need
>> 100% 16 bit memory however.
>
>The ISA bus has to support for 8 bit operation. All 8 bit onboard
>peripherals should be accessible from 16 bit CPU bus in correct way.
>The 8 bit only PC system is much simpler then 8/16 bit as you don't have
>to split or merge cycles.
Of course that task was made massively easier by plenty of IO instructions
that operated on bytes (8 bits) instead of words (16 bits). Even the DMA
chip could operate on bytes.
I could be vaguely misrecalling, but wasn't the PC JR a 186?
No, it was an 8088, too.
You're right, the difference between the PC and /XT was the memory
(64Kx1-256/640KB max vs. 16Kx1-64KB max).
>I certainly remember these things.
There were 8086 fully compatible PC/XT class systems made, however.
>On Fri, 07 Oct 2011 10:25:48 -0500, "k...@att.bizzzzzzzzzzzz"
><k...@att.bizzzzzzzzzzzz> wrote:
>
>>ALl "XT" class, and compatibles, were 8086 based. The '186 was rarely used
>>for a PC type system because of interrupt (and I/O) conflicts. Using it
>>automatically made it non-comparable. Some did it anyway but anything written
>>"to the metal" had problems.
>
> You're a fuckin' retard. The 80186 was not introduced for use in the
>PCs because the 80286 silicon was already in production, and was a huge
>step forward in design. The 80186 was dead before it hit the docks, and
>the reason had NOTHING to do with its operation.
How hard do you try to be wrong, AlwaysWrong? ...because you are, *always*.
The /AT came out in '84. The '186/8 was available, in quantity, in '81.
> The 80186 was then relegated to industrial controls, where it worked
>just fine (unlike you), interrupts and all.
>
> STOP making shit up, you retarded twit. If you do not have citations
>about "interrupt (and I/O) conflicts, shut the fuck up.
STOP being wrong, AlwaysWrong.
> The 80186 was fully compatible, and some were actually used in a PC
>design and it was successful in said design.
Wrong. <shock!>
And an MFM hard drive. Can't recall exactly, but I think it
was 10Mb. Slow. But better than the PC's floppies or the
PC's cassette tape drive interface, which I also remember
because I used a Radio Shack cassette recorder to save
programs.
>>I certainly remember these things.
>
>There were 8086 fully compatible PC/XT class systems made, however.
Yes, I'm getting that message loud and clear. I distinctly
remember 'difficulties' there and a general conclusion "not
to bother with them." But some did, apparently, and fewer
still actually managed to create something PC compatible from
what I've recently read posted here. Supplements and
corrects my recollections.
Jon
Sure. I was talking about the MB.
>>>I certainly remember these things.
>>
>>There were 8086 fully compatible PC/XT class systems made, however.
>
>Yes, I'm getting that message loud and clear. I distinctly
>remember 'difficulties' there and a general conclusion "not
>to bother with them." But some did, apparently, and fewer
>still actually managed to create something PC compatible from
>what I've recently read posted here. Supplements and
>corrects my recollections.
The '286 came out just a couple of years later, about the time the whole thing
took off. After the '286, there was no reason to use the '86 at all. The
'186 was still cost-effective, but it wasn't 100% compatible, without which a
system wasn't sellable.
josephkk wrote:
To be PC compatible, all 8 and 16 bit instructions have to operate
correctly regardless. That 8/16 bit issue gets more complicated with
PC/AT, and then with 386 and later. Bus interface unit would be hard to
make from discrete logic parts.
We bought 3 186 IBM pc's at the time, but about 6 months
later they switched to 286 cpu's.
We used IBM network cards in them, those worked without failure
for about 8 years, until replaced by ethernet.(3com).
Never noticed much difference between them, but they all
had math co-processors.
So yes, for a brief time they were on the market.
Olivetti M20 / M24??? were 8086 based. It was really fast,
better than early 286s. XTs were 8088 based and slooooow.
We had a lot of the Olivettis running QNX. Was a good thing.
80186 was announced at the very same same time as the 286.
It was not really compatible to an AT or XT, some timer /
DMA / interrupt addresses were different and that could not be healed.
I also got a datasheet for an 80187 under NDA, but that chip
never saw the light of day. Instead they proposed a hack with a 8087 and
a PAL IIRC.
At that time I have built a lot of 80186 machines for Multibus I
and AMS/SMP bus, also with _very_ early 186 silicon.
Gerhard
p.s.
I suppose, Intel gave on the iAPX[1234]86 type numbers, because now they
would have to pay royalties to Apple.
1/2 :-) only.
> On 09 Oct 2011 22:10:08 GMT, Sjouke Burry <bu...@planet.nl> wrote:
>
>>David Harmon <sou...@netcom.com> wrote in
>>news:W6mdnXNtWeX3IAzT...@earthlink.com:
>>
>>> On Thu, 06 Oct 2011 23:42:14 -0700 in sci.electronics.design, Jon
>>> Kirwan <jo...@infinitefactors.org> wrote,
>>>>I don't recall ever seeing an 8086 compatible. I remember
>>>>keeping an eye out, too. I vaguely recall there wasn't any
>>>>80186 compatibles, either.
>>>
>>> I could be vaguely misrecalling, but wasn't the PC JR a 186?
>>>
>>
>>We bought 3 186 IBM pc's at the time, but about 6 months
>>later they switched to 286 cpu's.
>
> No you didn't. IBM never used the 186 or 188 in PCs (couldn't have).
> AFAIK, the only thing they used the 8086 in was the System/23
> DataMaster (a.k.a. DataToaster).
Curious. You know better, what we bought???????
I have had years in which to read the label on the
front of the case, showing 186.
That was in the Netherlands, and I dont think the label
was lying.
>"k...@att.bizzzzzzzzzzzz" <k...@att.bizzzzzzzzzzzz> wrote in
>news:jn84971kbj664ne1s...@4ax.com:
>
>> On 09 Oct 2011 22:10:08 GMT, Sjouke Burry <bu...@planet.nl> wrote:
>>
>>>David Harmon <sou...@netcom.com> wrote in
>>>news:W6mdnXNtWeX3IAzT...@earthlink.com:
>>>
>>>> On Thu, 06 Oct 2011 23:42:14 -0700 in sci.electronics.design, Jon
>>>> Kirwan <jo...@infinitefactors.org> wrote,
>>>>>I don't recall ever seeing an 8086 compatible. I remember
>>>>>keeping an eye out, too. I vaguely recall there wasn't any
>>>>>80186 compatibles, either.
>>>>
>>>> I could be vaguely misrecalling, but wasn't the PC JR a 186?
>>>>
>>>
>>>We bought 3 186 IBM pc's at the time, but about 6 months
>>>later they switched to 286 cpu's.
>>
>> No you didn't. IBM never used the 186 or 188 in PCs (couldn't have).
>> AFAIK, the only thing they used the 8086 in was the System/23
>> DataMaster (a.k.a. DataToaster).
>
>Curious. You know better, what we bought???????
I know it wasn't an IBM, as described. Yes.
>I have had years in which to read the label on the
>front of the case, showing 186.
>That was in the Netherlands, and I dont think the label
>was lying.
Someone is.
I do remember 386 board with 8-bit CGA on it. while all of its bus is
16-bit wide.
Could you explain more about correctly accessing 8-bit bus in 16 bit
ISA bus, particularly for 8086 processor.
separate document or web site would be better I think.
Thanks
we can obtain 16-bit wide SRAM today, does byte swapping still any use.
How come 8086 machine is faster than 80286 machine, was it clocked
faster, which I doubt.
Berlin wall is Kaput, could you share the NDA document with us now.
Danke Schoon
I believe 8088 is crippled version of 8086, with only 8-bit data bus
hmm , I would like the one with cassette port in it.
Lots of fun :-)
Do you mean the original five slot PC motherboard?
It wasn't. For the 8086 to be faster, it had to be a pretty horrid
implementation of the '286 system. The '86 was a *lot* cheaper, however.
There was one problem with the 80286, solved in the 80386 and
beyond, that greatly slowed it down when using memory beyond
the 20 address limit (in other words, the upper four address
lines of the 80286 were non-zero.) [Obviously, this does NOT
relate to the above discussion about the 8086 vs 80286, but
it made me remember things so I'm writing it anyway. :P ]
The 80286 could not shift back from protected mode into real
mode without a processor reset. So the BIOS routines that
supported accessing memory past the 1Mb boundary would set up
a protected mode environment, shift to protected mode,
perform the indicated operation, and then ... well, then the
BIOS used the clock calendar chip with a very tiny battery
backed memory, stored a special code there so that on power
reset it could look and realize that it was coming back from
a protected mode call, and then would return to the caller in
real mode rather than reboot the O/S from disk.
Which reminds me of yet another oddity. Anyone remember (I
do) that code can be downloaded into a motherboard via the
keyboard interface -- no disks required? A feature used to
download diagnostic/test code for motherboard manufacturing.
Jon
>On Mon, 10 Oct 2011 10:12:21 -0500, "k...@att.bizzzzzzzzzzzz"
;-)
Yes, but the keyboard trick (patented by IBM, IIRC) worked reasonably well.
>The 80286 could not shift back from protected mode into real
>mode without a processor reset. So the BIOS routines that
>supported accessing memory past the 1Mb boundary would set up
>a protected mode environment, shift to protected mode,
>perform the indicated operation, and then ... well, then the
>BIOS used the clock calendar chip with a very tiny battery
>backed memory, stored a special code there so that on power
>reset it could look and realize that it was coming back from
>a protected mode call, and then would return to the caller in
>real mode rather than reboot the O/S from disk.
>Which reminds me of yet another oddity. Anyone remember (I
>do) that code can be downloaded into a motherboard via the
>keyboard interface -- no disks required? A feature used to
>download diagnostic/test code for motherboard manufacturing.
Part of (side effect of) the cassette interface, IIRC.
Mine are complete units, minus some case screws, perhaps. I don't have the
original SS diskette drive, however.
>> The 80286 could not shift back from protected mode into real
>> mode without a processor reset. So the BIOS routines that
>> supported accessing memory past the 1Mb boundary would set up
>> a protected mode environment, shift to protected mode,
>> perform the indicated operation, and then ... well, then the
>> BIOS used the clock calendar chip with a very tiny battery
>> backed memory, stored a special code there so that on power
>> reset it could look and realize that it was coming back from
>> a protected mode call, and then would return to the caller in
>> real mode rather than reboot the O/S from disk.
Yes! Xilinx place & route did that once a millisecond to keep
the mouse happy.
Gerhard
Well, it was 30 years ago... ;-)
I seem to remember that it was. The cassette port was part of extended BIOS,
though you're right it didn't exist after the 5150.
>
>
>josephkk wrote:
>
>> On Fri, 07 Oct 2011 00:20:51 -0500, Vladimir Vassilevsky
>> <nos...@nowhere.com> wrote:
>>
>>
>>>
>>>josephkk wrote:
>>>
>>>
>>>>On Mon, 03 Oct 2011 15:17:31 -0500, Vladimir Vassilevsky
>>>><nos...@nowhere.com> wrote:
>>>
>>>>>>>The original PC and XT used 8088, which has an 8 bit data bus.
>>>>>>>For a turbo version, use NEC V20. It can also run 8080 code.
>>>>>>>
>>>>>>
>>>>>>I want 16-bit CPU running 16-bit bus. that would simplify the design
>>>>>>alot.
>>>>>
>>>>>That complicates the design alot. To be PC compatible, you have to
>>>>>convert 16 bit bus cycles to 2 x 8 bit cycles and back.
>>>>>
>>>>
>>>>I don't think so. There were 8086 based clones out there. You would need
>>>>100% 16 bit memory however.
>>>
>>>The ISA bus has to support for 8 bit operation. All 8 bit onboard
>>>peripherals should be accessible from 16 bit CPU bus in correct way.
>>>The 8 bit only PC system is much simpler then 8/16 bit as you don't have
>>>to split or merge cycles.
>>
>>
>> Of course that task was made massively easier by plenty of IO instructions
>> that operated on bytes (8 bits) instead of words (16 bits). Even the DMA
>> chip could operate on bytes.
>
>To be PC compatible, all 8 and 16 bit instructions have to operate
>correctly regardless. That 8/16 bit issue gets more complicated with
>PC/AT, and then with 386 and later. Bus interface unit would be hard to
>make from discrete logic parts.
>
>
>Vladimir Vassilevsky
>DSP and Mixed Signal Design Consultant
>http://www.abvolt.com
Thus it is pretty convenient that the 8086 chips have proper interface
electronics onboard for that. Then you have a much easier time designing
the matching circuitry for memory and IO.
?-)
The difference in memory bandwidth made for a rather noticeable difference
in performance.