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  <20112012  2013  2014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: vxWorks network problems
From: "Steven M. Hartman" <hartmansm@ornl.gov>
To: Andrew Johnson <anj@aps.anl.gov>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Tue, 24 May 2011 09:04:01 -0400
Hello Andrew--

On Mon, 23 May 2011, Andrew Johnson wrote:

I found and fixed a few issues in the dec21x40End.c driver for vxWorks 5.5.x
in 2009.  The main one was to make DMA underflow a recoverable event (which
might be relevant to this problem), but I also fixed the packet counting which
wasn't working properly in this driver.  I believe I sent Dave Thompson my
fixes at the time, but whether they got into the SNS version or not I don't
know.

If it was 2009, then I don't think your fixes made it in to the SNS BSP. That BSP pre-dates my arrival at SNS in 2008. But I will check with Dave. Thanks.

On a related question, have you ever heard of an mv2100 BSP for vxWorks 6.x?
I'm currently working on upgrading the mv2700 BSP from 6.4 to 6.8, but I can't
find an mv2100 BSP for any 6.x OS version at the Wind River website.

When I checked, Wind River was not going to provide a 6.x BSP for the mv2100. I looked briefly at the VxWorks 6 BSP porting guide, and it did not seem too difficult. However, with the bad experiences SNS has had with the mv2100, I did not think it was worth the effort. (Future budgets may lead us to reconsider, though.) At this point, we are leaving our 2100s at 5.5 and using 6.7 for our mv5500 boards.

--
Steven Hartman
hartmansm@ornl.gov

Navigate by Date:
Prev: Suggestion for IOC log server Abadie Lana
Next: Re: vxWorks network problems Steven M. Hartman
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: vxWorks network problems Andrew Johnson
Next: When a record is changed twice very fast, camonitor only detects first change Mikel Rojo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·