On Jan 7, 18:37, Tom Leffingwell wrote:
>
> It seems to work. I tried 772410, and it returned 000000. With
> 772414 it returned 006200. Is there a way to look at the what is being
> transferred into memory?
If you know how to program it, or have some software to do it, you could
clear an area in memory, get it to DMA some data in, and then look at the
memory again.
> I'm starting to think that my problem stems the lack of the
> ADV11-C module that it wants. The program goes into simulation mode if
"a
> hardware port is missing" which I assume to mean one of the interfaces it
> uses, a DRV11, a DRV11-B, and an ADV11-C. Since I don't need the
> funtionality provided by the ADV11-C (and the fact that I can't find
one),
> I didn't install it.
That's almost certainly what's wrong. The software probably checks for the
presence of a device at the address(es) it expects for the ADV11; that's
very easy to do (just set up a trap handler in case it causes a bus
timeout, then try to read from the address. If it doesn't cause a trap,
the device is there.)
The standard adresses for an ADV11 are 170400 for the CSR and 170402 for
the Data Buffer Register. The standard addresses for a DRV11 are 167770
for CSR, and 167772 and 167774 for the OUTBUF and INBUF registers.
If you haven't got an ADV11, I can think of three options open to you:
1) get an ADV11
2) get a 3rd party equivalent, such as an ADAC card
3) use some other device, set it to the ADV11 addresses, and hope you
fool the software
--
Pete Peter Turnbull
Network Manager
University of York
Received on Mon Jan 07 2002 - 19:07:00 GMT