Re: Re: RTEMS 5 Cannot Read Event Generator

[chengsn via Tech-talk <tech-talk at aps.anl.gov>]

1. You're right. I mistyped the configuration of the A24 address in the mail, it should have been 0x180000. I checked my st.cmd file and it did configure 0x180000, not 0x1800000.

2. Yes, I do not use the mrfioc2 module.

3. Sorry, I did not express the situation clearly. RTEMS 5 can read the EVR just like vxWorks, but cannot read the EVG.

4. I do the test again and confirm that the A24 address of EVG is set to 0x180000, and the error message returned EgConfigure: Unable to read Event Generator Card 0 (slot 3) at VME/A24 address 0x180000.

Thanks for your help!

chensn

IHEP

-----Original Messages-----
From:"Andrew Johnson" <anj at anl.gov>
Sent Time:2022-08-18 00:42:18 (Thursday)
To: chengsn at ihep.ac.cn, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Cc:
Subject: Re: RTEMS 5 Cannot Read Event Generator

Hi,

On 8/17/22 4:03 AM, chengsn via Tech-talk wrote:

I try to running the mrfEventSystem driver with EPICS 7 on RTEMS 5. After modifying part of the code, the driver can read the EVR(EVent Reciever) Card, and it works well. But when I run the driver and use the EVG(EVent Generator), I get this error: EgConfigure: Unable to read Event Generator Card 0 (slot 3) at VME/A24 address 0x1800000.

In st.cmd file, the configuration for the EVG is EgConfigure(0, 3, 0x1800000). When I change the OS from RTEMS to vxWorks(on MVME6100 and MVME5500), the driver can read the EVG.

0x1800000 = 0x01800000 is not a valid VME A24 address, it has too many digits set to fit into 24 bits. Have you tried say 0x00800000 instead, or did you mean 0x00180000?

Here is the hardware I am using:

 EVG: VME-EVG-230.

 EVR: VME-EVG-230-RF. 

 Single board computer: MVME6100 and MVME5500.

The software:

 mrfEventSystem Driver Version: MRF Series 200 Event System Software Release V2-4.

Ahh, that's not the mrfioc2 module which explains why you're using EgConfigure() to register the card.

The value of ret: EVR returns 0; EVG returns 0x88FD0000 (in vxWorks and RTEMS, sizeof(long) = 8).

Do you have any suggestions?

The fact that you can talk to the EVR at that address from one OS but not the other implies that VxWorks may be masking off the high byte to generate its A24 address, but RTEMS doesn't.

The other suggestion I have for that situation would be that the VME address modifiers used might be different from the two VME bus interface drivers, but I think you should fix the address length before looking into that.

HTH,

- Andrew

-- 
Complexity comes for free, Simplicity you have to work for.