Book on HW/SW interface?

Book on HW/SW interface?

Post by Slav Inge » Wed, 02 Jun 1999 04:00:00



Hello,

My question is very simple, but I haven't been able to find an answer.
I've been searching for a book that delves into the theory of how
software controls the hardware (basically a hardware/software interface)
- literally, how software (machine code) causes bits to flip or motors
to actuate.  I've seen only a few books on this topic, but they didn't
answer my questions.  I guess this question deals with control theory,
systems, computer science, and everything inbetween.  I've also been
searching for information on theory of object code and how program
loaders work.  Anything you can suggest?  I'm not looking for an
architecture reference - I've read all CPU and hardware manuals I could
find on a number of computer architectures.

Thanks very much.

- Slav Inger.

 
 
 

Book on HW/SW interface?

Post by Andy » Sat, 05 Jun 1999 04:00:00



> Hello,

> My question is very simple, but I haven't been able to find an answer.
<snip>
> - literally, how software (machine code) causes bits to flip or motors
> to actuate.
<snip>
> Anything you can suggest?  I'm not looking for an
> architecture reference - I've read all CPU and hardware manuals I could
> find on a number of computer architectures.

Why don't the CPU and hardware manuals answer the
question? If you go to a much lower level, then you
are into electrical engineering.

Are you trying to figure out low-level semi-conductor
devices, bi-polar junctions, MOSFETs and associated
interactions? How to bias a transistor junction?

This doesn't look like a simple question.

-Andy

 
 
 

Book on HW/SW interface?

Post by geof » Thu, 10 Jun 1999 04:00:00


The question is simple, the answer isn't.  The answer will
vary depending on every specific piece of hardware.  To
my knowledge, there is no standard or standard family
of interfaces across hardware devices.

A few hardware vendors (Parallax comes to mind) who
design hardware, then embed an OS into the hardware
which communicates via some communications protocol.
In this case, you write your app then make an external
call to control the hardware.  If this is implemented
across an entire product family (as Parallax has done)
then you get a nice consistent manner of doing things.

Problem here is that this approach is not particularly
flexible, and potentially incurs signficant (and I
mean significant) overhead on the hardware device.

Here's an idea... if you live near a used bookstore,
look for one of the *really* old PC hardware books.
They tend to have short chapters on using x86 assembly.
That may be useful to you, just in terms of concept.

-geoff

: >
: > Hello,
: >
: > My question is very simple, but I haven't been able to find an answer.
: <snip>
: > - literally, how software (machine code) causes bits to flip or motors
: > to actuate.
: <snip>
: > Anything you can suggest?  I'm not looking for an
: > architecture reference - I've read all CPU and hardware manuals I could
: > find on a number of computer architectures.
: >

: Why don't the CPU and hardware manuals answer the
: question? If you go to a much lower level, then you
: are into electrical engineering.

: Are you trying to figure out low-level semi-conductor
: devices, bi-polar junctions, MOSFETs and associated
: interactions? How to bias a transistor junction?

: This doesn't look like a simple question.

: -Andy

--
-----------------------------------------------------------------------

UNIX Systems Administrator             through comedy for longer than I
astrology.net                          care to admit.
(415)447-6193 x896