Leng Yongbin wrote:
>
> So we select a solution consisting of MVME2302, VIPC616, and GSOctal IP module. We also download the Ipac2.2 package.
> But we failed set up this device driver from within a vxWorks startup script. The information is as follows:
>
> ipacAddCarrier &vipc616,"0x6000"
> value = 0 = 0x0
> MODO = tyGSOctalModuleInit("GSIP_OCTAL232",0x80,0,0)
> 0x1bef5d0 (tShell): tyGSOctalModuleInit: No memory allocated for carrier
The last line above is a hint to your problem. The GreenSpring Octal232
module needs more register space than is normally available in the IPAC
module Register area, so it also needs the carrier to provide some memory
space for its interrupt vector register. There are jumpers on the VIPC616
that set the A24 base address for the IPAC memory space (I strongly
suggest you do not use A32 space because that will need changes to your
vxWorks build). You will also need to provide additional arguments in the
ipacAddCarrier initialization string to tell the carrier driver where and
how much memory you have set them up for - use the smallest 64KB setting,
and read the VIPC616 section of the drvIpac documentation for details.
- Andrew
--
Every great idea appears crazy to start with.
- References:
- Problems with GSOctalRS232 Leng Yongbin
- Navigate by Date:
- Prev:
Re: longoutRecord Bug Marty Kraimer
- Next:
RE: Problems with GSOctalRS232 Mark Rivers
- 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:
Problems with GSOctalRS232 Leng Yongbin
- Next:
RE: Problems with GSOctalRS232 Mark Rivers
- 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
|