| 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 |
Hi again, The KAV HARDWARE INSTALLATION AND USER'S GUIDE (p4-6) states that the KAV30 in master mode can perform D08, D16, and D32 data transfers. However, can these be done in burst mode? It states that in slave mode the KAV30 can do block mode data transfers; however, the docs don't indicate whether in master mode whether the KAV30 can do 256 byte burst mode transfers. A customer of ours indicates that AEON's VME300 does do this but needs to know for his KAV30. If so, does the KAV$BUS_WRITE facilitate this? Should an Ada access type using the selected component ".ALL" also facilitate a burst mode transfer? Also, I realize this may be an Ada-specific question, but, is the KAV$BUS_WRITE using the KAV$K_WORD qualifier the only way to force 16-bit data transfers? Does anyone know if the Ada compiler should be smart enough to recognize a base type of 16 bit integers and generate word transfers rather than longword transfers? The customer sees longword transfer code generated which his device can't recognize. Thanks again, Alan P.S. The KAV30 business has definitely picked up recently here.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 62.1 | BAYERN::WOLFF | Conformism is for little minds. | Tue Jul 28 1992 16:54 | 14 | |
For transferring data into the KAV30 you can do block moves of up to 4 LW. We will not guarantee that this will always succeed, however with 4 LWs you are pretty much on the safe side. The AEON board cannot possibly doe 256 byte block moves unless it violates the rtVAX300 spec, this spec says that you have to give up the CDAL bus within 6 us to allow the SGEC chips to access memory. Due to that limitation we can only do 4 LWs max. The same thing is tru for AEON, again unless they have chosen to violate the rtVAX spec. This is documented in the KAV30 programmers guide, chapter 2, page 2-3, note 1. Tell your customer to read the documentation :-) As far as the outbound access goes we do not support block mode outbound. Julian. | |||||
| 62.2 | re: .1 | ZYDECO::BODA | Realtime Products Support | Tue Jul 28 1992 17:07 | 9 |
Hi Julian, Is it possible that outbound block mode transfers can be done, but the KAV30 just doesn't support it? I think outbound block mode transfers is what the customer was referring to regarding AEON's VME300. Thanks, Alan | |||||
| 62.3 | Yes. | EICMFG::WOLFF | Conformism is for little minds. | Thu Jul 30 1992 11:21 | 8 |
Yep that is possible. We do not have the VIC VME interface chip. This
chip does support the outbound transfer. The reason why we did not use
this chip was simple... bugs in the chip when we started the KAV30.
AEON took that risk, and VITA got the chip ready by the time AEON
shipped its product.
Julian.
| |||||