[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | VAX on VMEbus: KAV30 |
| Notice: | Could have been as fast as 68K but its a VAX! |
| Moderator: | CSSVMS::KAV30_SUPP |
|
| Created: | Thu Apr 18 1991 |
| Last Modified: | Fri Aug 02 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 159 |
| Total number of notes: | 645 |
98.0. "A16 addressing CPI IOBC board " by ZYDECO::REDDY () Fri Aug 06 1993 00:55
We have a customer who is replacing his Aeon 300s with KAV30s. They are
using a CPI IOBC card which can be configured for A16, A24, or A32 addressing
mode. When they were using this board with the Aeon 300, they had no problems
addressing this board in any of the three modes.
When they switched to KAV30, CPI IOBC card only works in the A24 mode.
Either the A16 mode or the A32 mode gives them VME/VSB write error. They take
the virtual address the out map returns, add the offset and then access the CSR
which is located at hex FF00. They have modeled their driver after the
KAV_MVMEDRIVER.C that is in the kit.
Is there any KAV30 hardware or software restriction that could be causing this
board not to work in the A16 or A32 mode? I could not find any such
restrictions in the manual. Any ideas on what might be causing the problem?
Thanks for any suggestions.
Sumithra
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 98.1 | Configuration.... | BAYERN::WOLFF | Conformism is for little minds. | Fri Aug 06 1993 09:55 | 5 |
| It looks like a configuration problem I would bet that the page is mapped wrong
or the offset is incorrect. There are no restrictions in A32 mode. The
address FF00 lies within the page 0, also look at the AM codes.
Julian.
|