[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 49.910::kav30

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

82.0. "Can a non-arbiter get arbiter errors in the error log?" by ZYDECO::BODA (Realtime Products Support) Tue Mar 30 1993 21:19

Hi KAV folks,

We are tracking down some problems for a customer doing KAV to KAV communications
by mapping to a buffer in the other's space.  However, they are taking some
errors.  One KAV has done an IN_MAP allowing others to see it's buffer and
the other is doing an OUT_MAP to get to the other's space.

Two questions of you if I may:

The first is a curiosity question as this problem is resolved:

1) If a KAV30 has an A24 base address inadvertantly set to the same address
as another VMEbus device and if the KAV30 has not done an IN_MAP, should this
cause a conflict?  We found that it did when the other KAV30 attempted to
write to the VMEbus device.  The KAV30 with the wrong address would no
longer be visible on the net and may have crashed.
Changing the A24 base address cured this problem

Second question is still pending:

2) Should a non-arbiter KAV30 be able to take a bus arbiter error (5c5c as
per the error log)?  We also see the same KAV30 which should be in master
mode taking slave errors (5C9C) with subcodes indicating invalid SGM's on 
reads.  Noone should be writing to or reading from this KAV30 (slave mode)
rather it should be doing reading of the other KAV30.  

Thanks for any thoughts you may have.

Alan
T.RTitleUserPersonal
Name
DateLines
82.1resolution to #2 question in .0ZYDECO::BODARealtime Products SupportWed Mar 31 1993 03:5812
The problem in .0's question #2 has been resolved.

Once the customer put both the KAV's next to each other (as was recommended
to them by a colleague of mine earlier) they no longer experience the
arbiter, slave, or master errors.  The arbiter error apparently can simply
mean that there was an arbitration problem on the bus - not that it necessarily
was the arbiter.  I could even indicate that there was no arbiter.  Given that
we did not know how their intervening VMEbus devices were configured, it's
possible that the arbitration was not taking place correctly.

Rule of thumb therefore is, for KAV30's doing master/slave access to one another,
place them next to eachother on the bus.
82.2You can have open slots, assuming you've configured your VME bus/backplane correctlySTAR::NORDHOpenVMS Development, DTN 381-1672Fri Apr 30 1993 20:3221
Re. .1

>>>Rule of thumb therefore is, for KAV30's doing master/slave access to one another,
>>>place them next to eachother on the bus.

	This is not really true! You problem which you had was that the VME slots between
the two KAV30's did not have the arbitrator control lines wired for each open slot
at the back of the backplane.

	So, to correct your rule of thumb, is that it must be VME boards(any) between two 
masters or have the arbiter lines wired for each slot where no VME modules is inserted, to 
pass along the arbiter control lines to the arbiter(slot 1). The arbiter is always the 
slot 1 module. I believe I remember that there exist VME "grant" cards, so you do not need
to insert jumpers for each open slot.

	All this is documented in the KAV30 documentation set(as far as I remember) under
configuration rules section.

Hope this helps,

-Jan
82.3I stand corrected . . .ZYDECO::BODARealtime Products SupportSat May 01 1993 03:4014
Hi Jan,

Thanks for that clarification.  Unfortunately, I must have missed that in the 
installation/configuration portion of the KAV30 H/W and Installation  Guide.
The only section on configuring the VMEbus Backplane I saw was on p2-2 which
then refers you to the VMEbus crate and backplane documentation for info
on configuring the VMEbus backplane.  I admit I did not have the doc readily
available.

82.2 has just become part of my docset.

Thanks again,

Alan