Experimental Physics and
Industrial Control System

Hello Makarow,

         You are right as the reference says “VME bus interrupts which can be assigned a value by the user should be confined to numbers in the range 0xc0 thru 0xff”.

         At the beginning, I used the correct interrupt vector such as 0xC1, but it is Failure to connect interrupt.

         Today I tried the 0xC1 again. And copied the error information as following:

                  

                   pmacVmeConfig(0,0x7FA000,0,0xC1,1)

pmacVmeConfig: Failure to connect interrupt.

value = 34144258 = 0x2090002

pmacAsynConfig( "PMAC_MBX_PORT_", 0 )

value = 0 = 0x0

pmacDrvConfig(0,0,0,0,"PMAC_MBX_PORT_0")

pmacDrvConfig: unable to connect to asynPort PMAC_MBX_PORT_0 value = -1 = 0xffffffff

 

         So the previous unresponsive phenomenons may because the wrong interrupt vector provided in the st.cmd script.

         And the problem is confined to why the driver cann’t connect the interrupt vector.

 

         Zhaohong

                  

Message: 1

Date: Mon, 12 Dec 2016 10:23:04 -0600

From: "Oleg A. Makarov" <[email protected]>

To: <[email protected]>

Subject: Re: ??: ??: MVME5500 and turbo-pmac-vme-ultralite

Message-ID: <[email protected]">[email protected]>

Content-Type: text/plain; charset="utf-8"; Format="flowed"

 

Hello Zhaohong,

 

With MVME5500 board PMAC should use interrupts in the *0xc0 - 0xff *range, see reference below.

I suggest you change I96 to $C1 and use this value here:

pmacVmeConfig(0,0x7fa000,0,0xc1,1)

 

Oleg Makarov