Ned Arnold wrote:
>
> For an even simpler way of poking at memory, place the following in the
> startup script :
>
> vxMemProbe(0xfffe102b,1,1,&(mydata = (char)0x0))
I like the idea of using vxMemProbe to poke values into memory - I've
been wondering how to do this from a startup script for ages. Can I
suggest the following simplification, which avoids the need to create
the local symbol mydata:
vxMemProbe(0xfffe102b,1,1,"\0")
In fact just "" without the \0 ought to work, but it's slightly less
obvious what value is being poked then.
-- Andrew
___
.' `. Andrew Johnson, Head of Electronics
/ Royal ) Royal Greenwich Observatory
\ Greenwich Madingley Road, Cambridge, CB3 0EZ
| Observatory Tel: +44 1223 374823 Fax: 374700
+---------- WWW: http://www.ast.cam.ac.uk/~anj
- References:
- Re: NI-1014 help needed Ned Arnold
- Navigate by Date:
- Prev:
Re: NI-1014 help needed Ned Arnold
- Next:
[Fwd: EPICS: Error in db/callback.c] Marty Kraimer
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: NI-1014 help needed Ned Arnold
- Next:
BUG(?) in AR.c and AR_cmd.c Noboru Yamamoto
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|