Andrew Johnson wrote:
> Strictly speaking Jeff's comment about making these items volatile is
> incorrect, because I know they're all in a PROM on the IPAC module and
> hence cannot change at run-time. However this does actually solve the
> problem because gcc cuts out the optimisation. Change the beginning of
> the ipmCheck routine by adding the volatile keyword to the definition of
> id to produce the following:
>
> int ipmCheck (
> ushort_t carrier,
> ushort_t slot
> ) {
> volatile ipac_idProm_t *id;
> char dummy;Q
>
Well, thanks to everybody for the prompt replies. The volatile keyword
did the trick.
Additional note:
We got our CAN-bus running today. We are using the TIP810 industry pack
on an MV162 (Andrew's documentation says this driver is not tested, as
he runs carrier boards). We had to add a call to ipmIrqCmd to enable the
ipic interrupt on the MV162.
- rolf -
--
+----------------------------------------------------------+
: Rolf Keitel | [email protected] :
: TRIUMF | Tel: (604) 222-7453 :
: 4004 Wesbrook Mall | Fax: (604) 222-7307 :
: Vancouver, B.C., V6T 2A3 | www.triumf.ca :
+----------------------------------------------------------+
- References:
- gnu cross-compiler problem Rolf Keitel
- Re: gnu cross-compiler problem Andrew Johnson
- Navigate by Date:
- Prev:
Re: gnu cross-compiler problem Steve Lewis
- Next:
[no subject] Bill Stewart
- 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: gnu cross-compiler problem Andrew Johnson
- Next:
Re: gnu cross-compiler problem Steve Lewis
- 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
|