Experimental Physics and
Industrial Control System

Hello Ron，

Does the VxWorks Board Support Package (BSP) for your MVME5500 board handle VMEbus errors?

         I don’t know how to judge if the BSP handle VMEbus error!

If you remove the Delta Tau board from the VMEbus crate, just boot-up VxWorks, not EPICS, and then try to read the mailbox memory location (0xf06fa005) using the VxWorks shell's display memory command (dm), what results do you get?

         When using the d 0xf06fa005 command the MVME5500 board crashes immediately without any erro information.

         If removing the Delta Tau board from the VMEbus crate, and executing the “d 0xf06fa005” command, the v xWorks shell diplays:

         -> d 0xf06fa005                                                                      

f06fa000:            ffff ffff ffff ffff ffff ffff   *      ..........*        

f06fa010:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa020:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa030:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa040:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa050:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa060:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa070:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa080:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa090:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa0a0:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa0b0:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa0c0:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa0d0:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa0e0:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa0f0:  ffff ffff ffff ffff ffff ffff ffff ffff   *................*        

f06fa100:  ffff ffff                                 *................*        

value = 21 = 0x15  

 

If the MVME5500 board crashes and the VxWorks console becomes unresponsive, then you have a VxWorks BSP problem with it handling VMEbus errors, which makes it almost impossible to diagnose what, if any, problems you are having with TPMAC and the Delta Tau board.
         Do you know how to add the VMEbus erro handling functions?

 

Zhaohong

 

发件人: Ron Sluiter [mailto:[email protected]]
发送时间: 2016年12月10日 5:51
收件人: zzh; [email protected]
主题: Re: 答复: MVME5500 and turbo-pmac-vme-ultralite

 

Hello Zhaohong,

Does the VxWorks Board Support Package (BSP) for your MVME5500 board handle VMEbus errors?

If you remove the Delta Tau board from the VMEbus crate, just boot-up VxWorks, not EPICS, and then try to read the mailbox memory location (0xf06fa005) using the VxWorks shell's display memory command (dm), what results do you get?

If the MVME5500 board crashes and the VxWorks console becomes unresponsive, then you have a VxWorks BSP problem with it handling VMEbus errors, which makes it almost impossible to diagnose what, if any, problems you are having with TPMAC and the Delta Tau board.

Ron

On 12/8/2016 5:42 PM, zzh wrote:

Hello Ron,

 

It seems that the EPICS driver is Ok. The problem may be the communication between the 5500 and pmac.

The controller is without DPRAM. And I use the TPMAC-3-11 for EPICS control.

 

The VME was setup as,

I90=$39, I91=$4, I92=$FF,I93=$7F, I94=$A0, I95=$1,I96=$A1, I97=$46, I98=$60,I99=$A

 

In the startup scripts(st.cmd file), the system was configured as,

         pmacVmeConfig(0,0x7fa000,0,0xa1,1)

         pmacAsynConfig( "PMAC_MBX_PORT_", 0 )

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

        

AND I loaded a simple db,

         record(stringin, "motorStrCmd") {

                 field(FLNK, motorStrRsp.PROC PP MS")

}

 

record(stringout, "motorStrRsp") {

                 field(DTYP, "PMAC-VME ASCII")

                 field(DOL, motorStrCmd.VAL NPP MS")

                 field(OMSL, "closed_loop")

                 field(OUT, "#C0S1 @#8")

}

 

 

After I executed the “caput motorStrCmd ‘j=1000’” command, the ioc printed no error information. But the pmac controller seemed to have no resonse. The pewin32pro software was running simultaneously.

 

The debug information shows:

         0x1ec62bd0(cas-client): devPmacMbxSo_write command [#8j=1000]

         0x1ec62bd0(CAS-client): drvPmacMbxScan: rngBufPut completed.

 

I am looking forward to your reply.

 

Best regards.

 

发件人: Ron Sluiter [mailto:[email protected]]
发送时间: 2016年12月8日 23:04
收件人: zzh; [email protected]
主题: Re: MVME5500 and turbo-pmac-vme-ultralite

 

On 12/6/2016 11:03 PM, zzh wrote:

the 5500 and pmac will both crash immediately.

Is there a crash message from VxWorks on the 5500? If so, what exactly is the message?

Does anyone has experiences with the 5500+pmac-vme-mailbox?

I have some experience with Delta Tau Turbo PMAC2 VME Ultralight used with various VME CPU boards (5100/6100), but not the 5500.

Ron