Note: Possible bug? Failure to initialise crate or vme on first occasion since power on ...
This note is an extension of that in TestingSctRodDaq 4 1
It seems there may be a bug of unknown origin causing ROD initialisation to occur on the first (and only the first) time since crate power-on:
(10:55:01) lester: I have noticed with 4.1 (10:55:07) lester: (probably also with head) (10:55:50) lester: that initialising the vme bus seems to fail on the very first occasion (since the crate has been turned on, that is) but not on any subsequent occasion. (10:56:14) alan: Interesting (10:56:25) alan: I've seen similar problems. (10:56:42) lester: Under normal running you get the (10:56:45) alan: which DF are you using for initialising VME? (10:56:54) lester: (10) (10:57:16) lester: normally you get the (10:57:26) lester: "Sucessfully initialisaed VME interface" message, (10:57:31) lester: 5 second pause (10:57:43) lester: "ROD initialissed" (10:57:46) lester: 5 second pause (10:57:52) lester: and then other things happen (10:58:02) lester: What happens ()instead) on first power on seems to be (10:58:15) lester: the last 5 second pause becomes a very long one (10:58:18) lester: (more than 5 seconds) (10:58:27) lester: and then something corba (or IPC) (10:58:33) lester: times out on a CORBA transient
Further to the above, now that I have re-enabled some of the debug output in SctApi we see the some MRS messages that may be relevent. Here is a sample:
TEXTBUFF_ARRIVE DIAGNOSTIC [MDSP: rodConfiguration.c, 735]::Configuring ROD: initialization mode. 1305 vme3 2005/Feb/21 16:34:40 SCTAPI partition 0 crate 0 rodSlot 5 Type INFO Text [MDSP: rodConfiguration.c, 735]:: Configuring ROD: initialization mode. ROD_INIT INFORMATION ROD Initialised 1305 vme3 2005/Feb/21 16:34:40 SCTAPI number 0 slot 5
TEXTBUFF_ARRIVE DIAGNOSTIC [SDSP 0: utilities.c, 615]::SCT DSP code version 1.2.0 Jan 27 2005 1304 vme3 2005/Feb/21 16:34:41 SCTAPI partition 0 crate 0 rodSlot 5 Type TRANSFER Text [SDSP 0: utilities.c, 615]:: SCT DSP code version 1.2.0 Jan 27 2005
TEXTBUFF_ARRIVE DIAGNOSTIC [SDSP 0: utilities.c, 615]::SCT DSP code version 1.2.0 Jan 27 2005 1304 vme3 2005/Feb/21 16:34:41 SCTAPI partition 0 crate 0 rodSlot 5 Type TRANSFER Text [SDSP 0: utilities.c, 615]:: SCT DSP code version 1.2.0 Jan 27 2005
TEXTBUFF_ARRIVE DIAGNOSTIC [MDSP: smGetSlvTxtBuff.c, 202]:: Error 0x61a occurred in smGetSlvTxtBuff with severity 2. The tr 1304 vme3 2005/Feb/21 16:34:41 SCTAPI partition 0 crate 0 rodSlot 5 Type ERROR Text [MDSP: smGetSlvTxtBuff.c, 202]:: Error 0x61a occurred in smGetSlvTxtBuff with severity 2. The transfer buffer is full! TEXTBUFF_ARRIVE DIAGNOSTIC [MDSP: smGetSlvTxtBuff.c, 202]:: Error 0x61a occurred in smGetSlvTxtBuff with severity 2. The tr 1304 vme3 2005/Feb/21 16:34:42 SCTAPI partition 0 crate 0 rodSlot 5 Type ERROR Text [MDSP: smGetSlvTxtBuff.c, 202]:: Error 0x61a occurred in smGetSlvTxtBuff with severity 2. The transfer buffer is full!
Here is a full copy of the mrs log.
On second boot, none of the "Error 0x61a" messages are generated.