Re: VxWorks 6.9

["Bjorklund, Eric A" <bjorklund@lanl.gov>]

Hi Stefen

The short, blunt, answer is “Yes”.  That is why people like Andrew and I use modified BSP’s.  WR is also a little funky in the way they handle A32 space.  A32 addresses are mapped starting at 0x08000000 and the first 256K is ear-marked for inter-SBC communication across the backplane (making that section useless for hardware addressing).  Andrew and I have mods for that too.

-Eric Bj.

On Jan 27, 2016, at 10:23 PM, Stefen Paul <stefen4114@gmail.com> wrote:

Hi Andrew,

Thanks for the mail.

I think I will prefer the first option that involves some tweaking in the BSP.

Because I feel it will be more systematic and persistent.

So please share the information about the same.

I would also like to draw your attention to my initial query:

" Is it true that VxWorks 6.9 BSP for MVME-5500 can't make use of VME64  addressing capabilities even if the SBC on which it is running has this feature ?

  Because in config.h I can see only A16, A24 and A32 address space details."

Regards, 

Stefen.

On Sat, Jan 23, 2016 at 3:58 AM, Andrew Johnson <anj@aps.anl.gov> wrote:

Hi Stefen,

On 01/22/2016 06:06 AM, Stefen Paul wrote:
> I have one more query regarding VxWorks 6.9 on MVME5500.
>
> How can one access CR/CSR portion of a peripheral board from either the
> vxWorks prompt or a simple C program ?

Unfortunately this is not a simple thing to do.

The "correct" way to give access to the CR/CSR address space is to
modify your BSP to configure a VME Master window which addresses it.
There was a conversation about doing this on tech-talk recently:
  http://www.aps.anl.gov/epics/tech-talk/2016/msg00051.php
However Eric's presentation was about the MVME6100 board which has a
Tundra TSI-148 chip for its VME interface. Your MVME5500 board uses the
Universe-2 chip, so Eric's code won't work for you, but I have made
equivalent changes to the MVME5100 board which we use here at the APS,
and I can publish my changes on tech-talk if you want to see them. You
won't be able to apply them directly to the mv5500 BSP since the board's
memory map is different, but the two are close enough that most of the
code should be the same.

There is a simpler way to get access to that space, which involves
temporarily changing the mapping of the VME A24 Master window to access
CR/CSR space, doing what you need and then changing the window back to
access A24 space. I would only suggest using this on a system where you
only need to access that space for a very short period of time and you
know that no other VME drivers could be handling interrupts or trying to
access hardware in the VME A24 space at the time you have the window
re-mapped. Typically that means that you would only need to do this once
to configure some registers on the peripheral board, and that you can do
that configuration before any other board gets fully initialized.

Let me know which of those two options you prefer.

- Andrew

--
There are only two hard problems in distributed systems:
  2. Exactly-once delivery
  1. Guaranteed order of messages
  2. Exactly-once delivery
 -- Mathias Verraes