EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: VxWorks 6.9
From: Stefen Paul <[email protected]>
To: EPICS Tech Talk <[email protected]>
Date: Fri, 15 Jan 2016 11:29:48 +0530
Hi,

As most of you must be aware that a VME bus-error is a condition when there is no/unresponsive peripheral board preset at the address that is put on the bus by CPU for a read/write cycle.

While using and reading about MVME5500 (with vxworks 6.9), I have realized that it is not possible to precisely catch a VME bus-error in software while doing a write operation on a peripheral board. This ,as I learnt, is due to the PCI bus based architecture of the board which uses write-posting.

However, one can catch a VME bus-error during a read cycle as reading is done immediately from the peripheral board.

Is this scenario same for all other CPU boards also (whether PowerPC or Intel based ) that have PCI bus based architecture.

Regards,
Stefen.

On Thu, Jan 14, 2016 at 10:52 AM, Stefen Paul <[email protected]> wrote:
Hi Andrew,

I am referring to BSP for MVME-5500 board.

Thanks,
Stefen.

On Wed, Jan 13, 2016 at 9:36 PM, Andrew Johnson <[email protected]> wrote:
Hi Stefen,

On 01/13/2016 06:41 AM, Stefen Paul wrote:
> Is it true that VxWorks 6.9 BSP can't make use of VME64 or VME64x
> 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.

That depends on the BSP (you didn't tell us which board/BSP you're
using), but you could be right. Over the 15 years I've been maintaining
BSPs for the APS I have added many features to our BSPs which did not
come with the originals from Wind River. I have made several of those
changes available to the EPICS community through tech-talk, which you
can find by searching the archives, but please note that I can't publish
the full BSP code because the original BSPs are proprietary software,
not Open Source.

If you explain what you're looking for in a bit more detail there are
several people on this list who might be able to help.

- 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



Replies:
Re: VxWorks 6.9 Andrew Johnson
References:
VxWorks 6.9 Stefen Paul
Re: VxWorks 6.9 Andrew Johnson
Re: VxWorks 6.9 Stefen Paul

Navigate by Date:
Prev: Re: Re:Re: Re:Re: EPICS Multiple Archiver Appliance problem Shankar, Murali
Next: RE: Dynamically refresh CSS BOY runtime OPI Mazanec Tomáš
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: VxWorks 6.9 Stefen Paul
Next: Re: VxWorks 6.9 Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Jul 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·