| 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 |
I have problems with KAV$ functions:
1) a problem with KAV$SET_CLOCK.
The C declaration format in the KAV manual is:
int kav$set_clock ([int *status,]
int clock_functions)
but the status that the function returns is unknown
( while the function is working fine !)
How should I interpret the status value returned?
2) a problem with KAV$CHECK_BATTERY.
The C declaration format in KAV manual is:
int kav$check_battery (int *status)
The status returned is %KERNEL-F-BAD_COUNT in every case!
I think the correct declaration should be
int kav$check_battery( void )
Is this correct ?
3) Can I read the switch 5 (bus arbiter) of the KAV30
from my program ? If yes, how ?
4) I read ( release note KAV30 ) that I can use the diagnostic
error information, but the example program doesn't say how this
information is stored. May I have more information about that?
Thanks in advance.
Best Regards,
Marco Cavallotto
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 93.1 | BAYERN::WOLFF | Conformism is for little minds. | Tue Jun 15 1993 09:27 | 22 | |
>> 1) a problem with KAV$SET_CLOCK. Fixed in VAXELN V4.4 >> 2) a problem with KAV$CHECK_BATTERY. Fixed in VAXELN V4.4 >> 3) Can I read the switch 5 (bus arbiter) of the KAV30 No, but there is a LED in the front - won't help you much I guess. >> 4) I read ( release note KAV30 ) that I can use the diagnostic We do not publish the internal format of how the information is stored. The errorlog information is stored in NVRAM. This area is inaccessible for normal user programs, but only accessible thru the system service Gather_ErrorLog. However the errorlog is stored (If I remember right) as a ring buffer where the oldest information (ie Errors) get overwritten eventually. Julian. | |||||
| 93.2 | STAR::NORDH | OpenVMS Development, DTN 381-1672 | Thu Jul 08 1993 16:04 | 10 | |
Re .1: >>>However the errorlog is stored (If I remember right) as a ring buffer where >>>the oldest information (ie Errors) get overwritten eventually. Thats correct, the errorlog information is stored as a ring buffer, wow you remembered it correctly Julian! :) -Jan (former KAV30 kernel developer) | |||||