From vxwexplo-errs@csg.lbl.gov  Fri Nov  1 04:03:31 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Fri Nov  1 04:03:33 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Fri Nov  1 04:03:28 PST 2002

        Subject: Re: sysClkRate reasonable values..
        Subject: Re: GetTickCount
        Subject: Re: Bootrom size question
        Subject: Re: sysClkRate reasonable values..
        Subject: Re: sysClkRate reasonable values..
        Subject: Re: vxWorks BSP manual needed
        Subject: Re: vxWorks BSP manual needed
        Subject: Re: Bootrom size question
        Subject: Re: WindRiver Tornado problem: ftp server with wu-ftpd in Linux
        Subject: Re: MPC8260  lock up  when FCC1 configured for ATM, SBC8260 board
        Subject: Re: TCP/IP stacks performance
        Subject: Re: The infamous "No rule to make target" problem
        Subject: Power PC 24 bit relocation and -mlongcall
        Subject: Re: x86 based PC104 CPU Board
        Subject: Re: Linux
        Subject: Re: Request for tylib.c source code.
        Subject: recent developmwnts
        Subject: Re: MPC860 training suggestions
        Subject: Re: Tornado/VxWorks newbie question
        Subject: Re: TCP/IP implementation concept under RTOS like uCOS II
        Subject: Re: WDB Configuration error
        Subject: End Drvier can ping, but socket not working
        Subject: Re: The infamous "No rule to make target" problem
        Subject: Bind PPP on top of non-standard device (RLP 3 stream, 3G simulation)
        Subject: Re: Linux
        Subject: Re: End Drvier can ping, but socket not working
        Subject: System boot up time
        Subject: Re: System boot up time
        Subject: Re: Tornado/VxWorks newbie question
        Subject: Re: End Drvier can ping, but socket not working
        Subject: Re: System boot up time

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: sysClkRate reasonable values..
Date: Wed, 30 Oct 2002 14:44:52 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$0sos4h$zs1$1@lnews.actcom.co.il>
References: <1035882002.428469@newsreader2.wirehub.nl> <29b153d9.0210291302.5b6b717c@posting.google.com> <apog15$fv2$1@knossos.btinternet.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:apog15$fv2$1@knossos.btinternet.com...
>
> >   Increasing the system clock to 1000Hz is generally not advisable.
> > Each tick causes the kernel to wake up and see what needs to be done.
> > This activity consumes CPU cycles, and is the overhead associated with
> > an RTOS.
>
> But it is still slow for a modern cpu.  60Hz (US power freq) was used
> for slow 68k systems.  Most modern cpus run fast enough that it is
> unlikely to be a problem.
> Remember you won't affect the system interrupt latency by increasing
> the frequency of the timer interrupt.
>
> David
>

David, several years ago one of my clients had a 1KHz sys clock on a
68k based VME system without any problem at all, except a few precent
overhead fot the timing processing.
In otehr cases, I found out that 100Hz is a much greater choise then the
legacy 60Hz value, I wonder why that is still the default.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: GetTickCount
Date: Wed, 30 Oct 2002 14:03:52 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1035983093.430589@newsreader2.wirehub.nl>
References: <ecca3ca6.0210300354.5288b145@posting.google.com>

Sorry about this one, but why dont you read the manual?
tickGet should do the trick.
Number of seconds sinds startup is:
  seconds =  tickGet() / sysClkRateGet();

Cheers,
Renee
- - - - - - - - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

"Ravi Uday" <ravi368@yahoo.com> wrote in message
news:ecca3ca6.0210300354.5288b145@posting.google.com...
> Hi,
>
> The GetTickCount function retrieves the number of milliseconds that
> have elapsed since the system was started. It is limited to the
> resolution of the system timer.
> DWORD GetTickCount(VOID);
> Its an windows implementation.
>
> Can i have an equivalent which works on VxWorks ?
> Thanks for u support in advance
>
> Ravi

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Bootrom size question
Date: 30 Oct 2002 07:24:11 -0800
From: kiranmandava@hotmail.com (kmandava)
Organization: http://groups.google.com/
Message-ID: <d656e178.0210300724.413151aa@posting.google.com>
References: <apn93j$sei$1@newpoisson.nosc.mil>

>owen@manta.nosc.mil (Wallace E. Owen) wrote in message >news:<apn93j$sei$1@newpoisson.nosc.mil>...
> I'm trying to build a moderately large (~1.2MB text segment) app to be
> booted and run from a floppy on an embedded PC.  A helloworld app builds
> fine, but when I try to make my full app's boot image, romsize complains
> that the imagre is ~600K too large.  I adjusted the RAM_LOW_ADRS from
> 0x00108000 to 0x00208000, and changed the ROM_SIZE from 0x00090000 to
> 0x00190000 thinking that this would make enough room for the image and
> the boot loader (I'm trying to make my app boot from floppy).  The app
> builds without complaint, but it just hangs after the loader loads it.
> 
> Any clues appreciated.
> 
> 
>   // Wally

If it is the bootrom which gets loaded from the floppy, RAM_HIGH_ADRS
is the one you would be interested right.! where is ROM_HIGH_ADRS
ponited to..!

//kiran

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: sysClkRate reasonable values..
Date: Wed, 30 Oct 2002 15:26:33 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <apotn8$cpp$1@sparta.btinternet.com>
References: <1035882002.428469@newsreader2.wirehub.nl> <29b153d9.0210291302.5b6b717c@posting.google.com> <apog15$fv2$1@knossos.btinternet.com> <newscache$0sos4h$zs1$1@lnews.actcom.co.il>

> David, several years ago one of my clients had a 1KHz sys clock on a
> 68k based VME system without any problem at all, except a few precent
> overhead fot the timing processing.

Doesn't surprise me, I suspect the (very) early unix systems (eg for
pdp11) used a 60Hz (or line freq) timer interrupt.  They are (probably)
slower than a 68000 and have a longer timer ISR that vxworks.

> In other cases, I found out that 100Hz is a much greater choise then the
> legacy 60Hz value, I wonder why that is still the default.

Probably because noone dare change anything because they don't know how
it works any more :-)
I ran our vxworks system with 100Hz clock (60Hz us just plain stupid
given the interfaces you have to support).  I also fixed my code for
faster clocks.  Does get tricky when the taskDelay(1) calls have to
be stretched. IIRC I used things like
	taskDelay(sysClockRateGet()/64u + 1);

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: sysClkRate reasonable values..
Date: Wed, 30 Oct 2002 17:08:27 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1035994169.359135@newsreader2.wirehub.nl>
References: <1035882002.428469@newsreader2.wirehub.nl> <29b153d9.0210291302.5b6b717c@posting.google.com> <apog15$fv2$1@knossos.btinternet.com> <1035982934.89356@newsreader2.wirehub.nl> <apotu5$hrh$1@venus.btinternet.com>

Disassembling the driver is what would have done if our BSP vendor
said he would look into it. Our expiriences with VMIC are in such a
way that I trust them that they do. Assembler isnt my trade, but it's
getting better every time ;)

Thanx,
Renee.

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:apotu5$hrh$1@venus.btinternet.com...
> Renee Teunissen wrote:
> > therefore we were thinking of setting the clockrate to 1000,
>  > to get it in a 1ms grid.
>
> 1000 should be fine, don't go above 2147 though there are some
> integer overflow problems lurking.
>
> > But this does not solve the problem. I talked about it with our
BSP
> > vendor, to see what they can to. Our intel 82559 FEI-driver is
closed
> > source, so I dont know if they are doing a taskDelay(60) to wait
for a
> > single second.. this scares the creeps out of me...
>
> Disassemble the driver code and have a look!  It won't be that big.
>
> David
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: vxWorks BSP manual needed
Date: Wed, 30 Oct 2002 16:48:36 GMT
From: "Chad" <ckrueger@NOSPAM.thomsontechnology.com>
Organization: Shaw Residential Internet
Message-ID: <E3Uv9.633291$Ag2.24389485@news2.calgary.shaw.ca>
References: <CwYr9.216$zE6.1018@rwcrnsc51.ops.asp.att.net> <Vyyv9.638993$f05.26480793@news1.calgary.shaw.ca> <3DBF0B89.692D@despam.autobahn.mb.ca> <Xns92B6DECE67C2jborkhuisproximcom@192.19.193.66>

sure thing.

"Johan Borkhuis" <JBorkhuis@proxim.com> wrote in message
news:Xns92B6DECE67C2jborkhuisproximcom@192.19.193.66...
> "H. E. Taylor" <het@despam.autobahn.mb.ca> wrote:
>
> > In article <Vyyv9.638993$f05.26480793@news1.calgary.shaw.ca>,
> ><ckrueger@NOSPAM.thomsontechnology.com> Chad wrote:
> >> I found a document entitled "VxWorks - Device drivers in a nutshell"
> >> which I believe was gnu public licensed several months ago, I found
> >> it quite informative and if I can dig it up I'll email it to you.  It
> >> gives a general device driver framework and example, though I believe
> >> (I've yet to look into it in too much detail) things have changed a
> >> bit in vxWorks 5.5.
> >>
> >
> >      Could you put it on the web, or alternatively
> >      could someone else [Johann?] in the group?
> >      This type of doc is frequently requested, but
> >      unfortunately I don't have online room for it myself.
> >      [I'm near my 10 meg limit.]
>
> If you send it to me (or tell me where to find it) I will put it on the
> site.
>
> Kind regards,
>         Johan
>
> --
>         o o o o o o o . . .   _____________________________
>        o      _____           ||    Johan Borkhuis        |
>      .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
>     >(________|__|_[_________]_|__________________________|
>     _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
> === VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: vxWorks BSP manual needed
Date: Wed, 30 Oct 2002 16:56:34 GMT
From: "Chad" <ckrueger@NOSPAM.thomsontechnology.com>
Organization: Shaw Residential Internet
Message-ID: <6bUv9.633371$Ag2.24390434@news2.calgary.shaw.ca>
References: <CwYr9.216$zE6.1018@rwcrnsc51.ops.asp.att.net> <Vyyv9.638993$f05.26480793@news1.calgary.shaw.ca> <3DBF0B89.692D@despam.autobahn.mb.ca> <Xns92B6DECE67C2jborkhuisproximcom@192.19.193.66>

In fact here is the original source, I had thought for some time this site
was no longer available.

http://www.ayyalasoft.com/Drivers.htm it is listed at the end of this page
as reference material.

Cheers,
Chad

"Johan Borkhuis" <JBorkhuis@proxim.com> wrote in message
news:Xns92B6DECE67C2jborkhuisproximcom@192.19.193.66...
> "H. E. Taylor" <het@despam.autobahn.mb.ca> wrote:
>
> > In article <Vyyv9.638993$f05.26480793@news1.calgary.shaw.ca>,
> ><ckrueger@NOSPAM.thomsontechnology.com> Chad wrote:
> >> I found a document entitled "VxWorks - Device drivers in a nutshell"
> >> which I believe was gnu public licensed several months ago, I found
> >> it quite informative and if I can dig it up I'll email it to you.  It
> >> gives a general device driver framework and example, though I believe
> >> (I've yet to look into it in too much detail) things have changed a
> >> bit in vxWorks 5.5.
> >>
> >
> >      Could you put it on the web, or alternatively
> >      could someone else [Johann?] in the group?
> >      This type of doc is frequently requested, but
> >      unfortunately I don't have online room for it myself.
> >      [I'm near my 10 meg limit.]
>
> If you send it to me (or tell me where to find it) I will put it on the
> site.
>
> Kind regards,
>         Johan
>
> --
>         o o o o o o o . . .   _____________________________
>        o      _____           ||    Johan Borkhuis        |
>      .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
>     >(________|__|_[_________]_|__________________________|
>     _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
> === VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Bootrom size question
Date: 30 Oct 2002 09:22:47 -0800
From: cherubhollyhock@yahoo.com (Karen)
Organization: http://groups.google.com/
Message-ID: <b30aa455.0210300922.230ad01c@posting.google.com>
References: <apn93j$sei$1@newpoisson.nosc.mil>

owen@manta.nosc.mil (Wallace E. Owen) wrote in message news:<apn93j$sei$1@newpoisson.nosc.mil>...
> I'm trying to build a moderately large (~1.2MB text segment) app to be
> booted and run from a floppy on an embedded PC.  A helloworld app builds
> fine, but when I try to make my full app's boot image, romsize complains
> that the imagre is ~600K too large.  I adjusted the RAM_LOW_ADRS from
> 0x00108000 to 0x00208000, and changed the ROM_SIZE from 0x00090000 to
> 0x00190000 thinking that this would make enough room for the image and
> the boot loader (I'm trying to make my app boot from floppy).  The app
> builds without complaint, but it just hangs after the loader loads it.
> 
> Any clues appreciated.
> 
> 
>   // Wally

I have no clue about your app. 

Does your app use any func that's not available at boot time? I assume
at that time the VxWorks OS isn't running yet.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: WindRiver Tornado problem: ftp server with wu-ftpd in Linux
Date: Mon, 28 Oct 2002 10:06:53 +0000 (UTC)
From: Jeff Zheng <zhengzhe@hotmail.com>
Organization: Your Company
Message-ID: <apj27t$22jh$1@mail.cn99.com>
References: <3DB8D84A.70601@ms3.senao.com.tw>

Hi Richard:
    	VxWorks is known not to work well with unix ftp server. In fact it
    is not the problem of the ftp server but between the vxWorks tcp and
    unix tcp.
    	Where did u boot stop? are u using the vxWorks.sym? if the boot
    stopped at downloading vxWorks.sym then your problem is about the
    unix tcp. 
     You may search google newsgroup vxWorks TIME_WAIT for detail
     information. 

Jeff Zheng

Richard Wang <richard.wang@ms3.senao.com.tw> wrote in
news:3DB8D84A.70601@ms3.senao.com.tw: 

> Hi,
> 
> To boot a board, I need to download the image through ftp. There are
> at least two ways to do this. I can build the server with Tornado's
> ftp server. I can also build a ftp server on another computer. When
> I tried to put downloaded image from a remote computer running Linux 
> system, I can not boot the image successfully even though I use the
> same image that just successfully booted the board through a ftp
> server on Windows, that comes with Tornado package.
> 
> Both images seem to be downloaded successfully. However, the one
> downloaded through wu-ftpd (lINUX) can not be started successfully.
> Have you have this problem before? Why? Is there other way to solve
> this? 
> 
> Thanx,
> Richard
> 
> 

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: MPC8260  lock up  when FCC1 configured for ATM, SBC8260 board
Date: Wed, 30 Oct 2002 19:50:39 +0000 (UTC)
From: "Graham Baxter" <gbaxter@NOSPAMbcs.org.uk>
Organization: BT Openworld
Message-ID: <appd6e$a0c$1@venus.btinternet.com>
References: <ccfbed74.0210301127.5dae80dd@posting.google.com>

Haluk,

The FCC Ethernet driver takes some dual-port RAM for its TX and RX FIFO
buffers.

Look at the Ethernet registers to establish where this is and make sure that
your ATM driver is also not using it. It uses the place where you are
recommended to use for the ATM tables.

I no longer have access to the source code (motfccend.c .h) but remember it
was a round address like 0x3000 or 0xB000 relative to DPRAM.

I hope this helps.

- --
Regards,

Graham Baxter
Freelance Software Engineer (VxWorks and pSOS BSPs)
Graham Baxter (Software) Limited
gbaxter@NOSPAMbcs.org.uk

"Haluk" <aral007@bellsouth.net> wrote in message
news:ccfbed74.0210301127.5dae80dd@posting.google.com...
> Hello,
> I am using FCC2 for Ethernet and wanna use FCC1 for ATM on EST
> SBC8260.
> I have a simple driver for just an internal ATM loopback,  initialize
> all registers, BD, interrupt queues, etc without a problem.
> As soon as  enable TX and RX  with  GFMR,  board locks up.
> Did anyone has the similiar problem?, any idea what is wrong ?
> thanks
> Haluk

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: TCP/IP stacks performance
Date: Mon, 28 Oct 2002 12:23:27 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$5wso4h$q3j$1@lnews.actcom.co.il>
References: <3DB98C1B.84785269@NOSPAM.slb.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Frederic" <frederic.torras@NOSPAM.slb.com> wrote in message
news:3DB98C1B.84785269@NOSPAM.slb.com...
> hi all,
>
> does anyone know where to find informations about TCP/IP stack
> performance under VxWorks ?
>
> benchmarks should be appreciate.
>
> Thanks.
>
The ultimate answer would come form your own benchmarks  that
accurately reproduce your applications behaviour pattern, and the
particular hardware you intend to use.

The performance depends on processor architecture, but even moreso
depends on the particular network interface hardware and driver
implementation.

In my expesience, the performance is usually adequate for small and
medium workload, such as distributted application or remote management.
But when heavy workload is expected, the performance of the bundled stack
is usually not satisfactory, and solution range from improvement of the
particular hardware, to total replacement of the stack.

- -- HTH
- -----------------------------------------------------------------------
   Leonid Rosenboim                Visit:
http://gamla.org.il/english/index.htm
        Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: The infamous "No rule to make target" problem
Date: 24 Oct 2002 09:24:33 -0600
From: taashlo@sandia.gov
Organization: Sandia National Laboratories, Albuquerque, NM USA
Message-ID: <of9j97wu.fsf@sandia.gov>
References: <3db57e4b$2@news.mhogaming.com> <8z0q8l6m.fsf@sandia.gov> <m27kga2xm3.fsf@sympatico.ca>
Sender: taashlo@TYPHOON

Bill Pringlemeir <spam_account@sympatico.ca> writes:
> [snip]
> 
>  Tad> At this point when I take a look at the makefile and the .prj
>  Tad> file, they both still have references to the old file
>  Tad> (pmcsio4.cpp) and no mention of the new file (serial.cpp).
> 
>  Tad> I didn't have this problem with earlier versions of Tornado
>  Tad> (2.0, 1.x).
> 
>  Tad> If you find out any way of working around this problem, please
>  Tad> let us know.
> 
> I am not sure if I know about this problem.
> 
>  "http://www.xs4all.nl/~borkhuis/vxworks/vxw_pt1.html#1.6-B"
>  "http://www.xs4all.nl/~borkhuis/vxworks/vxw_pt1.html#1.7-C"

I tried the makeGen.tcl script and it generated a makefile identical
to the one in my project.  I suspect that this is due to the .prj
file not having the dependencies in the first place.  Pushing the
"Update Dependencies" button in the Tornado IDE doesn't even
generate a new .prj file (i.e. the file time doesn't change).

> In our projects we have more than one target.  Often I get what is
> being discussed, or so I believe.  Changing the build target and
> updating dependacies seems to solve this.

Tried this and it didn't change anything.

> The "wpj" is just a list of information that a TCL script reads and
> uses to produce the make file.  The "makeGen.tcl" in Johan's FAQ uses
> these TCL files.  There are also some other Tornado files for doing
> command line builds.  I filed a TSR about this and it is fairly
> complex to set up, but it does work.  The file comments have some
> statements that aren't quite right. For example,
> 
>  "/Tornado/host/resource/tcl/app-config/Project/cmpScriptLib.tcl"
> 
> Not sure if this is the actual files I was looking at...  I just ended
> up using a modified version of "makeGen.tcl" to produce lint rules and
> emacs ebrowse files.
> 
> hth,
> Bill Pringlemeir.
> -- 
> CESID CIDA 2600 Magazine secure Skipjack basement halcon PLO Rule Psix
> USDOJ UOP Sears Tower RSA supercomputer INSCOM AES crack

Thank you Bill for trying to help.

Tad

---------------------------

Newsgroups: comp.os.vxworks
Subject: Power PC 24 bit relocation and -mlongcall
Date: 30 Oct 2002 14:26:18 -0800
From: b.beauchaine@attbi.com (Bob Beauchaine)
Organization: http://groups.google.com/
Message-ID: <15647182.0210301426.504ed3fd@posting.google.com>

I've recompiled my entire application and kernel with the -mlongcall
option.  The code loads with all symbols resolved and runs.  Well,
sort of. I see odd behavior in code that worked with 24 bit addressing
- - strange crashes, processes throwing exceptions, PCI bus interrupts
(when we're not using the PCI bus)...

Anyone else encountered this kind of problem before?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: x86 based PC104 CPU Board
Date: Wed, 30 Oct 2002 23:56:48 GMT
From: "Steve Mowbray" <steve_mowbray@hotmail.com>
Organization: blueyonder (post doesn't reflect views of blueyonder)
Message-ID: <4l_v9.3814$O_3.27564079@news-text.cableinet.net>
References: <appi08$ipv$1@news01.cit.cornell.edu>

As far as I am aware, the PC104 is basically the same as the EISA spec other
than for mechanical details (such as the form factors/connector types etc)
so the CPU card should behave like a standard PC. Others here may disagree
as I have only used OS9/WinCE on PC104, but I am willing to stick my neck
out.

The main contention you will have is that there are far fewer network (and
general expansion) cards available for the PC104 bus, so if you are using
networking you will need the appropriate VxWorks END/NPT driver and you may
need to modify the BSP accordingly.

I would suggest that you check the availability of VxWorks drivers and
expansion cards for PC104 target system as a first assessment.

Cheers
Steve

"Jin-Woo Lee" <jl206@cornell.edu> wrote in message
news:appi08$ipv$1@news01.cit.cornell.edu...
> Hello,
>
> If I have a BSP for x86 target, can I use it for any x86 based target?
> For example, is it possible to building a VxWorks boot image for PC104
> target board without any modification?
>
> If anyone is using PC104 board under VxWorks, can you inform me what model
> of the boards are?
>
> Thanks,
> Jinwoo
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Linux
Date: 28 Oct 2002 11:06:08 +0000
From: Simon Wright <simon.j.wright@amsjv.com>
Organization: Alenia Marconi Systems, ISD, Farlington
Message-ID: <x7vy98ibz6n.fsf@galadriel.frlngtn.gecm.com>
References: <d2f67bd8.0210230927.164179ce@posting.google.com>
Sender: sjw@galadriel.frlngtn.gecm.com

brian_doe@hotmail.com (brian) writes:

> Has anyone out there been told by their company, or heard of others
> being told, that they can't use Linux, due to potential GPL issues?
> I realise that the debate goes on, however Im wondering what the
> large companies with lawyers think?

You might check this with companies supplying Linux development suport
in the embedded arena; eg http://www.lynuxworks.com/ .

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Request for tylib.c source code.
Date: Thu, 31 Oct 2002 09:49:01 +0000 (UTC)
From: Johan Borkhuis <JBorkhuis@proxim.com>
Organization: Proxim Corp.
Message-ID: <Xns92B86D6A16DFBjborkhuisproximcom@192.19.193.66>
References: <WL1w9.171216$md1.37989@sccrnsc03>

"k.croswell" <k.croswell@insightbb.com> wrote:

> If anyone has an idea where I can get the tylib.c source I would greatly
> appreciate it.  Working on a project and desperately need it.
> Thanks in advance.

Ask your FAE. If you can give a good reason for it they can provide you 
with it, or make the modifications you request.

Kind regards,
        Johan

- -- 
        o o o o o o o . . .   _____________________________
       o      _____           ||    Johan Borkhuis        |
     .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
    >(________|__|_[_________]_|__________________________|
    _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
=== VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===

---------------------------

Newsgroups: comp.os.vxworks
Subject: recent developmwnts
Date: 31 Oct 2002 02:37:58 -0800
From: linsonaugustine@yahoo.co.in (Linson)
Organization: http://groups.google.com/
Message-ID: <ff09eb35.0210310237.6cc9b204@posting.google.com>

I just finished my undergraduate studies and like to secure my
master's in RTOS. Will anybody please tell me the latest developments
in RTOS. Or where can I learn more about the recent developments(any
news groups). I searched the net using google search engine but am not
satisfied.

   Thanking you in advance,
Linss

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: MPC860 training suggestions
Date: Thu, 31 Oct 2002 12:28:15 -0800
From: "Michael R. Kesti" <mkesti@gv.net>
Organization: MK Associates
Message-ID: <3DC1925F.156E3B29@gv.net>
References: <72e486b0.0210261955.3b660b3e@posting.google.com> <3DBC0A03.2F12A1DF@gv.net> <72e486b0.0210311101.22f698e7@posting.google.com>
Reply-To: mkesti@gv.net

kishuri wrote:

>Thank you Michael. That was very informative. You said it is basically
>C and assembler presentation. NO RTOS base.  That means are they
>mainly focused on programming each peripherals such as SCC, SMC, SPI,
>I2c, MMU, BIU with corresponding protocols and functions. Besides, are
>there any PowerPC core, mpc860/mpc8260 architecture history and
>detials included in the course?

There may have been a short presentation of these topics on the first
day, but the bulk of the course related to understanding and programming
the MPC860 and its on-board peripherals.

>My understanding is that MPC8260 is more advanced than mpc860. But
>they have separate courses for each architecure?

A quick look at http://www.arnewsh.com shows that they offer seperate
courses for the MPC8260, MPC824x, MPC860/821, and MPC60x/750/740
architectures.

>                                                 I gained little
>experience in  mpc860 and programmed SMC1 as UART and have its BSP
>source code to study further. But it is very time consuming, and there
>are no easy way to learn.  I don't have the hardware now.   Wish to
>master programming every peripherals with all protocol for future
>assignments. I have RTOS and writing device driver knowledge.
>Although it is basically programming register in right order, and most
>of it also given in the manual. I think, what I don't get quickly is
>that the understanding the programming sequences, its purpose. For
>example Port A-B-C have to programmed to assign pins, buffer
>descriptor management etc. There are not enough protocol details in
>the user manual.  By this in mind, would you please comment further.

I believe that the user manuals do present sufficient detail but because
they are reference documents, rather than tutorials, it is difficult to
use them without any prior experience.  The value of courses such as
Arnewsh's is that they provide a way to relatively quickly pick up
enough experience to allow the user manuals to become effective.

>Again, Thank you Michael.

You're very welcome.

- -- 
========================================================================
          Michael Kesti            |  "And like, one and one don't make
                                   |   two, one and one make one."
          mkesti@gv.net            |          - The Who, Bargain

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado/VxWorks newbie question
Date: 31 Oct 2002 12:57:38 -0800
From: suenews@schooner.com (Susan LoVerso)
Organization: http://groups.google.com/
Message-ID: <27127820.0210311257.1d70793@posting.google.com>
References: <WlNv9.186023$8o4.29661@afrodite.telenet-ops.be> <b30aa455.0210301214.63095bcb@posting.google.com>

cherubhollyhock@yahoo.com (Karen) wrote in message news:<b30aa455.0210301214.63095bcb@posting.google.com>...
> "who am i" <who@am.i> wrote in message news:<WlNv9.186023$8o4.29661@afrodite.telenet-ops.be>...
> > 
> > Now I'm wondering if there are cheaper (non-WR?  Open source?) ways of
> > getting some frameworks, software components etc...  I need stuff for:
> > 
> > 3. A database to store (a lot of) records in different tables in SRAM
> > (directly or through a filesystem).
> 
> File system is free. You have to hack up your own database or pay
> dearly for an off-shelf one.
> I might be wrong. It's been a year since I looked around for embedded
> DB.

[Disclaimer: I work for Sleepycat Software.]

Berkeley DB is an Open Source product.  You may download it
and use it at no charge, provided that you meet at least one
of these two requirements:

        +  You do not redistribute it off of a single physical site.
           If you use Berkeley DB on a Web server that is accessed
           from many locations, but you do not redistribute the actual
           code that uses Berkeley DB, you do not need to pay us.

        +  If you redistribute your application, you make your source
           code freely available.

If, instead, you want to redistribute in binary form the application
that uses Berkeley DB, you need to purchase a license from Sleepycat
Software.

Berkeley DB runs under T2.0 and AE and is certified under T2.0.  So depending
on your uses you can get an open-source database without paying dearly.

You can get more information at www.sleepycat.com.

sue

---------------------------

Newsgroups: comp.arch.embedded,comp.os.psos,comp.os.qnx,comp.os.vxworks,comp.realtime,comp.sys.arm
Subject: Re: TCP/IP implementation concept under RTOS like uCOS II
Date: Thu, 31 Oct 2002 22:10:49 -0000
From: Bahadir Balban <root@so-16077-x0.essex.ac.uk>
Message-ID: <Pine.LNX.4.44.0210312202580.1482-100000@so-16077-x0.essex.ac.uk>
References: <f8hr9.39321$N_6.555353@news.chello.at>
 <VhBv9.1108$t93.85902621@newssvr14.news.prodigy.com>

I suggest you use lwip Lightweight TCP/IP stack written by Adam Dunkels 
in Swedish Institute of Computer Science. It is freely available 
under modified GNU licence and there's a whole lwip community you can talk 
to. Lwip is designed for embedded systems with tenths of kilobytes of RAM 
and ROM. It runs both with or without a RTOS and a BSD style API is 
provided as well as lwip's own API.
See www.sics.se/~adam/lwip

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: WDB Configuration error
Date: 23 Oct 2002 22:17:58 -0700
From: vxnerd@rediffmail.com (subbarayan)
Organization: http://groups.google.com/
Message-ID: <f81c4277.0210232117.3b7b3a07@posting.google.com>
References: <fa651d64.0210230258.709d708e@posting.google.com> <Y01MmEGicst9EAVt@wtoram.co.uk>

dear vanessa,
Heres the proceedure how u go abt to make a standalone bootable floppy
based target:
In my case target cpu is I80486.U jus check and change where ever u
encounter this I80486 to the cpu ur going to use.
This is learnt it my way.
             VxWorks Booting procedure for floppy based target

Here are the steps to be followed for configuring a target on vxworks
by using a floppy jus like the one in psos:

1.First compile ur source file by typing ur code and accessing the
following menu in tornado:
Menu project-customise-addnewbutton-type the following:
CPU=I80386 ADDED_CFLAGS=-g trial.o
Here my source file name is trial.
Note:Always save ur source file in bsp target directory
itself.That&#8217;s the first thing u have to do.Ur .c file and .o
file both must be in the bsp directory file itself.This is very
crucial for configuring the target.
Give the working directory for source file as:
c:\tornado\target\config\pc386-here my target bsp is pc386.
Open debug menu and give the source search path the same as above
said.

2.Then compile ur source file by accessing build menu in project menu
and then makecurrentsourcefile menu both should be done.

3.Then open the bsp file(i.e. pc386,pc486 like that).

4.Goto DOS prompt.

5.Open the target bsp directory there.

6.Type edit makefile

7.Here makefile is target make file.

8.A window opens for makefile edition.

9.There type the following:
MACH_EXTRA=ursourcefile.o-trial.o in my case.

10.Execute the makefile after editing there itself by typing:
in dos prompt in the same location:
make

11.This will make ur target config file ready.

12.Goto tornado folder,select the config.h file in the target BSP
directory.
Add the following in the .h file of the respective target directory as
follows:
#define INCLUDE_USER_APPL
#define USER_APPL_INIT then a space near init and type the name of the
first task to be spawned in ur appln.i mean the root task.
12.Note that u define the above said in the last lines of the .h file.

13.Goto tornado environment and access the BSP configuration dialogue
box and include the following in it:
INCLUDE_LOADER
INCLUDE_UNLOADER.

14.After that build ur BSP from the same dialogue box by accessing
build button.

15.Now BSP config file is ready.

16.Now goto project menu in IDE and access make
target-makepc386-bootromtargets-bootrom_uncmp

17.Then similarly access under project
menu-makepc386-vxworks-vxworks.st

18.Goto DOS prompt and access the target bsp folder and type mkboot a:
bootrom_uncmp.

19.This will install the bootrom file in floppy.

20.Copy the .st file from the target BSP folder to the floppy.

21.Now the floppy is ready to boot and run the appln.

22.Boot the target and run the appln.

That&#8217;s all folks.After booting call ur first function which u
like to.Note:the first function ur abt to call after booting must be
defined in userappinit.c file .
Hope this helps u.
tell me if any doubts in the above proceedure.

---------------------------

Newsgroups: comp.os.vxworks
Subject: End Drvier can ping, but socket not working
Date: 31 Oct 2002 16:50:44 -0800
From: txwchen@yahoo.com (William)
Organization: http://groups.google.com/
Message-ID: <13dd0214.0210311650.2a7e121@posting.google.com>

Hi, there,

I wrote a virtual END driver in Tornad0 2.02. The drvier name is set
to "CIP", and data link is ATM.
I loaded the driver by calling:

    muxload(), 
    muxDevStart();
    ipattch();
    ifMaskSet();
    ifAddrSet();

and arpAdd() to bypass the arp.

Ping is working, I could ping the other machine, and saw the
ICMP packets sending out and receiving. 

But in UDP socket application, when I call sendto() function, 
nothing happened. No packet sending out.

Using muxShow, the driver seems correctly installed.
    -> muxShow
    Device: dc Unit: 0
    Description: dec21x40 Enhanced Network Driver
    Protocol: Wind Debug Agent	Type: 257	Recv 0x128f24	Shutdown 0x0
    Protocol: IP 4.4 ARP	Type: 2054	Recv 0x13d4a0	Shutdown 0x13d764
    Protocol: IP 4.4 TCP/IP	Type: 2048	Recv 0x13d4a0	Shutdown 0x13d69c
    Device: CIP Unit: 1
    Description: END clipoaEnd Driver.
    Protocol: IP 4.4 ARP	Type: 2054	Recv 0x13d4a0	Shutdown 0x13d764
    Protocol: IP 4.4 TCP/IP	Type: 2048	Recv 0x13d4a0	Shutdown 0x13d69c
    value = 0 = 0x0

Using ifShow, the IP address seems OK.
    -> ifShow
    dc (unit number 0):
        Flags: (0x8063) UP BROADCAST RUNNING ARP MULTICAST 
        Type: ETHERNET_CSMACD
        Internet address: 10.1.1.59 
        Broadcast address:   10.255.255.255
        Netmask 0xff000000 Subnetmask 0xff000000
        Ethernet address is 00:c0:a8:89:96:51
        Metric is 0
        Maximum Transfer Unit size is 1500
        2023 packets received; 1276 packets sent
        227 multicast packets received
        1 multicast packets sent
        0 input errors; 0 output errors
        0 collisions; 0 dropped
    lo (unit number 0):
        Flags: (0x8069) UP LOOPBACK RUNNING ARP MULTICAST 
        Type: SOFTWARE_LOOPBACK
        Internet address: 127.0.0.1 
        Netmask 0xff000000 Subnetmask 0xff000000
        Metric is 0
        Maximum Transfer Unit size is 32768
        77 packets received; 77 packets sent
        0 multicast packets received
        0 multicast packets sent
        0 input errors; 0 output errors
        0 collisions; 0 dropped
    CIP (unit number 1):
        Flags: (0x80e3) UP BROADCAST RUNNING MULTICAST 
        Type: 
        Internet address: 11.0.2.1 
        Broadcast address:   11.255.255.255
        Netmask 0xff000000 Subnetmask 0xff000000
        Ethernet address is 00:80:f9:01:02:3
        Metric is 0
        Maximum Transfer Unit size is 1520
        2 packets received; 2 packets sent
        0 multicast packets received
        0 multicast packets sent
        0 input errors; 0 output errors
        0 collisions; 0 dropped
    value = 0 = 0x0

Using arpShow, the arp address is shown also.
    -> arpShow

    LINK LEVEL ARP TABLE
    destination      gateway            flags  Refcnt  Use          
Interface
    --------------------------------------------------------------------------
    10.1.1.178       00:c0:a8:89:96:51    405    1       1293         
dc0
    11.0.2.1         00:80:f9:01:02:3     c05    0       0            
CIP1
    --------------------------------------------------------------------------
    value = 75 = 0x4b = 'K'

Using routShow, the route table looks"
    -> routeShow
    
    ROUTE NET TABLE
    destination      gateway              flags  Refcnt  Use          
Interface
    ----------------------------------------------------------------------------
    10.0.0.0         10.1.1.59            101    0       0            
dc0
    11.0.0.0         11.0.2.1             101    0       0            
CIP1
    ----------------------------------------------------------------------------
    
    ROUTE HOST TABLE
    destination      gateway              flags  Refcnt  Use          
Interface
    ----------------------------------------------------------------------------
    127.0.0.1        127.0.0.1            5      1       70           
lo0
    ----------------------------------------------------------------------------
    value = 77 = 0x4d = 'M'

Did I miss something?

Thanks.

William

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: The infamous "No rule to make target" problem
Date: Thu, 31 Oct 2002 01:50:13 GMT
From: "franco spadafora" <francospadafora@worldnet.att.net>
Organization: franco_182@hotmail.com
Message-ID: <p%%v9.15582$VJ5.919913@bgtnsc05-news.ops.worldnet.att.net>
References: <3db57e4b$2@news.mhogaming.com>
Reply-To: "franco spadafora" <franco_182@hotmail.com>

1. check for capitalization, slashes, etc...
2. Give up and write a Makefile. If you don't need to play around on a
regular basis with the vxWorks libraries and project settings, there is not
much advantage to using the GUI.

"Matt Osminer" <mosminer@vantum.com> wrote in message
news:3db57e4b$2@news.mhogaming.com...
> I seem to have come to an impasse with the infamous "No rule to make
target"
> problem.  As any Tornado sufferer will tell you the solution should be
>
> 1. Add -I directives to your C/C++ settings
> 2. Add a VPATH directive to your makefile Macros from the Project Macros
Tab
> 3. Rebuild all dependencies, then Build-All
>
> Wondering if anybody has tried all of the above, as I have, and still been
> unable to get past the "No rule" error?  My project was working just fine
> and then I did the unthinkable act of removing a few obsolete files and
> adding some new files.  I didn't touch the -I or VPATH configurations and
my
> new files all fell within the bounds of the original settings so there
> shouldn't have been a problem.
>
> The weird thing is Tornado just seems to be having a hard time locating
this
> one directory.  All my other -I directories appear just fine.
>
> I've tried:
> 1. Closing Tornado, rebuilding dependencies, saving the workspace, and
> "building-all" in about every combination you can think of.
> 2.  Removing all the -I options and re-entering them
> 3. Removing the VPATH and re-entering it
> 4. Checked for directory existance etc.
>
> Any further ideas out there???
>
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Bind PPP on top of non-standard device (RLP 3 stream, 3G simulation)
Date: Fri, 01 Nov 2002 05:06:44 GMT
From: "J Faurote" <spamnot_j_faurote@hotmail.com>
Organization: AT&T Broadband
Message-ID: <EZnw9.183733$md1.42659@sccrnsc03>
Reply-To: "J Faurote" <spamnot_j_faurote@hotmail.com>

Hello,

We're in the middle of a project to simulate the mobile and radio of a 3G
system to a BSC.  We've successfully ported the simulator from proprietary
hardware and a proprietary O/S to a cPCI platform using VxWorks.  The old
simulator would take a canned chunk of data, add a 7E delimiter to make the
receiving side think it was PPP and send it over RLP3 and a proprietary
communications stack to the base station.  Now we're toying with the idea of
using real PPP and possibly a TCP/IP stack above it so we can set up an FTP
session with the endpoint and transfer real data in either direction.

So now we have a couple questions.  Is there a way to get VxWorks PPP
implementation to bind into our RLP3 layer instead of a serial device
driver?  Possibly writing a virtual device driver that just communicates
with our RLP3 instead?  And what are the limitations of the PPP
implementation for VxWorks (5.4) (e.g., how many sessions can be supported,
how much overhead does each active session consume, etc)?

Any insight or suggestions would be greatly appreciated.

Regards,
- -Joe

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Linux
Date: Fri, 1 Nov 2002 10:48:43 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$d63w4h$hb8$1@lnews.actcom.co.il>
References: <d2f67bd8.0210230927.164179ce@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

In my previous postings, I have quoted other people's opinions,
and now, that the flow of responses seems to have dried out,
it is time for me to express my own opinion about using GPL
code in embedded systems, so here it goes:

It is not a mere coincidence that after so many years that the
GPL (and other open source licenses) have been in existence,
not even once a suit has been filed with a court of law against
commercial companies who use open source code inside their
commercial products.

In fact, filing such a law suite, would counter the goal of
the open source, and any such law suite will ultimately defeat
the purposes which led the code owners to release their code
to the public domain (GPL or other license) in the first place.

In other words, if you need to use any open source code
in your commercial products - go ahead! Because it is very unlikely that
you will be sued for non-compliance with the associated license.
I believe that any such law suit will fail in the courts:
the license itself may be in breach of law; any click-through
and shrink-wrap license is not considered a legally binding agreement;
it is difficult to prove the actual ownership of any given code as many
of the open source packages are based on earlier open source codes;
the court's ability to consider the associated technical details (e.g.
dynamic
vs. static linkage) is extremely limited; Open source rights owners'
resources
are limited, thus their ability to participate in a lengthy court action is
in doubt;
etc.

But long before the court makes up its mind about the suit, the negative
publicity resulting from the filing of any such suite will cause companies
to stop using GPL code, and opt for commercial licensed software instead,
and that will in effect work against the open source movement, and reverse
most of their progress and achievements in the recent years.

Many of you may disagree with me, but before you do, please consider the
actual motives for a person or a group of persons that drove them to donate
their code to the public domain, or to develop it under GPL terms initially.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim                Visit:
http://gamla.org.il/english/index.htm
        Consultant                Email: my first name at consultant dot com

"brian" <brian_doe@hotmail.com> wrote in message
news:d2f67bd8.0210230927.164179ce@posting.google.com...
> Hi Folx,
>
> Has anyone out there been told by their company, or heard of others
> being told, that they can't use Linux, due to potential GPL issues?  I
> realise that the debate goes on, however Im wondering what the large
> companies with lawyers think?
>
> Thanx in advance
>
> brian

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: End Drvier can ping, but socket not working
Date: Fri, 1 Nov 2002 10:00:01 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1036141268.929093@newsreader2.wirehub.nl>
References: <13dd0214.0210311650.2a7e121@posting.google.com>

Hi Wiliam,

I dont know how to solve your problem, but can give you some
thoughts...

* You could try to add some debugHooks, things like etherOutputHookAdd
and there several of those, maybe you could use some of these to do
some packet tracking.
* Add some tracing to your driver and see if packets do get at your
driver.
* Did you try this with a known-working END ethernet driver? Just to
see if the init stuff is ok? And if it is, try to see/trace the way
the ethernet driver works/the packets flow and compare it with the way
if works/flows with your driver.

I hope this will give you some idears to find it.

Goodluck,
Renee.
- - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

"William" <txwchen@yahoo.com> wrote in message
news:13dd0214.0210311650.2a7e121@posting.google.com...
> Hi, there,
>
> I wrote a virtual END driver in Tornad0 2.02. The drvier name is set
> to "CIP", and data link is ATM.
> I loaded the driver by calling:
>
>     muxload(),
>     muxDevStart();
>     ipattch();
>     ifMaskSet();
>     ifAddrSet();
>
> and arpAdd() to bypass the arp.
>
> Ping is working, I could ping the other machine, and saw the
> ICMP packets sending out and receiving.
>
> But in UDP socket application, when I call sendto() function,
> nothing happened. No packet sending out.
>
> Using muxShow, the driver seems correctly installed.
>     -> muxShow
>     Device: dc Unit: 0
>     Description: dec21x40 Enhanced Network Driver
>     Protocol: Wind Debug Agent Type: 257 Recv 0x128f24 Shutdown 0x0
>     Protocol: IP 4.4 ARP Type: 2054 Recv 0x13d4a0 Shutdown 0x13d764
>     Protocol: IP 4.4 TCP/IP Type: 2048 Recv 0x13d4a0 Shutdown
0x13d69c
>     Device: CIP Unit: 1
>     Description: END clipoaEnd Driver.
>     Protocol: IP 4.4 ARP Type: 2054 Recv 0x13d4a0 Shutdown 0x13d764
>     Protocol: IP 4.4 TCP/IP Type: 2048 Recv 0x13d4a0 Shutdown
0x13d69c
>     value = 0 = 0x0
>
>
> Using ifShow, the IP address seems OK.
>     -> ifShow
>     dc (unit number 0):
>         Flags: (0x8063) UP BROADCAST RUNNING ARP MULTICAST
>         Type: ETHERNET_CSMACD
>         Internet address: 10.1.1.59
>         Broadcast address:   10.255.255.255
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Ethernet address is 00:c0:a8:89:96:51
>         Metric is 0
>         Maximum Transfer Unit size is 1500
>         2023 packets received; 1276 packets sent
>         227 multicast packets received
>         1 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     lo (unit number 0):
>         Flags: (0x8069) UP LOOPBACK RUNNING ARP MULTICAST
>         Type: SOFTWARE_LOOPBACK
>         Internet address: 127.0.0.1
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Metric is 0
>         Maximum Transfer Unit size is 32768
>         77 packets received; 77 packets sent
>         0 multicast packets received
>         0 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     CIP (unit number 1):
>         Flags: (0x80e3) UP BROADCAST RUNNING MULTICAST
>         Type:
>         Internet address: 11.0.2.1
>         Broadcast address:   11.255.255.255
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Ethernet address is 00:80:f9:01:02:3
>         Metric is 0
>         Maximum Transfer Unit size is 1520
>         2 packets received; 2 packets sent
>         0 multicast packets received
>         0 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     value = 0 = 0x0
>
> Using arpShow, the arp address is shown also.
>     -> arpShow
>
>     LINK LEVEL ARP TABLE
>     destination      gateway            flags  Refcnt  Use
> Interface
>     ----------------------------------------------------------------
- ----------
>     10.1.1.178       00:c0:a8:89:96:51    405    1       1293
> dc0
>     11.0.2.1         00:80:f9:01:02:3     c05    0       0
> CIP1
>     ----------------------------------------------------------------
- ----------
>     value = 75 = 0x4b = 'K'
>
>
>
> Using routShow, the route table looks"
>     -> routeShow
>
>     ROUTE NET TABLE
>     destination      gateway              flags  Refcnt  Use
> Interface
>     ----------------------------------------------------------------
- ------------
>     10.0.0.0         10.1.1.59            101    0       0
> dc0
>     11.0.0.0         11.0.2.1             101    0       0
> CIP1
>     ----------------------------------------------------------------
- ------------
>
>     ROUTE HOST TABLE
>     destination      gateway              flags  Refcnt  Use
> Interface
>     ----------------------------------------------------------------
- ------------
>     127.0.0.1        127.0.0.1            5      1       70
> lo0
>     ----------------------------------------------------------------
- ------------
>     value = 77 = 0x4d = 'M'
>
>
> Did I miss something?
>
> Thanks.
>
> William

---------------------------

Newsgroups: comp.os.vxworks
Subject: System boot up time
Date: Fri, 1 Nov 2002 16:57:41 +0800
From: "Yung" <general_miller@yahoo.com>
Organization: IMS Netvigator
Message-ID: <aptfm8$paj1@imsp212.netvigator.com>

Hello experts,

This happens on a 32-bits 133MHz MIPS platform with Tornado 2.0.2.

I use the Tornado project environment to generate the run-time image
"vxWorks_romCompress". The resulting image is 3.5Mbyte in size. I burn it
onto Flash memory. It takes 3.5 minutes to boot up which is far too long!

After careful inspection of the romStart.c, i find out that the system boots
up in the following sequence:

- - copy the data segment needed by the decompression routine to RAM_HIGH_ADRS
- - execute the decompression routine "deflate" to decompress the sub-image
(vxWorks image) into RAM_LOW_ADRS
- - Jump to RAM_LOW_ADRS to begin the system.

I have found out that all the 3.5 minutes were spent on decompression. I
think it is the problem of executing the decompression routine that resides
in ROM instead of RAM.

On the other hand, i have also checked the bootROM routine bootInit.c. It
copies the whole ROM image (text + data + subimage) to RAM first, then do
the decompression on RAM. It is much faster and takes only about 8 seconds
for the same size of image (3.5Mbyte).
How can i do the same on the run-time image?
Any idea?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: System boot up time
Date: Fri, 1 Nov 2002 10:25:58 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1036142826.121493@newsreader2.wirehub.nl>
References: <aptfm8$paj1@imsp212.netvigator.com>

Hi,

Then why dont you copy the decompression routine to ram as well and
run it from there. Should not that difficult to implement. You could
also add this to the decompression routine that it copies itself to
RAM and jumps / continues on its new location.

Btw is this decompression routine in ROM of flash? Just make sure it
does not do any writing in flash. Cant you add ROM caching in a BIOS
or something alike ?

Are you sure every thing else is the same, like
bus-configuration/speed and more system parameters?

Just somethoughts,
Renee.

- - - - - - - - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

"Yung" <general_miller@yahoo.com> wrote in message
news:aptfm8$paj1@imsp212.netvigator.com...
> Hello experts,
>
> This happens on a 32-bits 133MHz MIPS platform with Tornado 2.0.2.
>
> I use the Tornado project environment to generate the run-time image
> "vxWorks_romCompress". The resulting image is 3.5Mbyte in size. I
burn it
> onto Flash memory. It takes 3.5 minutes to boot up which is far too
long!
>
> After careful inspection of the romStart.c, i find out that the
system boots
> up in the following sequence:
>
> - copy the data segment needed by the decompression routine to
RAM_HIGH_ADRS
> - execute the decompression routine "deflate" to decompress the
sub-image
> (vxWorks image) into RAM_LOW_ADRS
> - Jump to RAM_LOW_ADRS to begin the system.
>
> I have found out that all the 3.5 minutes were spent on
decompression. I
> think it is the problem of executing the decompression routine that
resides
> in ROM instead of RAM.
>
> On the other hand, i have also checked the bootROM routine
bootInit.c. It
> copies the whole ROM image (text + data + subimage) to RAM first,
then do
> the decompression on RAM. It is much faster and takes only about 8
seconds
> for the same size of image (3.5Mbyte).
> How can i do the same on the run-time image?
> Any idea?
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado/VxWorks newbie question
Date: Fri, 01 Nov 2002 09:37:24 GMT
From: "who am i" <who@am.i>
Organization: Telenet Internet
Message-ID: <oXrw9.190085$8o4.30315@afrodite.telenet-ops.be>
References: <WlNv9.186023$8o4.29661@afrodite.telenet-ops.be> <b30aa455.0210301214.63095bcb@posting.google.com> <27127820.0210311257.1d70793@posting.google.com>

> [Disclaimer: I work for Sleepycat Software.]

OK, no probs

> Berkeley DB is an Open Source product.  You may download it
> and use it at no charge...

I knew about that one already.  Thanx anyway.

> Berkeley DB runs under T2.0 and AE and is certified under T2.0.  So
depending
> on your uses you can get an open-source database without paying dearly.

How about T2.2?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: End Drvier can ping, but socket not working
Date: Fri, 1 Nov 2002 11:37:34 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$sf5w4h$nf8$1@lnews.actcom.co.il>
References: <13dd0214.0210311650.2a7e121@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

I wonder if your ATM interface shouldn't been a Point-to-point (istead of
Broadcast) type, but that has no effect on the issue at hand:

There is really no reason that your UDP app wou;dn't work where ICMP
worked, unless there is an error in teh UDP application itself.
Test it via the Ethernet network first, i.e. send UDP packets
to the 10.x.x.x address range.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim                Visit:
http://gamla.org.il/english/index.htm
        Consultant                Email: my first name at consultant dot com

"William" <txwchen@yahoo.com> wrote in message
news:13dd0214.0210311650.2a7e121@posting.google.com...
> Hi, there,
>
> I wrote a virtual END driver in Tornad0 2.02. The drvier name is set
> to "CIP", and data link is ATM.
> I loaded the driver by calling:
>
>     muxload(),
>     muxDevStart();
>     ipattch();
>     ifMaskSet();
>     ifAddrSet();
>
> and arpAdd() to bypass the arp.
>
> Ping is working, I could ping the other machine, and saw the
> ICMP packets sending out and receiving.
>
> But in UDP socket application, when I call sendto() function,
> nothing happened. No packet sending out.
>
> Using muxShow, the driver seems correctly installed.
>     -> muxShow
>     Device: dc Unit: 0
>     Description: dec21x40 Enhanced Network Driver
>     Protocol: Wind Debug Agent Type: 257 Recv 0x128f24 Shutdown 0x0
>     Protocol: IP 4.4 ARP Type: 2054 Recv 0x13d4a0 Shutdown 0x13d764
>     Protocol: IP 4.4 TCP/IP Type: 2048 Recv 0x13d4a0 Shutdown 0x13d69c
>     Device: CIP Unit: 1
>     Description: END clipoaEnd Driver.
>     Protocol: IP 4.4 ARP Type: 2054 Recv 0x13d4a0 Shutdown 0x13d764
>     Protocol: IP 4.4 TCP/IP Type: 2048 Recv 0x13d4a0 Shutdown 0x13d69c
>     value = 0 = 0x0
>
>
> Using ifShow, the IP address seems OK.
>     -> ifShow
>     dc (unit number 0):
>         Flags: (0x8063) UP BROADCAST RUNNING ARP MULTICAST
>         Type: ETHERNET_CSMACD
>         Internet address: 10.1.1.59
>         Broadcast address:   10.255.255.255
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Ethernet address is 00:c0:a8:89:96:51
>         Metric is 0
>         Maximum Transfer Unit size is 1500
>         2023 packets received; 1276 packets sent
>         227 multicast packets received
>         1 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     lo (unit number 0):
>         Flags: (0x8069) UP LOOPBACK RUNNING ARP MULTICAST
>         Type: SOFTWARE_LOOPBACK
>         Internet address: 127.0.0.1
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Metric is 0
>         Maximum Transfer Unit size is 32768
>         77 packets received; 77 packets sent
>         0 multicast packets received
>         0 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     CIP (unit number 1):
>         Flags: (0x80e3) UP BROADCAST RUNNING MULTICAST
>         Type:
>         Internet address: 11.0.2.1
>         Broadcast address:   11.255.255.255
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Ethernet address is 00:80:f9:01:02:3
>         Metric is 0
>         Maximum Transfer Unit size is 1520
>         2 packets received; 2 packets sent
>         0 multicast packets received
>         0 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     value = 0 = 0x0
>
> Using arpShow, the arp address is shown also.
>     -> arpShow
>
>     LINK LEVEL ARP TABLE
>     destination      gateway            flags  Refcnt  Use
> Interface
>     ----------------------------------------------------------------------
- ----
>     10.1.1.178       00:c0:a8:89:96:51    405    1       1293
> dc0
>     11.0.2.1         00:80:f9:01:02:3     c05    0       0
> CIP1
>     ----------------------------------------------------------------------
- ----
>     value = 75 = 0x4b = 'K'
>
>
>
> Using routShow, the route table looks"
>     -> routeShow
>
>     ROUTE NET TABLE
>     destination      gateway              flags  Refcnt  Use
> Interface
>     ----------------------------------------------------------------------
- ------
>     10.0.0.0         10.1.1.59            101    0       0
> dc0
>     11.0.0.0         11.0.2.1             101    0       0
> CIP1
>     ----------------------------------------------------------------------
- ------
>
>     ROUTE HOST TABLE
>     destination      gateway              flags  Refcnt  Use
> Interface
>     ----------------------------------------------------------------------
- ------
>     127.0.0.1        127.0.0.1            5      1       70
> lo0
>     ----------------------------------------------------------------------
- ------
>     value = 77 = 0x4d = 'M'
>
>
> Did I miss something?
>
> Thanks.
>
> William

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: System boot up time
Date: Fri, 1 Nov 2002 17:48:01 +0800
From: "Yung" <general_miller@yahoo.com>
Organization: IMS Netvigator
Message-ID: <aptikk$paq20@imsp212.netvigator.com>
References: <aptfm8$paj1@imsp212.netvigator.com> <1036142826.121493@newsreader2.wirehub.nl>

Thanks Renee, that is also what i am pursuing to do for the moment. The
first go wasn't successful. As i am not very familair with the MIPS
platform, i have problem interpreting the meaning of this:

 ((FUNCPTR)ROM_OFFSET(copyLongs))(ROM_TEXT_ADRS,(UINT)K0_TO_K1(romInit),
          ((UINT)edata-(UINT)romInit)/sizeof(long));

while K0_TO_K1 is simply defined as:

#define K0_TO_K1(x) ((unsigned)(x)|0xA0000000) /* kseg0 to kseg1 */

Anybody ever come across too?
btw, thanks for reminding. I will also have a check on the cache setting.

"Renee Teunissen"
<if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you
agree.with.these.terms@mail.zevenaar.org> wrote in message
news:1036142826.121493@newsreader2.wirehub.nl...
>
> Hi,
>
> Then why dont you copy the decompression routine to ram as well and
> run it from there. Should not that difficult to implement. You could
> also add this to the decompression routine that it copies itself to
> RAM and jumps / continues on its new location.
>
> Btw is this decompression routine in ROM of flash? Just make sure it
> does not do any writing in flash. Cant you add ROM caching in a BIOS
> or something alike ?
>
> Are you sure every thing else is the same, like
> bus-configuration/speed and more system parameters?
>
> Just somethoughts,
> Renee.
>
> - - - - - - - -
> Renee A. Teunissen
> PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
> T.+31-(0)35-6926969, M.+31-(0)6-22778313,
> http://www.pts.nl, <first_name>@pts.nl
> personal link page: http://wittenburg10c.nl/db/dest/links.html
>
>
> "Yung" <general_miller@yahoo.com> wrote in message
> news:aptfm8$paj1@imsp212.netvigator.com...
> > Hello experts,
> >
> > This happens on a 32-bits 133MHz MIPS platform with Tornado 2.0.2.
> >
> > I use the Tornado project environment to generate the run-time image
> > "vxWorks_romCompress". The resulting image is 3.5Mbyte in size. I
> burn it
> > onto Flash memory. It takes 3.5 minutes to boot up which is far too
> long!
> >
> > After careful inspection of the romStart.c, i find out that the
> system boots
> > up in the following sequence:
> >
> > - copy the data segment needed by the decompression routine to
> RAM_HIGH_ADRS
> > - execute the decompression routine "deflate" to decompress the
> sub-image
> > (vxWorks image) into RAM_LOW_ADRS
> > - Jump to RAM_LOW_ADRS to begin the system.
> >
> > I have found out that all the 3.5 minutes were spent on
> decompression. I
> > think it is the problem of executing the decompression routine that
> resides
> > in ROM instead of RAM.
> >
> > On the other hand, i have also checked the bootROM routine
> bootInit.c. It
> > copies the whole ROM image (text + data + subimage) to RAM first,
> then do
> > the decompression on RAM. It is much faster and takes only about 8
> seconds
> > for the same size of image (3.5Mbyte).
> > How can i do the same on the run-time image?
> > Any idea?
> >
> >
> >
>
>

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sat Nov  2 04:03:15 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sat Nov  2 04:03:16 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sat Nov  2 04:03:12 PST 2002

        Subject: Re: Tornado/VxWorks newbie question
        Subject: Re: Linux
        Subject: Re: System boot up time
        Subject: Re: Linux
        Subject: Re: MPC860 training suggestions
        Subject: Re: End Drvier can ping, but socket not working
        Subject: Re: Stack size
        Subject: Re: Semaphores for WatchDog timers.
        Subject: Re: vxWorks BSP manual needed
        Subject: Help on network card configuration

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado/VxWorks newbie question
Date: 1 Nov 2002 07:24:44 -0800
From: suenews@schooner.com (Susan LoVerso)
Organization: http://groups.google.com/
Message-ID: <27127820.0211010724.6dbb1015@posting.google.com>
References: <WlNv9.186023$8o4.29661@afrodite.telenet-ops.be> <b30aa455.0210301214.63095bcb@posting.google.com> <27127820.0210311257.1d70793@posting.google.com> <oXrw9.190085$8o4.30315@afrodite.telenet-ops.be>

"who am i" <who@am.i> wrote in message news:<oXrw9.190085$8o4.30315@afrodite.telenet-ops.be>...
> > [Disclaimer: I work for Sleepycat Software.]
> OK, no probs
>  
> > Berkeley DB runs under T2.0 and AE and is certified under T2.0.  So
>  depending
> > on your uses you can get an open-source database without paying dearly.
> 
> How about T2.2?

Our latest release does not contain T2.2 project files/workspaces.  Our current
in-progress release has been ported.  There were only .wpj and .wsp changes,
no source code changes required for DB itself.  So using earlier releases on
T2.2 should not be difficult.

   sue

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Linux
Date: 01 Nov 2002 10:59:24 -0500
From: Bill Pringlemeir <spam_account@sympatico.ca>
Organization: Bell Sympatico
Message-ID: <m2lm4dp9gj.fsf@sympatico.ca>
References: <d2f67bd8.0210230927.164179ce@posting.google.com> <newscache$d63w4h$hb8$1@lnews.actcom.co.il>
Sender: bpringle@DeadDuck

"brian" <brian_doe@hotmail.com> wrote in message

> Has anyone out there been told by their company, or heard of others
> being told, that they can't use Linux, due to potential GPL issues?  I
> realise that the debate goes on, however Im wondering what the large
> companies with lawyers think?

 Leonid> In my previous postings, I have quoted other people's
 Leonid> opinions, and now, that the flow of responses seems to have

[snip]

 Leonid> In other words, if you need to use any open source code in
 Leonid> your commercial products - go ahead! Because it is very
 Leonid> unlikely that you will be sued for non-compliance with the
 Leonid> associated license.  I believe that any such law suit will
 Leonid> fail in the courts: the license itself may be in breach of
 Leonid> law; any click-through and shrink-wrap license is not
 Leonid> considered a legally binding agreement; it is difficult to
 Leonid> prove the actual ownership of any given code as many of the
 Leonid> open source packages are based on earlier open source codes;
 Leonid> the court's ability to consider the associated technical
 Leonid> details (e.g.  dynamic vs. static linkage) is extremely
 Leonid> limited; Open source rights owners' resources are limited,
 Leonid> thus their ability to participate in a lengthy court action
 Leonid> is in doubt; etc.

Your assumption that only the "Open Source" movement would be entitled
to sue is wrong.  There are several parties involved.  In order to
perpetrate FUD, MicroSoft only has to buy such a product and start a
lawsuit.  Or some "hyper legal firm".  I don't think that the
copyright holders are the only persons who could enforce the license.
For instance, WRS will give you source to the GNU tools distributed
with vxWorks.  What the proper legal course would be if they didn't, I
don't know.  However, it would seem that the FSF would not have to be
involved (but I am not a lawyer).

 Leonid> But long before the court makes up its mind about the suit,
 Leonid> the negative publicity resulting from the filing of any such
 Leonid> suite will cause companies to stop using GPL code, and opt
 Leonid> for commercial licensed software instead, and that will in
 Leonid> effect work against the open source movement, and reverse
 Leonid> most of their progress and achievements in the recent years.

This might be beneficial for certain interests....

 Leonid> Many of you may disagree with me, but before you do, please
 Leonid> consider the actual motives for a person or a group of
 Leonid> persons that drove them to donate their code to the public
 Leonid> domain, or to develop it under GPL terms initially.

I don't disagree with anything you said.  However, the reality of life
is that the software business involves more parties than just GPL
developers and developers using the GPLed code.

fwiw,
Bill Pringlemeir.

- -- 
Finish your beer -- there are sober people in China!

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: System boot up time
Date: 1 Nov 2002 08:39:50 -0800
From: rick@cyclone.com (Richard Nardone)
Organization: http://groups.google.com/
Message-ID: <29b153d9.0211010839.16023a56@posting.google.com>
References: <aptfm8$paj1@imsp212.netvigator.com> <1036142826.121493@newsreader2.wirehub.nl> <aptikk$paq20@imsp212.netvigator.com>

> Thanks Renee, that is also what i am pursuing to do for the moment. The
> first go wasn't successful. As i am not very familair with the MIPS
> platform, i have problem interpreting the meaning of this:
> 
>  ((FUNCPTR)ROM_OFFSET(copyLongs))(ROM_TEXT_ADRS,(UINT)K0_TO_K1(romInit),
>           ((UINT)edata-(UINT)romInit)/sizeof(long));
> 
> while K0_TO_K1 is simply defined as:
> 
> #define K0_TO_K1(x) ((unsigned)(x)|0xA0000000) /* kseg0 to kseg1 */
> 
> Anybody ever come across too?
> btw, thanks for reminding. I will also have a check on the cache setting.

Let's take care of the easy stuff first.  The function
copyLongs(source, destination, nlongs) has three arguments.  The
source argument is ROM_TEXT_ADRS, which should be the start of the
program in Flash.  The destination address has to work out to some RAM
space where the program will run.  The nlongs parameter is calculating
the number of long words to copy.  The calculation for nlong is
pulling the edata address from the linker directive file, and this is
the end of the data section.  The romInit should be a label at the
start of the text section (the address of the romInit function which
is the entry point for VxWorks in FLASH).

I don't know about MIPS, so you have to look at what the processor
does when it first starts up.  Where does it read the first
instruction from when coming out of reset condition?  You need to look
at this because it can affect how the program is set up in Flash.  You
might have sections of the program located in non contiguous sections
of Flash.

  - Richard Nardone
    Cyclone Microsystems

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Linux
Date: 01 Nov 2002 11:36:07 -0500
From: "Paul D. Smith" <pausmith@nortelnetworks.com>
Organization: Nortel Networks, Inc. / Billerica, MA
Message-ID: <p5y98di6x4.fsf@lemming.engeast.baynetworks.com>
References: <d2f67bd8.0210230927.164179ce@posting.google.com> <newscache$d63w4h$hb8$1@lnews.actcom.co.il> <m2lm4dp9gj.fsf@sympatico.ca>
Reply-To: pausmith@nortelnetworks.com

%% Bill Pringlemeir <spam_account@sympatico.ca> writes:

  Leonid> In other words, if you need to use any open source code in
  Leonid> your commercial products - go ahead! Because it is very
  Leonid> unlikely that you will be sued for non-compliance with the
  Leonid> associated license.

This depends almost entirely on who owns the copyright on the open
source code you use.

If you use code that is copyright by the FSF, they _WILL_ unquestionably
sue you (if it should come to that: first, of course, they send you a
polite letter asking you to desist).  They have threatened this in the
past, and have even come very, very close to going to court before the
matter was resolved (the infringing party caved).

  Leonid> I believe that any such law suit will fail in the courts: the
  Leonid> license itself may be in breach of law; any click-through and
  Leonid> shrink-wrap license is not considered a legally binding
  Leonid> agreement;

First, that is not true.  Unfortunately shrink-wrap licenses have been
upheld in the courts in the past (at least in the USA).

Second, the GPL is _NOT_ a shrink-wrap license.

Remember that a work, merely by virtue of being copyright, has various
restrictions on it, without any license at all.  Copyright work can't be
reproduced, etc.  It also allows certain things, like fair use, etc.

A license _MODIFIES_ the rights you normally get through copyright.

A typical EULA _restricts_ the rights you would normally get with a
copyrighted work, so that you can't perform them anymore.  This is why
the legitimacy of shrink-wrap licenses is important, because if they are
held to be unenforceable then you would gain back those rights that the
EULA denied you.

The GPL, and other open source licenses, are fundamentally different in
that they _give_ you _MORE_ rights than you would normally have under
plain copyright law, they don't take any of your rights away.  In
particular, only by accepting the terms of the license are you _ALLOWED_
to use the software in an "open source" manner.

So, if you do not agree to the license, then what happens?  Well, the
rights you used to have under the license are rescinded and you're left
with only the rights that normal copyright law allows.  Which is also
just fine with the copyright holders.

  Leonid> it is difficult to prove the actual ownership of any given
  Leonid> code as many of the open source packages are based on earlier
  Leonid> open source codes;

This is only an issue with _SOME_ open source code.  The FSF, for
example, is very, very careful to obtain paperwork for any significant
donation of code or documentation which assigns copyright to them (the
FSF).

They are in a _very_ strong position to defend their copyright.  Other
works, like Perl, Linux, etc. would have a more difficult time, but I'm
sure they could still do it.

  Leonid> the court's ability to consider the associated technical
  Leonid> details (e.g.  dynamic vs. static linkage) is extremely
  Leonid> limited;

That may be so, but they can be educated, they can appoint "special
masters", etc.  There have already been _extremely_ technically
sophisticated cases brought before the court: what about the Microsoft
case?  Also revolved on technical issues like this.

  Leonid> Open source rights owners' resources are limited, thus their
  Leonid> ability to participate in a lengthy court action is in doubt;
  Leonid> etc.

There are lots of resources for this: many groups would rally around and
donate money, legal counsel, etc. if it came down to that.  I don't
think this would be a significant issue.

  bp> Your assumption that only the "Open Source" movement would be
  bp> entitled to sue is wrong.  There are several parties involved.

Actually, at least in the USA, I believe that only parties that have a
legal stake in the outcome can sue.  In practice this means that only
people who hold copyright on the code can sue.

- -- 
- -------------------------------------------------------------------------------
 Paul D. Smith <pausmith@nortelnetworks.com> HASMAT--HA Software Mthds & Tools
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
- -------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: MPC860 training suggestions
Date: 1 Nov 2002 09:42:43 -0800
From: rick@cyclone.com (Richard Nardone)
Organization: http://groups.google.com/
Message-ID: <29b153d9.0211010942.76c22957@posting.google.com>
References: <72e486b0.0210261955.3b660b3e@posting.google.com> <3DBC0A03.2F12A1DF@gv.net> <72e486b0.0210311101.22f698e7@posting.google.com>

> 
> My understanding is that MPC8260 is more advanced than mpc860. But
> they have separate courses for each architecure? I gained little
> experience in  mpc860 and programmed SMC1 as UART and have its BSP
> source code to study further. But it is very time consuming, and there
> are no easy way to learn.  I don't have the hardware now.   Wish to
> master programming every peripherals with all protocol for future
> assignments. I have RTOS and writing device driver knowledge.
> Although it is basically programming register in right order, and most
> of it also given in the manual. I think, what I don't get quickly is
> that the understanding the programming sequences, its purpose. For
> example Port A-B-C have to programmed to assign pins, buffer
> descriptor management etc. There are not enough protocol details in
> the user manual.  By this in mind, would you please comment further.

  If you have some 860 experience, I think you will be OK with the
8260.  There is a lot of information about the PPC60x core out there,
which is worth reading. The 8260 specific information in the User's
Manual is difficult to read, but the best (maybe only) source of
information out there.  You have most of the background necessary for
a successful project, I would skip the training, hit the books hard,
and spend the money on an evaluation platform and a good JTAG
emulator.  The Motorola website had the best information and example
code.  Be sure to get the latest Errata and keep in touch with your
Motorola FAE.

The 8260 is pretty complicated so I would look for a course with lab
exposure, and an instructor who has actually worked with the processor
and RTOS.  If you can find this quality of course, it may be worth
your while.  I'm not sure it is readily available.

You are going to experience some pain and suffering with the 8260, but
it is an amazing processor once you get things running.   I got a
custom board up with an 8260 and then did a HDLC/E1 driver using the
MCC.   Read the Users Manual, Be the User's Manual.  Good luck!

   Richard Nardone
   Cyclone Microsystems

I found a training CD helpful: CD860TRAINING/D from Motorola.  Maybe
they have updated it for the 8260.  I heard the 8560 is coming.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: End Drvier can ping, but socket not working
Date: 1 Nov 2002 12:35:13 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211011235.26ef607@posting.google.com>
References: <13dd0214.0210311650.2a7e121@posting.google.com>

Hello,

You didn't specify the architecture, but on some (e.g. ARM) it is
necessary to realign the packets that are received so that the stack
can examine the IP address correctly using a 32 bit memory access.
This doesn't affect ping since the packet is simply reflected by a
lower layer in the stack, so often when ping works, but the upper
layers do not this is the cause.

You can tell if you need this by looking in the load string for the dc
driver (usually in configNet.h or built dynamically in sysEnd.c in
your BSP). If the 'offset' field in the string has the value 2, then
this is something that your new driver will need to deal with as well.
Check in your reference manual entry for the dc driver (one of
dec21x4xEnd or dec2104xEnd depending on your BSP) for the exact
position of the 'offset' field in the string.

HTH,

John...

txwchen@yahoo.com (William) wrote in message news:<13dd0214.0210311650.2a7e121@posting.google.com>...
> Hi, there,
> 
> I wrote a virtual END driver in Tornad0 2.02. The drvier name is set
> to "CIP", and data link is ATM.
> I loaded the driver by calling:
> 
>     muxload(), 
>     muxDevStart();
>     ipattch();
>     ifMaskSet();
>     ifAddrSet();
> 
> and arpAdd() to bypass the arp.
> 
> Ping is working, I could ping the other machine, and saw the
> ICMP packets sending out and receiving. 
> 
> But in UDP socket application, when I call sendto() function, 
> nothing happened. No packet sending out.
> 
> Using muxShow, the driver seems correctly installed.
>     -> muxShow
>     Device: dc Unit: 0
>     Description: dec21x40 Enhanced Network Driver
>     Protocol: Wind Debug Agent	Type: 257	Recv 0x128f24	Shutdown 0x0
>     Protocol: IP 4.4 ARP	Type: 2054	Recv 0x13d4a0	Shutdown 0x13d764
>     Protocol: IP 4.4 TCP/IP	Type: 2048	Recv 0x13d4a0	Shutdown 0x13d69c
>     Device: CIP Unit: 1
>     Description: END clipoaEnd Driver.
>     Protocol: IP 4.4 ARP	Type: 2054	Recv 0x13d4a0	Shutdown 0x13d764
>     Protocol: IP 4.4 TCP/IP	Type: 2048	Recv 0x13d4a0	Shutdown 0x13d69c
>     value = 0 = 0x0
> 
> 
> Using ifShow, the IP address seems OK.
>     -> ifShow
>     dc (unit number 0):
>         Flags: (0x8063) UP BROADCAST RUNNING ARP MULTICAST 
>         Type: ETHERNET_CSMACD
>         Internet address: 10.1.1.59 
>         Broadcast address:   10.255.255.255
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Ethernet address is 00:c0:a8:89:96:51
>         Metric is 0
>         Maximum Transfer Unit size is 1500
>         2023 packets received; 1276 packets sent
>         227 multicast packets received
>         1 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     lo (unit number 0):
>         Flags: (0x8069) UP LOOPBACK RUNNING ARP MULTICAST 
>         Type: SOFTWARE_LOOPBACK
>         Internet address: 127.0.0.1 
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Metric is 0
>         Maximum Transfer Unit size is 32768
>         77 packets received; 77 packets sent
>         0 multicast packets received
>         0 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     CIP (unit number 1):
>         Flags: (0x80e3) UP BROADCAST RUNNING MULTICAST 
>         Type: 
>         Internet address: 11.0.2.1 
>         Broadcast address:   11.255.255.255
>         Netmask 0xff000000 Subnetmask 0xff000000
>         Ethernet address is 00:80:f9:01:02:3
>         Metric is 0
>         Maximum Transfer Unit size is 1520
>         2 packets received; 2 packets sent
>         0 multicast packets received
>         0 multicast packets sent
>         0 input errors; 0 output errors
>         0 collisions; 0 dropped
>     value = 0 = 0x0
> 
> Using arpShow, the arp address is shown also.
>     -> arpShow
> 
>     LINK LEVEL ARP TABLE
>     destination      gateway            flags  Refcnt  Use          
> Interface
>     --------------------------------------------------------------------------
>     10.1.1.178       00:c0:a8:89:96:51    405    1       1293         
> dc0
>     11.0.2.1         00:80:f9:01:02:3     c05    0       0            
> CIP1
>     --------------------------------------------------------------------------
>     value = 75 = 0x4b = 'K'
> 
> 
> 
> Using routShow, the route table looks"
>     -> routeShow
>     
>     ROUTE NET TABLE
>     destination      gateway              flags  Refcnt  Use          
> Interface
>     ----------------------------------------------------------------------------
>     10.0.0.0         10.1.1.59            101    0       0            
> dc0
>     11.0.0.0         11.0.2.1             101    0       0            
> CIP1
>     ----------------------------------------------------------------------------
>     
>     ROUTE HOST TABLE
>     destination      gateway              flags  Refcnt  Use          
> Interface
>     ----------------------------------------------------------------------------
>     127.0.0.1        127.0.0.1            5      1       70           
> lo0
>     ----------------------------------------------------------------------------
>     value = 77 = 0x4d = 'M'
> 
> 
> Did I miss something?
> 
> Thanks.
> 
> William

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Stack size
Date: Sat, 2 Nov 2002 00:24:24 -0000
From: "cecil" <cecil@bkup.fsnet.co.uk>
Message-ID: <apv5vv$c5$1$8300dec7@news.demon.co.uk>
References: <ap5ehc$s04$1@news.mch.sbs.de> <3db660c8$0$97618$edfadb0f@dspool01.news.tele.dk>

If your running on x86 platform you and run your application for some time
(days and weeks) you might notice the maximum stack size creeps.  This is
because the task's stack is used as the interrupt stack too....so be
generous and make sure you have at least 1k margin.
Nigel
"Jakob Olsen" <jbol@cotas.dk> wrote in message
news:3db660c8$0$97618$edfadb0f@dspool01.news.tele.dk...
> Hi Mohan
>
> Well, the hard way of doing it is to actually calculate a worst case stack
> size of your program. Nobody I know actually does this.
> The easy way is to set the stack size very high, to make sure that there
is
> enough. Then let the task run for some time, stressing it a bit, to make
> sure it has been through all possible situations where a large stack is
> neccessary.
> Now, open a shell and use the command "ti NameOfYourTask" to see the task
> info of your task. This will reveal how big the tasks stack is, the
maximum
> use, and what margin this yields.
> Now go back to your taskSpawn and adjust the stack size using the new
> information you just got. (I usually run with a stack size twice as big as
> needed, just to be sure)
>
> Jakob
>
> "Ram Mohan" <ram.naga@sisl.co.in> wrote in message
> news:ap5ehc$s04$1@news.mch.sbs.de...
> > Hello,
> >
> > I am new to VxWorks.
> >
> > One of the taskSpawn() argument is stackSize.
> >
> > My questions are,
> > 1. How to guess the stack size ? Is there any procedure ?
> > 2. If the given stackSize is not sufficient for the task then what
happens
> ?
> >
> >
> > Please help me to clarify about doubts,
> >
> > Thanks & Regards,
> > Mohan
> >
> >
> >
>
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Semaphores for WatchDog timers.
Date: 29 Oct 2002 07:43:55 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0210290743.590b3a52@posting.google.com>
References: <df8a7b26.0210282121.10ad8f87@posting.google.com>

Hello,

You need to read the manuals. The timer callback routine runs as an
ISR, and therefore cannot take a semaphore. It can *give* a semaphore.

While on the subject, the timer callback routine also cannot call
printf(), and it probably shouldn't call time() since that is not on
the list of ISR-safe routines (though it might work) - check in the
VxWorks Programmer's Guide for the list of routines that can be called
from an ISR.

Finally, it looks very much as if you are using a binary semaphore for
mutual exclusion. While that works, you might want to look into using
a mutex semaphore instead. They offer a number of protections that are
not available with a binary semaphore (e.g. only the task that took
the semaphore may give it, and the delete safety and priority
inversion safety features).

HTH,

John...

vxworksonline@yahoo.com (Shiny) wrote in message news:<df8a7b26.0210282121.10ad8f87@posting.google.com>...
> Hi,
> This is my flow of the program. I have a task named Task, which
> creates a semaphore and takes it. The semaphore is taken before the
> timer is created. Inside the Timer CB also the semaphore is taken. The
> semaphoere is given after 10 seconds in the main task. The expected
> result is that the TimerCB should wait in the semaphore until it is
> given from the main task(for 10 seconds). But that doesnot happen. I
> think watchdog timers donot wait on semaphores. If I want to achieve
> my expected result, what kind of semaphore should I use?
> 
> int Task(void)
> {
> 	
>     semBinary = semBCreate(SEM_Q_FIFO, SEM_FULL);
>     printf("\nTaking Semaphore in the task before creating the
> timer\n");
>     semTake(semBinary,WAIT_FOREVER);
> 
>     printf("Creating the timer\n");
>     wdogId = wdCreate();
>     if ( wdogId == NULL )
>     {
> 	printf( "timedemo: couldn't create watchdog\n" );
> 	return ERROR;
>     }	
>     else 
>     {
>         if ( wdStart( wdogId, sysClkRateGet() * 5, (FUNCPTR)TimerCB,
> 			0) == ERROR )
> 	{
> 	    printf( "timedemo: couldn't create watchdog\n" );
> 	    return ERROR;
> 	}
> 	else
> 	{
> 	    printf("In 10 seconds timer\n");			
> 	}
>     }
> 
>     printf("Waiting for 10 seconds\n");
>     taskDelay (sysClkRateGet ( ) * 10);	
> 
>     printf("Giving semaphore inside Main task\n");
>     return 0;
> }
> 
> void TimerCB(void)
> {
>     time(&timet);
>     printf("time1 : %u\n",timet);
> 
>     printf("Timer call back Fired\n");
>     printf("Taking semaphore inside timer call back\n");
>     semTake(semBinary,WAIT_FOREVER);
> 	
>     if (wdStart( wdogId, sysClkRateGet() * 10, (FUNCPTR)TimerCB,
> 			0) == ERROR )
>     {
> 	printf( "timedemo: couldn't create watchdog\n" );		
> 	return;
>     }
> 
>     printf("Giving semaphore inside timer call back\n");
>     semGive(semBinary);		
> }
> 
> TIA, Shiney.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: vxWorks BSP manual needed
Date: Tue, 29 Oct 2002 20:57:47 +0000 (UTC)
From: Johan Borkhuis <JBorkhuis@proxim.com>
Organization: Proxim Corp.
Message-ID: <Xns92B6DECE67C2jborkhuisproximcom@192.19.193.66>
References: <CwYr9.216$zE6.1018@rwcrnsc51.ops.asp.att.net> <Vyyv9.638993$f05.26480793@news1.calgary.shaw.ca> <3DBF0B89.692D@despam.autobahn.mb.ca>

"H. E. Taylor" <het@despam.autobahn.mb.ca> wrote:

> In article <Vyyv9.638993$f05.26480793@news1.calgary.shaw.ca>,
><ckrueger@NOSPAM.thomsontechnology.com> Chad wrote:
>> I found a document entitled "VxWorks - Device drivers in a nutshell"
>> which I believe was gnu public licensed several months ago, I found
>> it quite informative and if I can dig it up I'll email it to you.  It
>> gives a general device driver framework and example, though I believe
>> (I've yet to look into it in too much detail) things have changed a
>> bit in vxWorks 5.5. 
>> 
> 
>      Could you put it on the web, or alternatively 
>      could someone else [Johann?] in the group?  
>      This type of doc is frequently requested, but
>      unfortunately I don't have online room for it myself. 
>      [I'm near my 10 meg limit.]

If you send it to me (or tell me where to find it) I will put it on the 
site.

Kind regards,
        Johan

- -- 
        o o o o o o o . . .   _____________________________
       o      _____           ||    Johan Borkhuis        |
     .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
    >(________|__|_[_________]_|__________________________|
    _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
=== VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===

---------------------------

Newsgroups: comp.os.vxworks
Subject: Help on network card configuration
Date: Sun, 27 Oct 2002 18:41:48 +0800
From: "Lawrence Lo" <lo627@netvigator.com>
Organization: IMS Netvigator
Message-ID: <apgftl$fjp2@imsp212.netvigator.com>

Hi

I had problems in connecting the target server to the target agent over
ethernet. I got the rpccore timeout. I booted the target by floppy and have
added 'o=elPci' at the end of boot parameter. (I use 3c509c-tx ethernet
card).

However it seems that the card is not initialized and attached after VxWorks
is booted from floppy. I want to know how I could configure the IRQ and I/O
address of the 3c509 card?

Thanks a lot for your help!

Lawrence

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sun Nov  3 04:03:14 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sun Nov  3 04:03:15 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sun Nov  3 04:03:12 PST 2002

        Subject: Re: Using fast RAM for .data section?
        Subject: Tornado/VxWorks newbie question
        Subject: Re: Bootrom size question
        Subject: Re: sysClkRate reasonable values..
        Subject: Re: USB camera in vxworks ? Re: USB
        Subject: Re: JTAG debugger for MPC82xx
        Subject: Re: Linux
        Subject: Re: Symbol Table problems on VisionClick , VxWorks
        Subject: Re: taskSuspend/taskResume counted?

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Using fast RAM for .data section?
Date: Wed, 30 Oct 2002 11:12:54 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$lyes4h$hh1$1@lnews.actcom.co.il>
References: <200210292242.g9TMgi924215@solar.brecis.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

DO you have more then one kind of RAM ?

Is your fast RAM very large ?

Are there any PARTICULAR bottlenecks where
you want to increase performance with this fast RAM ?

WHat I am trying to say, is that moving the whole .data segment
into the fast RAM is not necesarily the most effecient way to
use this memory resources for best results.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim                Visit:
http://gamla.org.il/english/index.htm
        Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tornado/VxWorks newbie question
Date: Wed, 30 Oct 2002 09:10:14 GMT
From: "who am i" <who@am.i>
Organization: Telenet Internet
Message-ID: <WlNv9.186023$8o4.29661@afrodite.telenet-ops.be>

Hello,

I have to develop a device from scratch and it is going to be my first
experiance with VxWorks and Tornado.  I have registered myself and a
collegue of mine for the Tornado 2.2/VxWorks 5.4 training at the end of the
month.  I hope to get a lot of info there, but in the mean time I have to
start thinking and looking around for the software components, middleware,
frameworks, libraries or whatever I'll need.  I know that WR has a lot of
stuff, but they ask a lot of money too for all these things.

Now I'm wondering if there are cheaper (non-WR?  Open source?) ways of
getting some frameworks, software components etc...  I need stuff for:

1. Handling input events from keyboard and some serial device(s).  Using a
event queue?

2. UI stuff on a QVGA display.  e.g. menus, form input (with input masks,
validation).  I would also like to use (part of) the same validation rules
and UI rules to allow remote access to the device through a web browser
(HTML + javacript or a Java applet?)

3. A database to store (a lot of) records in different tables in SRAM
(directly or through a filesystem).

Are there pointers, links or whatever around here concerning systems design
with VxWorks, best practices, etc?

Thanks in advance

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Bootrom size question
Date: 30 Oct 2002 03:42:34 -0800
From: seasoblue2000@yahoo.com.cn (seasoblue)
Organization: http://groups.google.com/
Message-ID: <e82d8e83.0210300342.c2c0ff2@posting.google.com>
References: <apn93j$sei$1@newpoisson.nosc.mil>

Hi,
   Have you made the changes both in makefile and config.h?

owen@manta.nosc.mil (Wallace E. Owen) wrote in message news:<apn93j$sei$1@newpoisson.nosc.mil>...
> I'm trying to build a moderately large (~1.2MB text segment) app to be
> booted and run from a floppy on an embedded PC.  A helloworld app builds
> fine, but when I try to make my full app's boot image, romsize complains
> that the imagre is ~600K too large.  I adjusted the RAM_LOW_ADRS from
> 0x00108000 to 0x00208000, and changed the ROM_SIZE from 0x00090000 to
> 0x00190000 thinking that this would make enough room for the image and
> the boot loader (I'm trying to make my app boot from floppy).  The app
> builds without complaint, but it just hangs after the loader loads it.
> 
> Any clues appreciated.
> 
> 
>   // Wally

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: sysClkRate reasonable values..
Date: Wed, 30 Oct 2002 15:26:09 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$voqs4h$gw1$1@lnews.actcom.co.il>
References: <1035882002.428469@newsreader2.wirehub.nl> <29b153d9.0210291302.5b6b717c@posting.google.com> <apog15$fv2$1@knossos.btinternet.com> <1035982934.89356@newsreader2.wirehub.nl>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

If you ask nicely, WR will give you the current source of the
FEI driver, so you will be able to fix the delay code easily.
Talk to your FAE, and make sure to submit a TSR with Support.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim                Visit:
http://gamla.org.il/english/index.htm
        Consultant                Email: my first name at consultant dot com

"Renee Teunissen"
<if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you
agree.with.these.terms@mail.zevenaar.org> wrote in message
news:1035982934.89356@newsreader2.wirehub.nl...
> Well our reason for thining it where several.
>
> At first we ewanted to move to clockrate that is more "devidable",
> like100, 200, 250 or something like that. 60 is not a wonderfull
> value. 100 seems more reasable than 60.
>
> Second we're using it in a simulation system where quite a lot of
> tasks are running to some kind of elemtairy task and we didnt want to
> this by creating a huge statemachine. Think about 60+tasks and some
> triggers the other or sendout a signal/pulse or do both. therefore we
> were thinking of setting the clockrate to 1000, to get it in a 1ms
> grid.
>
> We are running on a 833Mz PIII system, which should fast enought not
> to get "locked up" in only taskswitching.
>
> Thanx a lot so far.
>
> But this does not solve the problem. I talked about it with our BSP
> vendor, to see what they can to. Our intel 82559 FEI-driver is closed
> source, so I dont know if they are doing a taskDelay(60) to wait for a
> single second.. this scares the creeps out of me...
>
> Cheers,
> Renee
> - - - - - - - -
> Renee A. Teunissen
> PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
> T.+31-(0)35-6926969, M.+31-(0)6-22778313,
> http://www.pts.nl, <first_name>@pts.nl
> personal link page: http://wittenburg10c.nl/db/dest/links.html
>
>
> "David Laight" <david@spam.me.l8s.co.uk> wrote in message
> news:apog15$fv2$1@knossos.btinternet.com...
> >
> > >   Increasing the system clock to 1000Hz is generally not
> advisable.
> > > Each tick causes the kernel to wake up and see what needs to be
> done.
> > > This activity consumes CPU cycles, and is the overhead associated
> with
> > > an RTOS.
> >
> > But it is still slow for a modern cpu.  60Hz (US power freq) was
> used
> > for slow 68k systems.  Most modern cpus run fast enough that it is
> > unlikely to be a problem.
> > Remember you won't affect the system interrupt latency by increasing
> > the frequency of the timer interrupt.
> >
> > David
> >
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: USB camera in vxworks ? Re: USB
Date: 28 Oct 2002 01:01:49 -0800
From: ravi368@yahoo.com (Ravi Uday)
Organization: http://groups.google.com/
Message-ID: <ecca3ca6.0210280101.dd850d0@posting.google.com>
References: <ecca3ca6.0210162128.c36f98c@posting.google.com> <IqPs9.73706$v_3.1544103@news.bora.net> <488e459a.0210212115.752d889c@posting.google.com> <Tr7t9.77017$v_3.1624862@news.bora.net> <ap55rt$1968$1@mail.cn99.com>

Jeff Zheng <zhengzhe@hotmail.com> wrote in message news:<ap55rt$1968$1@mail.cn99.com>...
> Usb bus is designed to be much software related. 
> The usb controller is much like an ethernet controller. 
> Usb device driver is much like socket users. 
> And there must be some kind of protocol stack between them. 
> I have tried to migrate linux usb stack to vxWorks. but havn't succeed yet.
> 
> Jeff

Jeff :

Whats the OHCI u r using ?? Which chipset ( Host Controller ) are u
using.
I am now trying my hands on ScanLogics SL11H Host Controller. But its
on windows I need one for VxWorks. Any suggestions. ?? My transfer is
Bulk as well
Your views are appreciated before hand

- - Ravi

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: JTAG debugger for MPC82xx
Date: Thu, 31 Oct 2002 01:34:58 GMT
From: "franco spadafora" <francospadafora@worldnet.att.net>
Organization: franco_182@hotmail.com
Message-ID: <6N%v9.15541$VJ5.917779@bgtnsc05-news.ops.worldnet.att.net>
References: <aph4n5$jne$1@newshost.mot.com> <Xns92B559F2DA559jborkhuisproximcom@192.19.193.66>
Reply-To: "franco spadafora" <franco_182@hotmail.com>

I have used the vision family of products for quite a while now and am
extremely happy with them.  I have very limited Poweratap exposure, but now
that WindRiver owns (or do they just distribute) visionICE, you get
everything from one source.

"Johan Borkhuis" <JBorkhuis@proxim.com> wrote in message
news:Xns92B559F2DA559jborkhuisproximcom@192.19.193.66...
> "Martin Roth" <bmr006@email.mot.com> wrote:
>
> >  I consider purchasing a JTAG debugger for BSP development. The CPU
> >  board is
> > based on MPC82xx processor of Motorola and will run Vxworks 5.4 OS.
> > I have two options for JTAG debuggers:
> > 1) Visionice II of Windriver
> > 2) PowerTap of Applied Microsystems
> > I would appreciate to have any good/bad opinion regarding these JTAG
> > debuggers!
>
> I use visionICE quite a lot, for both MIPS and PPC (824x), and it works
> very well. The SW is stable (btw: visionICE runs under pSOS :-),
> visionCLICK (the PC SW) knows how to interface with VxWorks, and you can
> use the visionICE as a WDB interface.
>
> Kind regards,
>         Johan
>
> --
>         o o o o o o o . . .   _____________________________
>        o      _____           ||    Johan Borkhuis        |
>      .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
>     >(________|__|_[_________]_|__________________________|
>     _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
> === VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Linux
Date: Thu, 24 Oct 2002 08:48:16 +0100
From: Danny Chapman <dc8@lucent.com>
Organization: Lucent Technologies, Indian Hill
Message-ID: <Pine.GSO.4.43.0210240842310.6536-100000@mlgw069.uk.lucent.com>
References: <d2f67bd8.0210230927.164179ce@posting.google.com>
 <newscache$pc4g4h$y0n$1@lnews.actcom.co.il>

On Wed, 23 Oct 2002, Leonid Rosenboim wrote:

> There are certain ways used by different companies (including WIndRiver
> who use GPL'ed code in the tool chain) that think the have figured it
> out (i.e. separate their proprietary stuff from GPL stuff)...

I happened to notice a while back that demangle.h (supplied by WR) is
licensed under the full GNU GPL, and does not have the library exception
clause that all the other GNU headers contain (e.g. fstream.h). I assume
this means that any product whose source includes demangle.h would have to
be licensed under the full GNU GPL.

??

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Symbol Table problems on VisionClick , VxWorks
Date: Wed, 30 Oct 2002 20:08:02 +0000
From: Philipez <philipez@blaq.co.uk>
Organization: Blaq Industries
Message-ID: <us0f12ngblvj8b@corp.supernews.com>
References: <appb5l$aa4$1@overload.lbl.gov>

On Wed, 30 Oct 2002 18:30:39 +0000, Shiv wrote:

> the VisionClick Debugger turns up a
> bunch unresolved symbols , not for the entire code segment , but ONLY
> for a selective few local variables that come up as "unresolved" when I
> probe them via break-points?

Are you using optimisation at all? Is it possible that the compiler is
optimising away some variables that it doesn't really need?

Just an idea...
Philipez.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: taskSuspend/taskResume counted?
Date: Sun, 3 Nov 2002 10:33:57 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$strz4h$0hj$1@lnews.actcom.co.il>
References: <bob-0CD481.12580002112002@news.apple.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Bob Bradley" <bob@chaoticsoftware.com> wrote in message
news:bob-0CD481.12580002112002@news.apple.com...
> Do the taskSuspend and taskResume routines internally keep track of
> whether they have been called such that a taskResume that comes before a
> taskSuspend will cause the taskSuspend to be nullified? The
> documentation indicates task suspension is additive, but it only seems
> to state this in terms of other states such as pended or delayed.
>
No, a taskResume() call on a task which is not suspended has no effect,
much like a semGive() on a semaphore which has not been taken yet.
Suspetion is a state of a task, which is additive to otehr task attrubutes,
but is only a binary memoryless state by itself.

> For some debugging code, I would like to have a task send to a message
> queue with the task id then taskSuspend itself. The receipient of the
> message would then resume the task. This opens up a window for a race
> condition if the taskResume happens before the taskSuspend unless
> taskSuspend/taskResume keep track of whether taskResume/taskSuspend has
> already been called.

Well, using task suspention for anything other then debugging is
discouraged.
In your case, I could suggest the task uses preemption locking to avoid any
race condition, and since this is only for debugging, the generally
dangerous
preemption locking can be excused:

  taskLock();
 msgQSend( qid, ... );
 taskSuspend(0);
 taskUnlock();

Please note that when the task suspends itself, preemption is re-enabled,
until this task gets to RUN again, then it preemtpion lock will be
momentarily
restored only to be lifted a few instructions thereafter.

>
> I'm wondering whether I need to use another mechanism, such as creating
> a temporary semaphore to send to the server task (extra overhead and
> memory usage to create and delete a semaphore for each operation).
>
> The pthreads code as part of the VxWorks FAQ uses this technique in
> pthread_cond_wait and I wasn't sure if it suffers from this race
> condition or if taskSuspend/taskResume allow it to work properly.

If I understand this correctly, the FAQ implementation for conditional
variable uses taskSuspend() ? If that is indeed the case, I would recommend
against using this particular implementation.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim                Visit:
http://gamla.org.il/english/index.htm
        Consultant                Email: my first name at consultant dot com

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sun Nov  3 21:53:04 2002
From: M Israr Khan <isrark@enabtech.com>
Date: Sun Nov  3 21:53:05 PST 2002
Subject: Hooking exceptions.

Hi,

Is there a way to capture/hook exceptions or page faults in VxWorks. The
system i am working on is running multiple threads and i want to generate
and error log (stack trace), and reboot the system  whenever a thread is
suspended/crashes. 

Regards
M.Israr Khan

From vxwexplo-errs@csg.lbl.gov  Mon Nov  4 04:10:18 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Mon Nov  4 04:10:20 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Mon Nov  4 04:10:16 PST 2002

        Subject: Re: Newbie Interrupt Service Routine Question
        Subject: Re: Tornado/VxWorks newbie question
        Subject: Re: Hooking exceptions.
        Subject: Re: is "register"  C keyword not supported by the GNU compiler in
        Subject: Re: Differences between Auto-Sensing and Auto-Negotiation in Ethernet
        Subject: Re: sysClkRate reasonable values..

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Newbie Interrupt Service Routine Question
Date: Fri, 25 Oct 2002 21:57:51 GMT
From: robotz@robotz.rob (Robotz)
Organization: Randori News - http://www.randori.com - Try our FREE Usenet Scanner!
Message-ID: <3db9b93d.3958838949@news.airband.net>
References: <3db557bb.3671715708@news.airband.net>
Reply-To: robotz@robotz.rob

After a lot of googling and searching the source code, I found the
file m8260IntrCtl.c which appears to have the functions to use the
8260 interrupts.  This is what I've come up with based on an example I
found in a source file, but I'm still not getting any interrupt
signal.  If anyone has any tips of can give some example code it would
be greatly appreciated.   

- -paul

int i;

LOCAL void intRecv( int temp )
{
	i++;
}

 .
 .
 .
	intConnect(	m8260InumToIvec(INUM_IRQ4), 
			(VOIDFUNCPTR)intRecv, 
			0
			);

	intEnable( INUM_IRQ4 );

	/* delay 10 seconds */
	taskDelay(sysClkRateGet() * 10);

	intDisable( INUM_IRQ4 );

	printf( "\n i=%d \n", i );

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado/VxWorks newbie question
Date: Fri, 01 Nov 2002 09:43:34 GMT
From: "who am i" <who@am.i>
Organization: Telenet Internet
Message-ID: <a1sw9.190093$8o4.30339@afrodite.telenet-ops.be>
References: <WlNv9.186023$8o4.29661@afrodite.telenet-ops.be> <b30aa455.0210301214.63095bcb@posting.google.com>

> GUI? Mouse input? Web server? I'm confued here. Anyway, it might be
> easy if memory and image size are not issues. It might be hard if it's
> "real" embeded app.

OK, it is not a small or tiny embedded device.  But still it is embedded.
It's not using PC technology or a mainstream OS (windows CE, windows
embedded, Linux).   Mouse input isn't going to be used on the device itself,
but a touch screen is foreseen for the future...  So that's like a mouse...
16MB of memory should be OK I guess (SH3 CPU).

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Hooking exceptions.
Date: Mon, 4 Nov 2002 07:55:45 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <aq55li$qh4$1@snoopy.bndlg.de>
References: <aq54i1$3nr$1@overload.lbl.gov>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@145.253.156.162

RTFM
- -> excHookAdd( )

Michael

"M Israr Khan" <isrark@enabtech.com> schrieb im Newsbeitrag
news:aq54i1$3nr$1@overload.lbl.gov...
>
> Hi,
>
> Is there a way to capture/hook exceptions or page faults in VxWorks. The
> system i am working on is running multiple threads and i want to generate
> and error log (stack trace), and reboot the system  whenever a thread is
> suspended/crashes.
>
>
> Regards
> M.Israr Khan
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: is "register"  C keyword not supported by the GNU compiler in
 Tornado 2.0?
Date: Mon, 4 Nov 2002 08:59:55 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <aq5cua$dab$1@sparta.btinternet.com>
References: <585c4698.0210311824.80e6adc@posting.google.com> <apuomj$dd4$1@venus.btinternet.com>

> register should only be used on automatic variables:

Even then it is (with most modern compilers) a waste of
time typing it.  The compiler will ignore the 'register'
keyword and use registers to hold variables at the
appropriate times, rather than meticulously loading
and storing non-register variables from/to stack locations
every time one is referenced.

Even some old compilers that allocated registers to 'register'
variables would often genererate better code if 'register'
was not specified.

	David

---------------------------

Newsgroups: comp.arch.embedded,comp.os.vxworks
Subject: Re: Differences between Auto-Sensing and Auto-Negotiation in Ethernet
Date: Mon, 4 Nov 2002 09:09:47 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <aq5dgq$6ia$1@knossos.btinternet.com>
References: <d83bb8e3.0211010955.27e4347f@posting.google.com>

Raymond Yeung wrote:
> I think I know what auto-negotiation is.  But how does auto-sensing
> differ from auto-negotiating?  Is auto-sensing the same as "parallel
> detection algorithm" described in standard reference texts?

It is all done by 'magic' using the 'link test pulses'.

A 10M device will send a single link test pulse about every 16ms.
A 100M device will send a short burst of link test pulses each time.
A device that determines the whether it is receiving single or
bursts of pulses in doing 'auto-detection'.

For autonegotiation information words are passed between the two
transceivers encoded in the link test burst (by minor changes in the
timings - I don't have the spec handy).  One of the words contains
a bit-pattern of supported link protocols and the two transceivers
will agree to use the fastest one that both support.

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: sysClkRate reasonable values..
Date: Mon, 4 Nov 2002 09:51:38 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1036401232.55417@newsreader1.wirehub.nl>
References: <1035882002.428469@newsreader2.wirehub.nl> <29b153d9.0210291302.5b6b717c@posting.google.com> <b30aa455.0210300934.32d2b855@posting.google.com> <1036065656.432162@newsreader2.wirehub.nl> <b30aa455.0211010646.28aa0bba@posting.google.com> <newscache$9dlw4h$a79$1@lnews.actcom.co.il>

Hi,

With respect to the strange findign about the intel 82559 driver.. I
assumed we had T202 Driverpack installed (TDK-13418) installed. we did
not. In the was a SPR# 63430 which said for fei82557End.c:
    setTaskDelay()s to reference sysClkRateGet()

How stupid one can be to overlook this patch..

Cheers,
Renee
- - - - - - - - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

"Leonid Rosenboim" <My_1st_name@Consultant.Com> wrote in message
news:newscache$9dlw4h$a79$1@lnews.actcom.co.il...
> "Karen" <cherubhollyhock@yahoo.com> wrote in message
> news:b30aa455.0211010646.28aa0bba@posting.google.com...
> > "Renee Teunissen"
> <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you
> agree.with.these.terms@mail.zevenaar.org> wrote in message
> news:<1036065656.432162@newsreader2.wirehub.nl>...
> > > Hi Karen,
> > >
> > > What kind of problems are you thinking about ?
> > >
> > > Thanx,
> > > Renee.
> >
> > I don't know. I still can't figure out.
> >
> > One legacy app was running in 60 ticks. We speeded it up to 180
ticks.
> > We ran into many problems. We gave up the idea.
> >
> > But we had a very slow CPU and our App and "many" drivers were
> > originally written for 60 ticks. You start from scratch with a
much
> > faster CPU. I don't know if the same with happen to you.
>
> I doubt that CPU speed is an issue here, I have experience running
> 1KHz sys clock on a 33MHz MC68030, so your 180 is not a serious lot.
>
> It is qutie likely that lots of the old code simply took 60Hz for
granted,
> and it is a rather tedious job to find all the relevant calls and
fix them.
>
> --
> --------------------------------------------------------------------
- ---
>    Leonid Rosenboim                Visit:
> http://gamla.org.il/english/index.htm
>         Consultant                Email: my first name at consultant
dot com
>
>
>
>

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Mon Nov  4 06:48:04 2002
From: sailinder.harpal@philips.com
Date: Mon Nov  4 06:48:05 PST 2002
Subject: Conversion *.S format to *.OMF

Hi all,

Ive been looking for a application which convert *.s (Motorola file generated by VxWorks) to Intel - > OMF386 file.
Ive have seen that more developer are looking for this conversion, maybe someone already had found a solution.
I also read that it could be possible to configure Tornado in such a way that he would generate OMF files automically, is this true ?
Does anyone heared of this or know how to do it ???

I hope te hear from somebody soon,

With Kindest Regards,
Sailinder Harpal

From vxwexplo-errs@csg.lbl.gov  Mon Nov  4 15:06:02 2002
From: Shiv <ShivS@optima-systems.com>
Date: Mon Nov  4 15:06:04 PST 2002
Subject: double-slash Commenting in Tornado 2.0 ?

Is there some kind of switch in the GNU C/C++ (ppc860 toolchain) compiler
that came with Tornado 2.0 to enable "//" commenting ? I've perused through
most of the documents and can't seem to track that down. 

Shiv

From vxwexplo-errs@csg.lbl.gov  Tue Nov  5 04:03:15 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Tue Nov  5 04:03:16 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Tue Nov  5 04:03:13 PST 2002

        Subject: Re: Tornado22/vxworks5.5
        Subject: Re: double-slash Commenting in Tornado 2.0 ?
        Subject: Re: System boot up time
        Subject: Text alignment on PPC?
        Subject: Why Does Swap RAM_LOW_ADRS and RAM_HIGH_ADRS?
        Subject: Re: Conversion *.S format to *.OMF
        Subject: Problems Booting VxWorks5.5 / T2.2

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado22/vxworks5.5
Date: Mon, 04 Nov 2002 13:38:53 +0100
From: Red Fenris <fenris@netcourrier.com>
Organization: No way - anarchy makes me feel better ;)
Message-ID: <aq5ppc$d1t$1@news-reader10.wanadoo.fr>
References: <88aw9.51304$wm6.15618@nwrddc01.gnilink.net> <newscache$venu4h$2e5$1@lnews.actcom.co.il> <d1834426.0210311154.432eb23a@posting.google.com>
Reply-To: fenris@netcourrier.com

webber wrote:

>
>  If not WindRiver, then any personal suggestions welcomed.
> <snip>

Try this for the Web server -  That's an open source project

http://www.goahead.com/webserver/webserver.htm

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: double-slash Commenting in Tornado 2.0 ?
Date: Mon, 4 Nov 2002 16:05:46 -0800
From: <j>
Organization: http://www.cyclonews.com
Message-ID: <3dc70968$3_6@news.cyclonews.com>
References: <aq6vcg$gn0$1@overload.lbl.gov>

- -ansi disables // comments.

- -- jim

"Shiv" <ShivS@optima-systems.com> wrote in message
news:aq6vcg$gn0$1@overload.lbl.gov...
>
> Is there some kind of switch in the GNU C/C++ (ppc860 toolchain) compiler
> that came with Tornado 2.0 to enable "//" commenting ? I've perused
through
> most of the documents and can't seem to track that down.
>
> Shiv

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: System boot up time
Date: Tue, 5 Nov 2002 11:22:33 +0800
From: "Yung" <general_miller@yahoo.com>
Organization: IMS Netvigator
Message-ID: <aq7dhp$t569@imsp212.netvigator.com>
References: <aptfm8$paj1@imsp212.netvigator.com> <4gwx9.17567$V21.499423@news>

Thanks for the advice of you all. Finally I have managed to resolve the
problem. With the wish that some observations may be helpful to the others,
i am trying to summarise my findings as follows:

For the Project Builds "vxWorks_rom" and "vxWorks_romCompress", Tornado
generates the bootable images in 2 main steps:
Step 1: generate the vxWorks runtime image (procedures are identical to the
generation of "vxWorks" image).
Step 2: the above image is then compressed (if necessary) and then linked
with romInit.o and romStart.o to form the final image, which is then to be
ROMed.

In step 2 above, the linker assumes the addresses to be on ROM. Hence the
resulting image can ONLY be run in ROM. When the system starts, the
romStart() routine actually copies only the data segment to RAM and then
calls the decompression routine. The decompression routine executes right on
ROM (with data segment on RAM) and the decompression action is "copying and
decompressing the image from ROM to RAM). In my case it takes 3.5 minutes to
complete for a 7M-large final image (with Cache enabled)!!!

On the other hand, the bootROM is doing something totally different. During
link time (stage 2) it assumes an execution address in the RAM_HIGH range.
But actually it is burnt to ROM for storage and it is run on ROM during
start up. romStart() copies the whole ROM image onto RAM_HIGH before
triggering the decompression routine. But this time decompression is from
RAM to RAM. In my case it has taken less than 15 seconds to complete (same,
with cache enabled).

True. In either case the use of cache is vital to the boot up speed.

What i have done now is to adopt the bootROM way of start-up by altering the
concerned build rules and codes in romStart.
Thanks again!
(The above are based on a 32-bit MIPS platform, Tornado 2.0.2)

"somebody" <sdfs@hotmail.com> wrote in message
news:4gwx9.17567$V21.499423@news...
> If you enable your "code cache" it would really speed up your boot up .
Try
> enabling it in the BSP before decompression.
>             Hadi
> "Yung" <general_miller@yahoo.com> wrote in message
> news:aptfm8$paj1@imsp212.netvigator.com...
> > Hello experts,
> >
> > This happens on a 32-bits 133MHz MIPS platform with Tornado 2.0.2.
> >
> > I use the Tornado project environment to generate the run-time image
> > "vxWorks_romCompress". The resulting image is 3.5Mbyte in size. I burn
it
> > onto Flash memory. It takes 3.5 minutes to boot up which is far too
long!
> >
> > After careful inspection of the romStart.c, i find out that the system
> boots
> > up in the following sequence:
> >
> > - copy the data segment needed by the decompression routine to
> RAM_HIGH_ADRS
> > - execute the decompression routine "deflate" to decompress the
sub-image
> > (vxWorks image) into RAM_LOW_ADRS
> > - Jump to RAM_LOW_ADRS to begin the system.
> >
> > I have found out that all the 3.5 minutes were spent on decompression. I
> > think it is the problem of executing the decompression routine that
> resides
> > in ROM instead of RAM.
> >
> > On the other hand, i have also checked the bootROM routine bootInit.c.
It
> > copies the whole ROM image (text + data + subimage) to RAM first, then
do
> > the decompression on RAM. It is much faster and takes only about 8
seconds
> > for the same size of image (3.5Mbyte).
> > How can i do the same on the run-time image?
> > Any idea?
> >
> >
> >
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Text alignment on PPC?
Date: 04 Nov 2002 22:21:53 -0500
From: "Paul D. Smith" <pausmith@nortelnetworks.com>
Organization: Nortel Networks, Inc. / Billerica, MA
Message-ID: <p565vcu2em.fsf@lemming.engeast.baynetworks.com>
Reply-To: pausmith@nortelnetworks.com

I'm working with VxWorks 5.3.1 (so the GCC 2.7.2 compiler and binutils
"cygnus 2.6" ld etc.)

In our system we have two CPUs performing different tasks.  We load two
images into memory, which actually contain the same code but are linked
at different (static) locations.

The first one is linked to load at 0x100000 (1M), using "ld .. -Ttext
0x100000 ...".  The second one is linked to load above the first.

To compute the offset of the second one I am using ELF tools to
determine the memory size (readelf --program-headers, grabbing the
MemSiz parameter).

Then I am rounding that up to the nearest 4k boundary: according to the
binutils docs I've seen the default alignment is 0x1000 (4K).

However, after doing this the size of the second image in memory is a
_LOT_ larger than the size of the first, by about 60K.  This is
important as there is obviously other stuff I need to load above the
second image so I need to know where it ends.

It _appears_ as though I need to round up to the nearest 64k (0x10000)
boundary.  But, I want to be sure that's true.  I've used ld --version
to show the link script, etc. and I can't find any alignment settings or
anything.

So, can anyone confirm/deny that I need to align the text segment to
load on a 64k boundary, in the above-describe hardware/OS/link
toolchain?  Or is there more to it than that even?

Thanks!

- -- 
- -------------------------------------------------------------------------------
 Paul D. Smith <pausmith@nortelnetworks.com> HASMAT--HA Software Mthds & Tools
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
- -------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Why Does Swap RAM_LOW_ADRS and RAM_HIGH_ADRS?
Date: 5 Nov 2002 00:32:19 -0800
From: xmtang@facri.com (xiaomingtang)
Organization: http://groups.google.com/
Message-ID: <acabfdad.0211050032.1fd1c1d9@posting.google.com>

BOARD = PC 386/486
and from the modification history of Makefile(WRS provided),there is a
line: Swap RAM_LOW_ADRS and RAM_HIGH_ADRS. And they defined
RAM_LOW_ADRS = 00108000 and RAM_HIGH_ADRS=00008000. Why does define
RAM_LOW_ADRS 'NOT LOW' RAM_HIGH_ADRS?  as i know, we generally
configure RAM_LOW_ADRS lower than RAM_HIGH_ADRS.
More question is I totally confused by following code in Makefile
     # ifdef BOOTCODE_IN_RAM
       ROM_TEXT_ADRS  = 00008000 
       ROM_SIZE       = 00090000
     #else
     ......
     #endif
why not configure ROM_TEXT_ADRS in upper address space where ROM
actually is?

Please Help!!!   Thanks in advance.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Conversion *.S format to *.OMF
Date: 5 Nov 2002 00:40:17 -0800
From: xmtang@facri.com (xiaomingtang)
Organization: http://groups.google.com/
Message-ID: <acabfdad.0211050040.651c4b96@posting.google.com>
References: <aq66g4$bat$1@overload.lbl.gov>

I thinks such thing is not very reasonable 'cause OMF386 have more
infomation than S-record. if you really want to do, my suggestion is
than you must get OMF386 Format specifacation first(it is not very
easy!) and S-Record format.

Good Lucky!!

---------------------------

Newsgroups: comp.os.vxworks
Subject: Problems Booting VxWorks5.5 / T2.2
Date: 5 Nov 2002 00:58:30 -0800
From: fabio.roncadi@gambro.com (Fabio Roncadi)
Organization: http://groups.google.com/
Message-ID: <9ec0e92c.0211050058.53ce905d@posting.google.com>

Hello,

I installed Tornado 2.2 package on a Win2k Host for X86 Pentium
target.

I am trying to build a working bootrom.sys to create the first
bootable floppy to begin with.

I proceed exactly in the same way as in the past with T2.0.2/VxWorks
5.4 with the same target hardware... (configuring config.h, pc.h...
building bootrom_uncmp or bootrom_uncmp.bin, mkboot a: bootrom_uncmp,
etc etc...)

When the target boots the loader (V1.6) starts displaying "+" chars
(about 14 rows) and then it hangs... without showing any "blue" boot
screen.

Is there any way to debug the bootrom init. sequence?
I would appreciate any idea, suggestion, comment...

Thanks a lot!

fabio.roncadi@gambro.com

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Tue Nov  5 06:09:26 2002
From: "=?iso-2022-jp?B?GyRCP04+ZRsoQiAbJEI3e0ZzTzobKEI=?=" <K.Nikami@cec-ltd.co.jp>
Date: Tue Nov  5 06:09:28 PST 2002
Subject: send() blocking problem

Hi.

I'm using VxWorks 5.4 with Tornado 2.0.
My program calls send() about 800 times in one second
at variable intervals.
Receiving program works on Windows 2000.

Usually, send() returns with 'OK' immediately.
But after several time (5 seconds - 10 minutes) , send() 
blocks about 20msec, at last, send() infinitely blocks.

I set TCP_NODELAY and FIONBIO to that socket.
But that seems no effect to the problem above.

If send() is called about 300 times in one second, this problem
doesn't reproduce.

Please give me several pieces of advice.

Thanks.

Ken

Kenjiro Nikami
Computer Engineering & Consulting, Ltd. 
Japan.

From vxwexplo-errs@csg.lbl.gov  Thu Nov  7 01:29:08 2002
From: "luotian" <luotian@oceanus.com.cn>
Date: Thu Nov  7 01:29:09 PST 2002
Subject: what is it in build output?

when I finished building  the vxworks, there was a sentence in the last line of the build output,"vxWorks: 5401492(t) + 702100(d) +  1667052(b) = 7770644 (8941036 unused)".
Could someone tell me what the three sections , "5401492(t) + 702100(d) +  1667052(b) ",mean? 
What are the t/d/b 

From vxwexplo-errs@csg.lbl.gov  Thu Nov  7 05:09:26 2002
From: kang@accton.com.tw
Date: Thu Nov  7 05:09:27 PST 2002
Subject: .text relocation overflow ...

Dear All,

? We are using Tornado 2.0/VxWorks5.4 for ARM7 CPU taget
? We encouter .text relocation overflow issue.
? It seems that Tornado 2.0/VxWorks5.4 for ARM7 can only produce COFF
format and COFF can't have more than 65535 relocations in a session.
? We have tried the -split-by-reloc ld option, but it doesn't help.
? We have tried many compiler/linker options but none of them can solve the
.text reloc overflow: 0x....>0xffff issue.
? However, if we exclude few modules from our application then the build
succeeds and vxWorks image is created.

? Could anyone help us on this??

/Lewis

**********************************************************************************
This email and any files transmitted with it are confidential and intended
solely for the use of  the individual or entity to whom they are addressed.
If you have received it by mistake, please  let us know by e-mail reply and
delete it from your system; you may not copy this message or  disclose its
contents to anyone.  Please note that any views or opinions presented in
this  email are solely those of the author and do not necessarily represent
those of the company.

Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.
Accton Technology Corporation,  No. I Creation Road III, Science-based
Industrial Park, Hsinchu 300, Taiwan.,  www.accton.com.tw
Thank you in advance for your cooperation.
**********************************************************************************
The claim below is in Chinese.
ʹqllΨǰeɪ[ɮקyKzAȨѶla}WҸ
Hι ϥΡCYz]~Ӧ즹qllAбzQιqllqڭ̡AåBb
ztΤRCzoNoǤ󭫻sαN䴦SHC
Ъ`NGʹqll󤤤ݪkηNY@̩ҬAäMNq
߳C̫AˬdʹqllΨɮ׬O_qfrsbC
zLʹqllǻqfr]ӵoͤl`AqtvdCP
±ztXI
ުѥq
a}Gs˥Ǥu~ϬsT@
}Gwww.accton.com.tw
**********************************************************************************

From vxwexplo-errs@csg.lbl.gov  Thu Nov  7 16:29:44 2002
From: "=?GB2312?Q?=B6=AD=BF=A1?=" <dongjun@fiberhome.com.cn>
Date: Thu Nov  7 16:29:46 PST 2002
Subject: Re: Vx Exploder Digest

hi,luotian
 
>Subject: what is it in build output?
>
>**********
>
>From vxwexplo-errs@csg.lbl.gov  Thu Nov  7 01:29:08 2002
>From: "luotian" <luotian@oceanus.com.cn>
>Date: Thu Nov  7 01:29:09 PST 2002
>Subject: what is it in build output?
>
>when I finished building  the vxworks, there was a sentence in the last line of the build output,"vxWorks: 5401492(t) + 702100(d) +  1667052(b) = 7770644 (8941036 unused)".
>Could someone tell me what the three sections , "5401492(t) + 702100(d) +  1667052(b) ",mean? 
>What are the t/d/b 
>
t means text, which is the execute code reside
d means data, which is where the initialized global variables reside
b means bss, which is where the uninitialized global variables reside

From vxwexplo-errs@csg.lbl.gov  Thu Nov  7 22:59:39 2002
From: "Nithya P" <nithyap490@hotmail.com>
Date: Thu Nov  7 22:59:41 PST 2002
Subject: TCL sample

Hi Everybody,
  I'm newbie to vxWorks & TCL.
Can anybody give me a sample tcl file and methods of compliling& executing 
it??
Is there any tutorial on TCL availble in the website??

Thanks
Nithya

_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

From vxwexplo-errs@csg.lbl.gov  Fri Nov  8 04:03:29 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Fri Nov  8 04:03:30 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Fri Nov  8 04:03:26 PST 2002

        Subject: Re: Problems Booting VxWorks5.5 / T2.2
        Subject: Whats the difference between an ATA driver and and IDE driver
        Subject: msgQCreate --- how large is maxMsgs
        Subject: Why the address down after linker?
        Subject: doubts on differences between vxworks5.4 and vxworks5.5?
        Subject: Re: Problems Booting VxWorks5.5 / T2.2
        Subject: How to build a .out files as EXTRA_MODULES into Vxworks image?
        Subject: Re: Whats the difference between an ATA driver and and IDE driver
        Subject: Re: timerWdHandler
        Subject: Creating NFS directories (via nfsDrv) with 0777 permissions
        Subject: Re: multi-ICE backend for Tornado?
        Subject: Re: msgQCreate --- how large is maxMsgs
        Subject: tftp download file too big problem
        Subject: DosFs2.2 question? pls help
        Subject: Re: Help on network card configuration
        Subject: Re: Any documentation on STL included with vxWorks 5.4.2 (Tornado 2.0.2)
        Subject: Re: How to build a .out files as EXTRA_MODULES into Vxworks image?
        Subject: Re: How to build a .out files as EXTRA_MODULES into Vxworks image?
        Subject: How cacheDmaMalloc ( ) work?
        Subject: motorola FADS860 cpm network boot failure
        Subject: Re: How cacheDmaMalloc ( ) work?
        Subject: Re: DosFs2.2 question? pls help
        Subject: Message Queues from ISRs
        Subject: Re: Printing a 32 bit value
        Subject: x86 motherboards that are well-supported?
        Subject: Loading files using target shell
        Subject: Re: Exception calling timer_create
        Subject: Re: x86 based PC104 CPU Board
        Subject: Re: Tornado22/vxworks5.5
        Subject: Can gcc support __try and __except or alike?
        Subject: SNMP in Vxworks have security risk??
        Subject: Re: motorola FADS860 cpm network boot failure
        Subject: Diab compiler and StrongARM
        Subject: Re: x86 motherboards that are well-supported?

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Problems Booting VxWorks5.5 / T2.2
Date: Tue, 5 Nov 2002 13:21:10 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <aq8d3i$adi$1@snoopy.bndlg.de>
References: <9ec0e92c.0211050058.53ce905d@posting.google.com>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@145.253.156.162

Hi Fabio,

is INCLUDE_PC_CONSOLE set in config.h ?
If not, you get the described behaviour. Your boot menu should be sent to
COM1.

Michael

"Fabio Roncadi" <fabio.roncadi@gambro.com> schrieb im Newsbeitrag
news:9ec0e92c.0211050058.53ce905d@posting.google.com...
> Hello,
>
> I installed Tornado 2.2 package on a Win2k Host for X86 Pentium
> target.
>
> I am trying to build a working bootrom.sys to create the first
> bootable floppy to begin with.
>
> I proceed exactly in the same way as in the past with T2.0.2/VxWorks
> 5.4 with the same target hardware... (configuring config.h, pc.h...
> building bootrom_uncmp or bootrom_uncmp.bin, mkboot a: bootrom_uncmp,
> etc etc...)
>
> When the target boots the loader (V1.6) starts displaying "+" chars
> (about 14 rows) and then it hangs... without showing any "blue" boot
> screen.
>
> Is there any way to debug the bootrom init. sequence?
> I would appreciate any idea, suggestion, comment...
>
> Thanks a lot!
>
> fabio.roncadi@gambro.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Whats the difference between an ATA driver and and IDE driver
Date: Tue, 05 Nov 2002 18:17:55 -0700
From: James Scott <james.scott@motorola.com>
Organization: OneIT Directory Services News Site
Message-ID: <3DC86DC3.28DAA89E@motorola.com>

I have been under the assumption that ATA was a marketing term and
IDE was a hardware term for the same thing, but looking at the
driver source tree, and documentation, I see that VxWorks has two
distinct drivers.  One for ATA and one for IDE.

What is the difference and why would I choose one over the other?

---------------------------

Newsgroups: comp.os.vxworks
Subject: msgQCreate --- how large is maxMsgs
Date: 5 Nov 2002 18:37:05 -0800
From: lin_mu@hotmail.com (Forest)
Organization: http://groups.google.com/
Message-ID: <f92014ed.0211051837.3b76b499@posting.google.com>

Dear All:

I try to find out how many messages can be queued in a msgQ,
but the vxWorks manual don't say anything in this regard.

for example:

msgQCreate (int maxMsgs, int maxMsgLength, int options);

how large can maxMsgs be?

Also in msgQLib.h, in the following structure

typedef struct			/* MSG_Q_INFO */
    {
    int     numMsgs;		/* OUT: number of messages queued */
    int     numTasks;		/* OUT: number of tasks waiting on msg q */

    int     sendTimeouts;	/* OUT: count of send timeouts */
    int     recvTimeouts;	/* OUT: count of receive timeouts */

    int     options;		/* OUT: options with which msg q was created */
    int     maxMsgs;		/* OUT: max messages that can be queued */
    int     maxMsgLength;	/* OUT: max byte length of each message */

    int     taskIdListMax;	/* IN: max tasks to fill in taskIdList */
    int *   taskIdList;		/* PTR: array of task ids waiting on msg q */

    int     msgListMax;		/* IN: max msgs to fill in msg lists */
    char ** msgPtrList;		/* PTR: array of msg ptrs queued to msg q */
    int *   msgLenList;		/* PTR: array of lengths of msgs */

    } MSG_Q_INFO;

What's meaning of msgListMax?

Any suggetion or pointer to documents will be highly appreciated.

Regards

Lm

---------------------------

Newsgroups: comp.os.vxworks
Subject: Why the address down after linker?
Date: 5 Nov 2002 19:28:13 -0800
From: xmtang@facri.com (xiaomingtang)
Organization: http://groups.google.com/
Message-ID: <acabfdad.0211051928.615d67a5@posting.google.com>

rule in Makefile is:
boot: startup.o vxboot.o
	$(LD) -X -N -e startup -Ttext 000f0000 -Tdata 00110000 -o $@ \
		startup.o vxboot.o \
		$(WIND_BASE)/target/lib/lib$(CPU)$(TOOL)vx.a
	$(ROMSIZEPROG) -b fff0 boot
	size386 boot

using command objdump386 -d boot|more

boot:     file format a.out-i386
Disassembly of section .text:
00000000 <startup-f0000> jmp    00000002 <startup-efffe>
00000002 <startup-efffe> cli
00000003 <startup-efffd> addr16 lidt %cs:0x2a0
0000000d <startup-efff3> addr16 lgdt %cs:0x2b0
00000017 <startup-effe9> movl   %cr0,%eax
0000001a <startup-effe6> orw    $0x1,%ax
0000001e <startup-effe2> movl   %eax,%cr0
00000021 <startup-effdf> jmp    00000023 <startup-effdd>
00000023 <startup-effdd> movw   $0x10,%ax
 My question is why the address is down from startup(f0000) rather
than up as f0002,f0003,f000d?
BUT using command nm386 boot|more

000f0002 t InitSC400
000f02e8 t ___gnu_compiled_c
000f0a88 t ___gnu_compiled_c
001102a0 B __bss_start
001102a0 D __edata
00129f18 B __end
000f3b68 T __etext
from indicated above, the address of Text Code is UP(increasing) from
f0000 and the address of DS or BSS is UP from 00110000.

---------------------------

Newsgroups: comp.os.vxworks
Subject: doubts on differences between vxworks5.4 and vxworks5.5?
Date: 5 Nov 2002 22:12:06 -0800
From: vxnerd@rediffmail.com (subbarayan)
Organization: http://groups.google.com/
Message-ID: <f81c4277.0211052212.50881489@posting.google.com>

dear mentors,
   Could any of u explain me the version compatibility issues of
tornado2.0/vxworks 5.4 and the future versions of tornado and vxworks
released after 2.0/5.4 version?It will be helpful to know if any one
say me what exactly is the difference between vxworks5.4/tornado2.0
and future released versions of vxworks/tornado?
In particular,I would like to know whether the driver developed for
pci card with tornado2.0/vxworks5.4 work well in further realeased
vxworks versions like 5.5?Are any changes required in driver level to
make the code developed in 5.4 to work with further released versions?
Any pointers will be highly appreciated.Advanced thanks to the persons
replying .

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Problems Booting VxWorks5.5 / T2.2
Date: 5 Nov 2002 23:39:10 -0800
From: fabio.roncadi@gambro.com (Fabio Roncadi)
Organization: http://groups.google.com/
Message-ID: <9ec0e92c.0211052339.6c8d1604@posting.google.com>
References: <9ec0e92c.0211050058.53ce905d@posting.google.com> <aq8d3i$adi$1@snoopy.bndlg.de>

Hi Michael,

yes, INCLUDE_PC_CONSOLE is set and sent to COM1, but the behavior is the same...

Thanks

Fabio

>"Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message 
> news:<aq8d3i$adi$1@snoopy.bndlg.de>...
> Hi Fabio,
> 
> is INCLUDE_PC_CONSOLE set in config.h ?
> If not, you get the described behaviour. Your boot menu should be sent to
> COM1.
> 
> Michael
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: How to build a .out files as EXTRA_MODULES into Vxworks image?
Date: 6 Nov 2002 00:03:11 -0800
From: r1y2g3@sina.com (Eagle)
Organization: http://groups.google.com/
Message-ID: <3d425998.0211060003.128b4ceb@posting.google.com>

How to build a .out files as EXTRA_MODULES into Vxworks image?
and how to build more than one .o files as EXTRA_MODULES into Vxworks image?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Whats the difference between an ATA driver and and IDE driver
Date: Wed, 6 Nov 2002 11:20:13 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$1zd55h$op4$1@lnews.actcom.co.il>
References: <3DC86DC3.28DAA89E@motorola.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"James Scott" <james.scott@motorola.com> wrote in message
news:3DC86DC3.28DAA89E@motorola.com...
> I have been under the assumption that ATA was a marketing term and
> IDE was a hardware term for the same thing, but looking at the
> driver source tree, and documentation, I see that VxWorks has two
> distinct drivers.  One for ATA and one for IDE.
>
> What is the difference and why would I choose one over the other?
>
The generic terms: IDE is indeed the hardware bus to connect disk drives
to host adapter, while ATA is  the protocol implemented over IDE and other
alternative busses (such as PCMCIA, CompacfFlash etc.) that these disk
drives respond to There is also another protocol ATAPI which too works
over the IDE bus and is used for CD-ROM, CDRW and Tape drive devices.

On the VxWorks driver issue, the IDE driver is simply an old one, which has
been subsequently replaced by the ATA driver, the later also has support for
alternative busses such as PCMCIA. ataDrv completely supercedes the ideDrv,
and I have no idea why idDrv was not completely phased out of the
distribution.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: timerWdHandler
Date: Wed, 6 Nov 2002 15:44:28 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1036593931.871256@newsreader2.wirehub.nl>
References: <1036510176.145630@newsreader1.wirehub.nl>

Hi,

I found the reason why this happed. If your task -which created the
timer- does not exists anymore, the warning can happen. While a timer
is active/running, the task that created the timer must not die of be
deleted.

Just wanted to let you know.

Cheers,
Renee
- - - - - - - - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

> Hi,
>
> In a timer application I get errors like "timerWdHandler: kill
failed
> (timerid=0x..., tid=.. errno=0x16)
>
> Anyone seen this one before?
>
> Cheers,
> Renee
> - - - - - - - -
> Renee A. Teunissen
> PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
> T.+31-(0)35-6926969, M.+31-(0)6-22778313,
> http://www.pts.nl, <first_name>@pts.nl
> personal link page: http://wittenburg10c.nl/db/dest/links.html
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Creating NFS directories (via nfsDrv) with 0777 permissions
Date: 6 Nov 2002 08:30:57 -0800
From: eyal.rozenblat@seabridgenetworks.com (Eyal Rozenblat)
Organization: http://groups.google.com/
Message-ID: <12f96c64.0211060830.82cea8f@posting.google.com>

All,
  I am using NFS client component, to locate my persistent data on a
UNIX machine. When using the open(fileName, flag, FSTAT_DIR) for
creating directories, I see no option of defining the permission level
for this created directory.
Is there one ? How ? (Using ioctl, or'ing FSTAT_DIR with 0777 ???)
Same for creating files. Then I put the mode to be 0777 but get on the
UNIX only the default 644 permission level.
Is there any place that "masks" my requests in some VxWorks
configuration file?

An example would be very welcome.

Thanks,
Eyal

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: multi-ICE backend for Tornado?
Date: Wed, 06 Nov 2002 16:43:30 +0000
From: c.news.0211@csd.co.uk
Message-ID: <3DC946B2.529AECB@csd.co.uk>
References: <Aqlx9.15285$M63.836419@news.bora.net>

shryoo@lge.com wrote:

> Hello all, have you ever heard the multi-ICE backned for Tornado?
> If you have any information for this, please let me know.
> 
> Thanx in advance.

The Multi-ICE backend for Tornado (wdbmice), like other Tornado
backends, creates a communications path between the target server and
the target, in this case, using the ARM Multi-ICE product. wdbmice can
be used in two modes: agentless and agent-based. When used agentless, it
can be used to load kernels/bootroms onto bare boards (i.e. those
without ROM/Flash devices), debug startup code, interrupt handlers etc..
In agent-based mode, it communicates with an agent configured into the
kernel via the Debug Communications Channel and can be used to load
modules, spawn tasks etc..

We (CSD - http://www.csd.co.uk) wrote wdbmice for ARM but you will have
to
contact ARM if you want to use it.

I hope this helps.

- -- 
   Christopher

- ---------------------------------------------------------------
Christopher Partington                      +44 (0) 1223 518815
CSD, No.1 Andersons Court, Newnham Road, Cambridge, CB3 9EZ, UK

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: msgQCreate --- how large is maxMsgs
Date: 6 Nov 2002 10:26:27 -0800
From: lin_mu@hotmail.com (Forest)
Organization: http://groups.google.com/
Message-ID: <f92014ed.0211061026.605584b5@posting.google.com>
References: <f92014ed.0211051837.3b76b499@posting.google.com> <newscache$rld55h$9p4$1@lnews.actcom.co.il>

Thanks a lot , Leonid.

---------------------------

Newsgroups: comp.os.vxworks
Subject: tftp download file too big problem
Date: Wed, 6 Nov 2002 13:41:48 -0500
From: "Harjinder Chayra" <harjinder.chayra@imedia.com>
Organization: Storm Internet Services
Message-ID: <aqbnpl$2ri$1@news.storm.ca>
Sender: terayon@gw-terayon.storm.ca

When using tftp (tftpGet) to download a file, is there a mechanism where we
can be informed that the file is bigger than the space allocated for it?,
otherwise memory will get corrupted.

Thanks

Harjinder

---------------------------

Newsgroups: comp.os.vxworks
Subject: DosFs2.2 question? pls help
Date: 6 Nov 2002 14:30:47 -0800
From: roswel_ajf@hotmail.com (roswell)
Organization: http://groups.google.com/
Message-ID: <6dcae13d.0211061430.3b7dd90@posting.google.com>

my dosfs2.2 is giving this junk at startup time. i have no clue what
this mean. i have a 32mb ramdisk.

Retrieved old volume params with %33 confidence:
Volume Parameters: FAT type: FAT32, sectors per cluster 0
  0 FAT copies, 0 clusters, 0 sectors per FAT
  Sectors reserved 0, hidden 0, FAT sectors 0
  Root dir entries 0, sysId (null)  , serial number 0
  Label:"           " ...
Disk with 65536 sectors of 512 bytes will be formatted with:
Volume Parameters: FAT type: FAT16, sectors per cluster 2
  2 FAT copies, 32623 clusters, 128 sectors per FAT
  Sectors reserved 1, hidden 0, FAT sectors 256
  Root dir entries 512, sysId VXDOS16 , serial number 0
  Label:"           " ...

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Help on network card configuration
Date: Wed, 06 Nov 2002 15:26:15 -0700
From: Marcos Gallego <marcos.gallego@ericsson.com>
Organization: Ericsson Data Services Americas
Message-ID: <3DC99706.EAD1F84B@ericsson.com>
References: <apgftl$fjp2@imsp212.netvigator.com>

Hi Lawrence,
You can get a DOS boot diskette and boot with the DOS.
THen, you can get the 3COM installation disk and look for one application that
do a diagnostic on the network card you have. This is why I suggest to have a
DOS boot disk in order to run that diag application. After that, you can change
or read the network card configuration.

Hope this helps,

Marcos

Lawrence Lo wrote:

> Hi
>
> I had problems in connecting the target server to the target agent over
> ethernet. I got the rpccore timeout. I booted the target by floppy and have
> added 'o=elPci' at the end of boot parameter. (I use 3c509c-tx ethernet
> card).
>
> However it seems that the card is not initialized and attached after VxWorks
> is booted from floppy. I want to know how I could configure the IRQ and I/O
> address of the 3c509 card?
>
> Thanks a lot for your help!
>
> Lawrence

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Any documentation on STL included with vxWorks 5.4.2 (Tornado 2.0.2)
Date: 7 Nov 2002 00:15:23 GMT
From: Denis Perelyubskiy <kiev78@dslextreme.com>
Message-ID: <slrnasjc39.2du.kiev78@finch.lecs.cs.ucla.edu>
References: <a7b7bb67.0211060738.7a564dad@posting.google.com>

Frank,

 * frankg <FrankGleeson@motorola.com> [11-Wed-02 07:38 -0800]:
 >
 > I am using vxWorks 5.4.2 and INCLUDEing the SGI STL by having
 > #define INCLUDE_CPLUS_STL in configAll.h.

 > A co-worker wants to use the STL bitset<> template.
 > I can not find either bitset or bitvector headers anywhere
 > in our vxWorks distribution. Did windriver choose to ommit 
 > portions of SGI's STL? Is there a list anywhere of what is
 > included and what is excluded? I guess it could also be a 
 > version issue if the version of the STL shipped with vxWorks is
 > much older than the current release.

 > I have been looking through the headers supplied with
 > vxWorks 5.4.2 like atl.h and stl_algo.h etc. There does
 > not seem to be any SGI version information in there.
 > There is a Copywright (c) 1996, can I infer a version
 > number from this? Or was there only 1 release of the SGI
 > STL so that versioning info is not required?

While I can't answer your specific question, maybe this will
help. I've used this library on linux worry-free (for a
raytracer, nothing serious though)... From the page it looks
like vxworks is supported as well...

   http://www.stlport.org/product.html

good luck,

denis

- -- 
'From' email address is used as a sink. Not read. Ever.
Instead, send to [t-h-e-u-k-r-a-i-n-i-a-n|h-o-t-m-a-i-l|c-o-m]
(remove dashes, replace the first vertical bar with @, 
and second with a dot)

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How to build a .out files as EXTRA_MODULES into Vxworks image?
Date: Wed, 6 Nov 2002 19:45:53 -0500
From: "BruceL" <bruce@yahoo.nospam.com>
Message-ID: <aqcd8f$ijc$1@bob.news.rcn.net>
References: <3d425998.0211060003.128b4ceb@posting.google.com>

"Eagle" <r1y2g3@sina.com> wrote in message
news:3d425998.0211060003.128b4ceb@posting.google.com...
> How to build a .out files as EXTRA_MODULES into Vxworks image?
> and how to build more than one .o files as EXTRA_MODULES into Vxworks
image?

Not exactly sure, but I think you want to build a .out file from the .elf
file.  If this is true, use the convert.exe utility from WindRiver and add
the command line to the POST_BUILD_RULES (or some such thing) macro in the
build properties dialog.

Bruce

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How to build a .out files as EXTRA_MODULES into Vxworks image?
Date: 6 Nov 2002 18:34:29 -0800
From: redracoon@163.com (racoon)
Organization: http://groups.google.com/
Message-ID: <99d3b4cc.0211061834.769d8a7e@posting.google.com>
References: <3d425998.0211060003.128b4ceb@posting.google.com>

r1y2g3@sina.com (Eagle) wrote in message news:<3d425998.0211060003.128b4ceb@posting.google.com>...
> How to build a .out files as EXTRA_MODULES into Vxworks image?
> and how to build more than one .o files as EXTRA_MODULES into Vxworks image?

I am still a newbie in vxworks,but I think you can do it by the following steps:
1)create a bootable project,which is based on your bsp;
2)edit your project's makefile,add "EXTRA_MODULES= .out"
then build your project.
If you want to build more than one .o files,just edit makefile like follows:
EXTRA_MODULES=a.o b.o c.o...
Hope this help.

---------------------------

Newsgroups: comp.os.vxworks
Subject: How cacheDmaMalloc ( ) work?
Date: 6 Nov 2002 19:11:38 -0800
From: ryeung@earthlink.net (Raymond Yeung)
Organization: http://groups.google.com/
Message-ID: <d83bb8e3.0211061911.b5fbdfd@posting.google.com>

My board uses 8260, and has two Ethernet devices configured, one 10BaseT
and the other 100BaseT.  Both devices use cacheDmaMalloc() to allocate non-
cacheable memory for buffering.

Recently, I need to increase the buffer size of 100BaseT.  As I do so,
the other device fails to initialize because cacheDmaMalloc() returns
NULL.

I've 16Mbytes of SDRAM on 60x-bus, and 4Mbytes of SDRAM on local-bus.
Does cacheDmaMalloc allocate memory off the 60x-bus heap,
and mark via MMU the appropriate page(s) non-cacheable?  The total amount of
non-cacheable memory I need from the 2 devices are at the most around 
1 Mbytes.  What caused the failure?  Are there some #define's that govern
the amount of memory I can cacheDmaMalloc?  Any idea on what I may try?

I've checked sysPhysMemDesc[] in sysLib.c.  All 16Mbytes of 60x-bus SDRAM
are mapped as cacheable.  And in config.h, the LOCAL_MEMORY_SIZE is also
16Mbytes.

Thanks,
Raymond

---------------------------

Newsgroups: comp.os.vxworks
Subject: motorola FADS860 cpm network boot failure
Date: 6 Nov 2002 22:05:24 -0800
From: challa23@yahoo.com (Murali Challa)
Organization: http://groups.google.com/
Message-ID: <c1e650d9.0211062205.4ab7c7f9@posting.google.com>

Hi !!
This is Murali Challa from Bangalore,India
We are using motorola FADS860 as VxWorks target.
Torando 2.0 with ads860 BSP.I edited config.h to enable cpm as boot
device ,made the bootrom_uncmp.hex and burnt the flash..
My Boot parameters

bootdevice:cpm
processor No:0
Unit NO:0
hostname:Murali
filename:c:/tornado/target/config/ads860/vxworks
inet on ethernet(e):192.168.1.38:ffffff00
inet on host:192.168.1.230
ftploginame:user
pwd:user
flags:0x00

vxworksboot]@

attached TCP/IP interface to cpm0
attaching network interface to lo0..done
Loading...

Error Loading boot file errorno:0xd003

vxworksboot]

I started ftp server on the host specifying the file name with user Id
and pwd before giving @ command.
I tested the FTP server from other system .Its is working fine.
I tried tsfs boot.It is working fine.At shell promp 
- ->ifShow
It is showing only local loop back device lo0.(127.0.0.1)

Plz help me how to configure BSP and Network to boot over the network
with cpm network interface..

I have been struggling for a long time ....

Thankx in advance

Murali Challa

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How cacheDmaMalloc ( ) work?
Date: Wed, 6 Nov 2002 23:20:54 -0800
From: "Dan Gold" <dgold1@san.rr.com>
Organization: Mailgate.ORG Server - http://www.Mailgate.ORG
Message-ID: <aqd4cl$ksr$1@newsreader.mailgate.org>
References: <d83bb8e3.0211061911.b5fbdfd@posting.google.com>
Sender: gold@ensemble.com

Raymond Yeung wrote in message ...
>My board uses 8260, and has two Ethernet devices configured, one 10BaseT
>and the other 100BaseT.  Both devices use cacheDmaMalloc() to allocate non-
>cacheable memory for buffering.
>
>Recently, I need to increase the buffer size of 100BaseT.  As I do so,
>the other device fails to initialize because cacheDmaMalloc() returns
>NULL.
>
>I've 16Mbytes of SDRAM on 60x-bus, and 4Mbytes of SDRAM on local-bus.
>Does cacheDmaMalloc allocate memory off the 60x-bus heap,
>and mark via MMU the appropriate page(s) non-cacheable?

It depends, but mainly yes.  cacheDmaMalloc() definitely allocates a chunk
of memory from the heap that IIRC is page aligned (via memalign()), then
marks the appropriate pages non-cacheable, via PTEs and the MMU.  It
allocates memory from the heap.  If your heap consists solely of 60x bus
memory, then yes, it allocates memory from a 60x bus heap.  I have seen (and
participated in) some designs that add the local bus memory to the heap (via
memAddToPool()).  In that case results can vary...

Do you know what the 4MB of local bus memory is used for, i.e. is it used
for anything in the Ethernet driver ?

I assume when you say increase buffer size you mean increasing the number of
Rx buffers in the driver's pool ?  Are you also increasing the number of Rx
BDs or just the buffers ?

>The total amount of
>non-cacheable memory I need from the 2 devices are at the most around
>1 Mbytes.  What caused the failure?  Are there some #define's that govern
>the amount of memory I can cacheDmaMalloc?  Any idea on what I may try?

I don't know what caused the failure, but you might try doing a memShow()
and memShow(1) right before you do the cacheDmaMalloc() and see what the
heap looks like.  I don't know of any limitations on memory that you can
cacheDmaMalloc().  When you do a memShow() does it show you have 16 MBytes
total memory ?

I suppose you could also try and emulate the cacheDmaMalloc() yourself with
memalign() and vmBaseStateSet().

>I've checked sysPhysMemDesc[] in sysLib.c.  All 16Mbytes of 60x-bus SDRAM
>are mapped as cacheable.  And in config.h, the LOCAL_MEMORY_SIZE is also
>16Mbytes.

Are you using the DBATs for anything (i.e. memory) that could cause problems
?

  hth,
   Dan Gold   gold@ensemble.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: DosFs2.2 question? pls help
Date: Thu, 7 Nov 2002 10:39:57 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$yr675h$8n8$1@lnews.actcom.co.il>
References: <6dcae13d.0211061430.3b7dd90@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"roswell" <roswel_ajf@hotmail.com> wrote in message
news:6dcae13d.0211061430.3b7dd90@posting.google.com...
> my dosfs2.2 is giving this junk at startup time. i have no clue what
> this mean. i have a 32mb ramdisk.
>
> Retrieved old volume params with %33 confidence:
> Volume Parameters: FAT type: FAT32, sectors per cluster 0
>   0 FAT copies, 0 clusters, 0 sectors per FAT
>   Sectors reserved 0, hidden 0, FAT sectors 0
>   Root dir entries 0, sysId (null)  , serial number 0
>   Label:"           " ...
> Disk with 65536 sectors of 512 bytes will be formatted with:
> Volume Parameters: FAT type: FAT16, sectors per cluster 2
>   2 FAT copies, 32623 clusters, 128 sectors per FAT
>   Sectors reserved 1, hidden 0, FAT sectors 256
>   Root dir entries 512, sysId VXDOS16 , serial number 0
>   Label:"           " ...

First, if you do not feel you need this diagnostics, you should set the
"quiet"
flag when you cal dosFsVolFormat(). These really dont mean a lot
when a RAM drive is formatted.

When you are about to format a volume, the format routine will print out
the current format parameters as recorded in the current boo tblock, with
an estimate how reasonable these parameters are, which is that confidence
percentage.
Them if the old params seems resonably sane, format will assume them as
default, otherwise it will calculate the default format parameters based
on volume size, and will call an optional callback that can be used by
the application to override any of the defaults (old or calculated), and
finally, the parameters are printed when the volume is in fact formatted.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Message Queues from ISRs
Date: Thu, 7 Nov 2002 14:59:18 +0000 (UTC)
From: "Steve Comfort" <sdc@ccii.co.za>
Organization: Mailgate.ORG Server - http://www.Mailgate.ORG
Message-ID: <0f742a96c8a1f10b80dbe198124e4e89.105305@mygate.mailgate.org>

I'm trying to decouple an ISR from the rest of a driver by posting a
message to a task, which in turn is supposed to call a higher layer
receive function in the driver. Here's what the send routine looks like:

         sent = msgQSend(ccStmRxMsgQId,
			 MESSAGE,  /* (char *)&data_msg, */
			 CCSTM_MAX_RX_MSG_SIZE, 
			 NO_WAIT,
		         MSG_PRI_NORMAL);
	if (ERROR != sent)
	{
           DRV_MPT (DRV_MPT_FLOW,"Msg Q'd on Q %p\n",
	            ccStmRxMsgQId,0,0,0,0,0);
        }
        else
        {
	   switch (errno)
             ...

Here CCSTM_MAX_RX_MSG_SIZE = 1, and MESSAGE is just a single character.

The receive routine is

		bytes_received = msgQReceive(ccStmRxMsgQId,
		                             rx_buffer,
		                             CCSTM_MAX_RX_MSG_SIZE,
		                             NO_WAIT);
		if ((ERROR != bytes_received) &&
		    (0 > bytes_received))

Although the ISR claims it has sent the message, this is untrue (maybe
with NO_WAIT this is correct??).

When I do a msgQShow here's what I get :

Message Queue Id    : 0x7efef94   
Task Queueing       : FIFO      
Message Byte Len    : 1         
Messages Max        : 1         
Messages Queued     : 0         
Receivers Blocked   : 0         
Send Timeouts       : 0         
Receive Timeouts    : 870   

The question is, what am I doing wrong?

- -- 
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Printing a 32 bit value
Date: Thu, 7 Nov 2002 19:39:13 +0000 (UTC)
From: "Graham Baxter" <gbaxter@NOSPAMbcs.org.uk>
Organization: BT Openworld
Message-ID: <aqefh1$pop$1@venus.btinternet.com>
References: <Ixyy9.1171$9T2.98958455@newssvr14.news.prodigy.com>

Charles,

Try something like:

*((unsigned long *)&pMblk->mBlkHdr.mData[i])

Take the address of the char, cast it to a pointer to long, de-reference it.

I hope this helps.

- --
Regards,

Graham Baxter
Freelance Software Engineer (VxWorks and pSOS BSPs)
Graham Baxter (Software) Limited
gbaxter@NOSPAMbcs.org.uk

"Charles Krinke" <someone@pacbell.net> wrote in message
news:Ixyy9.1171$9T2.98958455@newssvr14.news.prodigy.com...
> Well, I thought I was a bit smarter then this, but I cant seem to see this
> one.
>
> I have a subroutine where I want to print the data in an Mblk as 32 bit
> dwords. I can print the individual bytes of pMblk->mBlkHdr.mData just fine
> using the construct (char)pMblk->mBlkHdr.mData[i] where i is going from 0
to
> pMblk->mBllHdr.mLen.
>
> The problem occurs when I want to make i go from 0 to mLen in steps of 4
and
> print out 32 bit values of the contents of mData. When I say
> (ULONG)pMblk->mBlkHdr.mData[i], where I know that the 4 bytes are say
> "12345678", I get "00000078" instead.
>
> So, why am I not able to print out all of the bytes in a 32 bit mData with
> one statement. This must be something really simple I am missing here.
>
> Charles
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: x86 motherboards that are well-supported?
Date: 7 Nov 2002 12:56:19 -0800
From: danderson@kns.com (Don)
Organization: http://groups.google.com/
Message-ID: <b2f97e75.0211071256.9fa0581@posting.google.com>

We are looking at running VxWorks 5.4 on a "standard" PC. I am looking
for suggestions on ones that people have had few problems getting the
OS and application working on.  General requirements:

ATX or micro-ATX form factor
Celeron, Pentium III, or Pentium 4
4 or more PCI slots
none, or easily supported LAN chipset [we'll have to add/support 3
initially]
ATA hard disk support

Information about chipsets that work well [Intel, VIA, SiS, etc.],
whether memory types [SDRAM, DDR, RDRAM, etc.] have any impacts, and
particular brands [Asus, Gigabyte, Intel, etc.] would all be
appreciated.

TIA,
Don

---------------------------

Newsgroups: comp.os.vxworks
Subject: Loading files using target shell
Date: 7 Nov 2002 13:39:34 -0800
From: arohb@cc.usu.edu (Aroh Barjatya)
Organization: http://groups.google.com/
Message-ID: <ecdec0b9.0211071339.70b42f79@posting.google.com>

Hello All,

I have a standalone system running target shell off of one of its
serial ports (accessed using a hyperterminal). There are no other
connections whatsoever of my board with the outside world.

Is there anyway I can upload a file to my CPU board using this setup ?

I did manage to hook up a target server connection with a second
serial port on the board, and then use the {ld
1,0,"/tgtsvr/mymodule.o"} command to load a module. But like I said
the final version of the board will have no other connection to
outside world except the target shell (running through a
Hyperterminal)

Aroh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Exception calling timer_create
Date: Thu, 07 Nov 2002 23:23:31 GMT
From: robotz@robotz.rob (Paul Slocum)
Organization: Randori News - http://www.randori.com - Try our FREE Usenet Scanner!
Message-ID: <3dcabaff.236434745@news.airband.net>
References: <3dc9c374.173055781@news.airband.net> <488e459a.0211070018.1abe5954@posting.google.com>
Reply-To: robotz@robotz.rob

Well, I restarted everything today and my target server said there was
a checksum error in the core files.  So I reloaded the vxWorks image
on the target, and the problem disappeared!  Somehow I had corrupted
the flash I guess.  But I had answered your questions before I tried
this so I'll go ahead and post my answers.  John: Thanks for
responding anyway.  :o)

>1) Try connecting the debugger to the system and spawning the function
>as a task under the debugger.

I tried that but I'm new to vxWorks and PPC so I figured I'd post and
see if there was a simple solution before jumping into the
disassembly.

>2) What is at address 0x1508f0 (i.e. the address that was reported as
>the program counter at the time of the exception)?

The exception trips right when the debugger goes into create_timer.
Here's some of what the debugger showed:

0x1508f0 +0x024:       stw         r31, 0x2c(r1)
0x1508f4 +0x028:       stw         r0, 0x34(r1)
0x1508f8 +0x032:       or          r28, r3, r3
0x1508fc +0x036:       or          r30, r4, r4
0x150900 +0x040:       or          r27, r5, r5
0x150904 +0x044:       bl          intContext
0x150908 +0x048:       or.         r29, r3, r3
0x15090c +0x052:       bc          0x4, 0x2, timer_create + 0x68
0x150910 +0x056:       bl          clockLibInit
0x150914 +0x060:       li          r3, 0x1 (1)
0x150918 +0x064:       li          r4, 0x60 (96)
0x15091c +0x068:       bl          calloc
0x150920 +0x072:       or.         r31, r3, r3
0x150924 +0x076:       bc          0xc, 0x2, timer_create + 0x68
0x150928 +0x080:       bl          wdCreate
0x15092c +0x084:       cmpi        crf1, 0, r3, 0x0 (0)
0x150930 +0x088:       stw         r3, 0x0(r31)
0x150934 +0x092:       bc          0x4, 0x6, timer_create + 0x70
0x150938 +0x096:       or          r3, r31, r31
0x15093c +0x100:       bl          free
0x150940 +0x104:       li          r3, 0xffff (-1)
0x150944 +0x108:       b           timer_create + x12c
0x150948 +0x112:       stw         r29, 0x4(r31)

>3) Did you get any errors when you downloaded your .o file? In
>particular, did you see any undefined symbol errors at the time you
>downloaded the file?

The first time I tried to download the object code I did, but then I
added POSIX_TIMERS to the vxWorks image and it linked okay after that.

- -Paul

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: x86 based PC104 CPU Board
Date: Fri, 08 Nov 2002 01:01:41 GMT
From: "Mike Kim" <cskim@fdlab.co.kr>
Organization: Dacom
Message-ID: <V1Ey9.5094$S3.87026@news.bora.net>
References: <appi08$ipv$1@news01.cit.cornell.edu>

Hi~~

I'm using x86 board with PC104 I/F and one additional  serial board. (model
no. HS-4500, http://www.boser.com.tw)

If you have a Tornado and x86 BSP, I think you could boot over your pc104
type target board

using 3.5" floopy diskette. Booting using floopy is a common way in x86
board.

"Jin-Woo Lee" <jl206@cornell.edu> wrote in message
news:appi08$ipv$1@news01.cit.cornell.edu...
> Hello,
>
> If I have a BSP for x86 target, can I use it for any x86 based target?
> For example, is it possible to building a VxWorks boot image for PC104
> target board without any modification?
>
> If anyone is using PC104 board under VxWorks, can you inform me what model
> of the boards are?
>
> Thanks,
> Jinwoo
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado22/vxworks5.5
Date: Fri, 08 Nov 2002 01:24:42 GMT
From: "verizon" <webb.family@verizon.net>
Message-ID: <unEy9.17788$Wf5.12952@nwrddc04.gnilink.net>
References: <88aw9.51304$wm6.15618@nwrddc01.gnilink.net> <newscache$venu4h$2e5$1@lnews.actcom.co.il> <d1834426.0210311154.432eb23a@posting.google.com> <aq5ppc$d1t$1@news-reader10.wanadoo.fr>

Thanks, downloaded and looking it over.

"Red Fenris" <fenris@netcourrier.com> wrote in message
news:aq5ppc$d1t$1@news-reader10.wanadoo.fr...
> webber wrote:
>
> >
> >  If not WindRiver, then any personal suggestions welcomed.
> > <snip>
>
> Try this for the Web server -  That's an open source project
>
> http://www.goahead.com/webserver/webserver.htm
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Can gcc support __try and __except or alike?
Date: 7 Nov 2002 21:37:56 -0800
From: hotJacky@163.net (Bryan)
Organization: http://groups.google.com/
Message-ID: <8f77d4a.0211072137.7b19ed94@posting.google.com>

Microsft support __try to extent C language(SEH)&#12290;It is very
useful to locate some unexpected problem.It seems that gcc is not
support __try or SEH.Can anybody tell me how realize the the exception
mechanism just as the microsoft do?

Thank you!
Sincerely,
Bryan

---------------------------

Newsgroups: comp.os.vxworks
Subject: SNMP in Vxworks have security risk??
Date: Fri, 8 Nov 2002 11:54:01 +0800
From: <dingdingjiang@pek.destiny.com.cn>
Organization: Beijing Telegraph Administration
Message-ID: <aqfcl0$m21$1@info.bta.net.cn>
Reply-To: <dingdingjiang@pek.destiny.com.cn>

the SNMP in Vxworks have security risk??
HOW to advoid??

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: motorola FADS860 cpm network boot failure
Date: 8 Nov 2002 00:02:05 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211080002.2c46ee5d@posting.google.com>
References: <c1e650d9.0211062205.4ab7c7f9@posting.google.com>

Hello,

> filename:c:/tornado/target/config/ads860/vxworks

This is probably the problem here... your filename is using unix style
delimiters, but a Windows style drive name. Try using the '\'
separator in this filename.

HTH,

John...

> inet on ethernet(e):192.168.1.38:ffffff00
> inet on host:192.168.1.230
> ftploginame:user
> pwd:user
> flags:0x00
> 
> vxworksboot]@
> 
> attached TCP/IP interface to cpm0
> attaching network interface to lo0..done
> Loading...
> 
> Error Loading boot file errorno:0xd003
> 
> vxworksboot]
> 
> I started ftp server on the host specifying the file name with user Id
> and pwd before giving @ command.
> I tested the FTP server from other system .Its is working fine.
> I tried tsfs boot.It is working fine.At shell promp 
> ->ifShow
> It is showing only local loop back device lo0.(127.0.0.1)
> 
> Plz help me how to configure BSP and Network to boot over the network
> with cpm network interface..
> 
> I have been struggling for a long time ....
> 
> Thankx in advance
> 
> Murali Challa

---------------------------

Newsgroups: comp.os.vxworks
Subject: Diab compiler and StrongARM
Date: 8 Nov 2002 01:14:17 -0800
From: vardi_rajana@hotmail.com (Vardi Rajana)
Organization: http://groups.google.com/
Message-ID: <e8b83763.0211080114.607d2979@posting.google.com>

Hello,

I have downloaded the Diab compiler 5.0 from WindRiver to see it
produces faster code than the gcc compiler. Even though it's claimed
that the Diab ARM version supports StrongARM I cannot get it to
produce code that links with my ccarm-compiled code. Have anyone here
experience from Diab and StrongARM? For ccarm I use:
- -mcpu=strongarm110 -mapcs-32 to specify the platform, what would be
the equivalent in Diab?

Thanks

Vardi

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: x86 motherboards that are well-supported?
Date: Fri, 8 Nov 2002 12:40:41 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$61795h$ttc$1@lnews.actcom.co.il>
References: <b2f97e75.0211071256.9fa0581@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

Don,

it very much depends on how you define "working well", because
at a very basic level, paractically any board will work. using backward
compatibility modes, but to get really good performance you will
need to adopt the drivers to the particular chipset.

I have used an Intel motherboard with Intel 810 and 815e chipsets,
and they worked out of the box using standard FEI driver for the network,
and the ataDrv for ATA, but in order to get full 100Mbps Ethernet throughput
the FEI driver had to be optimized, and the ataDrv driver had to be improved
to support PCI Bus Master feature of the chipset to releeive the CPU of the
data transfer burden, and to support UltraDMA transfer modes.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

"Don" <danderson@kns.com> wrote in message
news:b2f97e75.0211071256.9fa0581@posting.google.com...
> We are looking at running VxWorks 5.4 on a "standard" PC. I am looking
> for suggestions on ones that people have had few problems getting the
> OS and application working on.  General requirements:
>
> ATX or micro-ATX form factor
> Celeron, Pentium III, or Pentium 4
> 4 or more PCI slots
> none, or easily supported LAN chipset [we'll have to add/support 3
> initially]
> ATA hard disk support
>
> Information about chipsets that work well [Intel, VIA, SiS, etc.],
> whether memory types [SDRAM, DDR, RDRAM, etc.] have any impacts, and
> particular brands [Asus, Gigabyte, Intel, etc.] would all be
> appreciated.
>
> TIA,
> Don

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sat Nov  9 04:03:14 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sat Nov  9 04:03:15 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sat Nov  9 04:03:12 PST 2002

        Subject: Re: Aaarrrgghh.... Ping never frees the mbuf from my driver.   Any netcluster gurus?
        Subject: Re: Simple RIP/router question
        Subject: Re: timer gotchas..
        Subject: Re: Simple RIP/router question
        Subject: Re: How to check dosFs/TFFS data integrity before attempting a mount?
        Subject: Re: tftp download file too big problem
        Subject: Re: Routines from ISR that use tExcTask

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Aaarrrgghh.... Ping never frees the mbuf from my driver.   Any netcluster gurus?
Date: 8 Nov 2002 05:15:03 -0800
From: doug_dyer@yahoo.com (Doug Dyer)
Organization: http://groups.google.com/
Message-ID: <9b386c37.0211080515.667ab594@posting.google.com>
References: <9b386c37.0211070505.5efb0ac5@posting.google.com>

Well thought I would answer my own question for the sake of anyone
searching on this:

MBufs of ICMP and ARP packets (and probably others) are not freed back
to your pool after they reach their destination.  Its like they are
held in a fifo of about 50 deep or so.

Since my driver had a total of 40 mbufs in my pool, ICMP ping packets
after 40 pings killed my driver drying up all of the mbufs. 
Increasing my mbufs by 100 my pings now run forever (as opposed to
40).

Interesting problem.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Simple RIP/router question
Date: Fri, 8 Nov 2002 17:12:43 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$mmj95h$jgd$1@lnews.actcom.co.il>
References: <3dcb7084.247037320@News.CIS.DFN.DE>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

Actually Ignacio, your options are not very bad, but there are more options
too.

Your option #1 is a must, I think, even if you use option #2, the default
router
address provides the "route of last resort".

Regarding #2, every end-node can run RIP, but as long as it has only one
interface, it will not advertise anything, just listen to the router's
advertisements,
and update its routing table accordingly.

A third option you did not consider, may only work for a fairly limitted
size
network (i.e. no access ro the Internet) - you can have the netmask on the
VxWorks target deliberately extended with respect to router netmask, and the
router can provide Proxy ARP for the hosts which are in fact on the other
side of the
router, making the VxWOrks beleive they are local.

For example, on the VxWorks targets, you set the address as

    192.168.200.1 to 192.168.200.125 with netmask 0xffffff00

On the router you set the interface which is on the same LAN as the VxWeorks
target as

    192.168.200.126 netmask 0xffffff80 (or 255.255.255.128)

and on the other interface of the router the address would be
192.168.200.254, the host across the router will be 192.168.200.200 and
netmask on both 255.255.255.128 and the host shall have default router
192.168.200.00

Effectively, you split the Class C network in two, have the VxWorks targets
deliberately
unaware of the split, and having the router do proxy-arp and answer to ARP
requests on behalf of the host on the other side of the router.

This 3rd option can have you get away without modifying ANYTHING on the
targets.

- -- Adios !
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

"Ignacio Gonzalez" <igtorque@yahoo.es> wrote in message
news:3dcb7084.247037320@News.CIS.DFN.DE...
> I have a net of some 60 VxWorks targets that are to be connected to a
> router (non-VxWorks.) At the other side of the router, there lies a
> host (non-VxWorks) that will request information from some of the
> VxWorks targets.
>
> Before introducing the router-and-host, the network configuration in
> the VxWorks targets has been very simple: 1 IP & mask for everyone,
> making a unique subnet (say it is 200.1.10.0/0xFFFFFF00), and that's
> all.
>
> But, what should I do in the VxWorks to connect my subnet to the
> router? Reading the VxWorks books, I think I have several options:
>
> 1) Use mRouteAdd ("0.0.0.0.", "routerAddr", 0, 0, 0) in every VxWorks
> target to add a default entry to the routing table (being "routeAddr"
> = "200.1.10.1", for instance.)
>
> 2) Rely on dynamic routes, via RIP protocol. Now, I have a question:
> do I have to set INCLUDE_RIP in the targets, or this option is only
> for the routers? Perhaps I am confounded with the expression "RIP
> server". In order for my targets to be able to discover the
> router/gateway, do I have to set them as RIP servers with INCLUDE_RIP,
> or the "default" network configuration without INCLUDE_RIP will be
> enough?
>
> I think option 1 is simple, but forces me to include another
> configuration parameter ("routerAddr") in my targets (which I'd like
> to avoid.) On the other hand, if RIP can do the trick (without
> INCLUDE_RIP?) I can avoid that parameter.
>
> What do you think?
>
> --
> Ignacio G.T.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: timer gotchas..
Date: Fri, 8 Nov 2002 17:14:58 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$eqj95h$mgd$1@lnews.actcom.co.il>
References: <1036752207.335238@newsreader1.wirehub.nl>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Renee Teunissen"
<if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you
agree.with.these.terms@mail.zevenaar.org> wrote in message
news:1036752207.335238@newsreader1.wirehub.nl...
[snip]
>
> Any comments, thoughts ?

Dont mind repeating this -

    do not ever use SUSPEND for anything other then debugging.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Simple RIP/router question
Date: Fri, 08 Nov 2002 16:25:42 GMT
From: igtorque@yahoo.es (Ignacio Gonzalez)
Message-ID: <3dcbe476.276719371@News.CIS.DFN.DE>
References: <3dcb7084.247037320@News.CIS.DFN.DE> <newscache$mmj95h$jgd$1@lnews.actcom.co.il>
Reply-To: igtorque@yahoo.es

Thanks, Leonid. I'll try your suggestions.

,,auf Wiedersehen ! "

- --
Ignacio G.T.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How to check dosFs/TFFS data integrity before attempting a mount?
Date: Fri, 8 Nov 2002 19:21:05 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$sqp95h$3pd$1@lnews.actcom.co.il>
References: <apsdjp$1h2$1@overload.lbl.gov> <newscache$ox1w4h$la8$1@lnews.actcom.co.il> <a8c9b703.0211080807.1ec0b9b4@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"John Sambrook" <john_sambrook@yahoo.com> wrote in message
news:a8c9b703.0211080807.1ec0b9b4@posting.google.com...
> Thank you, Leonid.
>
> Because this application is response-time-sensitive, I'd like to
> be able to peek at a few bytes in the flash to determine if the
> flash has been formatted.  I understand that TFFS puts an erase
> unit header at the start of every flash block.
>
> Is this structure defined in a public place, or is it in the
> non-exposed part of the TFFS that's shipped with VxWorks?
>
> I'd like to be able to make a quick check for a magic number in
> order to decide whether the device has ever been formatted by
> TFFS.  I don't need the check to be complete, just sufficient to
> rule out a few other possible cases.
>
John,

the TFFS data structure is proprietary and somewhat complex.
The "logical data" is what you would see when accessing the
TFFS above the device driver (or what the file system sees).
This "logical data" is cattered all around the Flash bank,
and TFFS uses special overhead regions in each erase block
to keep track of where each logical block ios located physically.
Still, some erase blocks may appear to be erased (i.e. all 0xFF)
although the device is indeed formatted - these are the "spare blocks"
that are used to move data around.

I could do some more research for you, but the amount of work
needed depnds on your need to differentiate states:
Do you need only to determine if the Flash was formatted with TFFS or
nor formatted at all (i.e. blank form factory), or do you need also to be
able
to detect some other state, e.g. corrupt, some QA test residual data, etc.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: tftp download file too big problem
Date: Fri, 8 Nov 2002 17:45:32 -0000
From: "Dimitrios Siganos" <nospam_dimitrios.siganos@newport-networks.com>
Organization: Newport Networks Ltd.
Message-ID: <1036777532.663525@azores.network-i.net>
References: <aqbnpl$2ri$1@news.storm.ca>

TFTP is a very crude protocol and cannot know the size of the file it is
downloading.
When a transfer is started, the TFTP client starts downloading until it sees
a "special" packet that signals the end of transfer.

If you want to know the size a transfer will be use FTP.

If you absolutely must use TFTP you could probably write the length of the
file in the first few bytes of each file and then hack the TFTP client to
read that and act accordingly.

Dimitris

"Harjinder Chayra" <harjinder.chayra@imedia.com> wrote in message
news:aqbnpl$2ri$1@news.storm.ca...
> When using tftp (tftpGet) to download a file, is there a mechanism where
we
> can be informed that the file is bigger than the space allocated for it?,
> otherwise memory will get corrupted.
>
> Thanks
>
> Harjinder
>
>
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Routines from ISR that use tExcTask
Date: Fri, 8 Nov 2002 20:21:29 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$8ds95h$atd$1@lnews.actcom.co.il>
References: <3DCBE38C.7599AB28@infineon.no.spam.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Stefan Tauche" <stefan.tauche@infineon.no.spam.com> wrote in message
news:3DCBE38C.7599AB28@infineon.no.spam.com...
[snip]
>
> Just to be informed, does anybody have a list of routines that use
> excJobAdd()
> when called from an ISR ?
>

Here is a rather simnple method:

    cd $(WIND_BASE)/target/lib
    nm386 -o libPENTIUMgnuvx.a | grep excJobAdd

will generate the list of MODULES that have external reference to
excJobAdd().
This method has one shortcoming - some years back, at about when
MicroWorks(tm)
was released, excLib and tExcTask where made OPTIONAL, so some of the
libraries
referncing excJobAdd() where modified to refer the function by way of a
global hook
variable (this is where my recollecion stops at the moment - can't recall
the name
of that variable), so you will be able to guess the variable name by listing
the
symbol names of excLib.o

Still, many modules call the excJobAdd function directly so excLib and
tExcTask
are not really optional for any practical purpose.

- -- HTH
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sun Nov 10 04:03:14 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sun Nov 10 04:03:16 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sun Nov 10 04:03:12 PST 2002

        Subject: wrapping printf()
        Subject: Re: Message Queues from ISRs
        Subject: Re: taskSuspend/taskResume counted?
        Subject: Re: PCI address space assignment
        Subject: Re: Is there a limit on maxLen in read when using NFS?

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: wrapping printf()
Date: Sat, 9 Nov 2002 20:38:56 +0800
From: "Yung" <general_miller@yahoo.com>
Organization: IMS Netvigator
Message-ID: <aqivl2$8mm3@imsp212.netvigator.com>

Hi all,

Our vxWorks system has a number of application tasks which are handled by
different engineers. In order to make the individuals' debug messages more
organized as they appear on the console, I am thinking of wrapping up
printf() with another function such that different groups of debug messages
can be conditionally supressed or displayed as required. In order to do
this, i need to get access to the internal printf() too. Do you think there
is a way to do this? Or is there any other means besides that that can help
in the situation?
Thanks a lot!

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Message Queues from ISRs
Date: 9 Nov 2002 10:47:22 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211091047.96676ac@posting.google.com>
References: <0f742a96c8a1f10b80dbe198124e4e89.105305@mygate.mailgate.org> <Bl2z9.2857$hK4.223037@bgtnsc05-news.ops.worldnet.att.net>

Hello,
"franco spadafora" <francospadafora@worldnet.att.net> wrote in message news:<Bl2z9.2857$hK4.223037@bgtnsc05-news.ops.worldnet.att.net>...
> I've accomplished the same by using the vxWorks rngLib and a semafore.  Or
> for speed sake, implement your own long-word based circular ring queue.  Off
> the top of my head I couldn't tell you why this doesn't work.  But look
> into:
> 1. is 1 byte message allowed in msg queue?

Yes; a zero byte message is allowed too...

> 2. is message queue  1 message deep allowed?

Yes.

> you can test both without using an isr.
> 3. is msgQSend callable from an ISR? If it is, it would only be so using
> NO_WAIT.

Yes; this is described in the list of functions that may be called
from an ISR (see your VxWorks Programmer's Guide).

HTH,

John...

> "Steve Comfort" <sdc@ccii.co.za> wrote in message
> news:0f742a96c8a1f10b80dbe198124e4e89.105305@mygate.mailgate.org...
> > I'm trying to decouple an ISR from the rest of a driver by posting a
> > message to a task, which in turn is supposed to call a higher layer
> > receive function in the driver. Here's what the send routine looks like:
> >
> >
> >          sent = msgQSend(ccStmRxMsgQId,
> > MESSAGE,  /* (char *)&data_msg, */
> > CCSTM_MAX_RX_MSG_SIZE,
> > NO_WAIT,
> >          MSG_PRI_NORMAL);
> > if (ERROR != sent)
> > {
> >            DRV_MPT (DRV_MPT_FLOW,"Msg Q'd on Q %p\n",
> >             ccStmRxMsgQId,0,0,0,0,0);
> >         }
> >         else
> >         {
> >    switch (errno)
> >              ...
> >
> > Here CCSTM_MAX_RX_MSG_SIZE = 1, and MESSAGE is just a single character.
> >
> > The receive routine is
> >
> > bytes_received = msgQReceive(ccStmRxMsgQId,
> >                              rx_buffer,
> >                              CCSTM_MAX_RX_MSG_SIZE,
> >                              NO_WAIT);
> > if ((ERROR != bytes_received) &&
> >     (0 > bytes_received))
> >
> >
> >
> > Although the ISR claims it has sent the message, this is untrue (maybe
> > with NO_WAIT this is correct??).
> >
> > When I do a msgQShow here's what I get :
> >
> > Message Queue Id    : 0x7efef94
> > Task Queueing       : FIFO
> > Message Byte Len    : 1
> > Messages Max        : 1
> > Messages Queued     : 0
> > Receivers Blocked   : 0
> > Send Timeouts       : 0
> > Receive Timeouts    : 870
> >
> > The question is, what am I doing wrong?
> >
> >
> > --
> > Posted via Mailgate.ORG Server - http://www.Mailgate.ORG

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: taskSuspend/taskResume counted?
Date: 9 Nov 2002 10:48:53 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211091048.225ccb2d@posting.google.com>
References: <bob-0CD481.12580002112002@news.apple.com> <newscache$strz4h$0hj$1@lnews.actcom.co.il> <Dl2z9.2858$hK4.224929@bgtnsc05-news.ops.worldnet.att.net>

Hello,

"franco spadafora" <francospadafora@worldnet.att.net> wrote in message news:<Dl2z9.2858$hK4.224929@bgtnsc05-news.ops.worldnet.att.net>...
> one minor correction... if a semafore is created as EMPTY, semGive() will
> make it FULL....  or am i wrong on that one?

If it is a binary semaphore then this is correct; for other types the
behaviour will be different. Read the section in the programmer's
guide about semaphores for more information.

HTH,

John...
 
> "Leonid Rosenboim" <My_1st_name@Consultant.Com> wrote in message
> news:newscache$strz4h$0hj$1@lnews.actcom.co.il...
> > "Bob Bradley" <bob@chaoticsoftware.com> wrote in message
> > news:bob-0CD481.12580002112002@news.apple.com...
> > > Do the taskSuspend and taskResume routines internally keep track of
> > > whether they have been called such that a taskResume that comes before a
> > > taskSuspend will cause the taskSuspend to be nullified? The
> > > documentation indicates task suspension is additive, but it only seems
> > > to state this in terms of other states such as pended or delayed.
> > >
> > No, a taskResume() call on a task which is not suspended has no effect,
> > much like a semGive() on a semaphore which has not been taken yet.
> > Suspetion is a state of a task, which is additive to otehr task
>  attrubutes,
> > but is only a binary memoryless state by itself.
> >
> >
> > > For some debugging code, I would like to have a task send to a message
> > > queue with the task id then taskSuspend itself. The receipient of the
> > > message would then resume the task. This opens up a window for a race
> > > condition if the taskResume happens before the taskSuspend unless
> > > taskSuspend/taskResume keep track of whether taskResume/taskSuspend has
> > > already been called.
> >
> > Well, using task suspention for anything other then debugging is
> > discouraged.
> > In your case, I could suggest the task uses preemption locking to avoid
>  any
> > race condition, and since this is only for debugging, the generally
> > dangerous
> > preemption locking can be excused:
> >
> >   taskLock();
> >  msgQSend( qid, ... );
> >  taskSuspend(0);
> >  taskUnlock();
> >
> > Please note that when the task suspends itself, preemption is re-enabled,
> > until this task gets to RUN again, then it preemtpion lock will be
> > momentarily
> > restored only to be lifted a few instructions thereafter.
> >
> > >
> > > I'm wondering whether I need to use another mechanism, such as creating
> > > a temporary semaphore to send to the server task (extra overhead and
> > > memory usage to create and delete a semaphore for each operation).
> > >
> > > The pthreads code as part of the VxWorks FAQ uses this technique in
> > > pthread_cond_wait and I wasn't sure if it suffers from this race
> > > condition or if taskSuspend/taskResume allow it to work properly.
> >
> > If I understand this correctly, the FAQ implementation for conditional
> > variable uses taskSuspend() ? If that is indeed the case, I would
>  recommend
> > against using this particular implementation.
> >
> > --
> > -----------------------------------------------------------------------
> >    Leonid Rosenboim                Visit:
> > http://gamla.org.il/english/index.htm
> >         Consultant                Email: my first name at consultant dot
>  com
> >
> >
> >
> >

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: PCI address space assignment
Date: 9 Nov 2002 10:54:07 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211091054.4ae712dc@posting.google.com>
References: <aqhrsm$6am$1@news.asu.edu>

Hello,

You need to configure the PCI card, and allocate it some address
space. VxWorks doesn't do this by default (though there is a PCI
auto-config feature that you can enable). Check the manual entries for
pciConfigLib and also the code in your BSP that sets up your ethernet
device (assuming that is a PCI card as well).

You can try all the config routines from the shell by the way, so you
don't need to write code and rebuild all the time. You should reboot
though if you configure the card and it doesn't work before trying
again.

HTH,

John...

"Sandeep P" <psandeep77@hotmail.com> wrote in message news:<aqhrsm$6am$1@news.asu.edu>...
> Hello All,
>              I have a problem that requires to be fixed asap.
> 
> I have plugged a soundblaster soundcard to my IXP1200EB pci slot. After
> booting it up, I ran the command "pciAddrShow" to see the memory space
> assigned to my new card. The following is the output: -
> 
> -> pciAddrShow
> bus 0  dev 0  error 0  id 80861200
>   size 00100000  addr 02000000
>   size 00000080  addr 00000001
>   size 02000000  addr 00000000
> bus 0  dev 6  error 0  id 12745880    <-----------
>   size 00000040  addr 00000081
> bus 0  dev 7  error 0  id 80861229
>   size 00001000  addr 02200000
>   size 00000040  addr 000000C1
>   size 00100000  addr 02100000
> value = 31 = 0x1f
> ->
> 
> The arrow shows the entry for the sound card. All address blocks whose
> starting addresses have '1' in the LSB are considered to lie in the I/O
> space. From the values we see that it is assigning the starting address 0x81
> to it with a size of 0x40 bytes. This forms part of the I/O space. But in
> reality, there is even a memory space on the card, but for some reason, it
> is not showing up. The manual indicates this by saying that the joystick
> values are stored in location 0x201. So there must be a memory space from
> where I should be able to read the joystick values. Why isnt Vxworks showing
> that part of the address space?
> Is there a solution for this? If vxworks is itself unable to recognize this
> address space on the sound card, will the addition of any new code be of any
> use???
> 
> Regards,
> Sandeep.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is there a limit on maxLen in read when using NFS?
Date: Sun, 10 Nov 2002 14:00:23 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$520d5h$6jm$1@lnews.actcom.co.il>
References: <12f96c64.0211100239.76cbe933@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Eyal Rozenblat" <eyal.rozenblat@seabridgenetworks.com> wrote in message
news:12f96c64.0211100239.76cbe933@posting.google.com...
> All,
>   I am using NFS from my system to read/write files residing on a UNIX
> machine. I fail to read a file I created myself, when attempting to
> read it all, 5MB, at one call. The read returns -1.
> Prior to this read the file looks good, and contains the content I
> have placed inside.
> Is there any limit on applying a read to a file via NFS ?
> Thanks,
> Eyal

In principle, as long as you got enoygh memory, any size of buffer in read()
should
succeed, even if th efile is smaller then th ebuffer, read() should return
the number
of bytes it has actuall retreived before EOF. This usually means repeating
an
operation (such as NFS read op) as many times as needed to satisfy the
request.

With the WR NFS client, there is however a small cache that belongs to the
NFS client, which may be the cause of this problem.

Here are a few ideas on how to check what is going on:

1. What is the value of the "int" global variable ?
    nfsMaxMsgLen
2. If you begin witn a reasonably small buffer, and increase it
progressively (assuming a 5 Meg file size), what ithe buffer size where
read() actually fails ?
3. Is there any correlation between the answers in #1 and #2 ?
4. What happens if you set nfsMaxMsgLen=0 early in your BSP code (be sure to
do this before the cann to nfsDrvInit() ) ?

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sun Nov 10 08:59:49 2002
From: Mike McCullough <mike@mccengineering.com>
Date: Sun Nov 10 08:59:51 PST 2002
Subject: Re: wrapping printf() 

I would recommend AGAINST mucking about with the printf code. If you want 
to select which tasks can output to where then use the ioTaskStdSet() 
routine to do so. Much engineering time has been spent re-writing the 
multiple levels of printf when simply using a combination of 
ioTaskStdSet(), ioGlobalStdSet(), and logFdSet() would solve the problem.

Now if only the Wind River engineers would learn to use them 
appropriately... :)

Newsgroups: comp.os.vxworks
Subject:
Date: Sat, 9 Nov 2002 20:38:56 +0800
From: "Yung" <general_miller@yahoo.com>
Organization: IMS Netvigator
Message-ID: <aqivl2$8mm3@imsp212.netvigator.com>
Hi all,
Our vxWorks system has a number of application tasks which are handled by
different engineers. In order to make the individuals' debug messages more
organized as they appear on the console, I am thinking of wrapping up
printf() with another function such that different groups of debug messages
can be conditionally supressed or displayed as required. In order to do
this, i need to get access to the internal printf() too. Do you think there
is a way to do this? Or is there any other means besides that that can help
in the situation?
Thanks a lot!

**********************************************************
Mike McCullough                    MCC Engineering
President and CEO                  9 Cheshire Court
                                    Londonderry, NH 03053

mike@mccengineering.com            Tel:  603-537-9593
                                    Fax:  603-434-9890
www.mccengineering.com            Cell: 603-247-1219

**********************************************************
        24x7 VxWorks Support  Custom Support Programs
          VxWorks Training   Embedded Consulting Services
                     A WindLink Partner
**********************************************************

From vxwexplo-errs@csg.lbl.gov  Mon Nov 11 08:19:33 2002
From: "KENT DURHAM" <DURHAM@aaicorp.com>
Date: Mon Nov 11 08:19:34 PST 2002
Subject: Tornado 2.0 (Windows) automatically saving files without

One of the users on our system has come to me with this issue he is
having with Tornado 2.0 for Windows using the built-in editor, and I
have been able to duplicate it on my machine: 

This is the following scenario:
1. Open up fooA.c   .  Edit the file.  Do not save  (Asterisk denoting
changed file shows up in the title bar.)
2. Open up fooB.c .  (Notice asterisk in fooA.c window title bar
disappears immediately.)  Play around with this file.  Close this file.
3. Notices fooA.c no longer has an asterisk.  Goes to close fooA.c. 
fooA.c does not prompt to save changes.  
4. Re-opens fooA.c  .  Edits from step 1 have been saved, although user
never asked for this to happen.

I didn't see any Tornado Options that seemed related to this.  Toggled
the Save Before Running Tools/Build checkbox, but the behavior is the
same with either setting.  

Has anyone noticed this behavior before?  Is there another setting I
can change to resolve this, or is it just a bug?

From vxwexplo-errs@csg.lbl.gov  Tue Nov 12 08:23:13 2002
From: "Deenadayalan P - CTD, Chennai." <pdeena@ctd.hcltech.com>
Date: Tue Nov 12 08:23:14 PST 2002
Subject: Attaching ISR to the interrupt vector.

Hi all,

I am trying to write an interrupt controller driver for MPC8240 without any
OS support. I wanted to connect my interrupt handler to the external
interrupt. Something like "excIntConnect" of vxworks. I am using GNU Toolkit
for Compiling. 
Here is the code fragment I am using.

	.org 0x0500  /*External exception vector for MPC8240*/   
	bl IntrHandler /*This is a C routine, with no arguments*/
	rfi	

But this doesn't work. Is there anything else, that I should to do?
Thanks in advance.

-Deena

-with warm regards,
Deena.

Deena Dayalan
HCL Technologies Ltd,
184-188,190,192-196,
N.S.K Salai (Arcot Road),
Vadapalani,
Chennai - 600 026.
 INDIA
Phone
   Office: 91-44-3728366 ( Ext - 1311 )
   Residence: 91-44-8444705
E-mail: pdeena@ctd.hcltech.com

This document is intended for transmission to the named recipient only.  If
you are not that person, you should note that legal rights reside in this
document and you are not authorized to access, read, disclose, copy, use or
otherwise deal with it and any such actions are prohibited and may be
unlawful. The views expressed in this document are not necessarily those of
HCL Technologies Ltd. Notice is hereby given that no representation,
contract or other binding obligation shall be created by this e-mail, which
must be interpreted accordingly. Any representations, contractual rights or
obligations shall be separately communicated in writing and signed in the
original by a duly authorized officer of the relevant company.

From vxwexplo-errs@csg.lbl.gov  Wed Nov 13 04:03:19 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Wed Nov 13 04:03:21 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Wed Nov 13 04:03:16 PST 2002

        Subject: Re: 1553 bus and Vxworks drivers
        Subject: Re: Telnet problem after building vxWorks.st_rom
        Subject: Re: 1553 bus and Vxworks drivers
        Subject: Power-of-2 algorithm in SDRAM address bus diagnostics
        Subject: Re: Telnet problem after building vxWorks.st_rom
        Subject: Re: C++ in vxWorks image
        Subject: etherAddrResolve(...)" function and "Default Gateway"
        Subject: Re: Telnet problem after building vxWorks.st_rom
        Subject: Re: Telnet problem after building vxWorks.st_rom
        Subject: Re: Aaarrrgghh.... Ping never frees the mbuf from my driver.   Any 
        Subject: IP not receive my packet...
        Subject: Re: C++ in vxWorks image
        Subject: Re: Tornado 2.0 (Windows) automatically saving files without
        Subject: Text I/O from multiple protection domains
        Subject: Re: Power-of-2 algorithm in SDRAM address bus diagnostics
        Subject: Re: C++ in vxWorks image
        Subject: Re: C++ in vxWorks image
        Subject: Re: accessing game port on pci sound card
        Subject: Re: Why the address down after linker?
        Subject: Re: Manipulate debug info in ELF file
        Subject: Re: Text I/O from multiple protection domains
        Subject: Re: how to set up WDB connection to 3C905C-TX?
        Subject: Re: Attaching ISR to the interrupt vector.
        Subject: Re: accessing game port on pci sound card
        Subject: CyrixMediaGX and Tornado 2.2/VxWorks 5.5 Pentium BSP
        Subject: Re: accessing game port on pci sound card

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: 1553 bus and Vxworks drivers
Date: Mon, 11 Nov 2002 07:01:35 -0500
From: Joe Durusau <joseph.a.durusau@lmco.com>
Organization: Lockheed Martin Corporation
Message-ID: <3DCF9C1F.B19496FA@lmco.com>
References: <hfyz9.20$5x.12712@newsfep2-win.server.ntli.net>

Mike Barton wrote:
> 
> Does anyone know of any 1553bus interface cards that have good vxworks
> drivers?
> 
> Mike

You can find a list of modules in various form factors
at www.vita.com.  (assuming you want something in the 
VME/VXI/Ipak line).  All of them I have seen use
the DDC ICs to do the work, so drivers should not be
a problem.

Speaking only for myself,

Joe Durusau

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Telnet problem after building vxWorks.st_rom
Date: Mon, 11 Nov 2002 07:04:44 -0500
From: Joe Durusau <joseph.a.durusau@lmco.com>
Organization: Lockheed Martin Corporation
Message-ID: <3DCF9CDC.264372DF@lmco.com>
References: <12fb1996.0211080646.319d42ea@posting.google.com>

dpf wrote:
> 
> VxWorks version 5.4.2
> Kernel: WIND Version 2.5
> Motorola PPC 2604
> BSP version 1.2
> 
> I have successfully built a "vxWorks.st_rom" image and our application
> is working fine.  However, when I attempt to telnet to the system, I
> immediately get the following error message:
> 
> Trying xxx.xxx.xxx.xxx...
> Connected to yyy.
> Escape character is '^]'.
> 
> VxWorks login:
> 
> Login timed out after 60 seconds!
> 
> Connection closed by foreign host.
> 
> Any ideas?
> 
> Thanks

Did you try to log in to the vxWorks host?

There is a default login ID defined somewhere; I never
used it, so I don't know what it is.  

Speaking only for myself,

Joe Durusau

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: 1553 bus and Vxworks drivers
Date: Mon, 11 Nov 2002 07:16:07 -0800
From: "Melvin Gardipee <mbgardipee@" <"NO_SPAM_raytheon>.com">
Organization: Raytheon Company
Message-ID: <XQPz9.24$Z74.374@dfw-service2.ext.raytheon.com>
References: <hfyz9.20$5x.12712@newsfep2-win.server.ntli.net>

    A lot of test equipment that we have designed in house uses
SBS-Avionics VME and PMC1-1 products with VxWorks.  The PMC line
now has two families. The VME and PMC1-1 are TI DSP based with
an FPGA, the newer PMC2-X is all FPGA based.
    The older cards firmware is more mature and works well.  I had
some problems with the PMC2-1, but that was a year ago and the card
was being used unconventionally.
    As with all PCI based systems used with VxWorks, your mileage may
vary. You will probably have to write your own PCI configuration code
if your BSP doesn't have auto configuration. I've covered this issue
in the past in this newsgroup, check the archives on Google.
    Product support is excellent and their quick to resolve issues
if you can give them a good example of the problem.
	
Speaking only for myself,
Melvin Gardipee

Mike Barton wrote:
> 
> Does anyone know of any 1553bus interface cards that have good vxworks
> drivers?
> 
> Mike

---------------------------

Newsgroups: comp.os.vxworks,comp.arch.embedded
Subject: Power-of-2 algorithm in SDRAM address bus diagnostics
Date: 11 Nov 2002 11:51:46 -0800
From: ryeung@earthlink.net (Raymond Yeung)
Organization: http://groups.google.com/
Message-ID: <d83bb8e3.0211111151.2d2eeab3@posting.google.com>

It seems to me, due to SDRAM's address lines multiplexing nature, power-of-2
algorithm would result in more work than necessary in order to provide 
same fault coverage over the same address space.  

I guess I can tolerate more work, as long as the coverage is just as complete
(as in non-multiplexing case).  What's your thought in using such algorithm
in SDRAM, in terms of efficiency and adequacy?  What algorithm(s) do people 
use instead?

Raymond

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Telnet problem after building vxWorks.st_rom
Date: 11 Nov 2002 12:06:01 -0800
From: jamesmh@excite.com (James)
Organization: http://groups.google.com/
Message-ID: <5c5c831e.0211111206.69b36ad2@posting.google.com>
References: <12fb1996.0211080646.319d42ea@posting.google.com>

david.floyd-1@ksc.nasa.gov (dpf) wrote in message news:<12fb1996.0211080646.319d42ea@posting.google.com>...
> VxWorks version 5.4.2
> Kernel: WIND Version 2.5
> Motorola PPC 2604
> BSP version 1.2
> 
> I have successfully built a "vxWorks.st_rom" image and our application
> is working fine.  However, when I attempt to telnet to the system, I
> immediately get the following error message:
> 
> Trying xxx.xxx.xxx.xxx...
> Connected to yyy.
> Escape character is '^]'.
> 
> VxWorks login: 
> 
> Login timed out after 60 seconds!
> 
> Connection closed by foreign host.
> 

Try using it with the login id/password disabled, just straight
automatic login.
I have used it this way. I know there was a bug with the password
encryption program in v 5.3, not sure about the current version.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: C++ in vxWorks image
Date: 11 Nov 2002 21:56:32 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211112156.2ae558cb@posting.google.com>
References: <3DCA8595.5060706@minn.teradyne.com> <488e459a.0211072358.effa57a@posting.google.com> <3DD03E0A.2020505@minn.teradyne.com>

Hello,

Just on WindSurf searching for something and I cam across this article
that might be helpful for what you're doing with the ROM images:

http://www.windriver.com/cgi-bin/windsurf/techtips/public/viewSum.cgi?1899

HTH,

John...

Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DD03E0A.2020505@minn.teradyne.com>...
> Thanks John,
> 
> Actual I was able to get it all to build ok with the archive files, but
> will certainly give the .out build a whirl.
> 
> Any idea how to put a 4 Meg vxWorks image into a ROM, that is, a ROMed
> version of our applcation that skips the download step.  I see several
> targets, e.g., vxWorks.st_rom, but none work directly with our setup.
> 
> We've got a PPC with 1M of head room from the boot vector.  We have 15M below
> this address space that we can access, but the boot process and config MACROS
> seem to want a contiguous memory.  Do I have to write my own code to facilite
> this, or is there something I'm not seeing?  I suppose we could use some sort
> of flash file system (TFFS for example), but that seems a little awkward.
> 
> Any info would certainly help!  And thanks again. Hope I can return the favor someday!
> 
> -Keith
> 
> 
> 
> 
> John wrote:
> 
> > Hello,
> > 
> > No, LIB_EXTRA is not the correct thing to use, nor is a .a format
> > file. Instead, use the ADDED_MODULES macro to add your program.out
> > file directly to the image (if you have more than one, add them all to
> > this macro).
> > 
> > The problem with the .a file format is that the linker will only
> > extract the .o files from it that it believes are needed by the
> > program, based on symbolic dependencies between them.
> > 
> > HTH,
> > 
> > John...
> > 
> > Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DCA8595.5060706@minn.teradyne.com>...
> > 
> >>We've used C++ in our e.g., progam.out downloads successfully for some time.
> >>
> >>however, when we add our now archived (e.g., program.a) files to LIB_EXTRA in the
> >>makefile for our 'make vxWorks' build name mangling or some such appears to
> >>be getting in the way.
> >>
> >>Anybody know if LIB_EXTRA is the appropriate place to add our acrhives?
> >>If so, anything that needs to be done to allow for C++ in the vxWorks image?
> >>
> >>Regards,
> >>-ko
> >>

---------------------------

Newsgroups: comp.os.vxworks
Subject: etherAddrResolve(...)" function and "Default Gateway"
Date: 11 Nov 2002 23:30:25 -0800
From: oded.weissman@motorola.com (Oded Weissman)
Organization: http://groups.google.com/
Message-ID: <acaaa989.0211112330.1f48d66a@posting.google.com>

Does "etherAddrResolve(...)" function
    need to return the mac address of the "Default Gateway"
    if the IP was asked to be resolved is out of the local subnet ???

Oded Weissman
Motorola Communication Israel

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Telnet problem after building vxWorks.st_rom
Date: Tue, 12 Nov 2002 08:22:33 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <aqqdo8$csq$1@venus.btinternet.com>
References: <12fb1996.0211080646.319d42ea@posting.google.com> <5c5c831e.0211111206.69b36ad2@posting.google.com>

James wrote:
> I know there was a bug with the password encryption program in v 5.3,
Beware that that 'encryption' function is very weak, I think I could
reverse it by hand....
	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Telnet problem after building vxWorks.st_rom
Date: Tue, 12 Nov 2002 12:50:46 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <aqqtf5$60s$1@venus.btinternet.com>
References: <12fb1996.0211080646.319d42ea@posting.google.com> <5c5c831e.0211111206.69b36ad2@posting.google.com> <aqqdo8$csq$1@venus.btinternet.com> <aqqpop$6d1$1@snoopy.bndlg.de>

>>Beware that that 'encryption' function is very weak, I think I could
>>reverse it by hand....
> 
> AFAIK not reverse, as it looses information, but you might find another
> matching pattern ;-)

Probably a shorter one as well :-)

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Aaarrrgghh.... Ping never frees the mbuf from my driver.   Any 
 netcluster gurus?
Date: Tue, 12 Nov 2002 14:29:34 +0100
From: Emmanuel Herbreteau <eherbreteau@sepro-robotique.com>
Organization: SEPRO Robotique (BEP)
Message-ID: <3DD1023E.1767AD5@sepro-robotique.com>
References: <9b386c37.0211070505.5efb0ac5@posting.google.com> <9b386c37.0211080515.667ab594@posting.google.com>

Hi Doug,

Network buffers are freed after a fixed delay.
This is why you need to increase the number of mbuf.
You can also try to slow down the ping rate.

This is a common problem with the network stack.
You will get the same trouble if you open and close
TCP socket very quickly (ie : FTP transfert of small
files).

Regards
Emmanuel.

Doug Dyer wrote:
> Since my driver had a total of 40 mbufs in my pool, ICMP ping packets
> after 40 pings killed my driver drying up all of the mbufs.
> Increasing my mbufs by 100 my pings now run forever

---------------------------

Newsgroups: comp.os.vxworks
Subject: IP not receive my packet...
Date: 11 Nov 2002 16:51:02 -0800
From: roswel_ajf@hotmail.com (roswell)
Organization: http://groups.google.com/
Message-ID: <6dcae13d.0211111651.7c9c4c5a@posting.google.com>

Hi.

 I have a virutal ethernet interface. I wrote the driver for it. And I
am able to ping from target shell out into the virtaul interface. So,
TX is working.

 But, for RX, vif_PacketDataGet (my endEtherPacketDataGet routine ),
is getting called. But, the pkt doesn't seem to go anymore up in the
stack. Even when i put junk in my "pre-canned" ping pkt, i don't get
checksum error or anything. when, doing ifShow "myvif", i can see
"packets received" field get incremented. I know my driver increments
the "unicast packets received" field. But, as a result of ping, it
(pingDmon on target) should reply back, and consequently, "sent" count
on my vif should go up. So, i conclude, pingD did never really RXed my
pkt. Perhaps, IP saw it....well, as you can see, i am lost in the RX
side. If i could get IP/ping complain about its RX packt, at least, i
could go from there...

Any help is most welcome.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: C++ in vxWorks image
Date: Tue, 12 Nov 2002 12:27:30 -0600
From: Keith Obrien <obrienk.spam@minn.teradyne.com>
Message-ID: <3DD14812.3050707@minn.teradyne.com>
References: <3DCA8595.5060706@minn.teradyne.com> <488e459a.0211072358.effa57a@posting.google.com> <3DD03E0A.2020505@minn.teradyne.com> <488e459a.0211112156.2ae558cb@posting.google.com>

Thanks John,

Unfortunately my Windsurf login just ran out in Oct...

- -Keith

John wrote:

> Hello,
> 
> Just on WindSurf searching for something and I cam across this article
> that might be helpful for what you're doing with the ROM images:
> 
> http://www.windriver.com/cgi-bin/windsurf/techtips/public/viewSum.cgi?1899
> 
> HTH,
> 
> John...
> 
> Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DD03E0A.2020505@minn.teradyne.com>...
> 
>>Thanks John,
>>
>>Actual I was able to get it all to build ok with the archive files, but
>>will certainly give the .out build a whirl.
>>
>>Any idea how to put a 4 Meg vxWorks image into a ROM, that is, a ROMed
>>version of our applcation that skips the download step.  I see several
>>targets, e.g., vxWorks.st_rom, but none work directly with our setup.
>>
>>We've got a PPC with 1M of head room from the boot vector.  We have 15M below
>>this address space that we can access, but the boot process and config MACROS
>>seem to want a contiguous memory.  Do I have to write my own code to facilite
>>this, or is there something I'm not seeing?  I suppose we could use some sort
>>of flash file system (TFFS for example), but that seems a little awkward.
>>
>>Any info would certainly help!  And thanks again. Hope I can return the favor someday!
>>
>>-Keith
>>
>>
>>
>>
>>John wrote:
>>
>>
>>>Hello,
>>>
>>>No, LIB_EXTRA is not the correct thing to use, nor is a .a format
>>>file. Instead, use the ADDED_MODULES macro to add your program.out
>>>file directly to the image (if you have more than one, add them all to
>>>this macro).
>>>
>>>The problem with the .a file format is that the linker will only
>>>extract the .o files from it that it believes are needed by the
>>>program, based on symbolic dependencies between them.
>>>
>>>HTH,
>>>
>>>John...
>>>
>>>Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DCA8595.5060706@minn.teradyne.com>...
>>>
>>>
>>>>We've used C++ in our e.g., progam.out downloads successfully for some time.
>>>>
>>>>however, when we add our now archived (e.g., program.a) files to LIB_EXTRA in the
>>>>makefile for our 'make vxWorks' build name mangling or some such appears to
>>>>be getting in the way.
>>>>
>>>>Anybody know if LIB_EXTRA is the appropriate place to add our acrhives?
>>>>If so, anything that needs to be done to allow for C++ in the vxWorks image?
>>>>
>>>>Regards,
>>>>-ko
>>>>
>>>>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.0 (Windows) automatically saving files without
Date: Tue, 12 Nov 2002 19:06:11 GMT
From: ggg+news@best.com (GGG)
Organization: rest
Message-ID: <DicA9.39$I1.2167@iad-read.news.verio.net>
References: <sdcf9106.000@chestnut.aaicorp.com>

Just tried it, and same here, even with T2.2.  Looks like a valid bug.
Have you contacted WR support?

GGG

In article <sdcf9106.000@chestnut.aaicorp.com>,
KENT DURHAM <DURHAM@aaicorp.com> wrote:
>One of the users on our system has come to me with this issue he is
>having with Tornado 2.0 for Windows using the built-in editor, and I
>have been able to duplicate it on my machine: 
>
>This is the following scenario:
>1. Open up fooA.c   .  Edit the file.  Do not save  (Asterisk denoting
>changed file shows up in the title bar.)
>2. Open up fooB.c .  (Notice asterisk in fooA.c window title bar
>disappears immediately.)  Play around with this file.  Close this file.
>3. Notices fooA.c no longer has an asterisk.  Goes to close fooA.c. 
>fooA.c does not prompt to save changes.  
>4. Re-opens fooA.c  .  Edits from step 1 have been saved, although user
>never asked for this to happen.
>
>I didn't see any Tornado Options that seemed related to this.  Toggled
>the Save Before Running Tools/Build checkbox, but the behavior is the
>same with either setting.  
>
>Has anyone noticed this behavior before?  Is there another setting I
>can change to resolve this, or is it just a bug?
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Text I/O from multiple protection domains
Date: 12 Nov 2002 14:49:11 -0800
From: risselbruce@yahoo.com (Bruce)
Organization: http://groups.google.com/
Message-ID: <c3dc319c.0211121449.2815b310@posting.google.com>

Our Vxworks AE system has a number of applications each running in a
separate protection domain.  If possible we would like to have a
separate console with separate text I/O for each protection domain. 
Then an engineer working on a particular application within a given
protection domain could send and receive text to/from the application
that he/she is working on with out interference from any of the other
applications.  Do you think that there is a way to do this?

---------------------------

Newsgroups: comp.os.vxworks,comp.arch.embedded
Subject: Re: Power-of-2 algorithm in SDRAM address bus diagnostics
Date: Mon, 11 Nov 2002 20:34:57 -0700
From: Thad Smith <ThadSmith@acm.org>
Message-ID: <3DD076E1.573EAE54@acm.org>
References: <d83bb8e3.0211111151.2d2eeab3@posting.google.com>

Raymond Yeung wrote:
> 
> It seems to me, due to SDRAM's address lines multiplexing nature, power-of-2
> algorithm would result in more work than necessary in order to provide
> same fault coverage over the same address space.

What is the "power-of-2 algorithm"?

> I guess I can tolerate more work, as long as the coverage is just as complete
> (as in non-multiplexing case).  What's your thought in using such algorithm
> in SDRAM, in terms of efficiency and adequacy?  

What are you trying to achieve with the algorithm?  If you are only
testing the lines that go directly to the chip, you could probably
reduce the test cases by taking advantage of the multiplexing.  If you
are testing RAM, you will need to test each bit cell in both states, as
well as check for various types of cross-talk.

Thad

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: C++ in vxWorks image
Date: 11 Nov 2002 19:49:01 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211111949.519e688c@posting.google.com>
References: <3DCA8595.5060706@minn.teradyne.com> <488e459a.0211072358.effa57a@posting.google.com> <3DD03E0A.2020505@minn.teradyne.com>

Hello Keith,

> Any idea how to put a 4 Meg vxWorks image into a ROM, that is, a ROMed
> version of our applcation that skips the download step.  I see several
> targets, e.g., vxWorks.st_rom, but none work directly with our setup.
> 
> We've got a PPC with 1M of head room from the boot vector.  We have 15M below
> this address space that we can access, but the boot process and config MACROS
> seem to want a contiguous memory.  Do I have to write my own code to facilite
> this, or is there something I'm not seeing?  I suppose we could use some sort
> of flash file system (TFFS for example), but that seems a little awkward.

Two things spring to mind immediately, though I've not tried either:

1) Modify the boot code that copies the payload from ROM to RAM to
read the image from underneath the boot code, instead of above it. Not
sure how easy this would be to arrange, but with some magic with
linker options and/or scripts it should be possible.

2) Boot a simple application in the kernel image, that then loads the
main image from lower in flash (again, you can just binary copy this
assuming you create it linked at a fixed address - and you can do that
using the linker's -R option to link against the kernel image by
reference so you get the VxWorks API symbols resolved correctly).

HTH,

John...

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: C++ in vxWorks image
Date: Tue, 12 Nov 2002 19:09:48 GMT
From: "Charles Krinke" <someone@pacbell.net>
Organization: Prodigy Internet http://www.prodigy.com
Message-ID: <0mcA9.1684$KA.90677406@newssvr14.news.prodigy.com>
References: <3DCA8595.5060706@minn.teradyne.com> <488e459a.0211072358.effa57a@posting.google.com> <3DD03E0A.2020505@minn.teradyne.com> <488e459a.0211112156.2ae558cb@posting.google.com> <3DD14812.3050707@minn.teradyne.com>

I have used two methods in the past. The first is to make a bootrom.hex that
includes the application program. The second is appropriate if you are using
TFFS and that method consists of formatting the flash with your vxWorks
image and instructing it to load from flash instead of across the network. I
believe the instructions for this are in the TFFS documentation for vxWorks.

Charles

> >>
> >>Any idea how to put a 4 Meg vxWorks image into a ROM, that is, a ROMed
> >>version of our applcation that skips the download step.  I see several
> >>targets, e.g., vxWorks.st_rom, but none work directly with our setup.
> >>
> >>We've got a PPC with 1M of head room from the boot vector.  We have 15M
below
> >>this address space that we can access, but the boot process and config
MACROS
> >>seem to want a contiguous memory.  Do I have to write my own code to
facilite
> >>this, or is there something I'm not seeing?  I suppose we could use some
sort
> >>of flash file system (TFFS for example), but that seems a little
awkward.
> >>
> >>Any info would certainly help!  And thanks again. Hope I can return the
favor someday!
> >>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: accessing game port on pci sound card
Date: 12 Nov 2002 12:05:35 -0800
From: psandeep@asu.edu (Sandeep)
Organization: http://groups.google.com/
Message-ID: <eb8d77e7.0211121205.765ce4f3@posting.google.com>
References: <eb8d77e7.0211102314.255329fb@posting.google.com> <aqnnf0$d1s$1@snoopy.bndlg.de>

Thank you Michael and John.

IXP1200EB is STRONGARM architecture.
I would like to add a few more things I know.
I have seen the source code in linux. It simply issues an outb(0x201)
function call to access the joystick port. So, I believe that the
sound card writes the joystick information to the I/O space on the
main board. My card does not have any I/O space, it has only memory
space. I do not know where the sound card is trying to write!!
I think that we need to add an offset to 0x201 to get to that
location. But the problem is in finding that offset.

Regards,
Sandeep.

"Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message news:<aqnnf0$d1s$1@snoopy.bndlg.de>...
> Hi Sandeep,
> 
> would like to help, but don't know the IXP1200EB, so give me a chance and
> tell me what architecure type is it?
> x86, 68k, PPC, ARM, ... ?
> 
> Regards,
> Michael
> 
> "Sandeep" <psandeep@asu.edu> schrieb im Newsbeitrag
> news:eb8d77e7.0211102314.255329fb@posting.google.com...
> > Hello All,
> >          Has anybody tried plugging in any of creative technology's
> > sound cards (pci) into a single board computer running vxworks?? I am
> > facing a problem that requires an urgent fix.
> >
> > I do not know the gameport absolute address. The documentation says
> > that the gameport lies at 0x201. But I am sure that I have to add an
> > offset to this number and then access the port. I have accessed it
> > previously with an ISA card plugged into an MBX860. It was as simple
> > as adding the CPU_PCI_ISA_IO_ADRS as offset to 0x201 to directly
> > access the gameport. I need to access the gameport to track movements
> > of the joystick. Can somebody tell me how to find the base address to
> > which I need to add 0x201? I have plugged the sound card to the
> > IXP1200EB. I tried using just 0x201 without adding an offset (just
> > like it is done on PC) but it did not work out. BTW, 0x201 is part of
> > flash memory on my board, so the result was as expected.
> >
> > The card also has an Ensoniq PCI bus master. I am using a 1997 version
> > specification. Is this the latest. Am I using the right version, or
> > does anybody have a much later version?? I have observed many control
> > register default values to be different from that mentioned in the
> > documentation. Its not allowing me to modify registers that the
> > documentation says can be written.
> >
> >
> > Regards,
> > Sandeep.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Why the address down after linker?
Date: 12 Nov 2002 15:58:01 -0800
From: roysun@rediffmail.com (Shantanu K Roy)
Organization: http://groups.google.com/
Message-ID: <f904b8d2.0211121558.6331a132@posting.google.com>
References: <acabfdad.0211051928.615d67a5@posting.google.com>

xmtang@facri.com (xiaomingtang) wrote in message news:<acabfdad.0211051928.615d67a5@posting.google.com>...
> rule in Makefile is:
> boot: startup.o vxboot.o
> 	$(LD) -X -N -e startup -Ttext 000f0000 -Tdata 00110000 -o $@ \
> 		startup.o vxboot.o \
> 		$(WIND_BASE)/target/lib/lib$(CPU)$(TOOL)vx.a
> 	$(ROMSIZEPROG) -b fff0 boot
> 	size386 boot
> 
> 
> using command objdump386 -d boot|more
> 
> boot:     file format a.out-i386
> Disassembly of section .text:
> 00000000 <startup-f0000> jmp    00000002 <startup-efffe>
> 00000002 <startup-efffe> cli
> 00000003 <startup-efffd> addr16 lidt %cs:0x2a0
> 0000000d <startup-efff3> addr16 lgdt %cs:0x2b0
> 00000017 <startup-effe9> movl   %cr0,%eax
> 0000001a <startup-effe6> orw    $0x1,%ax
> 0000001e <startup-effe2> movl   %eax,%cr0
> 00000021 <startup-effdf> jmp    00000023 <startup-effdd>
> 00000023 <startup-effdd> movw   $0x10,%ax
>  My question is why the address is down from startup(f0000) rather
> than up as f0002,f0003,f000d?
> BUT using command nm386 boot|more
> 
> 000f0002 t InitSC400
> 000f02e8 t ___gnu_compiled_c
> 000f0a88 t ___gnu_compiled_c
> 001102a0 B __bss_start
> 001102a0 D __edata
> 00129f18 B __end
> 000f3b68 T __etext
> from indicated above, the address of Text Code is UP(increasing) from
> f0000 and the address of DS or BSS is UP from 00110000.

I do not understand why you should complain. 
...
00000000 <startup-f0000> jmp    00000002 <startup-efffe>
00000002 <startup-efffe> cli
00000003 <startup-efffd> addr16 lidt %cs:0x2a0
0000000d <startup-efff3> addr16 lgdt %cs:0x2b0
00000017 <startup-effe9> movl   %cr0,%eax
...
The values inside the < > brackets are actually the addresses in the
first column by substituting startup = 0xf0000 (size of the text
segment as provided by you as the part of the makefile rule "$(LD) -X
- -N -e startup -Ttext 000f0000 ...")
So
...
00000000 <f0000-f0000 = 0> jmp    00000002 <startup-efffe>
00000002 <f0000-efffe = 0x2> cli
00000003 <f0000-efffd = 0x3> addr16 lidt %cs:0x2a0
0000000d <f0000-efff3 = 0xd> addr16 lgdt %cs:0x2b0
00000017 <f0000-effe9 = 0x17> movl   %cr0,%eax
...
HTH

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Manipulate debug info in ELF file
Date: 12 Nov 2002 16:49:16 -0800
From: adwait@iit.edu (Adwait Sathe)
Organization: http://groups.google.com/
Message-ID: <83f4b1f4.0211121649.7ceadb51@posting.google.com>
References: <83f4b1f4.0211120738.10ef8c23@posting.google.com> <1037126835.810994@newsreader2.wirehub.nl>

Renee,
Our enginering requirements make it difficult to strip debug info from
released builds. The idea here is to allow individual user to decide
what debug info to keep depending on the requirement. A tool to
manipulate ELF file to create stripped ELF file is envisioned that can
be used to generate debugger file.

Adwait

"rat" <if.you.sent.me.unsollicited.email.or.span.you.will.agree.to.my.terms.of.paying.me.1000EURO.per.email@mail.zevenaar.org> wrote in message news:<1037126835.810994@newsreader2.wirehub.nl>...
> Hi,
> 
> What you could do is, build your application/image. You can strip a
> objectfile from it's debugging symbols. After removing the debug symbols of
> the object you dont need the debugging info, link them together into an
> image. Be aware that out only remove the debug symbols and not all symbols.
> You can do this with nm.
> 
> If you need partially stripped objects, try to be inventive with nm, or
> splitup your object - if possible in a part with and without symbols. just
> take a close look at nm and ld - and you might see a new world... :)
> 
> Goodluck,
> Renee.
> 
> "Adwait Sathe" <adwait@iit.edu> wrote in message
> news:83f4b1f4.0211120738.10ef8c23@posting.google.com...
> > The single step debugger we use has a size limitation of 260 MB. We
> > are facing problems with corrupt symbol tables as our *.ou1 file is
> > bigger than 260 MB. We cannot event strip the debug info from our
> > images.
> > I am trying to remove selected debug records from ELF file and create
> > a new file that we can use to create *.ou1. This is what I did.
> > 1. Parse .debug section( It's in Dwarf V1 format).
> > 2. Process DW_TAG_COMPILE_UNIT tag. and look for source file name.
> > 3. Remove the record if debug info for that file in not required.
> > 4. Remove corresponding entry from .debug_srcinfo and .line sections.
> > 5. Update line offset in .debug_srcinfo.
> > 6. Update attributes associated with DW_TAG_COMPILE_UNIT viz.
> > DW_AT_STMT_LIST for line info offset and 0x8106 ( I couldn't see any
> > attributes defined for this in dwarf.h)for source offset.
> >
> > I still get errors while running fromelf(Diab). Can someone please
> > help me out with this. Am I doing the right thing?
> >
> > Thanks in advance,
> >
> > Adwait

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Text I/O from multiple protection domains
Date: 12 Nov 2002 18:51:08 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211121851.56f4ba52@posting.google.com>
References: <c3dc319c.0211121449.2815b310@posting.google.com>

Hello,

If you have enough serial channels (or plan to use sockets), then yes.
Take a look in target/src/demo/PD at the source code for the Eliza
demo. This code makes use of the pdStdIoSet() function to change
standard in and out for a domain to be the socket that the client's
telnet connection came in on. The application code (eliza.c) simply
uses printf() and gets().

HTH,

John...

risselbruce@yahoo.com (Bruce) wrote in message news:<c3dc319c.0211121449.2815b310@posting.google.com>...
> Our Vxworks AE system has a number of applications each running in a
> separate protection domain.  If possible we would like to have a
> separate console with separate text I/O for each protection domain. 
> Then an engineer working on a particular application within a given
> protection domain could send and receive text to/from the application
> that he/she is working on with out interference from any of the other
> applications.  Do you think that there is a way to do this?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: how to set up WDB connection to 3C905C-TX?
Date: Tue, 12 Nov 2002 22:45:06 -0700
From: marcos <gallego@4dv.net>
Message-ID: <92p3tucumif9p2es93mk8trmdpk5o0t1tj@4ax.com>
References: <551abbdb.0208272255.7bd94c3f@posting.google.com>

Hi Gennady

I also have the same problem. I am trying to do a boot over the
network (Pentium target and Win2K as the host). After booting, I am
getting "muxLoad failed!"

I found good documents as "VxWorks Network 5.4 Programmers Guide"  but
still did not help me much.

Also, I think  maybe worth to check your config.h file. There are some
settings on that for the network settings.

Thanks

Marcos

See part of the config.h file here:
=============================================================
#endif	/* INCLUDE_MMU_PENTIUMPRO */
#endif	/* (CPU_VARIANT == PENTIUM) */

#define IO_ADRS_ELC	0x240
#define INT_LVL_ELC	0x0b
#define MEM_ADRS_ELC	0xc8000
#define MEM_SIZE_ELC	0x4000
#define CONFIG_ELC	0	/* 0=EEPROM 1=RJ45+AUI 2=RJ45+BNC */

#define IO_ADRS_ULTRA	0x240
#define INT_LVL_ULTRA	0x0b
#define MEM_ADRS_ULTRA	0xc8000
#define MEM_SIZE_ULTRA	0x4000
#define CONFIG_ULTRA	0	/* 0=EEPROM 1=RJ45+AUI 2=RJ45+BNC */

#define IO_ADRS_EEX	0x240
#define INT_LVL_EEX	0x0b
#define NTFDS_EEX	0x00
#define CONFIG_EEX	0	/* 0=EEPROM  1=AUI  2=BNC  3=RJ45 */
				/* Auto-detect is not supported, so
choose */
				/* the right one you're going to use
*/

#define IO_ADRS_ELT	0x300
#define INT_LVL_ELT	0x0a
#define NRF_ELT		0x00
#define CONFIG_ELT	3	/* 0=EEPROM 1=AUI  2=BNC  3=RJ45 */

=============================================================

On 27 Aug 2002 23:55:48 -0700, kuznetsov_gv@mail.ru (Gennady) wrote:

>Hi all.
>
>Excuse me for a little dumb question but I really need to know...
>I try to set up WDB connection to PC with 3C905C-TX ethernet card. Well, I
>included "WDB END driver connection" in Tornado project. Then it looks I
>have to include ELT netif BSD driver. So there are two questions there.
>First one is that in manual of el3c90xEND driver this ethernet card's
>modification is not listed as supported. Is it critical or 3C905B or 3C905
>are the same? The second one is that the parameters I have to set up for ELT
>are not clear to me (especially NRF_ELT). Do you know any manual references
>about it?
>
>Well, anyway after I set it up and I see that muxDevLoad calls in procedures
>usrEndLibInit (usrEndLib.c) and wdbCommDevInit (wdbEnd.c) are failed, even
>sysEl3c90xEndLoad had not been called. pDevTbl->endLoadString is empty for
>these calls, and I don't see where it should be formed. I think that some
>parameters are not correct but I have no idea which of them.
>
>So can anyone give me any clue, manual reference or just an idea? VxWorks
>5.4, Tornado 2, Pentium BSP.
>Thank you.
>
>Best regards,
>Gennady

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Attaching ISR to the interrupt vector.
Date: Wed, 13 Nov 2002 07:44:09 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <aqssbn$4o1$1@snoopy.bndlg.de>
References: <aqre69$9vf$1@overload.lbl.gov>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

> .org 0x0500  /*External exception vector for MPC8240*/
> bl IntrHandler /*This is a C routine, with no arguments*/
> rfi
>
> But this doesn't work. Is there anything else, that I should to do?
Much more!
How about rescueing registers like LR ?

"Deenadayalan P - CTD, Chennai." <pdeena@ctd.hcltech.com> schrieb im
Newsbeitrag news:aqre69$9vf$1@overload.lbl.gov...
> Hi all,
>
> I am trying to write an interrupt controller driver for MPC8240 without
any
> OS support. I wanted to connect my interrupt handler to the external
> interrupt. Something like "excIntConnect" of vxworks. I am using GNU
Toolkit
> for Compiling.
> Here is the code fragment I am using.
>
> .org 0x0500  /*External exception vector for MPC8240*/
> bl IntrHandler /*This is a C routine, with no arguments*/
> rfi
>
> But this doesn't work. Is there anything else, that I should to do?
> Thanks in advance.
>
> -Deena
>
>
>
> -with warm regards,
> Deena.
>
> Deena Dayalan
> HCL Technologies Ltd,
> 184-188,190,192-196,
> N.S.K Salai (Arcot Road),
> Vadapalani,
> Chennai - 600 026.
>  INDIA
> Phone
>    Office: 91-44-3728366 ( Ext - 1311 )
>    Residence: 91-44-8444705
> E-mail: pdeena@ctd.hcltech.com
>
> This document is intended for transmission to the named recipient only.
If
> you are not that person, you should note that legal rights reside in this
> document and you are not authorized to access, read, disclose, copy, use
or
> otherwise deal with it and any such actions are prohibited and may be
> unlawful. The views expressed in this document are not necessarily those
of
> HCL Technologies Ltd. Notice is hereby given that no representation,
> contract or other binding obligation shall be created by this e-mail,
which
> must be interpreted accordingly. Any representations, contractual rights
or
> obligations shall be separately communicated in writing and signed in the
> original by a duly authorized officer of the relevant company.
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: accessing game port on pci sound card
Date: Wed, 13 Nov 2002 07:57:34 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <aqst4r$617$1@snoopy.bndlg.de>
References: <eb8d77e7.0211102314.255329fb@posting.google.com> <aqnnf0$d1s$1@snoopy.bndlg.de> <eb8d77e7.0211121205.765ce4f3@posting.google.com>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Hi Sandeep,

sorry, haven't ever worked with STRONGARM.
But if it's similiar to PPC, you won't find an I/O-space, but an address
space that the local2Pci-bridge translates to PCI-I/O accesses.
So my tip: look into the PCI configuration in your config.h. Find the
constant named PCI_MSTR_IO_LOCAL --> this is the address base you should use
to add your 0x201.

Regards,
Michael

"Sandeep" <psandeep@asu.edu> schrieb im Newsbeitrag
news:eb8d77e7.0211121205.765ce4f3@posting.google.com...
> Thank you Michael and John.
>
> IXP1200EB is STRONGARM architecture.
> I would like to add a few more things I know.
> I have seen the source code in linux. It simply issues an outb(0x201)
> function call to access the joystick port. So, I believe that the
> sound card writes the joystick information to the I/O space on the
> main board. My card does not have any I/O space, it has only memory
> space. I do not know where the sound card is trying to write!!
> I think that we need to add an offset to 0x201 to get to that
> location. But the problem is in finding that offset.
>
> Regards,
> Sandeep.
>
>
>
>
> "Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message
news:<aqnnf0$d1s$1@snoopy.bndlg.de>...
> > Hi Sandeep,
> >
> > would like to help, but don't know the IXP1200EB, so give me a chance
and
> > tell me what architecure type is it?
> > x86, 68k, PPC, ARM, ... ?
> >
> > Regards,
> > Michael
> >
> > "Sandeep" <psandeep@asu.edu> schrieb im Newsbeitrag
> > news:eb8d77e7.0211102314.255329fb@posting.google.com...
> > > Hello All,
> > >          Has anybody tried plugging in any of creative technology's
> > > sound cards (pci) into a single board computer running vxworks?? I am
> > > facing a problem that requires an urgent fix.
> > >
> > > I do not know the gameport absolute address. The documentation says
> > > that the gameport lies at 0x201. But I am sure that I have to add an
> > > offset to this number and then access the port. I have accessed it
> > > previously with an ISA card plugged into an MBX860. It was as simple
> > > as adding the CPU_PCI_ISA_IO_ADRS as offset to 0x201 to directly
> > > access the gameport. I need to access the gameport to track movements
> > > of the joystick. Can somebody tell me how to find the base address to
> > > which I need to add 0x201? I have plugged the sound card to the
> > > IXP1200EB. I tried using just 0x201 without adding an offset (just
> > > like it is done on PC) but it did not work out. BTW, 0x201 is part of
> > > flash memory on my board, so the result was as expected.
> > >
> > > The card also has an Ensoniq PCI bus master. I am using a 1997 version
> > > specification. Is this the latest. Am I using the right version, or
> > > does anybody have a much later version?? I have observed many control
> > > register default values to be different from that mentioned in the
> > > documentation. Its not allowing me to modify registers that the
> > > documentation says can be written.
> > >
> > >
> > > Regards,
> > > Sandeep.

---------------------------

Newsgroups: comp.os.vxworks
Subject: CyrixMediaGX and Tornado 2.2/VxWorks 5.5 Pentium BSP
Date: 13 Nov 2002 01:39:43 -0800
From: fabio.roncadi@gambro.com (Fabio Roncadi)
Organization: http://groups.google.com/
Message-ID: <9ec0e92c.0211130139.49d8cd80@posting.google.com>

I got it! After a lot of investigation and the help of Windriver
Support...

The problem was in the SysAlib.s inside the SysCpuProbeStart:

*****
sysCpuProbeStart:
	pushfl				/* save EFLAGS */
        cli				/* LOCK INTERRUPT */
- ---->>>	jmp sysCpuProbePentium  <<<-----
	/* check 386. AC bit is a new bit for 486, 386 can not toggle */
*****

I added this jump to the label sysCpuProbePentium cause my CPU is a
CyrixMediaGx and not a genuine Intel.

Now After the system boots up the output is displayed correctly.
No more problems on the bootrom.sys.... i hope... :)

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: accessing game port on pci sound card
Date: Wed, 13 Nov 2002 12:37:41 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1037187574.794123@newsreader1.wirehub.nl>
References: <eb8d77e7.0211102314.255329fb@posting.google.com> <aqnnf0$d1s$1@snoopy.bndlg.de> <eb8d77e7.0211121205.765ce4f3@posting.google.com>

Have you looked in the strongarm/arch directories to see how things
are done. Not every driver is "ported" to all CPU-architectures. You
could try to find a bootable kernel for your device - if it is
available - and play with /proc/pci :)  And look at other
dlinux/strongarm drivers to see how they resolve the missing
IO-addressing parts.

Btw what cpu are you using? sa1100?

I guess the documentation of your bourd should help you out, how PCI
io-addresses are mapped. you could also try to search for the
"netwinder" which is a small "PC"-like thing using a strongarm CPU.
The linux-code for this device is available, dont know if it using
PCI. You could check.

I've used this device once as a "development" target until our
own-designed board was available, just to get linux, X and apps
running on a strongarm device.

Cheers,
Renee
- - - - - - - - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

"Sandeep" <psandeep@asu.edu> wrote in message
news:eb8d77e7.0211121205.765ce4f3@posting.google.com...
> Thank you Michael and John.
>
> IXP1200EB is STRONGARM architecture.
> I would like to add a few more things I know.
> I have seen the source code in linux. It simply issues an
outb(0x201)
> function call to access the joystick port. So, I believe that the
> sound card writes the joystick information to the I/O space on the
> main board. My card does not have any I/O space, it has only memory
> space. I do not know where the sound card is trying to write!!
> I think that we need to add an offset to 0x201 to get to that
> location. But the problem is in finding that offset.
>
> Regards,
> Sandeep.
>
>
>
>
> "Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in
message news:<aqnnf0$d1s$1@snoopy.bndlg.de>...
> > Hi Sandeep,
> >
> > would like to help, but don't know the IXP1200EB, so give me a
chance and
> > tell me what architecure type is it?
> > x86, 68k, PPC, ARM, ... ?
> >
> > Regards,
> > Michael
> >
> > "Sandeep" <psandeep@asu.edu> schrieb im Newsbeitrag
> > news:eb8d77e7.0211102314.255329fb@posting.google.com...
> > > Hello All,
> > >          Has anybody tried plugging in any of creative
technology's
> > > sound cards (pci) into a single board computer running vxworks??
I am
> > > facing a problem that requires an urgent fix.
> > >
> > > I do not know the gameport absolute address. The documentation
says
> > > that the gameport lies at 0x201. But I am sure that I have to
add an
> > > offset to this number and then access the port. I have accessed
it
> > > previously with an ISA card plugged into an MBX860. It was as
simple
> > > as adding the CPU_PCI_ISA_IO_ADRS as offset to 0x201 to directly
> > > access the gameport. I need to access the gameport to track
movements
> > > of the joystick. Can somebody tell me how to find the base
address to
> > > which I need to add 0x201? I have plugged the sound card to the
> > > IXP1200EB. I tried using just 0x201 without adding an offset
(just
> > > like it is done on PC) but it did not work out. BTW, 0x201 is
part of
> > > flash memory on my board, so the result was as expected.
> > >
> > > The card also has an Ensoniq PCI bus master. I am using a 1997
version
> > > specification. Is this the latest. Am I using the right version,
or
> > > does anybody have a much later version?? I have observed many
control
> > > register default values to be different from that mentioned in
the
> > > documentation. Its not allowing me to modify registers that the
> > > documentation says can be written.
> > >
> > >
> > > Regards,
> > > Sandeep.

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Thu Nov 14 04:03:37 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Thu Nov 14 04:03:39 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Thu Nov 14 04:03:35 PST 2002

        Subject: flash routines for mvme51xx
        Subject: Is there more convenient way to present Tornado compiler output?
        Subject: Re: Is there more convenient way to present Tornado compiler output?
        Subject: netbuflib
        Subject: Re: Routines from ISR that use tExcTask
        Subject: 405 BSP, IRQ's, MMU (was Re: FLASH lockup on PPC405GP eval board? )
        Subject: Re: Is there more convenient way to present Tornado compiler output?
        Subject: Sparc Library supporting Soft-Float
        Subject: The interface between MPC860 and asynchronous FIFO
        Subject: Re: netbuflib

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: flash routines for mvme51xx
Date: 13 Nov 2002 04:33:08 -0800
From: kelly.hornsby@trw.com (flingylingy)
Organization: http://groups.google.com/
Message-ID: <2aac1ba4.0211130433.2e687560@posting.google.com>

Hello All

I'm looking for some flash storage routines for the MVME51xx series of
devices.  Does anyone have any they would like to share?  Otherwise, I
have to roll my own, and I don't like the idea of reinventing the
wheel every time.  There's not one in the BSP.

reply here or email me.

thanks a lot

---------------------------

Newsgroups: comp.os.vxworks
Subject: Is there more convenient way to present Tornado compiler output?
Date: 13 Nov 2002 05:23:19 -0800
From: toader@mail.ru (Andrei Sedelnikov)
Organization: http://groups.google.com/
Message-ID: <6839b7a5.0211130523.79dee7b1@posting.google.com>

Hello,

I'm just wondering, whether the more convenient way to present Tornado
compiler output exist. What we get now, running the compiler from
command line is a huge text output where one can hardly locate the
message, which caused the compilation, among others.

Thanks
Andrei

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is there more convenient way to present Tornado compiler output?
Date: Wed, 13 Nov 2002 14:32:36 GMT
From: "Lou Rohan" <L&R&R&1@cec.wustl.edu>
Organization: The Boeing Company
Message-ID: <H5Ir2C.4w8@news.boeing.com>
References: <6839b7a5.0211130523.79dee7b1@posting.google.com>
Sender: nntp@news.boeing.com (Boeing NNTP News Access)

"Andrei Sedelnikov" <toader@mail.ru> wrote in message
news:6839b7a5.0211130523.79dee7b1@posting.google.com...
> Hello,
>
> I'm just wondering, whether the more convenient way to present Tornado
> compiler output exist. What we get now, running the compiler from
> command line is a huge text output where one can hardly locate the
> message, which caused the compilation, among others.
>
> Thanks
> Andrei

Have you tried redirecting the standard error and standard output to a file?

csh
make >& output.txt

sh
make > output.txt 2>&1

DOS
make 2>&1 output.txt

I think the redirections above are correct, if not, google.

Lou (remove &s to get my email address)

---------------------------

Newsgroups: comp.os.vxworks
Subject: netbuflib
Date: Wed, 13 Nov 2002 17:28:22 +0200
From: "Martin Roth" <bmr006@email.mot.com>
Organization: Motorola
Message-ID: <aqtr31$im8$1@newshost.mot.com>

I would like to see netBufLib source files. Specifically speaking:

1. Why when setting my own function in my own created pool (not netpool of
system/network task, but my own created pool), cause system/netpool to call
them.
Does this means POOL_FUNC member in netPool is not re-entrant ? Or is there
any way around this BUG ?

2. I'd like to know when clBlkGetRtn is called. It is not called from
netTupleGet.

3. What does the code related to  pClBlk->pClFreeRtn does ? Meaning I'd like
to set my own free function of a cluster belonging to a clBlk, is this the
appropriate function ?

Martin Roth
Mailto:bmr006@email.mot.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Routines from ISR that use tExcTask
Date: Wed, 13 Nov 2002 18:04:35 +0100
From: Stefan Tauche <stefan.tauche@infineon.no.spam.com>
Organization: Infineon Technologies AG
Message-ID: <3DD28623.546CDFA8@infineon.no.spam.com>
References: <3DCBE38C.7599AB28@infineon.no.spam.com> <newscache$8ds95h$atd$1@lnews.actcom.co.il>

Hi Leonid,

many thanks for your answer.
The culprit in my case was selWakeupAll() from selectLib, which
is listed below.
But just to avoid this confusing "messages lost"-message in the
terminal,
do you know, if there's a way to find out, if the execTask-Queue is full
or not ?

Regards
Stefan ;-)

12521      libPPC860gnuvx.a:rlogLib.o:         U excJobAdd
13435      libPPC860gnuvx.a:excLib.o:         U _func_excJobAdd
13440      libPPC860gnuvx.a:excLib.o:000000dc T excJobAdd
13531      libPPC860gnuvx.a:funcBind.o:00000004 C _func_excJobAdd
14542      libPPC860gnuvx.a:selectLib.o:         U excJobAdd
14596      libPPC860gnuvx.a:sigLib.o:         U excJobAdd
15043      libPPC860gnuvx.a:dbgLib.o:         U excJobAdd
15875      libPPC860gnuvx.a:aioPxLib.o:         U excJobAdd
18418      libPPC860gnuvx.a:taskLib.o:         U _func_excJobAdd
20101      libPPC860gnuvx.a:fioLib.o:         U excJobAdd
20261      libPPC860gnuvx.a:shellLib.o:         U excJobAdd
20397      libPPC860gnuvx.a:telnetLib.o:         U excJobAdd
20446      libPPC860gnuvx.a:tyLib.o:         U _func_excJobAdd

Leonid Rosenboim wrote:
> 
> "Stefan Tauche" <stefan.tauche@infineon.no.spam.com> wrote in message
> news:3DCBE38C.7599AB28@infineon.no.spam.com...
> [snip]
> >
> > Just to be informed, does anybody have a list of routines that use
> > excJobAdd()
> > when called from an ISR ?
> >
> 
> Here is a rather simnple method:
> 
>     cd $(WIND_BASE)/target/lib
>     nm386 -o libPENTIUMgnuvx.a | grep excJobAdd
> 
> will generate the list of MODULES that have external reference to
> excJobAdd().
> This method has one shortcoming - some years back, at about when
> MicroWorks(tm)
> was released, excLib and tExcTask where made OPTIONAL, so some of the
> libraries
> referncing excJobAdd() where modified to refer the function by way of a
> global hook
> variable (this is where my recollecion stops at the moment - can't recall
> the name
> of that variable), so you will be able to guess the variable name by listing
> the
> symbol names of excLib.o
> 
> Still, many modules call the excJobAdd function directly so excLib and
> tExcTask
> are not really optional for any practical purpose.
> 
> -- HTH
> -----------------------------------------------------------------------
>    Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
>        Consultant                Email: my first name at consultant dot com

- -- 
         //================================
        // Stefan Tauche
       //  Application Engineering
      //   Carrier Access Products
     //
    //     Infineon Technologies AG, Munich
   //
  //       Email: stefan.tauche@infineon.no-spam.com
 // 		  Remove no-spam to reply
//===========================

---------------------------

Newsgroups: comp.os.vxworks
Subject: 405 BSP, IRQ's, MMU (was Re: FLASH lockup on PPC405GP eval board? )
Date: 13 Nov 2002 14:07:57 -0800
From: sohacki@nc.rr.com (Tim Sohacki)
Organization: http://groups.google.com/
Message-ID: <e48fc478.0211131407.531a170e@posting.google.com>

> Charles wrote:
> > We are using WindRivers PPC405GP evaluation board. The onboard FLASH 
> > periodically locks up. The unit no longer responds to the terminal 
> > port on boot and will not download VxWorks image on ethernet connection.
> > The only way to recover is to rewrite the FLASH with JTAG connection.
> > 
> > Anyone else experience this?  What is the cause?
> 
> Yep, all the time. Sectors get erased and/or locked somehow. 
> Don't know why, but you're not alone.

Folks,

I've recreated a variation of this problem by sticking an IRQ line
ACTIVE.

To recreate: enable the GPIO line that is multiplexed with IRQ6 as a
output, drive it low, and enable IRQ as an ACTIVE LOW interrupt.  BAM!
Flash is hosed.

Variations (different IRQ's, for example) don't necessarily hose
Flash.

What happens is data something like the following is written *all*
over the memory space.  The data below includes an address (in this
case, 0xf0604170 which is locally relative, this stuff was found near
0xf0600000), LR (0x006ffc2c), the CR (0x42000040), the MSR
(0x00000030), and something else (0x0000111c).  The pattern repeats.

With StrataFlash, the errant 0x42000040 is sufficient to enable a
write.

   ... snip ...
   f0 60 41 70   00 00 00 00   00 00 00 00   00 00 00 00 
   00 00 00 00   00 00 00 00   00 00 00 30   00 00 11 1c
   00 00 00 00   00 6f fc 2c   42 00 00 40   00 00 00 00 
   00 00 00 00   00 00 00 00   00 00 00 00   00 00 00 00 
   f0 60 01 b0   00 00 00 00   00 00 00 00   00 00 00 00
   ... snip ...

Any thoughts or suggestions?   Thanks! 

Cheers,
Tim.

405 405GP MMU PPC405GP wrSbc405gp interrupt IRQ vxWorks uicIntr.c TLB

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is there more convenient way to present Tornado compiler output?
Date: 13 Nov 2002 17:15:55 -0800
From: hsingyuan@yahoo.com (Hsing Yuan)
Organization: http://groups.google.com/
Message-ID: <70d78653.0211131715.69799b5e@posting.google.com>
References: <6839b7a5.0211130523.79dee7b1@posting.google.com> <H5Ir2C.4w8@news.boeing.com>

In unix environment, you can use the unix command "script" to capture
any output to the terminal.

Hsing Yuan

"Lou Rohan" <L&R&R&1@cec.wustl.edu> wrote in message news:<H5Ir2C.4w8@news.boeing.com>...
> "Andrei Sedelnikov" <toader@mail.ru> wrote in message
> news:6839b7a5.0211130523.79dee7b1@posting.google.com...
> > Hello,
> >
> > I'm just wondering, whether the more convenient way to present Tornado
> > compiler output exist. What we get now, running the compiler from
> > command line is a huge text output where one can hardly locate the
> > message, which caused the compilation, among others.
> >
> > Thanks
> > Andrei
> 
> Have you tried redirecting the standard error and standard output to a file?
> 
> csh
> make >& output.txt
> 
> sh
> make > output.txt 2>&1
> 
> DOS
> make 2>&1 output.txt
> 
> I think the redirections above are correct, if not, google.
> 
> Lou (remove &s to get my email address)

---------------------------

Newsgroups: comp.os.vxworks
Subject: Sparc Library supporting Soft-Float
Date: Thu, 14 Nov 2002 05:32:13 GMT
From: "Edward Ryoo" <shryoo@lge.com>
Organization: Dacom
Message-ID: <xzGA9.2697$Bd3.332995@news.bora.net>

Hi all,

The CPU of LSI's Avia9600 that I use now, is a family of SPARC V8, but it
does not include a floating point unit
and a coprocessor. So, I wanna use a software floating point emulation, but,
as I know, there is no soft-float routines in sparc library file in
Tornado2.0 for Sparc, but only in sparclite one.
How can I get the sparc library supporting soft-float?

Thankx in advance.

Ed

---------------------------

Newsgroups: comp.os.vxworks
Subject: The interface between MPC860 and asynchronous FIFO
Date: 14 Nov 2002 03:01:39 -0800
From: microtnt@sina.com (MicorTNT)
Organization: http://groups.google.com/
Message-ID: <f373d5a6.0211140301.2849f362@posting.google.com>

There is a EPLD between my MPC860 Board and asynchronous FIFO
IDT7201LA(512*9).

The connection logics are:
FIFO_TX_W = MPC_CS4 .OR. MPC_WE0;
FIFO_RX_R = MPC_CS4 .OR. MPC_GPL1;
PC13 = FIFO_Tx_Full_Flag;
PC12 = FIFO_Rx_Empty_Flag;
PA1 = FIFO_Rx_Half_Flag;
Tx_Reset = FIFO_PA0;
There is a bidir_buffer between MPC860 Data bus and FIFO Data enabled
by FIFO_Tx_Full_Flag and FIFO_Rx_Empty_Flag.
The read FIFO address is 0x04007FFE and write_FIFO address is
0x04007FFF.
I selected GPCM to handle it.The port is 8-bit size.

On another side, there are two FIFO:one for send(Address: 0x04007FFF),
another for receive(Address: 0x04007FFE).

I want to access this interface,so I set up MMU as:
OR4:0x00000F44
BR4:0x04000401
and I define the macro:#define FIFOData(base)	(CAST(VUINT8 *)((base))

but when I access FIFO as following:
Write:
*FIFOData(0x04007FFF)=0xXX;
Read:
UINT8 XXX=*FIFOData(0x04007FFE).
in a task in Tornado 2.

There are error as following:
- -> AsynFIFO
value = 33047040 = 0x1f84200

Exception number 768: Task: 0x1f84200 (tAsynFIFO)

data access
program counter:  0x298754
access address:   0x4007fff
machine status:   0x9030
72d7c    vxTaskEntry    +5c : AsynFIFOBegin ([])
2984ec   AsynFIFOBegin  +1c : FIFOStart ([])
298620   FIFOStart      +20 : OnFIFOSend ([])

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: netbuflib
Date: Thu, 14 Nov 2002 11:39:30 -0000
From: "Garry C. Marshall" <gary_marshall@non.agilent.com>
Organization: Agilent Technologies
Message-ID: <1037273981.886403@pengu.britain.agilent.com>
References: <aqtr31$im8$1@newshost.mot.com>

Martin:

"Martin Roth" <bmr006@email.mot.com> wrote in message
news:aqtr31$im8$1@newshost.mot.com...
> I would like to see netBufLib source files. Specifically speaking:
>
> 1. Why when setting my own function in my own created pool (not netpool of
> system/network task, but my own created pool), cause system/netpool to
call
> them.
> Does this means POOL_FUNC member in netPool is not re-entrant ? Or is
there
> any way around this BUG ?

From the description of your problem, I'm assuming your code to initialise
the pool
looks something like:

    NET_POOL  netPool;
    NET_POOL_ID       pNetPool = &netPool;

    if (netPoolInit (pNetPool,  &mClBlkConfig,  &clDescTbl[0],
clDescTblNumEnt,
               NULL) != OK)
               return (ERROR);

And you then use netPool.pFuncTbl to set the POOL_FUNC members to your
own functions.

If this is the case, this is incorrect as the NULL parameter in the
netPoolInit call
above, will result in your pool being given the same default function table
used
by netBufLib.

To use your own functions, you have to provide a pointer to your own
POOL_FUNC
table in the call to netPoolInit.

Have a closer look at the netPoolInit man page for more details.

Regards,

Garry.

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Thu Nov 14 05:00:22 2002
From: "Nithya P" <nithyap490@hotmail.com>
Date: Thu Nov 14 05:00:23 PST 2002
Subject: Running a sample program creates unresolved errors..how to rectify

Hello all,

On running the following sample code, i got some unresolved errors.
I had pasted both the code and error.Please tell how rectify the errors.

Code:
**************************

#include <iostream>
#include "wvapi.h"

int main (int argc, char ** argv)
    {
    if (argc != 2)
        {
        cout << "usage:" << argv [0] << " <logfile.wvr>" << endl;
        exit (1);
        }

    try
        {
        WVEventBase     eb;

        if (eb.load (argv [1]) == OK)
            {
            WVEventBase::iterator       i;

            for (i = eb.begin (); i != eb.end (); ++i)
                {
                WVContext               ctx;
                WVContext::iterator     j;

                ctx = *i;
                for (j = ctx.begin (); j != ctx.end (); ++j)
                    {
                    cout << eb.eventAsString (*j) << endl;
                    }
                }
            }
        else
            {
            cout << "Could not load eventbase " << argv [1] << endl;
            }
        }
    catch (const wv_error &e)
        {
        cout << "WVAPI Error:" << e.what () << " code="
             << e.errorCode () << endl;
        exit (1);
        }

    return 0;
    }

**************************
Linker error:

Errors while downloading 
F:/Tornadox86/target/proj/TestCases/WView/default/VxWV002.o:

___11WVEventBaseP10Tcl_Interp

__$_11WVEventBase

_load__11WVEventBasePCcPFPvii_iPvP7__sFILE

___8WVEBIterPC10CEventBaseUi

_begin__C11WVEventBase

___as__8WVEBIterRC8WVEBIter

_end__C11WVEventBase

___ne__C8WVEBIterRC8WVEBIter

___9WVCtxIterPC8CContextUi

___ml__C8WVEBIter

___as__9WVContextRC9WVContext

___as__9WVCtxIterRC9WVCtxIter

___ne__C9WVCtxIterRC9WVCtxIter

___ml__C9WVCtxIter

_eventAsString__C11WVEventBaseRC7WVEventPCc

___pp__9WVCtxIter

___pp__8WVEBIter

_size__C9WVContext

**************************
what do to rectify this error??

Waiting for your reply.
Thanks
Nithya

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

From vxwexplo-errs@csg.lbl.gov  Fri Nov 15 00:22:15 2002
From: "Adu" <dongjun@fiberhome.com.cn>
Date: Fri Nov 15 00:22:16 PST 2002
Subject: Re: Vx Exploder Digest

hi, all
 

   i want to execute system debugging in VxWorks through serial COM1,
is anyone kind enough to tell me how to configure that step by step ?

thanks in advance

dj

From vxwexplo-errs@csg.lbl.gov  Fri Nov 15 04:03:20 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Fri Nov 15 04:03:21 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Fri Nov 15 04:03:17 PST 2002

        Subject: Download of .out to VxSim fails - communication error - unable to decode parameters
        Subject: Serial communication !
        Subject: ENOBUFS returned by sendmsg()
        Subject: DMA memory mapping
        Subject: Re: Attaching ISR to the interrupt vector.
        Subject: Re: 1553 bus and Vxworks drivers
        Subject: Re: Running a sample program creates unresolved errors..how to rectify
        Subject: Re: The interface between MPC860 and asynchronous FIFO
        Subject: Artesyn PM/PPC boards available
        Subject: Re: The interface between MPC860 and asynchronous FIFO
        Subject: Re: DMA memory mapping
        Subject: Re: flash routines for mvme51xx
        Subject: Re: DMA memory mapping
        Subject: Re: Serial communication !
        Subject: PC104 VGA card on MBX860

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Download of .out to VxSim fails - communication error - unable to decode parameters
Date: Thu, 14 Nov 2002 12:19:23 GMT
From: "Jerry Flood" <jflood@tellium.com>
Organization: Optimum Online
Message-ID: <fxMA9.33461$Vy4.28815@news4.srv.hcvlny.cv.net>

Hi,

I've configured my NT machine to download a  Tornado project to VxSim. The
target server comes up OK , however, when I download the project .out file,
I get communication error and the target server indicates that it could not
decode the parameters.

Could someone point me in the direction of what to look at ?

Thanks

---------------------------

Newsgroups: comp.os.vxworks
Subject: Serial communication !
Date: 14 Nov 2002 06:12:45 -0800
From: g.croitoru@topex.rdsnet.ro (gigid100)
Organization: http://groups.google.com/
Message-ID: <4288b3b7.0211140612.46c6210f@posting.google.com>

I have a board on which I installed vxworks. In Tornado Shell apperars
installed UART0-> devs : "/tyCo/0", but i can't write and read from
it. If you have some source code examples which do this, plese help
me!

---------------------------

Newsgroups: comp.os.vxworks
Subject: ENOBUFS returned by sendmsg()
Date: Thu, 14 Nov 2002 14:13:56 -0000
From: "King L" <pauld@naespam.spider.com>
Message-ID: <ar0bfl$c01$1$8302bc10@news.demon.co.uk>

When I send lots of packets via sendmsg() in vxWorks IP, send message
returns ENOBUFS.
If I have a delay between sends it is OK.

I have increased the number of buffers NUM_64, NUM_128, NUM_SYS_64,
NUM_SYS_128 etc
in netBufLib.h file. When I see the ENOBUFS error I check
netStackDataPoolShow() and netStackSysPoolShow() and there are no "failed to
find space" errors.

I have also sent a SO_SNDBUF socket option down to increase that value
without success.

Does anyone have any other ideas as to what may be causing this error?

Thanks,
King L

---------------------------

Newsgroups: comp.os.vxworks
Subject: DMA memory mapping
Date: Thu, 14 Nov 2002 20:39:35 -0000
From: "William Stukeley" <gregory.holmes@baesystems.com>
Message-ID: <ar11m8$n39$1@newsg3.svr.pol.co.uk>

Hello there VxWorkers

I wondered if any of you could shed any light on the problem I'm having.

I'm using an Ampro Littleboard P5v and a GMM serial card and writing a
device driver to read 422 data from the GMM using DMA on the
generic Pentium BSP.

I can't seem to find any information about how to map the memory in
VxWorks to the PC memory and DMA so that the DMA transfer can take place.
I know that the Floppy Driver uses DMA and maps to 0x5000 to 0x8000 but I
can't seem to find the code it uses to study how the memory mapping works.

I know that the DMA buffer must be below 16MB as that is the limit of
the addressing range of the 8237 DMA chip.

I have seen that I can alter the sysPhysMemDesc structure in the
syslib.c file to allocate a physical buffer using the following;

{
(void*) 0x?????, /* virtual address      */
(void*) 0x08000, /* physical DMA address */
0x20000,  /* 2 x 64k buffers      */
VM_STATE_MASK_VALID|VM_STATE_MASK_WRITABLE|VM_STATE_MASK_CACHEABLE_NOT,
VM_STATE_MASK_VALID|VM_STATE_MASK_WRITABLE|VM_STATE_MASK_CACHEABLE_NOT
},

But as you can see I can't see where to allocate the virtual address or
how the virtual and physical addresses map to each other. I have seen
CACHE_DMA_PHYS_TO_VIRT() but still do not understand how this works.

I have tried to use cacheDmaMalloc(buffer) but have seen that this only
returns
a pointer to a buffer which is in memory above the 16MB I can address with
the 8237 DMA register.

I'm lost in a haze of manuals and printouts from the newsgroups. If I had
any hair I would be tearing it out! I would be most grateful if anyone could
point me in the right direction by suggesting some suitable resource to read
or give me some example code which I may be able to comprehend.

Many Thanks

Greg Holmes

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Attaching ISR to the interrupt vector.
Date: Thu, 14 Nov 2002 22:32:10 +0100
From: "Rene Straub" <_remove_rene.straub@yetnet.ch>
Organization: Swisscom IP+ (post doesn't reflect views of Swisscom)
Message-ID: <ar14oe$oen$1@rex.ip-plus.net>
References: <aqre69$9vf$1@overload.lbl.gov> <aqssbn$4o1$1@snoopy.bndlg.de>

"Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message
news:aqssbn$4o1$1@snoopy.bndlg.de...
> > .org 0x0500  /*External exception vector for MPC8240*/
> > bl IntrHandler /*This is a C routine, with no arguments*/
> > rfi
> >
> > But this doesn't work. Is there anything else, that I should to do?
> Much more!
> How about rescueing registers like LR ?
>
> "Deenadayalan P - CTD, Chennai." <pdeena@ctd.hcltech.com> schrieb im
> Newsbeitrag news:aqre69$9vf$1@overload.lbl.gov...
> > Hi all,
> >
> > I am trying to write an interrupt controller driver for MPC8240 without
> any
> > OS support. I wanted to connect my interrupt handler to the external
> > interrupt. Something like "excIntConnect" of vxworks. I am using GNU
> Toolkit
> > for Compiling.
> > Here is the code fragment I am using.
> >
> > .org 0x0500  /*External exception vector for MPC8240*/
> > bl IntrHandler /*This is a C routine, with no arguments*/
> > rfi
> >
> > But this doesn't work. Is there anything else, that I should to do?
> > Thanks in advance.
> >
> > -Deena
> >
> >
> >
> > -with warm regards,
> > Deena.
> >
[Deleted very long signature]

In general it would be a good idea to save the CPU registers and
re-enable data and address translation (IR and DR in MSR). If required
also enable Floating Point support.

My advice is to disassemble the VxWorks interrupt entry and exit
code an learn from it. It might also be worth to look on Motorolas WebSite
for Application Notes covering this theme.

Yours
- - Rene

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: 1553 bus and Vxworks drivers
Date: 14 Nov 2002 15:22:49 -0800
From: goose23@spu.edu (Matthew Peltzer)
Organization: http://groups.google.com/
Message-ID: <75a1cd5a.0211141522.5fc942c6@posting.google.com>
References: <hfyz9.20$5x.12712@newsfep2-win.server.ntli.net>

"Mike Barton" <mikebnewsbox@yahoo.com> wrote in message news:<hfyz9.20$5x.12712@newsfep2-win.server.ntli.net>...
> Does anyone know of any 1553bus interface cards that have good vxworks
> drivers?
> 
> Mike

I work for Ballard Technology.
We produce a number of avionics interface products, including MIL STD
1553 bus interfaces.
I recently ported drivers for our PCI, cPCI, ISA, and PC104 429 and
1553 products to vxWorks.

Check us out: www.ballardtech.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Running a sample program creates unresolved errors..how to rectify
Date: 14 Nov 2002 16:53:35 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211141653.797ade51@posting.google.com>
References: <ar07mj$sra$1@overload.lbl.gov>

Hello,

There are so many problems here it is hard to know where to start.
Some suggestions/comments:

1) Read the VxWorks Programmer's Guide and the Getting Started Guide

2) Never use main() for VxWorks code (it causes the compiler to
generate things that are not supported in VxWorks). I use vxMain()
(and, indeed, in VxWorks AE this function has some main-like
properties).

3) VxWorks does not use argc/argv style parameters. Instead, functions
that are invoked by taskSpawn may take up to 10 32-bit integers (or
things that can be case to 32-bit integers).

4) VxWorks code should include "vxWorks.h" at the top of the list of
headers.

5) Avoid calling exit() in error cases like this. Calling this
function from the target shell with the incorrect parameters will
result in the shell task exiting - not what you want I suspect.
Instead, VxWorks has a convention whereby functions return 'STATUS'
(that is a type). Status can be OK or ERROR.

Now, your list of undefined symbols suggests that you have either not
included the correct component(s) in your kernel build, or not
downloaded the correct .o files before loading your test case.

I don't recognise the WVEventBase class, so I suspect that it is
something written locally - you should speak to whoever wrote that
code to find out whether it needs to be linked to the kernel somehow,
or if you can just download a .o or .out file before loading your test
code.

HTH,

John...

"Nithya P" <nithyap490@hotmail.com> wrote in message news:<ar07mj$sra$1@overload.lbl.gov>...
> Hello all,
> 
> On running the following sample code, i got some unresolved errors.
> I had pasted both the code and error.Please tell how rectify the errors.
> 
> Code:
> **************************
> 
> #include <iostream>
> #include "wvapi.h"
> 
> int main (int argc, char ** argv)
>     {
>     if (argc != 2)
>         {
>         cout << "usage:" << argv [0] << " <logfile.wvr>" << endl;
>         exit (1);
>         }
> 
>     try
>         {
>         WVEventBase     eb;
> 
>         if (eb.load (argv [1]) == OK)
>             {
>             WVEventBase::iterator       i;
> 
>             for (i = eb.begin (); i != eb.end (); ++i)
>                 {
>                 WVContext               ctx;
>                 WVContext::iterator     j;
> 
>                 ctx = *i;
>                 for (j = ctx.begin (); j != ctx.end (); ++j)
>                     {
>                     cout << eb.eventAsString (*j) << endl;
>                     }
>                 }
>             }
>         else
>             {
>             cout << "Could not load eventbase " << argv [1] << endl;
>             }
>         }
>     catch (const wv_error &e)
>         {
>         cout << "WVAPI Error:" << e.what () << " code="
>              << e.errorCode () << endl;
>         exit (1);
>         }
> 
>     return 0;
>     }
> 
> **************************
> Linker error:
> 
> Errors while downloading 
> F:/Tornadox86/target/proj/TestCases/WView/default/VxWV002.o:
> 
> ___11WVEventBaseP10Tcl_Interp
> 
> __$_11WVEventBase
> 
> _load__11WVEventBasePCcPFPvii_iPvP7__sFILE
> 
> ___8WVEBIterPC10CEventBaseUi
> 
> _begin__C11WVEventBase
> 
> ___as__8WVEBIterRC8WVEBIter
> 
> _end__C11WVEventBase
> 
> ___ne__C8WVEBIterRC8WVEBIter
> 
> ___9WVCtxIterPC8CContextUi
> 
> ___ml__C8WVEBIter
> 
> ___as__9WVContextRC9WVContext
> 
> ___as__9WVCtxIterRC9WVCtxIter
> 
> ___ne__C9WVCtxIterRC9WVCtxIter
> 
> ___ml__C9WVCtxIter
> 
> _eventAsString__C11WVEventBaseRC7WVEventPCc
> 
> ___pp__9WVCtxIter
> 
> ___pp__8WVEBIter
> 
> _size__C9WVContext
> 
> **************************
> what do to rectify this error??
> 
> Waiting for your reply.
> Thanks
> Nithya
> 
> _________________________________________________________________
> Protect your PC - get McAfee.com VirusScan Online 
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: The interface between MPC860 and asynchronous FIFO
Date: 14 Nov 2002 16:57:36 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211141657.42f15979@posting.google.com>
References: <f373d5a6.0211140301.2849f362@posting.google.com> <29b153d9.0211140841.660b8742@posting.google.com>

Hello,

I don't believe that the 860 devices have BAT registers... they do
have an MMU though, so if the address that you are trying to access
was not covered by the descriptions in sysPhysMemDesc[] in your BSP,
then you will get a data access error every time you try to read or
write that address.

HTH,

John...

rick@cyclone.com (Richard Nardone) wrote in message news:<29b153d9.0211140841.660b8742@posting.google.com>...
> Take a look at the addressing mode being utilized.  If you are using
> Block Address Translation, then you are writing to an address not
> covered by one of the four DBAT regions.  The error you are getting
> would be consistent with this condition.
> 
>    Richard Nardone
>    Cyclone Microsystems

---------------------------

Newsgroups: comp.os.vxworks,comp.arch.embedded
Subject: Artesyn PM/PPC boards available
Date: Fri, 15 Nov 2002 01:03:42 GMT
From: ben_myers@charter.net (Ben Myers)
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <3dd4462c.42145567@news.charter.net>
Reply-To: ben_myers@charter.net

I have a pair of Artesyn PM/PPC boards available in good condition, mounted on
PCI carrier boards.  Specs are 333MHz PowerPC, 64Mx72 SDRAM, JTAG.  NetBSD,
Linux, QNX, other OSes supported.  Reasonable offers accepted, including exact
shipping to you.

Ben Myers
Spirit of Performance, Inc.
73 Westcott Road
Harvard, MA 01451
tel: 978-456-3889
eFax: 810-963-0412 
PayPal, MC, VISA, AMEX accepted.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: The interface between MPC860 and asynchronous FIFO
Date: 14 Nov 2002 18:52:28 -0800
From: microtnt@sina.com (MicorTNT)
Organization: http://groups.google.com/
Message-ID: <f373d5a6.0211141852.36c4b411@posting.google.com>
References: <f373d5a6.0211140301.2849f362@posting.google.com> <29b153d9.0211140841.660b8742@posting.google.com>

Thank you! I will try it.
But where can I find the detail about address mode in MPC860 User's Mannul
It seems there is few about this in UM.

And what is the meaning of DBAT regions?

rick@cyclone.com (Richard Nardone) wrote in message news:<29b153d9.0211140841.660b8742@posting.google.com>...
> Take a look at the addressing mode being utilized.  If you are using
> Block Address Translation, then you are writing to an address not
> covered by one of the four DBAT regions.  The error you are getting
> would be consistent with this condition.
> 
>    Richard Nardone
>    Cyclone Microsystems

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: DMA memory mapping
Date: Fri, 15 Nov 2002 07:35:46 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1037342219.441966@newsreader2.wirehub.nl>
References: <ar11m8$n39$1@newsg3.svr.pol.co.uk>

Hi Chris,

To access memory on a PCI system, you have to add the address (+size)
to the mmu, with sysMmuMapAdd, before the kernel executes usrMmuInit.
If that is not possible you could try to make you'r own all to
usrMmuInit just after adding the address ranges. you just can add
memorymapped address and not IO.

I dont know if calling usrMmuInit a second time is safe, but it worked
with us. Thou we are leaving it.

And you should do somthing like:

pciConfigOutWord (pciBusNum, pciDeviceNum, pciFuncNum,
       PCI_CFG_COMMAND,
       PCI_CMD_IO_ENABLE | /* +io access */
       PCI_CMD_MEM_ENABLE | /* +mem access */
       PCI_CMD_SERR_ENABLE | /* +syserror */
       0)

To anble the PCI bus for this device. Also take a look at
pciDeviceShow, pciHeaderShow etc.

Hope this helps. Dont know about DMA.

Cheers,
Renee
- - - - - - - - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

"William Stukeley" <gregory.holmes@baesystems.com> wrote in message
news:ar11m8$n39$1@newsg3.svr.pol.co.uk...
> Hello there VxWorkers
>
> I wondered if any of you could shed any light on the problem I'm
having.
>
> I'm using an Ampro Littleboard P5v and a GMM serial card and writing
a
> device driver to read 422 data from the GMM using DMA on the
> generic Pentium BSP.
>
> I can't seem to find any information about how to map the memory in
> VxWorks to the PC memory and DMA so that the DMA transfer can take
place.
> I know that the Floppy Driver uses DMA and maps to 0x5000 to 0x8000
but I
> can't seem to find the code it uses to study how the memory mapping
works.
>
> I know that the DMA buffer must be below 16MB as that is the limit
of
> the addressing range of the 8237 DMA chip.
>
> I have seen that I can alter the sysPhysMemDesc structure in the
> syslib.c file to allocate a physical buffer using the following;
>
> {
> (void*) 0x?????, /* virtual address      */
> (void*) 0x08000, /* physical DMA address */
> 0x20000,  /* 2 x 64k buffers      */
>
VM_STATE_MASK_VALID|VM_STATE_MASK_WRITABLE|VM_STATE_MASK_CACHEABLE_NOT
,
>
VM_STATE_MASK_VALID|VM_STATE_MASK_WRITABLE|VM_STATE_MASK_CACHEABLE_NOT
> },
>
> But as you can see I can't see where to allocate the virtual address
or
> how the virtual and physical addresses map to each other. I have
seen
> CACHE_DMA_PHYS_TO_VIRT() but still do not understand how this works.
>
> I have tried to use cacheDmaMalloc(buffer) but have seen that this
only
> returns
> a pointer to a buffer which is in memory above the 16MB I can
address with
> the 8237 DMA register.
>
> I'm lost in a haze of manuals and printouts from the newsgroups. If
I had
> any hair I would be tearing it out! I would be most grateful if
anyone could
> point me in the right direction by suggesting some suitable resource
to read
> or give me some example code which I may be able to comprehend.
>
> Many Thanks
>
> Greg Holmes
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: flash routines for mvme51xx
Date: Fri, 15 Nov 2002 07:01:27 GMT
From: Dave Wilhardt <dave@wilhardts.com>
Organization: Prodigy Internet http://www.prodigy.com
Message-ID: <3DD49BBB.E189AF40@wilhardts.com>
References: <2aac1ba4.0211130433.2e687560@posting.google.com>

Pretty sure I added TrueFFS support.  Have you looked into that?

- - Dave

flingylingy wrote:

> Hello All
>
> I'm looking for some flash storage routines for the MVME51xx series of
> devices.  Does anyone have any they would like to share?  Otherwise, I
> have to roll my own, and I don't like the idea of reinventing the
> wheel every time.  There's not one in the BSP.
>
> reply here or email me.
>
> thanks a lot

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: DMA memory mapping
Date: 15 Nov 2002 01:19:28 -0800
From: shenoy_sudhakar@hotmail.com (Sudhakar Shenoy)
Organization: http://groups.google.com/
Message-ID: <4d53234f.0211150119.587b3b53@posting.google.com>
References: <ar11m8$n39$1@newsg3.svr.pol.co.uk>

"William Stukeley" <gregory.holmes@baesystems.com> wrote in message news:<ar11m8$n39$1@newsg3.svr.pol.co.uk>...
> Hello there VxWorkers
> 
> I wondered if any of you could shed any light on the problem I'm having.
> 
> I'm using an Ampro Littleboard P5v and a GMM serial card and writing a
> device driver to read 422 data from the GMM using DMA on the
> generic Pentium BSP.
> 
> I can't seem to find any information about how to map the memory in
> VxWorks to the PC memory and DMA so that the DMA transfer can take place.
> I know that the Floppy Driver uses DMA and maps to 0x5000 to 0x8000 but I
> can't seem to find the code it uses to study how the memory mapping works.
> 
> I know that the DMA buffer must be below 16MB as that is the limit of
> the addressing range of the 8237 DMA chip.
> 
> I have seen that I can alter the sysPhysMemDesc structure in the
> syslib.c file to allocate a physical buffer using the following;
> 
> {
> (void*) 0x?????, /* virtual address      */
> (void*) 0x08000, /* physical DMA address */
> 0x20000,  /* 2 x 64k buffers      */
> VM_STATE_MASK_VALID|VM_STATE_MASK_WRITABLE|VM_STATE_MASK_CACHEABLE_NOT,
> VM_STATE_MASK_VALID|VM_STATE_MASK_WRITABLE|VM_STATE_MASK_CACHEABLE_NOT
> },
> 
> But as you can see I can't see where to allocate the virtual address or
> how the virtual and physical addresses map to each other. I have seen
> CACHE_DMA_PHYS_TO_VIRT() but still do not understand how this works.
> 
> I have tried to use cacheDmaMalloc(buffer) but have seen that this only
> returns
> a pointer to a buffer which is in memory above the 16MB I can address with
> the 8237 DMA register.
> 
> I'm lost in a haze of manuals and printouts from the newsgroups. If I had
> any hair I would be tearing it out! I would be most grateful if anyone could
> point me in the right direction by suggesting some suitable resource to read
> or give me some example code which I may be able to comprehend.
> 
> Many Thanks
> 
> Greg Holmes

Hi Greg,
 there is no need to allocate any such buffers for DMA.u can allocate
normal memory using malloc and cacheDmaMalloc(). in the MIPS
processor, the memory is divided into cached and cache-safe buffers.
so when u do a "malloc()", u will get a memory buffer address from the
memory that is cached. and when u do a "cacheDmaMalloc()", u will get
a buffer from the cache-safe memory.
    the virtual addresses that are assigned to the unmapped-cached
memory start from 0x80000000 while the cache-safe buffers get the
address 0xA0000000.
and for a device to access the data, the physical address is required.
so what u can do is, first allocate a buffer ,then use the
"CACHE_DMA_PHYS_TO_VIRT()" to get the actual physical address of the
buffer and give this address for the DMA operation as its Buffer
address along with the Length,next address and other parameters.
i hope this had helped u.
thanks n regds,
Sudhakar Shenoy.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Serial communication !
Date: Thu, 14 Nov 2002 11:10:52 -0500
From: Joe Durusau <joseph.a.durusau@lmco.com>
Organization: Lockheed Martin Corporation
Message-ID: <3DD3CB0C.3978A87E@lmco.com>
References: <4288b3b7.0211140612.46c6210f@posting.google.com>

gigid100 wrote:
> 
> I have a board on which I installed vxworks. In Tornado Shell apperars
> installed UART0-> devs : "/tyCo/0", but i can't write and read from
> it. If you have some source code examples which do this, plese help
> me!

What kind of a problem are you having?  What version of 
vxWorks?  If you type printf("XXX\n") in the shell, where 
(if anywhere) does the XXX show up?  

Speaking only for myself,

Joe Durusau

---------------------------

Newsgroups: comp.os.vxworks
Subject: PC104 VGA card on MBX860
Date: 15 Nov 2002 03:49:24 -0800
From: matthewp@aishtechnologies.com (Matt pardoe)
Organization: http://groups.google.com/
Message-ID: <c3d19f90.0211150349.57f6ab51@posting.google.com>

We are using ugl 1.2 with vxworks, we have an mbx60 board which we are
trying to set up a pc104 vga card. I have configured the ugl to use
the vga driver.

The framebuffer gets mapped into ISA mem space at 0xc00A0000, and the 
registers get mapped to 0x80000000 + reg offset, in ISA I/O space

I have everything set up but get no output to the display when I run
the ugl demo program.

I have tried the card in a PC with a pc104 carrier card and he card
works OK when the PC is set up with the default vga driver.

Has anyone got a vga card working with an mbx860 or other PPC board
using ugl vga drivers.
Is there anything else I need to set up for this to work.

Any help, pointers greatly appreciated

Thanks

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Fri Nov 15 11:23:18 2002
From: Mike McCullough <mike@mccengineering.com>
Date: Fri Nov 15 11:23:19 PST 2002
Subject: Help with JNI in VxWorks

Does anyone have some example code for JNI running in JWorks 4.0 that 
passes a value from the C code back to the Java?? The code from my JNI book 
doesn't even compile, and of course the Wind River tutorial only does 
printf's on the target side...

Any clues would be greatly appreciated...

**********************************************************
Mike McCullough                    MCC Engineering
President and CEO                  9 Cheshire Court
                                    Londonderry, NH 03053

mike@mccengineering.com            Tel:  603-537-9593
                                    Fax:  603-434-9890
www.mccengineering.com            Cell: 603-247-1219

**********************************************************
        24x7 VxWorks Support  Custom Support Programs
          VxWorks Training   Embedded Consulting Services
                     A WindLink Partner
**********************************************************

From vxwexplo-errs@csg.lbl.gov  Fri Nov 15 11:50:54 2002
From: Mike McCullough <mike@mccengineering.com>
Date: Fri Nov 15 11:50:55 PST 2002
Subject: Re: Help with JNI in VxWorks

Answering my own question as I had an old JNI book and the syntax has 
changed...

jstring JNICALL Java_com_windriver_demo_jni_NativePort_NativeGetFileString 
(JNIEnv *env, jobject obj)
{
   char s[20];
   strcpy(s,"w04.jpg");
   printf("C String is: %s\n",s);
   return ((*env)->NewStringUTF(env,s));
}

The SUN Java tutorial corrected the error of my ways...

**********************************************************
Mike McCullough                    MCC Engineering
President and CEO                  9 Cheshire Court
                                    Londonderry, NH 03053

mike@mccengineering.com            Tel:  603-537-9593
                                    Fax:  603-434-9890
www.mccengineering.com            Cell: 603-247-1219

**********************************************************
        24x7 VxWorks Support  Custom Support Programs
          VxWorks Training   Embedded Consulting Services
                     A WindLink Partner
**********************************************************

From vxwexplo-errs@csg.lbl.gov  Sat Nov 16 04:03:17 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sat Nov 16 04:03:19 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sat Nov 16 04:03:14 PST 2002

        Subject: Re: Attaching ISR to the interrupt vector.
        Subject: Re: Download of .out to VxSim fails - communication error - unable to decode parameters
        Subject: Bypassing parts of the stack
        Subject: Passing interface ID with packet to application
        Subject: 826x BSP:  When should I enable RAM based exceptions?
        Subject: [AE] CP3 - Cumulative patch 3
        Subject: Re: The interface between MPC860 and asynchronous FIFO
        Subject: Re: Anyone using GDB?
        Subject: Re: Attaching ISR to the interrupt vector.
        Subject: Passing Data from boot
        Subject: Re: Artesyn PM/PPC boards available
        Subject: Re: Passing Data from boot
        Subject: Re: 826x BSP:  When should I enable RAM based exceptions?
        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: Running a sample program creates unresolved errors..how to rectify
        Subject: Re: CP7000 and DMA
        Subject: Tornado2.0 : start: could not read file "TRY=..."
        Subject: Re: Passing Data from boot

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Attaching ISR to the interrupt vector.
Date: 15 Nov 2002 05:45:57 -0800
From: kiranmandava@hotmail.com (kmandava)
Organization: http://groups.google.com/
Message-ID: <d656e178.0211150545.7068773e@posting.google.com>
References: <aqre69$9vf$1@overload.lbl.gov> <aqssbn$4o1$1@snoopy.bndlg.de> <ar14oe$oen$1@rex.ip-plus.net>

As someone already suggested you should disassemble the excIntConnect
code and try to look at it..as i did recently
the way interrupt handlers work on vxworks is

a. Interrupt stack is different from the normal task stack
b. do you want to support nested interrupts(interrutps with in
terrupts)

here is the general flow...
  at the exception lets say 0x500
  1.  check if it is already handling an interrupt . this is usually
done by using a scratch register
  2. store the link register somwhere..usually one more scrach
register
  3. if it is hanlding the interrupt change the stack to the interrupt
stack and save all the necessary registers
  4. now set a but on a scratch register to say you are handling
interrupt
  5. if required enale IR and DR in the ISR
  6. call your interrupt handler
  7. once done with your ISR now restore the context.

thanks,
kiran

   "Rene Straub" <_remove_rene.straub@yetnet.ch> wrote in message news:<ar14oe$oen$1@rex.ip-plus.net>...
> "Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message
> news:aqssbn$4o1$1@snoopy.bndlg.de...
> > > .org 0x0500  /*External exception vector for MPC8240*/
> > > bl IntrHandler /*This is a C routine, with no arguments*/
> > > rfi
> > >
> > > But this doesn't work. Is there anything else, that I should to do?
> > Much more!
> > How about rescueing registers like LR ?
> >
> > "Deenadayalan P - CTD, Chennai." <pdeena@ctd.hcltech.com> schrieb im
> > Newsbeitrag news:aqre69$9vf$1@overload.lbl.gov...
> > > Hi all,
> > >
> > > I am trying to write an interrupt controller driver for MPC8240 without
>  any
> > > OS support. I wanted to connect my interrupt handler to the external
> > > interrupt. Something like "excIntConnect" of vxworks. I am using GNU
>  Toolkit
> > > for Compiling.
> > > Here is the code fragment I am using.
> > >
> > > .org 0x0500  /*External exception vector for MPC8240*/
> > > bl IntrHandler /*This is a C routine, with no arguments*/
> > > rfi
> > >
> > > But this doesn't work. Is there anything else, that I should to do?
> > > Thanks in advance.
> > >
> > > -Deena
> > >
> > >
> > >
> > > -with warm regards,
> > > Deena.
> > >
> [Deleted very long signature]
> 
> In general it would be a good idea to save the CPU registers and
> re-enable data and address translation (IR and DR in MSR). If required
> also enable Floating Point support.
> 
> My advice is to disassemble the VxWorks interrupt entry and exit
> code an learn from it. It might also be worth to look on Motorolas WebSite
> for Application Notes covering this theme.
> 
> Yours
> - Rene

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Download of .out to VxSim fails - communication error - unable to decode parameters
Date: 15 Nov 2002 05:49:45 -0800
From: jflood@tellium.com (Jerry)
Organization: http://groups.google.com/
Message-ID: <67292d97.0211150549.2b56e64e@posting.google.com>
References: <fxMA9.33461$Vy4.28815@news4.srv.hcvlny.cv.net>

More accurately, the error message indicated it could not "decode
arguments".

The problem was related to having installed a VPN client as described
in

http://groups.google.com/groups?selm=3D128D78.E4E1DBF%40nc.rr.com&output=gplain

In my case, the VPN client installs software from Deterministic
Networks which apparently tweeks the MTU size. While NOT connected via
the VPN client we set the following Registry Key from 100 to 0 and the
download succeeded:

/HKEY_LOCAL_MACHINE/SOFTWARE/DeterministicNetworks/DNE/Parameters/MtuAdjustment

I don't know the long term effect of changing the header MTU size as
described in the above article, so for now, I am removing the VPN
client software.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Bypassing parts of the stack
Date: Fri, 15 Nov 2002 09:08:12 -0500
From: David Cooper <cooper_dave@si.com>
Organization: Smiths Industries
Message-ID: <MPG.183ec9d8a5dfe794989680@news.si.com>

I have an Ethernet board which implements IP and UDP on board.  I still 
want to be able to use other higher level protocols which are available 
in the Wind River stack.  Is there a way to bind my driver through the 
MUX interface to the higher level protocols ? 

...david

---------------------------

Newsgroups: comp.os.vxworks
Subject: Passing interface ID with packet to application
Date: Fri, 15 Nov 2002 09:44:41 -0500
From: "Harjinder Chayra" <harjinder.chayra@imedia.com>
Organization: Storm Internet Services
Message-ID: <ar318u$jsd$1@news.storm.ca>
Sender: terayon@gw-terayon.storm.ca

In a MUX based system how can we pass an ID indicating the receive interface
(ifIndex) to an application (e.g. SNMP agent) along with the packet ?

Thanks
Harjinder

---------------------------

Newsgroups: comp.os.vxworks
Subject: 826x BSP:  When should I enable RAM based exceptions?
Date: 15 Nov 2002 07:02:34 -0800
From: FrankGleeson@motorola.com (frankg)
Organization: http://groups.google.com/
Message-ID: <a7b7bb67.0211150702.39293677@posting.google.com>

I am porting v34 of the wrSbc8260 BSP to an 8265 board
that we have designed. We use a bootrom to bootp and then
tftp a vxWorks.st build and then transfer control to it.
This question only deals with the bootrom however.

In romInit.s I have setup the MSR IP bit so that exceptions
are flash based. Later on from sysHwInit2() I change the IP
bit so that exceptions are RAM based. 

I must run initially with flash based exceptions because unlike 
the wrSbc8260 design we are using the 8260 watchdog timer. So I 
have a flash based decrementer executing at 10Hz for kicking the 
watchdog. The watchdog is configured for max timeout in our design 
this is 1.97 seconds.

The BSP has been running fine with watchdog disabled. I am now trying
to get the watchdog functionality working. I have to clear the MSR[IP]
bit (ram based exceptions) for the vxWorks intConnect functionality to
work. I think the current location in sysHwInit2() is way to early.

The ram based timer exception handler will also kick the watchdog. The
problem is I need to manage the transition from flash based to ram
based so that there is never a 2 second gap between kicks. I think I
should postpone
the transition until immediately after the vxworks timer has been
setup.

Does anyone know the best location for this? I am thinking of putting
it in bootConfig.c in usrRoot() like so:

    /* set up system timer */

    sysClkConnect ((FUNCPTR) usrClock, 0);/* connect clock interrupt
routine */
    sysClkRateSet (60);         /* set system clock rate */
    sysClkEnable ();            /* start it */
    sysEnableRamBasedExceptions();

I guess I am looking for a sanity check. Can anyone think of a reason
why this would not work?

---------------------------

Newsgroups: comp.os.vxworks
Subject: [AE] CP3 - Cumulative patch 3
Date: 15 Nov 2002 08:45:39 -0800
From: strick@hiwaay.net (BS)
Organization: http://groups.google.com/
Message-ID: <d64227b2.0211150845.35c89f7d@posting.google.com>

Has any of the Tornado AE users upgraded to CP3? If so, have you guys
seen any problems with the close() function.

A customer has complained that his system dies after calling close()
for a file. He verified that the descriptor was correct, and stated
that this code worked before the CP3 update?

Thanks,
Brian

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: The interface between MPC860 and asynchronous FIFO
Date: 15 Nov 2002 09:00:39 -0800
From: rick@cyclone.com (Richard Nardone)
Organization: http://groups.google.com/
Message-ID: <29b153d9.0211150900.33215478@posting.google.com>
References: <f373d5a6.0211140301.2849f362@posting.google.com> <29b153d9.0211140841.660b8742@posting.google.com> <488e459a.0211141657.42f15979@posting.google.com>

john_94501@yahoo.com (John) wrote in message news:<488e459a.0211141657.42f15979@posting.google.com>...
> Hello,
> 
> I don't believe that the 860 devices have BAT registers... they do
> have an MMU though, so if the address that you are trying to access
> was not covered by the descriptions in sysPhysMemDesc[] in your BSP,
> then you will get a data access error every time you try to read or
> write that address.
> 
> HTH,
> 
> John...

  Hi,

   I was incorrect about the MPC860 having BATs.  The registers you
are interested are in the DMMU section, DTLBs as described in Chapter
9 of the MPC860 user's manual.  I would follow John's advice here.

   The 8260 can use BATs as defined in the PowerPC Programming
Environments for 32-Bit Microprocessors.

   The basic point is that even though you have a FIFO interfaced to
the 860 memory controller, you need to make sure your progam has that
address covered by the MMU, if address translation is enabled.

   Regards,

   Richard Nardone
   Cyclone Microsystems

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Anyone using GDB?
Date: 15 Nov 2002 11:01:24 -0800
From: larryc@softcon.net (larry ciummo)
Organization: http://groups.google.com/
Message-ID: <bf43546.0211151101.54c172b7@posting.google.com>
References: <fc6aa284.0210261103.e1ffd10@posting.google.com>

Just start your target server from Tornado or write a little batch
file with tgtsvr.exe args in it, then start gdb, and enter "target wtx
"name of your target svr" then attach to your process from there.

If you decide to switch to rdb protocol, then you'll have to put the
rdb code into your image (if you can still find it), and start gdb and
tell it you are using rdb instead of wtx.  You can also use Insight,
DDD, or gdbtk instead of the line mode gdb interface.

Good luck,
LC

trmanning@netzero.net (tom manning) wrote in message news:<fc6aa284.0210261103.e1ffd10@posting.google.com>...
> Although the Tornado debugger is nice when it works, mostly it does things
> like locks up the Windows NT process or is so intolerably slow that I give
> up on using it. So I was wondering about using GDB, but from everything that
> I have read (all fairly dated), one must INCLUDE_RDB on the target for
> this to work. Unfortunately this INCLUDE doesn't seem to be supported
> anymore. Am I missing something? What debuggers are you using, and how well
> do they work?
> 
> Thanks,
> 
>      ....Tom

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Attaching ISR to the interrupt vector.
Date: 15 Nov 2002 12:54:39 -0800
From: kiranmandava@hotmail.com (kmandava)
Organization: http://groups.google.com/
Message-ID: <d656e178.0211151254.1f0d7d5e@posting.google.com>
References: <aqre69$9vf$1@overload.lbl.gov> <aqssbn$4o1$1@snoopy.bndlg.de> <ar14oe$oen$1@rex.ip-plus.net> <d656e178.0211150545.7068773e@posting.google.com>

here is the general flow...
   at the exception lets say 0x500
   1.  check if it is already handling an interrupt . this is usually
 done by using a scratch register
   2. store the link register somwhere..usually one more scrach
 register
   3. if it is not hanlding the interrupt change the stack to the
interrupt
 stack and save all the necessary registers, else if it is already
handling an interupt use stack pinter and store the context.

   4. now set a bit on a scratch register to say you are handling
 interrupt
   5. if required enale IR and DR in the MSR
   6. call your interrupt handler
   7. once done with your ISR now restore the context.
 
 
 thanks,
 kiran

kiranmandava@hotmail.com (kmandava) wrote in message news:<d656e178.0211150545.7068773e@posting.google.com>...
> As someone already suggested you should disassemble the excIntConnect
> code and try to look at it..as i did recently
> the way interrupt handlers work on vxworks is
> 
> a. Interrupt stack is different from the normal task stack
> b. do you want to support nested interrupts(interrutps with in
> terrupts)
> 
> 
> here is the general flow...
>   at the exception lets say 0x500
>   1.  check if it is already handling an interrupt . this is usually
> done by using a scratch register
>   2. store the link register somwhere..usually one more scrach
> register
>   3. if it is hanlding the interrupt change the stack to the interrupt
> stack and save all the necessary registers
>   4. now set a but on a scratch register to say you are handling
> interrupt
>   5. if required enale IR and DR in the ISR
>   6. call your interrupt handler
>   7. once done with your ISR now restore the context.
> 
> 
> thanks,
> kiran
> 
>    "Rene Straub" <_remove_rene.straub@yetnet.ch> wrote in message news:<ar14oe$oen$1@rex.ip-plus.net>...
> > "Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message
> > news:aqssbn$4o1$1@snoopy.bndlg.de...
> > > > .org 0x0500  /*External exception vector for MPC8240*/
> > > > bl IntrHandler /*This is a C routine, with no arguments*/
> > > > rfi
> > > >
> > > > But this doesn't work. Is there anything else, that I should to do?
> > > Much more!
> > > How about rescueing registers like LR ?
> > >
> > > "Deenadayalan P - CTD, Chennai." <pdeena@ctd.hcltech.com> schrieb im
> > > Newsbeitrag news:aqre69$9vf$1@overload.lbl.gov...
> > > > Hi all,
> > > >
> > > > I am trying to write an interrupt controller driver for MPC8240 without
>  any
> > > > OS support. I wanted to connect my interrupt handler to the external
> > > > interrupt. Something like "excIntConnect" of vxworks. I am using GNU
>  Toolkit
> > > > for Compiling.
> > > > Here is the code fragment I am using.
> > > >
> > > > .org 0x0500  /*External exception vector for MPC8240*/
> > > > bl IntrHandler /*This is a C routine, with no arguments*/
> > > > rfi
> > > >
> > > > But this doesn't work. Is there anything else, that I should to do?
> > > > Thanks in advance.
> > > >
> > > > -Deena
> > > >
> > > >
> > > >
> > > > -with warm regards,
> > > > Deena.
> > > >
> > [Deleted very long signature]
> > 
> > In general it would be a good idea to save the CPU registers and
> > re-enable data and address translation (IR and DR in MSR). If required
> > also enable Floating Point support.
> > 
> > My advice is to disassemble the VxWorks interrupt entry and exit
> > code an learn from it. It might also be worth to look on Motorolas WebSite
> > for Application Notes covering this theme.
> > 
> > Yours
> > - Rene

---------------------------

Newsgroups: comp.os.vxworks
Subject: Passing Data from boot
Date: Fri, 15 Nov 2002 19:54:29 GMT
From: "Joe Welfeld" <jwelfeld@paragon-networks.com>
Organization: Prodigy Internet http://www.prodigy.com
Message-ID: <VhcB9.5871$7w7.1057163410@newssvr10.news.prodigy.com>
Reply-To: "Joe Welfeld" <jwelfeld@paragon-networks.com>

Hello,

I have been searching,  with no luck,  on how I could pass a string from the
bootrom, into "application" ?  I guess I could carve out a spot
USER_RESERVED_MEM,  but I was wondering if there is a preferred method for
doing this ?

Thanks,

Joe Welfeld

---------------------------

Newsgroups: comp.os.vxworks,comp.arch.embedded
Subject: Re: Artesyn PM/PPC boards available
Date: 15 Nov 2002 15:12:54 -0600
From: David Kroeber <kroeby@gmx.de>
Message-ID: <3dd5628b$0$19348$45beb828@newscene.com>
References: <3dd4462c.42145567@news.charter.net>

ben_myers@charter.net (Ben Myers) wrote in
news:3dd4462c.42145567@news.charter.net: 

> I have a pair of Artesyn PM/PPC boards available in good condition,
> mounted on PCI carrier boards.  Specs are 333MHz PowerPC, 64Mx72
> SDRAM, JTAG.  NetBSD, Linux, QNX, other OSes supported.  Reasonable
> offers accepted, including exact shipping to you.

costs (one board)? Available for everyone?

- -- 
Fatal Error in printf(): Console on fire
 - Ullrich von Bassewitz in dcoup

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Passing Data from boot
Date: Fri, 15 Nov 2002 17:27:05 -0500
From: joe durusau <durusau@bellsouth.net>
Organization: WEBUSENET.com
Message-ID: <3DD574B9.3975A386@bellsouth.net>
References: <VhcB9.5871$7w7.1057163410@newssvr10.news.prodigy.com>

Joe Welfeld wrote:

> Hello,
>
> I have been searching,  with no luck,  on how I could pass a string from the
> bootrom, into "application" ?  I guess I could carve out a spot
> USER_RESERVED_MEM,  but I was wondering if there is a preferred method for
> doing this ?
>
> Thanks,
>
> Joe Welfeld

I don't know about "preferred", but vxWorks itself uses part of
the NVRAM if the system has such, to keep stuff like the bootline.
You could do something along that line rather painlessly.

Speaking only for myself,

Joe Durusau

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: 826x BSP:  When should I enable RAM based exceptions?
Date: 15 Nov 2002 15:36:33 -0800
From: FrankGleeson@motorola.com (frankg)
Organization: http://groups.google.com/
Message-ID: <a7b7bb67.0211151536.3da869a9@posting.google.com>
References: <a7b7bb67.0211150702.39293677@posting.google.com>

A status update for anyone that cares. My bootrom code seems to work
fine.
I am switching to RAM based exceptions right after sysClkEnable().

Of course as soon as I obtain my vxWorks.st build via tftp and load it
to ram
I reset shortly thereafter due to the watchdog.

I plan to to use the same strategy there in sysALib.s I will set
MSR[ip] and
MSR[ee]. That way I can use the already debugged dec exception to kick
the watchdog. Once the clock is enabled in usrConfig.c usrRoot I will
turn on clear MSR[ip] (RAM based exceptions). Hopefully there will be
no problems.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Fri, 15 Nov 2002 14:07:20 -0000
From: "King L" <pauld@naespam.spider.com>
Message-ID: <ar2vat$pqq$1$830fa7b3@news.demon.co.uk>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com>

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:ar0d4n$19r$1@helle.btinternet.com...
> King L wrote:
> > When I send lots of packets via sendmsg() in vxWorks IP, send message
> > returns ENOBUFS.
> > If I have a delay between sends it is OK.
> >
> > I have increased the number of buffers NUM_64, NUM_128, NUM_SYS_64,
> > NUM_SYS_128 etc
> > in netBufLib.h file. When I see the ENOBUFS error I check
> > netStackDataPoolShow() and netStackSysPoolShow() and there are no
"failed to
> > find space" errors.
>
> Are there any free buffers?  Don't rely on the error counts being correct!
> There is also a buffer pool allocated by the ethernet driver (ptr in
> END structure).
>
> Try calling netStackDataPoolShow() when you get ENOBUFS - should
> show whether that pool is out of data, or if the problem is elsewhere.
>
> IIRC there are 'problems' in that there is no local flow control
> for transmitted datagrams, so if you are sending a lot back to back
> some will be discarded before reaching the media.  IMHO this is
> a serious bug, the error rate of a (correctly built) local LAN
> segment is very close to zero so it is actually reasonable to
> assume that almost all datagrams that leave one system will
> (in the absence of bridges and routers) be detected by the target
> system - if only as a lost packet because if a lack of receive
> buffers.
>
> David
>

Thanks for the advice David.

I have called netStackDataPoolShow() when I got ENOBUFS but there always
seems
to be plenty of buffers available.

Cheers,
Paul

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Running a sample program creates unresolved errors..how to rectify
Date: Sat, 16 Nov 2002 04:42:47 GMT
From: "drdiags" <drdiags@attbi.com>
Organization: AT&T Broadband
Message-ID: <b1kB9.14119$__1.6592@rwcrnsc51.ops.asp.att.net>
References: <ar07mj$sra$1@overload.lbl.gov> <488e459a.0211141653.797ade51@posting.google.com>

NIthya

    This is the Windview sample code which was meant to be built on the host
platform
(be it Windows or Solaris or etc...). This came out of the Windview User's
Guide
2.0.1. So you may want to re-read using the C API calls for Windview. The
Tcl  and
C APIs were intended to do analysis of a Windview trace after the target has
uploaded
it to the system. At least the WV eventbase stuff..... On Windows, I used MS
.NET
to build this code, even expanded it to give me a better idea of what was
happening.
On Solaris, just link in the apilib.so. On Windows, you have to link in
apilib.lib (?)
IIRC.

"John" <john_94501@yahoo.com> wrote in message
news:488e459a.0211141653.797ade51@posting.google.com...
> Hello,
>
> There are so many problems here it is hard to know where to start.
> Some suggestions/comments:
>
> 1) Read the VxWorks Programmer's Guide and the Getting Started Guide
>
> 2) Never use main() for VxWorks code (it causes the compiler to
> generate things that are not supported in VxWorks). I use vxMain()
> (and, indeed, in VxWorks AE this function has some main-like
> properties).
>
> 3) VxWorks does not use argc/argv style parameters. Instead, functions
> that are invoked by taskSpawn may take up to 10 32-bit integers (or
> things that can be case to 32-bit integers).
>
> 4) VxWorks code should include "vxWorks.h" at the top of the list of
> headers.
>
> 5) Avoid calling exit() in error cases like this. Calling this
> function from the target shell with the incorrect parameters will
> result in the shell task exiting - not what you want I suspect.
> Instead, VxWorks has a convention whereby functions return 'STATUS'
> (that is a type). Status can be OK or ERROR.
>
> Now, your list of undefined symbols suggests that you have either not
> included the correct component(s) in your kernel build, or not
> downloaded the correct .o files before loading your test case.
>
> I don't recognise the WVEventBase class, so I suspect that it is
> something written locally - you should speak to whoever wrote that
> code to find out whether it needs to be linked to the kernel somehow,
> or if you can just download a .o or .out file before loading your test
> code.
>
> HTH,
>
> John...
>
> "Nithya P" <nithyap490@hotmail.com> wrote in message
news:<ar07mj$sra$1@overload.lbl.gov>...
> > Hello all,
> >
> > On running the following sample code, i got some unresolved errors.
> > I had pasted both the code and error.Please tell how rectify the errors.
> >
> > Code:
> > **************************
> >
> > #include <iostream>
> > #include "wvapi.h"
> >
> > int main (int argc, char ** argv)
> >     {
> >     if (argc != 2)
> >         {
> >         cout << "usage:" << argv [0] << " <logfile.wvr>" << endl;
> >         exit (1);
> >         }
> >
> >     try
> >         {
> >         WVEventBase     eb;
> >
> >         if (eb.load (argv [1]) == OK)
> >             {
> >             WVEventBase::iterator       i;
> >
> >             for (i = eb.begin (); i != eb.end (); ++i)
> >                 {
> >                 WVContext               ctx;
> >                 WVContext::iterator     j;
> >
> >                 ctx = *i;
> >                 for (j = ctx.begin (); j != ctx.end (); ++j)
> >                     {
> >                     cout << eb.eventAsString (*j) << endl;
> >                     }
> >                 }
> >             }
> >         else
> >             {
> >             cout << "Could not load eventbase " << argv [1] << endl;
> >             }
> >         }
> >     catch (const wv_error &e)
> >         {
> >         cout << "WVAPI Error:" << e.what () << " code="
> >              << e.errorCode () << endl;
> >         exit (1);
> >         }
> >
> >     return 0;
> >     }
> >
> > **************************
> > Linker error:
> >
> > Errors while downloading
> > F:/Tornadox86/target/proj/TestCases/WView/default/VxWV002.o:
> >
> > ___11WVEventBaseP10Tcl_Interp
> >
> > __$_11WVEventBase
> >
> > _load__11WVEventBasePCcPFPvii_iPvP7__sFILE
> >
> > ___8WVEBIterPC10CEventBaseUi
> >
> > _begin__C11WVEventBase
> >
> > ___as__8WVEBIterRC8WVEBIter
> >
> > _end__C11WVEventBase
> >
> > ___ne__C8WVEBIterRC8WVEBIter
> >
> > ___9WVCtxIterPC8CContextUi
> >
> > ___ml__C8WVEBIter
> >
> > ___as__9WVContextRC9WVContext
> >
> > ___as__9WVCtxIterRC9WVCtxIter
> >
> > ___ne__C9WVCtxIterRC9WVCtxIter
> >
> > ___ml__C9WVCtxIter
> >
> > _eventAsString__C11WVEventBaseRC7WVEventPCc
> >
> > ___pp__9WVCtxIter
> >
> > ___pp__8WVEBIter
> >
> > _size__C9WVContext
> >
> > **************************
> > what do to rectify this error??
> >
> > Waiting for your reply.
> > Thanks
> > Nithya
> >
> > _________________________________________________________________
> > Protect your PC - get McAfee.com VirusScan Online
> > http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: CP7000 and DMA
Date: 15 Nov 2002 20:52:00 -0800
From: shenoy_sudhakar@hotmail.com (Sudhakar Shenoy)
Organization: http://groups.google.com/
Message-ID: <4d53234f.0211152052.c6a050f@posting.google.com>
References: <4d53234f.0210202243.2c15e9b0@posting.google.com> <d656e178.0210291617.4cc7ad63@posting.google.com>

kiranmandava@hotmail.com (kmandava) wrote in message news:<d656e178.0210291617.4cc7ad63@posting.google.com>...
> shenoy_sudhakar@hotmail.com (Sudhakar Shenoy) wrote in message news:<4d53234f.0210202243.2c15e9b0@posting.google.com>...
> > Hi,
> >     we have a Ocelot board with R4000 Mips processor. the board
> > supports 2 PMC slots on it along with the Galileo system controller.we
> > have a custom made PMC card.
> >    if i want to do DMA some data using the gtDma() (galileo dma
> > routine provided by the BSP of ocelot ,cp7000), if the Data is written
> > in memory allocated through "cacheDmaMalloc", it works fine. but if i
> > try writing the same data just by using the "malloc" and DMAing it, it
> > doenst respond.
> >    is it necessary to do some other setting for the same to work??
> > please let me know,
> > thanks n regds,
> > Sudhakar Shenoy.
> 
> cacheDmaMalloc : it allocates the memory which is cache safe which
> could be used for the DMA stuff..!
> 
> malloc doesn't care anything about the caches..
> 
> ofcourse it is not true on all the processors...
> just to try this make the whole of your memory map to be not cacheable
> and try it..!
> 
> kiran
hi kiran,
     thanks for ur response.
actually, what i wanted to do is to allocate a cached memory buffer to
do the DMA operation. so making the entire memory non-cacheble was not
acceptable.
and i was  able to do it by using the cache routines before calling
the dma routines.
thanks n regds,
Sudhakar Shenoy.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tornado2.0 : start: could not read file "TRY=..."
Date: Fri, 15 Nov 2002 11:57:24 +0100
From: "Mario Semo" <mario.semo@kirchnersoft.com>
Organization: Nextra Telekom GmbH
Message-ID: <ar55qa$8lt$1@at-vie-newsmaster01.nextra.at>

Hello,

I had an installation of T2 on aWinNT 4.0machine. last weeki got a new
machinewih W2K and i copied my Tornado dirctory to this new machine. the i
run the setup.exe from the install CD Rom. and finally i exported theT2
specific parts from the registry and imported them in the new machines
regstry.
Then i  added the following to my systems environment
"WIND_BASE"="C:\\APPS\\Tornado"
"WIND_HOST_TYPE"="x86-win32"
"HOSTNAME"="localhost"
NOTE: T2 was installed in f:\tornado on the old machine and is now installed
in c:\apps\Tornado. of course i fixed all drive references in the registry
before i transferred the registry.

Now, when i start T2 i get an error msg
cannot open file "TRY=localhost\host\resource\tcl\windview.win32.tcl"
Then i press ok and T2 starts up.
(the problem occurs all times i start T2).

Now
a) anyone with an idea regarding this problem? i have a file
c:\apps\tornado\host\resource\tcl\windview.win32.tcl.
b) any ideas what i can do?
c) what is this file for? what functionality will i loose?

Another problem (currently not really a problem, i am just confused)
There are some files which contains absolutes pathes:

C:\apps\tornado\host\resource\help\Tornadow.FTS
C:\apps\tornado\host\resource\help\tornadow.GID
C:\apps\tornado\host\resource\help\wv4win.GID
C:\apps\tornado\host\x86-win32\bin\wftpd32.GID

what are these files for? what can i do against this problem?

- --
regards, Mario Semo. http://www.kirchnersoft.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Passing Data from boot
Date: Sat, 16 Nov 2002 11:55:12 +0000 (UTC)
From: "Graham Baxter" <gbaxter@NOSPAMbcs.org.uk>
Organization: BT Openworld
Message-ID: <ar5bms$77l$1@knossos.btinternet.com>
References: <VhcB9.5871$7w7.1057163410@newssvr10.news.prodigy.com>

Joe,

Yes, reserve some place in USER_RESERVED_MEMORY.

I always use it to pass information between the boot and application code.

- --
Regards,

Graham Baxter
Freelance Software Engineer (VxWorks and pSOS BSPs)
Graham Baxter (Software) Limited
gbaxter@NOSPAMbcs.org.uk

"Joe Welfeld" <jwelfeld@paragon-networks.com> wrote in message
news:VhcB9.5871$7w7.1057163410@newssvr10.news.prodigy.com...
> Hello,
>
> I have been searching,  with no luck,  on how I could pass a string from
the
> bootrom, into "application" ?  I guess I could carve out a spot
> USER_RESERVED_MEM,  but I was wondering if there is a preferred method for
> doing this ?
>
> Thanks,
>
> Joe Welfeld
>
>

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sun Nov 17 04:03:13 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sun Nov 17 04:03:15 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sun Nov 17 04:03:11 PST 2002

        Subject: Re: Tornado2.0 : start: could not read file "TRY=..."
        Subject: Re: Passing Data from boot
        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: Running a sample program creates unresolved errors..how to rectify
        Subject: Re: Download of .out to VxSim fails - communication error - unable to decode parameters
        Subject: Re: Running a sample program creates unresolved errors..how to rectify
        Subject: Re: symTbl.c error for vxWorks.st_rom build also ERROR for __FRAME_BEGIN

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado2.0 : start: could not read file "TRY=..."
Date: Sat, 16 Nov 2002 18:43:08 GMT
From: "drdiags" <drdiags@attbi.com>
Organization: AT&T Broadband
Message-ID: <0lwB9.19581$__1.9142@rwcrnsc51.ops.asp.att.net>
References: <ar55qa$8lt$1@at-vie-newsmaster01.nextra.at>

Mario,

   For the "TRY=...." error, there was an SPR Patch for WIN2K Hosts and
Tornado.
If  you can get to WindSurf, you could try looking at the published SPRs for
T2.0.
Or else someone will probably post the number, I just don't remember off
hand.
A google search of this newsgroup should also give you the number. HTH.
  For those other files, sorry no clue.

"Mario Semo" <mario.semo@kirchnersoft.com> wrote in message
news:ar55qa$8lt$1@at-vie-newsmaster01.nextra.at...
> Hello,
>
> I had an installation of T2 on aWinNT 4.0machine. last weeki got a new
> machinewih W2K and i copied my Tornado dirctory to this new machine. the i
> run the setup.exe from the install CD Rom. and finally i exported theT2
> specific parts from the registry and imported them in the new machines
> regstry.
> Then i  added the following to my systems environment
> "WIND_BASE"="C:\\APPS\\Tornado"
> "WIND_HOST_TYPE"="x86-win32"
> "HOSTNAME"="localhost"
> NOTE: T2 was installed in f:\tornado on the old machine and is now
installed
> in c:\apps\Tornado. of course i fixed all drive references in the registry
> before i transferred the registry.
>
> Now, when i start T2 i get an error msg
> cannot open file "TRY=localhost\host\resource\tcl\windview.win32.tcl"
> Then i press ok and T2 starts up.
> (the problem occurs all times i start T2).
>
> Now
> a) anyone with an idea regarding this problem? i have a file
> c:\apps\tornado\host\resource\tcl\windview.win32.tcl.
> b) any ideas what i can do?
> c) what is this file for? what functionality will i loose?
>
> Another problem (currently not really a problem, i am just confused)
> There are some files which contains absolutes pathes:
>
> C:\apps\tornado\host\resource\help\Tornadow.FTS
> C:\apps\tornado\host\resource\help\tornadow.GID
> C:\apps\tornado\host\resource\help\wv4win.GID
> C:\apps\tornado\host\x86-win32\bin\wftpd32.GID
>
> what are these files for? what can i do against this problem?
>
> --
> regards, Mario Semo. http://www.kirchnersoft.com
>
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Passing Data from boot
Date: 16 Nov 2002 13:11:12 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211161311.60721c69@posting.google.com>
References: <VhcB9.5871$7w7.1057163410@newssvr10.news.prodigy.com>

Hello,

As long as the string is not too long (>80 chars I suspect), you could
use the 'other' field in the bootline. Take a look at the code under
target/config/comps/src to see how to get to this information in your
code.

HTH,

John...

"Joe Welfeld" <jwelfeld@paragon-networks.com> wrote in message news:<VhcB9.5871$7w7.1057163410@newssvr10.news.prodigy.com>...
> Hello,
> 
> I have been searching,  with no luck,  on how I could pass a string from the
> bootrom, into "application" ?  I guess I could carve out a spot
> USER_RESERVED_MEM,  but I was wondering if there is a preferred method for
> doing this ?
> 
> Thanks,
> 
> Joe Welfeld

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Thu, 14 Nov 2002 19:21:28 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$dltk5h$ky9$1@lnews.actcom.co.il>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:ar0d4n$19r$1@helle.btinternet.com...
[snip]
> IIRC there are 'problems' in that there is no local flow control
> for transmitted datagrams, so if you are sending a lot back to back
> some will be discarded before reaching the media.  IMHO this is
> a serious bug, the error rate of a (correctly built) local LAN
> segment is very close to zero so it is actually reasonable to
> assume that almost all datagrams that leave one system will
> (in the absence of bridges and routers) be detected by the target
> system - if only as a lost packet because if a lack of receive
> buffers.
>
> David
>
David, my friend, please allow me to disagree -
the ENOBUF error is in fact a flow control signal
that tells the application the packet could not be
delivered down to the interface queue.
In my experience, if you dont ignore this errors,
all packets the application sends succesfully
do reach teh wire.

Asl to LANs and their packet loss rate, I am not sure
there exists such a thing as a "properly designed network",
in reality. Therefore applications should be designed with the
assumption that packets do get lost, and mittigate that.

But even in a "perfect LAN", there are still wires, which have
a certain S/N ratio and a certain BER which translates to a
certain packet loss percentage. There is no communication
medium in the world that has a zero BER (Bit Error Rate),
so however small your BER is, it translates to a certain
amount of lost packets, due to laws of physics.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com
         If you doubt that Nicotine has an effect on women's vocal cords -
           try to drop some ash on the carpet.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Running a sample program creates unresolved errors..how to rectify
Date: Fri, 15 Nov 2002 00:29:55 GMT
From: ggg+news@best.com (GGG)
Organization: rest
Message-ID: <7eXA9.154$I1.14457@iad-read.news.verio.net>
References: <ar07mj$sra$1@overload.lbl.gov>

Your "error while downloading" is confusing.  The example code on the
WindView C++ API is for host (Solaris or Windows) use of WindView (.wvr)
files.  You should be building and running this on your example code.  It
should not be downloaded to your target running VxWorks.

The WindView User's Guide (I'm looking at 2.2, not sure what you are
using), has instructions for compiling Windows and Solaris C++ WindView
API code.

This is in Apendix B.2, C++ API (the example code is in B.4), for me.

Following the instructions there for compiling (include path, adding
libraries) and making sure your path is set appropriately for running the
result should help.

GGG

In article <ar07mj$sra$1@overload.lbl.gov>,
Nithya P <nithyap490@hotmail.com> wrote:
>Hello all,
>
>On running the following sample code, i got some unresolved errors.
>I had pasted both the code and error.Please tell how rectify the errors.
>
>Code:
>**************************
>
>#include <iostream>
>#include "wvapi.h"
>
>int main (int argc, char ** argv)
>    {
>    if (argc != 2)
>        {
>        cout << "usage:" << argv [0] << " <logfile.wvr>" << endl;
>        exit (1);
>        }
>
>    try
>        {
>        WVEventBase     eb;
>
>        if (eb.load (argv [1]) == OK)
>            {
>            WVEventBase::iterator       i;
>
>            for (i = eb.begin (); i != eb.end (); ++i)
>                {
>                WVContext               ctx;
>                WVContext::iterator     j;
>
>                ctx = *i;
>                for (j = ctx.begin (); j != ctx.end (); ++j)
>                    {
>                    cout << eb.eventAsString (*j) << endl;
>                    }
>                }
>            }
>        else
>            {
>            cout << "Could not load eventbase " << argv [1] << endl;
>            }
>        }
>    catch (const wv_error &e)
>        {
>        cout << "WVAPI Error:" << e.what () << " code="
>             << e.errorCode () << endl;
>        exit (1);
>        }
>
>    return 0;
>    }
>
>**************************
>Linker error:
>
>Errors while downloading 
>F:/Tornadox86/target/proj/TestCases/WView/default/VxWV002.o:
>
>___11WVEventBaseP10Tcl_Interp
>
>__$_11WVEventBase
>
>_load__11WVEventBasePCcPFPvii_iPvP7__sFILE
>
>___8WVEBIterPC10CEventBaseUi
>
>_begin__C11WVEventBase
>
>___as__8WVEBIterRC8WVEBIter
>
>_end__C11WVEventBase
>
>___ne__C8WVEBIterRC8WVEBIter
>
>___9WVCtxIterPC8CContextUi
>
>___ml__C8WVEBIter
>
>___as__9WVContextRC9WVContext
>
>___as__9WVCtxIterRC9WVCtxIter
>
>___ne__C9WVCtxIterRC9WVCtxIter
>
>___ml__C9WVCtxIter
>
>_eventAsString__C11WVEventBaseRC7WVEventPCc
>
>___pp__9WVCtxIter
>
>___pp__8WVEBIter
>
>_size__C9WVContext
>
>**************************
>what do to rectify this error??
>
>Waiting for your reply.
>Thanks
>Nithya
>
>_________________________________________________________________
>Protect your PC - get McAfee.com VirusScan Online 
>http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Download of .out to VxSim fails - communication error - unable to decode parameters
Date: Fri, 15 Nov 2002 00:42:24 GMT
From: ggg+news@best.com (GGG)
Organization: rest
Message-ID: <QpXA9.156$I1.6971@iad-read.news.verio.net>
References: <fxMA9.33461$Vy4.28815@news4.srv.hcvlny.cv.net>

Built-in or full simulator, which Tornado version?

If full, which backend?

Can you provide the the parameters used to start the target server
(available from the "Details" button on the VxSim Launch dialog or through
the manual Tools->Target Server->Configure menu)?

Can you provide the actual error message?

GGG

In article <fxMA9.33461$Vy4.28815@news4.srv.hcvlny.cv.net>,
Jerry Flood <jflood@tellium.com> wrote:
>Hi,
>
>I've configured my NT machine to download a  Tornado project to VxSim. The
>target server comes up OK , however, when I download the project .out file,
>I get communication error and the target server indicates that it could not
>decode the parameters.
>
>Could someone point me in the direction of what to look at ?
>
>Thanks
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Running a sample program creates unresolved errors..how to rectify
Date: Fri, 15 Nov 2002 20:53:30 GMT
From: ggg+news@best.com (GGG)
Organization: rest
Message-ID: <e9dB9.183$I1.15754@iad-read.news.verio.net>
References: <ar07mj$sra$1@overload.lbl.gov> <488e459a.0211141653.797ade51@posting.google.com>

The code cited is host code for the WindView Event Base C++ API.

Follow the instructions in the WindView User's Guide for working with the
code (instructions for Win MSVC or Solaris, include paths, libraries) in
the same appendix that provided the code (B, sections 2 and 4 for 2.2, at
least).

GGGG

In article <488e459a.0211141653.797ade51@posting.google.com>,
John <john_94501@yahoo.com> wrote:
>Hello,
>
>There are so many problems here it is hard to know where to start.
>Some suggestions/comments:
>
>1) Read the VxWorks Programmer's Guide and the Getting Started Guide
>
>2) Never use main() for VxWorks code (it causes the compiler to
>generate things that are not supported in VxWorks). I use vxMain()
>(and, indeed, in VxWorks AE this function has some main-like
>properties).
>
>3) VxWorks does not use argc/argv style parameters. Instead, functions
>that are invoked by taskSpawn may take up to 10 32-bit integers (or
>things that can be case to 32-bit integers).
>
>4) VxWorks code should include "vxWorks.h" at the top of the list of
>headers.
>
>5) Avoid calling exit() in error cases like this. Calling this
>function from the target shell with the incorrect parameters will
>result in the shell task exiting - not what you want I suspect.
>Instead, VxWorks has a convention whereby functions return 'STATUS'
>(that is a type). Status can be OK or ERROR.
>
>Now, your list of undefined symbols suggests that you have either not
>included the correct component(s) in your kernel build, or not
>downloaded the correct .o files before loading your test case.
>
>I don't recognise the WVEventBase class, so I suspect that it is
>something written locally - you should speak to whoever wrote that
>code to find out whether it needs to be linked to the kernel somehow,
>or if you can just download a .o or .out file before loading your test
>code.
>
>HTH,
>
>John...
>
>"Nithya P" <nithyap490@hotmail.com> wrote in message
>news:<ar07mj$sra$1@overload.lbl.gov>...
>> Hello all,
>> 
>> On running the following sample code, i got some unresolved errors.
>> I had pasted both the code and error.Please tell how rectify the errors.
>> 
>> Code:
>> **************************
>> 
>> #include <iostream>
>> #include "wvapi.h"
>> 
>> int main (int argc, char ** argv)
>>     {
>>     if (argc != 2)
>>         {
>>         cout << "usage:" << argv [0] << " <logfile.wvr>" << endl;
>>         exit (1);
>>         }
>> 
>>     try
>>         {
>>         WVEventBase     eb;
>> 
>>         if (eb.load (argv [1]) == OK)
>>             {
>>             WVEventBase::iterator       i;
>> 
>>             for (i = eb.begin (); i != eb.end (); ++i)
>>                 {
>>                 WVContext               ctx;
>>                 WVContext::iterator     j;
>> 
>>                 ctx = *i;
>>                 for (j = ctx.begin (); j != ctx.end (); ++j)
>>                     {
>>                     cout << eb.eventAsString (*j) << endl;
>>                     }
>>                 }
>>             }
>>         else
>>             {
>>             cout << "Could not load eventbase " << argv [1] << endl;
>>             }
>>         }
>>     catch (const wv_error &e)
>>         {
>>         cout << "WVAPI Error:" << e.what () << " code="
>>              << e.errorCode () << endl;
>>         exit (1);
>>         }
>> 
>>     return 0;
>>     }
>> 
>> **************************
>> Linker error:
>> 
>> Errors while downloading 
>> F:/Tornadox86/target/proj/TestCases/WView/default/VxWV002.o:
>> 
>> ___11WVEventBaseP10Tcl_Interp
>> 
>> __$_11WVEventBase
>> 
>> _load__11WVEventBasePCcPFPvii_iPvP7__sFILE
>> 
>> ___8WVEBIterPC10CEventBaseUi
>> 
>> _begin__C11WVEventBase
>> 
>> ___as__8WVEBIterRC8WVEBIter
>> 
>> _end__C11WVEventBase
>> 
>> ___ne__C8WVEBIterRC8WVEBIter
>> 
>> ___9WVCtxIterPC8CContextUi
>> 
>> ___ml__C8WVEBIter
>> 
>> ___as__9WVContextRC9WVContext
>> 
>> ___as__9WVCtxIterRC9WVCtxIter
>> 
>> ___ne__C9WVCtxIterRC9WVCtxIter
>> 
>> ___ml__C9WVCtxIter
>> 
>> _eventAsString__C11WVEventBaseRC7WVEventPCc
>> 
>> ___pp__9WVCtxIter
>> 
>> ___pp__8WVEBIter
>> 
>> _size__C9WVContext
>> 
>> **************************
>> what do to rectify this error??
>> 
>> Waiting for your reply.
>> Thanks
>> Nithya
>> 
>> _________________________________________________________________
>> Protect your PC - get McAfee.com VirusScan Online 
>> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: symTbl.c error for vxWorks.st_rom build also ERROR for __FRAME_BEGIN
Date: 16 Nov 2002 13:42:51 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211161342.2ea808eb@posting.google.com>
References: <3DD51FC7.1090105@minn.teradyne.com>

Hello Keith,

> Many many lines like
> 
> ...
> symTbl.c:5456: warning: type defaults to `int' in declaration of `routeCmd'
> ...

This one is well known. The script generates K&R style statements.
Newer releases actually generate ANSI ones (i.e. there is an 'int' in
between the IMPORT and the symbol name.

Depending on the version of Tornado you have, this can be fixed by
finding the script that your system uses - just take a look in
host/sun4-solaris2/bin/makeSymTbl to see whether it is the script
itself, or whether it is simply a wrapper for a TCL script.

> Caused by compile of symTbl.c as created, then compiled below:
> 
> VX_CPU_FAMILY=ppc /wind/host/sun4-solaris2/bin/makeSymTbl tmp.o >symTbl.c
> 
> ccppc -B/wind/host/sun4-solaris2/lib/gcc-lib/ -c -fdollars-in-identifiers -mstrict-align 
> -ansi -nostdinc -O2 -fvolatile -fn
> o-builtin -fno-for-scope -Wall -I/h   -I. -I/wind/target/config/all -I/wind/target/h 
> -I/wind/target/src/config -I/wind/targ
> et/src/drv -DCPU=PPC603   -g -O   symTbl.c
> 
> 
> The compile finally fails:
> 
> symTbl.c:9094: numeric constant contains digits beyond the radix
> symTbl.c:9095: `__FRAME_BEGIN__' undeclared here (not in a function)
> symTbl.c:9095: parse error before `00000000'
> symTbl.c:9096: numeric constant contains digits beyond the radix
> symTbl.c:9097: nondigits in number and not hexadecimal

This one is a little harder to fix. It is caused by the compiler
inserting symbols with a '.' in the name into the code (often caused
when C++ code is included in the kernel). The only fix I know of
(unless you can persuade the compiler not to generate '.' characters
in symbol names, which sometimes is possible via a -f option), is to
run the output of makeSymTbl through a sed or awk script that strips
the lines containing a '.' character.

That means you won't see those symbols on the target, but since they
are normally internal ones anyway this is probably not a significant
loss.

HTH,

John...

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sun Nov 17 21:25:32 2002
From: "Nithya P" <nithyap490@hotmail.com>
Date: Sun Nov 17 21:25:33 PST 2002
Subject:  Re: Running a sample program creates unresolved errors..how to rectify

Hi all,
  Thanks you all guys  for responding to my queries.

I tried the same code in VC++ 6.0 .since i got error there.I proceeded to 
Tornado.Ok. Let me tell what i have tried now.

My host is windows 2k & using MS VC 6.0 compliler(hope thatz not a problem) 
& project is win32 console application.

Tools-Oprions:-
Include Dir: F:\Tornadox86\host\include
Lib Dir: F:\Tornadox86\host\x86-win32\lib

Project settings:
Link->library modules:
apilib.lib
This time no compiler (or) linker error.

But i got apilib.dll is not found in paths :

ex. Winnt/System32
     %WIND_BASE/host/%WIND_HOST_TYPE/bin

But apilib.dll is present in  %WIND_BASE/host/%WIND_HOST_TYPE/bin

Sol:

  so , i copied apilib.dll  to Winnt/System32

Another error popped out :
    tcl .dll is not found in the path eventhough it is present.

Please help your solutions.
********************************************************
sample
#include <iostream.h>
#include "wvapi.h"

int main (int argc, char ** argv)
    {
    if (argc != 2)
        {
        cout << "usage:" << argv [0] << " <logfile.wvr>" << endl;
        exit (1);
        }

    try
        {
        WVEventBase     eb;

        if (eb.load (argv [1]) == OK)
            {
            WVEventBase::iterator       i;

            for (i = eb.begin (); i != eb.end (); ++i)
                {
                WVContext               ctx;
                WVContext::iterator     j;

                ctx = *i;
                for (j = ctx.begin (); j != ctx.end (); ++j)
                    {
                    cout << eb.eventAsString (*j) << endl;
                    }
                }
            }
        else
            {
            cout << "Could not load eventbase " << argv [1] << endl;
            }
        }
    catch (const wv_error &e)
        {
        cout << "WVAPI Error:" << e.what () << " code="
             << e.errorCode () << endl;
        exit (1);
        }

    return 0;
    }

******************************************

Thanks
Nithya

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail

From vxwexplo-errs@csg.lbl.gov  Mon Nov 18 04:03:08 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Mon Nov 18 04:03:10 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Mon Nov 18 04:03:06 PST 2002

        Subject: doc on line about VxWorks
        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: doc on line about VxWorks
        Subject: Re: Large App in Boot ROM
        Subject: VxWorks Download?
        Subject: Re: .text relocation overflow ...
        Subject: Re: ENOBUFS returned by sendmsg()

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: doc on line about VxWorks
Date: Sun, 17 Nov 2002 15:01:31 +0100
From: "sald" <sald@oreka.com>
Organization: 9Telecom
Message-ID: <ar87ih$5q0$1@apollon.grec.isp.9tel.net>

Hello,

Is there anyone who knows where on the WEB I can find documentations about
VxWorks ?

I would like to read the concepts and the difference between VxWorks and
PSOS.

Thanks in advance.

Best regards

SALD

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Sun, 17 Nov 2002 20:09:00 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <ar8t0s$hsn$1@knossos.btinternet.com>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com> <newscache$dltk5h$ky9$1@lnews.actcom.co.il>

> David, my friend, please allow me to disagree -
> the ENOBUF error is in fact a flow control signal
> that tells the application the packet could not be
> delivered down to the interface queue.

Firstly I would expect sendmsg to block, Posix (I know vxworks isn't
posix but) says:

http://www.opengroup.org/onlinepubs/007904975/functions/sendmsg.html

If space is not available at the sending socket to hold the message to 
be transmitted and the socket file descriptor does not have O_NONBLOCK 
set, the sendmsg() function shall block until space is available. If 
space is not available at the sending socket to hold the message to be 
transmitted and the socket file descriptor does have O_NONBLOCK set, the 
sendmsg() function shall fail.

The correct error is EAGAIN or EWOULDBLOCK.

> In my experience, if you dont ignore this errors,
> all packets the application sends succesfully
> do reach teh wire.

But you should have reasonable 'back pressure' flow control
from the ethernet MAC back to your application.

> 
> As to LANs and their packet loss rate, I am not sure
> there exists such a thing as a "properly designed network",
> in reality. Therefore applications should be designed with the
> assumption that packets do get lost, and mittigate that.

Certainly they should not assume that packets are not lost, but it
is reasonable to assume that none are gratuitously discarded.

> But even in a "perfect LAN", there are still wires, which have
> a certain S/N ratio and a certain BER which translates to a
> certain packet loss percentage.

I did some tests a few years ago, the error rate on my LAN segent
was 0.  IIRC I was sending small packets as fast as I could...

> There is no communication
> medium in the world that has a zero BER (Bit Error Rate),
> so however small your BER is, it translates to a certain
> amount of lost packets, due to laws of physics.

But error rates < 1 in 10^8 are achievable. I would expect a
local ethernet segment to be at least that good.

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: doc on line about VxWorks
Date: 17 Nov 2002 20:58:15 -0800
From: vxnerd@rediffmail.com (subbarayan)
Organization: http://groups.google.com/
Message-ID: <f81c4277.0211172058.395b4e46@posting.google.com>
References: <ar87ih$5q0$1@apollon.grec.isp.9tel.net>

dear sald,
I am not sure abt the documents available on net.But as i have worked
on both,I will be able to give u few differences:
1)pSos was product of integrated systems later bought by windriver.
2)pSos has 255 as the highest task priority.where as in vxworks its
reverse.
3)psos uses posix standard 1003.1 where as vxworks follows posix
standars 1003.1b
4)psos has interrupt latency time>4.33 micro secs.where as in vxworks
its less then that.
5)task spawning is possible in vxworks,psos theres no task spwaning.
6)psos takes 4 arguments user supplied,vxworlks takes 10 arguments.
   And there may be few more which i am not able to remember but
others might say.Hope this was helpful to u.
Regards,
s.subbarayan

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Large App in Boot ROM
Date: 17 Nov 2002 13:29:55 -0800
From: brentbergan@yahoo.com (brentb)
Organization: http://groups.google.com/
Message-ID: <2222d8d3.0211171329.2f511acc@posting.google.com>
References: <3DC7F74D.4090702@minn.teradyne.com>

Keith,

I am also using a MPC8245 and have experienced this problem.  For example,
the vxWorks_rom image consists of text, data, and bss.  The text section
consists of romInit.s and romStart.c. During compilation, the actual vxWorks.o
image is converted entirely to .data, hence the use of binArrayStart and
binArrayEnd in the copy process in romStart. In the final link line of the
make file output, there is a flag that specifies where the text section
will be located (-Ttext fff00100), at fff00100.  You can just add a line
to the flags to specify the location of the .data section using the following:
- -Tdata <data location>, i.e. -Tdata ff80000.  Let me know if that helps.

- -Brent

Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DC7F74D.4090702@minn.teradyne.com>...
> We are using a MPC8245 that has a boot vector at fff00100 (~1M) upper rom
> remaining.  Our application is spread over several projects and is
> on the order of 4 Megabytes.  We have significant ROM and RAM
> resources (e.g., 16M / 128M).
> 
> Question:
> --------------------
> 1) Is there an easy way to put the image to be copied from ROM to
> RAM in a different location other than contiguously with the BOOT ROM,
> e.g., boots at FFF00100, but copylongs/unzip copies from FF800000.
> 
> 
> Anyone had any experience with this issue?
> 
> 
> Thanks,
> Keitho

---------------------------

Newsgroups: comp.os.vxworks
Subject: VxWorks Download?
Date: Mon, 18 Nov 2002 09:24:35 +0300
From: " " <smalakhov@alcor.nnov.ru>
Organization: Commercial Information Networks
Message-ID: <ara14q$1626$1@news.kis.ru>

   VxWorks&

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: .text relocation overflow ...
Date: Mon, 18 Nov 2002 16:24:48 +0800
From: "Lewis Kang" <kang@accton.com.tw>
Organization: DCI HiNet
Message-ID: <ara84i$o7b@netnews.hinet.net>
References: <aqdp2q$2b4$1@overload.lbl.gov> <aqdr55$sbk$1@venus.btinternet.com>
Reply-To: "Lewis Kang" <kang@accton.com.tw>

Hi,

  Do you mean we have to write a special linker script  in addition to
the -split-by-reloc  ld option?
  I had tried to search the archive using the keyword: "relocation", but
it's hard to find the script you mentioned. (I don't know how to search the
whole archive at once. Is there a way for searching the whole archive?)
  Could you tell me how to locate the script which you posted before? Using
which keyword? Or could you tell me the possible time you posted that
script?
  Thanks in advance!

/Lewis

"David Laight" <david@spam.me.l8s.co.uk>
???????:aqdr55$sbk$1@venus.btinternet.com...
> kang@accton.com.tw wrote:
> > Dear All,
> >
> > ? We are using Tornado 2.0/VxWorks5.4 for ARM7 CPU taget
> > ? We encouter .text relocation overflow issue.
> > ? It seems that Tornado 2.0/VxWorks5.4 for ARM7 can only produce COFF
> > format and COFF can't have more than 65535 relocations in a session.
> > ? We have tried the -split-by-reloc ld option, but it doesn't help.
>
> -split-by-reloc SHOULD help, you do need to put it in the correct place
> and supply [1] a linker script for the subsequent link.
> I don't have access to the script at the moment, search the newsgroup
> archive I've posted it before.
>
> You will have trouble if a single .o files has too many relocations.
>
> [1] I generated it on the fly in the makefile.
>
> David
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Mon, 18 Nov 2002 11:14:30 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$wplr5h$4f1$1@lnews.actcom.co.il>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com> <newscache$dltk5h$ky9$1@lnews.actcom.co.il> <ar8t0s$hsn$1@knossos.btinternet.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:ar8t0s$hsn$1@knossos.btinternet.com...
>
> > David, my friend, please allow me to disagree -
> > the ENOBUF error is in fact a flow control signal
> > that tells the application the packet could not be
> > delivered down to the interface queue.
>
> Firstly I would expect sendmsg to block, Posix (I know vxworks isn't
> posix but) says:
>
> http://www.opengroup.org/onlinepubs/007904975/functions/sendmsg.html
>
> If space is not available at the sending socket to hold the message to
> be transmitted and the socket file descriptor does not have O_NONBLOCK
> set, the sendmsg() function shall block until space is available. If
> space is not available at the sending socket to hold the message to be
> transmitted and the socket file descriptor does have O_NONBLOCK set, the
> sendmsg() function shall fail.
>
> The correct error is EAGAIN or EWOULDBLOCK.
>

You may be right there, this could be a bug in the VxWorks
sockets implementation, which is dated before the POSIX
standards I think.

> > In my experience, if you dont ignore this errors,
> > all packets the application sends succesfully
> > do reach teh wire.
>
> But you should have reasonable 'back pressure' flow control
> from the ethernet MAC back to your application.
>
This is indeed acheivable. Good L-2 switches use the "collision"
signal to back pressure the sender when in half-duplex mode,
while some newer MACs support the PAUSE flow control frames in
hardware, so flow control is there for you to use at the MAC level,
which will eventually translate unto ENOBUFS for the application,
and that sounds good enough of a flow control to me.

> >
> > As to LANs and their packet loss rate, I am not sure
> > there exists such a thing as a "properly designed network",
> > in reality. Therefore applications should be designed with the
> > assumption that packets do get lost, and mittigate that.
>
> Certainly they should not assume that packets are not lost, but it
> is reasonable to assume that none are gratuitously discarded.

Layer-2 errors are simply discarded, and there is no way to inform
the sends of that. Also, when a Layer-2 switch does not have
proper flow control, packets are discarded simply due to congestion.
This is specifically notable when devices of different rates are connected
to the same switch (i.e. some are 10mbps while others are 100Mbos).

>
> > But even in a "perfect LAN", there are still wires, which have
> > a certain S/N ratio and a certain BER which translates to a
> > certain packet loss percentage.
>
> I did some tests a few years ago, the error rate on my LAN segent
> was 0.  IIRC I was sending small packets as fast as I could...
>
I think that large packets are better suitted to this kind of test,
and a fairly long test period is required too.

> > There is no communication
> > medium in the world that has a zero BER (Bit Error Rate),
> > so however small your BER is, it translates to a certain
> > amount of lost packets, due to laws of physics.
>
> But error rates < 1 in 10^8 are achievable. I would expect a
> local ethernet segment to be at least that good.
>
Ok, assuming the BER is 1e-8, and an interface speed at 100Mbps
(that is 1e+8 bits/sec), at a 100% interface utilization, on ebit error
is expected every second on the average.
I think that the actual BER on Cat-5e cable at 100Mbps is better -
wireless connections often specify a 1e-6 BER, so I would expect a
Cat-5 cable perform at least 1e-12 (need to google a bit to find
specific test results), but an 1e-12 BER would result in a single
bit error every 3 hours. Also, BEr would depend on a wide range
of factors like cable length, connectro and jumper impedance matching.

Still, one would conclude that never-ever should an application assume
that no packets are lost on a local LAN segment.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Mon Nov 18 23:17:54 2002
From: "Nithya P" <nithyap490@hotmail.com>
Date: Mon Nov 18 23:17:56 PST 2002
Subject: Errors while Building Vxworks with system defined timestamping

Hi all,
   When i downloade the following code, i got unresolved errors for 
systimestamping calls. So , I included system defined timestamping of 
windview component in Vxworks tab of Build spec.

I'm getting errors which i had pasted below:Please help me to solve it.

#include <vxworks.h>
#include "string.h"
#include "stdio.h"
#include "wvLib.h"
#include "taskLib.h"
#include "drv/timer/timerDev.h"
#include "wvTmrLib.h"
#include "rBuffLib.h"
#include "wdb/wdbVioLib.h"
#include "private/wvFileUploadPathLibP.h"
#include "private/wvTsfsUploadPathLibP.h"
#include "private/funcBindP.h"
#include "private/seqDrvP.h"

extern FUNCPTR	_func_wvOnUploadPathCreate;
extern FUNCPTR	_func_wvOnUploadPathClose;

extern int wvArgHtons;
extern char * wvLogMsgString1;
extern char * wvLogMsgString2;

void testView(void)
{

    wvLibInit();                       /* low-level kernel instrumentation 
needed by windview */
    
/*wvTmrRegister((UINTFUNCPTR)seqStamp,(UINTFUNCPTR)seqStampLock,(FUNCPTR)seqEnable,(FUNCPTR)seqDisable,(FUNCPTR)seqConnect,(UINTFUNCPTR) 
seqPeriod,(UINTFUNCPTR) seqFreq);*/ /* no timestamping */
	wvTmrRegister (sysTimestamp,
                   sysTimestampLock,
                   sysTimestampEnable,
                   sysTimestampDisable,
                   sysTimestampConnect,
                   sysTimestampPeriod,
                   sysTimestampFreq);
    rBuffLibInit ();                    /* windview 2.0 ring of buffers for 
event logging  */
    wdbTsfsDrv ("/tgtsvr");             /* virtual file system based on the 
WDB agent */
  /*  usrWvTsfsUploadPathInit ();  */       /* initialize path for the 
upload through TSFS socket  */
    /*usrWvFileUploadPathInit (); */        /* initialize path for the 
upload to file  */

    _func_wvOnUploadPathCreate = (FUNCPTR) fileUploadPathCreate;
    _func_wvOnUploadPathClose = (FUNCPTR) fileUploadPathClose;
    wvArgHtons = 0;
    wvLogMsgString1 = "fname=";
    wvLogMsgString2 = "flag=";

    fileUploadPathLibInit ();

}

Errors on building:

wtxtcl F:\Tornadox86\host\src\hutils\configGen.tcl 
F:\Tornadox86\target\proj\TestCases\WVi
ew\WindView.wpj
ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32 
-U__WIN32 -U__WIN32__
-U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-pop 
-Wall -DRW_M
ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView 
-IF:\Tornadox86\targe
t\config\simpc -IF:\Tornadox86\target\config\comps\src 
-IF:\Tornadox86\target\h -If:\torna
dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD  
-c F:\Tornadox8
6\target\config\simpc\sysLib.c
ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32 
-U__WIN32 -U__WIN32__
-U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-pop 
-Wall -DRW_M
ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView 
-IF:\Tornadox86\targe
t\config\simpc -IF:\Tornadox86\target\config\comps\src 
-IF:\Tornadox86\target\h -If:\torna
dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD  
-c F:\Tornadox8
6\target\proj\TestCases\WView\prjConfig.c
ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32 
-U__WIN32 -U__WIN32__
-U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-pop 
-Wall -DRW_M
ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView 
-IF:\Tornadox86\targe
t\config\simpc -IF:\Tornadox86\target\config\comps\src 
-IF:\Tornadox86\target\h -If:\torna
dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD  
-c F:\Tornadox8
6\target\proj\TestCases\WView\linkSyms.c
vxrm F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst
Generating F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst...
ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32 
-U__WIN32 -U__WIN32__
-U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-pop 
-Wall -DRW_M
ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView 
-IF:\Tornadox86\targe
t\config\simpc -IF:\Tornadox86\target\config\comps\src 
-IF:\Tornadox86\target\h -If:\torna
dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD  
-c F:\Tornadox8
6\target\config\comps\src\version.c
ccsimpc -BF:\Tornadox86\host\x86-win32\lib\gcc-lib\ -U__WINNT -UWIN32 
-U__WINNT__ -UWINNT
-U__MINGW32__ -U_WIN32 -U__WIN32 -U__WIN32__ -U__WIN32 -nostdlib -r -Wl,-X \
    -Wl,@F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst  version.o  
F:\Tornadox86\t
arget\lib\libSIMNTgnuvx.a -o partialImage.o
nmsimpc -g partialImage.o 
@F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst | wtxtcl
F:\Tornadox86\host\src\hutils\munch.tcl -asm simpc > ctdt.c
ccsimpc -c -fdollars-in-identifiers -U__WINNT -UWIN32 -U__WINNT__ -UWINNT 
-U__MINGW32__ -U
_WIN32 -U__WIN32 -U__WIN32__ -U__WIN32 -mpentium -ansi -nostdinc -g 
-nostdlib -fno-builtin
-fno-defer-pop -Wall -DRW_MULTI_THREAD -D_REENTRANT 
-IF:\Tornadox86\target\proj\TestCases
\WView -IF:\Tornadox86\target\config\simpc 
-IF:\Tornadox86\target\config\comps\src -IF:\To
rnadox86\target\h -If:\tornadox86\host\include 
-IF:\Tornadox86\target\src\drv -DCPU=SIMNT
-DPRJ_BUILD  ctdt.c -o ctdt.o
ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32 
-U__WIN32 -U__WIN32__
-U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-pop 
-Wall -DRW_M
ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView 
-IF:\Tornadox86\targe
t\config\simpc -IF:\Tornadox86\target\config\comps\src 
-IF:\Tornadox86\target\h -If:\torna
dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD  
-c F:\Tornadox8
6\target\config\comps\src\dataSegPad.c
ldsimpc --subsystem=windows -e _WinMainCRTStartup 
F:\Tornadox86\host\x86-win32\i386-pc-min
gw32\lib\crt1.o \
	dataSegPad.o partialImage.o ctdt.o -o vxWorks
partialImage.o: In function `_tfd':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1ca9): undefined 
reference to `sysTi
mestampFreq'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cae): undefined 
reference to `sysTi
mestampPeriod'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cb3): undefined 
reference to `sysTi
mestampConnect'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cb8): undefined 
reference to `sysTi
mestampDisable'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cbd): undefined 
reference to `sysTi
mestampEnable'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cc2): undefined 
reference to `sysTi
mestampLock'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cc7): undefined 
reference to `sysTi
mestamp'
partialImage.o: In function `_tfUl':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2190): undefined 
reference to `WVEve
ntBase::WVEventBase(Tcl_Interp *)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x21b0): undefined 
reference to `WVEve
ntBase::~WVEventBase(void)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x21df): undefined 
reference to `WVEve
ntBase::load(char const *, int (*)(void *, int, int), void *, __sFILE *)'
partialImage.o: In function `_tfUx':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x21fc): undefined 
reference to `WVEBI
ter::WVEBIter(CEventBase const *, unsigned int)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2212): undefined 
reference to `WVEve
ntBase::begin(void) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2228): undefined 
reference to `WVEBI
ter::operator=(WVEBIter const &)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2240): undefined 
reference to `WVEve
ntBase::end(void) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2256): undefined 
reference to `WVEBI
ter::operator!=(WVEBIter const &) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x22b6): undefined 
reference to `WVCtx
Iter::WVCtxIter(CContext const *, unsigned int)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x22cc): undefined 
reference to `WVEBI
ter::operator*(void) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2313): undefined 
reference to `WVCon
text::operator=(WVContext const &)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2363): undefined 
reference to `WVCtx
Iter::operator=(WVCtxIter const &)'
partialImage.o: In function `_tfUs':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2391): undefined 
reference to `WVCtx
Iter::operator!=(WVCtxIter const &) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x23b4): undefined 
reference to `WVCtx
Iter::operator*(void) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x23cc): undefined 
reference to `WVEve
ntBase::eventAsString(WVEvent const &, char const *) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x23f8): undefined 
reference to `WVCtx
Iter::operator++(void)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2430): undefined 
reference to `WVEBI
ter::operator++(void)'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2493): undefined 
reference to `WVEve
ntBase::~WVEventBase(void)'
partialImage.o: In function `$_16__ptmf_type_info':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x27e5): undefined 
reference to `WVCon
text::size(void) const'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x27f4): undefined 
reference to `WVCtx
Iter::WVCtxIter(CContext const *, unsigned int)'
partialImage.o: In function `_tf16__func_type_info':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x281e): undefined 
reference to `WVCtx
Iter::WVCtxIter(CContext const *, unsigned int)'
partialImage.o: In function `_tf16__attr_type_info':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28dd): undefined 
reference to `sysTi
mestampFreq'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28e2): undefined 
reference to `sysTi
mestampPeriod'
partialImage.o: In function `$_16__attr_type_info':
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28e7): undefined 
reference to `sysTi
mestampConnect'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28ec): undefined 
reference to `sysTi
mestampDisable'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28f1): undefined 
reference to `sysTi
mestampEnable'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28f6): undefined 
reference to `sysTi
mestampLock'
\wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28fb): undefined 
reference to `sysTi
mestamp'
make: *** [vxWorks] Error 0x1

Done.

Thanks
Nithya

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

From vxwexplo-errs@csg.lbl.gov  Tue Nov 19 04:03:23 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Tue Nov 19 04:03:24 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Tue Nov 19 04:03:20 PST 2002

        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: The interface between MPC860 and asynchronous FIFO
        Subject: Re: The interface between MPC860 and asynchronous FIFO
        Subject: Re: Bypassing parts of the stack
        Subject: Re: .text relocation overflow ...
        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: ENOBUFS returned by sendmsg()
        Subject: Re: Large App in Boot ROM
        Subject: newbie   VxWorks on cable modem
        Subject: Re: Large App in Boot ROM
        Subject: NEWS:  McObject Adds XML Support to eXtremeDB In-Memory Database
        Subject: Re: Large App in Boot ROM
        Subject: Re: Running a sample program creates unresolved errors..how to rectify
        Subject: How many byte do you know VxWorks BSP Image size?
        Subject: Re: How many byte do you know VxWorks BSP Image size?
        Subject: Re: wrapping printf()
        Subject: test
        Subject: Re: How many byte do you know VxWorks BSP Image size?
        Subject: Re: How many byte do you know VxWorks BSP Image size?
        Subject: VxWorks V5.4+ gcc2.95 ?
        Subject: Re: VxWorks Download?

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Thu, 14 Nov 2002 14:48:56 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <ar0d4n$19r$1@helle.btinternet.com>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk>

King L wrote:
> When I send lots of packets via sendmsg() in vxWorks IP, send message
> returns ENOBUFS.
> If I have a delay between sends it is OK.
> 
> I have increased the number of buffers NUM_64, NUM_128, NUM_SYS_64,
> NUM_SYS_128 etc
> in netBufLib.h file. When I see the ENOBUFS error I check
> netStackDataPoolShow() and netStackSysPoolShow() and there are no "failed to
> find space" errors.

Are there any free buffers?  Don't rely on the error counts being correct!
There is also a buffer pool allocated by the ethernet driver (ptr in
END structure).

Try calling netStackDataPoolShow() when you get ENOBUFS - should
show whether that pool is out of data, or if the problem is elsewhere.

IIRC there are 'problems' in that there is no local flow control
for transmitted datagrams, so if you are sending a lot back to back
some will be discarded before reaching the media.  IMHO this is
a serious bug, the error rate of a (correctly built) local LAN
segment is very close to zero so it is actually reasonable to
assume that almost all datagrams that leave one system will
(in the absence of bridges and routers) be detected by the target
system - if only as a lost packet because if a lack of receive
buffers.

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: The interface between MPC860 and asynchronous FIFO
Date: 14 Nov 2002 08:41:43 -0800
From: rick@cyclone.com (Richard Nardone)
Organization: http://groups.google.com/
Message-ID: <29b153d9.0211140841.660b8742@posting.google.com>
References: <f373d5a6.0211140301.2849f362@posting.google.com>

Take a look at the addressing mode being utilized.  If you are using
Block Address Translation, then you are writing to an address not
covered by one of the four DBAT regions.  The error you are getting
would be consistent with this condition.

   Richard Nardone
   Cyclone Microsystems

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: The interface between MPC860 and asynchronous FIFO
Date: 18 Nov 2002 05:19:21 -0800
From: microtnt@sina.com (MicorTNT)
Organization: http://groups.google.com/
Message-ID: <f373d5a6.0211180519.76ce948e@posting.google.com>
References: <f373d5a6.0211140301.2849f362@posting.google.com> <29b153d9.0211140841.660b8742@posting.google.com> <488e459a.0211141657.42f15979@posting.google.com> <29b153d9.0211150900.33215478@posting.google.com>

Thanks to John and Richard Nardone again!
I add the FIFO address into the structure sysPhysMemDesc[] in syslib.c
and the quetion is resolved.
In Vxworks Guide P291:I/O devices and memory not already included in
the structure must also be mapped and made noncacheable.
In the shell, there is no problem to read/write FIFO.

But new question comes:
In the Hyperterminal, the command 'd 0x***' displays the memory
started by 0x***. When I use it to display the FIFO data, it works
well. When I display the memory following FIFO address(this address is
not mapped in memory controller.),It still displays data with 0x0000?
but I think Machine check exception should happen.
This case in shell would not happen!
why???

rick@cyclone.com (Richard Nardone) wrote in message news:<29b153d9.0211150900.33215478@posting.google.com>...
> john_94501@yahoo.com (John) wrote in message news:<488e459a.0211141657.42f15979@posting.google.com>...
> > Hello,
> > 
> > I don't believe that the 860 devices have BAT registers... they do
> > have an MMU though, so if the address that you are trying to access
> > was not covered by the descriptions in sysPhysMemDesc[] in your BSP,
> > then you will get a data access error every time you try to read or
> > write that address.
> > 
> > HTH,
> > 
> > John...
> 
> 
>   Hi,
> 
>    I was incorrect about the MPC860 having BATs.  The registers you
> are interested are in the DMMU section, DTLBs as described in Chapter
> 9 of the MPC860 user's manual.  I would follow John's advice here.
> 
>    The 8260 can use BATs as defined in the PowerPC Programming
> Environments for 32-Bit Microprocessors.
> 
>    The basic point is that even though you have a FIFO interfaced to
> the 860 memory controller, you need to make sure your progam has that
> address covered by the MMU, if address translation is enabled.
> 
>    Regards,
> 
> 
>    Richard Nardone
>    Cyclone Microsystems

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Bypassing parts of the stack
Date: Fri, 15 Nov 2002 16:27:56 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$98gm5h$fdc$1@lnews.actcom.co.il>
References: <MPG.183ec9d8a5dfe794989680@news.si.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"David Cooper" <cooper_dave@si.com> wrote in message
news:MPG.183ec9d8a5dfe794989680@news.si.com...
> I have an Ethernet board which implements IP and UDP on board.  I still
> want to be able to use other higher level protocols which are available
> in the Wind River stack.  Is there a way to bind my driver through the
> MUX interface to the higher level protocols ?
>
Yes, there is a way to do this, but not using the MUX API.

What you essentially need is to hook into the BSD sockets layer,
which is unfortunately undocumented in VxWorks, so you would need
either some of the SENS sources, or another alternative TCP/IP stack
which has already been ported to VxWorks to borrow from.

I recall one such alternative stack from Hwa Jin Bae (a.k.a. peaceful star)
who's done the orignal BSD 4.3 net stack ported into VxWorks many years ago.
- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: .text relocation overflow ...
Date: Mon, 18 Nov 2002 13:55:45 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <ararh0$dna$1@knossos.btinternet.com>
References: <aqdp2q$2b4$1@overload.lbl.gov> <aqdr55$sbk$1@venus.btinternet.com> <ara84i$o7b@netnews.hinet.net>

Lewis Kang wrote:
> Hi,
> 
>   Do you mean we have to write a special linker script  in addition to
> the -split-by-reloc  ld option?
>   I had tried to search the archive using the keyword: "relocation", but
> it's hard to find the script you mentioned. (I don't know how to search the
> whole archive at once. Is there a way for searching the whole archive?)
>   Could you tell me how to locate the script which you posted before? Using
> which keyword? Or could you tell me the possible time you posted that
> script?

Just go into google, into groups and select comp.os.vxworks, then
'search only in comp.os.vxworks' for split-by=reloc.  This will show:

http://groups.google.co.uk/groups?q=split-by-reloc+group:comp.os.vxworks&hl=en&lr=&ie=UTF-8&selm=200011081510.PAA13805%40dsl-2.tadpole.co.uk&rnum=9

which shows the relevant bit of the makefile.

	$(LD) --verbose >ldscript
         @ adds="`objdumparm -h vxWorks.tmp |grep '.text[0-9]'| \
                 while read idx segment rest; \
                 do echo \"  }\n  $$segment :\n  {\n    *($$segment)\"; \
                 done;`"; \
             IFS=;echo 
"1,/^==/d\n/etext/\ni\n$$adds\n.\n/data/\n.s/0x4.*:/:/\n/^
==/\nd\nw\nq"| \
                 ed ldscript >/dev/null
         $(LD) -T ldscript $(LDFLAGS) -e $(SYS_ENTRY) $(LD_LOW_FLAGS) \
             -o vxWorks dataSegPad.o vxWorks.tmp ctdt.o

IIRC the previous line is the ld -r one...

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Mon, 18 Nov 2002 14:08:30 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <aras8t$hdr$1@helle.btinternet.com>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com> <newscache$dltk5h$ky9$1@lnews.actcom.co.il> <ar8t0s$hsn$1@knossos.btinternet.com> <newscache$wplr5h$4f1$1@lnews.actcom.co.il>

> You may be right there, this could be a bug in the VxWorks
> sockets implementation, which is dated before the POSIX
> standards I think.

Quite probably, but I don't recall us changing that when standardising
sockets for X/Open...

> This is indeed acheivable. Good L-2 switches use the "collision"
> signal to back pressure the sender when in half-duplex mode,
> while some newer MACs support the PAUSE flow control frames in
> hardware, so flow control is there for you to use at the MAC level,
> which will eventually translate unto ENOBUFS for the application,
> and that sounds good enough of a flow control to me.

And if your are inside a collision domain (eg just coax or hubs)
there there is never a problem.

> Layer-2 errors are simply discarded, and there is no way to inform
> the sends of that. Also, when a Layer-2 switch does not have
> proper flow control, packets are discarded simply due to congestion.
> This is specifically notable when devices of different rates are connected
> to the same switch (i.e. some are 10mbps while others are 100Mbos)

Agreed, I did say that intermediate switches/routers mustn't be
discarding packets.  Some early switches were particularly broken
and would discard packets if the target interface was busy!
Similarly some bridge/routers that used the AMD lance in promiscuous
mode would never (ever) send a packet onto a 99% busy LAN.

> I think that large packets are better suitted to this kind of test,
> and a fairly long test period is required too.

I probably left it running overnight (at least)...

>>But error rates < 1 in 10^8 are achievable. I would expect a
>>local ethernet segment to be at least that good.
>>
> 
> Ok, assuming the BER is 1e-8, and an interface speed at 100Mbps
> (that is 1e+8 bits/sec), at a 100% interface utilization, on ebit error
> is expected every second on the average.

I was probably thinking of a packet error rate.

> I think that the actual BER on Cat-5e cable at 100Mbps is better -
> wireless connections often specify a 1e-6 BER, so I would expect a
> Cat-5 cable perform at least 1e-12 (need to google a bit to find
> specific test results), but an 1e-12 BER would result in a single
> bit error every 3 hours. Also, BEr would depend on a wide range
> of factors like cable length, connectro and jumper impedance matching.

Yes, you do need to have good quality cables.  UTP probably isn't
as critical as coax though.
> 
> Still, one would conclude that never-ever should an application assume
> that no packets are lost on a local LAN segment.

Indeed, but OTOH they should also not expect them to be discarded.
The error recovery of most protocols doesn't work well in the presence
of large numbers of lost packets.  I have made protocols work in some
fairly horrid senarios (usually system with 8bit ISA ethernet cards
with 4k of buffer space....) but it is quite tricky, non-intuitive,
and best avoided if possible.

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Mon, 18 Nov 2002 16:31:06 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$kd0s5h$4x1$1@lnews.actcom.co.il>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com> <newscache$dltk5h$ky9$1@lnews.actcom.co.il> <ar8t0s$hsn$1@knossos.btinternet.com> <newscache$wplr5h$4f1$1@lnews.actcom.co.il> <aras8t$hdr$1@helle.btinternet.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:aras8t$hdr$1@helle.btinternet.com...
>
> > You may be right there, this could be a bug in the VxWorks
> > sockets implementation, which is dated before the POSIX
> > standards I think.
>
> Quite probably, but I don't recall us changing that when standardising
> sockets for X/Open...
>
> > This is indeed acheivable. Good L-2 switches use the "collision"
> > signal to back pressure the sender when in half-duplex mode,
> > while some newer MACs support the PAUSE flow control frames in
> > hardware, so flow control is there for you to use at the MAC level,
> > which will eventually translate unto ENOBUFS for the application,
> > and that sounds good enough of a flow control to me.
>
> And if your are inside a collision domain (eg just coax or hubs)
> there there is never a problem.
>
> > Layer-2 errors are simply discarded, and there is no way to inform
> > the sends of that. Also, when a Layer-2 switch does not have
> > proper flow control, packets are discarded simply due to congestion.
> > This is specifically notable when devices of different rates are
connected
> > to the same switch (i.e. some are 10mbps while others are 100Mbos)
>
> Agreed, I did say that intermediate switches/routers mustn't be
> discarding packets.  Some early switches were particularly broken
> and would discard packets if the target interface was busy!
> Similarly some bridge/routers that used the AMD lance in promiscuous
> mode would never (ever) send a packet onto a 99% busy LAN.
>
> > I think that large packets are better suitted to this kind of test,
> > and a fairly long test period is required too.
>
> I probably left it running overnight (at least)...
>
> >>But error rates < 1 in 10^8 are achievable. I would expect a
> >>local ethernet segment to be at least that good.
> >>
> >
> > Ok, assuming the BER is 1e-8, and an interface speed at 100Mbps
> > (that is 1e+8 bits/sec), at a 100% interface utilization, on ebit error
> > is expected every second on the average.
>
> I was probably thinking of a packet error rate.
>
> > I think that the actual BER on Cat-5e cable at 100Mbps is better -
> > wireless connections often specify a 1e-6 BER, so I would expect a
> > Cat-5 cable perform at least 1e-12 (need to google a bit to find
> > specific test results), but an 1e-12 BER would result in a single
> > bit error every 3 hours. Also, BEr would depend on a wide range
> > of factors like cable length, connectro and jumper impedance matching.
>
> Yes, you do need to have good quality cables.  UTP probably isn't
> as critical as coax though.
> >
> > Still, one would conclude that never-ever should an application assume
> > that no packets are lost on a local LAN segment.
>
> Indeed, but OTOH they should also not expect them to be discarded.
> The error recovery of most protocols doesn't work well in the presence
> of large numbers of lost packets.  I have made protocols work in some
> fairly horrid senarios (usually system with 8bit ISA ethernet cards
> with 4k of buffer space....) but it is quite tricky, non-intuitive,
> and best avoided if possible.
>
> David
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Mon, 18 Nov 2002 16:35:31 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$xk0s5h$7x1$1@lnews.actcom.co.il>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com> <newscache$dltk5h$ky9$1@lnews.actcom.co.il> <ar8t0s$hsn$1@knossos.btinternet.com> <newscache$wplr5h$4f1$1@lnews.actcom.co.il> <aras8t$hdr$1@helle.btinternet.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:aras8t$hdr$1@helle.btinternet.com...
[snip]
> >
> > Still, one would conclude that never-ever should an application assume
> > that no packets are lost on a local LAN segment.
>
> Indeed, but OTOH they should also not expect them to be discarded.
> The error recovery of most protocols doesn't work well in the presence
> of large numbers of lost packets.  I have made protocols work in some
> fairly horrid senarios (usually system with 8bit ISA ethernet cards
> with 4k of buffer space....) but it is quite tricky, non-intuitive,
> and best avoided if possible.

The recovery for lost packets should work well relative to the "expected"
packet loss rate (which in turn does depend on avg packet size).
But all should have reasonably well tested recovery mechaism, especially
now with the 802.11b WLANs popping up like mushrooms, where BER is
in the 1e-6 range (after FEC effect).

There are really nice tools these days for serious people to test their
wares,
before they hit the market, for example, SHUNRA have a network simulator
that can be instructed to emulate any kind of BER, Delay, Jitter and other
parameters, and be sure it works well before it hits the market.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ENOBUFS returned by sendmsg()
Date: Mon, 18 Nov 2002 15:10:59 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <aravu2$k35$1@knossos.btinternet.com>
References: <ar0bfl$c01$1$8302bc10@news.demon.co.uk> <ar0d4n$19r$1@helle.btinternet.com> <newscache$dltk5h$ky9$1@lnews.actcom.co.il> <ar8t0s$hsn$1@knossos.btinternet.com> <newscache$wplr5h$4f1$1@lnews.actcom.co.il> <aras8t$hdr$1@helle.btinternet.com> <newscache$xk0s5h$7x1$1@lnews.actcom.co.il>

> But all should have reasonably well tested recovery mechaism, especially
> now with the 802.11b WLANs popping up like mushrooms, where BER is
> in the 1e-6 range (after FEC effect).

Indeed, and the error rate of 802.11b is such that the recovery
algorithms of TCP implementations probably need looking at.
The losses on 802.11b are not helped by the fact that it is having
to do rate adaption as well.  I gave up using the the wireless card
under vxworks for NFS (vxworks server) because the error rate was
so high (probably confounded by writing to EEPROM).

> There are really nice tools these days for serious people to test their
> wares,
> before they hit the market, for example, SHUNRA have a network simulator
> that can be instructed to emulate any kind of BER, Delay, Jitter and other
> parameters, and be sure it works well before it hits the market.

I've not seen these, but they will only simulate the errors that have
been thought of.  It is the unknown errors that cause the problems.
Minimising the recovery time under adverse conditions isn't easy!

I suspect that we actually agree :-)

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Large App in Boot ROM
Date: 18 Nov 2002 08:41:29 -0800
From: brentbergan@yahoo.com (brentb)
Organization: http://groups.google.com/
Message-ID: <2222d8d3.0211180841.7f841746@posting.google.com>
References: <3DC7F74D.4090702@minn.teradyne.com> <2222d8d3.0211171329.2f511acc@posting.google.com>

Keith,

I forgot to add one more thing to the message below. You will have to
also change the call in romStart:

Original call:

    /* Original WindRiver call */
    copyLongs ((UINT *)ROM_DATA(binArrayStart),
        (UINT *)UNCACHED(RAM_DST_ADRS),
        (&binArrayEnd - binArrayStart) / sizeof (long));
   
Change to:

    copyLongs ((UINT *)binArrayStart,
        (UINT *)UNCACHED(RAM_DST_ADRS),
        (&binArrayEnd - binArrayStart) / sizeof (long));

If you work through the ROM_DATA macro, you will see why this is
necessary.  You really just need to copy from binArrayStart to RAM_DST_ADRS.
Hope this helps...

- -Brent 

brentbergan@yahoo.com (brentb) wrote in message news:<2222d8d3.0211171329.2f511acc@posting.google.com>...
> Keith,
> 
> I am also using a MPC8245 and have experienced this problem.  For example,
> the vxWorks_rom image consists of text, data, and bss.  The text section
> consists of romInit.s and romStart.c. During compilation, the actual vxWorks.o
> image is converted entirely to .data, hence the use of binArrayStart and
> binArrayEnd in the copy process in romStart. In the final link line of the
> make file output, there is a flag that specifies where the text section
> will be located (-Ttext fff00100), at fff00100.  You can just add a line
> to the flags to specify the location of the .data section using the following:
> -Tdata <data location>, i.e. -Tdata ff80000.  Let me know if that helps.
> 
> -Brent
> 
> Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DC7F74D.4090702@minn.teradyne.com>...
> > We are using a MPC8245 that has a boot vector at fff00100 (~1M) upper rom
> > remaining.  Our application is spread over several projects and is
> > on the order of 4 Megabytes.  We have significant ROM and RAM
> > resources (e.g., 16M / 128M).
> > 
> > Question:
> > --------------------
> > 1) Is there an easy way to put the image to be copied from ROM to
> > RAM in a different location other than contiguously with the BOOT ROM,
> > e.g., boots at FFF00100, but copylongs/unzip copies from FF800000.
> > 
> > 
> > Anyone had any experience with this issue?
> > 
> > 
> > Thanks,
> > Keitho

---------------------------

Newsgroups: comp.os.vxworks
Subject: newbie   VxWorks on cable modem
Date: Mon, 18 Nov 2002 18:03:19 +0100
From: "Sorin" <sorinucu@yahoo.com>
Organization: Wanadoo, l'internet avec France Telecom
Message-ID: <arb6fp$4q4$1@news-reader11.wanadoo.fr>

I have a Com21 cable modem with VxWorks os.
Where can i get some docs on it?
Thx

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Large App in Boot ROM
Date: Mon, 18 Nov 2002 16:12:07 -0600
From: Keith Obrien <obrienk.spam@minn.teradyne.com>
Message-ID: <3DD965B7.7000207@minn.teradyne.com>
References: <3DC7F74D.4090702@minn.teradyne.com> <2222d8d3.0211171329.2f511acc@posting.google.com>

Brent,

Thanks, very helpful.  Caused me to look more closely at the defs.bsp
file... Strange, looks like they sort of have the problem surround automagically,
but not entirely, apparently:

. . .
## bsp flags

LD_LOW_FLAGS    = -Ttext $(RAM_LOW_ADRS)
LD_HIGH_FLAGS   = -Ttext $(RAM_HIGH_ADRS)
RES_LOW_FLAGS   = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_LOW_ADRS)
RES_HIGH_FLAGS  = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_HIGH_ADRS)

ROM_ENTRY       = _romInit
SYS_ENTRY       = _sysInit
USR_ENTRY       = _usrInit

LDFLAGS         = -X -N
LD_PARTIAL_FLAGS= -X -r
. . .

It seems to me that the RES_LOW_FLAGS is more or less approprate, as I want
the code loaded to the RAM at that address, but I wonder if I can burn the
Flash with the ice as is... short of two seperate
burns with the VisionICE, with two seperate bias and offset values.

We recently had to upgrade to a newer gnu compiler to support >32M
jumps and have also seen problems with the elfHex (bin to hex) program,
any issues you've noticed?

Thanks Again,
- -Keith

brentb wrote:

> Keith,
> 
> I am also using a MPC8245 and have experienced this problem.  For example,
> the vxWorks_rom image consists of text, data, and bss.  The text section
> consists of romInit.s and romStart.c. During compilation, the actual vxWorks.o
> image is converted entirely to .data, hence the use of binArrayStart and
> binArrayEnd in the copy process in romStart. In the final link line of the
> make file output, there is a flag that specifies where the text section
> will be located (-Ttext fff00100), at fff00100.  You can just add a line
> to the flags to specify the location of the .data section using the following:
> -Tdata <data location>, i.e. -Tdata ff80000.  Let me know if that helps.
> 
> -Brent
> 
> Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DC7F74D.4090702@minn.teradyne.com>...
> 
>>We are using a MPC8245 that has a boot vector at fff00100 (~1M) upper rom
>>remaining.  Our application is spread over several projects and is
>>on the order of 4 Megabytes.  We have significant ROM and RAM
>>resources (e.g., 16M / 128M).
>>
>>Question:
>>--------------------
>>1) Is there an easy way to put the image to be copied from ROM to
>>RAM in a different location other than contiguously with the BOOT ROM,
>>e.g., boots at FFF00100, but copylongs/unzip copies from FF800000.
>>
>>
>>Anyone had any experience with this issue?
>>
>>
>>Thanks,
>>Keitho
>>

---------------------------

Newsgroups: comp.os.vxworks
Subject: NEWS:  McObject Adds XML Support to eXtremeDB In-Memory Database
Date: Mon, 18 Nov 2002 14:18:28 -0800
From: "Information" <info@mcobject.com>
Organization: McObject
Message-ID: <3dd969a5$1_1@news.foxinternet.com>
Reply-To: "Information" <info@mcobject.com>

Issaquah, WA-November 18, 2002-Responding to developers' increased interest
in realizing the benefits of XML (eXtensible Markup Language) for embedded
systems, McObject has released an XML interface for its eXtremeDB in-memory
database system. The eXtremeDB XML interface enables seamless data exchange
between eXtremeDB and other XML-enabled systems, and provides a simplified
means for updating underlying database structures.

McObject has created a freely downloadable example program demonstrating the
integration of the eXtremeDB embedded XML interface and Web Services through
SOAP interfaces.  Interested developers can download the demonstration
program and implementation files at http://www.mcobject.com.

The eXtremeDB XML interface enables the export of database data in XML
format as well as importing XML data into the database. Expressed in XML
form, data is easily shared between eXtremeDB-based embedded systems and the
outside world, in an efficient, standards-based fashion.

In contrast to some databases that store data as XML, eXtremeDB XML supports
the W3C XML specification but stores its contents in the eXtremeDB binary
format, applying eXtremeDB's efficient in-memory storage methodology to the
imported data. Stored objects retain eXtremeDB's compact layout, as well as
its fast and predictable search methods and updates. With eXtremeDB XML, the
database still reads and writes XML in the context of transactions, ensuring
reliability and data integrity.

eXtremeDB's XML stands out as a truly embeddable implementation. The module
adds just 40K to the run-time code size, meeting the footprint limitations
typically imposed by embedded systems and intelligent devices.

Potential uses include exporting real-time data from eXtremeDB-based
embedded devices into enterprise databases, for archiving and for building
cutting-edge embedded Web-servers and other applications. The ability to
accept incoming XML simplifies eXtremeDB schema evolution by allowing the
use of using XML editing and transformation tools to change the database
structure. eXtremeDB XML is developed in accordance with the W3C SOAP
encoding recommendations.

"Embedded systems developers are discovering that XML cuts project time via
well-understood standards and tools, and makes devices 'smarter' by
providing new connectivity options. With eXtremeDB's XML interface,
developers realize these benefits while continuing to enjoy an ultra-small
database footprint, fast performance and a rich development tool-set," said
Steve Graves, McObject co-founder and CEO. "eXtremeDB XML provides a key
connectivity component for building connected, state-of-the-art intelligent
devices."

About McObject

McObject, based in Issaquah, WA, is committed to building data management
technology that makes intelligent devices smarter, and to providing
first-rate support and consulting services to customers and partners. With
more than 30 years experience in compilers, real-time systems, embedded data
management and kernel level device-driver development, McObject's founders
are well-suited to deliver database technology that becomes as ubiquitous as
computing itself. The company can be reached at 425 831 5964, or visit
www.mcobject.com.

McObject and eXtremeDB are trademarks of McObject LLC. All other company or
product names mentioned herein are trademarks or registered trademarks of
their respective owners.

- --

McObject LLC
22525 SE 64th Place
Suite 302
Issaquah, WA  98027
Phone:+1 425 831 5964
Fax:    +1 425 831 1542
http://www.mcobject.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Large App in Boot ROM
Date: Mon, 18 Nov 2002 16:51:10 -0600
From: Keith Obrien <obrienk.spam@minn.teradyne.com>
Message-ID: <3DD96EDE.2030107@minn.teradyne.com>
References: <3DC7F74D.4090702@minn.teradyne.com> <2222d8d3.0211171329.2f511acc@posting.google.com> <2222d8d3.0211180841.7f841746@posting.google.com>

Hmm, seems we may have different software version, looks in our
version of the code (romStart) is using some linker defined
values, e.g.,

. . .
#elif   ((CPU_FAMILY == MIPS) || (CPU_FAMILY == PPC))
     copyLongs ((UINT *)(etext + 0), (UINT *) RESIDENT_DATA,
#else

. . .
Where,

IMPORT UCHAR    binArrayStart [];       /* compressed binary image */
IMPORT UCHAR    binArrayEnd;            /* end of compressed binary image */
IMPORT char     etext [];               /* defined by the loader */
IMPORT char     edata [];               /* defined by the loader */
IMPORT char     end [];                 /* defined by the loader */

Also, strangely enough, on a build of our application with 'vxWorks_rom'
(due to the inclusion of dataSegPad I'm guessing)
the following sizes are noted:

ldppc -X -N -Map vsmMap.map -e _romInit -Ttext 00100000   \
     -o vxWorks_rom romInit.o bootInit_uncmp.o dataSegPad.o \
     ctmp.o ctdt.o
true  vxWorks_rom
VX_CPU_FAMILY=ppc /wind/host/sun4-solaris2/bin/romsize -b 00800000   vxWorks_rom
vxWorks_rom: 3247976(t) + 492004(d) = 3739980 (4648628 unused)
              ---------!

Note, this is before your suggested changes!

Regards,
- -Keith

brentb wrote:

> Keith,
> 
> I forgot to add one more thing to the message below. You will have to
> also change the call in romStart:
> 
> Original call:
> 
>     /* Original WindRiver call */
>     copyLongs ((UINT *)ROM_DATA(binArrayStart),
>         (UINT *)UNCACHED(RAM_DST_ADRS),
>         (&binArrayEnd - binArrayStart) / sizeof (long));
>    
> Change to:
> 
>     copyLongs ((UINT *)binArrayStart,
>         (UINT *)UNCACHED(RAM_DST_ADRS),
>         (&binArrayEnd - binArrayStart) / sizeof (long));
> 
> If you work through the ROM_DATA macro, you will see why this is
> necessary.  You really just need to copy from binArrayStart to RAM_DST_ADRS.
> Hope this helps...
> 
> -Brent 
> 
> brentbergan@yahoo.com (brentb) wrote in message news:<2222d8d3.0211171329.2f511acc@posting.google.com>...
> 
>>Keith,
>>
>>I am also using a MPC8245 and have experienced this problem.  For example,
>>the vxWorks_rom image consists of text, data, and bss.  The text section
>>consists of romInit.s and romStart.c. During compilation, the actual vxWorks.o
>>image is converted entirely to .data, hence the use of binArrayStart and
>>binArrayEnd in the copy process in romStart. In the final link line of the
>>make file output, there is a flag that specifies where the text section
>>will be located (-Ttext fff00100), at fff00100.  You can just add a line
>>to the flags to specify the location of the .data section using the following:
>>-Tdata <data location>, i.e. -Tdata ff80000.  Let me know if that helps.
>>
>>-Brent
>>
>>Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DC7F74D.4090702@minn.teradyne.com>...
>>
>>>We are using a MPC8245 that has a boot vector at fff00100 (~1M) upper rom
>>>remaining.  Our application is spread over several projects and is
>>>on the order of 4 Megabytes.  We have significant ROM and RAM
>>>resources (e.g., 16M / 128M).
>>>
>>>Question:
>>>--------------------
>>>1) Is there an easy way to put the image to be copied from ROM to
>>>RAM in a different location other than contiguously with the BOOT ROM,
>>>e.g., boots at FFF00100, but copylongs/unzip copies from FF800000.
>>>
>>>
>>>Anyone had any experience with this issue?
>>>
>>>
>>>Thanks,
>>>Keitho
>>>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Running a sample program creates unresolved errors..how to rectify
Date: Mon, 18 Nov 2002 23:41:51 GMT
From: "drdiags" <drdiags@attbi.com>
Organization: AT&T Broadband
Message-ID: <3VeC9.43360$P31.20407@rwcrnsc53>
References: <ara0j8$i9i$1@overload.lbl.gov>

Nithya,

    You shouldn't have to copy anything to get this to compile and work. All
I did was
added the "apilib.lib" file to my VC++5.0 and later VC++.net workspace with
the same results.
I added the library path to the host/x86-win32/lib directory and also added
the
path to find the wvapi.h file, so the host/include directory was added for
that. See
following snippet from vcproj file, maybe new with VC++.net,

Tool
    Name="VCCLCompilerTool"
    Optimization="0"
    AdditionalIncludeDirectories="E:\T202_THG\host\include"
    PreprocessorDefinitions="WIN32,_DEBUG,CONSOLE,__WIN32__,HOST"
    IgnoreStandardIncludePath="FALSE"
    RuntimeLibrary="5"
    UsePrecompiledHeader="2"
    PrecompiledHeaderFile=".\Debug/wvrReader.pch"
    AssemblerListingLocation=".\Debug/"
    ObjectFile=".\Debug/"
    ProgramDataBaseFileName=".\Debug/"
    WarningLevel="3"
    SuppressStartupBanner="TRUE"
    DebugInformationFormat="4"
    ShowIncludes="FALSE"/>
   <Tool>
Name="VCLinkerTool"
    AdditionalOptions="/MACHINE:I386"
    AdditionalDependencies="odbc32.lib odbccp32.lib apilib.lib"
    OutputFile=".\Debug/wvrReader.exe"
    LinkIncremental="2"
    SuppressStartupBanner="TRUE"

AdditionalLibraryDirectories="&quot;E:\T202_THG\host\x86-win32\lib&quot;"
    GenerateDebugInformation="TRUE"
    ProgramDatabaseFile=".\Debug/wvrReader.pdb"
    SubSystem="2"
    EntryPointSymbol="mainCRTStartup"/>

"Nithya P" <nithyap490@hotmail.com> wrote in message
news:ara0j8$i9i$1@overload.lbl.gov...
> Hi all,
>   Thanks you all guys  for responding to my queries.
>
> I tried the same code in VC++ 6.0 .since i got error there.I proceeded to
> Tornado.Ok. Let me tell what i have tried now.
>
> My host is windows 2k & using MS VC 6.0 compliler(hope thatz not a
problem)
> & project is win32 console application.
>
> Tools-Oprions:-
> Include Dir: F:\Tornadox86\host\include
> Lib Dir: F:\Tornadox86\host\x86-win32\lib
>
> Project settings:
> Link->library modules:
> apilib.lib
> This time no compiler (or) linker error.
>
> But i got apilib.dll is not found in paths :
>
> ex. Winnt/System32
>      %WIND_BASE/host/%WIND_HOST_TYPE/bin
>
> But apilib.dll is present in  %WIND_BASE/host/%WIND_HOST_TYPE/bin
>
> Sol:
>
>   so , i copied apilib.dll  to Winnt/System32
>
> Another error popped out :
>     tcl .dll is not found in the path eventhough it is present.
>
> Please help your solutions.
> ********************************************************
> sample
> #include <iostream.h>
> #include "wvapi.h"
>
> int main (int argc, char ** argv)
>     {
>     if (argc != 2)
>         {
>         cout << "usage:" << argv [0] << " <logfile.wvr>" << endl;
>         exit (1);
>         }
>
>     try
>         {
>         WVEventBase     eb;
>
>         if (eb.load (argv [1]) == OK)
>             {
>             WVEventBase::iterator       i;
>
>             for (i = eb.begin (); i != eb.end (); ++i)
>                 {
>                 WVContext               ctx;
>                 WVContext::iterator     j;
>
>                 ctx = *i;
>                 for (j = ctx.begin (); j != ctx.end (); ++j)
>                     {
>                     cout << eb.eventAsString (*j) << endl;
>                     }
>                 }
>             }
>         else
>             {
>             cout << "Could not load eventbase " << argv [1] << endl;
>             }
>         }
>     catch (const wv_error &e)
>         {
>         cout << "WVAPI Error:" << e.what () << " code="
>              << e.errorCode () << endl;
>         exit (1);
>         }
>
>     return 0;
>     }
>
> ******************************************
>
>
>
>
> Thanks
> Nithya
>
>
>
> _________________________________________________________________
> STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: How many byte do you know VxWorks BSP Image size?
Date: 18 Nov 2002 18:26:16 -0800
From: jeffkim@unicess.com (jeff)
Organization: http://groups.google.com/
Message-ID: <107f9c39.0211181826.e374715@posting.google.com>

my target cpu is ppc850.
i'd like to define boot rom size.
 currently, compile result: about 600-700kbyte
i want that less than 512kbyte
do you know this method?

thank you.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How many byte do you know VxWorks BSP Image size?
Date: Mon, 18 Nov 2002 20:37:49 -0800
From: "Michael R. Kesti" <mkesti@gv.net>
Organization: MK Associates
Message-ID: <3DD9C01D.B14117A1@gv.net>
References: <107f9c39.0211181826.e374715@posting.google.com>
Reply-To: mkesti@gv.net

jeff wrote:

>my target cpu is ppc850.
>i'd like to define boot rom size.
> currently, compile result: about 600-700kbyte
>i want that less than 512kbyte
>do you know this method?

If you're not currently building a compressed ROM image then you've got
two options.  You can begin building a compressed ROM image or you can
remove features so as to remove code.  You don't have the option of
simply defining an arbitrary size.

- -- 
========================================================================
          Michael Kesti            |  "And like, one and one don't make
                                   |   two, one and one make one."
          mkesti@gv.net            |          - The Who, Bargain

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: wrapping printf()
Date: Tue, 19 Nov 2002 06:36:28 +0000 (UTC)
From: sting <arm@vip.sina.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <Xns92CB94784BD63armvipsinacom@202.108.36.140>
References: <aqivl2$8mm3@imsp212.netvigator.com>

"Yung" <general_miller@yahoo.com> wrote in
news:aqivl2$8mm3@imsp212.netvigator.com: 

> Hi all,
> 
> Our vxWorks system has a number of application tasks which are handled
> by different engineers. In order to make the individuals' debug
> messages more organized as they appear on the console, I am thinking
> of wrapping up printf() with another function such that different
> groups of debug messages can be conditionally supressed or displayed
> as required. In order to do this, i need to get access to the internal
> printf() too. Do you think there is a way to do this? Or is there any
> other means besides that that can help in the situation?
> Thanks a lot!
> 
> 
> 
> 
> 

test

---------------------------

Newsgroups: comp.os.vxworks
Subject: test
Date: Tue, 19 Nov 2002 06:39:52 +0000 (UTC)
From: sting <arm@vip.sina.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <Xns92CB950B62FC5armvipsinacom@202.108.36.140>

sssssssssssssssssssssssssssss

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How many byte do you know VxWorks BSP Image size?
Date: 18 Nov 2002 23:30:04 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211182330.448b5ea2@posting.google.com>
References: <107f9c39.0211181826.e374715@posting.google.com>

Hello,

1) Take out features that you are not using (you can do this manually,
or check out the auto-scaling feature of Tornado - make a backup of
your project before running this though, just in case it takes out too
much).

2) Make sure that you are using a compressed ROM image

(Probably best to check (2) before spending time on (1) since it is
easier, but with very little effort I was able to get the default
mbx860 image below 500KB uncompressed.)

HTH,

John...

jeffkim@unicess.com (jeff) wrote in message news:<107f9c39.0211181826.e374715@posting.google.com>...
> my target cpu is ppc850.
> i'd like to define boot rom size.
>  currently, compile result: about 600-700kbyte
> i want that less than 512kbyte
> do you know this method?
> 
> thank you.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How many byte do you know VxWorks BSP Image size?
Date: Tue, 19 Nov 2002 08:31:11 +0100
From: Emmanuel Herbreteau <eherbreteau@sepro-robotique.com>
Organization: SEPRO Robotique (BEP)
Message-ID: <3DD9E8BF.B300955B@sepro-robotique.com>
References: <107f9c39.0211181826.e374715@posting.google.com>

Hi,

It depends on the type of bootrom. If you need
to boot your target from an ATA disk, such as
IDE or CompactFlash, you can build your custom
bootrom with the minimum number of modules
(core, ATA driver, DosFs2, etc...).

In this case, you should be able to make it
with only 300 KB uncompressed. With a compressed
image, a 256KB flash should do it as well, but
it use a small amount of RAM (the size of the uncompressed
code) and it's also slower (the code need to be unzip).

A good choice, in my opinion : a 512 KB flash bootrom.

(On our MPC823, it only use 223 KB to boot from ATA and DosFS1)

Regards
Emmanuel.

jeff wrote:
> my target cpu is ppc850.
> i'd like to define boot rom size.
>  currently, compile result: about 600-700kbyte
> i want that less than 512kbyte
> do you know this method?

---------------------------

Newsgroups: comp.os.vxworks
Subject: VxWorks V5.4+ gcc2.95 ?
Date: Mon, 18 Nov 2002 16:28:28 +0800
From: "Lewis Kang" <kang@accton.com.tw>
Organization: DCI HiNet
Message-ID: <ara8bg$p40@netnews.hinet.net>
Reply-To: "Lewis Kang" <kang@accton.com.tw>

Dear All,

  Since we found Tornado V2.0 has .text reloc overflow issue for ARM 7
target when application has many large software components. Tornado V2.0 can
only produce COFF file and which has a limitation as 65535 relocations for a
single .text section. We found the -split-by-reloc ld option can not take
affect.

  We are thinking of using gcc2.95 to do the compiler/linking. But still
make use of VxWorks V5.4.

  Do you have any comments? Is it workable?
  Have somebody ever tried it?
  Thanks.

/Lewis

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: VxWorks Download?
Date: 19 Nov 2002 08:47:16 GMT
From: Denis Perelyubskiy <kiev78@dslextreme.com>
Message-ID: <slrnatjukk.3kn.kiev78@concorde.cs.ucla.edu>
References: <ara14q$1626$1@news.kis.ru>

 *   <smalakhov@alcor.nnov.ru> [11-Sun-02 22:24
 * -0800]:
 >
 >    VxWorks&

   .  ,   , 
    .     
     WindRiver  
  ,     ,
    ,    .

    ,        WindRiver
(www.wrs.com)

,

denis

- -- 
'From' email address is used as a sink. Not read. Ever.
Instead, send to [t-h-e-u-k-r-a-i-n-i-a-n|h-o-t-m-a-i-l|c-o-m] (remove
dashes, replace the first vertical bar with @, and second with a dot)

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Tue Nov 19 04:21:00 2002
From: Mike Anderson <mike@theptrgroup.com>
Date: Tue Nov 19 04:21:02 PST 2002
Subject: Re: Errors while Building Vxworks with system defined timestamping

VxWorks Greetings!
On Tue, 2002-11-19 at 02:32, the vxWorks Users Group Exploder wrote:
> Submitted-by vxwexplo-errs@csg.lbl.gov  Mon Nov 18 23:17:54 2002
> Submitted-by: "Nithya P" <nithyap490@hotmail.com>
> 
> Hi all,
>    When i downloade the following code, i got unresolved errors for 
> systimestamping calls. So , I included system defined timestamping of 
> windview component in Vxworks tab of Build spec.
> 

[snip]

> gw32\lib\crt1.o \
> 	dataSegPad.o partialImage.o ctdt.o -o vxWorks
> partialImage.o: In function `_tfd':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1ca9): undefined 
> reference to `sysTi
> mestampFreq'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cae): undefined 
> reference to `sysTi
> 
> 
[snip]

Try rebuilding your dependencies and look at the build spec for "-I.".  
Either move the "-I." to the end of the list, or delete it altogether.  
It seems to confuse the Tornado build scripts.

HTH,

Mike

-- 
=======================================================
       T h e   P T R   G r o u p,   I n c.
=======================================================
       Embedded, Real-Time Solutions and Training

Mike Anderson             mailto:mike@ThePTRGroup.com
Chief Scientist           http://www.ThePTRGroup.com
C: (703) 585-9384         V: (703) 430-3748
=======================================================
"Software development is like making a baby...
 You can't make a baby in one month by impregnating
 nine women.  Some things just take time."

From vxwexplo-errs@csg.lbl.gov  Wed Nov 20 04:03:19 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Wed Nov 20 04:03:21 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Wed Nov 20 04:03:16 PST 2002

        Subject: Re: Errors while Building Vxworks with system defined timestamping
        Subject: muxDevUnload and the target server (end driver connection)
        Subject: MuxLoad failed error while booting
        Subject: Re: Embedded database comparison?
        Subject: Re: Web Server and MIB
        Subject: Re: doc on line about VxWorks
        Subject: Re: muxDevUnload and the target server (end driver connection)
        Subject: Re: newbie   VxWorks on cable modem
        Subject: Re: VxWorks V5.4+ gcc2.95 ?
        Subject: HowTo: INCLUDE_RPC using config.h in BSP (not Tornado)
        Subject: Re: [q] assemble error problem
        Subject: FEC0 works well with 10M HD, but get error with 10M FD
        Subject: When should vxWorks.st load drivers from endDevTbl?
        Subject: FEC0 works well with 10M Half Duplex, but got error with 10M Full Duplex.
        Subject: Re: Error message after booting
        Subject: Having Both Tornado and Target Shells with Tornado 2.1.
        Subject: WindNET stack and WindNET router stack.
        Subject: DDK - USBD VxWokd
        Subject: Re: [q] assemble error problem
        Subject: Re: HowTo: INCLUDE_RPC using config.h in BSP (not Tornado)
        Subject: [q] assemble error problem
        Subject: Error message after booting
        Subject: ftp server problem
        Subject: MIB-2 IP MIB get options
        Subject: Re: [q] assemble error problem

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Errors while Building Vxworks with system defined timestamping
Date: Tue, 19 Nov 2002 13:42:44 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <ardbk5$r48$1@snoopy.bndlg.de>
References: <arcs04$pt6$1@overload.lbl.gov>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Hi Nithya,

as your compiler output shows, you are working on SIMNT - you should tell
this explicitely.

AFAIK system defined timestamping is not supported under SIMNT, only
sequential.
IMHO system defined timestamping would make no sense, as the timing of your
simulator will defer from your target's in a big order - I hope :-)

Regards,
Michael

"Nithya P" <nithyap490@hotmail.com> schrieb im Newsbeitrag
news:arcs04$pt6$1@overload.lbl.gov...
> Hi all,
>    When i downloade the following code, i got unresolved errors for
> systimestamping calls. So , I included system defined timestamping of
> windview component in Vxworks tab of Build spec.
>
> I'm getting errors which i had pasted below:Please help me to solve it.
>
> #include <vxworks.h>
> #include "string.h"
> #include "stdio.h"
> #include "wvLib.h"
> #include "taskLib.h"
> #include "drv/timer/timerDev.h"
> #include "wvTmrLib.h"
> #include "rBuffLib.h"
> #include "wdb/wdbVioLib.h"
> #include "private/wvFileUploadPathLibP.h"
> #include "private/wvTsfsUploadPathLibP.h"
> #include "private/funcBindP.h"
> #include "private/seqDrvP.h"
>
> extern FUNCPTR _func_wvOnUploadPathCreate;
> extern FUNCPTR _func_wvOnUploadPathClose;
>
> extern int wvArgHtons;
> extern char * wvLogMsgString1;
> extern char * wvLogMsgString2;
>
> void testView(void)
> {
>
>     wvLibInit();                       /* low-level kernel instrumentation
> needed by windview */
>
>
/*wvTmrRegister((UINTFUNCPTR)seqStamp,(UINTFUNCPTR)seqStampLock,(FUNCPTR)seq
Enable,(FUNCPTR)seqDisable,(FUNCPTR)seqConnect,(UINTFUNCPTR)
> seqPeriod,(UINTFUNCPTR) seqFreq);*/ /* no timestamping */
> wvTmrRegister (sysTimestamp,
>                    sysTimestampLock,
>                    sysTimestampEnable,
>                    sysTimestampDisable,
>                    sysTimestampConnect,
>                    sysTimestampPeriod,
>                    sysTimestampFreq);
>     rBuffLibInit ();                    /* windview 2.0 ring of buffers
for
> event logging  */
>     wdbTsfsDrv ("/tgtsvr");             /* virtual file system based on
the
> WDB agent */
>   /*  usrWvTsfsUploadPathInit ();  */       /* initialize path for the
> upload through TSFS socket  */
>     /*usrWvFileUploadPathInit (); */        /* initialize path for the
> upload to file  */
>
>     _func_wvOnUploadPathCreate = (FUNCPTR) fileUploadPathCreate;
>     _func_wvOnUploadPathClose = (FUNCPTR) fileUploadPathClose;
>     wvArgHtons = 0;
>     wvLogMsgString1 = "fname=";
>     wvLogMsgString2 = "flag=";
>
>     fileUploadPathLibInit ();
>
> }
>
> Errors on building:
>
> wtxtcl F:\Tornadox86\host\src\hutils\configGen.tcl
> F:\Tornadox86\target\proj\TestCases\WVi
> ew\WindView.wpj
> ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32
> -U__WIN32 -U__WIN32__
> -U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-p
op
> -Wall -DRW_M
> ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView
> -IF:\Tornadox86\targe
> t\config\simpc -IF:\Tornadox86\target\config\comps\src
> -IF:\Tornadox86\target\h -If:\torna
> dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD
> -c F:\Tornadox8
> 6\target\config\simpc\sysLib.c
> ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32
> -U__WIN32 -U__WIN32__
> -U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-p
op
> -Wall -DRW_M
> ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView
> -IF:\Tornadox86\targe
> t\config\simpc -IF:\Tornadox86\target\config\comps\src
> -IF:\Tornadox86\target\h -If:\torna
> dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD
> -c F:\Tornadox8
> 6\target\proj\TestCases\WView\prjConfig.c
> ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32
> -U__WIN32 -U__WIN32__
> -U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-p
op
> -Wall -DRW_M
> ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView
> -IF:\Tornadox86\targe
> t\config\simpc -IF:\Tornadox86\target\config\comps\src
> -IF:\Tornadox86\target\h -If:\torna
> dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD
> -c F:\Tornadox8
> 6\target\proj\TestCases\WView\linkSyms.c
> vxrm F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst
> Generating F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst...
> ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32
> -U__WIN32 -U__WIN32__
> -U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-p
op
> -Wall -DRW_M
> ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView
> -IF:\Tornadox86\targe
> t\config\simpc -IF:\Tornadox86\target\config\comps\src
> -IF:\Tornadox86\target\h -If:\torna
> dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD
> -c F:\Tornadox8
> 6\target\config\comps\src\version.c
> ccsimpc -BF:\Tornadox86\host\x86-win32\lib\gcc-lib\ -U__WINNT -UWIN32
> -U__WINNT__ -UWINNT
> -U__MINGW32__ -U_WIN32 -U__WIN32 -U__WIN32__ -U__WIN32 -nostdlib -r -Wl,-X
\
>     -Wl,@F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst  version.o
> F:\Tornadox86\t
> arget\lib\libSIMNTgnuvx.a -o partialImage.o
> nmsimpc -g partialImage.o
> @F:\Tornadox86\target\proj\TestCases\WView\prjObjs.lst | wtxtcl
> F:\Tornadox86\host\src\hutils\munch.tcl -asm simpc > ctdt.c
> ccsimpc -c -fdollars-in-identifiers -U__WINNT -UWIN32 -U__WINNT__ -UWINNT
> -U__MINGW32__ -U
> _WIN32 -U__WIN32 -U__WIN32__ -U__WIN32 -mpentium -ansi -nostdinc -g
> -nostdlib -fno-builtin
> -fno-defer-pop -Wall -DRW_MULTI_THREAD -D_REENTRANT
> -IF:\Tornadox86\target\proj\TestCases
> \WView -IF:\Tornadox86\target\config\simpc
> -IF:\Tornadox86\target\config\comps\src -IF:\To
> rnadox86\target\h -If:\tornadox86\host\include
> -IF:\Tornadox86\target\src\drv -DCPU=SIMNT
> -DPRJ_BUILD  ctdt.c -o ctdt.o
> ccsimpc -U__WINNT -UWIN32 -U__WINNT__ -UWINNT -U__MINGW32__ -U_WIN32
> -U__WIN32 -U__WIN32__
> -U__WIN32 -mpentium -ansi -nostdinc -g -nostdlib -fno-builtin -fno-defer-p
op
> -Wall -DRW_M
> ULTI_THREAD -D_REENTRANT -IF:\Tornadox86\target\proj\TestCases\WView
> -IF:\Tornadox86\targe
> t\config\simpc -IF:\Tornadox86\target\config\comps\src
> -IF:\Tornadox86\target\h -If:\torna
> dox86\host\include -IF:\Tornadox86\target\src\drv -DCPU=SIMNT -DPRJ_BUILD
> -c F:\Tornadox8
> 6\target\config\comps\src\dataSegPad.c
> ldsimpc --subsystem=windows -e _WinMainCRTStartup
> F:\Tornadox86\host\x86-win32\i386-pc-min
> gw32\lib\crt1.o \
> dataSegPad.o partialImage.o ctdt.o -o vxWorks
> partialImage.o: In function `_tfd':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1ca9): undefined
> reference to `sysTi
> mestampFreq'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cae): undefined
> reference to `sysTi
> mestampPeriod'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cb3): undefined
> reference to `sysTi
> mestampConnect'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cb8): undefined
> reference to `sysTi
> mestampDisable'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cbd): undefined
> reference to `sysTi
> mestampEnable'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cc2): undefined
> reference to `sysTi
> mestampLock'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x1cc7): undefined
> reference to `sysTi
> mestamp'
> partialImage.o: In function `_tfUl':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2190): undefined
> reference to `WVEve
> ntBase::WVEventBase(Tcl_Interp *)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x21b0): undefined
> reference to `WVEve
> ntBase::~WVEventBase(void)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x21df): undefined
> reference to `WVEve
> ntBase::load(char const *, int (*)(void *, int, int), void *, __sFILE *)'
> partialImage.o: In function `_tfUx':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x21fc): undefined
> reference to `WVEBI
> ter::WVEBIter(CEventBase const *, unsigned int)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2212): undefined
> reference to `WVEve
> ntBase::begin(void) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2228): undefined
> reference to `WVEBI
> ter::operator=(WVEBIter const &)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2240): undefined
> reference to `WVEve
> ntBase::end(void) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2256): undefined
> reference to `WVEBI
> ter::operator!=(WVEBIter const &) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x22b6): undefined
> reference to `WVCtx
> Iter::WVCtxIter(CContext const *, unsigned int)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x22cc): undefined
> reference to `WVEBI
> ter::operator*(void) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2313): undefined
> reference to `WVCon
> text::operator=(WVContext const &)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2363): undefined
> reference to `WVCtx
> Iter::operator=(WVCtxIter const &)'
> partialImage.o: In function `_tfUs':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2391): undefined
> reference to `WVCtx
> Iter::operator!=(WVCtxIter const &) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x23b4): undefined
> reference to `WVCtx
> Iter::operator*(void) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x23cc): undefined
> reference to `WVEve
> ntBase::eventAsString(WVEvent const &, char const *) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x23f8): undefined
> reference to `WVCtx
> Iter::operator++(void)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2430): undefined
> reference to `WVEBI
> ter::operator++(void)'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x2493): undefined
> reference to `WVEve
> ntBase::~WVEventBase(void)'
> partialImage.o: In function `$_16__ptmf_type_info':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x27e5): undefined
> reference to `WVCon
> text::size(void) const'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x27f4): undefined
> reference to `WVCtx
> Iter::WVCtxIter(CContext const *, unsigned int)'
> partialImage.o: In function `_tf16__func_type_info':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x281e): undefined
> reference to `WVCtx
> Iter::WVCtxIter(CContext const *, unsigned int)'
> partialImage.o: In function `_tf16__attr_type_info':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28dd): undefined
> reference to `sysTi
> mestampFreq'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28e2): undefined
> reference to `sysTi
> mestampPeriod'
> partialImage.o: In function `$_16__attr_type_info':
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28e7): undefined
> reference to `sysTi
> mestampConnect'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28ec): undefined
> reference to `sysTi
> mestampDisable'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28f1): undefined
> reference to `sysTi
> mestampEnable'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28f6): undefined
> reference to `sysTi
> mestampLock'
> \wpwr\host\src\gnu.simpc.cpp\gcc\cp\tinfo2.cc(.text+0x28fb): undefined
> reference to `sysTi
> mestamp'
> make: *** [vxWorks] Error 0x1
>
> Done.
>
> Thanks
> Nithya
>
> _________________________________________________________________
> Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: muxDevUnload and the target server (end driver connection)
Date: 19 Nov 2002 04:51:35 -0800
From: fillmore2@arcor.de (Achim)
Organization: http://groups.google.com/
Message-ID: <9d082700.0211190451.75418afc@posting.google.com>

Hello all,

I have the problem that after the shutdown of the target server (end
driver connection, ln97xEnd), my Ethernet connection to the target is
lost if the interface had been unloaded & restarted (muxDevUnload -
muxDevLoad - musDevStart etc.). Working with the Tornado tools over
the Ethernet connection shows no obvious problems. Without a
preceeding unload/reload of the interface, the shutdown causes no
problems.

I suspect that the problem lies with unloading the interface that has
originally been loaded while booting vxWorks and where the Wdb is
connected.

Any ideas where exactly to start looking for a solution are much
appreciated.

Achim

---------------------------

Newsgroups: comp.os.vxworks
Subject: MuxLoad failed error while booting
Date: 19 Nov 2002 05:07:46 -0800
From: srik_ram@rediffmail.com (Srikanth)
Organization: http://groups.google.com/
Message-ID: <4e3aab22.0211190507.3f4d8c2d@posting.google.com>

Dear All,

I am trying to boot the pc pentium machine using network by creating
the bootable floppy in Vxworks.
I have created the bootable floppy for PC Pentium. 
When I tried to boot the target using this floppy, it is giving the
error "Muxload failed."
The boot device parameter is "fei0" and i have specified IP address of
target and host properly.
It is giving the above error and it is not trying to access the
network.
Can anybody please give the possible solution for the above.

Thanks 
Srikanth

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Embedded database comparison?
Date: Tue, 19 Nov 2002 13:37:04 -0000
From: "Andrew Deamer" <andrew.deamer@polyhedra.com>
Message-ID: <ardehb$l42$1$8300dec7@news.demon.co.uk>
References: <vouz9.13476$Nd.3656@afrodite.telenet-ops.be>

I think that you should consider Polyhedra if you are looking for an
embedded database - see www.polyhedra.com

Andrew Deamer
Polyhedra plc

"who am i" <who@am.i> wrote in message
news:vouz9.13476$Nd.3656@afrodite.telenet-ops.be...
> Hello,
>
> Anyone with experience with either BerkeleyDB (Sleepycat) or Birdstep?  Or
> some other embedded DB?  The marketting or commercial bla bla doesn't help
> me very much.  They are both high performance, small footprint etc...  But
> really how do they compare?
>
> Eddy
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Web Server and MIB
Date: 19 Nov 2002 13:35:23 GMT
From: "Tim Michals" <tmichals@verityinst.com>
Organization: Concentric Internet Services
Message-ID: <ardemr$pgi@dispatch.concentric.net>
References: <LrGq9.37055$Dn3.173403@dfw-read.news.verio.net>

Please Note that the Web syntax for IDB objects is different, I think it is
an extra underline or something.

Thanks,

Tim
"AW" <adrianw@erlangtech.com> wrote in message
news:LrGq9.37055$Dn3.173403@dfw-read.news.verio.net...
> Hi there,
>
> Is there anybody who is familiar with Tornado for Managed Switches (TMS)?
>
> I have built custom MIB and managed to insert it into IDB+. TMS is using
> Wind Web Server to access the MIB tree. My problem is that I can't access
my
> MIB from web pages. The steps I have done are:
> 1. Create a custom HTML page
> 2. Create an association .c file to define the symbols
> (mibgroupName_mibnodeName)
> 3. Recompile webif directory
> 4. Recompile vxWorks BSD
> And I still get "Symbol not found" error.
>
>
> Thank you very much in advance
>
>
> Adrian
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: doc on line about VxWorks
Date: Tue, 19 Nov 2002 14:00:15 +0000 (UTC)
From: Johan Borkhuis <JBorkhuis@proxim.com>
Organization: Proxim Corp.
Message-ID: <Xns92CB97F2EEE83jborkhuisproximcom@192.19.193.66>
References: <ar87ih$5q0$1@apollon.grec.isp.9tel.net>

"sald" <sald@oreka.com> wrote:

> Is there anyone who knows where on the WEB I can find documentations
> about VxWorks ?
> 
> I would like to read the concepts and the difference between VxWorks
> and PSOS.

They are available in the customer support section on the Windriver 
website. Ask a sales rep in your area if they can provide you with an 
access code, or ask for an evaluation version of Tornado, this comes with 
the complete docs.

Kind regards,
        Johan

- -- 
        o o o o o o o . . .   _____________________________
       o      _____           ||    Johan Borkhuis        |
     .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
    >(________|__|_[_________]_|__________________________|
    _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
=== VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: muxDevUnload and the target server (end driver connection)
Date: Tue, 19 Nov 2002 13:56:18 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <ardfu1$ga7$1@helle.btinternet.com>
References: <9d082700.0211190451.75418afc@posting.google.com>

> Any ideas where exactly to start looking for a solution are much
> appreciated.

Don't bother!

Does your final product require you to be able to unload the
ethernet driver?
Does it require wdb?

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: newbie   VxWorks on cable modem
Date: Tue, 19 Nov 2002 16:29:53 GMT
From: robotz@robotz.rob (Paul Slocum)
Organization: Randori News - http://www.randori.com - Try our FREE Usenet Scanner!
Message-ID: <3dda66dd.601667191@news.airband.net>
References: <arb6fp$4q4$1@news-reader11.wanadoo.fr>
Reply-To: robotz@robotz.rob

>I have a Com21 cable modem with VxWorks os.
>Where can i get some docs on it?

Maybe on the internet.

- -Paul

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: VxWorks V5.4+ gcc2.95 ?
Date: 19 Nov 2002 13:37:21 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211191337.41fb6396@posting.google.com>
References: <ara8bg$p40@netnews.hinet.net>

Hello,

>   Do you have any comments? Is it workable?

No, and it would make no difference anyway: it is COFF and not the
compiler version that is the cause of this problem (assuming that it
is the --split-by-reloc issue).

If you want to change compiler and object module format, say to ELF,
then upgrade to VxWorks 5.5. That will not only get the newer
compiler, it will also get you ELF instead of COFF.

Why make your life difficult by trying to make another compiler work
with 5.4?

HTH,

John...

---------------------------

Newsgroups: comp.os.vxworks
Subject: HowTo: INCLUDE_RPC using config.h in BSP (not Tornado)
Date: Tue, 19 Nov 2002 22:15:15 -0000
From: "Dimitrios Siganos" <nospam_dimitrios.siganos@newport-networks.com>
Organization: Newport Networks Ltd.
Message-ID: <1037744121.823605@azores.network-i.net>

Hi everyone,

I'm having severe problems getting RPC to work in a BSP. If I define
INCLUDE_RPC in config.h, the BSP compiles fine. When I run on the target,
the portmapper throws errors ...

- -> svc.c: - Select failed: errno = 0x390002
run_svc returned unexpectedly

Basically select fails and the portmapper daemon exits. The errno is
S_selectLib_NO_SELECT_CONTEXT.

Does anyone know if I have to define any other macros to get RPC to work? It
works okay if I create a project using Tornado based on the same BSP. Does
anyone know what Tornado is doing differently?

I have tried defining INCLUDE_BSD, INCLUDE_BSD_SOCKETS, INCLUDE_NFS_SERVER
without any success. I have increased NUM_FILES and the network buffers as
well.

I need to start RPC servers as early as possible as some of our hardware
configuration requires RPC network comms for synchronisation.
P.S. We are using T2.1, vxWorks 5.4, wrPpmc74xx_vx based bsp, target is
PPC7410.

Thanks in advance
Obi

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: [q] assemble error problem
Date: 19 Nov 2002 15:54:20 -0800
From: FrankGleeson@motorola.com (frankg)
Organization: http://groups.google.com/
Message-ID: <a7b7bb67.0211191554.1c371f7a@posting.google.com>
References: <4753b4b1.0211190931.4b8d034c@posting.google.com>

In the bootrom build romInit.s is compiled by gcc to a temporary
file.

On your system this is 
"C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s"

The assembler gas (gnu assembler) then compiles
the temporary into an object and deletes the temporary file.

Letting the c-preprocessor do a first pass allows programmers to
do things like use #define C-style macros and #include files and
use /* comments that span lines.

This makes debugging assembler errors very difficult.

What I do is make a backup copy the assembler source then invoke gcc
on romInit.s as normal except pass the -save-temps command line
parameter.
This will *OVERWRITE* your original assembler hence the backup copy.

You can now assemble the romInit.s that the c-preprocessor made. Now
when the assembler complains about a error on line number X you will
be able
to go look at it and figure it out.

I usually edit the CFLAGS_AS make variable in defs.bsp to add
- -save-temps
and then invoke make which automates the process. Just be careful to
save backups of any .s source files you have lying around. If you
modify defs.bsp
remember to change it back!

---------------------------

Newsgroups: comp.os.vxworks
Subject: FEC0 works well with 10M HD, but get error with 10M FD
Date: 19 Nov 2002 16:05:41 -0800
From: yanxiu@sbcglobal.net (Yan X.)
Organization: http://groups.google.com/
Message-ID: <34f7f684.0211191605.daaab05@posting.google.com>

hi,

my platform is MPC8260, m8260FccEnd.c is used as the driver of FEC, I
have configured FEC0 with diffrent flag set in configNet.h.

FEC0 works well with the following flag set,

1) 0x00: AN_ON;
2) 0x0D: AN_OFF + 10M + HalfDuplex;

but does works well with the flag of 0x19: AN_OFF + 10M + FullDuplex.
When I copy data into target, I got the following error message which
means "RX CRC error" and "Rx nonoctet aligned frame". When I copy data
off target, it works slowly. Note that I have set motFccEndDbg to
MOT_FCC_DBG_INT_RX_ERR | MOT_FCC_DBG_INT_TX_ERR;

0x640a448 (tNetTask): RX addr = 0x62d2ee0  Len = 0x275  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62cd740  Len = 0x2b6  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62c0ec0  Len = 0x271  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62d0960  Len = 0x398  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62c1500  Len = 0x238  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62cb7e0  Len = 0x337  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62c27c0  Len = 0x238  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62c0880  Len = 0x398  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62db8c0  Len = 0x238  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62d4800  Len = 0x3b7  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62dcba0  Len = 0x278  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62dbf00  Len = 0x24f  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62cb1a0  Len = 0x337  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62c8c00  Len = 0x255  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62cc460  Len = 0x385  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62cd100  Len = 0x238  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62cfcc0  Len = 0x3b7  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62bfbe0  Len = 0x250  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62d28a0  Len = 0xa0  Stat = 0x3c10

What's happened? Can anyone give me any advice?

Thanks
Yan

---------------------------

Newsgroups: comp.os.vxworks
Subject: When should vxWorks.st load drivers from endDevTbl?
Date: 19 Nov 2002 16:17:17 -0800
From: FrankGleeson@motorola.com (frankg)
Organization: http://groups.google.com/
Message-ID: <a7b7bb67.0211191617.5ac65021@posting.google.com>

I am porting the v34 of the wrSbc8260 BSP to our own custom 8265
based design. I am having trouble understanding how the system image
initializes the network drivers.

In the bootrom code in file bootConfig.c. The function bootLoad()
tries to locate an END driver. If it find one it calls muxDevStart
thereby initializing the driver. I can set a breakpoint on my drivers
init routine motFccStart() and see that the call was from
bootConfig.c.

If I set that same breakpoint in the system image it is never called.
I can not locate a function that loads the END drivers. What *really*
confuses me is that the FCCs ethernet works beautifully from the
system
image. Does this mean the system image is relying on the bootrom setup
and it is just somehow working? 

The Windriver docs indicate that the application (system image) should
not rely on the initialization provided by the bootcode. So if this is
whats going on
I need to fix it.

Is there a predefined location in the vxWorks.st build for doing an 
END driver table initialization? Or do I just need to add the calls
somewhere appropriate?

---------------------------

Newsgroups: comp.os.vxworks
Subject: FEC0 works well with 10M Half Duplex, but got error with 10M Full Duplex.
Date: 19 Nov 2002 16:18:18 -0800
From: yanxiu@sbcglobal.net (Yan X.)
Organization: http://groups.google.com/
Message-ID: <34f7f684.0211191618.35059f0f@posting.google.com>

hi,

Sorry for my last post!

my platform is MPC8260, m8260FccEnd.c is used as the driver of FEC, I
have configured FEC0 with diffrent flag set in configNet.h.

FEC0 works well with the following flag set,

1) 0x00: AN_ON;
2) 0x0D: AN_OFF + 10M + HalfDuplex;

but doesn't work well with the flag of 0x19: AN_OFF + 10M + FullDuplex.
When I copy data into target, I got the following error message which
means "RX CRC error" and "Rx nonoctet aligned frame". When I copy data
off target, it works slowly. Note that I have set motFccEndDbg to
MOT_FCC_DBG_INT_RX_ERR | MOT_FCC_DBG_INT_TX_ERR;

0x640a448 (tNetTask): RX addr = 0x62d2ee0  Len = 0x275  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62cd740  Len = 0x2b6  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62c0ec0  Len = 0x271  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62d0960  Len = 0x398  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62c1500  Len = 0x238  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62cb7e0  Len = 0x337  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62c27c0  Len = 0x238  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62c0880  Len = 0x398  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62db8c0  Len = 0x238  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62d4800  Len = 0x3b7  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62dcba0  Len = 0x278  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62dbf00  Len = 0x24f  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62cb1a0  Len = 0x337  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62c8c00  Len = 0x255  Stat = 0x1c04
0x640a448 (tNetTask): RX addr = 0x62cc460  Len = 0x385  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62cd100  Len = 0x238  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62cfcc0  Len = 0x3b7  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62bfbe0  Len = 0x250  Stat = 0x1c10
0x640a448 (tNetTask): RX addr = 0x62d28a0  Len = 0xa0  Stat = 0x3c10

What's happened? Can anyone give me any advice?

Thanks
Yan

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Error message after booting
Date: 19 Nov 2002 18:15:37 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211191815.20a958a7@posting.google.com>
References: <utkt98ousurh40@corp.supernews.com>

Hello,

Does the target have dual ethernet? If so, this message is probably
coming from the second channel. Try checking in your config.h for the
macro that defines the secondary ethernet, and undefining it.

If you only have the one channel, then I would look carefully at the
config of that channel. It would seem that MII at least believes that
there is no cable connected to it. You didn't say whether the network
connection was actually working...

Finally, if all else fails, contact WR support and make sure that you
have the latest drivers (both the network one and the MII driver that
it shares).

HTH,

John...

"cnwebb" <cwebb@maxtc.com> wrote in message news:<utkt98ousurh40@corp.supernews.com>...
> I am attempting to boot up a PowerPC 750 processor on a
> Motorola MVME2431 board using Tornado 2.0.2 & VxWorks 5.4
> 
> I have successfully built the microkernel and flashed it to the board,
> and the board appears to boot normally.  However after the VxWorks
> version information is displayed in my Hyperterminal window, I start
> getting the following error
>          miiPhyInit:  check cable connection
> 
> This error continues to be written to the display until I disconnect from
> the target.  I have checked the cable connections on both the host and
> the target, and they are secure.  I have also used the same cables to
> boot up another computer using a previous version of Tornado/VxWorks,
> so I don't believe there is a problem with the cables.
> 
> I would appreciate any help in determining the cause and solution of this
> problem.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Having Both Tornado and Target Shells with Tornado 2.1.
Date: 19 Nov 2002 07:11:30 -0700
From: taashlo@sandia.gov
Organization: Sandia National Laboratories, Albuquerque, NM USA
Message-ID: <8yzpy7hp.fsf@sandia.gov>
Sender: taashlo@TYPHOON

Hi VxWorkers,

With Tornado 2.0 (VxWorks 5.4), I had a configuration for a
standalone build that included not only the target shell, but
the Tornado (host) shell also.  With this configuration, I
could boot into the target shell and at some later time plug
in an ethernet cable and connect using the Tornado shell.
(When the target shell boots up I see "WDB: Ready" in the
banner and "tWdbTask" in the task list.)

I have since upgraded to Tornado 2.1 (VxWorks 5.4.2) and a
new BSP version.  I didn't change any of the config.h options
that I thought would relate to having both shells active, but
the new version only has the target shell.  (When the target
shell boots up I *don't* see "WDB: Ready" in the banner and
"tWdbTask" is *not* in the task list.)

Does anybody know the right way to configure VxWorks to have
both shells active?

Thanks,

Tad

---------------------------

Newsgroups: comp.os.vxworks
Subject: WindNET stack and WindNET router stack.
Date: 19 Nov 2002 21:19:04 -0800
From: vividh@hotmail.com (rasayani)
Organization: http://groups.google.com/
Message-ID: <28809481.0211192119.be5b8bd@posting.google.com>

Is WindNET router stack a seperate product? Whats the default stack
that comes with VxWorks 5.4? Also can someone tell me the difference
between these two stacks?

TIA
vividh

---------------------------

Newsgroups: comp.os.vxworks
Subject: DDK - USBD VxWokd
Date: 19 Nov 2002 23:27:04 -0800
From: ravi368@yahoo.com (Ravi Uday)
Organization: http://groups.google.com/
Message-ID: <ecca3ca6.0211192327.6dc0050@posting.google.com>
References: <ecca3ca6.0210162128.c36f98c@posting.google.com> <IqPs9.73706$v_3.1544103@news.bora.net> <488e459a.0210212115.752d889c@posting.google.com> <Tr7t9.77017$v_3.1624862@news.bora.net> <ap55rt$1968$1@mail.cn99.com> <ecca3ca6.0210280101.dd850d0@posting.google.com> <apknan$3u1$1@mail.cn99.com>

ZhengZhe <jeff.zhen@utstar.com> wrote in message news:<apknan$3u1$1@mail.cn99.com>...
> Hi Ravi:
>     	We are using UHCI, the chipset is intel's chipset for PentiumIII. 
> OHCI is compaq's spec. The chipset is not a matter, whatever it is from 
> it must follow one standard either UHCI or OHCI. For vxWorks USB u can 
> buy one, or u can migrate from linux. Linux implement both UHCI and
> OHCI, u only need to migrate one of them. But it is only the first step
> , after that u need to use the linux usb architecture to write your own
> driver.
>     	We spent three weeks on this, and we met some problem at DMA, my
> boss aborted the plan.
> 
> Jeff
> 

Hi all...

Do you/anybody have or working on the WindRivers SDK provided for USBD
stack..implementation..i am currently stuck up..n now seeking help for
Bulk transfer ...

- - Ravi

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: [q] assemble error problem
Date: Wed, 20 Nov 2002 10:33:52 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$569v5h$j98$1@lnews.actcom.co.il>
References: <4753b4b1.0211190931.4b8d034c@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Daniel KWAK" <dhgwak@yahoo.com> wrote in message
news:4753b4b1.0211190931.4b8d034c@posting.google.com...
> Hi
>
> I am new to vxworks environment, using
> - tornado ver 2.0 (vxworks 5.4)
> - wind web server 1.0
> - tornado for managed switches 2.0
>
> I was trying to build a bootable vxworks image,
> and got the following error message in compiling.
>
> By the way, building the same source was OK
> when I installed only tornado (no wind web server, no TMS).
> It seems there might be some error in compile option,
> or conflict between tornado ver2.0 and TMS.
>
> Any advice appreciated,
> Best regards,
>
>
> ccppc -c -g -mcpu=860 -ansi -nostdinc  -fvolatile -fno-builtin
> -fno-for-scope -P -x assemb
> ler-with-cpp -IC:\Tornado\target\proj\111
> -IC:\Tornado\target\config\mpc850 -IC:\Tornado\t
> arget\h -IC:\Tornado\target\config\comps\src
> -IC:\Tornado\target\src\drv -DCPU=PPC860 -
> DPRJ_BUILD -g -O  C:\Tornado\target\config\mpc850\romInit.s -o
> romInit.o
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s: Assembler messages:
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3284: Error:
> Unrecognized opcode: `typedef'
[snip]

It is quite common in VxWorks to have include files which are used by both
C and Assembly source code, specifically, include files that define hardware
register offsets and the like. This is why the make rules use the C
preprocessor
on the assembly source files before actually assembling them.

For this purpose, include files have an #ifdef statement that prevents
assembly
sources from using definitions other then by way of #define.

Look over the .h files included by rominit.s, and check each one that it
does

    #ifndef _ASMLANGUAGE

before any declaration of C types (struct, typedef, etc.) or external
variable definitions.

The offending include file may very well be nested from one of the BSP
header
files, so looking in the temporary (intermediate) file to see WHAT type it
attempted
to declare, could help you find the offending header file more quickly.
- -- HTH
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: HowTo: INCLUDE_RPC using config.h in BSP (not Tornado)
Date: Wed, 20 Nov 2002 10:37:08 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$mb9v5h$l98$1@lnews.actcom.co.il>
References: <1037744121.823605@azores.network-i.net>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

Dimitris,

defining NUM_FILES to a number greater then 256 will
definitely break selectLib in its current form.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

"Dimitrios Siganos" <nospam_dimitrios.siganos@newport-networks.com> wrote in
message news:1037744121.823605@azores.network-i.net...
> Hi everyone,
>
> I'm having severe problems getting RPC to work in a BSP. If I define
> INCLUDE_RPC in config.h, the BSP compiles fine. When I run on the target,
> the portmapper throws errors ...
>
> -> svc.c: - Select failed: errno = 0x390002
> run_svc returned unexpectedly
>
> Basically select fails and the portmapper daemon exits. The errno is
> S_selectLib_NO_SELECT_CONTEXT.
>
> Does anyone know if I have to define any other macros to get RPC to work?
It
> works okay if I create a project using Tornado based on the same BSP. Does
> anyone know what Tornado is doing differently?
>
> I have tried defining INCLUDE_BSD, INCLUDE_BSD_SOCKETS, INCLUDE_NFS_SERVER
> without any success. I have increased NUM_FILES and the network buffers as
> well.
>
> I need to start RPC servers as early as possible as some of our hardware
> configuration requires RPC network comms for synchronisation.
> P.S. We are using T2.1, vxWorks 5.4, wrPpmc74xx_vx based bsp, target is
> PPC7410.
>
> Thanks in advance
> Obi
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: [q] assemble error problem
Date: 19 Nov 2002 09:31:34 -0800
From: dhgwak@yahoo.com (Daniel KWAK)
Organization: http://groups.google.com/
Message-ID: <4753b4b1.0211190931.4b8d034c@posting.google.com>

Hi 

I am new to vxworks environment, using
- - tornado ver 2.0 (vxworks 5.4)
- - wind web server 1.0
- - tornado for managed switches 2.0

I was trying to build a bootable vxworks image, 
and got the following error message in compiling.

By the way, building the same source was OK 
when I installed only tornado (no wind web server, no TMS). 
It seems there might be some error in compile option,
or conflict between tornado ver2.0 and TMS.

Any advice appreciated,
Best regards,

ccppc -c -g -mcpu=860 -ansi -nostdinc  -fvolatile -fno-builtin
- -fno-for-scope -P -x assemb
ler-with-cpp -IC:\Tornado\target\proj\111
- -IC:\Tornado\target\config\mpc850 -IC:\Tornado\t
arget\h 	 -IC:\Tornado\target\config\comps\src
- -IC:\Tornado\target\src\drv	 -DCPU=PPC860 -
DPRJ_BUILD -g -O  C:\Tornado\target\config\mpc850\romInit.s -o
romInit.o
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s: Assembler messages:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3284: Error:
Unrecognized opcode: `typedef'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3285: Error: Rest of
line ignored. First ign
ored character is `{'.
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3286: Error:
Unrecognized opcode: `uint32'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3287: Error:
Unrecognized opcode: `uint32'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3288: Error: Rest of
line ignored. First ign
ored character is `}'.
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3290: Error:
Unrecognized opcode: `typedef'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3291: Error: Rest of
line ignored. First ign
ored character is `{'.
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3292: Error:
Unrecognized opcode: `uint8'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3293: Error:
Unrecognized opcode: `uint32'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3294: Error:
Unrecognized opcode: `uint32'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3295: Error:
Unrecognized opcode: `uint32'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3296: Error:
Unrecognized opcode: `sect_desc
r'
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3297: Error: Rest of
line ignored. First ign
ored character is `}'.
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:5233: Warning: operand
out of range (65536 n
ot between -32768 and 65535)
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:5353: Warning: operand
out of range (65536 n
ot between -32768 and 65535)
ccppc: Internal compiler error: program as got fatal signal 1
make: *** [romInit.o] Error 0x1

Done.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Error message after booting
Date: Tue, 19 Nov 2002 11:37:56 -0600
From: "cnwebb" <cwebb@maxtc.com>
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <utkt98ousurh40@corp.supernews.com>

I am attempting to boot up a PowerPC 750 processor on a
Motorola MVME2431 board using Tornado 2.0.2 & VxWorks 5.4

I have successfully built the microkernel and flashed it to the board,
and the board appears to boot normally.  However after the VxWorks
version information is displayed in my Hyperterminal window, I start
getting the following error
         miiPhyInit:  check cable connection

This error continues to be written to the display until I disconnect from
the target.  I have checked the cable connections on both the host and
the target, and they are secure.  I have also used the same cables to
boot up another computer using a previous version of Tornado/VxWorks,
so I don't believe there is a problem with the cables.

I would appreciate any help in determining the cause and solution of this
problem.

---------------------------

Newsgroups: comp.os.vxworks
Subject: ftp server problem
Date: Wed, 20 Nov 2002 18:02:21 +0800
From: "kenny" <dick.cheng@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <arfmjh$of3$1@mail.cn99.com>

This is a multi-part message in MIME format.

- ------=_NextPart_000_018E_01C290BE.F8BB5DD0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

I am fighting for a problem these days, but not resolved it till now.
The problem is as following:
A gateway runing vxworks OS get file from a ftp server from a =
solaris(version 8). During loading object files, sometimes when getting =
a file from solaris ftp server it failed many times.
following is the error message from soloris machine:
Can't create data socket (10.13.1.61,20): Interrupted system call.
Can anyone tell me how to do with it? thanks     =20

- ------=_NextPart_000_018E_01C290BE.F8BB5DD0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dgb2312" http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I&nbsp;am fighting for a problem&nbsp;these days, =
but not=20
resolved it&nbsp;till now.</FONT></DIV>
<DIV><FONT size=3D2>The problem is as following:</FONT></DIV>
<DIV><FONT size=3D2>A&nbsp;gateway&nbsp;runing vxworks OS get file from =
a ftp=20
server from a solaris(version 8). During loading&nbsp;object files, =
sometimes=20
when&nbsp;getting a&nbsp;file&nbsp;from&nbsp;solaris ftp server it =
failed many=20
times.</FONT></DIV>
<DIV><FONT size=3D2>following&nbsp;is the&nbsp;error message from=20
soloris&nbsp;machine:</FONT></DIV>
<DIV><FONT size=3D2>Can't create data socket (10.13.1.61,20): =
Interrupted system=20
call.<SPAN lang=3DEN-US><?xml:namespace prefix =3D o ns =3D=20
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN>
<P class=3DMsoPlainText><FONT face=3D=CB=CE=CC=E5 size=3D1><SPAN =
lang=3DEN-US><o:p>Can anyone tell=20
me how to&nbsp;do with it?=20
thanks&nbsp;</o:p></SPAN></FONT>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></P>=
</DIV></BODY></HTML>

- ------=_NextPart_000_018E_01C290BE.F8BB5DD0--

---------------------------

Newsgroups: comp.os.vxworks
Subject: MIB-2 IP MIB get options
Date: Wed, 20 Nov 2002 12:04:05 +0200
From: "Barak Hermesh" <barakh@ti.com>
Organization: Texas Instruments
Message-ID: <arfmmt$c0r$1@tilde.itg.ti.com>

My platform runs two different applications simultaniously. Both
applications have connection to the Ip stack, but each has a different set
of network interfaces connected to the IP stack.
Each of these applications should hold its own MIB-2 counters and each
should hold the IP MIB as if it is the only runnung application.

The problem is that vxWorks' IP MIB access functions like m2IpGroupInfoGet()
work on the total packets arriving on all interfaces. Some counters may be
overriden since their values can be calculated in the application but some
like ipInDiscards must be given by the IP stack.

The question is:
Is there a way to get the IP MIB counters from the IP stack per interface ?
Any other suggestions for solving this ?

Thanks,
Barak.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: [q] assemble error problem
Date: Wed, 20 Nov 2002 11:48:16 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <arfspv$ccl$1@venus.btinternet.com>
References: <4753b4b1.0211190931.4b8d034c@posting.google.com> <a7b7bb67.0211191554.1c371f7a@posting.google.com>

> Letting the c-preprocessor do a first pass allows programmers to
> do things like use #define C-style macros and #include files and
> use /* comments that span lines.
> 
> This makes debugging assembler errors very difficult.

I usually introduce an extra error (eg an xxx opcode)
somewhere near where I think the reported error is.
This soon tracks down the actual error line.

(It is rather a shame that gas doesn't act on the line number
directives that cpp outputs and use them to reset its line
number counter.)

	David

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Wed Nov 20 07:23:31 2002
From: Douglas Wilson <dwilson@birdstep.com>
Date: Wed Nov 20 07:23:32 PST 2002
Subject: Changing current directory on simulator, Tornado 2 on Windows NT

Is there any way to change the current directory (on the target, not the
host) from the shell, when running the simulator under Tornado 2, on Windows
NT?

Douglas Wilson

From vxwexplo-errs@csg.lbl.gov  Thu Nov 21 03:17:19 2002
From: Syed Rahman <miftahur_rahman@yahoo.com>
Date: Thu Nov 21 03:17:20 PST 2002
Subject: Problems with "taskOptionsGet"

--0-132054248-1037877436=:25479
Content-Type: text/plain; charset=us-ascii

Hello there,

I have a strange problem. According to the VxWorks manual "taskOptionsGet" is used to return the value of the option set.

With reference to this I have two problems:-                                                  i) Sometimes we spawn a task using more than one options.    For example:                                      taskSpawn("samp",100,VX_FP_TASK|VX_NO_STACK_FILL ,200,tsm2,0..)         IN THIS CASE our output will be the sum of the two options. How shall we identify -- which options were set from the SUM?

ii) This is a practical problem I am facing. When I give :          taskSpawn("samp",100,VX_FP_TASK,2000,tsm2,0,0,.....);            AND THEN USE "taskOptionsGet", I get "0xC" as answer. Itried with the other options as well and have found that 4 gets added to each one of them.

It will be very helpful if anyone can provide any solution.

Thanking you in advance,

Miftahur

---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
--0-132054248-1037877436=:25479
Content-Type: text/html; charset=us-ascii

<P><FONT size=3>Hello there,</FONT></P>
<P><FONT size=3>I have a strange problem. According to the VxWorks manual "taskOptionsGet" is used to return the value of the option set.</FONT></P>
<P><FONT size=3>With reference to this I have two problems:-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;  i) Sometimes we spawn a task using more than one options.&nbsp;&nbsp;&nbsp; For example:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;  taskSpawn("samp",100,VX_FP_TASK|VX_NO_STACK_FILL ,200,tsm2,0..)&nbsp;</FONT><FONT size=3>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IN THIS CASE our output will be the sum of the two options. How shall we identify -- which options were set from the SUM?</FONT></P>
<P><FONT size=3>ii) This is a&nbsp;practical problem I am facing. When I give :&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; taskSpawn("samp",100,VX_FP_TASK,2000,tsm2,0,0,.....);&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;  AND THEN USE "taskOptionsGet", I get "0xC" as answer. Itried with the other options as well and have found that 4 gets added to each one of them.</FONT></P>
<P><FONT size=3>It will be very helpful if anyone can provide any solution.</FONT></P>
<P><FONT size=3>Thanking you in advance,</FONT></P>
<P><FONT size=3>Miftahur</FONT></P><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://rd.yahoo.com/mail/mailsig/*http://mailplus.yahoo.com">Yahoo! Mail Plus</a> - Powerful. Affordable. <a href="http://rd.yahoo.com/mail/mailsig/*http://mailplus.yahoo.com">Sign up now</a>
--0-132054248-1037877436=:25479--

From vxwexplo-errs@csg.lbl.gov  Thu Nov 21 04:03:20 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Thu Nov 21 04:03:21 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Thu Nov 21 04:03:18 PST 2002

        Subject: Re: [q] assemble error problem
        Subject: sound blaster device/driver
        Subject: VxWorks symbol table problem
        Subject: Re: Ram disk on non-memory mapped NVRAM.
        Subject: Booting Application From VME PROM Board using MV2604
        Subject: Re: FEC0 works well with 10M HD, but get error with 10M FD
        Subject: Re: FEC0 works well with 10M HD, but get error with 10M FD
        Subject: How can I get the list of routines provided by BSP?
        Subject: 82557-559 ethernet driver
        Subject: Tornado 2 proj build leaves residual stderr file in bsp directory
        Subject: Re: Tornado 2 proj build leaves residual stderr file in bsp directory
        Subject: memory allocation  MALLOC ISSUE
        Subject: Re: How many byte do you know VxWorks BSP Image size?
        Subject: Re: When should vxWorks.st load drivers from endDevTbl?
        Subject: ethernet drivers
        Subject: vision click + powerpc 750
        Subject: Re: Changing current directory on simulator, Tornado 2 on Windows NT
        Subject: how to get BSP for AMD SC520
        Subject: Starting DHCP in applications
        Subject: Re: Changing current directory on simulator, Tornado 2 on Windows
        Subject: Re: Starting DHCP in applications
        Subject: Re: ATTRACT HOT SEXY WOMEN EASY WITH PHEROMONES (READ MORE)        ffffffffffffffffffff         [1/2]
        Subject: Re: Changing current directory on simulator, Tornado 2 on Windows NT

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: [q] assemble error problem
Date: Tue, 19 Nov 2002 12:40:53 -0500
From: Joe Durusau <joseph.a.durusau@lmco.com>
Organization: Lockheed Martin Corporation
Message-ID: <3DDA77A5.196FB6A7@lmco.com>
References: <4753b4b1.0211190931.4b8d034c@posting.google.com>

Daniel KWAK wrote:
> 
> Hi
> 
> I am new to vxworks environment, using
> - tornado ver 2.0 (vxworks 5.4)
> - wind web server 1.0
> - tornado for managed switches 2.0
> 
> I was trying to build a bootable vxworks image,
> and got the following error message in compiling.
> 
> By the way, building the same source was OK
> when I installed only tornado (no wind web server, no TMS).
> It seems there might be some error in compile option,
> or conflict between tornado ver2.0 and TMS.
> 
> Any advice appreciated,
> Best regards,
> 
> ccppc -c -g -mcpu=860 -ansi -nostdinc  -fvolatile -fno-builtin
> -fno-for-scope -P -x assemb
> ler-with-cpp -IC:\Tornado\target\proj\111
> -IC:\Tornado\target\config\mpc850 -IC:\Tornado\t
> arget\h          -IC:\Tornado\target\config\comps\src
> -IC:\Tornado\target\src\drv      -DCPU=PPC860 -
> DPRJ_BUILD -g -O  C:\Tornado\target\config\mpc850\romInit.s -o
> romInit.o
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s: Assembler messages:
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3284: Error:
> Unrecognized opcode: `typedef'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3285: Error: Rest of
> line ignored. First ign
> ored character is `{'.
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3286: Error:
> Unrecognized opcode: `uint32'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3287: Error:
> Unrecognized opcode: `uint32'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3288: Error: Rest of
> line ignored. First ign
> ored character is `}'.
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3290: Error:
> Unrecognized opcode: `typedef'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3291: Error: Rest of
> line ignored. First ign
> ored character is `{'.
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3292: Error:
> Unrecognized opcode: `uint8'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3293: Error:
> Unrecognized opcode: `uint32'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3294: Error:
> Unrecognized opcode: `uint32'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3295: Error:
> Unrecognized opcode: `uint32'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3296: Error:
> Unrecognized opcode: `sect_desc
> r'
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:3297: Error: Rest of
> line ignored. First ign
> ored character is `}'.
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:5233: Warning: operand
> out of range (65536 n
> ot between -32768 and 65535)
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca01576.s:5353: Warning: operand
> out of range (65536 n
> ot between -32768 and 65535)
> ccppc: Internal compiler error: program as got fatal signal 1
> make: *** [romInit.o] Error 0x1
> 
> Done.

I would look at  romInit.s .  It seems to have somehow gotton 
some C code included into it, and it is supposed to be a pure
assembler file.

Speaking only for myself,

Joe Durusau

---------------------------

Newsgroups: comp.os.vxworks
Subject: sound blaster device/driver
Date: Wed, 20 Nov 2002 15:54:25 +0100
From: Christophe Rabourg <christophe.rabourg@gaci.fr>
Organization: GACI
Message-ID: <3DDBA221.11EDAD6D@gaci.fr>

Does somebody know if a device/driver for a sound blaster compatible
board is available under VxWorks.

Thanks.

- -- 
Christophe Rabourg                   6 Av. Norvege BP46
crabourg@gaci.fr      G  A  C  I     91942 Courtaboeuf France
+33 1 69071686                       http://www.gaci.fr

---------------------------

Newsgroups: comp.os.vxworks
Subject: VxWorks symbol table problem
Date: Wed, 20 Nov 2002 16:41:22 +0100
From: Christian Weber <christian.weber@ires.in2p3.fr>
Organization: ires
Message-ID: <3DDBAD22.8DB291EB@ires.in2p3.fr>

Hello,

I've trying to generate a vxWorks kernel for PPC604 target. I've
compiling
on a debian Linux PC with gcc.
While compiling, everything looks fine until generation of vxWorks.sym.
Then make gives an error 1. Obviously the xsym command failed.
Can anybody tell me why ?

Many thanks

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Ram disk on non-memory mapped NVRAM.
Date: Wed, 20 Nov 2002 18:22:29 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$9vuv5h$mz8$1@lnews.actcom.co.il>
References: <5e76a7d7.0211200710.de97c13@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Dan Smith" <dansmith_1@yahoo.com> wrote in message
news:5e76a7d7.0211200710.de97c13@posting.google.com...
> The PowerCoreCPCI-680 board we are using has NVRAM that is not mapped
> to the main processor's address space.
>
> Is there a way to create a RAM Disk on this type of NVRAM? I know
> about ramDiskDevCreate but it requires a starting memory address.
> Since the NVRAM in question is non-memory mapped I don't have a
> starting address in the main processor's address space.
>
> The access to the NVRAM is 8-bit wide and indirect. To access a
> location within the NVRAM device:
> 1. Write the lower address byte to FE000073  (write-only).
> 2. Write the higher address byte to FE000075  (write-only).
> 3. Read or write data byte sized from or to FE000077.
>
>
> Thanks
>
> Dan Smith
> Telephonics Wireless Corporation
> Melbourne, FL

Sounds like easy enough job to rewrite the Ram disk driver to access
indirectly as you specified. The ram disk driver is delivered in source code
form (one of a very few) in VxWorks.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Booting Application From VME PROM Board using MV2604
Date: 20 Nov 2002 08:36:49 -0800
From: hugoitt@yahoo.com (Hugo Lucero)
Organization: http://groups.google.com/
Message-ID: <7f27b767.0211200836.7846b693@posting.google.com>

We have a PowerPC mv2604 board with 1 Meg of Flash and 8 Meg of PROM
on board.
My problem is that I want to boot vxWorks and my application from PROM
but my
application will exceed the 8 Meg Limit on the onboard PROM even when
compressed.

My question is: Can I buy a VME PROM board and have the Boot PROM
download the application from the external PROM board? Is this
doable??

A fellow engineer thinks their is an address limit that the Boot Prom
can access, specifically the 8 Meg address space that resides on
board.

thanks,

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: FEC0 works well with 10M HD, but get error with 10M FD
Date: Wed, 20 Nov 2002 08:48:39 -0800
From: "Dan Gold" <gold@ensemble.com>
Organization: Mailgate.ORG Server - http://www.Mailgate.ORG
Message-ID: <argef6$7oj$1@newsreader.mailgate.org>
References: <34f7f684.0211191605.daaab05@posting.google.com>
Sender: gold@ensemble.com

"Yan X." <yanxiu@sbcglobal.net> wrote in message
news:34f7f684.0211191605.daaab05@posting.google.com...
> hi,
> my platform is MPC8260, m8260FccEnd.c is used as the driver of FEC, I
> have configured FEC0 with diffrent flag set in configNet.h.
>
> FEC0 works well with the following flag set,
>
> 1) 0x00: AN_ON;

So you auto-negotiate speed and duplex and everything works.  After doing
this, what does your PHY device say it negotiated for link speed and duplex
?   And which PHY device are you using ?

> 2) 0x0D: AN_OFF + 10M + HalfDuplex;

So if you don't auto-negotiate but force the other side to 10Base-T and HD,
you are ok.

> but does works well with the flag of 0x19: AN_OFF + 10M + FullDuplex.

So when you try and force the other side to FD, it doesn't work.  It sounds
like whatever you are plugging into (hub or whatever) is not capable of
doing full duplex.

  hth,
   Dan Gold   gold@ensemble.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: FEC0 works well with 10M HD, but get error with 10M FD
Date: Wed, 20 Nov 2002 08:54:41 -0800
From: "Dan Gold" <gold@ensemble.com>
Organization: Mailgate.ORG Server - http://www.Mailgate.ORG
Message-ID: <argeqg$80s$1@newsreader.mailgate.org>
References: <34f7f684.0211191605.daaab05@posting.google.com> <argef6$7oj$1@newsreader.mailgate.org>
Sender: gold@ensemble.com

" I " <gold@ensemble.com> wrote in message
news:argef6$7oj$1@newsreader.mailgate.org...
> > but does works well with the flag of 0x19: AN_OFF + 10M + FullDuplex.
>
> So when you try and force the other side to FD, it doesn't work.  It
sounds
> like whatever you are plugging into (hub or whatever) is not capable of
> doing full duplex.

I forgot to add - make sure if you're in FD mode that the driver is setting
FPSMR[LPB] and FPSMR[FDE].  Or if you don't have the driver source, just
dump the FPSMR to make sure they are set.

  hth,
   Dan Gold   gold@ensemble.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: How can I get the list of routines provided by BSP?
Date: 20 Nov 2002 10:23:13 -0800
From: yangliang_mr@hotmail.com (Liang Yang)
Organization: http://groups.google.com/
Message-ID: <4f57a77f.0211201023.2e9a9943@posting.google.com>

Hi,

VxWorks reference manual only lists the
library routines provided by vxWorks
itsself, if I want to use the library
routines included in BSP directly,
how can I get the list of these kind
of routines in BSP?

Thanks.

Liang

---------------------------

Newsgroups: comp.os.vxworks
Subject: 82557-559 ethernet driver
Date: Wed, 20 Nov 2002 12:49:05 -0700
From: "pandari" <pandari@asu.edu>
Organization: Arizona State University
Message-ID: <argoth$ie0$1@news.asu.edu>

Hello,

I have a problem concerning the 82559 driver. It goes like this. We have a
motherboard from motorola called Low Profile embedded controller (LoPEC). We
make use of two ethernet adaptors for our project. One ethernet adaptor is
an on-board 82559ER adaptor and the other one (82559) is plugged into the
PCI slot. The operating system that I am working on is called DEOS (Digital
engine operating system from honeywell). This operating system is a real
time operating system similar to vxworks.

Some one has modified the linux 82557-559 ethernet driver to suit DEOS and
while doing it they have taken off the multi-interface support of the linux
driver. If a driver is said to support multi-interface, it means that a
single driver can drive more than one ethernet device. The modified driver
can only drive one ethernet device now (on-board 82559ER device).

What modifications are necessary inorder to make the driver work for the
82559 device that is plugged into the PCI slot and not work for the on-board
82559ER keeping the driver a single interface thing?

Thanks.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tornado 2 proj build leaves residual stderr file in bsp directory
Date: 20 Nov 2002 13:16:53 -0800
From: wolf.byte@verizon.net (Neil Stephenson)
Organization: http://groups.google.com/
Message-ID: <ad736b06.0211201316.36583017@posting.google.com>

Hello,

Am newbie to vxWorks bsp develoment and looking for assistance on how
to squelch the creation of an empty stderr file in the bsp directory.
This is happening during project build of the vxWorks image. The empty
stderr file is being created on both Solaris and Windows platforms
while using either the GUI or command line (bsp2proj.tcl) project
build invocations.

Also, just discovered recently the supporting WindRiver Field Eng's
phone has been disconnected. At the moment I have not contact person.

Thank you for your time...

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2 proj build leaves residual stderr file in bsp directory
Date: Wed, 20 Nov 2002 22:15:30 GMT
From: "drdiags" <drdiags@attbi.com>
Organization: AT&T Broadband
Message-ID: <1QTC9.66065$P31.33130@rwcrnsc53>
References: <ad736b06.0211201316.36583017@posting.google.com>

Neil,

Depends on how comfortable you are with Tcl. In the
"host/resource/tcl/app-config/Project/prjBuildLib.tcl" file
there is the following in the prjBuild procedure:

    if {[catch "eval exec $cmd > stdout 2> stderr" errMsg]} {
        cd $dir
        error $errMsg
    }

    If the evaluated $cmd was okay, no error output is re-directed to
stderr, but why isn't there a stdout file also? Anyway, you could try making
a
copy of the above and remove the redirection of any error message. Just let
it pass through to errMsg, since it will be printed out in the error call if
the catch
detects an error return. The command-line build eventually calls the same
procedure, so GUI or command-line eventually comes to this proc. Also,
 a grep of all the *.tcl files shows various places where stderr is sent
error messages,
so if this isn't your culprit........ HTH

"Neil Stephenson" <wolf.byte@verizon.net> wrote in message
news:ad736b06.0211201316.36583017@posting.google.com...
> Hello,
>
> Am newbie to vxWorks bsp develoment and looking for assistance on how
> to squelch the creation of an empty stderr file in the bsp directory.
> This is happening during project build of the vxWorks image. The empty
> stderr file is being created on both Solaris and Windows platforms
> while using either the GUI or command line (bsp2proj.tcl) project
> build invocations.
>
> Also, just discovered recently the supporting WindRiver Field Eng's
> phone has been disconnected. At the moment I have not contact person.
>
> Thank you for your time...

---------------------------

Newsgroups: comp.os.vxworks
Subject: memory allocation  MALLOC ISSUE
Date: Thu, 21 Nov 2002 01:23:03 GMT
From: "Jim McKain" <jim_mckain@nltek.com>
Organization: AT&T Broadband
Message-ID: <XzWC9.95906$QZ.14473@sccrnsc02>

HI All,

I'm running a project and we have ported a large windows application (10MB
of code) and are running into memory fragmentation problems.   [PPC, 860
arch, C++, OOD, 32MB RAM, Tornado 2.0]

I know that the OS is notorious for poor memory management. But does anyone
have a third party MALLOC routine that does best fit or some other smarter
way of allocation.

Has anyone used a Virtual MMgr with the 860 before?

Any help or pointers to solutions are appreciated.

- -Jim

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How many byte do you know VxWorks BSP Image size?
Date: 20 Nov 2002 18:57:46 -0800
From: patrick.klingele@siemens.com (Patrick)
Organization: http://groups.google.com/
Message-ID: <2450ac08.0211201857.245ab2fa@posting.google.com>
References: <107f9c39.0211181826.e374715@posting.google.com> <3DD9E8BF.B300955B@sepro-robotique.com>

Hi Emmanuel,
It seams that you are quite familiar with building bootable vxWorks 
images. I'm trying this now for about 3 days with mixed success.
I'm using T2.0.2/VxWorks5.4 and a target "Radisys board with intel 
80486 CPU and 32MB ram".

I was successfull in building a/the little demo application using 
the makefiles in the config/BSP folder. I get a compressed vxWorks 
running the little demo app. This compressed image is then put on 
floppy with 

mkboot a: vxWorks.app_rom 

this is a duplicated target from vxWorks.st_rom without the standalone 
feature. Boot the target system and a few seconds later the little 
demo is running. Great!

This was all done by using the make files on the command line.
Now I want to do the same thing from the IDE by selecting the build 
target vxWorks_romCompressed.
I added the very same little demo app to "usrAppInit.c" and build 
the image. I put it on the floppy the same way:

mkboot a: vxWorks_romCompressed

boot the target and after loading the image the screen stays black 
and the target system resets itself and does a warm boot. And the 
loading starts again.

I tried already to modify (correct?) the location for the data segment 
of the final linker stage (linking romInit.o, romStart.o, etc )(which 
was the same value 0x8000 as for the text segment) to a value behind 
the rom code (now value 0x10000). Same "reset" effect.

Is this target build from the IDE supposed to work correctly?
Do you have any suggestions? I would appreciate it very much.
BTW: My host is a Win2000 system with SP2.

Thanks Patrick

Emmanuel Herbreteau <eherbreteau@sepro-robotique.com> wrote in message news:<3DD9E8BF.B300955B@sepro-robotique.com>...
> Hi,
> 
> It depends on the type of bootrom. If you need
> to boot your target from an ATA disk, such as
> IDE or CompactFlash, you can build your custom
> bootrom with the minimum number of modules
> (core, ATA driver, DosFs2, etc...).
> 
> In this case, you should be able to make it
> with only 300 KB uncompressed. With a compressed
> image, a 256KB flash should do it as well, but
> it use a small amount of RAM (the size of the uncompressed
> code) and it's also slower (the code need to be unzip).
> 
> A good choice, in my opinion : a 512 KB flash bootrom.
> 
> (On our MPC823, it only use 223 KB to boot from ATA and DosFS1)
> 
> Regards
> Emmanuel.
> 
> jeff wrote:
> > my target cpu is ppc850.
> > i'd like to define boot rom size.
> >  currently, compile result: about 600-700kbyte
> > i want that less than 512kbyte
> > do you know this method?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: When should vxWorks.st load drivers from endDevTbl?
Date: Tue, 19 Nov 2002 16:26:02 -0800
From: "Dan Gold" <gold@ensemble.com>
Organization: Mailgate.ORG Server - http://www.Mailgate.ORG
Message-ID: <arekru$9rs$1@newsreader.mailgate.org>
References: <a7b7bb67.0211191617.5ac65021@posting.google.com>
Sender: gold@ensemble.com

"frankg" <FrankGleeson@motorola.com> wrote in message
news:a7b7bb67.0211191617.5ac65021@posting.google.com...
> In the bootrom code in file bootConfig.c. The function bootLoad()
> tries to locate an END driver. If it find one it calls muxDevStart
> thereby initializing the driver. I can set a breakpoint on my drivers
> init routine motFccStart() and see that the call was from
> bootConfig.c.

bootConfig.c is only used by the bootrom.  It is not compiled into the
system/application image.  Thus it will have the same function names
(usrInit, usrRoot) as usrConfig.c.

> If I set that same breakpoint in the system image it is never called.
> I can not locate a function that loads the END drivers. What *really*
> confuses me is that the FCCs ethernet works beautifully from the
> system
> image. Does this mean the system image is relying on the bootrom setup
> and it is just somehow working?
>
> Is there a predefined location in the vxWorks.st build for doing an
> END driver table initialization? Or do I just need to add the calls
> somewhere appropriate?

In usrConfig.c, there is a call to usrNetInit(), located in
target/src/config/usrNetwork.c, that (IIRC) gets included in usrExtra.c.
That is where the endDevTbl[] is parsed and mux devices loaded.

  hth,
   Dan Gold    gold@ensemble.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: ethernet drivers
Date: 20 Nov 2002 20:24:51 -0800
From: rkanumula@yahoo.com (arkay)
Organization: http://groups.google.com/
Message-ID: <e840ba3f.0211202024.2e27e0be@posting.google.com>

I am having DE 528CT card connected to PC ,
I am working on vxworks,please specify the type of BSD ethurnet drivers 
used

---------------------------

Newsgroups: comp.os.vxworks
Subject: vision click + powerpc 750
Date: 20 Nov 2002 21:54:17 -0800
From: abhishekbhattacharya@rediffmail.com (Abhishek)
Organization: http://groups.google.com/
Message-ID: <30221a01.0211202154.44e144e9@posting.google.com>

Hi
   We are developing a powerpc 750 board with vision click as a
debugger.
   Recently we are facing a problem related to Vision probe II.
   Whenever we connect vprobe to the board it always drives HRESET low
thereby permenantly asserting it!This behaviour is displayed even when
there is no power supply to the probe.On the other hand,the Hreset pin
does not show any shorting to the ground.
   We went to the configuration menu of vclick and changed cpu reset
to Sreset and disconnected Hreset.Following that we were able to go to
BKM prompt,load s/w codes and even display all registers(cpu).But we
were unable to execute the code by issuing go command.The system
always hangs when we try to do so!
    Can anybody throw some light of how this can be solved??Is it
possible to work by disabling Hreset from vCLICK/PROBE??
    thanks in advance
                       Abhishek
                       S/w engineer
                       ACL India

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Changing current directory on simulator, Tornado 2 on Windows NT
Date: 20 Nov 2002 22:20:23 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211202220.56a069b1@posting.google.com>
References: <argcgb$p7i$1@overload.lbl.gov> <newscache$rywv5h$e29$1@lnews.actcom.co.il>

> Looks like reading through the manuals is out of fasion these days ;-)

Our replies are obviously getting there in less time than it takes to
unwrap the shrink wrap on the books ;-)

---------------------------

Newsgroups: comp.os.vxworks
Subject: how to get BSP for AMD SC520
Date: 20 Nov 2002 22:28:41 -0800
From: role_y@163.net (Role_y)
Organization: http://groups.google.com/
Message-ID: <2fc0d90d.0211202228.24eaaa84@posting.google.com>

I want to run VxWorks 5.4 on AMD SC520 Eva. board, but don't know
where to get its BSP. I know Wind River has a BSP for AMD SC400, and I
am wondering if this BSP can work well on my SC520 board. Or anyone
else know there is a separate BSP for SC520?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Starting DHCP in applications
Date: Thu, 21 Nov 2002 15:40:50 +0800
From: "Yung" <general_miller@yahoo.com>
Organization: IMS Netvigator
Message-ID: <ari2m8$r761@imsp212.netvigator.com>

Hi experts,

in an attempt to use DHCP client on an embedded system, I have managed to
include all the DHCP components in the project environment. The system
starts up properly and is able to negotiate with the DHCP server to retrieve
the IP address.
The next step I want to do is to delay the DHCP start-up portion such that
DHCP can only start in subsequent application (instead of during start up),
say, when end-user chooses to do so.
Is there a simple method to achieve this?

It is a MIPS platform with vxWorks 5.4 (Tornado 2.0)
Thanks a lot in advance.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Changing current directory on simulator, Tornado 2 on Windows
 NT
Date: Thu, 21 Nov 2002 08:13:17 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <ari4is$lpc$1@venus.btinternet.com>
References: <argcgb$p7i$1@overload.lbl.gov> <newscache$rywv5h$e29$1@lnews.actcom.co.il> <488e459a.0211202220.56a069b1@posting.google.com>

John wrote:
>>Looks like reading through the manuals is out of fasion these days ;-)
> 
> 
> Our replies are obviously getting there in less time than it takes to
> unwrap the shrink wrap on the books ;-)

No: the required book is being used to balance the ICE unit
attached to the prototype board :-)

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Starting DHCP in applications
Date: Thu, 21 Nov 2002 08:39:01 +0000 (UTC)
From: Johan Borkhuis <JBorkhuis@proxim.com>
Organization: Proxim Corp.
Message-ID: <Xns92CD61828908Bjborkhuisproximcom@192.19.193.66>
References: <ari2m8$r761@imsp212.netvigator.com>

"Yung" <general_miller@yahoo.com> wrote:

> Hi experts,
> 
> in an attempt to use DHCP client on an embedded system, I have managed
> to include all the DHCP components in the project environment. The
> system starts up properly and is able to negotiate with the DHCP
> server to retrieve the IP address.
> The next step I want to do is to delay the DHCP start-up portion such
> that DHCP can only start in subsequent application (instead of during
> start up), say, when end-user chooses to do so.
> Is there a simple method to achieve this?

There are a couple of ways to do this. The DHCP application is started by 
the prjParams.c. You could remove the init call from there, but this file 
is regenerated after you save your project, so this is not really an 
option. The data to generate this file can be found in the CDF files in 
target\config\comps\vxWorks. Search for the init call and comment this 
line out. But you calso look for the function taht is called in the 
directory target\config\comps\src and change this function.

Kind regards,
        Johan

- -- 
        o o o o o o o . . .   _____________________________
       o      _____           ||    Johan Borkhuis        |
     .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
    >(________|__|_[_________]_|__________________________|
    _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
=== VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ATTRACT HOT SEXY WOMEN EASY WITH PHEROMONES (READ MORE)        ffffffffffffffffffff         [1/2]
Date: Thu, 21 Nov 2002 10:56:37 +0200
From: almonious@hotmail.com
Message-ID: <as7ptug145npqtegm2sno6bg32nr8gr77f@4ax.com>
References: <HBvC9.277622$LK5.3610295@newsfeed.slurp.net>

We program under Tornado.. attracting hot sexy women is child's play 
after that! :-)

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Changing current directory on simulator, Tornado 2 on Windows NT
Date: Thu, 21 Nov 2002 13:12:54 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$b7bx5h$8lb$1@lnews.actcom.co.il>
References: <argcgb$p7i$1@overload.lbl.gov> <newscache$rywv5h$e29$1@lnews.actcom.co.il> <488e459a.0211202220.56a069b1@posting.google.com> <ari4is$lpc$1@venus.btinternet.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:ari4is$lpc$1@venus.btinternet.com...
> John wrote:
> >>Looks like reading through the manuals is out of fasion these days ;-)
> >
> >
> > Our replies are obviously getting there in less time than it takes to
> > unwrap the shrink wrap on the books ;-)
>
> No: the required book is being used to balance the ICE unit
> attached to the prototype board :-)

Now who ever said these tons of printed manual from WR are useless, LOL ;-)

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Thu Nov 21 22:52:14 2002
From: "Rajat Asthana" <rajatm@delhi.tcs.co.in>
Date: Thu Nov 21 22:52:15 PST 2002
Subject: want to know all the available drives of the system

hello all,
i am rajat just started working on vxworks, i have a problem actually i want
to know all the available drives of the system , on window NT we have system
calls like "GetLogicalDriveStrings" which returns all the system drives
list. but in vxworks we dont have any corresponding call.
in vxworks we have to creat devices in which we associate a driver number
against that device, like driver number of floppy disk ranges (0 - 3) .
so the problem is that how i will be able to know that whether floppy disk
and cd drive is present in the system or not and if present then how to
assign them a driver number.
waiting for ur kind and early response.
regards
Rajat

From vxwexplo-errs@csg.lbl.gov  Fri Nov 22 04:03:15 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Fri Nov 22 04:03:17 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Fri Nov 22 04:03:13 PST 2002

        Subject: UDP max data length ?
        Subject: Re: How can I get the list of routines provided by BSP?
        Subject: Re: UDP max data length ?
        Subject: Re: memory allocation  MALLOC ISSUE
        Subject: Re: UDP max data length ?
        Subject: Re: Error message after booting
        Subject: Re: how to get BSP for AMD SC520
        Subject: Re: UDP max data length ?
        Subject: PCI I/O space and memory mapping space?
        Subject: VxSim problem under Solaris
        Subject: multi-interface/single interface 82559 driver- LoPEC (motorola)
        Subject: ifAddrAdd
        Subject: dosfs2-FAT
        Subject: Re: How many byte do you know VxWorks BSP Image size?
        Subject: Tornado 2.2 for X86
        Subject: Tornado 2.2 for target 2.2
        Subject: Tornado 2.2 for target X86
        Subject: Tornado 2.2 for target X86
        Subject: Re: ftp server problem
        Subject: Re: How can I get the list of routines provided by BSP?
        Subject: C++ Standard Library support
        Subject: Re: Any documentation on STL included with vxWorks 5.4.2 (Tornado 2.0.2)
        Subject: Download Procedure

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: UDP max data length ?
Date: Thu, 21 Nov 2002 16:30:33 +0200
From: "Martin Roth" <bmr006@email.mot.com>
Organization: Motorola
Message-ID: <ariqms$ar4$1@newshost.mot.com>

1.I would like to know what is the maximum size of data I can send by using
the sendto() function over a UDP socket. Is it ~ 65Kbytes or it is limited
by the size of MTU ?

2. Is there any limitation for the DATA size over UDP socket in case of
broadcasting over UDP? Is it still 65Kbytes or it is limited by the size of
MTU ?

3. Assume that the receiver receives the data by recvfrom() on UDP socket.
Is there a way to assure that the DATA is received in one block on return
from recvfrom() on UDP socket? Does IP fragmentation/defragmentation assure
this ?  What about broadcast msgs ?

Thanks,
Martin Roth
Mailto:bmr006@email.mot.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How can I get the list of routines provided by BSP?
Date: Wed, 20 Nov 2002 16:36:31 -0500
From: pappajoemamma@pandora.orbl.org
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <eP=bPTM5N1y0IcofXb23M=Z90ZeL@4ax.com>
References: <4f57a77f.0211201023.2e9a9943@posting.google.com>

yangliang_mr@hotmail.com (Liang Yang) wrote:

:(Hi,
:(
:(VxWorks reference manual only lists the
:(library routines provided by vxWorks
:(itsself, if I want to use the library
:(routines included in BSP directly,
:(how can I get the list of these kind
:(of routines in BSP?
:(
:(Thanks.
:(
:(Liang

Look in $WIND_BASE/docs/vxworks/bsp/ "name_of_bsp"

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: UDP max data length ?
Date: Thu, 21 Nov 2002 15:03:47 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <ariski$k19$1@sparta.btinternet.com>
References: <ariqms$ar4$1@newshost.mot.com>

Martin Roth wrote:
> 1.I would like to know what is the maximum size of data I can send by using
> the sendto() function over a UDP socket. Is it ~ 65Kbytes or it is limited
> by the size of MTU ?

It ought to be ~ 65k, UDP datagrams should be fragmented by IP.

> 2. Is there any limitation for the DATA size over UDP socket in case of
> broadcasting over UDP? Is it still 65Kbytes or it is limited by the size of
> MTU ?

Not sure...

> 3. Assume that the receiver receives the data by recvfrom() on UDP socket.
> Is there a way to assure that the DATA is received in one block on return
> from recvfrom() on UDP socket? Does IP fragmentation/defragmentation assure
> this ?  What about broadcast msgs ?

The entire datagram has to be assembled by IP before being passed to
UDP.  Thus it will be returned by a single recvfrom() call.

vxworks might be broken and object to datagrams longer that the
socket buffer size, IIRC some systems don't like >32k datagrams.

Receiving fragmented datagrams requires that the target system have
enough buffer space to receive all of the ethernet frames back to
back.  As the datagram gets longer this gets less and less likely
for systems that incapable of sustaining the network bamdwidth.
If wireless links are present you will lose out badly.

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: memory allocation  MALLOC ISSUE
Date: Thu, 21 Nov 2002 15:15:45 -0000
From: bob schulman <bob@seaweed.com>
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <utpu5183t56uc4@news.supernews.com>
References: <XzWC9.95906$QZ.14473@sccrnsc02>

Jim McKain <jim_mckain@nltek.com> wrote:
> I'm running a project and we have ported a large windows application (10MB
> of code) and are running into memory fragmentation problems.   [PPC, 860
> arch, C++, OOD, 32MB RAM, Tornado 2.0]

> I know that the OS is notorious for poor memory management. But does anyone
> have a third party MALLOC routine that does best fit or some other smarter
> way of allocation.

<commercial plug>
Seaweed Systems (www.seaweed.com) distributes a from-scratch, drop-in
replacement for memLib and its sister libs memPartLib and memShowLib.
This drop-in replacement significantly reduces the fragmentation as
compared with Wind River's allocator. It also does memory leak detection,
memory arena corruption detection, has improved low memory detection and,
in the general case, runs in O(1) time rather than O(n) time (where n
is the size of the free list).
</commercial plug>

Bob Schulman
bob@seaweed.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: UDP max data length ?
Date: Thu, 21 Nov 2002 17:38:52 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$linx5h$gcc$1@lnews.actcom.co.il>
References: <ariqms$ar4$1@newshost.mot.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Martin Roth" <bmr006@email.mot.com> wrote in message
news:ariqms$ar4$1@newshost.mot.com...
> 1.I would like to know what is the maximum size of data I can send by
using
> the sendto() function over a UDP socket. Is it ~ 65Kbytes or it is limited
> by the size of MTU ?
>
The sent packet size limit as the current send buffer size for the given UDP
socket, up until 64Kbytes.
The default socket buffer is 4k, and you need to change it with
setsockoption()
before being able to send larger packets. For the receiver to be able to
receive
a larger then default UDP packet, receive buffer size should be increased
accordingly.
I recommend to incrase the rx buffer to 2X max packet size to avoid packet
loss
that resul tfrom application latency.

> 2. Is there any limitation for the DATA size over UDP socket in case of
> broadcasting over UDP? Is it still 65Kbytes or it is limited by the size
of
> MTU ?
>
The size of DATA is limitted bu socket sen dbuffer size, DATA+UDP+IP is
limitted
by the inherent IPv4 64x1024 bytes limit.

Regarding BROADCAST or MULTICAST however, it is a bad idea to rely on IP
fragmentation, and thus the Max DATA+UDP+IP+MAC packet should not exceed
1500 bytes (standard MTU.
It is my experience that in a broad/multi case scenario, the IP
fragmentation
increases probability of packet loss beyond reasonable.
In certain Multicast applications where large WANs are concerned, it is
recommended
to limit pacet by PathMTU, which is 576 bytes, unless it can be explicitly
discovered.
[Ref: RTP]

> 3. Assume that the receiver receives the data by recvfrom() on UDP socket.
> Is there a way to assure that the DATA is received in one block on return
> from recvfrom() on UDP socket? Does IP fragmentation/defragmentation
assure
> this ?  What about broadcast msgs ?

It is assured that the UDP recvfrom() (or read, or recv) will EITHER receive
the
ENTIRE UDP packet in one peice, or return an ERROR to the receiver, if the
recvfrom() buffer is smaller then the packet stored in socket.
If the socket receve buffer is too small, the packet is discarded with no
diagnostic except the UDP statistics counter.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Error message after booting
Date: Thu, 21 Nov 2002 10:01:22 -0600
From: "cnwebb" <cwebb@maxtc.com>
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <utq0c1eor6126f@corp.supernews.com>
References: <utkt98ousurh40@corp.supernews.com> <H5vo7u.F2C@news.boeing.com>

Thanks, your suggestion worked!

I did have to be careful to ensure that I was using the archive
manipulation tools from the Tornado installation, though.  I have
Cygwin installed on my computer also, and due to my path settings
I was picking the "ar" command from the wrong directory at first.
This resulted in an incompatible archive, and I could not build my
boot.bin microkernel.  After I used explicit paths for the commands,
I had no trouble getting the microkernel built and in booting the board.

Cynthia
- ----------------------------------------------------------------------------
- ----------------------
"Lou Rohan" <L&R&R&1@cec.wustl.edu> wrote in message
news:H5vo7u.F2C@news.boeing.com...
I believe that I have seen this with a 2604 as well, and I think it stems
from the DEC 21140 ethernet driver.  When I tried booting the board with a
Tornado 2.0.2/VxWorks 5.4 kernel, it would do the same thing that yours
does.  I solved it by going back to a Tornado 2.0 installation and replacing
the 2.0 dec21x40End.o object file in the newer 2.02 libPPC604gnuvx.a archive
file.  I think it has something to do with auto negotiation...

This was just a quick fix, you should contact your WR customer support.

Lou (remove &s for proper email addr)

"cnwebb" <cwebb@maxtc.com> wrote in message
news:utkt98ousurh40@corp.supernews.com...
> I am attempting to boot up a PowerPC 750 processor on a
> Motorola MVME2431 board using Tornado 2.0.2 & VxWorks 5.4
>
> I have successfully built the microkernel and flashed it to the board,
> and the board appears to boot normally.  However after the VxWorks
> version information is displayed in my Hyperterminal window, I start
> getting the following error
>          miiPhyInit:  check cable connection
>
> This error continues to be written to the display until I disconnect from
> the target.  I have checked the cable connections on both the host and
> the target, and they are secure.  I have also used the same cables to
> boot up another computer using a previous version of Tornado/VxWorks,
> so I don't believe there is a problem with the cables.
>
> I would appreciate any help in determining the cause and solution of this
> problem.
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: how to get BSP for AMD SC520
Date: Thu, 21 Nov 2002 09:03:22 -0800
From: "Michael R. Kesti" <mkesti@gv.net>
Organization: MK Associates
Message-ID: <3DDD11DA.AAB01500@gv.net>
References: <2fc0d90d.0211202228.24eaaa84@posting.google.com>
Reply-To: mkesti@gv.net

Role_y wrote:

>I want to run VxWorks 5.4 on AMD SC520 Eva. board, but don't know
>where to get its BSP. I know Wind River has a BSP for AMD SC400, and I
>am wondering if this BSP can work well on my SC520 board. Or anyone
>else know there is a separate BSP for SC520?

Call you FAE and/or salesman.  Other may have answers to your questions
but the FAE's and salesman's answers are the only that matter!

- -- 
========================================================================
          Michael Kesti            |  "And like, one and one don't make
                                   |   two, one and one make one."
          mkesti@gv.net            |          - The Who, Bargain

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: UDP max data length ?
Date: Thu, 21 Nov 2002 19:00:08 +0200
From: "Martin Roth" <bmr006@email.mot.com>
Organization: Motorola
Message-ID: <arj3fb$ei0$1@newshost.mot.com>
References: <ariqms$ar4$1@newshost.mot.com> <newscache$linx5h$gcc$1@lnews.actcom.co.il>

Leonid,

Thanks, for the reply.

Our application broadcasts a heartbeat msg (in XML schema) each 60 seconds
to an server running on Linux . The heartbeat msg length is currently ~1400
bytes. We need to extend the format, so the length becomes ~1600 bytes.

Since we are changing the application protocol, we have two alternatives:
1) To proceed broadcasting 1600 bytes UDP msg on UDP socket as before, thus
exceeding the MTU of 1500 bytes.
2) To compress the msg (XML is highly compressible), thus we will broadcast
~500 bytes of compressed XML data

How reliable is solution #1 ?
Martin

"Leonid Rosenboim" <My_1st_name@Consultant.Com> wrote in message
news:newscache$linx5h$gcc$1@lnews.actcom.co.il...
>
> "Martin Roth" <bmr006@email.mot.com> wrote in message
> news:ariqms$ar4$1@newshost.mot.com...
> > 1.I would like to know what is the maximum size of data I can send by
> using
> > the sendto() function over a UDP socket. Is it ~ 65Kbytes or it is
limited
> > by the size of MTU ?
> >
> The sent packet size limit as the current send buffer size for the given
UDP
> socket, up until 64Kbytes.
> The default socket buffer is 4k, and you need to change it with
> setsockoption()
> before being able to send larger packets. For the receiver to be able to
> receive
> a larger then default UDP packet, receive buffer size should be increased
> accordingly.
> I recommend to incrase the rx buffer to 2X max packet size to avoid packet
> loss
> that resul tfrom application latency.
>
> > 2. Is there any limitation for the DATA size over UDP socket in case of
> > broadcasting over UDP? Is it still 65Kbytes or it is limited by the size
> of
> > MTU ?
> >
> The size of DATA is limitted bu socket sen dbuffer size, DATA+UDP+IP is
> limitted
> by the inherent IPv4 64x1024 bytes limit.
>
> Regarding BROADCAST or MULTICAST however, it is a bad idea to rely on IP
> fragmentation, and thus the Max DATA+UDP+IP+MAC packet should not exceed
> 1500 bytes (standard MTU.
> It is my experience that in a broad/multi case scenario, the IP
> fragmentation
> increases probability of packet loss beyond reasonable.
> In certain Multicast applications where large WANs are concerned, it is
> recommended
> to limit pacet by PathMTU, which is 576 bytes, unless it can be explicitly
> discovered.
> [Ref: RTP]
>
> > 3. Assume that the receiver receives the data by recvfrom() on UDP
socket.
> > Is there a way to assure that the DATA is received in one block on
return
> > from recvfrom() on UDP socket? Does IP fragmentation/defragmentation
> assure
> > this ?  What about broadcast msgs ?
>
> It is assured that the UDP recvfrom() (or read, or recv) will EITHER
receive
> the
> ENTIRE UDP packet in one peice, or return an ERROR to the receiver, if the
> recvfrom() buffer is smaller then the packet stored in socket.
> If the socket receve buffer is too small, the packet is discarded with no
> diagnostic except the UDP statistics counter.
>
> --
> -----------------------------------------------------------------------
>    Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
>        Consultant                Email: my first name at consultant dot
com
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: PCI I/O space and memory mapping space?
Date: 21 Nov 2002 09:28:36 -0800
From: yangliang_mr@hotmail.com (Liang Yang)
Organization: http://groups.google.com/
Message-ID: <4f57a77f.0211210928.1501d79e@posting.google.com>

Hi,

Suppose I have a Intel IXP1200 board,
I plug a Sound Card into one of the
PCI slots of this board.

What's the relationship between PCI 
I/O space, board memeory mapping space
and Sound Card address space?

If I want to access joystick game port
in the sound card, which base address
I should use when I know the offset
of this port number?

Can someone give a clear explanation
for these concepts?

Thanks.

Liang

---------------------------

Newsgroups: comp.os.vxworks
Subject: VxSim problem under Solaris
Date: Thu, 21 Nov 2002 19:20:06 +0000
From: Bill Findlay <yaldnifw@blueyonder.co.uk>
Organization: blueyonder (post doesn't reflect views of blueyonder)
Message-ID: <BA02E266.8E4%yaldnifw@blueyonder.co.uk>

I'm having trouble with VxSim/Tornado 2.0.2 under Solaris 8.

I works well when invoked from the Launcher, but I have a requirement to be
able to run it from the command line. When I do this, it fails at once,
taking its parent shell with it. When I capture the error message, I find
that the problem is an uncaught signal 1.

Does anyone else have any experience of this, or any pointers to a solution?

Many thanks.
- --
Bill Findlay

---------------------------

Newsgroups: comp.os.vxworks
Subject: multi-interface/single interface 82559 driver- LoPEC (motorola)
Date: Thu, 21 Nov 2002 13:52:12 -0700
From: "pandari" <pandari@asu.edu>
Organization: Arizona State University
Message-ID: <arjgvv$cei$1@news.asu.edu>

Hello,

I have a problem concerning the 82559 driver. It goes like this. We have a
motherboard from motorola called Low Profile embedded controller (LoPEC). We
make use of two ethernet adaptors for our project. One ethernet adaptor is
an on-board 82559ER adaptor and the other one (82559) is plugged into the
PCI slot. The operating system that I am working on is called DEOS (Digital
engine operating system from honeywell). This operating system is a real
time operating system similar to vxworks.

Some one has modified the linux 82557-559 ethernet driver to suit DEOS and
while doing it they have taken off the multi-interface support of the linux
driver. If a driver is said to support multi-interface, it means that a
single driver can drive more than one ethernet device. The modified driver
can only drive one ethernet device now (on-board 82559ER device).

What modifications are necessary inorder to make the driver work for the
82559 device that is plugged into the PCI slot and not work for the on-board
82559ER keeping the driver a single interface thing?

Thanks.

---------------------------

Newsgroups: comp.os.vxworks
Subject: ifAddrAdd
Date: Thu, 21 Nov 2002 22:02:41 +0100
From: Ralf Hoppe <ralf.hoppe@arcor.de>
Organization: Arcor
Message-ID: <3DDD49F1.8010207@arcor.de>
Reply-To: ralf.hoppe@ieee.org

Hi, i'am a pure novice with respect to the VxWorks network functions. 
The question that i have is, how does the function ifAddrAdd() work. Is 
it possible to assign two IP addresses (from the same network) to one 
interface device? And if so - can i open two sockets, one gets the 
traffic to the first IP address and the other receives the traffic to 
the second IP address? The other question related to that topic is: are 
there any side effects of that assignment of two addresses to one 
interface which should an network administrator have in mind if he 
configures the network (e.g. any ARP or ROUTING effects)?

Hope anybody knows an answer!?

Bye, Ralf

---------------------------

Newsgroups: comp.os.vxworks
Subject: dosfs2-FAT
Date: 21 Nov 2002 14:42:52 -0800
From: yli@transdimension.com (liyi)
Organization: http://groups.google.com/
Message-ID: <c994781b.0211211442.409ddca1@posting.google.com>

Hi, 

I have a hard driver which is formatted as FAT32 in windows 2000. But
when I put it in vxWorks system and do a ls, it show me all those old
files already deleted. After I did a dosFsVolFormat, those garbage
dispear, but again windows do not recognize that disk.
Why did that happen, aren't they all FAT?

Thanks,

Yi

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How many byte do you know VxWorks BSP Image size?
Date: 21 Nov 2002 15:55:49 -0800
From: patrick.klingele@siemens.com (Patrick)
Organization: http://groups.google.com/
Message-ID: <2450ac08.0211211555.57025ef2@posting.google.com>
References: <107f9c39.0211181826.e374715@posting.google.com> <3DD9E8BF.B300955B@sepro-robotique.com> <2450ac08.0211201857.245ab2fa@posting.google.com> <3ZCXdZHXkR39EAT2@wtoram.co.uk>

Hi Wade Oram,
thanks for your help. Unfortunately this is not the cause for my problem. 
The location you pointed out is inside the ROM_RESIDENT target. But I tried 
the change it in the romCompressed target from originaly ROM_ENTRY (which I
 thought should be correct) to SYS_ENTRY. It gave me linker error. 
So I'm back to square 1. 
I followed another comment to change the inflate-call in romStart.c. 
Remove the ROM_DATA  macro because it resolved to a negative/wrong source 
address.

    /* decompress the main image */

/*    if (UNCMP_RTN (ROM_DATA(binArrayStart),
		UNCACHED(RAM_DST_ADRS),
		&binArrayEnd - binArrayStart) != OK)
*/
    if (UNCMP_RTN ((UINT *)binArrayStart,
		UNCACHED(RAM_DST_ADRS),
		&binArrayEnd - binArrayStart) != OK)
	return;

But still no success.

Any further help available??

Patrick

Wade Oram <news@wtoram.co.uk> wrote in message news:<3ZCXdZHXkR39EAT2@wtoram.co.uk>...
> In message <2450ac08.0211201857.245ab2fa@posting.google.com>, Patrick 
> <patrick.klingele@siemens.com> writes
> >Hi Emmanuel,
> >It seams that you are quite familiar with building bootable vxWorks
> >images. I'm trying this now for about 3 days with mixed success.
> >I'm using T2.0.2/VxWorks5.4 and a target "Radisys board with intel
> >80486 CPU and 32MB ram".
> >
> >I was successfull in building a/the little demo application using
> >the makefiles in the config/BSP folder. I get a compressed vxWorks
> >running the little demo app. This compressed image is then put on
> >floppy with
> >
> >mkboot a: vxWorks.app_rom
> >
> >this is a duplicated target from vxWorks.st_rom without the standalone
> >feature. Boot the target system and a few seconds later the little
> >demo is running. Great!
> >
> >This was all done by using the make files on the command line.
> >Now I want to do the same thing from the IDE by selecting the build
> >target vxWorks_romCompressed.
> >I added the very same little demo app to "usrAppInit.c" and build
> >the image. I put it on the floppy the same way:
> >
> >mkboot a: vxWorks_romCompressed
> >
> >boot the target and after loading the image the screen stays black
> >and the target system resets itself and does a warm boot. And the
> >loading starts again.
> >
> >I tried already to modify (correct?) the location for the data segment
> >of the final linker stage (linking romInit.o, romStart.o, etc )(which
> >was the same value 0x8000 as for the text segment) to a value behind
> >the rom code (now value 0x10000). Same "reset" effect.
> >
> >Is this target build from the IDE supposed to work correctly?
> >Do you have any suggestions? I would appreciate it very much.
> >BTW: My host is a Win2000 system with SP2.
> >
> 
> I don't know whether it is still the case with Tornado 2.0.2 but with 
> Tornado 2 there was a fault with rule for the vxWorks_romCompressed 
> target. The entry point for the image was set to 'SYS_ENTRY' when it 
> should have been set to 'ROM_ENTRY'.
> 
> I believe this fault occurred in %WIND_BASE%\target\h\make\rules.vxWorks 
> at line 109 (or thereabouts).
> 
> If the fault persists in 2.0.2, this may be your problem.
> 
> 
> 
> You should also be aware that the rom_compressed image load into the 
> RAM_HIGH_ADRS which is perversely in low memory and therefor there is a 
> limit on the maximum size of the compressed image (it can't extend 
> beyond the 640k lower memory limit). Your are obviously not encountering 
> this problem at present but it is one to be aware of - it took me quite 
> a while to work out what was going on when this one struck me!
> 
> HTH

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tornado 2.2 for X86
Date: 22 Nov 2002 01:39:10 GMT
From: maheshv26@aol.com (Maheshv26)
Organization: AOL http://www.aol.com
Message-ID: <20021121203910.05840.00005962@mb-ms.aol.com>

Hi :

My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
target Intel X86 and for windows host.
I have created a Bootrom Image for Network configuration and When i try to boot
the kernel through the floppy disk, the screen becomes blank and it
automatically reboots. 

I will be happy if somebody can shed some on it. Also, is there any way to
debug and see what is going on underneath the hood.  

The configuration and software versions are as follows:
VxWorks - 5.5
Tornado - 2.2
CPU - PENTIUM
C++Compiler - g++pentium (version - 2.93)
Host - Windows 2000.
Ethernet Driver - fei82557End Intel Ethernet Driver.

The config.h is configured using these macros
INCLUDE_NETWORK
INCLUDE_END,
INCLUDE_FEI_END,
INCLUDE_FTP,
INCLUDE_FTP_SERVER.

thanks
Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tornado 2.2 for target 2.2
Date: 22 Nov 2002 02:05:36 GMT
From: maheshv26@aol.com (Maheshv26)
Organization: AOL http://www.aol.com
Message-ID: <20021121210536.05821.00007701@mb-ms.aol.com>

Hi:

My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
target Intel X86 and for windows host.
I have created a Bootrom Image for Network configuration and When i try to boot
the kernel through the floppy disk, the screen becomes blank and it
automatically reboots. 

I will be happy if somebody can provide me with some informatio. Also, is there
any way to debug and see what is going on underneath the hood.  

The configuration and software versions are as follows:
VxWorks - 5.5
Tornado - 2.2
CPU - PENTIUM
C++Compiler - g++pentium (version - 2.93)
Host - Windows 2000.
Ethernet Driver - fei82557End Intel Ethernet Driver.

The config.h is configured using these macros
INCLUDE_NETWORK
INCLUDE_END,
INCLUDE_FEI_END,
INCLUDE_FTP,
INCLUDE_FTP_SERVER.

thanks
Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tornado 2.2 for target X86
Date: 21 Nov 2002 18:30:44 -0800
From: v_mahesh@hotmail.com (Mahesh)
Organization: http://groups.google.com/
Message-ID: <4f7acce6.0211211830.42cf160c@posting.google.com>

Hi:

My name is Mahesh, Iam working on creating and Configuring VxWorks
Kernel for target Intel X86 and for windows host.
I have created a Bootrom Image for Network configuration and When i
try to boot the kernel through the floppy disk, the screen becomes
blank and it automatically reboots.

I will be happy if somebody can provide me some information. Also, is
there any way to debug and see what is going on underneath the hood.

The configuration and software versions are as follows:
VxWorks - 5.5
Tornado - 2.2
CPU - PENTIUM
C++Compiler - g++pentium (version - 2.93)
Host - Windows 2000.
Ethernet Driver - fei82557End Intel Ethernet Driver.

The config.h is configured using these macros
INCLUDE_NETWORK
INCLUDE_END,
INCLUDE_FEI_END,
INCLUDE_FTP,
INCLUDE_FTP_SERVER.

thanks
Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tornado 2.2 for target X86
Date: 21 Nov 2002 18:32:54 -0800
From: v_mahesh@hotmail.com (Mahesh)
Organization: http://groups.google.com/
Message-ID: <4f7acce6.0211211832.1ab3277e@posting.google.com>

Hi:

My name is Mahesh, Iam working on creating and Configuring VxWorks
Kernel for target Intel X86 and for windows host.
I have created a Bootrom Image for Network configuration and When i
try to boot the kernel through the floppy disk, the screen becomes
blank and it automatically reboots.

I will be happy if somebody can provide me some information. Also, is
there any way to debug and see what is going on underneath the hood.

The configuration and software versions are as follows:
VxWorks - 5.5
Tornado - 2.2
CPU - PENTIUM
C++Compiler - g++pentium (version - 2.93)
Host - Windows 2000.
Ethernet Driver - fei82557End Intel Ethernet Driver.

The config.h is configured using these macros
INCLUDE_NETWORK
INCLUDE_END,
INCLUDE_FEI_END,
INCLUDE_FTP,
INCLUDE_FTP_SERVER.

thanks
Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ftp server problem
Date: Fri, 22 Nov 2002 15:29:49 +0800
From: "kenny" <dick.cheng@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <arkmdj$94g$1@mail.cn99.com>
References: <arfmjh$of3$1@mail.cn99.com> <newscache$gqjv5h$jl8$1@lnews.actcom.co.il>

I have searched in google. This problem is occured in solaris2.4 or before
and often in anonymous ftp. Our solaris version is 8.0 and we use user name
and password to access ftp server. In addtion, no more such problem reported
after version 2.4. Do you have any idea about this? Thanks

"Leonid Rosenboim" <My_1st_name@Consultant.Com> wrote in message
news:newscache$gqjv5h$jl8$1@lnews.actcom.co.il...
>
> If you would only bother yourself to search this on Google, you would
> farther quickly have found this:
>
> http://www.ebsinc.com/solaris/network/ftp.html
>
> Quite:
>
>   Q: Why do I get the following error when I log in to my anonymous FTP
>   account? This seems to happen after anonymous FTP has been running
>   correctly for a while:
>
>     "Can't create data socket (150.203.21.26,20): Interrupted system
call."
>
>   A: This is a known bug #1167893, under Solaris 2.4. It is currently
>   being investigated. Rebooting the machine will return Anonymous FTP
>   to its correctly working state.
>
> Do a search on SunSolve, and get yourself a patch.
> --
> -----------------------------------------------------------------------
>    Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
>        Consultant                Email: my first name at consultant dot
com
>
>
> "kenny" <dick.cheng@utstar.com> wrote in message
> news:arfmjh$of3$1@mail.cn99.com...
> I am fighting for a problem these days, but not resolved it till now.
> The problem is as following:
> A gateway runing vxworks OS get file from a ftp server from a
> solaris(version 8). During loading object files, sometimes when getting a
> file from solaris ftp server it failed many times.
> following is the error message from soloris machine:
> Can't create data socket (10.13.1.61,20): Interrupted system call.
> Can anyone tell me how to do with it? thanks
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How can I get the list of routines provided by BSP?
Date: Thu, 21 Nov 2002 11:41:41 -0700
From: "pandari" <pandari@asu.edu>
Organization: Arizona State University
Message-ID: <arj9b7$3v3$1@news.asu.edu>
References: <4f57a77f.0211201023.2e9a9943@posting.google.com> <eP=bPTM5N1y0IcofXb23M=Z90ZeL@4ax.com>

Hello :-),

Just start the vxWorks Shell prompt. Type
lkup "pci" to get the names of all API routines which contains the keyword
pci.

Hope this helps.

<pappajoemamma@pandora.orbl.org> wrote in message
news:eP=bPTM5N1y0IcofXb23M=Z90ZeL@4ax.com...
> yangliang_mr@hotmail.com (Liang Yang) wrote:
>
> :(Hi,
> :(
> :(VxWorks reference manual only lists the
> :(library routines provided by vxWorks
> :(itsself, if I want to use the library
> :(routines included in BSP directly,
> :(how can I get the list of these kind
> :(of routines in BSP?
> :(
> :(Thanks.
> :(
> :(Liang
>
> Look in $WIND_BASE/docs/vxworks/bsp/ "name_of_bsp"

---------------------------

Newsgroups: comp.os.vxworks
Subject: C++ Standard Library support
Date: 22 Nov 2002 02:24:14 -0800
From: dlong@wvintenltd.com (Darren Long)
Organization: http://groups.google.com/
Message-ID: <5c34b056.0211220224.5784fe7a@posting.google.com>

Hi, hope someone can help

I'm new to VxWorks and Tornado.  In fact I'm so new I don't have it
installed yet. But I've discovered that the version my colleague has
doesn't appear to be provided with the <sstream> header file defining
std::stringstream.

I'm pretty concerned that Tornado/VxWorks doesn't provide full support
for the C++ Standard Library, and wondered whether a later version
might provide this.

In the past, I've been led to understand that things like
std::auto_ptr (defined in <memory> ) have been omitted.

The BSP for the PowerPC PMC that we are going to use appears to
support Tornado 2.1 and not the new version - 2.2 (?)

Can this lack of support be fixed, by using more recent distributions
of the C++ Standard Library alongside the old tools and kernel, or am
I stuck with a non-standard standard library?

I guess it might be possible that this is a GNU tools issue.  Any
ideas?

Direct responses via email would be welcomed, as I'm using google
groups to read news.

Darren

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Any documentation on STL included with vxWorks 5.4.2 (Tornado 2.0.2)
Date: 22 Nov 2002 02:31:06 -0800
From: dlong@wvintenltd.com (Darren Long)
Organization: http://groups.google.com/
Message-ID: <5c34b056.0211220231.5855694c@posting.google.com>
References: <a7b7bb67.0211060738.7a564dad@posting.google.com> <slrnasjc39.2du.kiev78@finch.lecs.cs.ucla.edu> <a7b7bb67.0211070758.1e3780a6@posting.google.com>

Hi,

Can the later version of the STL be used with earlier version of
Tornado successfully?

I need to use Tornado 2.1 due to board support pack versions for the
CPU crad.

Darren

FrankGleeson@motorola.com (frankg) wrote in message news:<a7b7bb67.0211070758.1e3780a6@posting.google.com>...
> Denis,
> Thanks for the info. Right now I am looking to maintain
> stability in the build environment. I also sent this question
> to my vxWorks FAE or whatever they call themselves now.
> 
> I will "quote" his response for the sake of anyone following
> this thread with a similar concern as mine.
> 
>  > For Tornado 2.0 through Tornado 2.0.2 through Tornado 2.1.x,
>  > the GNU version of the STL is the Feb 7, 1995 version.
>  
>  > Of the versions available on the SGI web page,
>  > it is closest to SGI version 2.0.3. Its hash templates
>  > are spelled differently, and it lacks the 'rope', 'slist'
>  > and 'type_trait' classes that 2.03 has. The GNU version
>  > has more templates than 2.03 however, and the differences
>  > are hard to describe briefly.
>  
>  > For Tornado 2.2 the C++ Standard Template Library for this release  
>  > corresponds to SGI version 3.11.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Download Procedure
Date: 22 Nov 2002 03:43:30 -0800
From: vxworks@india.com (V R R Raju)
Organization: http://groups.google.com/
Message-ID: <d6e2de0a.0211220343.5f0d758@posting.google.com>

Dear Friends,

I am working on Vxworks 5.4 and Tornado II. I am a newbie and don't
know how to download the bootable image to target from host using FTP.
I did what I was told by my friend and it is as follows:

1. Configure the Vxworks using the tornado and Include and Exclude the
components according to application requirements.

2. I don't know which Ethernet Driver type to include (ELT or ENT or
any other). I am using Realtek processor based Ethernet Card. Please
let me know which Ethernet Drivers should I use.

3. What parameter should I specify DEFAULT_BOOT_LINE for hardware
components properties.
I am specifying the following

"fd=0,0(0,0)host:c/tornado/target/config/pc486/vxWorks.st
h=131.200.2.244 e=131.200.2.105 u=target"

4. I am making a bootrom_uncmp image and then copying it to Floppy
Disk using mkboot a:bootrom_uncmp.

5. Then I am trying to boot my target using the floppy.

6. I am making a Vxworks.st standalone image.

7. I am starting the FTP server by giving the username and password
and also the home directory in which my image is stored.

8. I am executing the image in the target using the @ command after
changing any parameters using c and P commands.

9. Target gets started with saying Loading and suddenly some numbers
are displayed and it hangs. Even it is not getting connected to the
FTP server in the Host.

Please let me know where I have gone wrong and whether the above
procedure is correct. Also let me know whether there is another way of
downloading and its procedure which will help me a lot .

Thanks in advance.

with regards,

Rajneesh

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Fri Nov 22 06:23:00 2002
From: Mike McCullough <mike@mccengineering.com>
Date: Fri Nov 22 06:23:02 PST 2002
Subject: Re: memory allocation MALLOC ISSUE

 >>Newsgroups: comp.os.vxworks
 >>Subject: memory allocation MALLOC ISSUE
 >>Date: Thu, 21 Nov 2002 01:23:03 GMT
 >>From: "Jim McKain" <jim_mckain@nltek.com>
 >>Organization: AT&T Broadband
 >>Message-ID: <XzWC9.95906$QZ.14473@sccrnsc02>
 >>HI All,
 >>I'm running a project and we have ported a large windows application (10MB
 >>of code) and are running into memory fragmentation problems. [PPC, 860
 >>arch, C++, OOD, 32MB RAM, Tornado 2.0]

This is typical when you simply port over a desktop application. RTOS 
memory management is not for the faint of heart and it is certainly NOT 
like the desktop.

What you should do is examine where and when you are doing memory 
allocations. Typically in an RTOS you need to do your allocations up front 
and keep dynamic allocations to a bare minimum. Typical desktop 
applications dynamically allocate all over the place (what the heck, the 
user can always ctrl-alt-delete) which is where your problem really stems from.

My company sells a tool that would help in understanding your memory design 
as well as consulting for when you need to re-design. Real-Time Innovations 
and AMC also sell tools that would help you refine your memory usage.

 >>I know that the OS is notorious for poor memory management. But 
does >>anyone
 >>have a third party MALLOC routine that does best fit or some other smarter
 >>way of allocation.

It doesn't do poor memory management. It expects the users to understand 
the embedded environment and take appropriate design steps for their 
application. That said I believe Wind River may have a best-fit design to 
sell you, you should check with them as it came out of their consulting group.

 >>Has anyone used a Virtual MMgr with the 860 before?

Danger, danger, Will Robinson!! There is a world of hurt for you if you go 
this route such as: complete redesign of the Wind kernel, Wind River no 
longer supporting your application, etc. Don't go there. Get a consultant 
in for a week to help you with this, it will cost 1/10 of what going 
virtual will do to you.

 >>Any help or pointers to solutions are appreciated.

I hope this helps. Going from a desktop to an RTOS is NOT easy but there 
are many people out there who can help.

 >> -Jim

**********************************************************
Mike McCullough                    MCC Engineering
President and CEO                  9 Cheshire Court
                                    Londonderry, NH 03053

mike@mccengineering.com            Tel:  603-537-9593
                                    Fax:  603-434-9890
www.mccengineering.com            Cell: 603-247-1219

**********************************************************
        24x7 VxWorks Support  Custom Support Programs
          VxWorks Training   Embedded Consulting Services
                     A WindLink Partner
**********************************************************

From vxwexplo-errs@csg.lbl.gov  Sat Nov 23 04:03:17 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sat Nov 23 04:03:19 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sat Nov 23 04:03:15 PST 2002

        Subject: RIPv2 passing netmask
        Subject: PCI-POST card under vxWorks
        Subject: Newbie asks:How to reload application from ethernet connector?
        Subject: Re: duplicate/truncated filenames in Flash
        Subject: Re: ftp server problem
        Subject: Re: memory allocation  MALLOC ISSUE
        Subject: Non-volatile registers and __sjthrow
        Subject: Re: Tornado 2.2 for X86
        Subject: Re: want to know all the available drives of the system
        Subject: Re: Download Procedure
        Subject: Re: ifAddrAdd
        Subject: Re: Error message after booting
        Subject: Re: How can I get the list of routines provided by BSP?
        Subject: Re: PCI-POST card under vxWorks
        Subject: Re: Tornado 2.2 for X86
        Subject: Ram disk on non-memory mapped NVRAM.

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: RIPv2 passing netmask
Date: Fri, 22 Nov 2002 09:20:31 -0500
From: "N N" <naga@mindspring.com>
Organization: Lucent Technologies
Message-ID: <arlefg$51j@netnews.proxy.lucent.com>

Hi,
In the RIPv2 that is bundled with vxWorks 5.4system,
if interfaces are added with variable length subnet mask
like 10.1.1.1/30 (mask of 255.255.255.252)
the RIPv2 propagates 10.0.0.0/8 on the messages.

The RIPv2 is running on the interface
and I can see using sniffer RIPv2 messages sent out by the system
that has routes 10.0.0.0 and 255.0.0.0 as mask as opposed to 30 bit mask.

Is there any problem with RIPv2 messages or am I missing something?

Thanks!

---------------------------

Newsgroups: comp.os.vxworks
Subject: PCI-POST card under vxWorks
Date: Fri, 22 Nov 2002 16:22:55 +0100
From: "H.J.W. Gevers" <hjge@oce.nl>
Organization: Oce Technologies B.V.
Message-ID: <3DDE4BCF.7305C08A@oce.nl>

Hi,

For extra debugging, we are using a PCI-POST card to investigate an interrupt problem.
The Post card normaly uses the 0x80 (or 0x84) IO-Space of the ISA bus.
But for some reason I can't program the output using sysOutByte(0x80, 0);

Is it possible to use this kind of accessing ISA adres-space?

My system: Celeron platform with vxWorks 5.4.2 and a some PCI-slots 
(No ISA-slots)

Kind regards,

Bart Gevers

---------------------------

Newsgroups: comp.os.vxworks
Subject: Newbie asks:How to reload application from ethernet connector?
Date: 22 Nov 2002 09:01:44 -0800
From: zarfus@hotmail.com (Dan)
Organization: http://groups.google.com/
Message-ID: <60fb21d0.0211220901.5e3294ab@posting.google.com>

We are working with a DiskOnChip2000 on a pentium with VxWorks.
How can we set it up so that we can reload our executables
from the ethernet port? Right now, we have to reprogram our targets by
swapping the disk on chip parts.
Do we have to write application code, or can we just leave an FTP
server running
on the embedded machine?  Is there an FTP server for VxWorks?
Any ideas out there?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: duplicate/truncated filenames in Flash
Date: Fri, 22 Nov 2002 17:41:15 GMT
From: Andray Kaganovsky <andrayk@NOSPAMfutureway.com>
Organization: Futureway
Message-ID: <Xns92CE814BA8E96andrayk@142.77.1.194>
References: <6i%s9.260$B11.66292@news.uswest.net>

"kdb" <CAN_THE_SPAM@CAN_THE_SPAM.com> wrote in news:6i%s9.260$B11.66292
@news.uswest.net:

> Every once in a while my Flash filesystem will show duplicate and/or
> truncated filenames.  E.g.: what was once "Logs" will now be simply "L",
> what was "myfile" is now "m".  Or I may have multiple files all named
> "myfile".  Any idea what's going on here and how to fix it?
> 
> This happens with directories or normal files.  In both duplicates and
> truncations it does preserve the upper/lower case of the name.  The file or
> directory contents remain intact, it's just the names that are hosed.
> 
> System env: PowerPC 8245 (603-based, not using any floating point to my
> knowledge but I could be wrong), VxWorks 5.4.2, Tornado 2.0.2, dosFs 2.0,
> TrueFFS.
> 
> thanks in advance   - K
> 
> 
> 

[AndrayK]. Try using routine usrTffsLnConfig() instead of
usrTffsConfig() in usrTffs.c. 

Andray

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ftp server problem
Date: Wed, 20 Nov 2002 14:22:00 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$gqjv5h$jl8$1@lnews.actcom.co.il>
References: <arfmjh$of3$1@mail.cn99.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

If you would only bother yourself to search this on Google, you would
farther quickly have found this:

http://www.ebsinc.com/solaris/network/ftp.html

Quite:

  Q: Why do I get the following error when I log in to my anonymous FTP
  account? This seems to happen after anonymous FTP has been running
  correctly for a while:

    "Can't create data socket (150.203.21.26,20): Interrupted system call."

  A: This is a known bug #1167893, under Solaris 2.4. It is currently
  being investigated. Rebooting the machine will return Anonymous FTP
  to its correctly working state.

Do a search on SunSolve, and get yourself a patch.
- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

"kenny" <dick.cheng@utstar.com> wrote in message
news:arfmjh$of3$1@mail.cn99.com...
I am fighting for a problem these days, but not resolved it till now.
The problem is as following:
A gateway runing vxworks OS get file from a ftp server from a
solaris(version 8). During loading object files, sometimes when getting a
file from solaris ftp server it failed many times.
following is the error message from soloris machine:
Can't create data socket (10.13.1.61,20): Interrupted system call.
Can anyone tell me how to do with it? thanks

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: memory allocation  MALLOC ISSUE
Date: Fri, 22 Nov 2002 19:49:30 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <arm1oa$ke9$1@knossos.btinternet.com>
References: <XzWC9.95906$QZ.14473@sccrnsc02>

> I know that the OS is notorious for poor memory management. But does anyone
> have a third party MALLOC routine that does best fit or some other smarter
> way of allocation.

I reverse enginneered the free list format (it is particularly trivial)
and wrote a function to allocate from the smallest block that would
satisfy the request (instead of the first).

Link with the BSP and overwrite the first instruction of
memPartAlignedAlloc with a jump to your routine early on.

This will be orders of magnitude better than the WRS routine.
(unless your application is one that exhibits the required
pathological behaviour).

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Non-volatile registers and __sjthrow
Date: 22 Nov 2002 11:51:27 -0800
From: news@coldforged.org (Brian Dupuis)
Organization: http://groups.google.com/
Message-ID: <3ec04a44.0211221151.4b7721a8@posting.google.com>

Hello,

I'm currently waiting the requisite fortnight for WindRiver to address
an issue, so I figured I'd see what someone else thought. Here's my
issue.

For this version of the GCC toolchain "cygnus-2.7.2-960126 egcs-971225
tornado 2.0" for a PowerPC 405GP target, the following code is
delivered for the __sjthrow routine. Fear not, I'll paraphrase:

__sjthrow:
    00162B3C stwu r1,-0x670(r1)
    00162B40 mfspr r0,LR
    00162B44 stw r31,0x66C(r1)

Notice how friendly __sjthrow is, saving off r31 onto a stack frame.
Intriguing action for a routine that exits via a longjmp(), no? Let's
hop down some, while the code traverses the stacks, calling
destructors and popping the stack pointer up.

   00162C84 addi r9,r9,8
   00162C88 lwz r7,4(r9)
   00162C8C lwz r1,0xC(r9)

Here, the stack is restored to where it should be for whoever's
"catch"
block is going to catch this throw.

   00162C90 mtspr CTR,r7

Loading the longjmp destination into the CTR register.

   00162C94 lwz r0,8(r9)
   00162C98 stw r0,0(r1)
   00162C9C bctr

And off we go, longjmp()ing to the "catch", never to return. r31,
which was modified sometime during this function, is not restored to
the original value saved off on the stack. To me, this breaks the PPC
ABI, since it's supposed to retain value across function calls. Am I
crazy, or is this bad? It manifests itself in our software by some
poor sap about 5 calls up the calling chain losing its r31-based
"this" pointer when an exception is thrown well below it.

Can anyone think of a decent method of getting rid of this? I'm
concerned that WindRiver is not going to have a viable answer for me,
since who knows if they even keep their archived versions of GCC
around any more, and I am having a delightful time trying to find the
appropriate source tarball to attempt my own recompilation of the
appropriate object.

Any thoughts very much appreciated.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for X86
Date: 22 Nov 2002 13:00:00 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211221300.549ea28b@posting.google.com>
References: <20021121203910.05840.00005962@mb-ms.aol.com>

Hello,

> My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
> target Intel X86 and for windows host.
> I have created a Bootrom Image for Network configuration and When i try to boot
> the kernel through the floppy disk, the screen becomes blank and it
> automatically reboots. 

You need to change the console settings. In the newer versions of
VxWorks, including AE 1.x and 5.5, the default setting for the console
is the serial port (COM1 using DOS style naming, /tyCo/0 in VxWorks).

You can switch back to the VGA console if you need to (search the
archives for this group - it has been covered before), or you can
simply connect a terminal (or PC running HyperTerminal) to the serial
port and use that.

HTH,

John...
 
> I will be happy if somebody can shed some on it. Also, is there any way to
> debug and see what is going on underneath the hood.  
> 
> The configuration and software versions are as follows:
> VxWorks - 5.5
> Tornado - 2.2
> CPU - PENTIUM
> C++Compiler - g++pentium (version - 2.93)
> Host - Windows 2000.
> Ethernet Driver - fei82557End Intel Ethernet Driver.
> 
> The config.h is configured using these macros
> INCLUDE_NETWORK
> INCLUDE_END,
> INCLUDE_FEI_END,
> INCLUDE_FTP,
> INCLUDE_FTP_SERVER.
> 
> thanks
> Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: want to know all the available drives of the system
Date: 22 Nov 2002 13:25:16 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211221325.68adcf05@posting.google.com>
References: <arklse$t49$1@overload.lbl.gov>

Hello,

You could try to read the manuals, because you seem to be completely
off track when it comes to the VxWorks I/O system. Check the VxWorks
Programmer's Guide section on the I/O system.

Meantime, here are some pointers:

> in vxworks we have to creat devices in which we associate a driver number
> against that device, like driver number of floppy disk ranges (0 - 3) .

No, you give each device a name. That name can be anything, though you
should be careful when assigning names that are similar as the
matching algorithm is very simple. For your floppy disks, you could
use names like "/fd/0" or like "/fd0" or even "A:" or "fd0" - all
would be OK. You get to choose the naming convention you wish to use.

> so the problem is that how i will be able to know that whether floppy disk
> and cd drive is present in the system or not and if present then how to
> assign them a driver number.

You do not assign them a driver number. The driver number is assigned
by the OS to the driver (not to a specific device - each driver can
manage as many devices as it wants to). When you create a device, you
need to pass in the driver number of the corresponding driver, and a
name for the new device (that is not already in use).

Now, your floppy disk example has an added complexity since it is a
block device, not a character device. In these cases, the driver is
not installed into the I/O system. Instead, a file system is installed
into the I/O system, and the driver is associated with the file system
(see the programmer's guide again for information on this). When
creating a device in this case you will use a file system routine
rather than the iosDevCreate() routine that would be used for a
character device - see the reference manual entries for your file
system in this case.

If you want to tell if a device is already in the system, then you can
use iosDevFind() to get you the device handle for a named device. If
it cannot find one, then it will return NULL (see the reference manual
entry for more information). This should work for either kind of
device (block or character).

HTH,

John...

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Download Procedure
Date: 22 Nov 2002 16:23:16 -0800
From: techie_me@yahoo.com (Aardra)
Organization: http://groups.google.com/
Message-ID: <d6dd5318.0211221623.2816e2c5@posting.google.com>
References: <d6e2de0a.0211220343.5f0d758@posting.google.com>

The steps seems to be correct. About the ethernet driver include ENE
since its the realtek card.
Also did you change the config.h. Make sure to #define INCLUDE_ENE
Hope that works!!

vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211220343.5f0d758@posting.google.com>...
> Dear Friends,
> 
> I am working on Vxworks 5.4 and Tornado II. I am a newbie and don't
> know how to download the bootable image to target from host using FTP.
> I did what I was told by my friend and it is as follows:
> 
> 1. Configure the Vxworks using the tornado and Include and Exclude the
> components according to application requirements.
> 
> 2. I don't know which Ethernet Driver type to include (ELT or ENT or
> any other). I am using Realtek processor based Ethernet Card. Please
> let me know which Ethernet Drivers should I use.
> 
> 3. What parameter should I specify DEFAULT_BOOT_LINE for hardware
> components properties.
> I am specifying the following
> 
> "fd=0,0(0,0)host:c/tornado/target/config/pc486/vxWorks.st
> h=131.200.2.244 e=131.200.2.105 u=target"
> 
> 4. I am making a bootrom_uncmp image and then copying it to Floppy
> Disk using mkboot a:bootrom_uncmp.
> 
> 5. Then I am trying to boot my target using the floppy.
> 
> 6. I am making a Vxworks.st standalone image.
> 
> 7. I am starting the FTP server by giving the username and password
> and also the home directory in which my image is stored.
> 
> 8. I am executing the image in the target using the @ command after
> changing any parameters using c and P commands.
> 
> 9. Target gets started with saying Loading and suddenly some numbers
> are displayed and it hangs. Even it is not getting connected to the
> FTP server in the Host.
> 
> Please let me know where I have gone wrong and whether the above
> procedure is correct. Also let me know whether there is another way of
> downloading and its procedure which will help me a lot .
> 
> 
> Thanks in advance.
> 
> with regards,
> 
> Rajneesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ifAddrAdd
Date: 22 Nov 2002 16:31:28 -0800
From: techie_me@yahoo.com (Aardra)
Organization: http://groups.google.com/
Message-ID: <d6dd5318.0211221631.6cc26a7e@posting.google.com>
References: <3DDD49F1.8010207@arcor.de>

I dont think you can assign two IP addresses to one network interface.
But it is possible to have a system with two ip addresses if it has
two NICs and each one having one IP address.
Just curious, what type of application do you have in mind?

Ralf Hoppe <ralf.hoppe@arcor.de> wrote in message news:<3DDD49F1.8010207@arcor.de>...
> Hi, i'am a pure novice with respect to the VxWorks network functions. 
> The question that i have is, how does the function ifAddrAdd() work. Is 
> it possible to assign two IP addresses (from the same network) to one 
> interface device? And if so - can i open two sockets, one gets the 
> traffic to the first IP address and the other receives the traffic to 
> the second IP address? The other question related to that topic is: are 
> there any side effects of that assignment of two addresses to one 
> interface which should an network administrator have in mind if he 
> configures the network (e.g. any ARP or ROUTING effects)?
> 
> Hope anybody knows an answer!?
> 
> Bye, Ralf

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Error message after booting
Date: Wed, 20 Nov 2002 13:59:55 GMT
From: "Lou Rohan" <L&R&R&1@cec.wustl.edu>
Organization: The Boeing Company
Message-ID: <H5vo7u.F2C@news.boeing.com>
References: <utkt98ousurh40@corp.supernews.com>
Sender: nntp@news.boeing.com (Boeing NNTP News Access)

I believe that I have seen this with a 2604 as well, and I think it stems
from the DEC 21140 ethernet driver.  When I tried booting the board with a
Tornado 2.0.2/VxWorks 5.4 kernel, it would do the same thing that yours
does.  I solved it by going back to a Tornado 2.0 installation and replacing
the 2.0 dec21x40End.o object file in the newer 2.02 libPPC604gnuvx.a archive
file.  I think it has something to do with auto negotiation...

This was just a quick fix, you should contact your WR customer support.

Lou (remove &s for proper email addr)

"cnwebb" <cwebb@maxtc.com> wrote in message
news:utkt98ousurh40@corp.supernews.com...
> I am attempting to boot up a PowerPC 750 processor on a
> Motorola MVME2431 board using Tornado 2.0.2 & VxWorks 5.4
>
> I have successfully built the microkernel and flashed it to the board,
> and the board appears to boot normally.  However after the VxWorks
> version information is displayed in my Hyperterminal window, I start
> getting the following error
>          miiPhyInit:  check cable connection
>
> This error continues to be written to the display until I disconnect from
> the target.  I have checked the cable connections on both the host and
> the target, and they are secure.  I have also used the same cables to
> boot up another computer using a previous version of Tornado/VxWorks,
> so I don't believe there is a problem with the cables.
>
> I would appreciate any help in determining the cause and solution of this
> problem.
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How can I get the list of routines provided by BSP?
Date: Sat, 23 Nov 2002 11:04:22 +0900
From: "Girish Gulawani" <girishvgNOSPAM@yahoo.com>
Message-ID: <3ddee1ef$0$19941$44c9b20d@news3.asahi-net.or.jp>
References: <4f57a77f.0211201023.2e9a9943@posting.google.com> <eP=bPTM5N1y0IcofXb23M=Z90ZeL@4ax.com> <arj9b7$3v3$1@news.asu.edu>

lkup is just a symbol finder. one cas use it (mostly) to solve linker
errors. as a programmer one would like to see the parameters, returns,
description, etc. many bsp writers do not produce the man files. they think
it's mundane. so you have to rely on the source code or contact me address.
;-))

"pandari" <pandari@asu.edu> wrote in message
news:arj9b7$3v3$1@news.asu.edu...
> Hello :-),
>
> Just start the vxWorks Shell prompt. Type
> lkup "pci" to get the names of all API routines which contains the keyword
> pci.
>
> Hope this helps.
>
> <pappajoemamma@pandora.orbl.org> wrote in message
> news:eP=bPTM5N1y0IcofXb23M=Z90ZeL@4ax.com...
> > yangliang_mr@hotmail.com (Liang Yang) wrote:
> >
> > :(Hi,
> > :(
> > :(VxWorks reference manual only lists the
> > :(library routines provided by vxWorks
> > :(itsself, if I want to use the library
> > :(routines included in BSP directly,
> > :(how can I get the list of these kind
> > :(of routines in BSP?
> > :(
> > :(Thanks.
> > :(
> > :(Liang
> >
> > Look in $WIND_BASE/docs/vxworks/bsp/ "name_of_bsp"
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: PCI-POST card under vxWorks
Date: Sat, 23 Nov 2002 11:11:03 +0900
From: "Girish Gulawani" <girishvgNOSPAM@yahoo.com>
Message-ID: <3ddee381$0$19947$44c9b20d@news3.asahi-net.or.jp>
References: <3DDE4BCF.7305C08A@oce.nl>

0x80 is in PCI extended configuration space(?). did you try to access it as
a long at 0x80/4. otherwise i think there is no such restriction on
accessing extended config. registers.

"H.J.W. Gevers" <hjge@oce.nl> wrote in message
news:3DDE4BCF.7305C08A@oce.nl...
> Hi,
>
> For extra debugging, we are using a PCI-POST card to investigate an
interrupt problem.
> The Post card normaly uses the 0x80 (or 0x84) IO-Space of the ISA bus.
> But for some reason I can't program the output using sysOutByte(0x80, 0);
>
> Is it possible to use this kind of accessing ISA adres-space?
>
> My system: Celeron platform with vxWorks 5.4.2 and a some PCI-slots
> (No ISA-slots)
>
> Kind regards,
>
> Bart Gevers

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for X86
Date: 22 Nov 2002 20:17:09 -0800
From: v_mahesh@hotmail.com (Mahesh)
Organization: http://groups.google.com/
Message-ID: <4f7acce6.0211222017.365ed70@posting.google.com>
References: <20021121203910.05840.00005962@mb-ms.aol.com> <488e459a.0211221300.549ea28b@posting.google.com>

Hi john:

Thanks for the prompt reply. Iam a newbie to VxWorks, If the default
option setting for the console is serial then it should hang but
rather it was going into rebooting mode.

I will change the default setting and let you know.

thanks for the reply.

Mahesh

john_94501@yahoo.com (John) wrote in message news:<488e459a.0211221300.549ea28b@posting.google.com>...
> Hello,
> 
> > My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
> > target Intel X86 and for windows host.
> > I have created a Bootrom Image for Network configuration and When i try to boot
> > the kernel through the floppy disk, the screen becomes blank and it
> > automatically reboots. 
> 
> You need to change the console settings. In the newer versions of
> VxWorks, including AE 1.x and 5.5, the default setting for the console
> is the serial port (COM1 using DOS style naming, /tyCo/0 in VxWorks).
> 
> You can switch back to the VGA console if you need to (search the
> archives for this group - it has been covered before), or you can
> simply connect a terminal (or PC running HyperTerminal) to the serial
> port and use that.
> 
> HTH,
> 
> John...
>  
> > I will be happy if somebody can shed some on it. Also, is there any way to
> > debug and see what is going on underneath the hood.  
> > 
> > The configuration and software versions are as follows:
> > VxWorks - 5.5
> > Tornado - 2.2
> > CPU - PENTIUM
> > C++Compiler - g++pentium (version - 2.93)
> > Host - Windows 2000.
> > Ethernet Driver - fei82557End Intel Ethernet Driver.
> > 
> > The config.h is configured using these macros
> > INCLUDE_NETWORK
> > INCLUDE_END,
> > INCLUDE_FEI_END,
> > INCLUDE_FTP,
> > INCLUDE_FTP_SERVER.
> > 
> > thanks
> > Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Ram disk on non-memory mapped NVRAM.
Date: 20 Nov 2002 07:10:51 -0800
From: dansmith_1@yahoo.com (Dan Smith)
Organization: http://groups.google.com/
Message-ID: <5e76a7d7.0211200710.de97c13@posting.google.com>

The PowerCoreCPCI-680 board we are using has NVRAM that is not mapped
to the main processor's address space.

Is there a way to create a RAM Disk on this type of NVRAM? I know
about ramDiskDevCreate but it requires a starting memory address.
Since the NVRAM in question is non-memory mapped I don't have a
starting address in the main processor's address space.

The access to the NVRAM is 8-bit wide and indirect. To access a
location within the NVRAM device:
1. Write the lower address byte to FE000073  (write-only).
2. Write the higher address byte to FE000075  (write-only).
3. Read or write data byte sized from or to FE000077.

Thanks 

Dan Smith
Telephonics Wireless Corporation
Melbourne, FL

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sun Nov 24 04:03:10 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sun Nov 24 04:03:12 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sun Nov 24 04:03:08 PST 2002

        Subject: Re: Changing current directory on simulator, Tornado 2 on Windows NT
        Subject: Tcl interpreter on VxWorks target?
        Subject: Re: Tcl interpreter on VxWorks target?
        Subject: Re: 1553 bus and Vxworks drivers
        Subject: problem booting on VIA motherboard
        Subject: Re: Newbie asks:How to reload application from ethernet connector?
        Subject: Re: How many byte do you know VxWorks BSP Image size?
        Subject: unresolved sysmbol: sysInByte()

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Changing current directory on simulator, Tornado 2 on Windows NT
Date: Wed, 20 Nov 2002 19:07:48 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$rywv5h$e29$1@lnews.actcom.co.il>
References: <argcgb$p7i$1@overload.lbl.gov>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Douglas Wilson" <dwilson@birdstep.com> wrote in message
news:argcgb$p7i$1@overload.lbl.gov...
> Is there any way to change the current directory (on the target, not the
> host) from the shell, when running the simulator under Tornado 2, on
Windows
> NT?
>
> Douglas Wilson

Yes, do
    -> @cd "/newdir"
istead of
    -> cd "/newdir"

Looks like reading through the manuals is out of fasion these days ;-)

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Tcl interpreter on VxWorks target?
Date: 23 Nov 2002 08:39:32 -0800
From: rbinder@rbsc.com (Bob Binder)
Organization: http://groups.google.com/
Message-ID: <ded6b237.0211230839.35ae9faa@posting.google.com>

Does VxWorks include a Tcl interpreter which runs Tcl scripts on the
target platform?

If yes, is the IncrTcl package part of the VxWorks Tcl library?

I've searched web, faqs, and newsgroups about this, but can't find a
definitive indication (it is clear that Tcl scripts are used on the
development console platform.)  As I don't hold a VxWorks license, I
can't rtm.

Tia
Bob Binder

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tcl interpreter on VxWorks target?
Date: Sat, 23 Nov 2002 18:34:25 +0000
From: Wade Oram <news@wtoram.co.uk>
Organization: None
Message-ID: <yUbGO$Hxo839EADt@wtoram.co.uk>
References: <ded6b237.0211230839.35ae9faa@posting.google.com>
Reply-To: Wade Oram <wade@wtoram.co.uk>

In message <ded6b237.0211230839.35ae9faa@posting.google.com>, Bob Binder 
<rbinder@rbsc.com> writes
>Does VxWorks include a Tcl interpreter which runs Tcl scripts on the
>target platform?
>
>If yes, is the IncrTcl package part of the VxWorks Tcl library?
>
>I've searched web, faqs, and newsgroups about this, but can't find a
>definitive indication (it is clear that Tcl scripts are used on the
>development console platform.)  As I don't hold a VxWorks license, I
>can't rtm.
>
>Tia
>Bob Binder
Hello,

There is no target side Tcl interpreter supplied as part of vxWorks.

There was, at one point a version of Tcl ported for vxWorks freely 
available. I don't know if it is still available. It was not a current 
enough version to support Incremental.
- -- 
Wade Oram

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: 1553 bus and Vxworks drivers
Date: Sat, 23 Nov 2002 20:06:14 GMT
From: bob houston <bobhous@houston.rr.com>
Organization: Road Runner - Texas
Message-ID: <3DDFDF06.C0378DA1@houston.rr.com>
References: <hfyz9.20$5x.12712@newsfep2-win.server.ntli.net> <3DCF9C1F.B19496FA@lmco.com>
Reply-To: houst0n@yahoo.com

Joe Durusau wrote:
> 
> Mike Barton wrote:
> >
> > Does anyone know of any 1553bus interface cards that have good vxworks
> > drivers?
> >
> > Mike

Another 1553 card vendor with vxWorks support is Condor

   http://www.condoreng.com

- - bob

---------------------------

Newsgroups: comp.os.vxworks
Subject: problem booting on VIA motherboard
Date: Sat, 23 Nov 2002 20:30:02 GMT
From: Alan Screen <ascreen@peerless.com>
Organization: Cox Communications
Message-ID: <ezRD9.19617$mr2.1007475@news1.west.cox.net>

I'm trying to get operational on a VIA KT133A motherboard (that uses the 
VT82C686B superio) with an AMD Athalon CPU.  I'm running into problems 
on the VxWorks (v5.4) initial boot.

The VxLd goes through its paces showing the dots as it loads; however, 
it never makes it to the blue screen for continuing the boot process.

Q:  Has anyone gotten this motherboard/chipset to work with VxWorks??

- - Alan

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Newbie asks:How to reload application from ethernet connector?
Date: 23 Nov 2002 08:12:32 -0800
From: zarfus@hotmail.com (Dan)
Organization: http://groups.google.com/
Message-ID: <60fb21d0.0211230812.3cd814da@posting.google.com>
References: <60fb21d0.0211220901.5e3294ab@posting.google.com>

zarfus@hotmail.com (Dan) wrote in message news:<60fb21d0.0211220901.5e3294ab@posting.google.com>...
> We are working with a DiskOnChip2000 on a pentium with VxWorks.
> How can we set it up so that we can reload our executables
> from the ethernet port? Right now, we have to reprogram our targets by
> swapping the disk on chip parts.
> Do we have to write application code, or can we just leave an FTP
> server running
> on the embedded machine?  Is there an FTP server for VxWorks?
> Any ideas out there?

Additional Info:

The hope I have is that I can walk up to the device, hook up an
ethernet cable, and via the magic of FTP reprogram the device with a
new load image ( password protected?).

Note that the target boots directly to Vxworks, with no DOS involved. 
The DOC appears as the C: drive when booted from a DOS floppy, some
other thing from VxWorks.  Right now, the console I/O comes has been
redirected via
   shellFileDescriptor = open("/vio/0", O_RDWR | O_CREAT, 0);
   ioGlobalStdSet(STD_OUT, shellFileDescriptor);
   ioGlobalStdSet(STD_ERR, shellFileDescriptor);
   logFdSet(shellFileDescriptor);
(note that keyboard port still works if it is connected, we've taken
over the default display to do other things).

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: How many byte do you know VxWorks BSP Image size?
Date: Thu, 21 Nov 2002 17:34:15 +0000
From: Wade Oram <news@wtoram.co.uk>
Organization: None
Message-ID: <3ZCXdZHXkR39EAT2@wtoram.co.uk>
References: <107f9c39.0211181826.e374715@posting.google.com>
 <3DD9E8BF.B300955B@sepro-robotique.com>
 <2450ac08.0211201857.245ab2fa@posting.google.com>
Reply-To: Wade Oram <wade@wtoram.co.uk>

In message <2450ac08.0211201857.245ab2fa@posting.google.com>, Patrick 
<patrick.klingele@siemens.com> writes
>Hi Emmanuel,
>It seams that you are quite familiar with building bootable vxWorks
>images. I'm trying this now for about 3 days with mixed success.
>I'm using T2.0.2/VxWorks5.4 and a target "Radisys board with intel
>80486 CPU and 32MB ram".
>
>I was successfull in building a/the little demo application using
>the makefiles in the config/BSP folder. I get a compressed vxWorks
>running the little demo app. This compressed image is then put on
>floppy with
>
>mkboot a: vxWorks.app_rom
>
>this is a duplicated target from vxWorks.st_rom without the standalone
>feature. Boot the target system and a few seconds later the little
>demo is running. Great!
>
>This was all done by using the make files on the command line.
>Now I want to do the same thing from the IDE by selecting the build
>target vxWorks_romCompressed.
>I added the very same little demo app to "usrAppInit.c" and build
>the image. I put it on the floppy the same way:
>
>mkboot a: vxWorks_romCompressed
>
>boot the target and after loading the image the screen stays black
>and the target system resets itself and does a warm boot. And the
>loading starts again.
>
>I tried already to modify (correct?) the location for the data segment
>of the final linker stage (linking romInit.o, romStart.o, etc )(which
>was the same value 0x8000 as for the text segment) to a value behind
>the rom code (now value 0x10000). Same "reset" effect.
>
>Is this target build from the IDE supposed to work correctly?
>Do you have any suggestions? I would appreciate it very much.
>BTW: My host is a Win2000 system with SP2.
>

I don't know whether it is still the case with Tornado 2.0.2 but with 
Tornado 2 there was a fault with rule for the vxWorks_romCompressed 
target. The entry point for the image was set to 'SYS_ENTRY' when it 
should have been set to 'ROM_ENTRY'.

I believe this fault occurred in %WIND_BASE%\target\h\make\rules.vxWorks 
at line 109 (or thereabouts).

If the fault persists in 2.0.2, this may be your problem.

You should also be aware that the rom_compressed image load into the 
RAM_HIGH_ADRS which is perversely in low memory and therefor there is a 
limit on the maximum size of the compressed image (it can't extend 
beyond the 640k lower memory limit). Your are obviously not encountering 
this problem at present but it is one to be aware of - it took me quite 
a while to work out what was going on when this one struck me!

HTH
- -- 
Wade Oram

---------------------------

Newsgroups: comp.os.vxworks
Subject: unresolved sysmbol: sysInByte()
Date: 24 Nov 2002 01:57:47 -0800
From: swami36@hotmail.com (Tony_Rocky_Horror)
Organization: http://groups.google.com/
Message-ID: <c21c6d3.0211240157.4f9e5ea9@posting.google.com>

Hi, I am trying to use SysInByte () and sysOutByte() to read/write
ports
on an IXP1200 StrongArm processor.

When I download the module, it fails citing 
"unresolved symbol: _sysInByte",
(Someone posted an unanswered message abt this a few months back and
the
manuals seem to give no hint)

The sysLib.h file has the definition but nowhere can I find the
function definition. I am not including syslib.h in my code.
It gets linked by default when I download.

Is this the right way to read/write ports?
_Where_ is the function defn? 
Can anyone give some pointers?

Thanks a lot.Any help is appreciated.

TRH.

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Mon Nov 25 04:03:17 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Mon Nov 25 04:03:18 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Mon Nov 25 04:03:14 PST 2002

        Subject: [AE] bad typecast while defining parameters
        Subject: Re: Problems with "taskOptionsGet"
        Subject: Re: unresolved sysmbol: sysInByte()
        Subject: Re: unresolved sysmbol: sysInByte()
        Subject: Heartfelt Appologies!!!
        Subject: Re: Tornado 2.2 for X86
        Subject: Re: unresolved sysmbol: sysInByte()
        Subject: RTOS Services Question:VxWorks vs Nucleus
        Subject: Re: Newbie asks:How to reload application from ethernet connector?
        Subject: how to use arppc
        Subject: CHECK THIS OUT!!!!
        Subject: question for arppc
        Subject: MMU and stack allocation
        Subject: Re: Tornado 2.2 for target X86
        Subject: Re: unresolved sysmbol: sysInByte()
        Subject: Re: question for arppc

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: [AE] bad typecast while defining parameters
Date: 24 Nov 2002 06:29:51 -0800
From: shie_e@elbit.co.il (Shie Erlich)
Organization: http://groups.google.com/
Message-ID: <59949c14.0211240629.e70517f@posting.google.com>

hi people,
i'm trying to build a bsp for vxworks AE, and having problems creating
00regions.sdf. i'm getting the following while building:

Bad typecast in region value kernelIoPoolRgn3,LOGICAL_ADDR : 
((0x28000000)  + CORE_DSCR_IN_OFFSET)

now, kernelIoPoolRgn3 and the parameters are defined as:

LogicalRegion  kernelIoPoolRgn3  {
    NAME              kernelIoPoolRgn3
    SYNOPSIS          Core discrete in - non cachable
    LOGICAL_ADDR      (START_EXT_PERIPH_ADRS + CORE_DSCR_IN_OFFSET)
    VIRTUAL_ADDR      (START_EXT_PERIPH_ADRS + CORE_DSCR_IN_OFFSET)
    SIZE              PTE_PAGE_SIZE
    PAGE_SIZE         0
    FLAGS            
(RGN_INFO_REGION|RGN_CFG_XLATE_NOT|RGN_CFG_VALID)
    MMU_ATTRIBUTES    MMU_ATTR_SUP_IO | MMU_ATTR_CACHE_OFF
}
Parameter START_EXT_PERIPH_ADRS {
    DEFAULT	0x28000000
}
Parameter CORE_DSCR_IN_OFFSET {
    DEFAULT	0x04200000
}
Parameter PTE_PAGE_SIZE {
    DEFAULT	(4 * MEM_SIZE_1K)
}

btw: PTE_PAGE_SIZE seems to be ok as it is used in other places
successfully.
i can't see the difference between CORE_DSCR_IN_OFFSET, which tornado
can't seem to understand and START_EXT_PERIPH_ADRS which seems to be
parsed fine.

ideas, anyone ?

thanks,
  shie erlich

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Problems with "taskOptionsGet"
Date: Sun, 24 Nov 2002 19:33:42 GMT
From: ggg+news@best.com (GGG)
Organization: rest
Message-ID: <qQ9E9.231$io.9081@iad-read.news.verio.net>
References: <ariiqa$dkb$1@overload.lbl.gov>

In article <ariiqa$dkb$1@overload.lbl.gov>,
Syed Rahman  <miftahur_rahman@yahoo.com> wrote:
>
>--0-132054248-1037877436=:25479
>Content-Type: text/plain; charset=us-ascii
>
>
>Hello there,
>
>I have a strange problem. According to the VxWorks manual "taskOptionsGet" is used
>to return the value of the option set.
>
>With reference to this I have two problems:-                                      
>i) Sometimes we spawn a task using more than one options.    For example:         
>taskSpawn("samp",100,VX_FP_TASK|VX_NO_STACK_FILL ,200,tsm2,0..)         IN THIS
>CASE our output will be the sum of the two options. How shall we identify -- which
>options were set from the SUM?

Bitwise ORing, just combines the options.  Not sure what what you mean by
indentifying which options were set.  See target/h/taskLib.h for
definitions of the various task options bits.

>ii) This is a practical problem I am facing. When I give :         
>taskSpawn("samp",100,VX_FP_TASK,2000,tsm2,0,0,.....);            AND THEN USE
>"taskOptionsGet", I get "0xC" as answer. Itried with the other options as well and
>have found that 4 gets added to each one of them.

VX_DEALLOC_STACK is the 0x4 value you see ORed in.  It is included by
default, and commented as internal in taskLib.h.  If you wish to debug and
be able to see the stack after your task has been deleted use
taskOptionsSet (use taskOptionsGet first to get the current values then turn
off VX_DEALLOC_STACK) to get rid of this bit.  It is there by default to
return the task stack to the system memory pool.

The documentation for taskOptionsSet says only VX_UNBREAKABLE can be
changed after the task is created, but I've had good success changing
VX_DEALLOC_STACK as well.  (Incidentally, VX_UNBREAKABLE is also
commented as internal in taskLib.h.)

GGG

>It will be very helpful if anyone can provide any solution.
>
>Thanking you in advance,
>
>Miftahur

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: unresolved sysmbol: sysInByte()
Date: 24 Nov 2002 12:01:33 -0800
From: yangliang_mr@hotmail.com (Liang Yang)
Organization: http://groups.google.com/
Message-ID: <4f57a77f.0211241201.6add92ce@posting.google.com>
References: <c21c6d3.0211240157.4f9e5ea9@posting.google.com> <newscache$pit26h$o71$1@lnews.actcom.co.il>

But the problem is if the pci card pluged into the board
only support I/O space, we need to use sysInByte() or 
sysOutByte() these kind of I/O specific functions to
read/write I/O ports.

I already try to define some macros as follows:

#define  sysInByte(address)   (*(UINT8 *)(address))
#define  sysOutByte(address,data)     (*(UINT8 *)address)=(data)

But all the data I get from the port is zero. While
according to the the PCI card manual, these ports
should have some initial value instead of all zeros.

I think we can't use these kind of direct memory access
macros to access I/O ports in I/O space.

Liang

"Leonid Rosenboim" <My_1st_name@Consultant.Com> wrote in message news:<newscache$pit26h$o71$1@lnews.actcom.co.il>...
> Tony,
> 
> these functions (e.g. sysInByte, sysOutLong) all have originated from the
> Intel IA32 (aka x86) architecture, where there is a separate memory and I/O
> address spaces. The x86 processors (Pentium, Cyrix, etc.) need to emply
> special instuctions in order to access the I/O address space (aka ports),
> so the x86 BSP offers a bunch of functions written in assembly, in the
> sysALib.s
> source file, that provide a C interface for port access.
> 
> In other architectures (mc68k, PPC, ARM, MIPS, ...), there is only a memory
> space,
> which is simply accessed by means of memory access (i.e. a normal pointer
> dereference) and there is thus no apparent need for these functions.
> 
> But sometimes, when one needs to port a driver that originated in the x86
> architecture (e.g. a PCMCIA, or ATA driver) to a "normal" architecture,
> he would face the "missing" functions, that only need to be converted
> to simple pointer references. But the so called "ports" are now memory
> mapped addresses, where the device at hand is connected.
> 
> This replacement could be done by simply modifying code, or by defining
> macros, e.g.
> 
>     #define    IDE_PORT_OFFSET
>     #define    sysInByte(port)        (*((u_char
> *)(IDE_PORT_OFFSET+(port))))
>     #define    sysOutByte(port,data) \
>         ((*(u_char *)(IDE_PORT_OFFSET+(port)))=(data))
> 
> Hope this explains enough ... ;-)
> --
> -----------------------------------------------------------------------
>    Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
>        Consultant                Email: my first name at consultant dot com
> 
> 
> "Tony_Rocky_Horror" <swami36@hotmail.com> wrote in message
> news:c21c6d3.0211240157.4f9e5ea9@posting.google.com...
> > Hi, I am trying to use SysInByte () and sysOutByte() to read/write
> > ports
> > on an IXP1200 StrongArm processor.
> >
> > When I download the module, it fails citing
> > "unresolved symbol: _sysInByte",
> > (Someone posted an unanswered message abt this a few months back and
> > the
> > manuals seem to give no hint)
> >
> > The sysLib.h file has the definition but nowhere can I find the
> > function definition. I am not including syslib.h in my code.
> > It gets linked by default when I download.
> >
> > Is this the right way to read/write ports?
> > _Where_ is the function defn?
> > Can anyone give some pointers?
> >
> >
> > Thanks a lot.Any help is appreciated.
> >
> > TRH.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: unresolved sysmbol: sysInByte()
Date: 24 Nov 2002 14:55:03 -0800
From: swami36@hotmail.com (Tony_Rocky_Horror)
Organization: http://groups.google.com/
Message-ID: <c21c6d3.0211241455.171165ea@posting.google.com>
References: <c21c6d3.0211240157.4f9e5ea9@posting.google.com> <newscache$pit26h$o71$1@lnews.actcom.co.il>

Works like a charm.
Thanks a bunch.

TRH.

"Leonid Rosenboim" <My_1st_name@Consultant.Com> wrote in message news:<newscache$pit26h$o71$1@lnews.actcom.co.il>...
> Tony,
> 
> these functions (e.g. sysInByte, sysOutLong) all have originated from the
> Intel IA32 (aka x86) architecture, where there is a separate memory and I/O
> address spaces. The x86 processors (Pentium, Cyrix, etc.) need to emply
> special instuctions in order to access the I/O address space (aka ports),
> so the x86 BSP offers a bunch of functions written in assembly, in the
> sysALib.s
> source file, that provide a C interface for port access.
> 
> In other architectures (mc68k, PPC, ARM, MIPS, ...), there is only a memory
> space,
> which is simply accessed by means of memory access (i.e. a normal pointer
> dereference) and there is thus no apparent need for these functions.
> 
> But sometimes, when one needs to port a driver that originated in the x86
> architecture (e.g. a PCMCIA, or ATA driver) to a "normal" architecture,
> he would face the "missing" functions, that only need to be converted
> to simple pointer references. But the so called "ports" are now memory
> mapped addresses, where the device at hand is connected.
> 
> This replacement could be done by simply modifying code, or by defining
> macros, e.g.
> 
>     #define    IDE_PORT_OFFSET
>     #define    sysInByte(port)        (*((u_char
> *)(IDE_PORT_OFFSET+(port))))
>     #define    sysOutByte(port,data) \
>         ((*(u_char *)(IDE_PORT_OFFSET+(port)))=(data))
> 
> Hope this explains enough ... ;-)
> --
> -----------------------------------------------------------------------
>    Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
>        Consultant                Email: my first name at consultant dot com
> 
> 
> "Tony_Rocky_Horror" <swami36@hotmail.com> wrote in message
> news:c21c6d3.0211240157.4f9e5ea9@posting.google.com...
> > Hi, I am trying to use SysInByte () and sysOutByte() to read/write
> > ports
> > on an IXP1200 StrongArm processor.
> >
> > When I download the module, it fails citing
> > "unresolved symbol: _sysInByte",
> > (Someone posted an unanswered message abt this a few months back and
> > the
> > manuals seem to give no hint)
> >
> > The sysLib.h file has the definition but nowhere can I find the
> > function definition. I am not including syslib.h in my code.
> > It gets linked by default when I download.
> >
> > Is this the right way to read/write ports?
> > _Where_ is the function defn?
> > Can anyone give some pointers?
> >
> >
> > Thanks a lot.Any help is appreciated.
> >
> > TRH.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Heartfelt Appologies!!!
Date: Mon, 25 Nov 2002 04:25:15 GMT
From: "Hope and Love" <hopeandlove2002@hotmail.com>
Organization: Shaw Residential Internet
Message-ID: <LChE9.43203$ea.716479@news2.calgary.shaw.ca>
Reply-To: hopeandlove2002@hotmail.com
Sender: Hope and Love <hopeandlove2002@hotmail.com>

 I would like to appologize to all the readers and anybody else affected by my indescretions, I felt that i was advertising a product that I know works and signed up as an affiliate to promote this product
 so I listed it in the individual newsgroups with the URL I did not realize I was spamming, as I am an idividual and putting it in groups 1 at a time....well I thought wrong and ticked off a lot of people!!
 For this I am sorry. The company that Im an affiliate for in did not have any knowledge of what I did, and as soon as they found out ordered me to stop immediatly..which I did and it will not happen again
 I do hope that You will accept My appologies and not hold this against myself or the company whose product I was promoting.
 
 Mike

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for X86
Date: 24 Nov 2002 20:56:24 -0800
From: v_mahesh@hotmail.com (Mahesh)
Organization: http://groups.google.com/
Message-ID: <4f7acce6.0211242056.750e9b6a@posting.google.com>
References: <20021121203910.05840.00005962@mb-ms.aol.com> <488e459a.0211221300.549ea28b@posting.google.com>

Hi john:

I have changed the default setting for Vga console to PC Console and
created a bootrom floppy. If i boot the kernel with that floppy i
still get the see the same problem. I feel something might be wrong
with my configuration.

Please bear with my lack of experience. Iam attaching the config.h and
configNet.h for your reference....anything seem blatantly wrong? I
will be happy if you can have a look at it and letme know if iam
missing something.

thanks
Mahesh

/*************************** CONFIG.H
***************************************/
/* config.h - template configuration header file */

/* Copyright 1984-2002 Wind River Systems, Inc. */

/*
TODO -	Remove the template modification history and begin a new
history
	starting with version 01a and growing the history upward with
	each revision.

modification history
- --------------------
01y,18apr02,rhe  Added C++ Protection
01x,20dec01,cjj  Changed RAM_HIGH_ADRS to 0x200000
01w,09dec01,dat  Adding USB support for ARM, MIPS, PPC, PENTIUM, SH,
added
		 optional TFFS support for all.
01v,15dec00,pai  Simplified the network configuration macros used in
this file.
                 References to INCLUDE_BSD, INCLUDE_DEFER_NET_INIT,
and
                 INCLUDE_NET_INIT have been removed.  This template
config.h
                 now specifies INCLUDE_NETWORK and INCLUDE_END.  The
remaining
                 network configuration comes from configAll.h.
01u,11dec00,pai  made END driver support the default for new WRN code.
01t,11dec00,pai  introduced INCLUDE_DEFER_NET_INIT configuration
constant for
                 new WRN code.
01s,08apr99,dat  SPR 26491, fixed PCI macro names
01r,29mar99,dat  SPR 26125, added INCLUDE_BSD
01q,02feb99,tm   added PCI AutoConfig support to template BSPs (SPR
24733)
01p,28sep98,dat  added default PCI and VME macros
01o,07nov98,dat  added note about the values for ROM_TEXT_ADRS, and
		 ROM_WARM_ADRS
01n,21jul98,db   defined INCLUDE_NETWORK, changed ROM_SIZE to 0x40000.
01m,07jul98,db   changed BSP_VERSION to "1.2" and BSP_REVISION to
"/0".
		 added BSP_VER_1_2 macro, defined INCLUDE_END, removed
		 END_OVERRIDE(Tornado 2.0 release).
01l,25aug97,dat  code review comments from Kitty
01k,07jul97,dat  added supported for new END ethernet drivers
01j,23apr97,dat  added ROM_WARM_ADRS, INCLUDE_CDROMFS
01i,02apr97,dat  more documentation about VME and other macros.
01h,12mar97,dat  added VME mapping macros
01g,10mar97,dat  comments from reviewers
01f,28feb97,dat  added INCLUDE_USER_APPL, USER_APPL_INIT
01e,05feb97,dat  incorporated comments from Thierry P.
01d,23jan97,dat  moved timer constants to template.h
01c,17jan97,dat  added INCLUDE_SERIAL, INCLUDE_MMU, INCLUDE_VME
01b,16jan97,dat  added LOCAL_MEM_AUTOSIZE and moved INCLUDE_SCSI2
outside
		 of #if FALSE.
01a,22oct96,ms   derived from the mv147 BSP
*/

/*
This file contains the configuration parameters for the template BSP.
This template starts simple - with most facilities excluded by
default.

TODO -
Present the user with simple straight forward options.  Do not ask the
user to encode values together to form a value to be loaded in a
register.
Let the source code, or the pre-processor, do the computational work
to
determine what value to load in a particular register.
*/

#ifndef	INCconfigh
#define	INCconfigh

#ifdef __cplusplus
extern "C" {
#endif

/* BSP version/revision identification, before configAll.h */

#define BSP_VER_1_1	1	/* 1.2 is backward compatible with 1.1 */
#define BSP_VER_1_2	1
#define BSP_VERSION	"1.2"
#define BSP_REV		"/0"	/* 0 for first revision */

#include "configAll.h"		/* Set the VxWorks default configuration */
#include "pc.h"

#define DEFAULT_BOOT_LINE \
	"fei(0,0)/distcomp/wind/target/config/pcPentium2_2/vxWorks " \
	"h=132.200.200.13 e=132.200.200.84 u=taoadmin pw=tao+oci tn=vx86"

/* TODO - values in this header file are dummy values, update as
needed */

/* memory configuration */

#define LOCAL_MEM_LOCAL_ADRS	0		/* fixed at zero */
#undef	LOCAL_MEM_AUTOSIZE			/* run-time memory sizing */
#define LOCAL_MEM_SIZE		0x400000	/* 4M memory */
#define	USER_RESERVED_MEM	0		/* see sysMemTop() */

/*
 * The constants ROM_TEXT_ADRS, ROM_SIZE, RAM_HIGH_ADRS, and
RAM_LOW_ADRS
 * are defined in config.h and Makefile.
 * All definitions for these constants must be identical.
 *
 * TODO - Make sure these values match those in your Makefile.  The
values
 * shown below are the defaults for a 68000 series system.  Pay
particular
 * attention to ROM_TEXT_ADRS and ROM_WARM_ADRS.  The correct default
values
 * are in the Makefile for each template BSP.
 */

#define ROM_BASE_ADRS		0xff800000	/* base address of ROM */
#define ROM_TEXT_ADRS		(ROM_BASE_ADRS+8) /* with PC & SP */
#define ROM_WARM_ADRS		(ROM_TEXT_ADRS+8) /* warm reboot entry */
#define ROM_SIZE		0x00040000	/* 256KB ROM space */
#define RAM_HIGH_ADRS		0x00200000	/* RAM address for bootrom */
#define RAM_LOW_ADRS		0x00010000	/* RAM address for vxWorks */

/* Serial port configuration */

/* Commented for Now */
/* #define	INCLUDE_SERIAL */
#define INCLUDE_PC_CONSOLE

#ifdef  INCLUDE_PC_CONSOLE
#define PC_CONSOLE              0
#undef  N_VIRTUAL_CONSOLES
#define N_VIRTUAL_CONSOLES      2

#define KBD_INT_VEC             (INT_VEC_GET (KBD_INT_LVL))

#endif
#undef	NUM_TTY
#define	NUM_TTY			(N_UART_CHANNELS)	 /* defined in template.h */

#define PC_KBD_TYPE             PC_PS2_101_KBD

/* Timer configuration */

#undef  INCLUDE_TIMESTAMP		/* no timestamp driver support */

/*
 * Cache configuration
 *
 * TODO -
 * All cache is turned off to begin with. Activate caching after basic
 * BSP functionality is achieved.  Start with instruction caching,
followed
 * by data caching.  Begin without snooping options; and turn those on
 * later if the board supports it.
 *
 * Note that when MMU is enabled, cache modes are controlled by
 * the MMU table entries in sysPhysMemDesc[], not the cache mode
 * macros defined here.
 */

#undef	INCLUDE_CACHE_SUPPORT	/* no cacheLib support */
#undef	USER_I_CACHE_ENABLE
#undef	USER_I_CACHE_MODE
#define	USER_I_CACHE_MODE	CACHE_DISABLED
#undef	USER_D_CACHE_ENABLE
#undef	USER_D_CACHE_MODE
#define	USER_D_CACHE_MODE	CACHE_DISABLED
#undef	USER_B_CACHE_ENABLE

/* MMU configuration */

#undef	INCLUDE_MMU_BASIC	/* no MMU support */
#undef	INCLUDE_MMU_FULL	/* no MMU support */

/* Network driver configuration */

#define	INCLUDE_NETWORK
#define	INCLUDE_END		/* Enhanced Network Driver (see configNet.h) */

#undef	INCLUDE_EX
#undef	INCLUDE_ENP
#undef	INCLUDE_SM_NET

/* VME configuration */

/*
 * TODO -
 * Only those options that are actually user changeable should be
defined
 * here.  Options that cannot be changed should be moved to
template.h.
 */

#undef	INCLUDE_VME

/* A16 master window maps all of A16 to 0xff800000 locally */

#define	VME_A16_MSTR_BUS	0x0
#define	VME_A16_MSTR_SIZE	0x00010000
#define	VME_A16_MSTR_LOCAL	0xff800000

/* A24 master window maps all of A24 to 0xf8000000 locally */

#define	VME_A24_MSTR_BUS	0x0
#define	VME_A24_MSTR_SIZE	0x01000000
#define	VME_A24_MSTR_LOCAL	0xf8000000

/* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
local. */

#define	VME_A32_MSTR_BUS	(0x80000000)
#define	VME_A32_MSTR_SIZE	(0x02000000)
#define	VME_A32_MSTR_LOCAL	(0x80000000)

/* A16 slave window is not supported */

#define	VME_A16_SLV_LOCAL	0x0
#define	VME_A16_SLV_BUS		0x0
#define	VME_A16_SLV_SIZE	0x0

/* A24 slave window maps 1st 8MB of local memory to bus address
0x00800000 */

#define	VME_A24_SLV_LOCAL	LOCAL_MEM_LOCAL_ADRS
#define	VME_A24_SLV_BUS		0x00800000
#define	VME_A24_SLV_SIZE	0x00800000

/* A32 slave window maps all local memory to bus address 0x80000000 */

#define	VME_A32_SLV_LOCAL	(LOCAL_MEM_LOCAL_ADRS)
#define	VME_A32_SLV_BUS		0x80000000
#define	VME_A32_SLV_SIZE	((UINT)sysPhysMemTop() -
LOCAL_MEM_LOCAL_ADRS)

/* PCI configuration */

#undef	INCLUDE_PCI
#undef  INCLUDE_PCI_AUTOCONF

#ifndef PCI_CFG_TYPE
#   ifdef INCLUDE_PCI_AUTOCONF
#      define PCI_CFG_TYPE PCI_CFG_AUTO
#   else
#      define PCI_CFG_TYPE PCI_CFG_FORCE
#   endif /* INCLUDE_PCI_AUTOCONF */
#endif /* PCI_CFG_TYPE */
 

/*
 * TODO -
 * Only those options that are actually user changeable should be
defined
 * here.  Options that cannot be changed should be moved to
template.h.
 */

/* PCI I/O master window */

#define	PCI_MSTR_IO_LOCAL	0xff800000
#define	PCI_MSTR_IO_BUS		0x0
#define	PCI_MSTR_IO_SIZE	0x00010000

/* PCI MEMIO master (non-prefetch memory) window */

#define	PCI_MSTR_MEMIO_LOCAL	0xf8000000
#define	PCI_MSTR_MEMIO_BUS	0x0
#define	PCI_MSTR_MEMIO_SIZE	0x01000000

/* PCI MEM master (prefetchable memory) window */

#define	PCI_MSTR_MEM_LOCAL	0xfa000000
#define	PCI_MSTR_MEM_BUS	0x0
#define	PCI_MSTR_MEM_SIZE	0x01000000

/* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
local. */

#define	VME_A32_MSTR_BUS	(0x80000000)
#define	VME_A32_MSTR_SIZE	(0x02000000)
#define	VME_A32_MSTR_LOCAL	(0x80000000)

/* A16 slave window is not supported */

#define	VME_A16_SLV_LOCAL	0x0
#define	VME_A16_SLV_BUS		0x0
#define	VME_A16_SLV_SIZE	0x0

/* A24 slave window maps 1st 8MB of local memory to bus address
0x00800000 */

#define	VME_A24_SLV_LOCAL	LOCAL_MEM_LOCAL_ADRS
#define	VME_A24_SLV_BUS		0x00800000
#define	VME_A24_SLV_SIZE	0x00800000

/* A32 slave window maps all local memory to bus address 0x80000000 */

#define	VME_A32_SLV_LOCAL	(LOCAL_MEM_LOCAL_ADRS)
#define	VME_A32_SLV_BUS		0x80000000
#define	VME_A32_SLV_SIZE	((UINT)sysPhysMemTop() -
LOCAL_MEM_LOCAL_ADRS)

/* SCSI driver configuration */

#if	FALSE			/* change FALSE to TRUE for SCSI interface */
#define	INCLUDE_SCSI		/* include SCSI interface */
#define	INCLUDE_SCSI_DMA	/* include SCSI DMA interface */
#define	INCLUDE_SCSI_BOOT	/* include SCSI for boot option */
#define	INCLUDE_DOSFS		/* DOS file system */
#undef	INCLUDE_TAPEFS		/* tape file system */
#undef	INCLUDE_CDROMFS		/* CD-ROM (iso9660) file system */
#define SYS_SCSI_CONFIG		/* BSP scsi config routine */
#endif	/* FALSE/TRUE */

/* Select either SCSI-1 or SCSI-2, independent of INCLUDE_SCSI */

#define INCLUDE_SCSI2		/* undef for SCSI-1 support */

/*
 * User application initialization
 *
 * USER_APPL_INIT must be a valid C statement or block.  It is
 * included in the usrRoot() routine only if INCLUDE_USER_APPL is
 * defined.  The code for USER_APPL_INIT is only an example.  The
 * user is expected to change it as needed.  The use of taskSpawn
 * is recommended over direct execution of the user routine.
 */

#undef	INCLUDE_USER_APPL
#define	USER_APPL_INIT \
	{ \
	IMPORT int myAppInit(); \
	taskSpawn ("myApp", 30, 0, 5120, \
		   myAppInit, 0x1, 0x2, 0x3, 0,0,0,0,0,0,0); \
	}

/* Configurable interrupt vectors/levels (static defs go in
template.h) */

#if	FALSE
#define	INT_VEC_ABORT		xxx
#define	INT_VEC_CLOCK		xxx
...
#define	INT_LVL_ABORT		xxx
#define	INT_LVL_CLOCK		xxx
...
#endif

/* Basic USB Support (PPC, PENTIUM, ARM, MIPS, SH only) */

#if FALSE	/* set TRUE to include USB support */

/* USB Host Components */

#   define INCLUDE_USB 			/* Main USB Component */
#   undef  INCLUDE_USB_INIT		/* USB Initialization */
#   define INCLUDE_UHCI			/* UHCI Controller Driver */
#   undef  INCLUDE_UHCI_INIT    	/* UHCI Initialization */
#   define INCLUDE_OHCI			/* OHCI Controller Driver */
#   undef  INCLUDE_OHCI_INIT		/* OHCI Initialization */
#   undef  INCLUDE_OHCI_PCI_INIT 	/* OHCI PCI Initialization */
#   define INCLUDE_USBTOOL		/* usbTool Application */
#   undef  INCDLUE_USB_AUDIO_DEMO	/* USB Audio Demo */
#   define INCLUDE_USB_MOUSE 		/* USB Mouse Driver */
#   undef  INCLUDE_USB_MOUSE_INIT 	/* Mouse Driver Initialization */
#   define INCLUDE_USB_KEYBOARD 	/* USB Keyboard Driver */
#   undef  INCLUDE_USB_KEYBOARD_INIT 	/* Keyboard Driver
Initialization */
#   define INCLUDE_USB_PRINTER 		/* USB Printer Driver */
#   undef  INCLUDE_USB_PRINTER_INIT 	/* Printer Driver Initialization
*/
#   define INCLUDE_USB_SPEAKER 		/* USB Speaker Driver */
#   undef  INCLUDE_USB_SPEAKER_INIT 	/* Speaker Driver Initialization
*/
#   undef  INCLUDE_USB_MS_BULKONLY 	/* USB Bulk Driver */
#   undef  INCLUDE_USB_MS_BULKONLY_INIT /* Bulk Driver Initialization
*/
#   undef  INCLUDE_USB_MS_CBI 		/* USB CBI Driver */
#   undef  INCLUDE_USB_MS_CBI_INIT 	/* CBI Driver Initialization */
#   undef  INCLUDE_USB_PEGASUS_END 	/* USB Pegasus Network Driver */
#   undef  INCLUDE_USB_PEGASUS_END_INIT /* Pegaus Driver
Initialization */

/*  USB Parameters */

#   define BULK_DRIVE_NAME "/bd" 		/* Bulk Drive Name */	
#   define CBI_DRIVE_NAME "/cbid" 		/* CBI Drive Name */
#   define PEGASUS_IP_ADDRESS "90.0.0.3" 	/* Pegasus IP Address */
#   define PEGASUS_DESTINATION_ADDRESS "90.0.0.53" /* Destination IP
Address */
#   define PEGASUS_NET_MASK 0xffffff00 		/* Pegasus Net Mask */
#   define PEGASUS_TARGET_NAME "host" 		/* Pegasus Target Name */

#endif /* End of optional USB support */

/* Optional TFFS support.  Just define INCLUDE_TFFS to activate */

#undef	INCLUDE_TFFS

#include "template.h"		/* Verify user options, specify i/o addr etc */

#undef INCLUDE_MMU_BASIC      /* bundled mmu support */
#undef INCLUDE_CACHE_SUPPORT  /* cache support */

#ifdef __cplusplus
}
#endif

#endif	/* INCconfigh */
#if defined(PRJ_BUILD)
#include "prjParams.h"
#endif
/******************************************************************************************************/

/**************************** ConfigNet.h
******************************************************/
/* configNet.h - network configuration header */

/* Copyright 1984-2002 Wind River Systems, Inc. */

/*
TODO -	Remove the template modification history and begin a new
history
	starting with version 01a and growing the history upward with
	each revision.

modification history
- --------------------
01e,28may02,dat  exclude driver if NETWORK not defined, 77135
01d,18apr02,rhe  Added C++ Protection
01c,13dec00,pai  corrected endDevTbl[] definition (SPR #62994) and
specified
                 the return type in the END_LOAD_FUNC declaration.
01b,21jul98,db   dec21x40End replaced with template END driver. 
01a,07jul97,dat  written (from mv2603/configNet.h,ver 01b)
*/
 
#ifndef INCnetConfigh
#define INCnetConfigh

#ifdef __cplusplus
extern "C" {
#endif

#ifdef INCLUDE_NETWORK /* ignore everything if NETWORK not included */

#include "vxWorks.h"
#include "end.h"

/* This template presumes the template END driver */

#define FEI82557_LOAD_FUNC	fei82557EndLoad
#define FEI82557_BUFF_LOAN      1

/* <devAdrs>:<PCIadrs>:<ivec>:<ilevel>:<memBase>:<memSize>:<userFlags>
*/

#define	FEI82557_LOAD_STRING	"-1:0x00:0x20:0x20:0x00"

IMPORT END_OBJ * FEI82557_LOAD_FUNC ();

END_TBL_ENTRY endDevTbl [] =
    {
    { 0, FEI82557_LOAD_FUNC, FEI82557_LOAD_STRING, FEI82557_BUFF_LOAN,
NULL, FALSE},
    { 0, END_TBL_END, NULL, 0, NULL},
    };

#ifdef __cplusplus
}
#endif

#endif /* INCLUDE_NETWORK */
#endif /* INCnetConfigh */

john_94501@yahoo.com (John) wrote in message news:<488e459a.0211221300.549ea28b@posting.google.com>...
> Hello,
> 
> > My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
> > target Intel X86 and for windows host.
> > I have created a Bootrom Image for Network configuration and When i try to boot
> > the kernel through the floppy disk, the screen becomes blank and it
> > automatically reboots. 
> 
> You need to change the console settings. In the newer versions of
> VxWorks, including AE 1.x and 5.5, the default setting for the console
> is the serial port (COM1 using DOS style naming, /tyCo/0 in VxWorks).
> 
> You can switch back to the VGA console if you need to (search the
> archives for this group - it has been covered before), or you can
> simply connect a terminal (or PC running HyperTerminal) to the serial
> port and use that.
> 
> HTH,
> 
> John...
>  
> > I will be happy if somebody can shed some on it. Also, is there any way to
> > debug and see what is going on underneath the hood.  
> > 
> > The configuration and software versions are as follows:
> > VxWorks - 5.5
> > Tornado - 2.2
> > CPU - PENTIUM
> > C++Compiler - g++pentium (version - 2.93)
> > Host - Windows 2000.
> > Ethernet Driver - fei82557End Intel Ethernet Driver.
> > 
> > The config.h is configured using these macros
> > INCLUDE_NETWORK
> > INCLUDE_END,
> > INCLUDE_FEI_END,
> > INCLUDE_FTP,
> > INCLUDE_FTP_SERVER.
> > 
> > thanks
> > Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: unresolved sysmbol: sysInByte()
Date: Sun, 24 Nov 2002 12:36:30 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$pit26h$o71$1@lnews.actcom.co.il>
References: <c21c6d3.0211240157.4f9e5ea9@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

Tony,

these functions (e.g. sysInByte, sysOutLong) all have originated from the
Intel IA32 (aka x86) architecture, where there is a separate memory and I/O
address spaces. The x86 processors (Pentium, Cyrix, etc.) need to emply
special instuctions in order to access the I/O address space (aka ports),
so the x86 BSP offers a bunch of functions written in assembly, in the
sysALib.s
source file, that provide a C interface for port access.

In other architectures (mc68k, PPC, ARM, MIPS, ...), there is only a memory
space,
which is simply accessed by means of memory access (i.e. a normal pointer
dereference) and there is thus no apparent need for these functions.

But sometimes, when one needs to port a driver that originated in the x86
architecture (e.g. a PCMCIA, or ATA driver) to a "normal" architecture,
he would face the "missing" functions, that only need to be converted
to simple pointer references. But the so called "ports" are now memory
mapped addresses, where the device at hand is connected.

This replacement could be done by simply modifying code, or by defining
macros, e.g.

    #define    IDE_PORT_OFFSET
    #define    sysInByte(port)        (*((u_char
*)(IDE_PORT_OFFSET+(port))))
    #define    sysOutByte(port,data) \
        ((*(u_char *)(IDE_PORT_OFFSET+(port)))=(data))

Hope this explains enough ... ;-)
- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

"Tony_Rocky_Horror" <swami36@hotmail.com> wrote in message
news:c21c6d3.0211240157.4f9e5ea9@posting.google.com...
> Hi, I am trying to use SysInByte () and sysOutByte() to read/write
> ports
> on an IXP1200 StrongArm processor.
>
> When I download the module, it fails citing
> "unresolved symbol: _sysInByte",
> (Someone posted an unanswered message abt this a few months back and
> the
> manuals seem to give no hint)
>
> The sysLib.h file has the definition but nowhere can I find the
> function definition. I am not including syslib.h in my code.
> It gets linked by default when I download.
>
> Is this the right way to read/write ports?
> _Where_ is the function defn?
> Can anyone give some pointers?
>
>
> Thanks a lot.Any help is appreciated.
>
> TRH.

---------------------------

Newsgroups: comp.os.vxworks
Subject: RTOS Services Question:VxWorks vs Nucleus
Date: 24 Nov 2002 22:43:54 -0800
From: kmatpral@yahoo.com (Kott)
Organization: http://groups.google.com/
Message-ID: <3755c855.0211242243.8800769@posting.google.com>

Kott - 

In VxWorks we have taskVarAdd() and taskVarSet() services which allows
 to add  task info to the Task Context.

Is there any equivalent  or similar  service in Nucleus RTOS ?

Any help or pointers  would be appreciated.

Thanks
Kott

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Newbie asks:How to reload application from ethernet connector?
Date: Mon, 25 Nov 2002 08:47:09 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <arskhu$mmn$1@snoopy.bndlg.de>
References: <60fb21d0.0211220901.5e3294ab@posting.google.com>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Hi Dan,

there is an FTP-server you may (already have) configure(d) into vxWorks.
First step: bring your ethernet up and running.
Scnd: add the identifier of your NIC to the others-field in your bootline.
After reboot you should be able to ping your target. When opening FTP-client
on host, you will be connected to the current drive on target.
Security: Its a seperate feature to include and will manage login of FTP,
Telnet and Target-Shell.
No file based security available as long as you don't implement it yourself.

Regards,
Michael

"Dan" <zarfus@hotmail.com> schrieb im Newsbeitrag
news:60fb21d0.0211220901.5e3294ab@posting.google.com...
> We are working with a DiskOnChip2000 on a pentium with VxWorks.
> How can we set it up so that we can reload our executables
> from the ethernet port? Right now, we have to reprogram our targets by
> swapping the disk on chip parts.
> Do we have to write application code, or can we just leave an FTP
> server running
> on the embedded machine?  Is there an FTP server for VxWorks?
> Any ideas out there?

---------------------------

Newsgroups: comp.os.vxworks
Subject: how to use arppc
Date: Mon, 25 Nov 2002 14:54:08 +0800
From: "echo" <echoecho111@yahoo.com.cn>
Organization: Alcatel
Message-ID: <arshg8$6v$1@bt02e2.god.bel.alcatel.be>

hi, all
  I want to extract a object file from a Archive file, i.e.,.a file.
  Could anybody tell me whether I can use "arppc" to extract  .o from a
archive?
  Thanks a lot!

slf

---------------------------

Newsgroups: comp.os.vxworks
Subject: CHECK THIS OUT!!!!
Date: Sun, 24 Nov 2002 23:45:40 GMT
From: "Hope and Love" <hopeandlove2002@hotmail.com>
Organization: Shaw Residential Internet
Message-ID: <EwdE9.87666$ka.2285122@news1.calgary.shaw.ca>
Reply-To: hopeandlove2002@hotmail.com
Sender: Hope and Love <hopeandlove2002@hotmail.com>

Are You looking for the Perfect Christmas Gift for that Special Lady in Your Life???
Do You want to Help her have that smooooth look and feel???

http://www.advanceddermalsolutions.com/cgi-bin/affiliates/clickthru.cgi/Hope

---------------------------

Newsgroups: comp.os.vxworks
Subject: question for arppc
Date: Mon, 25 Nov 2002 17:19:10 +0800
From: "echo" <echoecho111@yahoo.com.cn>
Organization: Alcatel
Message-ID: <arsq06$a44$1@bt02e2.god.bel.alcatel.be>

Hi all,

Do you know how to use 'arppc' command to extract *.o from libPPC860gnuvx.a?

I know we may list the content of libPPC860gnuvx.a using 'arppc -tv', and
delete the *.o using 'arppc -dv', add the *.o using 'arppc -cru'.

Thanks for your help!

---------------------------

Newsgroups: comp.os.vxworks
Subject: MMU and stack allocation
Date: 25 Nov 2002 01:22:03 -0800
From: czdua@ocag.ch (Alex)
Organization: http://groups.google.com/
Message-ID: <7abe0ab2.0211250122.9021360@posting.google.com>

Hi all

We use vxWorks5.4.2/Tornado 2.0.2 on a PCORE 6750 board from Force
with 128MB RAM on it:

If I define "INCLUDE_MMU_BASIC" and set LOCAL_MEM_SIZE to 0x02000000
the stack   of the different tasks isn't allocated from high address
to lower addresses. The stack is instead allocated from 0x01000000 to
lower addresses.

- -> memShow(1)

FREE LIST:
  num     addr      size
  --- ---------- ----------
    1  0x1ffee90        600
    2   0xf60778         24
    3   0xf60600        344
    4   0xf60e98        400
    5  0x1ffb1e8       1152
    6   0x4404f8   11607112
    7  0x1800000    8368600

SUMMARY:
 status   bytes    blocks   avg block  max block
 ------ --------- -------- ---------- ----------
current
   free  19978232        7    2854033  11607112
  alloc   9118456      236      38637        -
cumulative
  alloc   9144376      292      31316        -
value = 0 = 0x0
- -> i

  NAME        ENTRY       TID    PRI   STATUS      PC       SP    
ERRNO  DELAY
- ---------- ------------ -------- --- ---------- -------- --------
- ------- -----
tExcTask   excTask        ffe7d8   0 PEND         1f5200   ffe6e8     
 0     0
tLogTask   logTask        ffbe50   0 PEND         1f5200   ffbd70     
 0     0
tShell     shell          f5b0d8   1 READY        18aff8   f5ad48     
 0     0
tRlogind   rlogind        f70c00   2 PEND         185b7c   f70820     
 0     0
tRlogOutTasrlogOutTask   1ffc9f8   2 READY        185b7c  1ffc860     
 0     0
tRlogInTaskrlogInTask     f53e38   2 READY        1859d0   f53c90     
 0     0
tWdbTask   17cab4         f63738   3 PEND         185b7c   f63570     
 0     0
tScsiTask  scsiMgr        fe0350   5 PEND         185b7c   fe0290     
 0     0
tAioIoTask1aioIoTask      fef848  50 PEND         18629c   fef790     
 0     0
tAioIoTask0aioIoTask      fe8630  50 PEND         18629c   fe8578     
 0     0
tNetTask   netTask        fa1188  50 READY        187b48   fa10b0     
3d     0
tAioWait   aioWaitTask    ff6a60  51 PEND         185b7c   ff68f8     
 0     0
tMountd    mountd         f6ddf0  55 PEND         185b7c   f6dc80  
d0003     0
tNfsd      nfsd           f6b3d8  55 PEND         185b7c   f6b250  
d0003     0
tNfsd0     nfsdRequestP   f67b10  60 PEND         1f5200   f679f8     
 0     0
tPortmapd  portmapd       f6f660 100 PEND         185b7c   f6f4e0     
16     0
value = 0 = 0x0
- -> sysBoardShow

BOARD         INFORMATION
=========================
Board:                  FORCE COMPUTERS PPC/PowerCore-6750
Compilation date :      Nov 25 2002 08:31:07
Processor:              #0

Software:               VxWorks 5.4.2
                        BSP revision 1.2/2-0

Type <CR> to continue, Q<CR> to stop:

MEMORY        INFORMATION
=========================
Memory configuration:   32 MByte
Memory size         :   32 MByte
Physical Memory size:   32 MByte
Reserved Memory size:   0 MByte
        (MMU in basic mode)

Available Memory:
          0 MB on-board memory.
        128 MB SDRAM on lower memory module.

Memory Bus Speed:       82.5MHz

Type <CR> to continue, Q<CR> to stop: q
value = 0 = 0x0
- -

If I undef "INCLUDE_MMU_BASIC" the stack of the tasks will be
allocated correctly from 0x02000000 to lower addresses. There is
another point. As soon as the bootprocess is finished an I start a new
task(for example tRlogOutTask above), then the stack is correctly
allocated from 0x02000000 down.

Could anyone explain to me, why there is this strange behaviour when
using the "MMU".

Thanks in advance
Alex

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for target X86
Date: 25 Nov 2002 01:49:47 -0800
From: be_gyus@yahoo.com (james)
Organization: http://groups.google.com/
Message-ID: <ff42611f.0211250149.4d41360a@posting.google.com>
References: <4f7acce6.0211211832.1ab3277e@posting.google.com>

v_mahesh@hotmail.com (Mahesh) wrote in message news:<4f7acce6.0211211832.1ab3277e@posting.google.com>...
> Hi:
> 
> My name is Mahesh, Iam working on creating and Configuring VxWorks
> Kernel for target Intel X86 and for windows host.
> I have created a Bootrom Image for Network configuration and When i
> try to boot the kernel through the floppy disk, the screen becomes
> blank and it automatically reboots.
> 
> I will be happy if somebody can provide me some information. Also, is
> there any way to debug and see what is going on underneath the hood.
> 
> The configuration and software versions are as follows:
> VxWorks - 5.5
> Tornado - 2.2
> CPU - PENTIUM
> C++Compiler - g++pentium (version - 2.93)
> Host - Windows 2000.
> Ethernet Driver - fei82557End Intel Ethernet Driver.
> 
> The config.h is configured using these macros
> INCLUDE_NETWORK
> INCLUDE_END,
> INCLUDE_FEI_END,
> INCLUDE_FTP,
> INCLUDE_FTP_SERVER.
> 
> thanks
> Mahesh

 Hi Mahesh,

 This is basically the configuration problem. In your config.h
corresponding to the BSP you are using, check whether the Bootline
parameters u have given is for fei....& with the right ip address.Mind
you ,There should be only one bootline.. comment the other lines if
exists in the Bootline for the particular BSP.
 Check whether your PC_console has been made TRUE...this will get u a
blue screen on the console (monitor if used) if made true else it will
give u a blank screen after the vxld........
 or the systme remains in a hung state.
 To cross check whether the target is up and the n/w is in tact ,Keep
pinging the target from the host m/e.

 These are the basic things to be done while building the bootrom.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: unresolved sysmbol: sysInByte()
Date: Mon, 25 Nov 2002 11:45:20 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$htl46h$gu3$1@lnews.actcom.co.il>
References: <c21c6d3.0211240157.4f9e5ea9@posting.google.com> <newscache$pit26h$o71$1@lnews.actcom.co.il> <4f57a77f.0211241201.6add92ce@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

Look into the conjfiguration of your PCI bridge -
there you will find a register which sets an offset
(or window) for PCI I/O space as seen from the
processor memory space, and then you can use
my macros, where IDE_PORT_OFFSET should be
replaced by PCI_IO_OFFSET (either a constant
or a variable), while the <port> argument would
be the port address as retreived from the device's
base address config register.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

"Liang Yang" <yangliang_mr@hotmail.com> wrote in message
news:4f57a77f.0211241201.6add92ce@posting.google.com...
> But the problem is if the pci card pluged into the board
> only support I/O space, we need to use sysInByte() or
> sysOutByte() these kind of I/O specific functions to
> read/write I/O ports.
>
> I already try to define some macros as follows:
>
> #define  sysInByte(address)   (*(UINT8 *)(address))
> #define  sysOutByte(address,data)     (*(UINT8 *)address)=(data)
>
> But all the data I get from the port is zero. While
> according to the the PCI card manual, these ports
> should have some initial value instead of all zeros.
>
> I think we can't use these kind of direct memory access
> macros to access I/O ports in I/O space.
>
> Liang
>
>
>
> "Leonid Rosenboim" <My_1st_name@Consultant.Com> wrote in message
news:<newscache$pit26h$o71$1@lnews.actcom.co.il>...
> > Tony,
> >
> > these functions (e.g. sysInByte, sysOutLong) all have originated from
the
> > Intel IA32 (aka x86) architecture, where there is a separate memory and
I/O
> > address spaces. The x86 processors (Pentium, Cyrix, etc.) need to emply
> > special instuctions in order to access the I/O address space (aka
ports),
> > so the x86 BSP offers a bunch of functions written in assembly, in the
> > sysALib.s
> > source file, that provide a C interface for port access.
> >
> > In other architectures (mc68k, PPC, ARM, MIPS, ...), there is only a
memory
> > space,
> > which is simply accessed by means of memory access (i.e. a normal
pointer
> > dereference) and there is thus no apparent need for these functions.
> >
> > But sometimes, when one needs to port a driver that originated in the
x86
> > architecture (e.g. a PCMCIA, or ATA driver) to a "normal" architecture,
> > he would face the "missing" functions, that only need to be converted
> > to simple pointer references. But the so called "ports" are now memory
> > mapped addresses, where the device at hand is connected.
> >
> > This replacement could be done by simply modifying code, or by defining
> > macros, e.g.
> >
> >     #define    IDE_PORT_OFFSET
> >     #define    sysInByte(port)        (*((u_char
> > *)(IDE_PORT_OFFSET+(port))))
> >     #define    sysOutByte(port,data) \
> >         ((*(u_char *)(IDE_PORT_OFFSET+(port)))=(data))
> >
> > Hope this explains enough ... ;-)
> > --
> > -----------------------------------------------------------------------
> >    Leonid Rosenboim     Visit:
http://www.masada2000.org/historical.html
> >        Consultant                Email: my first name at consultant dot
com
> >
> >
> > "Tony_Rocky_Horror" <swami36@hotmail.com> wrote in message
> > news:c21c6d3.0211240157.4f9e5ea9@posting.google.com...
> > > Hi, I am trying to use SysInByte () and sysOutByte() to read/write
> > > ports
> > > on an IXP1200 StrongArm processor.
> > >
> > > When I download the module, it fails citing
> > > "unresolved symbol: _sysInByte",
> > > (Someone posted an unanswered message abt this a few months back and
> > > the
> > > manuals seem to give no hint)
> > >
> > > The sysLib.h file has the definition but nowhere can I find the
> > > function definition. I am not including syslib.h in my code.
> > > It gets linked by default when I download.
> > >
> > > Is this the right way to read/write ports?
> > > _Where_ is the function defn?
> > > Can anyone give some pointers?
> > >
> > >
> > > Thanks a lot.Any help is appreciated.
> > >
> > > TRH.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: question for arppc
Date: Mon, 25 Nov 2002 11:47:23 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$vwl46h$iu3$1@lnews.actcom.co.il>
References: <arsq06$a44$1@bt02e2.god.bel.alcatel.be>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

arppc -xv taskLib.o libPPC860gnuvx.a

- -- Just curious - what DO you use your manuals for ?
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

"echo" <echoecho111@yahoo.com.cn> wrote in message
news:arsq06$a44$1@bt02e2.god.bel.alcatel.be...
> Hi all,
>
> Do you know how to use 'arppc' command to extract *.o from
libPPC860gnuvx.a?
>
> I know we may list the content of libPPC860gnuvx.a using 'arppc -tv', and
> delete the *.o using 'arppc -dv', add the *.o using 'arppc -cru'.
>
> Thanks for your help!
>
>

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Mon Nov 25 05:41:48 2002
From: sailinder.harpal@philips.com
Date: Mon Nov 25 05:41:49 PST 2002
Subject: start address intel386

Hi all,

This question is for the Intel 386 experts.

When I generate a Motorola 'S' Format file with Tornado 2.0. The output contains an address range from ROM_BASE_ADRS up to 234KB, why I don't know.
My ROM_SIZE is 512KB big. Why doesn't it shows the whole address range.

I know the Intel Program Counter starts from the Highest address. I'm wandering if it is possible to give an options to the VxWorks compiler or linker, that the PC jump from the Highest address to the our ROM_TEXT_ADRS (in our case 0x03F80000).
Can anyone help me?

Thanks in advance.

From vxwexplo-errs@csg.lbl.gov  Mon Nov 25 20:57:42 2002
From: "Sabarivel S" <sabaris@future.futsoft.com>
Date: Mon Nov 25 20:57:43 PST 2002
Subject: WDB debugger timing out ?!

Hi,

What may be the reasons  for the Tornado WDB timing out ?
And how we can increase the WDB timeout value ?
Kindly help me out in this regard.

regards,
sabari

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************

From vxwexplo-errs@csg.lbl.gov  Mon Nov 25 22:57:18 2002
From: radha@telecruz.com
Date: Mon Nov 25 22:57:20 PST 2002
Subject: RE: WDB debugger timing out ?!

Hi,

In Tornado's Target server configuaration, you can set the timeout.
(in Tornado: tools->Target server->configure-->>)

-Radha Krishna
TeleCruz,
India

Submitted-by vxwexplo-errs@csg.lbl.gov  Mon Nov 25 20:57:42 2002
Submitted-by: "Sabarivel S" <sabaris@future.futsoft.com>

Hi,

What may be the reasons  for the Tornado WDB timing out ?
And how we can increase the WDB timeout value ?
Kindly help me out in this regard.

regards,
sabari

From vxwexplo-errs@csg.lbl.gov  Tue Nov 26 04:03:25 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Tue Nov 26 04:03:27 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Tue Nov 26 04:03:20 PST 2002

        Subject: Re: question for arppc
        Subject: Re: Download Procedure
        Subject: Re: Tornado 2.2 for target X86
        Subject: Re: start address intel386
        Subject: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
        Subject: Need help with fromelf
        Subject: Telnet & Console
        Subject: Re: Tornado 2.2 for X86
        Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
        Subject: Re: Telnet & Console
        Subject: trashed vtable
        Subject: Re: WindRiver Tornado problem: ftp server with wu-ftpd in Linux
        Subject: ads860 cpm network working fine with crossover cable but not with the network.
        Subject: Re: Telnet & Console
        Subject: Re: Tornado 2.2 for target X86
        Subject: Re: trashed vtable
        Subject: Re: Tornado 2.2 for target X86
        Subject: Re: ifAddrAdd
        Subject: commit_and_inc: VirtualAlloc failed
        Subject: HELP!!!!!!why can't my vxworks DHCP client work properly???
        Subject: Re: HELP!!!!!!why can't my vxworks DHCP client work properly???
        Subject: Re: HELP!!!!!!why can't my vxworks DHCP client work properly???
        Subject: Re: HELP!!!!!!why can't my vxworks DHCP client work properly???
        Subject: Re: Large App in Boot ROM

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: question for arppc
Date: Mon, 25 Nov 2002 13:01:24 GMT
From: "Joe Welfeld" <jwelfeld@paragon-networks.com>
Organization: Prodigy Internet http://www.prodigy.com
Message-ID: <EapE9.120$PZ5.51398679@newssvr10.news.prodigy.com>
References: <arsq06$a44$1@bt02e2.god.bel.alcatel.be>
Reply-To: "Joe Welfeld" <jwelfeld@paragon-networks.com>

arppc -tv libPPCEC603gnuvx.a                                will list all .o
files in library
arppc -tv libPPCEC603gnuvx.a   file_name.o            will list file_name
arppc -x libPPCEC603gnuvx.a  file_name.o              will extract
file_name.o
arppc -d lib libPPCEC603gnuvx.a  file_name.o         will delete file
arppc -r lib libPPCEC603gnuvx.a  file_name.o          will add/replace file

"echo" <echoecho111@yahoo.com.cn> wrote in message
news:arsq06$a44$1@bt02e2.god.bel.alcatel.be...
> Hi all,
>
> Do you know how to use 'arppc' command to extract *.o from
libPPC860gnuvx.a?
>
> I know we may list the content of libPPC860gnuvx.a using 'arppc -tv', and
> delete the *.o using 'arppc -dv', add the *.o using 'arppc -cru'.
>
> Thanks for your help!
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Download Procedure
Date: 25 Nov 2002 05:59:53 -0800
From: harry2405@rediffmail.com (Harry)
Organization: http://groups.google.com/
Message-ID: <8e6507b.0211250559.662910dc@posting.google.com>
References: <d6e2de0a.0211220343.5f0d758@posting.google.com>

Hi 
The Realtek family of cards follow the NE2000 standard. So, you need
to
#define INCLUDE_ENE in config.h. This is already defined for you.

Also, your boot line is wrong. It shows "fd" (which means floppy) and
you are trying to get vxWorks from floppy, then FTP from 'c:' on your
host. This is whole lot confusing for the target and VxWorks just
hangs. Change fd=0,0(0,0) to ene(0,0). Add password (FTP pw) also to
the boot line. Your boot line should look something like this:

"ene(0,0)host:c/tornado/target/config/pc486/vxWorks
 h=131.200.2.244 e=131.200.2.105 u=target pw=target"

Then 'make' the following:
1.vxWorks, **not** vxWorks.st right now.
2.bootrom_uncmp, 
3.mkboot a: bootrom_uncmp

and reboot the target with the floppy (as you have done already).
If you can see "Attaching network interface ... done", be happy... you
have almost booted the target.

Now your target **DOESN'T** boot completely, because, you have not
configured the I/O and IRQ of the target network card. You get an
error 0xfd0003. Catch hold of your admin and get the correct I/O and
IRQ of the card with the correct driver floppy.

Edit the config.h file for correct IO_ADRS_ENE and INT_LVL_ENE. Then
build all images and make boot floppy and boot the target. This boots
the target.

Good luck..!!

Harry.

vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211220343.5f0d758@posting.google.com>...
> Dear Friends,
> 
> I am working on Vxworks 5.4 and Tornado II. I am a newbie and don't
> know how to download the bootable image to target from host using FTP.
> I did what I was told by my friend and it is as follows:
> 
> 1. Configure the Vxworks using the tornado and Include and Exclude the
> components according to application requirements.
> 
> 2. I don't know which Ethernet Driver type to include (ELT or ENT or
> any other). I am using Realtek processor based Ethernet Card. Please
> let me know which Ethernet Drivers should I use.
> 
> 3. What parameter should I specify DEFAULT_BOOT_LINE for hardware
> components properties.
> I am specifying the following
> 
> "fd=0,0(0,0)host:c/tornado/target/config/pc486/vxWorks.st
> h=131.200.2.244 e=131.200.2.105 u=target"
> 
> 4. I am making a bootrom_uncmp image and then copying it to Floppy
> Disk using mkboot a:bootrom_uncmp.
> 
> 5. Then I am trying to boot my target using the floppy.
> 
> 6. I am making a Vxworks.st standalone image.
> 
> 7. I am starting the FTP server by giving the username and password
> and also the home directory in which my image is stored.
> 
> 8. I am executing the image in the target using the @ command after
> changing any parameters using c and P commands.
> 
> 9. Target gets started with saying Loading and suddenly some numbers
> are displayed and it hangs. Even it is not getting connected to the
> FTP server in the Host.
> 
> Please let me know where I have gone wrong and whether the above
> procedure is correct. Also let me know whether there is another way of
> downloading and its procedure which will help me a lot .
> 
> 
> Thanks in advance.
> 
> with regards,
> 
> Rajneesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for target X86
Date: 25 Nov 2002 06:12:42 -0800
From: harry2405@rediffmail.com (Harry)
Organization: http://groups.google.com/
Message-ID: <8e6507b.0211250612.5e411707@posting.google.com>
References: <4f7acce6.0211211830.42cf160c@posting.google.com>

Hi Mahesh,
Try using a clean and new floppy. This should do the trick. I had this
problem earlier and it worked for me. Also, check if your bootrom
image is 'contiguous'. Boot image can't boot if the file bootrom.sys
is non-contiguous on the floppy.

You may not be able to see what's happening when the boot program is
loading. However, you can do the same when vxWorks is booting. You
need to configure your WDB agent as 'extern'. Refer the VxWorks bible:
VxWorks Programmers' guide, for that !

Also, you needn't include FTP or FTP server. Include this if you want
the target to act as a FTP server. You may also leave it like that.
I hope its clear.

Harry.

v_mahesh@hotmail.com (Mahesh) wrote in message news:<4f7acce6.0211211830.42cf160c@posting.google.com>...
> Hi:
> 
> My name is Mahesh, Iam working on creating and Configuring VxWorks
> Kernel for target Intel X86 and for windows host.
> I have created a Bootrom Image for Network configuration and When i
> try to boot the kernel through the floppy disk, the screen becomes
> blank and it automatically reboots.
> 
> I will be happy if somebody can provide me some information. Also, is
> there any way to debug and see what is going on underneath the hood.
> 
> The configuration and software versions are as follows:
> VxWorks - 5.5
> Tornado - 2.2
> CPU - PENTIUM
> C++Compiler - g++pentium (version - 2.93)
> Host - Windows 2000.
> Ethernet Driver - fei82557End Intel Ethernet Driver.
> 
> The config.h is configured using these macros
> INCLUDE_NETWORK
> INCLUDE_END,
> INCLUDE_FEI_END,
> INCLUDE_FTP,
> INCLUDE_FTP_SERVER.
> 
> thanks
> Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: start address intel386
Date: Mon, 25 Nov 2002 16:56:43 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$f8056h$rd4$1@lnews.actcom.co.il>
References: <artbb4$ddn$1@overload.lbl.gov>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

What are you trying to do?

x86 architecture atargets typically have BIOS which takes
control from the HW reset and the VxWorks for x86 uses the BIOS
for differetn boot shcemes.

Are you trying to make a BIOS-less x86 BSP ?

If so, I had done one like that several years ago it was an i486 CPU at the
time,
which worked without a fan or a heat sink on it.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

<sailinder.harpal@philips.com> wrote in message
news:artbb4$ddn$1@overload.lbl.gov...
> Hi all,
>
> This question is for the Intel 386 experts.
>
> When I generate a Motorola 'S' Format file with Tornado 2.0. The output
contains an address range from ROM_BASE_ADRS up to 234KB, why I don't know.
> My ROM_SIZE is 512KB big. Why doesn't it shows the whole address range.
>
> I know the Intel Program Counter starts from the Highest address. I'm
wandering if it is possible to give an options to the VxWorks compiler or
linker, that the PC jump from the Highest address to the our ROM_TEXT_ADRS
(in our case 0x03F80000).
> Can anyone help me?
>
> Thanks in advance.
>
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
Date: 25 Nov 2002 07:34:58 -0700
From: taashlo@sandia.gov
Organization: Sandia National Laboratories, Albuquerque, NM USA
Message-ID: <of8dg1kd.fsf@sandia.gov>
Sender: taashlo@TYPHOON

(Posted this last week, but I never saw it nor any replies. -Tad)

Hi VxWorkers,

With Tornado 2.0 (VxWorks 5.4), I had a configuration for a
standalone build that included not only the target shell, but
the Tornado (host) shell also.  With this configuration, I
could boot into the target shell and at some later time plug
in an ethernet cable and connect using the Tornado shell.
(When the target shell boots up I see "WDB: Ready" in the
banner and "tWdbTask" in the task list.)

I have since upgraded to Tornado 2.1 (VxWorks 5.4.2) and a
new BSP version.  I didn't change any of the config.h options
that I thought would relate to having both shells active, but
the new version only has the target shell.  (When the target
shell boots up I *don't* see "WDB: Ready" in the banner and
"tWdbTask" is *not* in the task list.)

Does anybody know the right way to configure VxWorks to have
both shells active?

Thanks,

Tad

---------------------------

Newsgroups: comp.os.vxworks
Subject: Need help with fromelf
Date: 25 Nov 2002 07:52:28 -0800
From: adwait@iit.edu (Adwait Sathe)
Organization: http://groups.google.com/
Message-ID: <83f4b1f4.0211250752.52b30cae@posting.google.com>

We are trying to selectively strip debug/line/srcinfo records from our
image to reduce image size. Debug format is DWARF 1 and we use DIAB
compiler.

fromelf -d xxx.sys gives me follwing error messages.

romelf: warning: partially resolved forward reference for sym
dyn_ltree
fromelf: warning: partially resolved forward reference for sym
dyn_dtree
fromelf: warning: partially resolved forward reference for sym bl_tree
fromelf: warning: partially resolved forward reference for sym
static_ltree
fromelf: warning: partially resolved forward reference for sym
static_dtree
fromelf: warning: partially resolved forward reference for sym u
fromelf: warning: partially resolved forward reference for sym
fixed_tl
fromelf: warning: partially resolved forward reference for sym fixed_t

Does anyone know what this is?

Regards,
Adwait

---------------------------

Newsgroups: comp.os.vxworks
Subject: Telnet & Console
Date: 25 Nov 2002 09:07:23 -0800
From: vkinger@hotmail.com (Kinger)
Organization: http://groups.google.com/
Message-ID: <f57b3351.0211250907.7531668f@posting.google.com>

Hi all,
The problem I am facing is that I want my "admin" user to see MY OWN
application(Menu driven console)when he connects through telnet.
Moreover, stdin, stdout and stderr should always be "connected" with
my application instead of the shell. The user "admin" doesn't need to
be aware of the shell existence.
The shell has to be running just to support telnet and rlogin
connection but "hidden".
However, I am facing the problem, in order to run telnet, I have to
enable the shell but after establishing the telnet connection I get
the shell prompt. How can I "show" my application instead of the
shell.

Thanks,
Kinger.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for X86
Date: 25 Nov 2002 09:30:34 -0800
From: pj1206@yahoo.com (Paul R)
Organization: http://groups.google.com/
Message-ID: <536dfe34.0211250930.2e4f0d10@posting.google.com>
References: <20021121203910.05840.00005962@mb-ms.aol.com> <488e459a.0211221300.549ea28b@posting.google.com> <4f7acce6.0211242056.750e9b6a@posting.google.com>

Mahesh
We had the identical problem here... although the cause might not be
the same
here's its worth looking at:
It turned out that the software key that we received from WRS was
wrong and didn't unlock the pentium software... you can check this by
making sure that in your target\config directory you have a
subdirectory like  pcpentium,or pcpentiumpro , not just the
template_x86 directory....
WRS sent us a new software key and all became well...
Give it a shot,
Paul R
Nomadix

v_mahesh@hotmail.com (Mahesh) wrote in message news:<4f7acce6.0211242056.750e9b6a@posting.google.com>...
> Hi john:
> 
> I have changed the default setting for Vga console to PC Console and
> created a bootrom floppy. If i boot the kernel with that floppy i
> still get the see the same problem. I feel something might be wrong
> with my configuration.
> 
> Please bear with my lack of experience. Iam attaching the config.h and
> configNet.h for your reference....anything seem blatantly wrong? I
> will be happy if you can have a look at it and letme know if iam
> missing something.
> 
> thanks
> Mahesh
> 
> /*************************** CONFIG.H
> ***************************************/
> /* config.h - template configuration header file */
> 
> /* Copyright 1984-2002 Wind River Systems, Inc. */
> 
> /*
> TODO -	Remove the template modification history and begin a new
> history
> 	starting with version 01a and growing the history upward with
> 	each revision.
> 
> modification history
> --------------------
> 01y,18apr02,rhe  Added C++ Protection
> 01x,20dec01,cjj  Changed RAM_HIGH_ADRS to 0x200000
> 01w,09dec01,dat  Adding USB support for ARM, MIPS, PPC, PENTIUM, SH,
> added
> 		 optional TFFS support for all.
> 01v,15dec00,pai  Simplified the network configuration macros used in
> this file.
>                  References to INCLUDE_BSD, INCLUDE_DEFER_NET_INIT,
> and
>                  INCLUDE_NET_INIT have been removed.  This template
> config.h
>                  now specifies INCLUDE_NETWORK and INCLUDE_END.  The
> remaining
>                  network configuration comes from configAll.h.
> 01u,11dec00,pai  made END driver support the default for new WRN code.
> 01t,11dec00,pai  introduced INCLUDE_DEFER_NET_INIT configuration
> constant for
>                  new WRN code.
> 01s,08apr99,dat  SPR 26491, fixed PCI macro names
> 01r,29mar99,dat  SPR 26125, added INCLUDE_BSD
> 01q,02feb99,tm   added PCI AutoConfig support to template BSPs (SPR
> 24733)
> 01p,28sep98,dat  added default PCI and VME macros
> 01o,07nov98,dat  added note about the values for ROM_TEXT_ADRS, and
> 		 ROM_WARM_ADRS
> 01n,21jul98,db   defined INCLUDE_NETWORK, changed ROM_SIZE to 0x40000.
> 01m,07jul98,db   changed BSP_VERSION to "1.2" and BSP_REVISION to
> "/0".
> 		 added BSP_VER_1_2 macro, defined INCLUDE_END, removed
> 		 END_OVERRIDE(Tornado 2.0 release).
> 01l,25aug97,dat  code review comments from Kitty
> 01k,07jul97,dat  added supported for new END ethernet drivers
> 01j,23apr97,dat  added ROM_WARM_ADRS, INCLUDE_CDROMFS
> 01i,02apr97,dat  more documentation about VME and other macros.
> 01h,12mar97,dat  added VME mapping macros
> 01g,10mar97,dat  comments from reviewers
> 01f,28feb97,dat  added INCLUDE_USER_APPL, USER_APPL_INIT
> 01e,05feb97,dat  incorporated comments from Thierry P.
> 01d,23jan97,dat  moved timer constants to template.h
> 01c,17jan97,dat  added INCLUDE_SERIAL, INCLUDE_MMU, INCLUDE_VME
> 01b,16jan97,dat  added LOCAL_MEM_AUTOSIZE and moved INCLUDE_SCSI2
> outside
> 		 of #if FALSE.
> 01a,22oct96,ms   derived from the mv147 BSP
> */
> 
> /*
> This file contains the configuration parameters for the template BSP.
> This template starts simple - with most facilities excluded by
> default.
> 
> TODO -
> Present the user with simple straight forward options.  Do not ask the
> user to encode values together to form a value to be loaded in a
> register.
> Let the source code, or the pre-processor, do the computational work
> to
> determine what value to load in a particular register.
> */
> 
> #ifndef	INCconfigh
> #define	INCconfigh
> 
> #ifdef __cplusplus
> extern "C" {
> #endif
> 
> /* BSP version/revision identification, before configAll.h */
> 
> #define BSP_VER_1_1	1	/* 1.2 is backward compatible with 1.1 */
> #define BSP_VER_1_2	1
> #define BSP_VERSION	"1.2"
> #define BSP_REV		"/0"	/* 0 for first revision */
> 
> #include "configAll.h"		/* Set the VxWorks default configuration */
> #include "pc.h"
> 
> #define DEFAULT_BOOT_LINE \
> 	"fei(0,0)/distcomp/wind/target/config/pcPentium2_2/vxWorks " \
> 	"h=132.200.200.13 e=132.200.200.84 u=taoadmin pw=tao+oci tn=vx86"
> 
> /* TODO - values in this header file are dummy values, update as
> needed */
> 
> /* memory configuration */
> 
> #define LOCAL_MEM_LOCAL_ADRS	0		/* fixed at zero */
> #undef	LOCAL_MEM_AUTOSIZE			/* run-time memory sizing */
> #define LOCAL_MEM_SIZE		0x400000	/* 4M memory */
> #define	USER_RESERVED_MEM	0		/* see sysMemTop() */
> 
> /*
>  * The constants ROM_TEXT_ADRS, ROM_SIZE, RAM_HIGH_ADRS, and
> RAM_LOW_ADRS
>  * are defined in config.h and Makefile.
>  * All definitions for these constants must be identical.
>  *
>  * TODO - Make sure these values match those in your Makefile.  The
> values
>  * shown below are the defaults for a 68000 series system.  Pay
> particular
>  * attention to ROM_TEXT_ADRS and ROM_WARM_ADRS.  The correct default
> values
>  * are in the Makefile for each template BSP.
>  */
> 
> #define ROM_BASE_ADRS		0xff800000	/* base address of ROM */
> #define ROM_TEXT_ADRS		(ROM_BASE_ADRS+8) /* with PC & SP */
> #define ROM_WARM_ADRS		(ROM_TEXT_ADRS+8) /* warm reboot entry */
> #define ROM_SIZE		0x00040000	/* 256KB ROM space */
> #define RAM_HIGH_ADRS		0x00200000	/* RAM address for bootrom */
> #define RAM_LOW_ADRS		0x00010000	/* RAM address for vxWorks */
> 
> /* Serial port configuration */
> 
> /* Commented for Now */
> /* #define	INCLUDE_SERIAL */
> #define INCLUDE_PC_CONSOLE
> 
> #ifdef  INCLUDE_PC_CONSOLE
> #define PC_CONSOLE              0
> #undef  N_VIRTUAL_CONSOLES
> #define N_VIRTUAL_CONSOLES      2
> 
> #define KBD_INT_VEC             (INT_VEC_GET (KBD_INT_LVL))
> 
> #endif
> #undef	NUM_TTY
> #define	NUM_TTY			(N_UART_CHANNELS)	 /* defined in template.h */
> 
> #define PC_KBD_TYPE             PC_PS2_101_KBD
> 
> /* Timer configuration */
> 
> #undef  INCLUDE_TIMESTAMP		/* no timestamp driver support */
> 
> /*
>  * Cache configuration
>  *
>  * TODO -
>  * All cache is turned off to begin with. Activate caching after basic
>  * BSP functionality is achieved.  Start with instruction caching,
> followed
>  * by data caching.  Begin without snooping options; and turn those on
>  * later if the board supports it.
>  *
>  * Note that when MMU is enabled, cache modes are controlled by
>  * the MMU table entries in sysPhysMemDesc[], not the cache mode
>  * macros defined here.
>  */
> 
> #undef	INCLUDE_CACHE_SUPPORT	/* no cacheLib support */
> #undef	USER_I_CACHE_ENABLE
> #undef	USER_I_CACHE_MODE
> #define	USER_I_CACHE_MODE	CACHE_DISABLED
> #undef	USER_D_CACHE_ENABLE
> #undef	USER_D_CACHE_MODE
> #define	USER_D_CACHE_MODE	CACHE_DISABLED
> #undef	USER_B_CACHE_ENABLE
> 
> /* MMU configuration */
> 
> #undef	INCLUDE_MMU_BASIC	/* no MMU support */
> #undef	INCLUDE_MMU_FULL	/* no MMU support */
> 
> /* Network driver configuration */
> 
> #define	INCLUDE_NETWORK
> #define	INCLUDE_END		/* Enhanced Network Driver (see configNet.h) */
> 
> #undef	INCLUDE_EX
> #undef	INCLUDE_ENP
> #undef	INCLUDE_SM_NET
> 
> /* VME configuration */
> 
> /*
>  * TODO -
>  * Only those options that are actually user changeable should be
> defined
>  * here.  Options that cannot be changed should be moved to
> template.h.
>  */
> 
> #undef	INCLUDE_VME
> 
> /* A16 master window maps all of A16 to 0xff800000 locally */
> 
> #define	VME_A16_MSTR_BUS	0x0
> #define	VME_A16_MSTR_SIZE	0x00010000
> #define	VME_A16_MSTR_LOCAL	0xff800000
> 
> /* A24 master window maps all of A24 to 0xf8000000 locally */
> 
> #define	VME_A24_MSTR_BUS	0x0
> #define	VME_A24_MSTR_SIZE	0x01000000
> #define	VME_A24_MSTR_LOCAL	0xf8000000
> 
> /* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
> local. */
> 
> #define	VME_A32_MSTR_BUS	(0x80000000)
> #define	VME_A32_MSTR_SIZE	(0x02000000)
> #define	VME_A32_MSTR_LOCAL	(0x80000000)
> 
> /* A16 slave window is not supported */
> 
> #define	VME_A16_SLV_LOCAL	0x0
> #define	VME_A16_SLV_BUS		0x0
> #define	VME_A16_SLV_SIZE	0x0
> 
> /* A24 slave window maps 1st 8MB of local memory to bus address
> 0x00800000 */
> 
> #define	VME_A24_SLV_LOCAL	LOCAL_MEM_LOCAL_ADRS
> #define	VME_A24_SLV_BUS		0x00800000
> #define	VME_A24_SLV_SIZE	0x00800000
> 
> /* A32 slave window maps all local memory to bus address 0x80000000 */
> 
> #define	VME_A32_SLV_LOCAL	(LOCAL_MEM_LOCAL_ADRS)
> #define	VME_A32_SLV_BUS		0x80000000
> #define	VME_A32_SLV_SIZE	((UINT)sysPhysMemTop() -
> LOCAL_MEM_LOCAL_ADRS)
> 
> /* PCI configuration */
> 
> #undef	INCLUDE_PCI
> #undef  INCLUDE_PCI_AUTOCONF
> 
> #ifndef PCI_CFG_TYPE
> #   ifdef INCLUDE_PCI_AUTOCONF
> #      define PCI_CFG_TYPE PCI_CFG_AUTO
> #   else
> #      define PCI_CFG_TYPE PCI_CFG_FORCE
> #   endif /* INCLUDE_PCI_AUTOCONF */
> #endif /* PCI_CFG_TYPE */
>  
> 
> /*
>  * TODO -
>  * Only those options that are actually user changeable should be
> defined
>  * here.  Options that cannot be changed should be moved to
> template.h.
>  */
> 
> /* PCI I/O master window */
> 
> #define	PCI_MSTR_IO_LOCAL	0xff800000
> #define	PCI_MSTR_IO_BUS		0x0
> #define	PCI_MSTR_IO_SIZE	0x00010000
> 
> /* PCI MEMIO master (non-prefetch memory) window */
> 
> #define	PCI_MSTR_MEMIO_LOCAL	0xf8000000
> #define	PCI_MSTR_MEMIO_BUS	0x0
> #define	PCI_MSTR_MEMIO_SIZE	0x01000000
> 
> /* PCI MEM master (prefetchable memory) window */
> 
> #define	PCI_MSTR_MEM_LOCAL	0xfa000000
> #define	PCI_MSTR_MEM_BUS	0x0
> #define	PCI_MSTR_MEM_SIZE	0x01000000
> 
> /* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
> local. */
> 
> #define	VME_A32_MSTR_BUS	(0x80000000)
> #define	VME_A32_MSTR_SIZE	(0x02000000)
> #define	VME_A32_MSTR_LOCAL	(0x80000000)
> 
> /* A16 slave window is not supported */
> 
> #define	VME_A16_SLV_LOCAL	0x0
> #define	VME_A16_SLV_BUS		0x0
> #define	VME_A16_SLV_SIZE	0x0
> 
> /* A24 slave window maps 1st 8MB of local memory to bus address
> 0x00800000 */
> 
> #define	VME_A24_SLV_LOCAL	LOCAL_MEM_LOCAL_ADRS
> #define	VME_A24_SLV_BUS		0x00800000
> #define	VME_A24_SLV_SIZE	0x00800000
> 
> /* A32 slave window maps all local memory to bus address 0x80000000 */
> 
> #define	VME_A32_SLV_LOCAL	(LOCAL_MEM_LOCAL_ADRS)
> #define	VME_A32_SLV_BUS		0x80000000
> #define	VME_A32_SLV_SIZE	((UINT)sysPhysMemTop() -
> LOCAL_MEM_LOCAL_ADRS)
> 
> /* SCSI driver configuration */
> 
> #if	FALSE			/* change FALSE to TRUE for SCSI interface */
> #define	INCLUDE_SCSI		/* include SCSI interface */
> #define	INCLUDE_SCSI_DMA	/* include SCSI DMA interface */
> #define	INCLUDE_SCSI_BOOT	/* include SCSI for boot option */
> #define	INCLUDE_DOSFS		/* DOS file system */
> #undef	INCLUDE_TAPEFS		/* tape file system */
> #undef	INCLUDE_CDROMFS		/* CD-ROM (iso9660) file system */
> #define SYS_SCSI_CONFIG		/* BSP scsi config routine */
> #endif	/* FALSE/TRUE */
> 
> /* Select either SCSI-1 or SCSI-2, independent of INCLUDE_SCSI */
> 
> #define INCLUDE_SCSI2		/* undef for SCSI-1 support */
> 
> /*
>  * User application initialization
>  *
>  * USER_APPL_INIT must be a valid C statement or block.  It is
>  * included in the usrRoot() routine only if INCLUDE_USER_APPL is
>  * defined.  The code for USER_APPL_INIT is only an example.  The
>  * user is expected to change it as needed.  The use of taskSpawn
>  * is recommended over direct execution of the user routine.
>  */
> 
> #undef	INCLUDE_USER_APPL
> #define	USER_APPL_INIT \
> 	{ \
> 	IMPORT int myAppInit(); \
> 	taskSpawn ("myApp", 30, 0, 5120, \
> 		   myAppInit, 0x1, 0x2, 0x3, 0,0,0,0,0,0,0); \
> 	}
> 
> /* Configurable interrupt vectors/levels (static defs go in
> template.h) */
> 
> #if	FALSE
> #define	INT_VEC_ABORT		xxx
> #define	INT_VEC_CLOCK		xxx
> ...
> #define	INT_LVL_ABORT		xxx
> #define	INT_LVL_CLOCK		xxx
> ...
> #endif
> 
> /* Basic USB Support (PPC, PENTIUM, ARM, MIPS, SH only) */
> 
> #if FALSE	/* set TRUE to include USB support */
> 
> /* USB Host Components */
> 
> #   define INCLUDE_USB 			/* Main USB Component */
> #   undef  INCLUDE_USB_INIT		/* USB Initialization */
> #   define INCLUDE_UHCI			/* UHCI Controller Driver */
> #   undef  INCLUDE_UHCI_INIT    	/* UHCI Initialization */
> #   define INCLUDE_OHCI			/* OHCI Controller Driver */
> #   undef  INCLUDE_OHCI_INIT		/* OHCI Initialization */
> #   undef  INCLUDE_OHCI_PCI_INIT 	/* OHCI PCI Initialization */
> #   define INCLUDE_USBTOOL		/* usbTool Application */
> #   undef  INCDLUE_USB_AUDIO_DEMO	/* USB Audio Demo */
> #   define INCLUDE_USB_MOUSE 		/* USB Mouse Driver */
> #   undef  INCLUDE_USB_MOUSE_INIT 	/* Mouse Driver Initialization */
> #   define INCLUDE_USB_KEYBOARD 	/* USB Keyboard Driver */
> #   undef  INCLUDE_USB_KEYBOARD_INIT 	/* Keyboard Driver
> Initialization */
> #   define INCLUDE_USB_PRINTER 		/* USB Printer Driver */
> #   undef  INCLUDE_USB_PRINTER_INIT 	/* Printer Driver Initialization
> */
> #   define INCLUDE_USB_SPEAKER 		/* USB Speaker Driver */
> #   undef  INCLUDE_USB_SPEAKER_INIT 	/* Speaker Driver Initialization
> */
> #   undef  INCLUDE_USB_MS_BULKONLY 	/* USB Bulk Driver */
> #   undef  INCLUDE_USB_MS_BULKONLY_INIT /* Bulk Driver Initialization
> */
> #   undef  INCLUDE_USB_MS_CBI 		/* USB CBI Driver */
> #   undef  INCLUDE_USB_MS_CBI_INIT 	/* CBI Driver Initialization */
> #   undef  INCLUDE_USB_PEGASUS_END 	/* USB Pegasus Network Driver */
> #   undef  INCLUDE_USB_PEGASUS_END_INIT /* Pegaus Driver
> Initialization */
> 
> /*  USB Parameters */
> 
> #   define BULK_DRIVE_NAME "/bd" 		/* Bulk Drive Name */	
> #   define CBI_DRIVE_NAME "/cbid" 		/* CBI Drive Name */
> #   define PEGASUS_IP_ADDRESS "90.0.0.3" 	/* Pegasus IP Address */
> #   define PEGASUS_DESTINATION_ADDRESS "90.0.0.53" /* Destination IP
> Address */
> #   define PEGASUS_NET_MASK 0xffffff00 		/* Pegasus Net Mask */
> #   define PEGASUS_TARGET_NAME "host" 		/* Pegasus Target Name */
> 
> #endif /* End of optional USB support */
> 
> /* Optional TFFS support.  Just define INCLUDE_TFFS to activate */
> 
> #undef	INCLUDE_TFFS
> 
> #include "template.h"		/* Verify user options, specify i/o addr etc */
> 
> #undef INCLUDE_MMU_BASIC      /* bundled mmu support */
> #undef INCLUDE_CACHE_SUPPORT  /* cache support */
> 
> #ifdef __cplusplus
> }
> #endif
> 
> #endif	/* INCconfigh */
> #if defined(PRJ_BUILD)
> #include "prjParams.h"
> #endif
> /******************************************************************************************************/
> 
> /**************************** ConfigNet.h
> ******************************************************/
> /* configNet.h - network configuration header */
> 
> /* Copyright 1984-2002 Wind River Systems, Inc. */
> 
> /*
> TODO -	Remove the template modification history and begin a new
> history
> 	starting with version 01a and growing the history upward with
> 	each revision.
> 
> modification history
> --------------------
> 01e,28may02,dat  exclude driver if NETWORK not defined, 77135
> 01d,18apr02,rhe  Added C++ Protection
> 01c,13dec00,pai  corrected endDevTbl[] definition (SPR #62994) and
> specified
>                  the return type in the END_LOAD_FUNC declaration.
> 01b,21jul98,db   dec21x40End replaced with template END driver. 
> 01a,07jul97,dat  written (from mv2603/configNet.h,ver 01b)
> */
>  
> #ifndef INCnetConfigh
> #define INCnetConfigh
> 
> #ifdef __cplusplus
> extern "C" {
> #endif
> 
> #ifdef INCLUDE_NETWORK /* ignore everything if NETWORK not included */
> 
> #include "vxWorks.h"
> #include "end.h"
> 
> /* This template presumes the template END driver */
> 
> #define FEI82557_LOAD_FUNC	fei82557EndLoad
> #define FEI82557_BUFF_LOAN      1
> 
> /* <devAdrs>:<PCIadrs>:<ivec>:<ilevel>:<memBase>:<memSize>:<userFlags>
> */
> 
> #define	FEI82557_LOAD_STRING	"-1:0x00:0x20:0x20:0x00"
> 
> IMPORT END_OBJ * FEI82557_LOAD_FUNC ();
> 
> END_TBL_ENTRY endDevTbl [] =
>     {
>     { 0, FEI82557_LOAD_FUNC, FEI82557_LOAD_STRING, FEI82557_BUFF_LOAN,
> NULL, FALSE},
>     { 0, END_TBL_END, NULL, 0, NULL},
>     };
> 
> #ifdef __cplusplus
> }
> #endif
> 
> #endif /* INCLUDE_NETWORK */
> #endif /* INCnetConfigh */
> 
> 
> 
> 
> 
> 
> john_94501@yahoo.com (John) wrote in message news:<488e459a.0211221300.549ea28b@posting.google.com>...
> > Hello,
> > 
> > > My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
> > > target Intel X86 and for windows host.
> > > I have created a Bootrom Image for Network configuration and When i try to boot
> > > the kernel through the floppy disk, the screen becomes blank and it
> > > automatically reboots. 
> > 
> > You need to change the console settings. In the newer versions of
> > VxWorks, including AE 1.x and 5.5, the default setting for the console
> > is the serial port (COM1 using DOS style naming, /tyCo/0 in VxWorks).
> > 
> > You can switch back to the VGA console if you need to (search the
> > archives for this group - it has been covered before), or you can
> > simply connect a terminal (or PC running HyperTerminal) to the serial
> > port and use that.
> > 
> > HTH,
> > 
> > John...
> >  
> > > I will be happy if somebody can shed some on it. Also, is there any way to
> > > debug and see what is going on underneath the hood.  
> > > 
> > > The configuration and software versions are as follows:
> > > VxWorks - 5.5
> > > Tornado - 2.2
> > > CPU - PENTIUM
> > > C++Compiler - g++pentium (version - 2.93)
> > > Host - Windows 2000.
> > > Ethernet Driver - fei82557End Intel Ethernet Driver.
> > > 
> > > The config.h is configured using these macros
> > > INCLUDE_NETWORK
> > > INCLUDE_END,
> > > INCLUDE_FEI_END,
> > > INCLUDE_FTP,
> > > INCLUDE_FTP_SERVER.
> > > 
> > > thanks
> > > Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
Date: Mon, 25 Nov 2002 22:08:44 +0000 (UTC)
From: Johan Borkhuis <JBorkhuis@proxim.com>
Organization: Proxim Corp.
Message-ID: <Xns92D1EACF570C7jborkhuisproximcom@192.19.193.66>
References: <of8dg1kd.fsf@sandia.gov>

taashlo@sandia.gov wrote:

> I have since upgraded to Tornado 2.1 (VxWorks 5.4.2) and a
> new BSP version.  I didn't change any of the config.h options
> that I thought would relate to having both shells active, but
> the new version only has the target shell.  (When the target
> shell boots up I *don't* see "WDB: Ready" in the banner and
> "tWdbTask" is *not* in the task list.)

You have to include WDB in your build. After you include this you will see 
the WDB ready prompt again.

Kind regards,
        Johan

- -- 
        o o o o o o o . . .   _____________________________
       o      _____           ||    Johan Borkhuis        |
     .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
    >(________|__|_[_________]_|__________________________|
    _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
=== VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Telnet & Console
Date: Mon, 25 Nov 2002 22:10:36 +0000 (UTC)
From: Johan Borkhuis <JBorkhuis@proxim.com>
Organization: Proxim Corp.
Message-ID: <Xns92D1EB2097B63jborkhuisproximcom@192.19.193.66>
References: <f57b3351.0211250907.7531668f@posting.google.com>

vkinger@hotmail.com (Kinger) wrote:

> Hi all,
> The problem I am facing is that I want my "admin" user to see MY OWN
> application(Menu driven console)when he connects through telnet.
> Moreover, stdin, stdout and stderr should always be "connected" with
> my application instead of the shell. The user "admin" doesn't need to
> be aware of the shell existence.
> The shell has to be running just to support telnet and rlogin
> connection but "hidden".
> However, I am facing the problem, in order to run telnet, I have to
> enable the shell but after establishing the telnet connection I get
> the shell prompt. How can I "show" my application instead of the
> shell.

There is another Telnet server (that also support multiple logins). You 
can reqest it from your FAE. It is supplied in source. You can write you 
own application to support this server.

Kind regards,
        Johan

- -- 
        o o o o o o o . . .   _____________________________
       o      _____           ||    Johan Borkhuis        |
     .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
    >(________|__|_[_________]_|__________________________|
    _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
=== VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===

---------------------------

Newsgroups: comp.os.vxworks
Subject: trashed vtable
Date: Tue, 26 Nov 2002 03:38:54 GMT
From: Barry Gold <BDGold@attbi.com>
Organization: AT&T Broadband
Message-ID: <3DE2EB1B.B9335D52@attbi.com>

I'm trying to port a C++ application to VxWorks.  Things seem to go
along smoothly until the first time I try to delete an object.  Then
control ends up somewhere random as if the vtable had been trashed.  The
same application gets much further under Visual C++ - it still dies but
much later, and in a more explicable way.

The target machine is an RIOC board (Power PC processor).

Has anybody else run into similar problems?

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: WindRiver Tornado problem: ftp server with wu-ftpd in Linux
Date: Tue, 26 Nov 2002 03:52:22 GMT
From: "2002 pacbell" <no_spam_email@nospam.org>
Organization: Prodigy Internet http://www.prodigy.com
Message-ID: <WdCE9.4661$QL4.215360797@newssvr14.news.prodigy.com>
References: <3DB8D84A.70601@ms3.senao.com.tw>

The problem is that the vxWorks ftp client prior to Tornado 2.2 did not
support PASSIVE mode.
This was a known problem and has been corrected.
Tornado 2.2 corrects this issue.  Upgrade to Tornado 2.2 and your problem
will go away.

Regards,
   Eric

---------------------------

Newsgroups: comp.os.vxworks
Subject: ads860 cpm network working fine with crossover cable but not with the network.
Date: 25 Nov 2002 20:18:00 -0800
From: challa23@yahoo.com (Murali Challa)
Organization: http://groups.google.com/
Message-ID: <c1e650d9.0211252018.5cd5ce06@posting.google.com>

Hi!!

Motorola FADS860 target is successfully booted using Ethernet Cross
over cable between Host and Target.
If i do the same thing with our network..It is giving 0xd003 error.
Is it problem with our HUB(DLINK)????.
Kindly suggest me how to make my VxWorks Target be a network host.

THANKX
murali

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Telnet & Console
Date: Tue, 26 Nov 2002 04:39:41 GMT
From: "2002 pacbell" <no_spam_email@nospam.org>
Organization: Prodigy Internet http://www.prodigy.com
Message-ID: <hWCE9.4670$9b5.217047349@newssvr14.news.prodigy.com>
References: <f57b3351.0211250907.7531668f@posting.google.com>

Tornado 2.2 contains a re-written telnet server that should help you solve
the problem.

There is a sample piece of code you can use as a template for writting your
own telnet application.
In order to use it,  select the 'unsupported code' option when you install
tornado 2.2.
 The module will be in:     [wind_base]/target/unsupported/telnet/*

The new telnet library supports multiple users and does not need the shell
at all (prior versions needed it).

Regards,
   Eric

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for target X86
Date: 25 Nov 2002 21:12:08 -0800
From: be_gyus@yahoo.com (james)
Organization: http://groups.google.com/
Message-ID: <ff42611f.0211252112.47a8f1a1@posting.google.com>
References: <4f7acce6.0211211832.1ab3277e@posting.google.com> <ff42611f.0211250149.4d41360a@posting.google.com> <4f7acce6.0211251525.5d403f14@posting.google.com>

Mahesh,

I see some fei stuff undefined check out is this the card you are
using... Also once u build your bootrom dont forget to build the
vxWorks i.e. make vxWorks...I think ur vxWorks image has not been
built..
If you still face the problem try doing a clean and build afresh..

v_mahesh@hotmail.com (Mahesh) wrote in message news:<4f7acce6.0211251525.5d403f14@posting.google.com>...
> HI james: 
> 
> thanks for the reply. Please bear with my lack of experience. Iam
> attaching the config.h and  configNet.h for your reference....anything
> seem blatantly wrong? I
> will be happy if you can have a look at it and letme know if iam 
> missing something. 
> 
> As you have suggested i configured and build the kernel by including
> INCLUDE_PC_CONSOLE but some reason it didn't work. I guess something
> might be wrong with my configuration.
> 
> thanks for the info. 
> 
> /************************* CONFIG.H
> *****************************************/
> 
> /* config.h - template configuration header file */
> 
> /* Copyright 1984-2002 Wind River Systems, Inc. */
> 
> /*
> TODO -  Remove the template modification history and begin a new
> history
>         starting with version 01a and growing the history upward with
>         each revision.
> 
> modification history
> --------------------
> 01y,18apr02,rhe  Added C++ Protection
> 01x,20dec01,cjj  Changed RAM_HIGH_ADRS to 0x200000
> 01w,09dec01,dat  Adding USB support for ARM, MIPS, PPC, PENTIUM, SH,
> added
>                  optional TFFS support for all.
> 01v,15dec00,pai  Simplified the network configuration macros used in
> this file.
>                  References to INCLUDE_BSD, INCLUDE_DEFER_NET_INIT,
> and
>                  INCLUDE_NET_INIT have been removed.  This template
> config.h
>                  now specifies INCLUDE_NETWORK and INCLUDE_END.  The
> remaining
>                  network configuration comes from configAll.h.
> 01u,11dec00,pai  made END driver support the default for new WRN code.
> 01t,11dec00,pai  introduced INCLUDE_DEFER_NET_INIT configuration
> constant for
>                  new WRN code.
> 01s,08apr99,dat  SPR 26491, fixed PCI macro names
> 01r,29mar99,dat  SPR 26125, added INCLUDE_BSD
> 01q,02feb99,tm   added PCI AutoConfig support to template BSPs (SPR
> 24733)
> 01p,28sep98,dat  added default PCI and VME macros
> 01o,07nov98,dat  added note about the values for ROM_TEXT_ADRS, and
>                  ROM_WARM_ADRS
> 01n,21jul98,db   defined INCLUDE_NETWORK, changed ROM_SIZE to 0x40000.
> 01m,07jul98,db   changed BSP_VERSION to "1.2" and BSP_REVISION to
> "/0".
>                  added BSP_VER_1_2 macro, defined INCLUDE_END, removed
>                  END_OVERRIDE(Tornado 2.0 release).
> 01l,25aug97,dat  code review comments from Kitty
> 01k,07jul97,dat  added supported for new END ethernet drivers
> 01j,23apr97,dat  added ROM_WARM_ADRS, INCLUDE_CDROMFS
> 01i,02apr97,dat  more documentation about VME and other macros.
> 01h,12mar97,dat  added VME mapping macros
> 01g,10mar97,dat  comments from reviewers
> 01f,28feb97,dat  added INCLUDE_USER_APPL, USER_APPL_INIT
> 01e,05feb97,dat  incorporated comments from Thierry P.
> 01d,23jan97,dat  moved timer constants to template.h
> 01c,17jan97,dat  added INCLUDE_SERIAL, INCLUDE_MMU, INCLUDE_VME
> 01b,16jan97,dat  added LOCAL_MEM_AUTOSIZE and moved INCLUDE_SCSI2
> outside
>                  of #if FALSE.
> 01a,22oct96,ms   derived from the mv147 BSP
> */
> 
> /*
> This file contains the configuration parameters for the template BSP.
> This template starts simple - with most facilities excluded by
> default.
> 
> TODO -
> Present the user with simple straight forward options.  Do not ask the
> user to encode values together to form a value to be loaded in a
> register.
> Let the source code, or the pre-processor, do the computational work
> to
> determine what value to load in a particular register.
> */
> 
> #ifndef INCconfigh
> #define INCconfigh
> 
> #ifdef __cplusplus
> extern "C" {
> #endif
> 
> /* BSP version/revision identification, before configAll.h */
> 
> #define BSP_VER_1_1     1       /* 1.2 is backward compatible with 1.1
> */
> #define BSP_VER_1_2     1
> #define BSP_VERSION     "1.2"
> #define BSP_REV         "/0"    /* 0 for first revision */
> 
> #include "configAll.h"          /* Set the VxWorks default
> configuration */
> #include "pc.h"
> 
> #define DEFAULT_BOOT_LINE \
>         "fei(0,0)/distcomp/wind/target/config/pcPentium2_2/vxWorks " \
>         "h=132.200.200.13 e=132.200.200.84 u=admin pw=admin_1 tn=vx86"
> 
> /* TODO - values in this header file are dummy values, update as
> needed */
> 
> /* memory configuration */
> 
> #define LOCAL_MEM_LOCAL_ADRS    0               /* fixed at zero */
> #undef  LOCAL_MEM_AUTOSIZE                      /* run-time memory
> sizing */
> #define LOCAL_MEM_SIZE          0x400000        /* 4M memory */
> #define USER_RESERVED_MEM       0               /* see sysMemTop() */
> 
> /*
>  * The constants ROM_TEXT_ADRS, ROM_SIZE, RAM_HIGH_ADRS, and
> RAM_LOW_ADRS
>  * are defined in config.h and Makefile.
>  * All definitions for these constants must be identical.
>  *
>  * TODO - Make sure these values match those in your Makefile.  The
> values
>  * shown below are the defaults for a 68000 series system.  Pay
> particular
>  * attention to ROM_TEXT_ADRS and ROM_WARM_ADRS.  The correct default
> values
>  * are in the Makefile for each template BSP.
>  */
> 
> #define ROM_BASE_ADRS           0xff800000      /* base address of ROM
> */
> #define ROM_TEXT_ADRS           (ROM_BASE_ADRS+8) /* with PC & SP */
> #define ROM_WARM_ADRS           (ROM_TEXT_ADRS+8) /* warm reboot entry
> */
> #define ROM_SIZE                0x00040000      /* 256KB ROM space */
> #define RAM_HIGH_ADRS           0x00200000      /* RAM address for
> bootrom */
> #define RAM_LOW_ADRS            0x00010000      /* RAM address for
> vxWorks */
> 
> /* Serial port configuration */
> 
> /* Commented for Now */
> /* #define      INCLUDE_SERIAL */
> #if     TRUE
> #define INCLUDE_PC_CONSOLE
> #endif  /* TRUE/FALSE */
> 
> #ifdef  INCLUDE_PC_CONSOLE
> #define PC_CONSOLE              0
> #undef  N_VIRTUAL_CONSOLES
> #define N_VIRTUAL_CONSOLES      2
> 
> #define KBD_INT_VEC             (INT_VEC_GET (KBD_INT_LVL))
> 
> #endif
> #undef  NUM_TTY
> #define NUM_TTY                 (N_UART_CHANNELS)        /* defined in
> template.h */
> 
> #define PC_KBD_TYPE             PC_PS2_101_KBD
> 
> /* Timer configuration */
> 
> #undef  INCLUDE_TIMESTAMP               /* no timestamp driver support
> */
> 
> /*
>  * Cache configuration
>  *
>  * TODO -
>  * All cache is turned off to begin with. Activate caching after basic
>  * BSP functionality is achieved.  Start with instruction caching,
> followed
>  * by data caching.  Begin without snooping options; and turn those on
>  * later if the board supports it.
>  *
>  * Note that when MMU is enabled, cache modes are controlled by
>  * the MMU table entries in sysPhysMemDesc[], not the cache mode
>  * macros defined here.
>  */
> 
> #undef  INCLUDE_CACHE_SUPPORT   /* no cacheLib support */
> #undef  USER_I_CACHE_ENABLE
> #undef  USER_I_CACHE_MODE
> #define USER_I_CACHE_MODE       CACHE_DISABLED
> #undef  USER_D_CACHE_ENABLE
> #undef  USER_D_CACHE_MODE
> #define USER_D_CACHE_MODE       CACHE_DISABLED
> #undef  USER_B_CACHE_ENABLE
> 
> /* MMU configuration */
> 
> #undef  INCLUDE_MMU_BASIC       /* no MMU support */
> #undef  INCLUDE_MMU_FULL        /* no MMU support */
> 
> /* Network driver configuration */
> 
> #define INCLUDE_NETWORK
> #define INCLUDE_END             /* Enhanced Network Driver (see
> configNet.h) */
> 
> #undef  INCLUDE_EX
> #undef  INCLUDE_ENP
> #undef  INCLUDE_SM_NET
> 
> /* VME configuration */
> 
> /*
>  * TODO -
>  * Only those options that are actually user changeable should be
> defined
>  * here.  Options that cannot be changed should be moved to
> template.h.
>  */
> 
> #undef  INCLUDE_VME
> 
> /* A16 master window maps all of A16 to 0xff800000 locally */
> 
> #define VME_A16_MSTR_BUS        0x0
> #define VME_A16_MSTR_SIZE       0x00010000
> #define VME_A16_MSTR_LOCAL      0xff800000
> 
> /* A24 master window maps all of A24 to 0xf8000000 locally */
> 
> #define VME_A24_MSTR_BUS        0x0
> #define VME_A24_MSTR_SIZE       0x01000000
> #define VME_A24_MSTR_LOCAL      0xf8000000
> 
> /* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
> local. */
> 
> #define VME_A32_MSTR_BUS        (0x80000000)
> #define VME_A32_MSTR_SIZE       (0x02000000)
> #define VME_A32_MSTR_LOCAL      (0x80000000)
> 
> /* A16 slave window is not supported */
> 
> #define VME_A16_SLV_LOCAL       0x0
> #define VME_A16_SLV_BUS         0x0
> #define VME_A16_SLV_SIZE        0x0
> 
> /* A24 slave window maps 1st 8MB of local memory to bus address
> 0x00800000 */
> 
> #define VME_A24_SLV_LOCAL       LOCAL_MEM_LOCAL_ADRS
> #define VME_A24_SLV_BUS         0x00800000
> #define VME_A24_SLV_SIZE        0x00800000
> 
> /* A32 slave window maps all local memory to bus address 0x80000000 */
> 
> #define VME_A32_SLV_LOCAL       (LOCAL_MEM_LOCAL_ADRS)
> #define VME_A32_SLV_BUS         0x80000000
> #define VME_A32_SLV_SIZE        ((UINT)sysPhysMemTop() -
> LOCAL_MEM_LOCAL_ADRS)
> 
> /* PCI configuration */
> 
> #undef  INCLUDE_PCI
> #undef  INCLUDE_PCI_AUTOCONF
> 
> #ifndef PCI_CFG_TYPE
> #   ifdef INCLUDE_PCI_AUTOCONF
> #      define PCI_CFG_TYPE PCI_CFG_AUTO
> #   else
> #      define PCI_CFG_TYPE PCI_CFG_FORCE
> #   endif /* INCLUDE_PCI_AUTOCONF */
> #endif /* PCI_CFG_TYPE */
>  
> 
> /*
>  * TODO -
>  * Only those options that are actually user changeable should be
> defined
>  * here.  Options that cannot be changed should be moved to
> template.h.
>  */
> 
> /* PCI I/O master window */
> 
> #define PCI_MSTR_IO_LOCAL       0xff800000
> #define PCI_MSTR_IO_BUS         0x0
> #define PCI_MSTR_IO_SIZE        0x00010000
> 
> /* PCI MEMIO master (non-prefetch memory) window */
> 
> #define PCI_MSTR_MEMIO_LOCAL    0xf8000000
> #define PCI_MSTR_MEMIO_BUS      0x0
> #define PCI_MSTR_MEMIO_SIZE     0x01000000
> 
> /* PCI MEM master (prefetchable memory) window */
> 
> #define PCI_MSTR_MEM_LOCAL      0xfa000000
> #define PCI_MSTR_MEM_BUS        0x0
> #define PCI_MSTR_MEM_SIZE       0x01000000
> 
> /* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
> local. */
> 
> #define VME_A32_MSTR_BUS        (0x80000000)
> #define VME_A32_MSTR_SIZE       (0x02000000)
> #define VME_A32_MSTR_LOCAL      (0x80000000)
> 
> /* A16 slave window is not supported */
> 
> #define VME_A16_SLV_LOCAL       0x0
> #define VME_A16_SLV_BUS         0x0
> #define VME_A16_SLV_SIZE        0x0
> 
> /* A24 slave window maps 1st 8MB of local memory to bus address
> 0x00800000 */
> 
> #define VME_A24_SLV_LOCAL       LOCAL_MEM_LOCAL_ADRS
> #define VME_A24_SLV_BUS         0x00800000
> #define VME_A24_SLV_SIZE        0x00800000
> 
> /* A32 slave window maps all local memory to bus address 0x80000000 */
> 
> #define VME_A32_SLV_LOCAL       (LOCAL_MEM_LOCAL_ADRS)
> #define VME_A32_SLV_BUS         0x80000000
> #define VME_A32_SLV_SIZE        ((UINT)sysPhysMemTop() -
> LOCAL_MEM_LOCAL_ADRS)
> 
> /* SCSI driver configuration */
> 
> #if     FALSE                   /* change FALSE to TRUE for SCSI
> interface */
> #define INCLUDE_SCSI            /* include SCSI interface */
> #define INCLUDE_SCSI_DMA        /* include SCSI DMA interface */
> #define INCLUDE_SCSI_BOOT       /* include SCSI for boot option */
> #define INCLUDE_DOSFS           /* DOS file system */
> #undef  INCLUDE_TAPEFS          /* tape file system */
> #undef  INCLUDE_CDROMFS         /* CD-ROM (iso9660) file system */
> #define SYS_SCSI_CONFIG         /* BSP scsi config routine */
> #endif  /* FALSE/TRUE */
> 
> /* Select either SCSI-1 or SCSI-2, independent of INCLUDE_SCSI */
> 
> #define INCLUDE_SCSI2           /* undef for SCSI-1 support */
> 
> /*
>  * User application initialization
>  *
>  * USER_APPL_INIT must be a valid C statement or block.  It is
>  * included in the usrRoot() routine only if INCLUDE_USER_APPL is
>  * defined.  The code for USER_APPL_INIT is only an example.  The
>  * user is expected to change it as needed.  The use of taskSpawn
>  * is recommended over direct execution of the user routine.
>  */
> 
> #undef  INCLUDE_USER_APPL
> #define USER_APPL_INIT \
>         { \
>         IMPORT int myAppInit(); \
>         taskSpawn ("myApp", 30, 0, 5120, \
>                    myAppInit, 0x1, 0x2, 0x3, 0,0,0,0,0,0,0); \
>         }
> 
> /* Configurable interrupt vectors/levels (static defs go in
> template.h) */
> 
> #if     FALSE
> #define INT_VEC_ABORT           xxx
> #define INT_VEC_CLOCK           xxx
> ...
> #define INT_LVL_ABORT           xxx
> #define INT_LVL_CLOCK           xxx
> ...
> #endif
> 
> /* Basic USB Support (PPC, PENTIUM, ARM, MIPS, SH only) */
> 
> #if FALSE       /* set TRUE to include USB support */
> 
> /* USB Host Components */
> 
> #   define INCLUDE_USB                  /* Main USB Component */
> #   undef  INCLUDE_USB_INIT             /* USB Initialization */
> #   define INCLUDE_UHCI                 /* UHCI Controller Driver */
> #   undef  INCLUDE_UHCI_INIT            /* UHCI Initialization */
> #   define INCLUDE_OHCI                 /* OHCI Controller Driver */
> #   undef  INCLUDE_OHCI_INIT            /* OHCI Initialization */
> #   undef  INCLUDE_OHCI_PCI_INIT        /* OHCI PCI Initialization */
> #   define INCLUDE_USBTOOL              /* usbTool Application */
> #   undef  INCDLUE_USB_AUDIO_DEMO       /* USB Audio Demo */
> #   define INCLUDE_USB_MOUSE            /* USB Mouse Driver */
> #   undef  INCLUDE_USB_MOUSE_INIT       /* Mouse Driver Initialization
> */
> #   define INCLUDE_USB_KEYBOARD         /* USB Keyboard Driver */
> #   undef  INCLUDE_USB_KEYBOARD_INIT    /* Keyboard Driver
> Initialization */
> #   define INCLUDE_USB_PRINTER          /* USB Printer Driver */
> #   undef  INCLUDE_USB_PRINTER_INIT     /* Printer Driver
> Initialization */
> #   define INCLUDE_USB_SPEAKER          /* USB Speaker Driver */
> #   undef  INCLUDE_USB_SPEAKER_INIT     /* Speaker Driver
> Initialization */
> #   undef  INCLUDE_USB_MS_BULKONLY      /* USB Bulk Driver */
> #   undef  INCLUDE_USB_MS_BULKONLY_INIT /* Bulk Driver Initialization
> */
> #   undef  INCLUDE_USB_MS_CBI           /* USB CBI Driver */
> #   undef  INCLUDE_USB_MS_CBI_INIT      /* CBI Driver Initialization
> */
> #   undef  INCLUDE_USB_PEGASUS_END      /* USB Pegasus Network Driver
> */
> #   undef  INCLUDE_USB_PEGASUS_END_INIT /* Pegaus Driver
> Initialization */
> 
> /*  USB Parameters */
> 
> #   define BULK_DRIVE_NAME "/bd"                /* Bulk Drive Name */
> #   define CBI_DRIVE_NAME "/cbid"               /* CBI Drive Name */
> #   define PEGASUS_IP_ADDRESS "90.0.0.3"        /* Pegasus IP Address
> */
> #   define PEGASUS_DESTINATION_ADDRESS "90.0.0.53" /* Destination IP
> Address */
> #   define PEGASUS_NET_MASK 0xffffff00          /* Pegasus Net Mask */
> #   define PEGASUS_TARGET_NAME "host"           /* Pegasus Target Name
> */
> 
> #endif /* End of optional USB support */
> 
> /* Optional TFFS support.  Just define INCLUDE_TFFS to activate */
> 
> #undef  INCLUDE_TFFS
> 
> #include "template.h"           /* Verify user options, specify i/o
> addr etc */
> 
> #undef INCLUDE_MMU_BASIC      /* bundled mmu support */
> #undef INCLUDE_CACHE_SUPPORT  /* cache support */
> 
> #ifdef __cplusplus
> }
> #endif
> 
> #endif  /* INCconfigh */
> #if defined(PRJ_BUILD)
> #include "prjParams.h"
> #endif
> 
> /******************************* CONFIGNET.h
> ******************************************************************************/
> /* configNet.h - network configuration header */
> 
> /* Copyright 1984-2002 Wind River Systems, Inc. */
> 
> /*
> TODO -  Remove the template modification history and begin a new
> history
>         starting with version 01a and growing the history upward with
>         each revision.
> 
> modification history
> --------------------
> 01e,28may02,dat  exclude driver if NETWORK not defined, 77135
> 01d,18apr02,rhe  Added C++ Protection
> 01c,13dec00,pai  corrected endDevTbl[] definition (SPR #62994) and
> specified
>                  the return type in the END_LOAD_FUNC declaration.
> 01b,21jul98,db   dec21x40End replaced with template END driver. 
> 01a,07jul97,dat  written (from mv2603/configNet.h,ver 01b)
> */
>  
> #ifndef INCnetConfigh
> #define INCnetConfigh
> 
> #ifdef __cplusplus
> extern "C" {
> #endif
> 
> #ifdef INCLUDE_NETWORK /* ignore everything if NETWORK not included */
> 
> #include "vxWorks.h"
> #include "end.h"
> 
> /* This template presumes the template END driver */
> 
> #define FEI82557_LOAD_FUNC      fei82557EndLoad
> #define FEI82557_BUFF_LOAN      1
> 
> /* <devAdrs>:<PCIadrs>:<ivec>:<ilevel>:<memBase>:<memSize>:<userFlags>
> */
> 
> #define FEI82557_LOAD_STRING    "-1:0x00:0x20:0x20:0x00"
> 
> IMPORT END_OBJ * FEI82557_LOAD_FUNC ();
> 
> END_TBL_ENTRY endDevTbl [] =
>     {
>     { 0, FEI82557_LOAD_FUNC, FEI82557_LOAD_STRING, FEI82557_BUFF_LOAN,
> NULL, FALSE},
>     { 0, END_TBL_END, NULL, 0, NULL},
>     };
> 
> #ifdef __cplusplus
> }
> #endif
> 
> #endif /* INCLUDE_NETWORK */
> #endif /* INCnetConfigh */
> /*******************************************************************************************/
> 
> /******************************* CONFIGALL.h
> **************************************************/
> 
> 
> /* configAll.h - default configuration header */
> 
> /* Copyright 1984 - 2002 Wind River Systems, Inc. */
> 
> /*
> modification history
> --------------------
> 08s,05jul02,hdn  added I80X86 CPU_FAMILY for 4KB VM_PAGE_SIZE
> 08r,22may02,sbs  Adding default system clock rate macro (SPR #1918)
> 08q,16may02,vvv  restored SLIP support
> 08p,30apr02,elr  Corrected default definition of LOGIN_PASSWORD
> 08o,27mar02,j_s  define WDB_COMM_TYPE to WDB_COMM_END (SPR #73338)
> 08n,13mar02,sn   include all available intrinsics by default
> 08m,13mar02,vvv  removed references to SLIP (SPR #72992)
> 08l,11mar02,sn   Wind Foundation classes no longer supported (SPR
> #73967)
> 08k,07mar02,vvv  fixed MIB startup sequence (SPR #72989)
> 08j,06feb02,sn   include intrinsics by default
> 08i,21jan02,sn   added INCLUDE_CTORS_DTORS to the default
> configuration
> 08h,07jan02,rbl  remove basic C++ again - diab does not have fine
> enough
>                  granularity in its C++ components, so too much is
> being
>                  pulled in. 
> 08g,10dec01,jlb  Change UGL to WindML
> 08f,10dec01,kab  SPR 71410 - stack overflow
> 08e,10dec01,sn   Turned on basic C++ by default; removed obsolete 
>                  INCLUDE_CPLUS_TOOLS
> 08d,03dec01,g_h  Adding WDB_COMM_VTMD macro.
> 08c,13aug01,pch  add PPC440
> 08b,20nov01,bwa  Added INCLUDE_VXEVENTS to default configuration.
> 08a,08nov01,jn   switch ARM OMF from COFF to ELF
> 07z,31oct01,gls  merged in pthread code from AE
> 07y,06nov01,vvv  made NFS max. path length configurable (SPR #63551)
> 07x,01nov01,vvv  changed BOOTP_MAX_REQUESTS to 3
> 07w,29oct01,sn   Temporarily remove C++ from default configuration
> 07v,10oct01,pad  Switched i86 architecture to ELF OMF.
> 07u,09oct01,rae  merge from truestack ver 07s, base 07q
> 07t,08oct01,dee  Merge from ColdFire T2.1.0 release
> 07s,04oct01,jws  change SM_OBJ_MAX_TRIES to 5000 (SPR68418)
> 07s,03oct01,jkf  added dosFs2 specific defines to FALSE section.
> 07r,18sep01,pcm  added INCLUDE_EXC_SHOW and INCLUDE_LSTLIB
> 07q,07sep01,zl   excluded HW floating point support for SH7700.
> 07q,27jul01,to   define INCLUDE_SW_FP for ARM
> 07p,14oct99,jk   added INCLUDE_SOUND to excluded facilities.
> 07p,10nov00,s_m  PPC405 support
> 07q,25oct00,rec  increase stack save size for ARM
> 07p,21oct99,jgn  stop shared memory network & proxy ARP being defaults
> 07r,13apr01,mem  Disable proxy arp client by default.
> 07q,27oct00,spm  fixed DHCP startup update and mod history entry
> 07p,23oct00,niq  updated DHCP startup for latest version (from tor3_x
> branch)
> 07p,02mar00,zl   merged SH support into T2
> 07o,19mar99,dat  removed old driver support SPR 25877
> 07n,10mar99,drm  changing WINDMP to VXFUSION to reflect new product
> name.
> 07m,23feb99,sn   corrected comment for INCLUDE_CPLUS_STL
>                  removed INCLUDE_CPLUS_BOOCH and INCLUDE_CPLUS_HEAP
> since
>                  they're no-ops.
> 07l,04feb99,jmp  added INCLUDE_TSFS_BOOT &
> INCLUDE_TSFS_BOOT_VIO_CONSOLE to
>                  the excluded facilities list (SPR# 24466).
> 07k,02feb99,tm   added PCI configuration type constants (PCI_CFG_*)
> 07j,28jan99,dat  removed INCLUDE_JAVA_RTX, according to simon
> 07i,27jan99,jco  merged from graphics2_0 branch
> 07h,19nov98,sn   added entries for C++ macros that are excluded by
> default
> 07h,01dec98,spm  added INCLUDE_ARP for automatic linking of API (SPR
> #7576)
> 07g,27oct98,ms   made INCLUDE_CPLUS the default
> 07f,25aug98,tpr  added PowerPC EC 603 support.
> 07o,01sep98,drm  added INCLUDE_WINDMP
> 07n,17apr98,nps  added INCLUDE_RBUFF.
> 07m,04mar97,jmb  must have HW_FP for HPSIM.
> 07l.28jan98,cth  removed WV_DEFAULT_ definitions
> 07k.18dec97,cth  reworked defines for WV 2.0, removed
> INCLUDE_INSTRUMENTATION
> 07j.20aug97,cth  added INCLUDE_WDB_TSFS option
> 07i,09mar98,sjw  added Java macros for conflict resolution
> 07h,26jun97,ics  added INCLUDE_HTTP (for Wind Web Server)
> 07g,02jun97,tcy  added support for WILLOWS RT
> 07o,04may98,cym  added SIMNT.
> 07n,29apr98,dbt  removed RDB referencies (no longer supported).
> 07m,19mar98,dbt  added INCLUDE_WDB_START_NOTIFY and
> INCLUDE_WDB_USER_EVENT.
> 07l,18mar98,jmb  HPSIM merge:  must have hardware FP
> 07k,11mar98,pdn  added WDB_COMM_PIPE (for VxSims)
> 07i,24nov97,jpd  changed VM_PAGE_SIZE for ARM family.
> 07f,06oct97,spm  added BSD43_COMPATIBLE define (optional binary
> compatibility).
> 07e,26aug97,spm  added defines for DHCP port selection
> 07d,15jul97,spm  added support for SNTP client and server
> 07c,03jul97,vin  added INCLUDE_ROUTE_SOCK
> 07b,03jul97,sgv  added INCLUDE_FTPD_SECURITY to fix spr #8602
> 07a,28apr97,spm  added DHCP_MAX_HOPS from dhcprLib.h
> 06w,02feb98,dbt  added INCLUDE_WDB_EVENTPOINTS to support WDB
> eventpoints.
> 06v,10dec97,spm  added INCLUDE_FTPD_SECURITY to support configurable
> password
>                  authentication for FTP server (SPR #8602)
> 06u,04feb96,ms   added WDB support for NetROM 500 series.
> 06z,17apr97,vin  added INCLUDE_IP_FILTER.
> 06y,10apr97,jag  added support for DNS resolver.
> 06x,07arp97,vin  added INCLUDE_MCAST_ROUTING
> 06w,07apr97,spm  added support for DHCP server and relay agent
> 06v,07apr97,gnn  removed bogus RIP defaults
> 06u,14feb97,rjc  added OSPF_INCLUDE dfine for ospf routing
> 06t,29jan97,spm  added DHCPC_MIN_LEASE define and changed
> DHCPC_DEFAULT_LEASE.
> 06s,11jan97,vin  reorganized network related includes.
> 06r,04dec96,gnn  added RIP and DHCP defines.
> 06q,28aug96,gnn  added WDB_COMM_END define.
> 06u,28nov96,cdp  added ARM support.
> 06t,03dec96,dbt  removed #ifdef INCLUDE_ANSI_ALL and #ifdef
> INCLUDE_MIB2_ALL
>                  (moved in usrDepend.c).
> 06s,15nov96,jag  changed string associated with MIB2_SYS_DESCR (SPR#
> 7476)
> 06r,04oct96,elp  added INCLUDE_SYM_TBL_SYNC (SPR# 6775).
> 06q,09aug96,dbt  Moved the ifdef INCLUDE_POSIX_ALL to usrDepend.c (SPR
> #5524).
> 06p,29jul96,ms   reworked the fix for SPR #5603.
> 06o,24jul96,ism  hand-merged SIMSOLARIS.
> 06n,19jul96,dbt  Moved the ifdef INCLUDE_CONFIGURATION_5_2
>                  to usrDepend.c (SPR #5603).
> 06m,11jul96,jmb  Eliminated alternative WDB macros names.  SPR #5707
> 06l,21jun96,jmb  long modhist -- deleted entries prior to 1994.  SPR
> #6528
> 06k,20jun96,tpr  added PowerPC 860 support.
> 06j,18jun96,dbt  removed line INCLUDE_ADA (spr 6645)
> 06i,10jun96,tam  changed STACK_RESIDENT to RAM_DST_ADRS for PPC
> 06j,16oct96.rjc  deleted snmp memory partition defines
> 06j,12aug96.rjc  changes for snmpdMemoryAlloc changes
> 06i,22apr96,kkk  fixed typo on CPU_FAMILY for PPC (SPR# 6385)
> 06h,04apr96,rjc  Modifications for snmp v1 agent for 5.3
> 06g,07mar96,dat  WDB comm config can be specified on make command line
> 06f,05mar96,tpr  Added RESERVED for PowerPC.
> 06e,04dec95,vin  increased EVT_STACK_SIZE to 7000.
> 06d,06sep95,jag  deleted unnecessary STREAMS defines.
> 06c,01aug95,dzb  renamed STREAMS macros.  Added STREAMS_PROTO_INIT_RTN
> macro.
> 06b,28jul95,jag  Changed INCLUDE_STREAMS_LOG to INCLUDE_STREAMS_STRACE
> and
>                  INCLUDE_STREAMS_STERR. Changed STREAMS_LOG_CONFIG_DIR
> to
>                  STREAMS_STRERR_OUTPUT_DIR and
> STREAMS_STRACE_OUTPUT_DIR
> 06a,26jul95,dzb  adjusted default socket macro for STREAMS.
> 05z,25jul95,dzb  added INCLUDE_BSD_SOCKET and DEFAULT_XXX_SOCKET.
> 05y,18jul95,dzb  added PPP_CONNECT_DELAY.
> 05x,11jul95,dzb  modified INCLUDE_PPP inclusion.
> 05w,26jun95,dzb  removed PPP_OPT_USEHOSTNAME option.
> 05v,22jun95,sgv  Added STREAMS support
> 05u,21jun95,dzb  Added INCLUDE_PPP_CRYPT for unbundled crypt()
> support.
> 05t,20jun95,dzb  added PPP support.
> 06e,23sep95,tpr  changed VM_PAGE_SIZE for PPC family.
> 06d,19jun95,caf  additional PPC support.
> 06e,11oct95,ms   made 5.2 configuration easier to recreate (SPR
> #5134).
> 06d,10oct95,dat  backward compatible BSP_VERSION and BSP_REV
> 06c,28sep95,dat  new #define INCLUDE_WDB_ANNOUNCE
> 06b,21sep95,ms   switched some WDB macros between here and usrWdb.c
> 06a,27jun95,ms   renamed WDB_COMM_XXX macros
> 05z,21jun95,ms   added INCLUDE_WDB_TTY_TEST and
> INCLUDE_WDB_EXIT_NOTIFY
> 05y,21jun95,tpr  added #define INCLUDE_WDB_MEM.
> 05x,13jun95,srh  Updated C++ support triggers.
> 05w,07jun95,ms   WDB_STACK_SIZE is now CPU dependant.
> 05v,07jun95,p_m  added INCLUDE_FORMATTED_IO. suppressed spy from
> default
>                  configuration.
> 05u,01jun95,ms   all WDB macros start with WDB_ (usrWdb.c modhist has
> details).
> 05t,22may95,ms   added WDB agent support.
>           + p_m  suppressed shell, symbol table and debug support from
> default
>                  configuration.
> 05s,29mar95,kdl  added INCLUDE_GCC_FP.
> 05r,28mar95,kkk  added scalability MACROS, changed edata and end to
> arrays
>                  (SPR #3917), added misc constants SM_PKTS_SIZE and
>                  SM_CPUS_MAX (SPR #4130), added misc constant
> CONSOLE_BAUD_RATE
> 05q,24mar95,tpr  added #define USER_B_CACHE_ENABLE (SPR #4168).
> 05p,14mar95,caf  restored mips resident rom support (SPR #3856).
> 05o,18jan95,tmk  Added MC68060 case for HW_FP
> 06c,25may95,yao  changed to use _end for FREE_MEM_ADRS for PowerPC.
> 06b,12jan95,caf  added PPC floating point support.
> 06a,09jan95,yao  added PPC support.
> 05n,10dec94,kdl  Moved INCLUDE_POSIX_ALL to unincluded (SPR 3822).
> 05m,10dec94,caf  undid mod 05a, use _sdata for resident roms (SPR
> #3856).
> 05l,09dec94,jag  Added INCLUDE_MIB2_AT.
> 05k,17nov94,kdl  Added INCLUDE_NFS_SERVER (excluded); removed TRON
> references.
> 05j,13nov94,dzb  Moved INCLUDE_PING to excluded.
> 05i,11nov94,dzb  Added ZBUF_SOCK, TCP_DEBUG, and PING defines.
> 05h,11nov94,jag  cleanup of SNMP and MIB defines.
> 05g,04nov94,kdl  initial merge cleanup.
> 05b,16jun94,caf  defined INCLUDE_ELF for MIPS, updated copyright
> notice.
> 04x,20jul94,ms   changed INCLUDE_HPPA_OUT to INCLUDE_SOM_COFF
> 05d,11apr94,jag  Removed conditions for definition of  NFS_GROUP and
> NFS_USER
>                  ID for SNMP demo support.
> 05c,18feb94,elh  (SNMP VERSION) moved INCLUDE_POSIX_ALL to false
> section.
>                  Added support for the mib2 library.
> 05f,25may94,kdl  (POSIX VERSION) removed erroneous NFS def's.
> 05e,23mar94,smb  (POSIX VERSION) removed PASSIVE_MODE
> 05d,15mar94,smb  renamed tEvtTask parameters.
> 05c,15feb94,smb  added define of WV_MODE
> 05b,12jan94,kdl  (POSIX VERSION) turned off instrumentation, added
>                  INCLUDE_POSIX_ALL; added INCLUDE_POSIX_SIGNALS;
> changed
>                  INCLUDE_POSIX_MEM_MAN to INCLUDE_POSIX_MEM; added
>                  NUM_SIGNAL_QUEUES.
> */
> 
> /*
> DESCRIPTION
> This header contains the parameters that define the default
> configuration for VxWorks.
> */
> 
> #ifndef INCconfigAllh
> #define INCconfigAllh
> 
> #include "smLib.h"
> #include "vme.h"
> #include "iv.h"
> 
> /******************************************************************************/
> /*                                                                    
>        */
> /*                      INCLUDED SOFTWARE FACILITIES                  
>        */
> /*                                                                    
>        */
> /******************************************************************************/
> 
> #define INCLUDE_CTORS_DTORS
> #define INCLUDE_CACHE_SUPPORT   /* include cache support package */
> #define INCLUDE_CONSTANT_RDY_Q  /* constant insert time ready queue */
> #define INCLUDE_ENV_VARS        /* unix compatable environment
> variables */
> #define INCLUDE_EXC_HANDLING    /* include basic exception handling */
> #define INCLUDE_EXC_SHOW        /* include exception show routines */
> #define INCLUDE_EXC_TASK        /* miscelaneous support task */
> #define INCLUDE_FLOATING_POINT  /* floating point I/O */
> #define INCLUDE_FORMATTED_IO    /* formatted I/O */
> #define INCLUDE_GCC_FP          /* gcc floating point support
> libraries */
> #define INCLUDE_IO_SYSTEM       /* include I/O system */
> #define INCLUDE_LOGGING         /* logTask logging facility */
> #define INCLUDE_MEM_MGR_FULL    /* full featured memory manager */
> #define INCLUDE_MSG_Q           /* include message queues */
> #define INCLUDE_NETWORK         /* network subsystem code */
> #define INCLUDE_PIPES           /* pipe driver */
> #define INCLUDE_SELECT          /* select() facility */
> #define INCLUDE_SEM_BINARY      /* include binary semaphores */
> #define INCLUDE_SEM_MUTEX       /* include mutex semaphores */
> #define INCLUDE_SEM_COUNTING    /* include counting semaphores */
> #define INCLUDE_SIGNALS         /* software signal library */
> #define INCLUDE_STDIO           /* standard I/O */
> #define INCLUDE_TASK_HOOKS      /* include kernel callouts */
> #define INCLUDE_TASK_VARS       /* task variable package */
> #define INCLUDE_TIMEX           /* timexLib for exec timing */
> #define INCLUDE_TTY_DEV         /* attach serial drivers */
> #define INCLUDE_VXEVENTS        /* include VxWorks events */
> #define INCLUDE_WATCHDOGS       /* include watchdogs */
> #define INCLUDE_WDB             /* WDB debug agent */
> #define INCLUDE_ANSI_ALL        /* includes complete ANSI C library
> functions */
> #define INCLUDE_ANSI_ASSERT     /* ANSI-C assert library functionality
> */
> #define INCLUDE_ANSI_CTYPE      /* ANSI-C ctype library functionality
> */
> #define INCLUDE_ANSI_LOCALE     /* ANSI-C locale library functionality
> */
> #define INCLUDE_ANSI_MATH       /* ANSI-C math library functionality
> */
> #define INCLUDE_ANSI_STDIO      /* ANSI-C stdio library functionality
> */
> #define INCLUDE_ANSI_STDLIB     /* ANSI-C stdlib library functionality
> */
> #define INCLUDE_ANSI_STRING     /* ANSI-C string library functionality
> */
> #define INCLUDE_ANSI_TIME       /* ANSI-C time library functionality
> */
> 
> /* Toolchain specific included software facilities */
> /* The following is for the benefit of the project facility */
> #define INCLUDE_ALL_INTRINSICS
> 
> #ifdef INCLUDE_ALL_INTRINSICS
> #ifdef _ARCH_SUPPORTS_GCC
> #define INCLUDE_GNU_INTRINSICS
> #endif
> #ifdef _ARCH_SUPPORTS_DCC
> #define INCLUDE_DIAB_INTRINSICS
> #endif
> #endif
> 
> /* CPU-SPECIFIC INCLUDED SOFTWARE FACILITIES */
> 
> /* include support for possibly existing floating point coprocessor */
> 
> #if     (CPU==MC68020 || CPU==MC68040 || CPU==MC68060 || CPU==CPU32)
> #define INCLUDE_MC68881         /* MC68881/2 (68040) floating pt
> coprocessor */
> #define INCLUDE_HW_FP           /* potential hardware fp support */
> #endif  /* CPU==MC68020 || CPU==MC68040 || CPU==MC68060 || CPU==CPU32
> */
> 
> #if     (CPU_FAMILY == SPARC) && defined(INCLUDE_FLOATING_POINT)
> #define INCLUDE_SPARC_FPU       /* SPARC Floating-Point Unit */
> #define INCLUDE_HW_FP           /* potential hardware fp support */
> #endif  /* CPU_FAMILY == SPARC */
> 
> #if     (CPU_FAMILY==MIPS)
> #define INCLUDE_R3010           /* R3010 float point co-processor */
> #define INCLUDE_HW_FP           /* potential hardware fp support */
> #endif  /* CPU_FAMILY==MIPS */
> 
> #if     ((CPU_FAMILY==PPC) && (CPU!=PPC403) && (CPU!=PPC405) &&
> (CPU!=PPC440) \
>         && (CPU!=PPCEC603) && (CPU!=PPC860))
> #define INCLUDE_PPC_FPU         /* PowerPC floating point unit */
> #define INCLUDE_HW_FP           /* potential hardware fp support */
> #endif  /* (CPU_FAMILY==PPC) && (CPU!=PPC4xx) && (CPU!=PPCEC603) &&
> (CPU!=PPC860) */
> 
> #if     (CPU==I960KB)
> #define INCLUDE_HW_FP           /* potential hardware fp support */
> #endif  /* I960KB */
> 
> #if     (CPU_FAMILY==I80X86)
> #define INCLUDE_I80387          /* I80387 float point co-processor */
> #define INCLUDE_HW_FP           /* potential hardware fp support */
> #endif  /* CPU_FAMILY==I80X86 */
> 
> #if     (CPU_FAMILY==SH)
> #if     (CPU==SH7750)
> #define INCLUDE_HW_FP
> #else
> #define INCLUDE_SW_FP
> #endif  /* CPU==SH7750 */
> #endif  /* CPU_FAMILY==SH */
> 
> #if     (CPU_FAMILY==ARM)
> #define INCLUDE_SW_FP
> #endif  /* CPU_FAMILY==ARM */
> 
> #if     (CPU_FAMILY==SIMHPPA)
> #define INCLUDE_HW_FP           /* potential hardware fp support */
> #endif  /* SIMHPPA */
> 
> /* define appropriate object module format for a given architecture */
> 
> #if     ((CPU_FAMILY==MIPS) || (CPU_FAMILY==PPC) || (CPU_FAMILY==SH)
> || \
>          (CPU_FAMILY==SIMSPARCSOLARIS) || (CPU_FAMILY==COLDFIRE) || \
>          (CPU_FAMILY==I80X86) || (CPU_FAMILY==ARM))
> #define INCLUDE_ELF             /* ELF object modules */
> #else
> #if     ((CPU_FAMILY==I960) || (CPU_FAMILY==AM29XXX)) 
> #define INCLUDE_COFF            /* COFF object modules */
> #else
> #if     (CPU_FAMILY==SIMHPPA)
> #define INCLUDE_SOM_COFF
> #else   /* default */
> #if     (CPU_FAMILY==SIMNT)
> #define INCLUDE_PECOFF
> #else   /* default */
> #define INCLUDE_AOUT            /* a.out object modules */
> #endif
> #endif
> #endif
> #endif
> 
> 
> /******************************************************************************/
> /*                                                                    
>        */
> /*                          EXCLUDED FACILITIES                       
>        */
> /*                                                                    
>        */
> /******************************************************************************/
> 
> #if FALSE
> 
> #define INCLUDE_CODETEST        /* CodeTEST target utilities library
> */
> #define INCLUDE_CPLUS           /* include C++ support */
> #define INCLUDE_CPLUS_IOSTREAMS /* include basic iostreams classes */
> #define INCLUDE_CPLUS_STL       /* include Standard Template Library
> core */
> #define INCLUDE_CPLUS_STRING      /* include string class */
> #define INCLUDE_CPLUS_STRING_IO   /* include i/o for string class */
> #define INCLUDE_CPLUS_COMPLEX     /* include complex number class */
> #define INCLUDE_CPLUS_COMPLEX_IO  /* include i/o for complex number
> class */
> #define INCLUDE_CPLUS_IOSTREAMS_FULL  /* include all of iostreams */
> #define INCLUDE_CONFIGURATION_5_2 /* pre-tornado tools */
> #define INCLUDE_DEBUG           /* pre-tornado debugging */
> #define INCLUDE_DEMO            /* include simple demo instead of
> shell */
> 
> #define INCLUDE_DISK_UTIL       /* ls, cd, mkdir, xcopy, etc. */
> #define INCLUDE_DOSFS           /* usrDosFsOld.c wrapper layer */
> #define INCLUDE_DOSFS_MAIN      /* dosFsLib (2) */
> #define INCLUDE_DOSFS_FAT       /* dosFs FAT12/16/32 FAT table handler
> */
> #define INCLUDE_DOSFS_DIR_VFAT  /* Microsoft VFAT dirent handler */
> #define INCLUDE_DOSFS_DIR_FIXED /* 8.3 & VxLongNames directory handler
> */
> #define INCLUDE_DOSFS_FMT       /* dosFs2 file system formatting
> module */
> #define INCLUDE_DOSFS_CHKDSK    /* file system integrity checking */
> #define INCLUDE_CBIO            /* CBIO API module */
> #define INCLUDE_DISK_CACHE      /* CBIO API disk caching layer */
> #define INCLUDE_DISK_PART       /* disk partition handling code,
> fdisk... */
> #define INCLUDE_DISK_UTIL       /* ls, cd, mkdir, xcopy, etc */
> #define INCLUDE_TAR             /* tar utility */
> #define INCLUDE_RAM_DISK        /* CBIO API ram disk driver */
> 
> #define INCLUDE_HTML            /* include HTML support */
> #define INCLUDE_JAVA            /* Java virtual machine */
> #define INCLUDE_LSTLIB          /* include linked list library
> lstLib.c */
> #define INCLUDE_SOUND       /* include support for sampled audio data
> */
> #define INCLUDE_LOADER          /* object module loading */
> 
> /* INCLUDE_MMU_BASIC is defined by many bsp's in config.h. If
> INCLUDE_MMU_FULL
>  * is defined in configAll.h and INCLUDE_MMU_BASIC is defined in
> config.h,
>  * then INCLUDE_MMU_FULL will take precedence.
>  */
> 
> #define INCLUDE_MMU_BASIC       /* bundled mmu support */
> #define INCLUDE_MMU_FULL        /* unbundled mmu support */
> 
> #define INCLUDE_SYM_TBL_SYNC    /* synchronize host and target symbol
> tables */
> 
> #define INCLUDE_POSIX_AIO       /* POSIX async I/O support */
> #define INCLUDE_POSIX_AIO_SYSDRV/* POSIX async I/O system driver */
> #define INCLUDE_POSIX_FTRUNC    /* POSIX ftruncate routine */
> #define INCLUDE_POSIX_MEM       /* POSIX memory locking */
> #define INCLUDE_POSIX_MQ        /* POSIX message queue support */
> #define INCLUDE_POSIX_PTHREADS  /* POSIX pthreads support */
> #define INCLUDE_POSIX_SCHED     /* POSIX scheduling */
> #define INCLUDE_POSIX_SEM       /* POSIX semaphores */
> #define INCLUDE_POSIX_SIGNALS   /* POSIX queued signals */
> #define INCLUDE_POSIX_TIMERS    /* POSIX timers */
> #define INCLUDE_PROTECT_TEXT    /* text segment write protection
> (unbundled) */
> #define INCLUDE_PROTECT_VEC_TABLE /* vector table write protection
> (unbundled)*/
> #define INCLUDE_RAMDRV          /* ram disk driver */
> #define INCLUDE_RAWFS           /* rawFs file system */
> #define INCLUDE_RBUFF           /* ring of buffers library */
> #define INCLUDE_RT11FS          /* rt11Fs file system */
> #define INCLUDE_SECURITY        /* shell security for network access
> */
> #define INCLUDE_SHELL           /* interactive c-expression
> interpreter */
> #define INCLUDE_SHOW_ROUTINES   /* show routines for system
> facilities*/
> #define INCLUDE_SM_OBJ          /* shared memory objects (unbundled)
> */
> #define INCLUDE_SPY             /* spyLib for task monitoring */
> #define INCLUDE_STANDALONE_SYM_TBL /* compiled-in symbol table */
> #define INCLUDE_STARTUP_SCRIPT  /* execute start-up script */
> #define INCLUDE_STAT_SYM_TBL    /* create user-readable error status
> */
> #define INCLUDE_SW_FP           /* software floating point emulation
> */
> #define INCLUDE_SYM_TBL         /* symbol table package */
> #define INCLUDE_WINDML          /* include WindML multimedia Library
> support */
> #define INCLUDE_UNLOADER        /* object module unloading */
> #define INCLUDE_WILLOWS_RT      /* include Willows RT library */
> #define INCLUDE_WDB_TSFS        /* target-server file system */
> #define INCLUDE_VXFUSION        /* WindMP (unbundled) */
> #define INCLUDE_WINDVIEW        /* WindView target facilities */
> #define INCLUDE_WVUPLOAD_ALL    /* include all Windview upload-path
> types */
> #define INCLUDE_WVUPLOAD_FILE   /* include file Windview upload-path
> */
> #define INCLUDE_WVUPLOAD_SOCK   /* include socket Windview upload-path
> */
> #define INCLUDE_WVUPLOAD_TSFSSOCK /* include tsfs sock Windview
> upload-path */
> 
> 
> #define INCLUDE_ANSI_5_0        /* include only version 5.0 ANSI
> support */
> #define INCLUDE_DELETE_5_0      /* define delete() function as in
> VxWorks 5.0 */
> 
> #define INCLUDE_TSFS_BOOT       /* Boot using Target Server File
> System */
> #define INCLUDE_TSFS_BOOT_VIO_CONSOLE   /* use tgtsvr Console for
> TSFS_BOOT */
> 
> #endif  /* FALSE */
> 
> /******************************************************************************/
> /*                                                                    
>        */
> /*                  KERNEL SOFTWARE CONFIGURATION                     
>        */
> /*                                                                    
>        */
> /******************************************************************************/
> 
> #define USER_I_CACHE_MODE       CACHE_WRITETHROUGH  /* default mode */
> #define USER_D_CACHE_MODE       CACHE_WRITETHROUGH  /* default mode */
> #define USER_I_CACHE_ENABLE                         /* undef to leave
> disabled*/
> #define USER_D_CACHE_ENABLE                         /* undef to leave
> disabled*/
> #define USER_B_CACHE_ENABLE                         /* undef to leave
> disabled*/
> #define USER_I_MMU_ENABLE                           /* undef to leave
> disabled*/
> #define USER_D_MMU_ENABLE                           /* undef to leave
> disabled*/
> 
> #define SYM_TBL_HASH_SIZE_LOG2  8       /* 256 entry hash table symbol
> table */
> #define STAT_TBL_HASH_SIZE_LOG2 6       /* 64 entry hash table for
> status */
> #define MQ_HASH_SIZE            0       /* POSIX message queue hash
> table size
>                                          * 0 = default */
> #define NUM_SIGNAL_QUEUES       16      /* POSIX queued signal count
> */
> 
> #if CPU==SIMNT
> #define FREE_RAM_ADRS           simMemBlock
> #else
> #define FREE_RAM_ADRS           (end)   /* start right after bss of
> VxWorks */
> #endif
> 
> 
> /* I/O system parameters */
> 
> #define SYS_CLK_RATE            60      /* default system clock rate
> */
> #define NUM_DRIVERS             20      /* max 20 drivers in drvTable
> */
> #define NUM_FILES               50      /* max 50 files open
> simultaneously */
> #define NUM_DOSFS_FILES         20      /* max 20 dosFs files open */
> #define NUM_RAWFS_FILES         5       /* max 5  rawFs files open */
> #define NUM_RT11FS_FILES        5       /* max 5  rt11Fs files open */
> #define MAX_LOG_MSGS            50      /* max 50 log msgs */
> 
> #define NUM_TTY                 2       /* number of tty channels */
> #define CONSOLE_TTY             0       /* console channel */
> 
> #define CONSOLE_BAUD_RATE       9600    /* console baud rate */
> 
> #ifdef  INCLUDE_SLIP
> #define SLIP_TTY                1       /* serial line IP channel */
> #endif  /* INCLUDE_SLIP */
> 
> #define MAX_LIO_CALLS           0       /* max outstanding lio calls
> 0=default */
> #define MAX_AIO_SYS_TASKS       0       /* max aio system tasks, 0 =
> default */
> #define AIO_TASK_PRIORITY       0       /* aio system tasks prior, 0 =
> default */
> #define AIO_TASK_STACK_SIZE     0       /* aio tasks stack size, 0 =
> default */
> 
> 
> /* kernel and system task parameters by architecture */
> 
> #if     CPU_FAMILY==MC680X0
> #define INT_LOCK_LEVEL          0x7     /* 68k interrupt disable mask
> */
> #define ROOT_STACK_SIZE         10000   /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
> */
> #define TRAP_DEBUG              2       /* trap 2 - breakpoint trap */
> #define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
> #endif  /* CPU_FAMILY==MC680X0 */
> 
> #if     CPU_FAMILY==COLDFIRE
> #define INT_LOCK_LEVEL          0x7     /* 68k interrupt disable mask
> */
> #define ROOT_STACK_SIZE         10000   /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
> */
> #define TRAP_DEBUG              2       /* trap 2 - breakpoint trap */
> #define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
> #endif  /* CPU_FAMILY==COLDFIRE */
> 
> #if     CPU_FAMILY==SPARC
> #define INT_LOCK_LEVEL          15      /* SPARC interrupt disable
> level */
> #define ROOT_STACK_SIZE         10000   /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        50000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          10000   /* size of ISR stack, in bytes
> */
> #define VEC_BASE                (LOCAL_MEM_LOCAL_ADRS + 0x1000)
> #define VEC_BASE_ADRS           ((char *) VEC_BASE)
> #endif  /* CPU_FAMILY==SPARC */
> 
> #if CPU_FAMILY==SIMNT || CPU_FAMILY==SIMSPARCSUNOS  ||
> CPU_FAMILY==SIMHPPA || CPU_FAMILY==SIMSPARCSOLARIS
> #define INT_LOCK_LEVEL          0x1     /* interrupt disable mask */
> #define ROOT_STACK_SIZE         20000   /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        50000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          50000   /* size of ISR stack, in bytes
> */
> #define VEC_BASE_ADRS           0       /* dummy */
> #endif  /* CPU_FAMILY ==SIMNT || CPU_FAMILY==SIMSPARCSUNOS  ||
> CPU_FAMILY==SIMHPPA || CPU_FAMILY==SIMSPARCSOLARIS */
> 
> #if     CPU_FAMILY==I960
> #define INT_LOCK_LEVEL          0x1f    /* i960 interrupt disable mask
> */
> #define ROOT_STACK_SIZE         20000   /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        40000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
> */
> #define TRAP_DEBUG              0       /* n/a for the 80960 */
> #define VEC_BASE_ADRS           NONE    /* base register not
> reconfigurable */
> #endif  /* CPU_FAMILY==I960 */
> 
> #if     CPU_FAMILY==MIPS
> #define INT_LOCK_LEVEL          0x1     /* R3K interrupt disable mask
> */
> #define ROOT_STACK_SIZE         (20000) /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        (20000) /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          (0x2000)/* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          (5000)  /* size of ISR stack, in bytes
> */
> #define VEC_BASE_ADRS           ((char *) 0x0)  /* meaningless in R3k
> land */
> #define VME_VECTORED            FALSE   /* use vectored VME interrupts
> */
> #define TRAP_DEBUG              0       /* trap 0 - breakpoint trap */
> #endif  /* CPU_FAMILY==MIPS */
> 
> #if     CPU_FAMILY==PPC
> #define INT_LOCK_LEVEL          0x0     /* not used */
> #define BOOT_CMD_STACK_SIZE     (11000) /* size of boot cmd stack, in
> bytes */
> #define ROOT_STACK_SIZE         (24000) /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        (20000) /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          (5000)  /* size of ISR stack, in bytes
> */
> #define VEC_BASE_ADRS           ((char *) 0x0)
> #endif  /* CPU_FAMILY==PPC */
> 
> #if     CPU_FAMILY==I80X86
> #define INT_LOCK_LEVEL          0x0     /* 80x86 interrupt disable
> mask */
> #define ROOT_STACK_SIZE         10000   /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
> */
> #define TRAP_DEBUG              0       /* not used */
> #define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
> #endif  /* CPU_FAMILY==I80X86 */
> 
> #if     CPU_FAMILY==AM29XXX
> #define INT_LOCK_LEVEL          0x0001  /* 29k all interrupts disable
> mask */
> #define ROOT_STACK_SIZE         10000   /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        40000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          10000   /* size of ISR stack, in bytes
> */
> #define TRAP_DEBUG              15      /* trap 2 - breakpoint trap */
> #define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
> #endif  /* CPU_FAMILY==AM29XXX */
> 
> #if     CPU_FAMILY==SH
> #define INT_LOCK_LEVEL          15
> #define ROOT_STACK_SIZE         10000
> #define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
> in bytes */
> #define ISR_STACK_SIZE          1000
> #define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
> #endif  /* CPU_FAMILY==SH */
> 
> #if     CPU_FAMILY==ARM
> #define INT_LOCK_LEVEL          0       /* interrupt disable mask -
> unused */
> #define ROOT_STACK_SIZE         0x4000  /* size of root's stack, in
> bytes */
> #define SHELL_STACK_SIZE        0x10000 /* size of shell's stack, in
> bytes */
> #define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
> in bytes */
> #define TRAP_DEBUG              0       /* not used */
> #define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
> /*
>  * NOTE: ISR_STACK_SIZE defined in config.h, not here - BSP interrupt
>  *       structure dependent
>  */
> #endif  /* CPU_FAMILY==ARM */
> 
> #ifndef BOOT_CMD_STACK_SIZE
> #define BOOT_CMD_STACK_SIZE     7000
> #endif  /* BOOT_CMD_STACK_SIZE */
> 
> /* WDB debug agent configuration */
> 
> #ifdef  INCLUDE_WDB
> 
> /* optional agent facilities */
> 
> #define INCLUDE_WDB_BANNER              /* print banner after agent
> starts */
> #define INCLUDE_WDB_VIO                 /* virtual I/O support */
> #define INCLUDE_WDB_TTY_TEST            /* test serial line
> communcation */
> #define INCLUDE_WDB_START_NOTIFY        /* notify the host of task
> creation */
> #define INCLUDE_WDB_USER_EVENT          /* user events handling */
> 
> /* core agent facilities - do not remove */
> 
> #define INCLUDE_WDB_CTXT                /* context control */
> #define INCLUDE_WDB_FUNC_CALL           /* spawn function as separate
> task */
> #define INCLUDE_WDB_DIRECT_CALL         /* call function in agents
> context */
> #define INCLUDE_WDB_EVENTS              /* host async event
> notification */
> #define INCLUDE_WDB_GOPHER              /* gopher info gathering */
> #define INCLUDE_WDB_BP                  /* breakpoint support */
> #define INCLUDE_WDB_EXC_NOTIFY          /* notify host of exceptions
> */
> #define INCLUDE_WDB_EXIT_NOTIFY         /* notify the host of task
> exit */
> #define INCLUDE_WDB_REG                 /* get/set hardware registers
> */
> #define INCLUDE_WDB_EVENTPOINTS         /* eventpoints handling */
> #define INCLUDE_WDB_MEM                 /* optional memory services */
> 
> /* agent mode */
> 
> #define WDB_MODE        WDB_MODE_DUAL   /* WDB_MODE_[DUAL|TASK|EXTERN]
> */
> 
> /* agent communication paths */
> 
> #define WDB_COMM_NETWORK        0       /* vxWorks network      - task
> mode */
> #define WDB_COMM_SERIAL         1       /* raw serial           -
> bimodal   */
> #define WDB_COMM_TYCODRV_5_2    2       /* older serial driver  - task
> mode */
> #define WDB_COMM_ULIP           3       /* vxSim packet device  -
> bimodal   */
> #define WDB_COMM_NETROM         4       /* netrom packet device -
> bimodal   */
> #define WDB_COMM_CUSTOM         5       /* custom packet device -
> bimodal   */
> #define WDB_COMM_END            6       /* END packet device    -
> bimodal */
> #define WDB_COMM_PIPE           7       /* vxSim pipe device    -
> bimodal   */
> #define WDB_COMM_VTMD           8       /* TMD packet device    -
> bimodal   */
> 
> /* communication path configuration */
> 
> #ifndef WDB_COMM_TYPE
> #define WDB_COMM_TYPE WDB_COMM_SERIAL   /* default path is the network
> */
> #endif
> 
> #ifndef WDB_TTY_CHANNEL
> #define WDB_TTY_CHANNEL         1       /* default Sio SERIAL channel
> */
> #endif
> 
> #ifndef WDB_TTY_DEV_NAME
> #define WDB_TTY_DEV_NAME    "/tyCo/1"   /* default TYCODRV_5_2 device
> name */
> #endif
> 
> #ifndef WDB_TTY_BAUD
> #define WDB_TTY_BAUD            9600    /* default baud rate */
> #endif
> 
> #ifndef WDB_ULIP_DEV
> #define WDB_ULIP_DEV    "/dev/ulip14"   /* default ULIP packet device
> */
> #endif
> 
> #define WDB_NETROM_TYPE         400     /* default is old 400 series
> */
> #define WDB_NETROM_WIDTH        1       /* width of a ROM word. This
> macro
>                                          * is not used for the 500
> series. */
> #define WDB_NETROM_INDEX        0       /* index into word of pod zero
> */
> #define WDB_NETROM_NUM_ACCESS   1       /* of pod zero per byte read
> */
> #define WDB_NETROM_ROMSIZE      ROM_SIZE /* size of a single ROM. If
> your
>                                          * board has N ROMs, this
> definition
>                                          * must be divided by N to be
> right */
> #define WDB_NETROM_POLL_DELAY   2       /* # clock ticks to poll for
> input */
> 
> /* miscelaneous agent constants */
> 
> #define WDB_MTU                 1500    /* max RPC message size */
> #define WDB_POOL_SIZE           ((sysMemTop() - FREE_RAM_ADRS)/16) /*
> memory pool for host tools */
> #define WDB_SPAWN_STACK_SIZE    0x5000  /* default stack size of
> spawned task */
> 
> #endif  /* INCLUDE_WDB */
> 
> 
> /******************************************************************************/
> /*                                                                    
>        */
> /*                   "GENERIC" BOARD CONFIGURATION                    
>        */
> /*                                                                    
>        */
> /******************************************************************************/
> 
> /* device controller I/O addresses when included */
> 
> #define IO_ADRS_EI      ((char *) 0x000fff00)   /* 32A,32D i82596CA
> Ethernet */
> 
> 
> /******************************************************************************/
> /*                                                                    
>        */
> /*                   "MISCELLANEOUS" CONSTANTS                        
>        */
> /*                                                                    
>        */
> /******************************************************************************/
> 
> /* shared memory objects parameters (unbundled) */
> 
> #define SM_OBJ_MAX_TASK         40      /* max # of tasks using smObj
> */
> #define SM_OBJ_MAX_SEM          60      /* max # of shared semaphores
> */
> #define SM_OBJ_MAX_MSG_Q        10      /* max # of shared message
> queues */
> #define SM_OBJ_MAX_MEM_PART     4       /* max # of shared memory
> partitions */
> #define SM_OBJ_MAX_NAME         100     /* max # of shared objects
> names */
> #define SM_OBJ_MAX_TRIES        5000    /* max # of tries to obtain
> lock */
> 
> /* shared memory network parameters  - defaults to values
> DEFAULT_PKTS_SIZE
>  * and DEFAULT_CPUS_MAX in smPktLib.h respectively
>  */
> 
> #define SM_PKTS_SIZE            0       /* shared memory packet size
> */
> #define SM_CPUS_MAX             0       /* max # of cpus for shared
> network */
> 
> /* low memory layout */
> 
> #if     (CPU_FAMILY == I80X86)
> #define GDT_BASE_OFFSET         0x800
> #define SM_ANCHOR_OFFSET        0x1100
> #define BOOT_LINE_OFFSET        0x1200
> #define EXC_MSG_OFFSET          0x1300
> #elif   (CPU_FAMILY == PPC)
> #define SM_ANCHOR_OFFSET        0x4100
> #define BOOT_LINE_OFFSET        0x4200
> #define EXC_MSG_OFFSET          0x4300
> #elif   (CPU==SH7750 || CPU==SH7729 || CPU==SH7700)
> #define SM_ANCHOR_OFFSET        0x1600  /* not used for SDRAM config.
> */
> #define BOOT_LINE_OFFSET        0x1700
> #define EXC_MSG_OFFSET          0x1800
> #else
> #define SM_ANCHOR_OFFSET        0x600
> #define BOOT_LINE_OFFSET        0x700
> #define EXC_MSG_OFFSET          0x800
> #endif  /* (CPU_FAMILY == I80X86) */
> 
> /* The backplane driver onboard anchor at the following address */
> 
> #define SM_ANCHOR_ADRS  ((char *)
> (LOCAL_MEM_LOCAL_ADRS+SM_ANCHOR_OFFSET))
> 
> 
> /* The bootroms put the boot line at the following address */
> 
> #define BOOT_LINE_ADRS  ((char *)
> (LOCAL_MEM_LOCAL_ADRS+BOOT_LINE_OFFSET))
> #define BOOT_LINE_SIZE  255     /* use 255 bytes for bootline */
> 
> /* The boot line is stored in non-volatile RAM at the following offset
> */
> 
> #define NV_BOOT_OFFSET  0       /* store the boot line at start of
> NVRAM */
> 
> 
> /* Messages from exceptions during exceptions go at the following
> address */
> 
> #define EXC_MSG_ADRS    ((char *)
> (LOCAL_MEM_LOCAL_ADRS+EXC_MSG_OFFSET))
> 
> 
> /* Backplane H/W support */
> 
> #define SM_TAS_TYPE     SM_TAS_HARD     /* hardware supports
> test-and-set */
> 
> 
> /* Resident ROMs constants */
> 
> #if     ((CPU_FAMILY==I960) || (CPU_FAMILY==ARM))
> #define STACK_SAVE      512             /* maximum stack used to
> preserve */
> #else   /* sparc or others */
> #if     ((CPU_FAMILY==SPARC) || (CPU_FAMILY==PPC))
> #define STACK_SAVE      0x1000
> #else   /* all other architecutes */
> #define STACK_SAVE      0x40            /* maximum stack used to
> preserve */
> #endif                                  /* mips cpp no elif */
> #endif
> 
> #if     (CPU_FAMILY==SPARC)
> #define RESERVED        0x2000          /* vector table base plus
> table size */
> #else   /* 68000 or others */
> #if     (CPU==MC68000)
> #define RESERVED        0x400           /* avoid zeroing MC68302
> vector table */
> #else
> #if     (CPU_FAMILY == PPC)
> #define RESERVED        0x4400          /* avoid zeroing EXC_MSG */
> #else   /* all other architectures */
> #define RESERVED        0
> #endif
> #endif                                  /* mips cpp no elif */
> #endif
> 
> #if     ((CPU_FAMILY == MIPS) || (CPU_FAMILY == PPC))
> #define STACK_RESIDENT  RAM_DST_ADRS
> #else
> #define STACK_RESIDENT  _sdata
> #endif
> 
> #if     (_STACK_DIR == _STACK_GROWS_DOWN)
> 
> #ifdef  ROM_RESIDENT
> #define STACK_ADRS      STACK_RESIDENT
> #else
> #define STACK_ADRS      _romInit
> #endif  /* ROM_RESIDENT */
> 
> #else   /* _STACK_DIR == _STACK_GROWS_UP */
> 
> #ifdef  ROM_RESIDENT
> #define STACK_ADRS      (STACK_RESIDENT-STACK_SAVE)
> #else
> #define STACK_ADRS      (_romInit-STACK_SAVE)
> #endif  /*  ROM_RESIDENT */
> 
> #endif  /* _STACK_DIR == _STACK_GROWS_UP */
> 
> 
> /* Default Boot Parameters */
> 
> #define HOST_NAME_DEFAULT       "bootHost"      /* host name */
> #define TARGET_NAME_DEFAULT     "vxTarget"      /* target name (tn) */
> #define HOST_USER_DEFAULT       "target"        /* user (u) */
> #define HOST_PASSWORD_DEFAULT   ""              /* password */
> #define SCRIPT_DEFAULT          ""              /* startup script (s)
> */
> #define OTHER_DEFAULT           ""              /* other (o) */
> 
> 
> /* Login security initial user name and password.
>  * Use vxencrypt on host to find encrypted password.
>  * Default password provided here is "password".
>  */
> 
> #ifdef  INCLUDE_SECURITY
> #define LOGIN_USER_NAME         "target"
> #define LOGIN_PASSWORD          "RcQbRbzRyc"    /* "password" */
> #endif  /* INCLUDE_SECURITY */
> 
> 
> /* install environment variable task create/delete hooks */
> 
> #ifdef  INCLUDE_ENV_VARS
> #define ENV_VAR_USE_HOOKS       TRUE
> #endif  /* INCLUDE_ENV_VARS */
> 
> /*
>  * default page size for MMU is 8k.
>  * 68040 will also work with 4k page size
>  * powerPC is only 8k
>  */
> 
> #if     ((CPU_FAMILY == PPC) || (CPU_FAMILY == ARM) || (CPU_FAMILY ==
> SH) || \
>          (CPU_FAMILY == I80X86))
> #   define VM_PAGE_SIZE         4096
> #else
> #   define VM_PAGE_SIZE         8192
> #endif  /* (CPU_FAMILY == PPC || ARM || SH || I80X86) */
> 
> /* vxWorks Network Configuration */
> #ifdef INCLUDE_NETWORK
> /******************************************************************************/
> /*                                                                    
>        */
> /*                         INCLUDED NETWORK FACILITIES                
>        */
> /*                                                                    
>        */
> /******************************************************************************/
> #define INCLUDE_BSD_SOCKET      /* include the BSD socket library */
> #define INCLUDE_ICMP            /* include icmp code */
> #define INCLUDE_IGMP            /* include igmp code */
> #define INCLUDE_UDP             /* include udp code */
> #define INCLUDE_TCP             /* include tcp code */
> #define INCLUDE_NET_DRV        /* Newly added  -Mahesh */
> #define INCLUDE_NET_INIT        /* network subsystem initialization */
> #define INCLUDE_NET_REM_IO      /* network remote file i/o driver */
> 
> #define INCLUDE_BOOTP           /* bootp */
> #define INCLUDE_FTP             /* ftp client */
> #define INCLUDE_FTP_SERVER      /* ftp Server */
> 
> /* INCLUDED NETWORK DRIVERS */
> #define INCLUDE_FEI
> #define FEI_POOL_ADRS NONE
> 
> 
> /******************************************************************************/
> /*                                                                    
>        */
> /*                         EXCLUDED NETWORK FACILITIES                
>        */
> /*                                                                    
>        */
> /******************************************************************************/
> #if FALSE
> #define INCLUDE_ARP             /* user interface to ARP table */
> #define INCLUDE_BSD             /* netif driver support */
> #define INCLUDE_DHCPC           /* DHCP client */
> #define INCLUDE_DHCPS           /* DHCP server */
> #define INCLUDE_DHCPR           /* DHCP relay agent */
> #define INCLUDE_DNS_DEBUG       /* DNS resolver debug mode */
> #define INCLUDE_DNS_RESOLVER    /* DNS resolver */
> #define INCLUDE_IP_FILTER       /* IP filter library */
> #define INCLUDE_FTP_SERVER      /* ftp server */
> #define INCLUDE_FTPD_SECURITY   /* password security for ftp sessions
> */
> #define INCLUDE_HTTP            /* http server (Wind Web Server) */
> #define INCLUDE_MCAST_ROUTING   /* include multicast routing in the
> code */
> #define INCLUDE_MIB2_ALL        /* All of MIB 2 */
> #define INCLUDE_MIB2_SYSTEM     /* the system group */
> #define INCLUDE_MIB2_TCP        /* the TCP group */
> #define INCLUDE_MIB2_ICMP       /* the ICMP group */
> #define INCLUDE_MIB2_UDP        /* the UDP group */
> #define INCLUDE_MIB2_IF         /* the interfaces group */
> #define INCLUDE_MIB2_AT         /* the AT group */
> #define INCLUDE_MIB2_IP         /* the IP group */
> #define INCLUDE_NET_SHOW        /* network info and status facilities
> */
> #define INCLUDE_NET_SYM_TBL     /* load symbol table from network */
> #define INCLUDE_NFS             /* nfs package */
> #define INCLUDE_NFS_SERVER      /* nfs server */
> #define INCLUDE_NFS_MOUNT_ALL   /* automatically mount all NFS file
> systems */
> #define INCLUDE_OSPF            /* open shortest path first routing
> protocol */
> #define INCLUDE_PING            /* ping() utility */
> #define INCLUDE_POSIX_ALL       /* include all available POSIX
> functions */
> #define INCLUDE_PPP             /* include Point-to-Point Procotol */
> #define INCLUDE_PROXY_CLIENT    /* proxy arp client (Slave Board) */
> #define INCLUDE_PROXY_DEFAULT_ADDR /* Use ethernet addr to generate bp
> addrs */
> #define INCLUDE_PROXY_SERVER    /* proxy arp server (Master Board) */
> #define INCLUDE_RIP             /* Routing Information Protocol RIP */
> #define INCLUDE_RLOGIN          /* remote login */
> #define INCLUDE_ROUTE_SOCK      /* include routing socket interface */
> #define INCLUDE_RPC             /* rpc package */
> #define INCLUDE_SLIP            /* include serial line interface */
> #define INCLUDE_SM_NET          /* include backplane net interface */
> #define INCLUDE_SM_SEQ_ADDR     /* shared memory network auto address
> setup */
> #define INCLUDE_SNMPD           /* SNMP Agent */
> #define INCLUDE_SNMPD_DEBUG     /* SNMP Agent debugging */
> #define INCLUDE_SNTPC           /* SNTP client */
> #define INCLUDE_SNTPS           /* SNTP server */
> #define INCLUDE_TCP_DEBUG       /* TCP debug facility */
> #define INCLUDE_TELNET          /* telnet-style remote login */
> #define INCLUDE_TFTP_SERVER     /* tftp server */
> #define INCLUDE_ZBUF_SOCK       /* zbuf socket interface */
> 
> #define DEFAULT_STREAMS_SOCKET     /* default to Streams socket for
> AF_INET */
> /* network drivers */
> #define INCLUDE_LN              /* include AMD LANCE interface */
> #define INCLUDE_LNSGI           /* include AMD LANCE interface for SGI
> VIP10 */
> #define INCLUDE_MED             /* include Matrix network interface*/
> #define INCLUDE_NIC             /* include National NIC interface */
> #endif  /* FALSE */
> 
> #endif  /* INCLUDE_NETWORK */
> 
> #ifdef INCLUDE_BSD_SOCKET
>     /*
>      * By default, set the sockets API for compatibility with BSD 4.3
>      * applications.
>      */
> #define BSD43_COMPATIBLE
> #endif
> 
> #ifdef INCLUDE_NFS
> /* Default NFS parameters - constants may be changed here, variables
>  * may be changed in usrConfig.c at the point where NFS is included.
>  */
> 
> #define NFS_USER_ID             2001            /* dummy nfs user id
> */
> #define NFS_GROUP_ID            100             /* dummy nfs user
> group id */
> #endif /* INCLUDE_NFS */
> 
> #if defined (INCLUDE_NFS_SERVER) || defined (INCLUDE_NFS)
> #define NFS_MAXPATH             255             /* max. file path
> length */
> #endif
> 
> /* SNMP configuration parameters */
> 
> #define SNMP_TRACE_LEVEL            0    /* Must be >= 0 and <= 3 with
> higher */
>                                          /* values giving more info
> and 0     */
>                                          /* giving no info            
>        */
> 
> #define PPP_TTY                         1       /* default PPP serial
> channel */
> #define PPP_OPTIONS_STRUCT                      /* use PPP options
> macros */
> #define PPP_OPTIONS_FILE                NULL    /* use PPP options
> file */
> #define PPP_CONNECT_DELAY               15      /* delay to establish
> link */
> 
> #undef  INCLUDE_PPP_CRYPT                       /* include PPP crypt
> support */
> 
> /* PPP options flags - set to 1 to turn on option */
> 
> #define PPP_OPT_NO_ALL                  0       /* Don't allow any
> options */
> #define PPP_OPT_PASSIVE_MODE            0       /* Set passive mode */
> #define PPP_OPT_SILENT_MODE             0       /* Set silent mode */
> #define PPP_OPT_DEFAULTROUTE            0       /* Add default route
> */
> #define PPP_OPT_PROXYARP                0       /* Add proxy ARP entry
> */
> #define PPP_OPT_IPCP_ACCEPT_LOCAL       0       /* Acpt peer's IP addr
> for us */
> #define PPP_OPT_IPCP_ACCEPT_REMOTE      0       /* Acpt peer's IP addr
> for it */
> #define PPP_OPT_NO_IP                   0       /* Disable IP addr
> negot. */
> #define PPP_OPT_NO_ACC                  0       /* Disable
> addr/control compr */
> #define PPP_OPT_NO_PC                   0       /* Disable proto field
> compr */
> #define PPP_OPT_NO_VJ                   0       /* Disable VJ
> compression */
> #define PPP_OPT_NO_VJCCOMP              0       /* Disable VJ conct-ID
> compr */
> #define PPP_OPT_NO_ASYNCMAP             0       /* Disable async map
> negot. */
> #define PPP_OPT_NO_MN                   0       /* Disable magic num
> negot. */
> #define PPP_OPT_NO_MRU                  0       /* Disable MRU
> negotiation */
> #define PPP_OPT_NO_PAP                  0       /* Don't allow PAP
> auth */
> #define PPP_OPT_NO_CHAP                 0       /* Don't allow CHAP
> auth */
> #define PPP_OPT_REQUIRE_PAP             0       /* Require PAP auth */
> #define PPP_OPT_REQUIRE_CHAP            0       /* Require CHAP auth
> */
> #define PPP_OPT_LOGIN                   0       /* Use login dbase for
> PAP */
> #define PPP_OPT_DEBUG                   0       /* Enable daemon debug
> mode */
> #define PPP_OPT_DRIVER_DEBUG            0       /* Enable driver debug
> mode */
> 
> /* PPP options strings - set to desired string to turn on option */
> 
> #define PPP_STR_ASYNCMAP                NULL    /* desired async map
> */
> #define PPP_STR_ESCAPE_CHARS            NULL    /* chars to escape on
> xmits */
> #define PPP_STR_VJ_MAX_SLOTS            NULL    /* max VJ compr header
> slots */
> #define PPP_STR_NETMASK                 NULL    /* netmask value */
> #define PPP_STR_MRU                     NULL    /* MRU value for
> negotiation */
> #define PPP_STR_MTU                     NULL    /* MTU value for
> negotiation */
> #define PPP_STR_LCP_ECHO_FAILURE        NULL    /* max LCP echo
> failures */
> #define PPP_STR_LCP_ECHO_INTERVAL       NULL    /* time for LCP echo
> requests */
> #define PPP_STR_LCP_RESTART             NULL    /* timeout for LCP */
> #define PPP_STR_LCP_MAX_TERMINATE       NULL    /* max LCP term-reqs
> */
> #define PPP_STR_LCP_MAX_CONFIGURE       NULL    /* max LCP conf-reqs
> */
> #define PPP_STR_LCP_MAX_FAILURE         NULL    /* max conf-naks for
> LCP */
> #define PPP_STR_IPCP_RESTART            NULL    /* timeout for IPCP */
> #define PPP_STR_IPCP_MAX_TERMINATE      NULL    /* max IPCP term-reqs
> */
> #define PPP_STR_IPCP_MAX_CONFIGURE      NULL    /* max IPCP conf-reqs
> */
> #define PPP_STR_IPCP_MAX_FAILURE        NULL    /* max # conf-naks for
> IPCP */
> #define PPP_STR_LOCAL_AUTH_NAME         NULL    /* local name for auth
> */
> #define PPP_STR_REMOTE_AUTH_NAME        NULL    /* remote name for
> auth */
> #define PPP_STR_PAP_FILE                NULL    /* PAP secrets file */
> #define PPP_STR_PAP_USER_NAME           NULL    /* username for PAP
> peer auth */
> #define PPP_STR_PAP_PASSWD              NULL    /* password for PAP
> peer auth */
> #define PPP_STR_PAP_RESTART             NULL    /* timeout for PAP */
> #define PPP_STR_PAP_MAX_AUTHREQ         NULL    /* max PAP auth-reqs
> */
> #define PPP_STR_CHAP_FILE               NULL    /* CHAP secrets file
> */
> #define PPP_STR_CHAP_RESTART            NULL    /* timeout for CHAP */
> #define PPP_STR_CHAP_INTERVAL           NULL    /* CHAP rechallenge
> interval */
> #define PPP_STR_CHAP_MAX_CHALLENGE      NULL    /* max CHAP challenges
> */
> 
> /* BOOTP client parameters */
> 
> #ifdef INCLUDE_BOOTP
> #define BOOTP_MAX_HDRSIZE       14    /* Maximum (link-level) Header
> Size */
> #define BOOTP_MAX_REQUESTS      3     /* BOOTP client transmit limit  
>    */
> #endif
> 
> /* DHCP client parameters */
> 
> #ifdef INCLUDE_DHCPC
> #define DHCPC_SPORT             67    /* Port monitored by DHCP
> servers. */
> #define DHCPC_CPORT             68    /* Port monitored by DHCP
> clients. */
> #define DHCPC_MAX_LEASES        4     /* Max. number of simultaneous
> leases */
> #define DHCPC_OFFER_TIMEOUT     5     /* Seconds to wait for multiple
> offers */
> #define DHCPC_DEFAULT_LEASE     3600  /* Desired lease length in
> seconds */
> #define DHCPC_MIN_LEASE         30    /* Minimum allowable lease
> length */
> #define DHCPC_MAX_MSGSIZE       590   /* Allows minimum message on
> Ethernet */
> #endif
> 
> /* DHCP server parameters */
> 
> #ifdef INCLUDE_DHCPS
> #define DHCPS_LEASE_HOOK        NULL   /* Name of required storage
> routine */
> #define DHCPS_ADDRESS_HOOK      NULL   /* Name of optional storage
> routine */
> #define DHCPS_DEFAULT_LEASE     3600   /* default lease length (secs).
> */
> #define DHCPS_MAX_LEASE         3600   /* default value of max lease
> (secs). */
> #endif
> 
> /* DHCP server and relay agent parameters */
> 
> #if defined (INCLUDE_DHCPS) || defined (INCLUDE_DHCPR)
> #define DHCP_MAX_HOPS           4       /* Hops before discard, up to
> 16. */
> #define DHCPS_SPORT             67      /* Port monitored by DHCP
> servers */
> #define DHCPS_CPORT             68      /* Port monitored by DHCP
> clients */
> #define DHCPS_MAX_MSGSIZE       590    /* Allows minimum message on
> Ethernet */
> #endif
> 
> /* SNTP parameters */
> 
> #if defined (INCLUDE_SNTPC) || defined (INCLUDE_SNTPS)
> #define SNTP_PORT 123
> 
> #ifdef INCLUDE_SNTPS
> #define SNTPS_MODE SNTP_ACTIVE     /* SNTP_ACTIVE or SNTP_PASSIVE */
> #define SNTPS_DSTADDR NULL         /* If NULL, uses subnet local
> broadcast. */
> #define SNTPS_INTERVAL 64          /* Broadcast interval, in seconds.
> */
> #define SNTPS_TIME_HOOK NULL       /* Name of required clock access
> routine. */
> #endif    /* SNTP server. */
> #endif /* SNTP server or client. */
> 
> /* DNS resolver parameters; You must change these defaults to your
> config. */
> 
> #ifdef INCLUDE_DNS_RESOLVER
> #define RESOLVER_DOMAIN_SERVER  "90.0.0.3"    /* DNS server IP address
> */
> #define RESOLVER_DOMAIN         "wrs.com"     /* Resolver domain */
> #endif /* INCLUDE_DNS_RESOLVER */
> 
> #ifdef INCLUDE_END
> #ifdef INCLUDE_FEI
> #undef  INCLUDE_FEI        /* Undefine FEI driver */
> #define INCLUDE_FEI_END    /* Use End driver instead */
> #endif
> #endif
> 
> 
> /* PCI device configuration type constants */
> 
> #define PCI_CFG_FORCE 0
> #define PCI_CFG_AUTO  1
> #define PCI_CFG_NONE  2
> 
> /* for backward compatibility with old 1.0 BSPs */
> 
> #ifndef BSP_VERSION
> #   define BSP_VERSION  "1.0"   /* old 1.0 style BSP */
> #   define BSP_VER_1_0  TRUE
> #endif
> 
> #ifndef BSP_REV
> #   define BSP_REV      "/0"    /* old 1.0 style BSP */
> #endif
> 
> #endif  /* INCconfigAllh */
> 
> 
> 
>  
> thanks 
> Mahesh 
> 
> 
> 
> Hi james:
> 
> I tried changing the default setting for the 
> 
> 
> be_gyus@yahoo.com (james) wrote in message news:<ff42611f.0211250149.4d41360a@posting.google.com>...
> > v_mahesh@hotmail.com (Mahesh) wrote in message news:<4f7acce6.0211211832.1ab3277e@posting.google.com>...
> > > Hi:
> > > 
> > > My name is Mahesh, Iam working on creating and Configuring VxWorks
> > > Kernel for target Intel X86 and for windows host.
> > > I have created a Bootrom Image for Network configuration and When i
> > > try to boot the kernel through the floppy disk, the screen becomes
> > > blank and it automatically reboots.
> > > 
> > > I will be happy if somebody can provide me some information. Also, is
> > > there any way to debug and see what is going on underneath the hood.
> > > 
> > > The configuration and software versions are as follows:
> > > VxWorks - 5.5
> > > Tornado - 2.2
> > > CPU - PENTIUM
> > > C++Compiler - g++pentium (version - 2.93)
> > > Host - Windows 2000.
> > > Ethernet Driver - fei82557End Intel Ethernet Driver.
> > > 
> > > The config.h is configured using these macros
> > > INCLUDE_NETWORK
> > > INCLUDE_END,
> > > INCLUDE_FEI_END,
> > > INCLUDE_FTP,
> > > INCLUDE_FTP_SERVER.
> > > 
> > > thanks
> > > Mahesh
> > 
> >  Hi Mahesh,
> > 
> >  This is basically the configuration problem. In your config.h
> > corresponding to the BSP you are using, check whether the Bootline
> > parameters u have given is for fei....& with the right ip address.Mind
> > you ,There should be only one bootline.. comment the other lines if
> > exists in the Bootline for the particular BSP.
> >  Check whether your PC_console has been made TRUE...this will get u a
> > blue screen on the console (monitor if used) if made true else it will
> > give u a blank screen after the vxld........
> >  or the systme remains in a hung state.
> >  To cross check whether the target is up and the n/w is in tact ,Keep
> > pinging the target from the host m/e.
> > 
> >  These are the basic things to be done while building the bootrom.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: trashed vtable
Date: Tue, 26 Nov 2002 05:50:27 GMT
From: "H. E. Taylor" <het@despam.autobahn.mb.ca>
Organization: MTS Internet
Message-ID: <3DE32660.6D26@despam.autobahn.mb.ca>
References: <3DE2EB1B.B9335D52@attbi.com>

In article <3DE2EB1B.B9335D52@attbi.com>,
<BDGold@attbi.com> Barry Gold wrote:
> 
> I'm trying to port a C++ application to VxWorks.  Things seem to go
> along smoothly until the first time I try to delete an object.  Then
> control ends up somewhere random as if the vtable had been trashed.  The
> same application gets much further under Visual C++ - it still dies but
> much later, and in a more explicable way.
> 
> The target machine is an RIOC board (Power PC processor).
> 
> Has anybody else run into similar problems?
>

	In my experience this usually indicates an inadvertent   
	over write of a memory header.  I would suggest 
	attacking the problem by subdividing your application
	to eliminate problem free areas, repeating as required.

<fwiw>
- -het

- --
"progress in software has not followed Moore's law."  -John Holland 

Computer Links: http://www.autobahn.mb.ca/~het/clinks.html
H.E. Taylor  http://www.autobahn.mb.ca/~het/

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for target X86
Date: 25 Nov 2002 15:25:52 -0800
From: v_mahesh@hotmail.com (Mahesh)
Organization: http://groups.google.com/
Message-ID: <4f7acce6.0211251525.5d403f14@posting.google.com>
References: <4f7acce6.0211211832.1ab3277e@posting.google.com> <ff42611f.0211250149.4d41360a@posting.google.com>

HI james: 

thanks for the reply. Please bear with my lack of experience. Iam
attaching the config.h and  configNet.h for your reference....anything
seem blatantly wrong? I
will be happy if you can have a look at it and letme know if iam 
missing something. 

As you have suggested i configured and build the kernel by including
INCLUDE_PC_CONSOLE but some reason it didn't work. I guess something
might be wrong with my configuration.

thanks for the info. 

/************************* CONFIG.H
*****************************************/

/* config.h - template configuration header file */

/* Copyright 1984-2002 Wind River Systems, Inc. */

/*
TODO -  Remove the template modification history and begin a new
history
        starting with version 01a and growing the history upward with
        each revision.

modification history
- --------------------
01y,18apr02,rhe  Added C++ Protection
01x,20dec01,cjj  Changed RAM_HIGH_ADRS to 0x200000
01w,09dec01,dat  Adding USB support for ARM, MIPS, PPC, PENTIUM, SH,
added
                 optional TFFS support for all.
01v,15dec00,pai  Simplified the network configuration macros used in
this file.
                 References to INCLUDE_BSD, INCLUDE_DEFER_NET_INIT,
and
                 INCLUDE_NET_INIT have been removed.  This template
config.h
                 now specifies INCLUDE_NETWORK and INCLUDE_END.  The
remaining
                 network configuration comes from configAll.h.
01u,11dec00,pai  made END driver support the default for new WRN code.
01t,11dec00,pai  introduced INCLUDE_DEFER_NET_INIT configuration
constant for
                 new WRN code.
01s,08apr99,dat  SPR 26491, fixed PCI macro names
01r,29mar99,dat  SPR 26125, added INCLUDE_BSD
01q,02feb99,tm   added PCI AutoConfig support to template BSPs (SPR
24733)
01p,28sep98,dat  added default PCI and VME macros
01o,07nov98,dat  added note about the values for ROM_TEXT_ADRS, and
                 ROM_WARM_ADRS
01n,21jul98,db   defined INCLUDE_NETWORK, changed ROM_SIZE to 0x40000.
01m,07jul98,db   changed BSP_VERSION to "1.2" and BSP_REVISION to
"/0".
                 added BSP_VER_1_2 macro, defined INCLUDE_END, removed
                 END_OVERRIDE(Tornado 2.0 release).
01l,25aug97,dat  code review comments from Kitty
01k,07jul97,dat  added supported for new END ethernet drivers
01j,23apr97,dat  added ROM_WARM_ADRS, INCLUDE_CDROMFS
01i,02apr97,dat  more documentation about VME and other macros.
01h,12mar97,dat  added VME mapping macros
01g,10mar97,dat  comments from reviewers
01f,28feb97,dat  added INCLUDE_USER_APPL, USER_APPL_INIT
01e,05feb97,dat  incorporated comments from Thierry P.
01d,23jan97,dat  moved timer constants to template.h
01c,17jan97,dat  added INCLUDE_SERIAL, INCLUDE_MMU, INCLUDE_VME
01b,16jan97,dat  added LOCAL_MEM_AUTOSIZE and moved INCLUDE_SCSI2
outside
                 of #if FALSE.
01a,22oct96,ms   derived from the mv147 BSP
*/

/*
This file contains the configuration parameters for the template BSP.
This template starts simple - with most facilities excluded by
default.

TODO -
Present the user with simple straight forward options.  Do not ask the
user to encode values together to form a value to be loaded in a
register.
Let the source code, or the pre-processor, do the computational work
to
determine what value to load in a particular register.
*/

#ifndef INCconfigh
#define INCconfigh

#ifdef __cplusplus
extern "C" {
#endif

/* BSP version/revision identification, before configAll.h */

#define BSP_VER_1_1     1       /* 1.2 is backward compatible with 1.1
*/
#define BSP_VER_1_2     1
#define BSP_VERSION     "1.2"
#define BSP_REV         "/0"    /* 0 for first revision */

#include "configAll.h"          /* Set the VxWorks default
configuration */
#include "pc.h"

#define DEFAULT_BOOT_LINE \
        "fei(0,0)/distcomp/wind/target/config/pcPentium2_2/vxWorks " \
        "h=132.200.200.13 e=132.200.200.84 u=admin pw=admin_1 tn=vx86"

/* TODO - values in this header file are dummy values, update as
needed */

/* memory configuration */

#define LOCAL_MEM_LOCAL_ADRS    0               /* fixed at zero */
#undef  LOCAL_MEM_AUTOSIZE                      /* run-time memory
sizing */
#define LOCAL_MEM_SIZE          0x400000        /* 4M memory */
#define USER_RESERVED_MEM       0               /* see sysMemTop() */

/*
 * The constants ROM_TEXT_ADRS, ROM_SIZE, RAM_HIGH_ADRS, and
RAM_LOW_ADRS
 * are defined in config.h and Makefile.
 * All definitions for these constants must be identical.
 *
 * TODO - Make sure these values match those in your Makefile.  The
values
 * shown below are the defaults for a 68000 series system.  Pay
particular
 * attention to ROM_TEXT_ADRS and ROM_WARM_ADRS.  The correct default
values
 * are in the Makefile for each template BSP.
 */

#define ROM_BASE_ADRS           0xff800000      /* base address of ROM
*/
#define ROM_TEXT_ADRS           (ROM_BASE_ADRS+8) /* with PC & SP */
#define ROM_WARM_ADRS           (ROM_TEXT_ADRS+8) /* warm reboot entry
*/
#define ROM_SIZE                0x00040000      /* 256KB ROM space */
#define RAM_HIGH_ADRS           0x00200000      /* RAM address for
bootrom */
#define RAM_LOW_ADRS            0x00010000      /* RAM address for
vxWorks */

/* Serial port configuration */

/* Commented for Now */
/* #define      INCLUDE_SERIAL */
#if     TRUE
#define INCLUDE_PC_CONSOLE
#endif  /* TRUE/FALSE */

#ifdef  INCLUDE_PC_CONSOLE
#define PC_CONSOLE              0
#undef  N_VIRTUAL_CONSOLES
#define N_VIRTUAL_CONSOLES      2

#define KBD_INT_VEC             (INT_VEC_GET (KBD_INT_LVL))

#endif
#undef  NUM_TTY
#define NUM_TTY                 (N_UART_CHANNELS)        /* defined in
template.h */

#define PC_KBD_TYPE             PC_PS2_101_KBD

/* Timer configuration */

#undef  INCLUDE_TIMESTAMP               /* no timestamp driver support
*/

/*
 * Cache configuration
 *
 * TODO -
 * All cache is turned off to begin with. Activate caching after basic
 * BSP functionality is achieved.  Start with instruction caching,
followed
 * by data caching.  Begin without snooping options; and turn those on
 * later if the board supports it.
 *
 * Note that when MMU is enabled, cache modes are controlled by
 * the MMU table entries in sysPhysMemDesc[], not the cache mode
 * macros defined here.
 */

#undef  INCLUDE_CACHE_SUPPORT   /* no cacheLib support */
#undef  USER_I_CACHE_ENABLE
#undef  USER_I_CACHE_MODE
#define USER_I_CACHE_MODE       CACHE_DISABLED
#undef  USER_D_CACHE_ENABLE
#undef  USER_D_CACHE_MODE
#define USER_D_CACHE_MODE       CACHE_DISABLED
#undef  USER_B_CACHE_ENABLE

/* MMU configuration */

#undef  INCLUDE_MMU_BASIC       /* no MMU support */
#undef  INCLUDE_MMU_FULL        /* no MMU support */

/* Network driver configuration */

#define INCLUDE_NETWORK
#define INCLUDE_END             /* Enhanced Network Driver (see
configNet.h) */

#undef  INCLUDE_EX
#undef  INCLUDE_ENP
#undef  INCLUDE_SM_NET

/* VME configuration */

/*
 * TODO -
 * Only those options that are actually user changeable should be
defined
 * here.  Options that cannot be changed should be moved to
template.h.
 */

#undef  INCLUDE_VME

/* A16 master window maps all of A16 to 0xff800000 locally */

#define VME_A16_MSTR_BUS        0x0
#define VME_A16_MSTR_SIZE       0x00010000
#define VME_A16_MSTR_LOCAL      0xff800000

/* A24 master window maps all of A24 to 0xf8000000 locally */

#define VME_A24_MSTR_BUS        0x0
#define VME_A24_MSTR_SIZE       0x01000000
#define VME_A24_MSTR_LOCAL      0xf8000000

/* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
local. */

#define VME_A32_MSTR_BUS        (0x80000000)
#define VME_A32_MSTR_SIZE       (0x02000000)
#define VME_A32_MSTR_LOCAL      (0x80000000)

/* A16 slave window is not supported */

#define VME_A16_SLV_LOCAL       0x0
#define VME_A16_SLV_BUS         0x0
#define VME_A16_SLV_SIZE        0x0

/* A24 slave window maps 1st 8MB of local memory to bus address
0x00800000 */

#define VME_A24_SLV_LOCAL       LOCAL_MEM_LOCAL_ADRS
#define VME_A24_SLV_BUS         0x00800000
#define VME_A24_SLV_SIZE        0x00800000

/* A32 slave window maps all local memory to bus address 0x80000000 */

#define VME_A32_SLV_LOCAL       (LOCAL_MEM_LOCAL_ADRS)
#define VME_A32_SLV_BUS         0x80000000
#define VME_A32_SLV_SIZE        ((UINT)sysPhysMemTop() -
LOCAL_MEM_LOCAL_ADRS)

/* PCI configuration */

#undef  INCLUDE_PCI
#undef  INCLUDE_PCI_AUTOCONF

#ifndef PCI_CFG_TYPE
#   ifdef INCLUDE_PCI_AUTOCONF
#      define PCI_CFG_TYPE PCI_CFG_AUTO
#   else
#      define PCI_CFG_TYPE PCI_CFG_FORCE
#   endif /* INCLUDE_PCI_AUTOCONF */
#endif /* PCI_CFG_TYPE */
 

/*
 * TODO -
 * Only those options that are actually user changeable should be
defined
 * here.  Options that cannot be changed should be moved to
template.h.
 */

/* PCI I/O master window */

#define PCI_MSTR_IO_LOCAL       0xff800000
#define PCI_MSTR_IO_BUS         0x0
#define PCI_MSTR_IO_SIZE        0x00010000

/* PCI MEMIO master (non-prefetch memory) window */

#define PCI_MSTR_MEMIO_LOCAL    0xf8000000
#define PCI_MSTR_MEMIO_BUS      0x0
#define PCI_MSTR_MEMIO_SIZE     0x01000000

/* PCI MEM master (prefetchable memory) window */

#define PCI_MSTR_MEM_LOCAL      0xfa000000
#define PCI_MSTR_MEM_BUS        0x0
#define PCI_MSTR_MEM_SIZE       0x01000000

/* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
local. */

#define VME_A32_MSTR_BUS        (0x80000000)
#define VME_A32_MSTR_SIZE       (0x02000000)
#define VME_A32_MSTR_LOCAL      (0x80000000)

/* A16 slave window is not supported */

#define VME_A16_SLV_LOCAL       0x0
#define VME_A16_SLV_BUS         0x0
#define VME_A16_SLV_SIZE        0x0

/* A24 slave window maps 1st 8MB of local memory to bus address
0x00800000 */

#define VME_A24_SLV_LOCAL       LOCAL_MEM_LOCAL_ADRS
#define VME_A24_SLV_BUS         0x00800000
#define VME_A24_SLV_SIZE        0x00800000

/* A32 slave window maps all local memory to bus address 0x80000000 */

#define VME_A32_SLV_LOCAL       (LOCAL_MEM_LOCAL_ADRS)
#define VME_A32_SLV_BUS         0x80000000
#define VME_A32_SLV_SIZE        ((UINT)sysPhysMemTop() -
LOCAL_MEM_LOCAL_ADRS)

/* SCSI driver configuration */

#if     FALSE                   /* change FALSE to TRUE for SCSI
interface */
#define INCLUDE_SCSI            /* include SCSI interface */
#define INCLUDE_SCSI_DMA        /* include SCSI DMA interface */
#define INCLUDE_SCSI_BOOT       /* include SCSI for boot option */
#define INCLUDE_DOSFS           /* DOS file system */
#undef  INCLUDE_TAPEFS          /* tape file system */
#undef  INCLUDE_CDROMFS         /* CD-ROM (iso9660) file system */
#define SYS_SCSI_CONFIG         /* BSP scsi config routine */
#endif  /* FALSE/TRUE */

/* Select either SCSI-1 or SCSI-2, independent of INCLUDE_SCSI */

#define INCLUDE_SCSI2           /* undef for SCSI-1 support */

/*
 * User application initialization
 *
 * USER_APPL_INIT must be a valid C statement or block.  It is
 * included in the usrRoot() routine only if INCLUDE_USER_APPL is
 * defined.  The code for USER_APPL_INIT is only an example.  The
 * user is expected to change it as needed.  The use of taskSpawn
 * is recommended over direct execution of the user routine.
 */

#undef  INCLUDE_USER_APPL
#define USER_APPL_INIT \
        { \
        IMPORT int myAppInit(); \
        taskSpawn ("myApp", 30, 0, 5120, \
                   myAppInit, 0x1, 0x2, 0x3, 0,0,0,0,0,0,0); \
        }

/* Configurable interrupt vectors/levels (static defs go in
template.h) */

#if     FALSE
#define INT_VEC_ABORT           xxx
#define INT_VEC_CLOCK           xxx
...
#define INT_LVL_ABORT           xxx
#define INT_LVL_CLOCK           xxx
...
#endif

/* Basic USB Support (PPC, PENTIUM, ARM, MIPS, SH only) */

#if FALSE       /* set TRUE to include USB support */

/* USB Host Components */

#   define INCLUDE_USB                  /* Main USB Component */
#   undef  INCLUDE_USB_INIT             /* USB Initialization */
#   define INCLUDE_UHCI                 /* UHCI Controller Driver */
#   undef  INCLUDE_UHCI_INIT            /* UHCI Initialization */
#   define INCLUDE_OHCI                 /* OHCI Controller Driver */
#   undef  INCLUDE_OHCI_INIT            /* OHCI Initialization */
#   undef  INCLUDE_OHCI_PCI_INIT        /* OHCI PCI Initialization */
#   define INCLUDE_USBTOOL              /* usbTool Application */
#   undef  INCDLUE_USB_AUDIO_DEMO       /* USB Audio Demo */
#   define INCLUDE_USB_MOUSE            /* USB Mouse Driver */
#   undef  INCLUDE_USB_MOUSE_INIT       /* Mouse Driver Initialization
*/
#   define INCLUDE_USB_KEYBOARD         /* USB Keyboard Driver */
#   undef  INCLUDE_USB_KEYBOARD_INIT    /* Keyboard Driver
Initialization */
#   define INCLUDE_USB_PRINTER          /* USB Printer Driver */
#   undef  INCLUDE_USB_PRINTER_INIT     /* Printer Driver
Initialization */
#   define INCLUDE_USB_SPEAKER          /* USB Speaker Driver */
#   undef  INCLUDE_USB_SPEAKER_INIT     /* Speaker Driver
Initialization */
#   undef  INCLUDE_USB_MS_BULKONLY      /* USB Bulk Driver */
#   undef  INCLUDE_USB_MS_BULKONLY_INIT /* Bulk Driver Initialization
*/
#   undef  INCLUDE_USB_MS_CBI           /* USB CBI Driver */
#   undef  INCLUDE_USB_MS_CBI_INIT      /* CBI Driver Initialization
*/
#   undef  INCLUDE_USB_PEGASUS_END      /* USB Pegasus Network Driver
*/
#   undef  INCLUDE_USB_PEGASUS_END_INIT /* Pegaus Driver
Initialization */

/*  USB Parameters */

#   define BULK_DRIVE_NAME "/bd"                /* Bulk Drive Name */
#   define CBI_DRIVE_NAME "/cbid"               /* CBI Drive Name */
#   define PEGASUS_IP_ADDRESS "90.0.0.3"        /* Pegasus IP Address
*/
#   define PEGASUS_DESTINATION_ADDRESS "90.0.0.53" /* Destination IP
Address */
#   define PEGASUS_NET_MASK 0xffffff00          /* Pegasus Net Mask */
#   define PEGASUS_TARGET_NAME "host"           /* Pegasus Target Name
*/

#endif /* End of optional USB support */

/* Optional TFFS support.  Just define INCLUDE_TFFS to activate */

#undef  INCLUDE_TFFS

#include "template.h"           /* Verify user options, specify i/o
addr etc */

#undef INCLUDE_MMU_BASIC      /* bundled mmu support */
#undef INCLUDE_CACHE_SUPPORT  /* cache support */

#ifdef __cplusplus
}
#endif

#endif  /* INCconfigh */
#if defined(PRJ_BUILD)
#include "prjParams.h"
#endif

/******************************* CONFIGNET.h
******************************************************************************/
/* configNet.h - network configuration header */

/* Copyright 1984-2002 Wind River Systems, Inc. */

/*
TODO -  Remove the template modification history and begin a new
history
        starting with version 01a and growing the history upward with
        each revision.

modification history
- --------------------
01e,28may02,dat  exclude driver if NETWORK not defined, 77135
01d,18apr02,rhe  Added C++ Protection
01c,13dec00,pai  corrected endDevTbl[] definition (SPR #62994) and
specified
                 the return type in the END_LOAD_FUNC declaration.
01b,21jul98,db   dec21x40End replaced with template END driver. 
01a,07jul97,dat  written (from mv2603/configNet.h,ver 01b)
*/
 
#ifndef INCnetConfigh
#define INCnetConfigh

#ifdef __cplusplus
extern "C" {
#endif

#ifdef INCLUDE_NETWORK /* ignore everything if NETWORK not included */

#include "vxWorks.h"
#include "end.h"

/* This template presumes the template END driver */

#define FEI82557_LOAD_FUNC      fei82557EndLoad
#define FEI82557_BUFF_LOAN      1

/* <devAdrs>:<PCIadrs>:<ivec>:<ilevel>:<memBase>:<memSize>:<userFlags>
*/

#define FEI82557_LOAD_STRING    "-1:0x00:0x20:0x20:0x00"

IMPORT END_OBJ * FEI82557_LOAD_FUNC ();

END_TBL_ENTRY endDevTbl [] =
    {
    { 0, FEI82557_LOAD_FUNC, FEI82557_LOAD_STRING, FEI82557_BUFF_LOAN,
NULL, FALSE},
    { 0, END_TBL_END, NULL, 0, NULL},
    };

#ifdef __cplusplus
}
#endif

#endif /* INCLUDE_NETWORK */
#endif /* INCnetConfigh */
/*******************************************************************************************/

/******************************* CONFIGALL.h
**************************************************/

/* configAll.h - default configuration header */

/* Copyright 1984 - 2002 Wind River Systems, Inc. */

/*
modification history
- --------------------
08s,05jul02,hdn  added I80X86 CPU_FAMILY for 4KB VM_PAGE_SIZE
08r,22may02,sbs  Adding default system clock rate macro (SPR #1918)
08q,16may02,vvv  restored SLIP support
08p,30apr02,elr  Corrected default definition of LOGIN_PASSWORD
08o,27mar02,j_s  define WDB_COMM_TYPE to WDB_COMM_END (SPR #73338)
08n,13mar02,sn   include all available intrinsics by default
08m,13mar02,vvv  removed references to SLIP (SPR #72992)
08l,11mar02,sn   Wind Foundation classes no longer supported (SPR
#73967)
08k,07mar02,vvv  fixed MIB startup sequence (SPR #72989)
08j,06feb02,sn   include intrinsics by default
08i,21jan02,sn   added INCLUDE_CTORS_DTORS to the default
configuration
08h,07jan02,rbl  remove basic C++ again - diab does not have fine
enough
                 granularity in its C++ components, so too much is
being
                 pulled in. 
08g,10dec01,jlb  Change UGL to WindML
08f,10dec01,kab  SPR 71410 - stack overflow
08e,10dec01,sn   Turned on basic C++ by default; removed obsolete 
                 INCLUDE_CPLUS_TOOLS
08d,03dec01,g_h  Adding WDB_COMM_VTMD macro.
08c,13aug01,pch  add PPC440
08b,20nov01,bwa  Added INCLUDE_VXEVENTS to default configuration.
08a,08nov01,jn   switch ARM OMF from COFF to ELF
07z,31oct01,gls  merged in pthread code from AE
07y,06nov01,vvv  made NFS max. path length configurable (SPR #63551)
07x,01nov01,vvv  changed BOOTP_MAX_REQUESTS to 3
07w,29oct01,sn   Temporarily remove C++ from default configuration
07v,10oct01,pad  Switched i86 architecture to ELF OMF.
07u,09oct01,rae  merge from truestack ver 07s, base 07q
07t,08oct01,dee  Merge from ColdFire T2.1.0 release
07s,04oct01,jws  change SM_OBJ_MAX_TRIES to 5000 (SPR68418)
07s,03oct01,jkf  added dosFs2 specific defines to FALSE section.
07r,18sep01,pcm  added INCLUDE_EXC_SHOW and INCLUDE_LSTLIB
07q,07sep01,zl   excluded HW floating point support for SH7700.
07q,27jul01,to   define INCLUDE_SW_FP for ARM
07p,14oct99,jk   added INCLUDE_SOUND to excluded facilities.
07p,10nov00,s_m  PPC405 support
07q,25oct00,rec  increase stack save size for ARM
07p,21oct99,jgn  stop shared memory network & proxy ARP being defaults
07r,13apr01,mem  Disable proxy arp client by default.
07q,27oct00,spm  fixed DHCP startup update and mod history entry
07p,23oct00,niq  updated DHCP startup for latest version (from tor3_x
branch)
07p,02mar00,zl   merged SH support into T2
07o,19mar99,dat  removed old driver support SPR 25877
07n,10mar99,drm  changing WINDMP to VXFUSION to reflect new product
name.
07m,23feb99,sn   corrected comment for INCLUDE_CPLUS_STL
                 removed INCLUDE_CPLUS_BOOCH and INCLUDE_CPLUS_HEAP
since
                 they're no-ops.
07l,04feb99,jmp  added INCLUDE_TSFS_BOOT &
INCLUDE_TSFS_BOOT_VIO_CONSOLE to
                 the excluded facilities list (SPR# 24466).
07k,02feb99,tm   added PCI configuration type constants (PCI_CFG_*)
07j,28jan99,dat  removed INCLUDE_JAVA_RTX, according to simon
07i,27jan99,jco  merged from graphics2_0 branch
07h,19nov98,sn   added entries for C++ macros that are excluded by
default
07h,01dec98,spm  added INCLUDE_ARP for automatic linking of API (SPR
#7576)
07g,27oct98,ms   made INCLUDE_CPLUS the default
07f,25aug98,tpr  added PowerPC EC 603 support.
07o,01sep98,drm  added INCLUDE_WINDMP
07n,17apr98,nps  added INCLUDE_RBUFF.
07m,04mar97,jmb  must have HW_FP for HPSIM.
07l.28jan98,cth  removed WV_DEFAULT_ definitions
07k.18dec97,cth  reworked defines for WV 2.0, removed
INCLUDE_INSTRUMENTATION
07j.20aug97,cth  added INCLUDE_WDB_TSFS option
07i,09mar98,sjw  added Java macros for conflict resolution
07h,26jun97,ics  added INCLUDE_HTTP (for Wind Web Server)
07g,02jun97,tcy  added support for WILLOWS RT
07o,04may98,cym  added SIMNT.
07n,29apr98,dbt  removed RDB referencies (no longer supported).
07m,19mar98,dbt  added INCLUDE_WDB_START_NOTIFY and
INCLUDE_WDB_USER_EVENT.
07l,18mar98,jmb  HPSIM merge:  must have hardware FP
07k,11mar98,pdn  added WDB_COMM_PIPE (for VxSims)
07i,24nov97,jpd  changed VM_PAGE_SIZE for ARM family.
07f,06oct97,spm  added BSD43_COMPATIBLE define (optional binary
compatibility).
07e,26aug97,spm  added defines for DHCP port selection
07d,15jul97,spm  added support for SNTP client and server
07c,03jul97,vin  added INCLUDE_ROUTE_SOCK
07b,03jul97,sgv  added INCLUDE_FTPD_SECURITY to fix spr #8602
07a,28apr97,spm  added DHCP_MAX_HOPS from dhcprLib.h
06w,02feb98,dbt  added INCLUDE_WDB_EVENTPOINTS to support WDB
eventpoints.
06v,10dec97,spm  added INCLUDE_FTPD_SECURITY to support configurable
password
                 authentication for FTP server (SPR #8602)
06u,04feb96,ms   added WDB support for NetROM 500 series.
06z,17apr97,vin  added INCLUDE_IP_FILTER.
06y,10apr97,jag  added support for DNS resolver.
06x,07arp97,vin  added INCLUDE_MCAST_ROUTING
06w,07apr97,spm  added support for DHCP server and relay agent
06v,07apr97,gnn  removed bogus RIP defaults
06u,14feb97,rjc  added OSPF_INCLUDE dfine for ospf routing
06t,29jan97,spm  added DHCPC_MIN_LEASE define and changed
DHCPC_DEFAULT_LEASE.
06s,11jan97,vin  reorganized network related includes.
06r,04dec96,gnn  added RIP and DHCP defines.
06q,28aug96,gnn  added WDB_COMM_END define.
06u,28nov96,cdp  added ARM support.
06t,03dec96,dbt  removed #ifdef INCLUDE_ANSI_ALL and #ifdef
INCLUDE_MIB2_ALL
                 (moved in usrDepend.c).
06s,15nov96,jag  changed string associated with MIB2_SYS_DESCR (SPR#
7476)
06r,04oct96,elp  added INCLUDE_SYM_TBL_SYNC (SPR# 6775).
06q,09aug96,dbt  Moved the ifdef INCLUDE_POSIX_ALL to usrDepend.c (SPR
#5524).
06p,29jul96,ms   reworked the fix for SPR #5603.
06o,24jul96,ism  hand-merged SIMSOLARIS.
06n,19jul96,dbt  Moved the ifdef INCLUDE_CONFIGURATION_5_2
                 to usrDepend.c (SPR #5603).
06m,11jul96,jmb  Eliminated alternative WDB macros names.  SPR #5707
06l,21jun96,jmb  long modhist -- deleted entries prior to 1994.  SPR
#6528
06k,20jun96,tpr  added PowerPC 860 support.
06j,18jun96,dbt  removed line INCLUDE_ADA (spr 6645)
06i,10jun96,tam  changed STACK_RESIDENT to RAM_DST_ADRS for PPC
06j,16oct96.rjc  deleted snmp memory partition defines
06j,12aug96.rjc  changes for snmpdMemoryAlloc changes
06i,22apr96,kkk  fixed typo on CPU_FAMILY for PPC (SPR# 6385)
06h,04apr96,rjc  Modifications for snmp v1 agent for 5.3
06g,07mar96,dat  WDB comm config can be specified on make command line
06f,05mar96,tpr  Added RESERVED for PowerPC.
06e,04dec95,vin  increased EVT_STACK_SIZE to 7000.
06d,06sep95,jag  deleted unnecessary STREAMS defines.
06c,01aug95,dzb  renamed STREAMS macros.  Added STREAMS_PROTO_INIT_RTN
macro.
06b,28jul95,jag  Changed INCLUDE_STREAMS_LOG to INCLUDE_STREAMS_STRACE
and
                 INCLUDE_STREAMS_STERR. Changed STREAMS_LOG_CONFIG_DIR
to
                 STREAMS_STRERR_OUTPUT_DIR and
STREAMS_STRACE_OUTPUT_DIR
06a,26jul95,dzb  adjusted default socket macro for STREAMS.
05z,25jul95,dzb  added INCLUDE_BSD_SOCKET and DEFAULT_XXX_SOCKET.
05y,18jul95,dzb  added PPP_CONNECT_DELAY.
05x,11jul95,dzb  modified INCLUDE_PPP inclusion.
05w,26jun95,dzb  removed PPP_OPT_USEHOSTNAME option.
05v,22jun95,sgv  Added STREAMS support
05u,21jun95,dzb  Added INCLUDE_PPP_CRYPT for unbundled crypt()
support.
05t,20jun95,dzb  added PPP support.
06e,23sep95,tpr  changed VM_PAGE_SIZE for PPC family.
06d,19jun95,caf  additional PPC support.
06e,11oct95,ms   made 5.2 configuration easier to recreate (SPR
#5134).
06d,10oct95,dat  backward compatible BSP_VERSION and BSP_REV
06c,28sep95,dat  new #define INCLUDE_WDB_ANNOUNCE
06b,21sep95,ms   switched some WDB macros between here and usrWdb.c
06a,27jun95,ms   renamed WDB_COMM_XXX macros
05z,21jun95,ms   added INCLUDE_WDB_TTY_TEST and
INCLUDE_WDB_EXIT_NOTIFY
05y,21jun95,tpr  added #define INCLUDE_WDB_MEM.
05x,13jun95,srh  Updated C++ support triggers.
05w,07jun95,ms   WDB_STACK_SIZE is now CPU dependant.
05v,07jun95,p_m  added INCLUDE_FORMATTED_IO. suppressed spy from
default
                 configuration.
05u,01jun95,ms   all WDB macros start with WDB_ (usrWdb.c modhist has
details).
05t,22may95,ms   added WDB agent support.
          + p_m  suppressed shell, symbol table and debug support from
default
                 configuration.
05s,29mar95,kdl  added INCLUDE_GCC_FP.
05r,28mar95,kkk  added scalability MACROS, changed edata and end to
arrays
                 (SPR #3917), added misc constants SM_PKTS_SIZE and
                 SM_CPUS_MAX (SPR #4130), added misc constant
CONSOLE_BAUD_RATE
05q,24mar95,tpr  added #define USER_B_CACHE_ENABLE (SPR #4168).
05p,14mar95,caf  restored mips resident rom support (SPR #3856).
05o,18jan95,tmk  Added MC68060 case for HW_FP
06c,25may95,yao  changed to use _end for FREE_MEM_ADRS for PowerPC.
06b,12jan95,caf  added PPC floating point support.
06a,09jan95,yao  added PPC support.
05n,10dec94,kdl  Moved INCLUDE_POSIX_ALL to unincluded (SPR 3822).
05m,10dec94,caf  undid mod 05a, use _sdata for resident roms (SPR
#3856).
05l,09dec94,jag  Added INCLUDE_MIB2_AT.
05k,17nov94,kdl  Added INCLUDE_NFS_SERVER (excluded); removed TRON
references.
05j,13nov94,dzb  Moved INCLUDE_PING to excluded.
05i,11nov94,dzb  Added ZBUF_SOCK, TCP_DEBUG, and PING defines.
05h,11nov94,jag  cleanup of SNMP and MIB defines.
05g,04nov94,kdl  initial merge cleanup.
05b,16jun94,caf  defined INCLUDE_ELF for MIPS, updated copyright
notice.
04x,20jul94,ms   changed INCLUDE_HPPA_OUT to INCLUDE_SOM_COFF
05d,11apr94,jag  Removed conditions for definition of  NFS_GROUP and
NFS_USER
                 ID for SNMP demo support.
05c,18feb94,elh  (SNMP VERSION) moved INCLUDE_POSIX_ALL to false
section.
                 Added support for the mib2 library.
05f,25may94,kdl  (POSIX VERSION) removed erroneous NFS def's.
05e,23mar94,smb  (POSIX VERSION) removed PASSIVE_MODE
05d,15mar94,smb  renamed tEvtTask parameters.
05c,15feb94,smb  added define of WV_MODE
05b,12jan94,kdl  (POSIX VERSION) turned off instrumentation, added
                 INCLUDE_POSIX_ALL; added INCLUDE_POSIX_SIGNALS;
changed
                 INCLUDE_POSIX_MEM_MAN to INCLUDE_POSIX_MEM; added
                 NUM_SIGNAL_QUEUES.
*/

/*
DESCRIPTION
This header contains the parameters that define the default
configuration for VxWorks.
*/

#ifndef INCconfigAllh
#define INCconfigAllh

#include "smLib.h"
#include "vme.h"
#include "iv.h"

/******************************************************************************/
/*                                                                    
       */
/*                      INCLUDED SOFTWARE FACILITIES                  
       */
/*                                                                    
       */
/******************************************************************************/

#define INCLUDE_CTORS_DTORS
#define INCLUDE_CACHE_SUPPORT   /* include cache support package */
#define INCLUDE_CONSTANT_RDY_Q  /* constant insert time ready queue */
#define INCLUDE_ENV_VARS        /* unix compatable environment
variables */
#define INCLUDE_EXC_HANDLING    /* include basic exception handling */
#define INCLUDE_EXC_SHOW        /* include exception show routines */
#define INCLUDE_EXC_TASK        /* miscelaneous support task */
#define INCLUDE_FLOATING_POINT  /* floating point I/O */
#define INCLUDE_FORMATTED_IO    /* formatted I/O */
#define INCLUDE_GCC_FP          /* gcc floating point support
libraries */
#define INCLUDE_IO_SYSTEM       /* include I/O system */
#define INCLUDE_LOGGING         /* logTask logging facility */
#define INCLUDE_MEM_MGR_FULL    /* full featured memory manager */
#define INCLUDE_MSG_Q           /* include message queues */
#define INCLUDE_NETWORK         /* network subsystem code */
#define INCLUDE_PIPES           /* pipe driver */
#define INCLUDE_SELECT          /* select() facility */
#define INCLUDE_SEM_BINARY      /* include binary semaphores */
#define INCLUDE_SEM_MUTEX       /* include mutex semaphores */
#define INCLUDE_SEM_COUNTING    /* include counting semaphores */
#define INCLUDE_SIGNALS         /* software signal library */
#define INCLUDE_STDIO           /* standard I/O */
#define INCLUDE_TASK_HOOKS      /* include kernel callouts */
#define INCLUDE_TASK_VARS       /* task variable package */
#define INCLUDE_TIMEX           /* timexLib for exec timing */
#define INCLUDE_TTY_DEV         /* attach serial drivers */
#define INCLUDE_VXEVENTS        /* include VxWorks events */
#define INCLUDE_WATCHDOGS       /* include watchdogs */
#define INCLUDE_WDB             /* WDB debug agent */
#define INCLUDE_ANSI_ALL        /* includes complete ANSI C library
functions */
#define INCLUDE_ANSI_ASSERT     /* ANSI-C assert library functionality
*/
#define INCLUDE_ANSI_CTYPE      /* ANSI-C ctype library functionality
*/
#define INCLUDE_ANSI_LOCALE     /* ANSI-C locale library functionality
*/
#define INCLUDE_ANSI_MATH       /* ANSI-C math library functionality
*/
#define INCLUDE_ANSI_STDIO      /* ANSI-C stdio library functionality
*/
#define INCLUDE_ANSI_STDLIB     /* ANSI-C stdlib library functionality
*/
#define INCLUDE_ANSI_STRING     /* ANSI-C string library functionality
*/
#define INCLUDE_ANSI_TIME       /* ANSI-C time library functionality
*/

/* Toolchain specific included software facilities */
/* The following is for the benefit of the project facility */
#define INCLUDE_ALL_INTRINSICS

#ifdef INCLUDE_ALL_INTRINSICS
#ifdef _ARCH_SUPPORTS_GCC
#define INCLUDE_GNU_INTRINSICS
#endif
#ifdef _ARCH_SUPPORTS_DCC
#define INCLUDE_DIAB_INTRINSICS
#endif
#endif

/* CPU-SPECIFIC INCLUDED SOFTWARE FACILITIES */

/* include support for possibly existing floating point coprocessor */

#if     (CPU==MC68020 || CPU==MC68040 || CPU==MC68060 || CPU==CPU32)
#define INCLUDE_MC68881         /* MC68881/2 (68040) floating pt
coprocessor */
#define INCLUDE_HW_FP           /* potential hardware fp support */
#endif  /* CPU==MC68020 || CPU==MC68040 || CPU==MC68060 || CPU==CPU32
*/

#if     (CPU_FAMILY == SPARC) && defined(INCLUDE_FLOATING_POINT)
#define INCLUDE_SPARC_FPU       /* SPARC Floating-Point Unit */
#define INCLUDE_HW_FP           /* potential hardware fp support */
#endif  /* CPU_FAMILY == SPARC */

#if     (CPU_FAMILY==MIPS)
#define INCLUDE_R3010           /* R3010 float point co-processor */
#define INCLUDE_HW_FP           /* potential hardware fp support */
#endif  /* CPU_FAMILY==MIPS */

#if     ((CPU_FAMILY==PPC) && (CPU!=PPC403) && (CPU!=PPC405) &&
(CPU!=PPC440) \
        && (CPU!=PPCEC603) && (CPU!=PPC860))
#define INCLUDE_PPC_FPU         /* PowerPC floating point unit */
#define INCLUDE_HW_FP           /* potential hardware fp support */
#endif  /* (CPU_FAMILY==PPC) && (CPU!=PPC4xx) && (CPU!=PPCEC603) &&
(CPU!=PPC860) */

#if     (CPU==I960KB)
#define INCLUDE_HW_FP           /* potential hardware fp support */
#endif  /* I960KB */

#if     (CPU_FAMILY==I80X86)
#define INCLUDE_I80387          /* I80387 float point co-processor */
#define INCLUDE_HW_FP           /* potential hardware fp support */
#endif  /* CPU_FAMILY==I80X86 */

#if     (CPU_FAMILY==SH)
#if     (CPU==SH7750)
#define INCLUDE_HW_FP
#else
#define INCLUDE_SW_FP
#endif  /* CPU==SH7750 */
#endif  /* CPU_FAMILY==SH */

#if     (CPU_FAMILY==ARM)
#define INCLUDE_SW_FP
#endif  /* CPU_FAMILY==ARM */

#if     (CPU_FAMILY==SIMHPPA)
#define INCLUDE_HW_FP           /* potential hardware fp support */
#endif  /* SIMHPPA */

/* define appropriate object module format for a given architecture */

#if     ((CPU_FAMILY==MIPS) || (CPU_FAMILY==PPC) || (CPU_FAMILY==SH)
|| \
         (CPU_FAMILY==SIMSPARCSOLARIS) || (CPU_FAMILY==COLDFIRE) || \
         (CPU_FAMILY==I80X86) || (CPU_FAMILY==ARM))
#define INCLUDE_ELF             /* ELF object modules */
#else
#if     ((CPU_FAMILY==I960) || (CPU_FAMILY==AM29XXX)) 
#define INCLUDE_COFF            /* COFF object modules */
#else
#if     (CPU_FAMILY==SIMHPPA)
#define INCLUDE_SOM_COFF
#else   /* default */
#if     (CPU_FAMILY==SIMNT)
#define INCLUDE_PECOFF
#else   /* default */
#define INCLUDE_AOUT            /* a.out object modules */
#endif
#endif
#endif
#endif

/******************************************************************************/
/*                                                                    
       */
/*                          EXCLUDED FACILITIES                       
       */
/*                                                                    
       */
/******************************************************************************/

#if FALSE

#define INCLUDE_CODETEST        /* CodeTEST target utilities library
*/
#define INCLUDE_CPLUS           /* include C++ support */
#define INCLUDE_CPLUS_IOSTREAMS /* include basic iostreams classes */
#define INCLUDE_CPLUS_STL       /* include Standard Template Library
core */
#define INCLUDE_CPLUS_STRING      /* include string class */
#define INCLUDE_CPLUS_STRING_IO   /* include i/o for string class */
#define INCLUDE_CPLUS_COMPLEX     /* include complex number class */
#define INCLUDE_CPLUS_COMPLEX_IO  /* include i/o for complex number
class */
#define INCLUDE_CPLUS_IOSTREAMS_FULL  /* include all of iostreams */
#define INCLUDE_CONFIGURATION_5_2 /* pre-tornado tools */
#define INCLUDE_DEBUG           /* pre-tornado debugging */
#define INCLUDE_DEMO            /* include simple demo instead of
shell */

#define INCLUDE_DISK_UTIL       /* ls, cd, mkdir, xcopy, etc. */
#define INCLUDE_DOSFS           /* usrDosFsOld.c wrapper layer */
#define INCLUDE_DOSFS_MAIN      /* dosFsLib (2) */
#define INCLUDE_DOSFS_FAT       /* dosFs FAT12/16/32 FAT table handler
*/
#define INCLUDE_DOSFS_DIR_VFAT  /* Microsoft VFAT dirent handler */
#define INCLUDE_DOSFS_DIR_FIXED /* 8.3 & VxLongNames directory handler
*/
#define INCLUDE_DOSFS_FMT       /* dosFs2 file system formatting
module */
#define INCLUDE_DOSFS_CHKDSK    /* file system integrity checking */
#define INCLUDE_CBIO            /* CBIO API module */
#define INCLUDE_DISK_CACHE      /* CBIO API disk caching layer */
#define INCLUDE_DISK_PART       /* disk partition handling code,
fdisk... */
#define INCLUDE_DISK_UTIL       /* ls, cd, mkdir, xcopy, etc */
#define INCLUDE_TAR             /* tar utility */
#define INCLUDE_RAM_DISK        /* CBIO API ram disk driver */

#define INCLUDE_HTML            /* include HTML support */
#define INCLUDE_JAVA            /* Java virtual machine */
#define INCLUDE_LSTLIB          /* include linked list library
lstLib.c */
#define INCLUDE_SOUND       /* include support for sampled audio data
*/
#define INCLUDE_LOADER          /* object module loading */

/* INCLUDE_MMU_BASIC is defined by many bsp's in config.h. If
INCLUDE_MMU_FULL
 * is defined in configAll.h and INCLUDE_MMU_BASIC is defined in
config.h,
 * then INCLUDE_MMU_FULL will take precedence.
 */

#define INCLUDE_MMU_BASIC       /* bundled mmu support */
#define INCLUDE_MMU_FULL        /* unbundled mmu support */

#define INCLUDE_SYM_TBL_SYNC    /* synchronize host and target symbol
tables */

#define INCLUDE_POSIX_AIO       /* POSIX async I/O support */
#define INCLUDE_POSIX_AIO_SYSDRV/* POSIX async I/O system driver */
#define INCLUDE_POSIX_FTRUNC    /* POSIX ftruncate routine */
#define INCLUDE_POSIX_MEM       /* POSIX memory locking */
#define INCLUDE_POSIX_MQ        /* POSIX message queue support */
#define INCLUDE_POSIX_PTHREADS  /* POSIX pthreads support */
#define INCLUDE_POSIX_SCHED     /* POSIX scheduling */
#define INCLUDE_POSIX_SEM       /* POSIX semaphores */
#define INCLUDE_POSIX_SIGNALS   /* POSIX queued signals */
#define INCLUDE_POSIX_TIMERS    /* POSIX timers */
#define INCLUDE_PROTECT_TEXT    /* text segment write protection
(unbundled) */
#define INCLUDE_PROTECT_VEC_TABLE /* vector table write protection
(unbundled)*/
#define INCLUDE_RAMDRV          /* ram disk driver */
#define INCLUDE_RAWFS           /* rawFs file system */
#define INCLUDE_RBUFF           /* ring of buffers library */
#define INCLUDE_RT11FS          /* rt11Fs file system */
#define INCLUDE_SECURITY        /* shell security for network access
*/
#define INCLUDE_SHELL           /* interactive c-expression
interpreter */
#define INCLUDE_SHOW_ROUTINES   /* show routines for system
facilities*/
#define INCLUDE_SM_OBJ          /* shared memory objects (unbundled)
*/
#define INCLUDE_SPY             /* spyLib for task monitoring */
#define INCLUDE_STANDALONE_SYM_TBL /* compiled-in symbol table */
#define INCLUDE_STARTUP_SCRIPT  /* execute start-up script */
#define INCLUDE_STAT_SYM_TBL    /* create user-readable error status
*/
#define INCLUDE_SW_FP           /* software floating point emulation
*/
#define INCLUDE_SYM_TBL         /* symbol table package */
#define INCLUDE_WINDML          /* include WindML multimedia Library
support */
#define INCLUDE_UNLOADER        /* object module unloading */
#define INCLUDE_WILLOWS_RT      /* include Willows RT library */
#define INCLUDE_WDB_TSFS        /* target-server file system */
#define INCLUDE_VXFUSION        /* WindMP (unbundled) */
#define INCLUDE_WINDVIEW        /* WindView target facilities */
#define INCLUDE_WVUPLOAD_ALL    /* include all Windview upload-path
types */
#define INCLUDE_WVUPLOAD_FILE   /* include file Windview upload-path
*/
#define INCLUDE_WVUPLOAD_SOCK   /* include socket Windview upload-path
*/
#define INCLUDE_WVUPLOAD_TSFSSOCK /* include tsfs sock Windview
upload-path */

#define INCLUDE_ANSI_5_0        /* include only version 5.0 ANSI
support */
#define INCLUDE_DELETE_5_0      /* define delete() function as in
VxWorks 5.0 */

#define INCLUDE_TSFS_BOOT       /* Boot using Target Server File
System */
#define INCLUDE_TSFS_BOOT_VIO_CONSOLE   /* use tgtsvr Console for
TSFS_BOOT */

#endif  /* FALSE */

/******************************************************************************/
/*                                                                    
       */
/*                  KERNEL SOFTWARE CONFIGURATION                     
       */
/*                                                                    
       */
/******************************************************************************/

#define USER_I_CACHE_MODE       CACHE_WRITETHROUGH  /* default mode */
#define USER_D_CACHE_MODE       CACHE_WRITETHROUGH  /* default mode */
#define USER_I_CACHE_ENABLE                         /* undef to leave
disabled*/
#define USER_D_CACHE_ENABLE                         /* undef to leave
disabled*/
#define USER_B_CACHE_ENABLE                         /* undef to leave
disabled*/
#define USER_I_MMU_ENABLE                           /* undef to leave
disabled*/
#define USER_D_MMU_ENABLE                           /* undef to leave
disabled*/

#define SYM_TBL_HASH_SIZE_LOG2  8       /* 256 entry hash table symbol
table */
#define STAT_TBL_HASH_SIZE_LOG2 6       /* 64 entry hash table for
status */
#define MQ_HASH_SIZE            0       /* POSIX message queue hash
table size
                                         * 0 = default */
#define NUM_SIGNAL_QUEUES       16      /* POSIX queued signal count
*/

#if CPU==SIMNT
#define FREE_RAM_ADRS           simMemBlock
#else
#define FREE_RAM_ADRS           (end)   /* start right after bss of
VxWorks */
#endif

/* I/O system parameters */

#define SYS_CLK_RATE            60      /* default system clock rate
*/
#define NUM_DRIVERS             20      /* max 20 drivers in drvTable
*/
#define NUM_FILES               50      /* max 50 files open
simultaneously */
#define NUM_DOSFS_FILES         20      /* max 20 dosFs files open */
#define NUM_RAWFS_FILES         5       /* max 5  rawFs files open */
#define NUM_RT11FS_FILES        5       /* max 5  rt11Fs files open */
#define MAX_LOG_MSGS            50      /* max 50 log msgs */

#define NUM_TTY                 2       /* number of tty channels */
#define CONSOLE_TTY             0       /* console channel */

#define CONSOLE_BAUD_RATE       9600    /* console baud rate */

#ifdef  INCLUDE_SLIP
#define SLIP_TTY                1       /* serial line IP channel */
#endif  /* INCLUDE_SLIP */

#define MAX_LIO_CALLS           0       /* max outstanding lio calls
0=default */
#define MAX_AIO_SYS_TASKS       0       /* max aio system tasks, 0 =
default */
#define AIO_TASK_PRIORITY       0       /* aio system tasks prior, 0 =
default */
#define AIO_TASK_STACK_SIZE     0       /* aio tasks stack size, 0 =
default */

/* kernel and system task parameters by architecture */

#if     CPU_FAMILY==MC680X0
#define INT_LOCK_LEVEL          0x7     /* 68k interrupt disable mask
*/
#define ROOT_STACK_SIZE         10000   /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
*/
#define TRAP_DEBUG              2       /* trap 2 - breakpoint trap */
#define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
#endif  /* CPU_FAMILY==MC680X0 */

#if     CPU_FAMILY==COLDFIRE
#define INT_LOCK_LEVEL          0x7     /* 68k interrupt disable mask
*/
#define ROOT_STACK_SIZE         10000   /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
*/
#define TRAP_DEBUG              2       /* trap 2 - breakpoint trap */
#define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
#endif  /* CPU_FAMILY==COLDFIRE */

#if     CPU_FAMILY==SPARC
#define INT_LOCK_LEVEL          15      /* SPARC interrupt disable
level */
#define ROOT_STACK_SIZE         10000   /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        50000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          10000   /* size of ISR stack, in bytes
*/
#define VEC_BASE                (LOCAL_MEM_LOCAL_ADRS + 0x1000)
#define VEC_BASE_ADRS           ((char *) VEC_BASE)
#endif  /* CPU_FAMILY==SPARC */

#if CPU_FAMILY==SIMNT || CPU_FAMILY==SIMSPARCSUNOS  ||
CPU_FAMILY==SIMHPPA || CPU_FAMILY==SIMSPARCSOLARIS
#define INT_LOCK_LEVEL          0x1     /* interrupt disable mask */
#define ROOT_STACK_SIZE         20000   /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        50000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          50000   /* size of ISR stack, in bytes
*/
#define VEC_BASE_ADRS           0       /* dummy */
#endif  /* CPU_FAMILY ==SIMNT || CPU_FAMILY==SIMSPARCSUNOS  ||
CPU_FAMILY==SIMHPPA || CPU_FAMILY==SIMSPARCSOLARIS */

#if     CPU_FAMILY==I960
#define INT_LOCK_LEVEL          0x1f    /* i960 interrupt disable mask
*/
#define ROOT_STACK_SIZE         20000   /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        40000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
*/
#define TRAP_DEBUG              0       /* n/a for the 80960 */
#define VEC_BASE_ADRS           NONE    /* base register not
reconfigurable */
#endif  /* CPU_FAMILY==I960 */

#if     CPU_FAMILY==MIPS
#define INT_LOCK_LEVEL          0x1     /* R3K interrupt disable mask
*/
#define ROOT_STACK_SIZE         (20000) /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        (20000) /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          (0x2000)/* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          (5000)  /* size of ISR stack, in bytes
*/
#define VEC_BASE_ADRS           ((char *) 0x0)  /* meaningless in R3k
land */
#define VME_VECTORED            FALSE   /* use vectored VME interrupts
*/
#define TRAP_DEBUG              0       /* trap 0 - breakpoint trap */
#endif  /* CPU_FAMILY==MIPS */

#if     CPU_FAMILY==PPC
#define INT_LOCK_LEVEL          0x0     /* not used */
#define BOOT_CMD_STACK_SIZE     (11000) /* size of boot cmd stack, in
bytes */
#define ROOT_STACK_SIZE         (24000) /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        (20000) /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          (5000)  /* size of ISR stack, in bytes
*/
#define VEC_BASE_ADRS           ((char *) 0x0)
#endif  /* CPU_FAMILY==PPC */

#if     CPU_FAMILY==I80X86
#define INT_LOCK_LEVEL          0x0     /* 80x86 interrupt disable
mask */
#define ROOT_STACK_SIZE         10000   /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          1000    /* size of ISR stack, in bytes
*/
#define TRAP_DEBUG              0       /* not used */
#define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
#endif  /* CPU_FAMILY==I80X86 */

#if     CPU_FAMILY==AM29XXX
#define INT_LOCK_LEVEL          0x0001  /* 29k all interrupts disable
mask */
#define ROOT_STACK_SIZE         10000   /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        40000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          10000   /* size of ISR stack, in bytes
*/
#define TRAP_DEBUG              15      /* trap 2 - breakpoint trap */
#define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
#endif  /* CPU_FAMILY==AM29XXX */

#if     CPU_FAMILY==SH
#define INT_LOCK_LEVEL          15
#define ROOT_STACK_SIZE         10000
#define SHELL_STACK_SIZE        10000   /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x1000  /* size of WDB agents stack,
in bytes */
#define ISR_STACK_SIZE          1000
#define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
#endif  /* CPU_FAMILY==SH */

#if     CPU_FAMILY==ARM
#define INT_LOCK_LEVEL          0       /* interrupt disable mask -
unused */
#define ROOT_STACK_SIZE         0x4000  /* size of root's stack, in
bytes */
#define SHELL_STACK_SIZE        0x10000 /* size of shell's stack, in
bytes */
#define WDB_STACK_SIZE          0x2000  /* size of WDB agents stack,
in bytes */
#define TRAP_DEBUG              0       /* not used */
#define VEC_BASE_ADRS           ((char *) LOCAL_MEM_LOCAL_ADRS)
/*
 * NOTE: ISR_STACK_SIZE defined in config.h, not here - BSP interrupt
 *       structure dependent
 */
#endif  /* CPU_FAMILY==ARM */

#ifndef BOOT_CMD_STACK_SIZE
#define BOOT_CMD_STACK_SIZE     7000
#endif  /* BOOT_CMD_STACK_SIZE */

/* WDB debug agent configuration */

#ifdef  INCLUDE_WDB

/* optional agent facilities */

#define INCLUDE_WDB_BANNER              /* print banner after agent
starts */
#define INCLUDE_WDB_VIO                 /* virtual I/O support */
#define INCLUDE_WDB_TTY_TEST            /* test serial line
communcation */
#define INCLUDE_WDB_START_NOTIFY        /* notify the host of task
creation */
#define INCLUDE_WDB_USER_EVENT          /* user events handling */

/* core agent facilities - do not remove */

#define INCLUDE_WDB_CTXT                /* context control */
#define INCLUDE_WDB_FUNC_CALL           /* spawn function as separate
task */
#define INCLUDE_WDB_DIRECT_CALL         /* call function in agents
context */
#define INCLUDE_WDB_EVENTS              /* host async event
notification */
#define INCLUDE_WDB_GOPHER              /* gopher info gathering */
#define INCLUDE_WDB_BP                  /* breakpoint support */
#define INCLUDE_WDB_EXC_NOTIFY          /* notify host of exceptions
*/
#define INCLUDE_WDB_EXIT_NOTIFY         /* notify the host of task
exit */
#define INCLUDE_WDB_REG                 /* get/set hardware registers
*/
#define INCLUDE_WDB_EVENTPOINTS         /* eventpoints handling */
#define INCLUDE_WDB_MEM                 /* optional memory services */

/* agent mode */

#define WDB_MODE        WDB_MODE_DUAL   /* WDB_MODE_[DUAL|TASK|EXTERN]
*/

/* agent communication paths */

#define WDB_COMM_NETWORK        0       /* vxWorks network      - task
mode */
#define WDB_COMM_SERIAL         1       /* raw serial           -
bimodal   */
#define WDB_COMM_TYCODRV_5_2    2       /* older serial driver  - task
mode */
#define WDB_COMM_ULIP           3       /* vxSim packet device  -
bimodal   */
#define WDB_COMM_NETROM         4       /* netrom packet device -
bimodal   */
#define WDB_COMM_CUSTOM         5       /* custom packet device -
bimodal   */
#define WDB_COMM_END            6       /* END packet device    -
bimodal */
#define WDB_COMM_PIPE           7       /* vxSim pipe device    -
bimodal   */
#define WDB_COMM_VTMD           8       /* TMD packet device    -
bimodal   */

/* communication path configuration */

#ifndef WDB_COMM_TYPE
#define WDB_COMM_TYPE WDB_COMM_SERIAL   /* default path is the network
*/
#endif

#ifndef WDB_TTY_CHANNEL
#define WDB_TTY_CHANNEL         1       /* default Sio SERIAL channel
*/
#endif

#ifndef WDB_TTY_DEV_NAME
#define WDB_TTY_DEV_NAME    "/tyCo/1"   /* default TYCODRV_5_2 device
name */
#endif

#ifndef WDB_TTY_BAUD
#define WDB_TTY_BAUD            9600    /* default baud rate */
#endif

#ifndef WDB_ULIP_DEV
#define WDB_ULIP_DEV    "/dev/ulip14"   /* default ULIP packet device
*/
#endif

#define WDB_NETROM_TYPE         400     /* default is old 400 series
*/
#define WDB_NETROM_WIDTH        1       /* width of a ROM word. This
macro
                                         * is not used for the 500
series. */
#define WDB_NETROM_INDEX        0       /* index into word of pod zero
*/
#define WDB_NETROM_NUM_ACCESS   1       /* of pod zero per byte read
*/
#define WDB_NETROM_ROMSIZE      ROM_SIZE /* size of a single ROM. If
your
                                         * board has N ROMs, this
definition
                                         * must be divided by N to be
right */
#define WDB_NETROM_POLL_DELAY   2       /* # clock ticks to poll for
input */

/* miscelaneous agent constants */

#define WDB_MTU                 1500    /* max RPC message size */
#define WDB_POOL_SIZE           ((sysMemTop() - FREE_RAM_ADRS)/16) /*
memory pool for host tools */
#define WDB_SPAWN_STACK_SIZE    0x5000  /* default stack size of
spawned task */

#endif  /* INCLUDE_WDB */

/******************************************************************************/
/*                                                                    
       */
/*                   "GENERIC" BOARD CONFIGURATION                    
       */
/*                                                                    
       */
/******************************************************************************/

/* device controller I/O addresses when included */

#define IO_ADRS_EI      ((char *) 0x000fff00)   /* 32A,32D i82596CA
Ethernet */

/******************************************************************************/
/*                                                                    
       */
/*                   "MISCELLANEOUS" CONSTANTS                        
       */
/*                                                                    
       */
/******************************************************************************/

/* shared memory objects parameters (unbundled) */

#define SM_OBJ_MAX_TASK         40      /* max # of tasks using smObj
*/
#define SM_OBJ_MAX_SEM          60      /* max # of shared semaphores
*/
#define SM_OBJ_MAX_MSG_Q        10      /* max # of shared message
queues */
#define SM_OBJ_MAX_MEM_PART     4       /* max # of shared memory
partitions */
#define SM_OBJ_MAX_NAME         100     /* max # of shared objects
names */
#define SM_OBJ_MAX_TRIES        5000    /* max # of tries to obtain
lock */

/* shared memory network parameters  - defaults to values
DEFAULT_PKTS_SIZE
 * and DEFAULT_CPUS_MAX in smPktLib.h respectively
 */

#define SM_PKTS_SIZE            0       /* shared memory packet size
*/
#define SM_CPUS_MAX             0       /* max # of cpus for shared
network */

/* low memory layout */

#if     (CPU_FAMILY == I80X86)
#define GDT_BASE_OFFSET         0x800
#define SM_ANCHOR_OFFSET        0x1100
#define BOOT_LINE_OFFSET        0x1200
#define EXC_MSG_OFFSET          0x1300
#elif   (CPU_FAMILY == PPC)
#define SM_ANCHOR_OFFSET        0x4100
#define BOOT_LINE_OFFSET        0x4200
#define EXC_MSG_OFFSET          0x4300
#elif   (CPU==SH7750 || CPU==SH7729 || CPU==SH7700)
#define SM_ANCHOR_OFFSET        0x1600  /* not used for SDRAM config.
*/
#define BOOT_LINE_OFFSET        0x1700
#define EXC_MSG_OFFSET          0x1800
#else
#define SM_ANCHOR_OFFSET        0x600
#define BOOT_LINE_OFFSET        0x700
#define EXC_MSG_OFFSET          0x800
#endif  /* (CPU_FAMILY == I80X86) */

/* The backplane driver onboard anchor at the following address */

#define SM_ANCHOR_ADRS  ((char *)
(LOCAL_MEM_LOCAL_ADRS+SM_ANCHOR_OFFSET))

/* The bootroms put the boot line at the following address */

#define BOOT_LINE_ADRS  ((char *)
(LOCAL_MEM_LOCAL_ADRS+BOOT_LINE_OFFSET))
#define BOOT_LINE_SIZE  255     /* use 255 bytes for bootline */

/* The boot line is stored in non-volatile RAM at the following offset
*/

#define NV_BOOT_OFFSET  0       /* store the boot line at start of
NVRAM */

/* Messages from exceptions during exceptions go at the following
address */

#define EXC_MSG_ADRS    ((char *)
(LOCAL_MEM_LOCAL_ADRS+EXC_MSG_OFFSET))

/* Backplane H/W support */

#define SM_TAS_TYPE     SM_TAS_HARD     /* hardware supports
test-and-set */

/* Resident ROMs constants */

#if     ((CPU_FAMILY==I960) || (CPU_FAMILY==ARM))
#define STACK_SAVE      512             /* maximum stack used to
preserve */
#else   /* sparc or others */
#if     ((CPU_FAMILY==SPARC) || (CPU_FAMILY==PPC))
#define STACK_SAVE      0x1000
#else   /* all other architecutes */
#define STACK_SAVE      0x40            /* maximum stack used to
preserve */
#endif                                  /* mips cpp no elif */
#endif

#if     (CPU_FAMILY==SPARC)
#define RESERVED        0x2000          /* vector table base plus
table size */
#else   /* 68000 or others */
#if     (CPU==MC68000)
#define RESERVED        0x400           /* avoid zeroing MC68302
vector table */
#else
#if     (CPU_FAMILY == PPC)
#define RESERVED        0x4400          /* avoid zeroing EXC_MSG */
#else   /* all other architectures */
#define RESERVED        0
#endif
#endif                                  /* mips cpp no elif */
#endif

#if     ((CPU_FAMILY == MIPS) || (CPU_FAMILY == PPC))
#define STACK_RESIDENT  RAM_DST_ADRS
#else
#define STACK_RESIDENT  _sdata
#endif

#if     (_STACK_DIR == _STACK_GROWS_DOWN)

#ifdef  ROM_RESIDENT
#define STACK_ADRS      STACK_RESIDENT
#else
#define STACK_ADRS      _romInit
#endif  /* ROM_RESIDENT */

#else   /* _STACK_DIR == _STACK_GROWS_UP */

#ifdef  ROM_RESIDENT
#define STACK_ADRS      (STACK_RESIDENT-STACK_SAVE)
#else
#define STACK_ADRS      (_romInit-STACK_SAVE)
#endif  /*  ROM_RESIDENT */

#endif  /* _STACK_DIR == _STACK_GROWS_UP */

/* Default Boot Parameters */

#define HOST_NAME_DEFAULT       "bootHost"      /* host name */
#define TARGET_NAME_DEFAULT     "vxTarget"      /* target name (tn) */
#define HOST_USER_DEFAULT       "target"        /* user (u) */
#define HOST_PASSWORD_DEFAULT   ""              /* password */
#define SCRIPT_DEFAULT          ""              /* startup script (s)
*/
#define OTHER_DEFAULT           ""              /* other (o) */

/* Login security initial user name and password.
 * Use vxencrypt on host to find encrypted password.
 * Default password provided here is "password".
 */

#ifdef  INCLUDE_SECURITY
#define LOGIN_USER_NAME         "target"
#define LOGIN_PASSWORD          "RcQbRbzRyc"    /* "password" */
#endif  /* INCLUDE_SECURITY */

/* install environment variable task create/delete hooks */

#ifdef  INCLUDE_ENV_VARS
#define ENV_VAR_USE_HOOKS       TRUE
#endif  /* INCLUDE_ENV_VARS */

/*
 * default page size for MMU is 8k.
 * 68040 will also work with 4k page size
 * powerPC is only 8k
 */

#if     ((CPU_FAMILY == PPC) || (CPU_FAMILY == ARM) || (CPU_FAMILY ==
SH) || \
         (CPU_FAMILY == I80X86))
#   define VM_PAGE_SIZE         4096
#else
#   define VM_PAGE_SIZE         8192
#endif  /* (CPU_FAMILY == PPC || ARM || SH || I80X86) */

/* vxWorks Network Configuration */
#ifdef INCLUDE_NETWORK
/******************************************************************************/
/*                                                                    
       */
/*                         INCLUDED NETWORK FACILITIES                
       */
/*                                                                    
       */
/******************************************************************************/
#define INCLUDE_BSD_SOCKET      /* include the BSD socket library */
#define INCLUDE_ICMP            /* include icmp code */
#define INCLUDE_IGMP            /* include igmp code */
#define INCLUDE_UDP             /* include udp code */
#define INCLUDE_TCP             /* include tcp code */
#define INCLUDE_NET_DRV        /* Newly added  -Mahesh */
#define INCLUDE_NET_INIT        /* network subsystem initialization */
#define INCLUDE_NET_REM_IO      /* network remote file i/o driver */

#define INCLUDE_BOOTP           /* bootp */
#define INCLUDE_FTP             /* ftp client */
#define INCLUDE_FTP_SERVER      /* ftp Server */

/* INCLUDED NETWORK DRIVERS */
#define INCLUDE_FEI
#define FEI_POOL_ADRS NONE

/******************************************************************************/
/*                                                                    
       */
/*                         EXCLUDED NETWORK FACILITIES                
       */
/*                                                                    
       */
/******************************************************************************/
#if FALSE
#define INCLUDE_ARP             /* user interface to ARP table */
#define INCLUDE_BSD             /* netif driver support */
#define INCLUDE_DHCPC           /* DHCP client */
#define INCLUDE_DHCPS           /* DHCP server */
#define INCLUDE_DHCPR           /* DHCP relay agent */
#define INCLUDE_DNS_DEBUG       /* DNS resolver debug mode */
#define INCLUDE_DNS_RESOLVER    /* DNS resolver */
#define INCLUDE_IP_FILTER       /* IP filter library */
#define INCLUDE_FTP_SERVER      /* ftp server */
#define INCLUDE_FTPD_SECURITY   /* password security for ftp sessions
*/
#define INCLUDE_HTTP            /* http server (Wind Web Server) */
#define INCLUDE_MCAST_ROUTING   /* include multicast routing in the
code */
#define INCLUDE_MIB2_ALL        /* All of MIB 2 */
#define INCLUDE_MIB2_SYSTEM     /* the system group */
#define INCLUDE_MIB2_TCP        /* the TCP group */
#define INCLUDE_MIB2_ICMP       /* the ICMP group */
#define INCLUDE_MIB2_UDP        /* the UDP group */
#define INCLUDE_MIB2_IF         /* the interfaces group */
#define INCLUDE_MIB2_AT         /* the AT group */
#define INCLUDE_MIB2_IP         /* the IP group */
#define INCLUDE_NET_SHOW        /* network info and status facilities
*/
#define INCLUDE_NET_SYM_TBL     /* load symbol table from network */
#define INCLUDE_NFS             /* nfs package */
#define INCLUDE_NFS_SERVER      /* nfs server */
#define INCLUDE_NFS_MOUNT_ALL   /* automatically mount all NFS file
systems */
#define INCLUDE_OSPF            /* open shortest path first routing
protocol */
#define INCLUDE_PING            /* ping() utility */
#define INCLUDE_POSIX_ALL       /* include all available POSIX
functions */
#define INCLUDE_PPP             /* include Point-to-Point Procotol */
#define INCLUDE_PROXY_CLIENT    /* proxy arp client (Slave Board) */
#define INCLUDE_PROXY_DEFAULT_ADDR /* Use ethernet addr to generate bp
addrs */
#define INCLUDE_PROXY_SERVER    /* proxy arp server (Master Board) */
#define INCLUDE_RIP             /* Routing Information Protocol RIP */
#define INCLUDE_RLOGIN          /* remote login */
#define INCLUDE_ROUTE_SOCK      /* include routing socket interface */
#define INCLUDE_RPC             /* rpc package */
#define INCLUDE_SLIP            /* include serial line interface */
#define INCLUDE_SM_NET          /* include backplane net interface */
#define INCLUDE_SM_SEQ_ADDR     /* shared memory network auto address
setup */
#define INCLUDE_SNMPD           /* SNMP Agent */
#define INCLUDE_SNMPD_DEBUG     /* SNMP Agent debugging */
#define INCLUDE_SNTPC           /* SNTP client */
#define INCLUDE_SNTPS           /* SNTP server */
#define INCLUDE_TCP_DEBUG       /* TCP debug facility */
#define INCLUDE_TELNET          /* telnet-style remote login */
#define INCLUDE_TFTP_SERVER     /* tftp server */
#define INCLUDE_ZBUF_SOCK       /* zbuf socket interface */

#define DEFAULT_STREAMS_SOCKET     /* default to Streams socket for
AF_INET */
/* network drivers */
#define INCLUDE_LN              /* include AMD LANCE interface */
#define INCLUDE_LNSGI           /* include AMD LANCE interface for SGI
VIP10 */
#define INCLUDE_MED             /* include Matrix network interface*/
#define INCLUDE_NIC             /* include National NIC interface */
#endif  /* FALSE */

#endif  /* INCLUDE_NETWORK */

#ifdef INCLUDE_BSD_SOCKET
    /*
     * By default, set the sockets API for compatibility with BSD 4.3
     * applications.
     */
#define BSD43_COMPATIBLE
#endif

#ifdef INCLUDE_NFS
/* Default NFS parameters - constants may be changed here, variables
 * may be changed in usrConfig.c at the point where NFS is included.
 */

#define NFS_USER_ID             2001            /* dummy nfs user id
*/
#define NFS_GROUP_ID            100             /* dummy nfs user
group id */
#endif /* INCLUDE_NFS */

#if defined (INCLUDE_NFS_SERVER) || defined (INCLUDE_NFS)
#define NFS_MAXPATH             255             /* max. file path
length */
#endif

/* SNMP configuration parameters */

#define SNMP_TRACE_LEVEL            0    /* Must be >= 0 and <= 3 with
higher */
                                         /* values giving more info
and 0     */
                                         /* giving no info            
       */

#define PPP_TTY                         1       /* default PPP serial
channel */
#define PPP_OPTIONS_STRUCT                      /* use PPP options
macros */
#define PPP_OPTIONS_FILE                NULL    /* use PPP options
file */
#define PPP_CONNECT_DELAY               15      /* delay to establish
link */

#undef  INCLUDE_PPP_CRYPT                       /* include PPP crypt
support */

/* PPP options flags - set to 1 to turn on option */

#define PPP_OPT_NO_ALL                  0       /* Don't allow any
options */
#define PPP_OPT_PASSIVE_MODE            0       /* Set passive mode */
#define PPP_OPT_SILENT_MODE             0       /* Set silent mode */
#define PPP_OPT_DEFAULTROUTE            0       /* Add default route
*/
#define PPP_OPT_PROXYARP                0       /* Add proxy ARP entry
*/
#define PPP_OPT_IPCP_ACCEPT_LOCAL       0       /* Acpt peer's IP addr
for us */
#define PPP_OPT_IPCP_ACCEPT_REMOTE      0       /* Acpt peer's IP addr
for it */
#define PPP_OPT_NO_IP                   0       /* Disable IP addr
negot. */
#define PPP_OPT_NO_ACC                  0       /* Disable
addr/control compr */
#define PPP_OPT_NO_PC                   0       /* Disable proto field
compr */
#define PPP_OPT_NO_VJ                   0       /* Disable VJ
compression */
#define PPP_OPT_NO_VJCCOMP              0       /* Disable VJ conct-ID
compr */
#define PPP_OPT_NO_ASYNCMAP             0       /* Disable async map
negot. */
#define PPP_OPT_NO_MN                   0       /* Disable magic num
negot. */
#define PPP_OPT_NO_MRU                  0       /* Disable MRU
negotiation */
#define PPP_OPT_NO_PAP                  0       /* Don't allow PAP
auth */
#define PPP_OPT_NO_CHAP                 0       /* Don't allow CHAP
auth */
#define PPP_OPT_REQUIRE_PAP             0       /* Require PAP auth */
#define PPP_OPT_REQUIRE_CHAP            0       /* Require CHAP auth
*/
#define PPP_OPT_LOGIN                   0       /* Use login dbase for
PAP */
#define PPP_OPT_DEBUG                   0       /* Enable daemon debug
mode */
#define PPP_OPT_DRIVER_DEBUG            0       /* Enable driver debug
mode */

/* PPP options strings - set to desired string to turn on option */

#define PPP_STR_ASYNCMAP                NULL    /* desired async map
*/
#define PPP_STR_ESCAPE_CHARS            NULL    /* chars to escape on
xmits */
#define PPP_STR_VJ_MAX_SLOTS            NULL    /* max VJ compr header
slots */
#define PPP_STR_NETMASK                 NULL    /* netmask value */
#define PPP_STR_MRU                     NULL    /* MRU value for
negotiation */
#define PPP_STR_MTU                     NULL    /* MTU value for
negotiation */
#define PPP_STR_LCP_ECHO_FAILURE        NULL    /* max LCP echo
failures */
#define PPP_STR_LCP_ECHO_INTERVAL       NULL    /* time for LCP echo
requests */
#define PPP_STR_LCP_RESTART             NULL    /* timeout for LCP */
#define PPP_STR_LCP_MAX_TERMINATE       NULL    /* max LCP term-reqs
*/
#define PPP_STR_LCP_MAX_CONFIGURE       NULL    /* max LCP conf-reqs
*/
#define PPP_STR_LCP_MAX_FAILURE         NULL    /* max conf-naks for
LCP */
#define PPP_STR_IPCP_RESTART            NULL    /* timeout for IPCP */
#define PPP_STR_IPCP_MAX_TERMINATE      NULL    /* max IPCP term-reqs
*/
#define PPP_STR_IPCP_MAX_CONFIGURE      NULL    /* max IPCP conf-reqs
*/
#define PPP_STR_IPCP_MAX_FAILURE        NULL    /* max # conf-naks for
IPCP */
#define PPP_STR_LOCAL_AUTH_NAME         NULL    /* local name for auth
*/
#define PPP_STR_REMOTE_AUTH_NAME        NULL    /* remote name for
auth */
#define PPP_STR_PAP_FILE                NULL    /* PAP secrets file */
#define PPP_STR_PAP_USER_NAME           NULL    /* username for PAP
peer auth */
#define PPP_STR_PAP_PASSWD              NULL    /* password for PAP
peer auth */
#define PPP_STR_PAP_RESTART             NULL    /* timeout for PAP */
#define PPP_STR_PAP_MAX_AUTHREQ         NULL    /* max PAP auth-reqs
*/
#define PPP_STR_CHAP_FILE               NULL    /* CHAP secrets file
*/
#define PPP_STR_CHAP_RESTART            NULL    /* timeout for CHAP */
#define PPP_STR_CHAP_INTERVAL           NULL    /* CHAP rechallenge
interval */
#define PPP_STR_CHAP_MAX_CHALLENGE      NULL    /* max CHAP challenges
*/

/* BOOTP client parameters */

#ifdef INCLUDE_BOOTP
#define BOOTP_MAX_HDRSIZE       14    /* Maximum (link-level) Header
Size */
#define BOOTP_MAX_REQUESTS      3     /* BOOTP client transmit limit  
   */
#endif

/* DHCP client parameters */

#ifdef INCLUDE_DHCPC
#define DHCPC_SPORT             67    /* Port monitored by DHCP
servers. */
#define DHCPC_CPORT             68    /* Port monitored by DHCP
clients. */
#define DHCPC_MAX_LEASES        4     /* Max. number of simultaneous
leases */
#define DHCPC_OFFER_TIMEOUT     5     /* Seconds to wait for multiple
offers */
#define DHCPC_DEFAULT_LEASE     3600  /* Desired lease length in
seconds */
#define DHCPC_MIN_LEASE         30    /* Minimum allowable lease
length */
#define DHCPC_MAX_MSGSIZE       590   /* Allows minimum message on
Ethernet */
#endif

/* DHCP server parameters */

#ifdef INCLUDE_DHCPS
#define DHCPS_LEASE_HOOK        NULL   /* Name of required storage
routine */
#define DHCPS_ADDRESS_HOOK      NULL   /* Name of optional storage
routine */
#define DHCPS_DEFAULT_LEASE     3600   /* default lease length (secs).
*/
#define DHCPS_MAX_LEASE         3600   /* default value of max lease
(secs). */
#endif

/* DHCP server and relay agent parameters */

#if defined (INCLUDE_DHCPS) || defined (INCLUDE_DHCPR)
#define DHCP_MAX_HOPS           4       /* Hops before discard, up to
16. */
#define DHCPS_SPORT             67      /* Port monitored by DHCP
servers */
#define DHCPS_CPORT             68      /* Port monitored by DHCP
clients */
#define DHCPS_MAX_MSGSIZE       590    /* Allows minimum message on
Ethernet */
#endif

/* SNTP parameters */

#if defined (INCLUDE_SNTPC) || defined (INCLUDE_SNTPS)
#define SNTP_PORT 123

#ifdef INCLUDE_SNTPS
#define SNTPS_MODE SNTP_ACTIVE     /* SNTP_ACTIVE or SNTP_PASSIVE */
#define SNTPS_DSTADDR NULL         /* If NULL, uses subnet local
broadcast. */
#define SNTPS_INTERVAL 64          /* Broadcast interval, in seconds.
*/
#define SNTPS_TIME_HOOK NULL       /* Name of required clock access
routine. */
#endif    /* SNTP server. */
#endif /* SNTP server or client. */

/* DNS resolver parameters; You must change these defaults to your
config. */

#ifdef INCLUDE_DNS_RESOLVER
#define RESOLVER_DOMAIN_SERVER  "90.0.0.3"    /* DNS server IP address
*/
#define RESOLVER_DOMAIN         "wrs.com"     /* Resolver domain */
#endif /* INCLUDE_DNS_RESOLVER */

#ifdef INCLUDE_END
#ifdef INCLUDE_FEI
#undef  INCLUDE_FEI        /* Undefine FEI driver */
#define INCLUDE_FEI_END    /* Use End driver instead */
#endif
#endif

/* PCI device configuration type constants */

#define PCI_CFG_FORCE 0
#define PCI_CFG_AUTO  1
#define PCI_CFG_NONE  2

/* for backward compatibility with old 1.0 BSPs */

#ifndef BSP_VERSION
#   define BSP_VERSION  "1.0"   /* old 1.0 style BSP */
#   define BSP_VER_1_0  TRUE
#endif

#ifndef BSP_REV
#   define BSP_REV      "/0"    /* old 1.0 style BSP */
#endif

#endif  /* INCconfigAllh */

 
thanks 
Mahesh 

Hi james:

I tried changing the default setting for the 

be_gyus@yahoo.com (james) wrote in message news:<ff42611f.0211250149.4d41360a@posting.google.com>...
> v_mahesh@hotmail.com (Mahesh) wrote in message news:<4f7acce6.0211211832.1ab3277e@posting.google.com>...
> > Hi:
> > 
> > My name is Mahesh, Iam working on creating and Configuring VxWorks
> > Kernel for target Intel X86 and for windows host.
> > I have created a Bootrom Image for Network configuration and When i
> > try to boot the kernel through the floppy disk, the screen becomes
> > blank and it automatically reboots.
> > 
> > I will be happy if somebody can provide me some information. Also, is
> > there any way to debug and see what is going on underneath the hood.
> > 
> > The configuration and software versions are as follows:
> > VxWorks - 5.5
> > Tornado - 2.2
> > CPU - PENTIUM
> > C++Compiler - g++pentium (version - 2.93)
> > Host - Windows 2000.
> > Ethernet Driver - fei82557End Intel Ethernet Driver.
> > 
> > The config.h is configured using these macros
> > INCLUDE_NETWORK
> > INCLUDE_END,
> > INCLUDE_FEI_END,
> > INCLUDE_FTP,
> > INCLUDE_FTP_SERVER.
> > 
> > thanks
> > Mahesh
> 
>  Hi Mahesh,
> 
>  This is basically the configuration problem. In your config.h
> corresponding to the BSP you are using, check whether the Bootline
> parameters u have given is for fei....& with the right ip address.Mind
> you ,There should be only one bootline.. comment the other lines if
> exists in the Bootline for the particular BSP.
>  Check whether your PC_console has been made TRUE...this will get u a
> blue screen on the console (monitor if used) if made true else it will
> give u a blank screen after the vxld........
>  or the systme remains in a hung state.
>  To cross check whether the target is up and the n/w is in tact ,Keep
> pinging the target from the host m/e.
> 
>  These are the basic things to be done while building the bootrom.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: ifAddrAdd
Date: 25 Nov 2002 23:36:48 -0800
From: anurag.srivastava@rsystems.com (Anurag S)
Organization: http://groups.google.com/
Message-ID: <e1751e71.0211252336.2b6441e1@posting.google.com>
References: <3DDD49F1.8010207@arcor.de> <d6dd5318.0211221631.6cc26a7e@posting.google.com>

techie_me@yahoo.com (Aardra) wrote in message news:<d6dd5318.0211221631.6cc26a7e@posting.google.com>...
> I dont think you can assign two IP addresses to one network interface.
> But it is possible to have a system with two ip addresses if it has
> two NICs and each one having one IP address.
> Just curious, what type of application do you have in mind?
> 
> Ralf Hoppe <ralf.hoppe@arcor.de> wrote in message news:<3DDD49F1.8010207@arcor.de>...
> > Hi, i'am a pure novice with respect to the VxWorks network functions. 
> > The question that i have is, how does the function ifAddrAdd() work. Is 
> > it possible to assign two IP addresses (from the same network) to one 
> > interface device? And if so - can i open two sockets, one gets the 
> > traffic to the first IP address and the other receives the traffic to 
> > the second IP address? The other question related to that topic is: are 
> > there any side effects of that assignment of two addresses to one 
> > interface which should an network administrator have in mind if he 
> > configures the network (e.g. any ARP or ROUTING effects)?
> > 
> > Hope anybody knows an answer!?
> > 
> > Bye, Ralf

You can always always assign more than one (infact any number ) of IP
addresses to a network interface. This helps in doing virtual
subnetting. IfAddrAdd takes interface name and secondary IP address as
inputs, refer manual. when you create an IP then it makes a routing
entry but if that address belongs t different subnet then you need to
check routing for that particular IP.So network admin has to take care
of routing issues. I think you can do the socket manipulation as
specified by you.

thanks,
Anurag

---------------------------

Newsgroups: comp.os.vxworks
Subject: commit_and_inc: VirtualAlloc failed
Date: Tue, 26 Nov 2002 09:31:19 +0100
From: "Juergen Hahn (S)" <juergen.hahn@rbg42.siemens.de>
Organization: AT BE DI SW3, Siemens RBG W
Message-ID: <3DE33157.61826600@rbg42.siemens.de>
Reply-To: juergen.hahn@rbg42.siemens.de

Hi,

is there anybody out there, who can explain me, why this compile error
occurs?
If we use "-O1" instead of "-Os", the problems goes away... but we want
to use "-Os" for size issues.

Some info: Tornado 2.1 for Hitach SH, no patches so far installed,
memory on NT-PC is 256MB Ram, 1GB Swap, but problem occurs every time
and independent of PC.

Thanks in advance...

======== Rebuilding
"k:/ahu_sourcefiles/Main/Dev_Env/VxWorks/C6_Std/Target/Release/AhuC6.o"
========                                                                                                             
        k:/ahu_tools/tornado/host/x86-win32/bin/ccsh
- -Ik:/ahu_sourcefiles/Include
- -Ik:/ahu_sourcefiles/System_Interfaces/Include
- -Ik:/ahu_sourcefiles/Swp_Interfaces/Include
- -Ik:/ahu_tools/tornado-pc/target/con
fig/MMI_AudiHU -Ik:/ahu_tools/tornado-pc/target/proj/MMI_AudiHU
- -Ik:/ahu_tools/Rhapsody/Include/C -Ik:/ahu_tools/Rhapsody/Include/Cpp
- -Ik:/ahu_sourcefiles/System/OS_Abstraction_Layer/OS_Wrapper/Include
- -Ik:/ah
u_sourcefiles/Swp/Services/Passive/Trace_Support/Include
- -Ik:/ahu_sourcefiles/Swp/Services/Passive/Messaging_System/Source/MsgQueue/Include 
- -Ik:/ahu_sourcefiles/Swp/Services/Passive/Messaging_System/Source/Ms
gQueue/Source 
- -Ik:/ahu_sourcefiles/Swp/Services/Passive/Messaging_System/Source/MsgQueue/Source/Xcpp 
- -Ik:/ahu_sourcefiles/Swp/GUI/Source/Xcpp 
- -Ik:/ahu_sourcefiles/Swp/Applications/Car_Functions/Source/BLCar
Functions/Source/Xcpp 
- -Ik:/ahu_sourcefiles/Swp/Applications/Car_Functions/Source/VDCarFunctions/Source/Xcpp 
- -Ik:/ahu_sourcefiles/Swp/Applications/Settings/Source/BLSettings/Source/Xcpp 
- -Ik:/ahu_sourcefiles/
Swp/Applications/Settings/Source/VDSettings/Source/Xcpp 
- -Ik:/ahu_sourcefiles/Swp/GUI/Source 
- -Ik:/ahu_sourcefiles/Swp/GUI/Source/Include 
- -Ik:/ahu_sourcefiles/Swp/Applications/Car_Functions/Include  -Os -m3 -
c -fno-weak -ansi -DRW_MULTI_THREAD -D_REENTRANT -fno-rtti
- -fconserve-space -fno-exceptions -fvolatile -fno-builtin -fno-for-scope
- -I. -Ik:/k:/ahu_tools/tornado/target/h  -o
k:/ahu_sourcefiles/Main/Dev_Env/VxW
orks/C6_Std/Target/Release/AhuC6.o
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp                                                                                                                                  
In file included from
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:151:                                                                                                                                          
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_AM.sub: In function `void
Install_AM()':                                                                                                                                
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_AM.sub:150: `class
AM_CAudioManagement' has no member named
`pInAM_IGUI'                                                                                                
In file included from
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:159:                                                                                                                                          
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DIAG.sub: In function `void
Install_DIAG()':                                                                                                                            
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DIAG.sub:100: `class
DIAG_CDiagnosis' has no member named
`pInSYS_ISubSystem'                                                                                           
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DIAG.sub:108: `class
DIAG_CDiagnosis' has no member named
`pInMSF_IKwpReceiver'                                                                                         
In file included from
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:165:                                                                                                                                          
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DSP.sub: In function `void
Install_DSP()':                                                                                                                              
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DSP.sub:173: `class DSP_CBL'
has no member named
`pInTM_IExpired'                                                                                                       
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp: In function `void
ConnectAll_Component2Component()':                                                                                                               
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:694: `class
DIAG_CDiagnosis' has no member named
`pOutMSF_IKwpSender'                                                                                               
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:722: `class DSP_CBL' has no
member named
`pOutDP_IDataPool'                                                                                                         
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:726: `class DSP_CBL' has no
member named
`pOutTM_IRequest'                                                                                                          
(k:\ahu_tools\tornado\host\x86-win32\lib\gcc-lib\sh-wrs-vxworks\gcc-2.96\cc1plus.exe
1002) commit_and_inc: VirtualAlloc
failed                                                                                   
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_TUN.sub: In function `void
__static_initialization_and_destruction_0(int,
int)':                                                                                        
k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_TUN.sub:57: virtual memory
exhausted                                                                                                                                    
*** Error code
1                                                                                                                                                                                                 

- -- 
 m   | Siemens VDO Automotive AG
<o)  | Dipl.-Ing. (FH) Juergen Hahn, SV I IS RD SW RBG
(_)= | RbgG/C25/1/13, Im Gewerbepark C25, 93059 Regensburg
 "   | Tel.: +49-941-790-5257, Fax.: +49-941-790-5192

---------------------------

Newsgroups: comp.os.vxworks
Subject: HELP!!!!!!why can't my vxworks DHCP client work properly???
Date: Tue, 26 Nov 2002 17:54:33 +0800
From: "Seraph Ma" <seraph.ma@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <arvgd2$2glc$1@mail.cn99.com>

 I wanna set up a DHCP enviorment using Windriver's DHCP components . The
DHCP server runs under the vxWorks platform, the DHCP Client too.
                1. I can susccesfully build the image for DHCP Server and
DHCP client.
                2. DHCP Server( vxoworks ) can start up, the DHCP Server
task was spawned OK!
                3. I modify DHCP Client's bootline--set the flag(f) to 0x40,
which means the target should get the configurations from a DHCP server.
                4. But the DHCP client just block here,

                   Attached TCP/IP network interface to ene0
                   Getting boot parameters from network interface ene0

                 5. I have add ethernet input package hook for the DHCP
server. By this way, I know that the DHCP server had received the DHCP
multicast packages sent by the DHCP client( form a IP address 0.0.0.0 to
255.255.255.255, also the source MAC address was the same with the DHCP
client's ).

                 OK, I just don't know why can not get the DHCP client
run~~~~
                 Would you please give me some advice about this. I will be
greatly appreciate if you can give a littlle help.
                Thanx in advance.

Best Regards,
Seraph Ma

UTStarcom Shenzhen Research & Development Center
Address: 3/F,Legend Research & Development Building,
High-tech Industrial Park,Nanshan Shenzhen,PRC
Zip Code: 518057
Tel: (86-755)2698 3555-3530
Mobile: (86)13312915835
Fax: (86-755)2698 3786
Email: seraph.ma@utstar.com
Web Site: http://www.utstar.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: HELP!!!!!!why can't my vxworks DHCP client work properly???
Date: Tue, 26 Nov 2002 17:57:08 +0800
From: "Seraph Ma" <seraph.ma@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <arvght$2gn5$1@mail.cn99.com>
References: <arvgd2$2glc$1@mail.cn99.com>

FYI

My enviorment

CPU Pentium
OS vxWorks 5.4

"Seraph Ma" <seraph.ma@utstar.com> wrote in message
news:arvgd2$2glc$1@mail.cn99.com...
> I wanna set up a DHCP enviorment using Windriver's DHCP components . The
> DHCP server runs under the vxWorks platform, the DHCP Client too.
>                 1. I can susccesfully build the image for DHCP Server and
> DHCP client.
>                 2. DHCP Server( vxoworks ) can start up, the DHCP Server
> task was spawned OK!
>                 3. I modify DHCP Client's bootline--set the flag(f) to
0x40,
> which means the target should get the configurations from a DHCP server.
>                 4. But the DHCP client just block here,
>
>                    Attached TCP/IP network interface to ene0
>                    Getting boot parameters from network interface ene0
>
>                  5. I have add ethernet input package hook for the DHCP
> server. By this way, I know that the DHCP server had received the DHCP
> multicast packages sent by the DHCP client( form a IP address 0.0.0.0 to
> 255.255.255.255, also the source MAC address was the same with the DHCP
> client's ).
>
>                  OK, I just don't know why can not get the DHCP client
> run~~~~
>                  Would you please give me some advice about this. I will
be
> greatly appreciate if you can give a littlle help.
>                 Thanx in advance.
>
> Best Regards,
> Seraph Ma
> 
> UTStarcom Shenzhen Research & Development Center
> Address: 3/F,Legend Research & Development Building,
> High-tech Industrial Park,Nanshan Shenzhen,PRC
> Zip Code: 518057
> Tel: (86-755)2698 3555-3530
> Mobile: (86)13312915835
> Fax: (86-755)2698 3786
> Email: seraph.ma@utstar.com
> Web Site: http://www.utstar.com
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: HELP!!!!!!why can't my vxworks DHCP client work properly???
Date: Tue, 26 Nov 2002 18:27:13 +0800
From: "Seraph Ma" <seraph.ma@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <arviaa$2ip0$1@mail.cn99.com>
References: <arvgd2$2glc$1@mail.cn99.com> <arvght$2gn5$1@mail.cn99.com>

You know that the know vxWorks DHCP port number is defined using 2 macros
like this

#define DHCPS_PORT  67          <-----  in hex 0x0043
#define DHCPC_PORT  68          <-----  in hex 0x0044

But when my DHCP server is booted up,I got this:
- ->dhcps_port
dhcps_port=17152; dhcps_port=0x4300
- ->dhcpc_port
dhcpc_port=17400; dhcpc_port=0x4400

As what we can see in the file of "target/h/dhcp/common.h"
extern u_short dhcps_port;     /* DHCP server port (network byte order) */
extern u_short dhcpc_port;     /* DHCP server port (network byte order) */

Are there any thing related with the network byte-oreder ????????

A worong port number leads to DHCP server's unable to receive the DHCP
client's multicast packages????????

"Seraph Ma" <seraph.ma@utstar.com> wrote in message
news:arvght$2gn5$1@mail.cn99.com...
> FYI
>
> My enviorment
>
> CPU Pentium
> OS vxWorks 5.4
>
>
>
>
>
> "Seraph Ma" <seraph.ma@utstar.com> wrote in message
> news:arvgd2$2glc$1@mail.cn99.com...
> > I wanna set up a DHCP enviorment using Windriver's DHCP components . The
> > DHCP server runs under the vxWorks platform, the DHCP Client too.
> >                 1. I can susccesfully build the image for DHCP Server
and
> > DHCP client.
> >                 2. DHCP Server( vxoworks ) can start up, the DHCP Server
> > task was spawned OK!
> >                 3. I modify DHCP Client's bootline--set the flag(f) to
> 0x40,
> > which means the target should get the configurations from a DHCP server.
> >                 4. But the DHCP client just block here,
> >
> >                    Attached TCP/IP network interface to ene0
> >                    Getting boot parameters from network interface ene0
> >
> >                  5. I have add ethernet input package hook for the DHCP
> > server. By this way, I know that the DHCP server had received the DHCP
> > multicast packages sent by the DHCP client( form a IP address 0.0.0.0 to
> > 255.255.255.255, also the source MAC address was the same with the DHCP
> > client's ).
> >
> >                  OK, I just don't know why can not get the DHCP client
> > run~~~~
> >                  Would you please give me some advice about this. I will
> be
> > greatly appreciate if you can give a littlle help.
> >                 Thanx in advance.
> >
> > Best Regards,
> > Seraph Ma
> > 
> > UTStarcom Shenzhen Research & Development Center
> > Address: 3/F,Legend Research & Development Building,
> > High-tech Industrial Park,Nanshan Shenzhen,PRC
> > Zip Code: 518057
> > Tel: (86-755)2698 3555-3530
> > Mobile: (86)13312915835
> > Fax: (86-755)2698 3786
> > Email: seraph.ma@utstar.com
> > Web Site: http://www.utstar.com
> >
> >
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: HELP!!!!!!why can't my vxworks DHCP client work properly???
Date: Tue, 26 Nov 2002 13:06:35 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$x8k66h$c37$1@lnews.actcom.co.il>
References: <arvgd2$2glc$1@mail.cn99.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Seraph Ma" <seraph.ma@utstar.com> wrote in message
news:arvgd2$2glc$1@mail.cn99.com...
> I wanna set up a DHCP enviorment using Windriver's DHCP components . The
> DHCP server runs under the vxWorks platform, the DHCP Client too.
[snip]

It may not answer your question directly, but it is very unusual
that a single computer is running both a DHCP server and client,
and there are many reasons for this:

A DHCP server has a IP address pool to give out to clients,
it should use one of these to setup a static address.
A DHCP server MUST have an IP address to begin operation,
but in your case the DHCP client will have to obtain it from
the same DHCP server, effectively creating a "chicken and an egg"
problem.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Large App in Boot ROM
Date: 26 Nov 2002 03:49:25 -0800
From: devoz@appiancom.com (Joe DeVincentis)
Organization: http://groups.google.com/
Message-ID: <476efddf.0211260349.10ddef1b@posting.google.com>
References: <3DC7F74D.4090702@minn.teradyne.com> <2222d8d3.0211171329.2f511acc@posting.google.com> <3DD965B7.7000207@minn.teradyne.com>

Another option I haven't seen mentioned is to modify the
hardware designs to boot to 0x100.  This allows you to
store the bootstrap image at the base of the flash,
offset by 0x100.  In the bootstrap code you would need
to add code that executes from dual-port memory and
remaps OR0/BR0 to place the flash where you ultimately
want it to reside in the address map.  You copy that 
sequence to dual-port, jump there, the chip select
is remapped, you jump to the new address space and 
continue with the bootstrap.  This lets you pretty much
chose any option, and make the most out of your flash.

I have implemented this technique on 8260 and other powerQuicc
cpus.

Joe

Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DD965B7.7000207@minn.teradyne.com>...
> Brent,
> 
> Thanks, very helpful.  Caused me to look more closely at the defs.bsp
> file... Strange, looks like they sort of have the problem surround automagically,
> but not entirely, apparently:
> 
> . . .
> ## bsp flags
> 
> LD_LOW_FLAGS    = -Ttext $(RAM_LOW_ADRS)
> LD_HIGH_FLAGS   = -Ttext $(RAM_HIGH_ADRS)
> RES_LOW_FLAGS   = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_LOW_ADRS)
> RES_HIGH_FLAGS  = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_HIGH_ADRS)
> 
> ROM_ENTRY       = _romInit
> SYS_ENTRY       = _sysInit
> USR_ENTRY       = _usrInit
> 
> LDFLAGS         = -X -N
> LD_PARTIAL_FLAGS= -X -r
> . . .
> 
> 
> It seems to me that the RES_LOW_FLAGS is more or less approprate, as I want
> the code loaded to the RAM at that address, but I wonder if I can burn the
> Flash with the ice as is... short of two seperate
> burns with the VisionICE, with two seperate bias and offset values.
> 
> We recently had to upgrade to a newer gnu compiler to support >32M
> jumps and have also seen problems with the elfHex (bin to hex) program,
> any issues you've noticed?
> 
> 
> Thanks Again,
> -Keith
> 
> 
> 
> brentb wrote:
> 
> > Keith,
> > 
> > I am also using a MPC8245 and have experienced this problem.  For example,
> > the vxWorks_rom image consists of text, data, and bss.  The text section
> > consists of romInit.s and romStart.c. During compilation, the actual vxWorks.o
> > image is converted entirely to .data, hence the use of binArrayStart and
> > binArrayEnd in the copy process in romStart. In the final link line of the
> > make file output, there is a flag that specifies where the text section
> > will be located (-Ttext fff00100), at fff00100.  You can just add a line
> > to the flags to specify the location of the .data section using the following:
> > -Tdata <data location>, i.e. -Tdata ff80000.  Let me know if that helps.
> > 
> > -Brent
> > 
> > Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DC7F74D.4090702@minn.teradyne.com>...
> > 
> >>We are using a MPC8245 that has a boot vector at fff00100 (~1M) upper rom
> >>remaining.  Our application is spread over several projects and is
> >>on the order of 4 Megabytes.  We have significant ROM and RAM
> >>resources (e.g., 16M / 128M).
> >>
> >>Question:
> >>--------------------
> >>1) Is there an easy way to put the image to be copied from ROM to
> >>RAM in a different location other than contiguously with the BOOT ROM,
> >>e.g., boots at FFF00100, but copylongs/unzip copies from FF800000.
> >>
> >>
> >>Anyone had any experience with this issue?
> >>
> >>
> >>Thanks,
> >>Keitho
> >>

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Tue Nov 26 08:18:32 2002
From: Mike McCullough <mike@mccengineering.com>
Date: Tue Nov 26 08:18:33 PST 2002
Subject: VxWorks and JWorks 4.0 question

Has anyone used Jworks and the VxWorks ramDrv to access files?? I am trying 
to load a JPEG image off the ramDrv into an AWT Panel and keep getting file 
not found errors. Any help greatly appreciated as always.

**********************************************************
Mike McCullough                    MCC Engineering
President and CEO                  9 Cheshire Court
                                    Londonderry, NH 03053

mike@mccengineering.com            Tel:  603-537-9593
                                    Fax:  603-434-9890
www.mccengineering.com            Cell: 603-247-1219

**********************************************************
        24x7 VxWorks Support  Custom Support Programs
          VxWorks Training   Embedded Consulting Services
                     A WindLink Partner
**********************************************************

From vxwexplo-errs@csg.lbl.gov  Tue Nov 26 09:51:26 2002
From: Douglas Wilson <dwilson@birdstep.com>
Date: Tue Nov 26 09:51:28 PST 2002
Subject: Re: Changing current directory on simulator, Tornado 2 on Windows

In message <newscache$rywv5h$e29$1@lnews.actcom.co.il> "Leonid Rosenboim"
<My_1st_name@Consultant.Com>
 wrote:

>Yes, do
>    -> @cd "/newdir"
>istead of
>    -> cd "/newdir"
>
>Looks like reading through the manuals is out of fasion these days ;-)

(in reply to my question: Is there any way to change the current directory
(on the target, not the host) from the shell, when running the simulator
under Tornado 2, on Windows NT?)

Hmm - this may look like a simple case of RTFM, but just for once, it's not.
When I try  using @cd the Shell responds thus:

undefined symbol: @cd

This is really a shame, because otherwise @cd would be exactly what I want
to do. Does this have something to do with the simulator I'm using (VxSim
lite, as opposed to the full simulator), or the Tornado version (2.0.2)?

From vxwexplo-errs@csg.lbl.gov  Wed Nov 27 02:29:07 2002
From: "ultidude_raj" <ramani@jobsrm.com>
Date: Wed Nov 27 02:29:09 PST 2002
Subject: Openings@Bangalore - Apply Here!

Hi Friends,

Mistral Solutions for their Bangalore operations are looking for 
Embedded Professionals with 4+ years of experience in RTOS (VxWorks, 
pSos etc.,) for the position of Project Leaders. Given below are the 
job responsibilities for your reference.

Lead a team of Team Leaders 
Planning and Design of modules/project
Assignment of tasks for team leaders
Helps Project manager in project estimation & planning 

Positions:
Project Leaders - 4.5 to 6 years
Sr.Project Leaders - 6 to 7.5 years

Kindly forward your profiles to ramani@jobsrm.com 

Thanks & Regards,
Rajesh Ramani

From vxwexplo-errs@csg.lbl.gov  Wed Nov 27 04:03:16 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Wed Nov 27 04:03:17 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Wed Nov 27 04:03:14 PST 2002

        Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
        Subject: Marge archives
        Subject: Re: Large App in Boot ROM
        Subject: socket call returns an error
        Subject: Re: Changing current directory on simulator, Tornado 2 on Windows
        Subject: Re: dosfs2-FAT
        Subject: Re: VxWorks and JWorks 4.0 question
        Subject: obtaining DHCP options
        Subject: question about library-code
        Subject: Re: question about library-code
        Subject: Mounting
        Subject: Re: question about library-code

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
Date: 26 Nov 2002 07:51:41 -0700
From: taashlo@sandia.gov
Organization: Sandia National Laboratories, Albuquerque, NM USA
Message-ID: <znrw1j0i.fsf@sandia.gov>
References: <of8dg1kd.fsf@sandia.gov> <Xns92D1EACF570C7jborkhuisproximcom@192.19.193.66>
Sender: taashlo@TYPHOON

Johan Borkhuis <JBorkhuis@proxim.com> writes:
> taashlo@sandia.gov wrote:
> 
> > I have since upgraded to Tornado 2.1 (VxWorks 5.4.2) and a
> > new BSP version.  I didn't change any of the config.h options
> > that I thought would relate to having both shells active, but
> > the new version only has the target shell.  (When the target
> > shell boots up I *don't* see "WDB: Ready" in the banner and
> > "tWdbTask" is *not* in the task list.)
> 
> You have to include WDB in your build. After you include this you will see 
> the WDB ready prompt again.
> 
> Kind regards,
>         Johan
> 
> -- 
>         o o o o o o o . . .   _____________________________
>        o      _____           ||    Johan Borkhuis        |
>      .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
>     >(________|__|_[_________]_|__________________________|
>     _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
> === VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===

I guess I deserved that. :-(

Yes, INCLUDE_WDB is defined.  Just as I had it defined when using
Tornado 2.0 and both shells were working.  I guess I'm asking if
something changed between Tornado 2.0 and 2.1 that would impact
both shells being enabled.  Or, if somebody knows the "official"
configuration for having both shells enabled (assuming that my
configuration accidently took advantage of a "loophole" in
Tornado 2.0).

I even put the following in my BSP's sysLib.c to prove to myself
that INCLUDE_WDB isn't getting #undef'd somewhere along the way:

#ifdef INCLUDE_WDB
#warning *** WDB IS INCLUDED ***
#endif

The warning message showed up during compilation so I believe
that INCLUDE_WDB is #defined.  But there is still no host shell,
no "WDB: Ready" in the banner, and no "tWdbTask".

Thank you,

Tad

---------------------------

Newsgroups: comp.os.vxworks
Subject: Marge archives
Date: 26 Nov 2002 07:24:13 -0800
From: oded.weissman@motorola.com (Oded Weissman)
Organization: http://groups.google.com/
Message-ID: <acaaa989.0211260724.4ec462a8@posting.google.com>

Hello

With what utility and\or command can I marge few archives (.a)
 to one big archive (created with diab "dar" utility).

Thanks

Oded

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Large App in Boot ROM
Date: 26 Nov 2002 09:33:44 -0800
From: devoz@appiancom.com (Joe DeVincentis)
Organization: http://groups.google.com/
Message-ID: <476efddf.0211260933.109c067b@posting.google.com>
References: <3DC7F74D.4090702@minn.teradyne.com> <2222d8d3.0211171329.2f511acc@posting.google.com> <3DD965B7.7000207@minn.teradyne.com> <476efddf.0211260349.10ddef1b@posting.google.com>

Ooops.  A motorola employee pointed out to me that the
8260/860 and probably other powerQuiccs assert chip select
0 (OR0/BR0) on every external access after reset, until you
program an internal register.  The 860 manual has a section
16.5.2 Boot Chip Select Operation that this.

I haven't tried this, I can't remember why I ended up dynamically
remapping the OR0/BR0 although I am certain we first tried just
setting up OR0/BR0 directly, my guess is that there was some other
instruction in the code prior to this that hit IMMR, or something?
etc.  Either that or I was just thinking too hard and reading too
little ;-)

Best wishes - Joe

devoz@appiancom.com (Joe DeVincentis) wrote in message news:<476efddf.0211260349.10ddef1b@posting.google.com>...
> Another option I haven't seen mentioned is to modify the
> hardware designs to boot to 0x100.  This allows you to
> store the bootstrap image at the base of the flash,
> offset by 0x100.  In the bootstrap code you would need
> to add code that executes from dual-port memory and
> remaps OR0/BR0 to place the flash where you ultimately
> want it to reside in the address map.  You copy that 
> sequence to dual-port, jump there, the chip select
> is remapped, you jump to the new address space and 
> continue with the bootstrap.  This lets you pretty much
> chose any option, and make the most out of your flash.
> 
> I have implemented this technique on 8260 and other powerQuicc
> cpus.
> 
> Joe
> 
> 
> 
> Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DD965B7.7000207@minn.teradyne.com>...
> > Brent,
> > 
> > Thanks, very helpful.  Caused me to look more closely at the defs.bsp
> > file... Strange, looks like they sort of have the problem surround automagically,
> > but not entirely, apparently:
> > 
> > . . .
> > ## bsp flags
> > 
> > LD_LOW_FLAGS    = -Ttext $(RAM_LOW_ADRS)
> > LD_HIGH_FLAGS   = -Ttext $(RAM_HIGH_ADRS)
> > RES_LOW_FLAGS   = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_LOW_ADRS)
> > RES_HIGH_FLAGS  = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_HIGH_ADRS)
> > 
> > ROM_ENTRY       = _romInit
> > SYS_ENTRY       = _sysInit
> > USR_ENTRY       = _usrInit
> > 
> > LDFLAGS         = -X -N
> > LD_PARTIAL_FLAGS= -X -r
> > . . .
> > 
> > 
> > It seems to me that the RES_LOW_FLAGS is more or less approprate, as I want
> > the code loaded to the RAM at that address, but I wonder if I can burn the
> > Flash with the ice as is... short of two seperate
> > burns with the VisionICE, with two seperate bias and offset values.
> > 
> > We recently had to upgrade to a newer gnu compiler to support >32M
> > jumps and have also seen problems with the elfHex (bin to hex) program,
> > any issues you've noticed?
> > 
> > 
> > Thanks Again,
> > -Keith
> > 
> > 
> > 
> > brentb wrote:
> > 
> > > Keith,
> > > 
> > > I am also using a MPC8245 and have experienced this problem.  For example,
> > > the vxWorks_rom image consists of text, data, and bss.  The text section
> > > consists of romInit.s and romStart.c. During compilation, the actual vxWorks.o
> > > image is converted entirely to .data, hence the use of binArrayStart and
> > > binArrayEnd in the copy process in romStart. In the final link line of the
> > > make file output, there is a flag that specifies where the text section
> > > will be located (-Ttext fff00100), at fff00100.  You can just add a line
> > > to the flags to specify the location of the .data section using the following:
> > > -Tdata <data location>, i.e. -Tdata ff80000.  Let me know if that helps.
> > > 
> > > -Brent
> > > 
> > > Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message news:<3DC7F74D.4090702@minn.teradyne.com>...
> > > 
> > >>We are using a MPC8245 that has a boot vector at fff00100 (~1M) upper rom
> > >>remaining.  Our application is spread over several projects and is
> > >>on the order of 4 Megabytes.  We have significant ROM and RAM
> > >>resources (e.g., 16M / 128M).
> > >>
> > >>Question:
> > >>--------------------
> > >>1) Is there an easy way to put the image to be copied from ROM to
> > >>RAM in a different location other than contiguously with the BOOT ROM,
> > >>e.g., boots at FFF00100, but copylongs/unzip copies from FF800000.
> > >>
> > >>
> > >>Anyone had any experience with this issue?
> > >>
> > >>
> > >>Thanks,
> > >>Keitho
> > >>

---------------------------

Newsgroups: comp.os.vxworks
Subject: socket call returns an error
Date: 26 Nov 2002 10:12:40 -0800
From: pkatre@hotmail.com (Prashant)
Organization: http://groups.google.com/
Message-ID: <18775478.0211261012.847646e@posting.google.com>

What could be the possible reasons for the API socket to return an error
under vxWorks. The errno from the socket call is 55, which means  NOBUFS.
Any help or pointers on this? Thanks in advance
Prashant

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Changing current directory on simulator, Tornado 2 on Windows
Date: Tue, 26 Nov 2002 20:27:43 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$6o476h$g18$1@lnews.actcom.co.il>
References: <as0dp7$73l$1@overload.lbl.gov>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Douglas Wilson" <dwilson@birdstep.com> wrote in message
news:as0dp7$73l$1@overload.lbl.gov...
[snip]
> Hmm - this may look like a simple case of RTFM, but just for once, it's
not.
> When I try  using @cd the Shell responds thus:
>
> undefined symbol: @cd
>
> This is really a shame, because otherwise @cd would be exactly what I want
> to do. Does this have something to do with the simulator I'm using (VxSim
> lite, as opposed to the full simulator), or the Tornado version (2.0.2)?

No, thos only has to do to what kind of Shell you are using:
if you are using the Target shell, then everything you do is
on the target, and the @ syntax does not apply.
Whne you use the Host Shell (akak WindSh), then some of its
commands are "builtins" and thus are executed on the host,
whereas the @ sytax directs it to use the equivalent target function.

It does seem like a simple case of RTFM.

- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: dosfs2-FAT
Date: 26 Nov 2002 14:30:06 -0800
From: yli@transdimension.com (liyi)
Organization: http://groups.google.com/
Message-ID: <c994781b.0211261430.22fd6c96@posting.google.com>
References: <c994781b.0211211442.409ddca1@posting.google.com> <60fb21d0.0211251309.64793a90@posting.google.com>

Thanks, FAT16 is enough for me now... I will try it.

zarfus@hotmail.com (Dan) wrote in message news:<60fb21d0.0211251309.64793a90@posting.google.com>...
> yli@transdimension.com (liyi) wrote in message news:<c994781b.0211211442.409ddca1@posting.google.com>...
> > Hi, 
> > 
> > I have a hard driver which is formatted as FAT32 in windows 2000. But
> > when I put it in vxWorks system and do a ls, it show me all those old
> > files already deleted. After I did a dosFsVolFormat, those garbage
> > dispear, but again windows do not recognize that disk.
> > Why did that happen, aren't they all FAT?
> > 
> > Thanks,
> > 
> > Yi
> 
> Hi Yi, 
> 
> I can tell you that we took the trouble here to reFDISK our drives to
> FAT16.
> We didn't really care about size, so that was fine for us.  FAT16
> works much better, it seems to me.
> 
> Of course, we're newbies.  But if you don't care about big drives,
> it'll work fine.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: VxWorks and JWorks 4.0 question
Date: Wed, 27 Nov 2002 00:29:03 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as13ke$nhh$2@helle.btinternet.com>
References: <5.1.0.14.2.20021126111444.00b5f140@pop3.ttlc.net>

Mike McCullough wrote:
> Has anyone used Jworks and the VxWorks ramDrv to access files?? I am trying 
> to load a JPEG image off the ramDrv into an AWT Panel and keep getting file 
> not found errors. Any help greatly appreciated as always.

I'd check that the filename doesn't start with // or a space.
I've seen both from the java under vxworks.

(intercepted open() and patch the filename to fix it...)

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: obtaining DHCP options
Date: Wed, 27 Nov 2002 14:57:54 +0800
From: "Yung" <general_miller@yahoo.com>
Organization: IMS Netvigator
Message-ID: <as1qdl$s5v62@imsp212.netvigator.com>

Hi Experts,

after the DHCP client is up and running, how can we further retrieve the
Gateway and DNS addresses from the DHCP server? Should we use
dhcpcOptionGet()? I just want to make sure I am on the right track.
Thanks a lot.

---------------------------

Newsgroups: comp.os.vxworks
Subject: question about library-code
Date: Wed, 27 Nov 2002 09:39:51 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1038386503.456087@newsreader2.wirehub.nl>

Hi,

Sometime ago I was helping a coworker debugging timer problems in his
VxWorks application, as said then the call timer_gettime returned
negative values. So I listed the asm-code in the shell, an recoded it
for him again into c, so debugging - or understanding the problem -
would become a bit easier.
Another thing, this helped to code a quick work workaround. Time is
quite critical in our project and dont know when windriver releases a
fix for the problem.

While listing timer_gettime en timer_settime I noticed a some
dead-code. I wondering why are they for. Especially in released
library code I did not exprect this code to be there.

For example:
xxxxxx5e    call __errno
xxxxxx63    mov [eax], 0x16,
xxxxxx69    mov eax, 0xffffffff
xxxxxx6e    jmp xxxxxx                 /* leave function */
xxxxxx73    lea esi, [esi]                /* !!!!!! */
xxxxxx75    lea esi, [esi+0]            /* !!!!!! */
xxxxxx7c    cmp[ebp+20],0

Why is the code at xxxxxx73 and xxxxxx75 there? In my opinion there
are 10 bytes wasted. I know it's not always easy to predict forward
jump addresses in compilers, but thought these issues where solved in
these days. If you look at the listings of other functions, one could
see similair parts of code. The code at the above mentioned address is
never executed and the code shows it never can.

System: PIII, Tornado 2, VxWorks 5.4

Just wondering why this code is here. Especially in embeded systems
every byte of code....

Cheers,
Renee
- - - - - - - - -
Renee A. Teunissen
PTS Software bv, Meerweg 7, 1405BA Bussum, NL.
T.+31-(0)35-6926969, M.+31-(0)6-22778313,
http://www.pts.nl, <first_name>@pts.nl
personal link page: http://wittenburg10c.nl/db/dest/links.html

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: question about library-code
Date: Wed, 27 Nov 2002 10:10:03 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as25lr$inq$1@knossos.btinternet.com>
References: <1038386503.456087@newsreader2.wirehub.nl>

> So I listed the asm-code in the shell, and recoded it
> for him again into c, so debugging - or understanding the problem -
> would become a bit easier.

Often a good way of finding that silly mistake in the source.
Staring at the source wont show things like:
	while (..) do {...} while (...);

> Another thing, this helped to code a quick work workaround. Time is
> quite critical in our project and dont know when windriver releases a
> fix for the problem.

Do they ever?  I ended up patching in fixes..

> While listing timer_gettime en timer_settime I noticed a some
> dead-code. I wondering why are they for. Especially in released
> library code I did not exprect this code to be there.
> 
> For example:
> xxxxxx5e    call __errno
> xxxxxx63    mov [eax], 0x16,
> xxxxxx69    mov eax, 0xffffffff
> xxxxxx6e    jmp xxxxxx                 /* leave function */
> xxxxxx73    lea esi, [esi]                /* !!!!!! */
> xxxxxx75    lea esi, [esi+0]            /* !!!!!! */
> xxxxxx7c    cmp[ebp+20],0
> 
> Why is the code at xxxxxx73 and xxxxxx75 there? In my opinion there
> are 10 bytes wasted. I know it's not always easy to predict forward
> jump addresses in compilers, but thought these issues where solved in
> these days. If you look at the listings of other functions, one could
> see similair parts of code. The code at the above mentioned address is
> never executed and the code shows it never can.

I suspect that it is dead space deliberately allocatedby the compiler
in order to get the label onto a cache line boundary.
Unfortunately the required alignment for the segment has been lost.

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Mounting
Date: 27 Nov 2002 02:54:53 -0800
From: ravi368@yahoo.com (Ravi Uday)
Organization: http://groups.google.com/
Message-ID: <ecca3ca6.0211270254.494e6ea3@posting.google.com>

Hi,
I am a bit confused with the mounting and unmounting concepts. What
are these actually. Say when i need to write a file to a device and
read back what all things do one needs to do before he attempts
considering OS to be VxWorks.
I know windows just abstracts the user from all these..inner
details..but since i am trying to write a device driver i am stuck at
this point.

I would also like to know about File Systems that are supported in
VxWorks OS
and in general how do u mount a dosFs file system and read from a
plugged in device.

All kinds of experience and help is really appreciated.

- - Ravi

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: question about library-code
Date: Wed, 27 Nov 2002 11:57:07 +0100
From: "Renee Teunissen" <if.you.spam.me.I.will.charge.you.1000.Euro.By.emailing.me.you agree.with.these.terms@mail.zevenaar.org>
Organization: Wirehub! Internet, The Netherlands
Message-ID: <1038394741.221110@newsreader2.wirehub.nl>
References: <1038386503.456087@newsreader2.wirehub.nl> <as25lr$inq$1@knossos.btinternet.com>

> > Another thing, this helped to code a quick work workaround. Time
is
> > quite critical in our project and dont know when windriver
releases a
> > fix for the problem.
>
> Do they ever?  I ended up patching in fixes..
Well he made a case of it.

>
> > While listing timer_gettime en timer_settime I noticed a some
> > dead-code. I wondering why are they for. Especially in released
> > library code I did not exprect this code to be there.
> >
> > For example:
> > xxxxxx5e    call __errno
> > xxxxxx63    mov [eax], 0x16,
> > xxxxxx69    mov eax, 0xffffffff
> > xxxxxx6e    jmp xxxxxx                 /* leave function */
> > xxxxxx73    lea esi, [esi]                /* !!!!!! */
> > xxxxxx75    lea esi, [esi+0]            /* !!!!!! */
> > xxxxxx7c    cmp[ebp+20],0
> >
> > Why is the code at xxxxxx73 and xxxxxx75 there? In my opinion
there
> > are 10 bytes wasted. I know it's not always easy to predict
forward
> > jump addresses in compilers, but thought these issues where solved
in
> > these days. If you look at the listings of other functions, one
could
> > see similair parts of code. The code at the above mentioned
address is
> > never executed and the code shows it never can.
>
> I suspect that it is dead space deliberately allocatedby the
compiler
> in order to get the label onto a cache line boundary.
> Unfortunately the required alignment for the segment has been lost.

Well you could be right about this. I'm not into compilers / asm
generation that deep these days. I learned my asm knowledge on the
6510 and 8080. 8086  and 80286 just enough to understand it. It's a
pitty many of my age (32) get quite scared if they even think about
assembler..

Thanx for the info.

Renee.

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Wed Nov 27 06:09:08 2002
From: Mike McCullough <mike@mccengineering.com>
Date: Wed Nov 27 06:09:10 PST 2002
Subject: Re: VxWorks and JWorks 4.0 question 

I don't know if that is the problem as I hard-coded the filename from the 
Java side without "//" or spaces in the name. Thanks for the open() 
suggestion, I'll take a look at that side and see what it's doing...

Newsgroups: comp.os.vxworks
Subject: Re: VxWorks and JWorks 4.0 question
Date: Wed, 27 Nov 2002 00:29:03 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as13ke$nhh$2@helle.btinternet.com>
References: <5.1.0.14.2.20021126111444.00b5f140@pop3.ttlc.net>
Mike McCullough wrote:
 > Has anyone used Jworks and the VxWorks ramDrv to access files?? I am trying
 > to load a JPEG image off the ramDrv into an AWT Panel and keep getting file
 > not found errors. Any help greatly appreciated as always.
I'd check that the filename doesn't start with // or a space.
I've seen both from the java under vxworks.
(intercepted open() and patch the filename to fix it...)
David

**********************************************************
Mike McCullough                    MCC Engineering
President and CEO                  9 Cheshire Court
                                    Londonderry, NH 03053

mike@mccengineering.com            Tel:  603-537-9593
                                    Fax:  603-434-9890
www.mccengineering.com            Cell: 603-247-1219

**********************************************************
        24x7 VxWorks Support  Custom Support Programs
          VxWorks Training   Embedded Consulting Services
                     A WindLink Partner
**********************************************************

From vxwexplo-errs@csg.lbl.gov  Wed Nov 27 17:58:28 2002
From: "gongjian" <gongjian_wx@sohu.com>
Date: Wed Nov 27 17:58:29 PST 2002
Subject: i want to join comp.os.vxworks

vxwexploã

	

 				

ningyu_98@yahoo.com

2002-11-28

From vxwexplo-errs@csg.lbl.gov  Thu Nov 28 00:07:18 2002
From: "=?iso-8859-1?Q?bighandsvx@libero.it?=" <bighandsvx@libero.it>
Date: Thu Nov 28 00:07:21 PST 2002
Subject: =?iso-8859-1?Q?point_to_point_ethernet_questions?=

Hi all,
I'm using vxWorks 5.4 on a Intel based board, with integrated DEC21143 
ethernet controller, in a CPCI rack with other ethernet boards: I'd 
like to use the onboard ethernet port as a private point to point 
connection (with TCP/IP stack!) with another board belonging to a 
different CPCI rack.
The problem is that all the ethernet boards on the same CPCI rack, 
being controlled by the same System board running vxWorks, have in 
common with my private port also the ARP table (and I can't be sure 
that my private point to point IP address isn't present also on the net 
connected to the other ethernet boards, in other words I don't want any 
routing or ARP).
I tried to use ifFlagChange with IFF_POINTTOPOINT flag to configure 
a "POINT TO POINT" connection (now my interface is "BROADCAST") but 
according with the manual that flag can be set just at interface 
initialization time. So I tried to pass some dcOpMode parameters to 
dcattach function ORING some of the following
#define DC_PROMISCUOUS_FLAG     	0x01	/* set promiscuous mode 
*/
#define DC_MULTICAST_FLAG		0x02	/* pass all multicast 
pkts */

/* Modes for 100-Mb/s Ethernet configuration */

#define DC_100_MB_FLAG			0x04	/* 100-Mb/s mode */	
#define DC_21140_FLAG			0x08	/* Lance chip is 21140 */
#define DC_FULLDUPLEX_FLAG		0x10	/* Full Duplex Mode */
#define DC_SCRAMBLER_FLAG		0x20	/* MII/SYM in scrambler 
mode */
#define DC_PCS_FLAG			0x40	/* MII/SYM in symbol 
mode */
#define DC_PS_FLAG			0x80	/* Serial Port selected  
*/
#define DC_ILOOPB_FLAG			0x100	/* Internal Loop Back 
Mode */
#define DC_ELOOPB_FLAG			0x200	/* External Loop Back 
Mode */
#define DC_HBE_FLAG			0x400	/* Heart Beat Enable 
Flag */

but the interface after initialization is still in "BROADCAST" mode.
Point to point means FullDuplex for low level drivers?
How can I set up successfully a POINTTOPOINT interface?
Any suggestions?
(BTW my solution for now is to turn off the ARP with IFF_NOARP and then 
sending using broadcast address for which
Thank you in advance,
BH (Maurizio)

From vxwexplo-errs@csg.lbl.gov  Thu Nov 28 03:40:12 2002
From: Atkinson Andrew <AATKINSON1@qinetiq.com>
Date: Thu Nov 28 03:40:13 PST 2002
Subject: Task Execution -  

vxworks

Hi All

I am writing some test code and I need the capability to determine whether a
specific task is currently executing/has executed - this needs to be
implemented in source code, so no GUI driven tools can be used.

Any ideas???

Cheers

Andy Atkinson
Software Engineer
Bldg 31a
QinetiQ, Bincleaves Technology Park
Weymouth
Dorset
DT4 8UR

Tel : 01305 764660
Fax : 01305 764661
e-mail : AATKINSON1@QinetiQ.com

vxworks

The Information contained in this E-Mail and any subsequent correspondence
is private and is intended solely for the intended recipient(s).
For those other than the recipient any disclosure, copying, distribution,
or any action taken or omitted to be taken in reliance on such information
is prohibited and may be unlawful.

From vxwexplo-errs@csg.lbl.gov  Thu Nov 28 03:41:47 2002
From: Douglas Wilson <dwilson@birdstep.com>
Date: Thu Nov 28 03:41:48 PST 2002
Subject: Re: Changing current directory on simulator, Tornado 2 on Windows

"Leonid Rosenboim" <leonid@Consultant.Com> wrote in message
<newscache$6o476h$g18$1@lnews.actcom.co.il>

> No, thos only has to do to what kind of Shell you are using:
> if you are using the Target shell, then everything you do is
> on the target, and the @ syntax does not apply.
> Whne you use the Host Shell (akak WindSh), then some of its
> commands are "builtins" and thus are executed on the host,
> whereas the @ sytax directs it to use the equivalent target function.
> 
> It does seem like a simple case of RTFM.

Okay, but I'm using the Host Shell - I'm starting it from the Tornado menu.
So doesn't that mean that the @ syntax should work? Shouldn't I be able to
use @cd to change directory on the target (the simulator in this case)?

From vxwexplo-errs@csg.lbl.gov  Thu Nov 28 04:03:16 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Thu Nov 28 04:03:17 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Thu Nov 28 04:03:13 PST 2002

        Subject: Re: question about library-code
        Subject: netTask
        Subject: Re: netTask
        Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
        Subject: Re: dosfs2-FAT
        Subject: X86 Boot Problem
        Subject: Re: X86 Boot Problem
        Subject: Macro inclusion verification and proof
        Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
        Subject: Re: Download Procedure
        Subject: Common Interview Questions!!
        Subject: Re: Download Procedure
        Subject: Re: WDB debugger timing out ?!

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: question about library-code
Date: Wed, 27 Nov 2002 14:47:00 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as2lt4$7j4$1@knossos.btinternet.com>
References: <1038386503.456087@newsreader2.wirehub.nl> <as25lr$inq$1@knossos.btinternet.com> <1038394741.221110@newsreader2.wirehub.nl>

> Well you could be right about this. I'm not into compilers / asm
> generation that deep these days. I learned my asm knowledge on the
> 6510 and 8080. 8086  and 80286 just enough to understand it. It's a
> pitty many of my age (32) get quite scared if they even think about
> assembler..

Yes, if you debug the compiler generated assembler you don't get
waylaid by odd macros, compiler bugs and nasty typos.
Reading compiler generated code (for source you have) is a reasonable
way of working out the instruction set.
Annotating the disassembly of an entire vxworks image (including
rtxwindows and java) is a way to go mad!

Yes - I am older than you, and have written reasonable amounts of pdp11,
6809, 8085, z80, x86, 68k, sparc and arm assembler.

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: netTask
Date: Wed, 27 Nov 2002 16:33:49 +0200
From: "Martin Roth" <bmr006@email.mot.com>
Organization: Motorola
Message-ID: <as2l5m$o2q$1@newshost.mot.com>

I have applied to Windriver in order to get some timing characteristics.
Hoping to get some answer from
I am using the following tools:
Tornado 2.02
Vxworks 5.4
The target board is with MPC855T (POWERPC) processor of Motorola.
The BSP is for ADS860 Motorola board and it is ported to our board. The
information I need is foro MPC8260 processor of Motorola.

1
For better design I need to understand better the functionality of netTask
task.
We need this information for design purposes. Specifically , I would like to
know how the network task operates in case of two Ethernet interfaces
(without a router).

2
For example, during reception the motFecHandleRecvInt() function is called
form netTask. This function also handles all the received buffers of a
specific interface.
While doing so, the second Ethernet interface is not being handled. netTask
will start handling the second interface after it has competed handling all
the incoming packets of the first one. This is my conclusion from reading
the motFecEnd  driver. Is this correct ?

Question 1: Assuming that netTask is the highest priority and assuming that
the interrupts come only from the timer (decrementer) and Ethernet, are
there any benchmarks that indicate the time of processing 1/10/50/100 UDP
packets (without fragmentation). In other words,  How long does it take one
UDP packet to get to a high priority task application from the moment
motFecReceive() starts handling it ? You can assume that there are no
interrupts during the packet handling.
I would appreciate if there is some benchmark, including the processor,
clock, etc.

Question 2: What does  netJobAdd() mean when it is called from Ethernet
interrupt ? Does it mean that control goes to netTask immediately after the
return from interrupt?
What if the netTask is the task that has been interrupted by the interrupt
from Ethernet controller ? How long can it take till the netTask gets to the
requested function buffered by netJobAdd() within Ethernet interrupt?

I must have this information in order to see if I can meet the timing
requirements I have.

Martin Roth
Mailto:bmr006@email.mot.com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: netTask
Date: Wed, 27 Nov 2002 17:38:40 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$hir86h$mka$1@lnews.actcom.co.il>
References: <as2l5m$o2q$1@newshost.mot.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Martin Roth" <bmr006@email.mot.com> wrote in message
news:as2l5m$o2q$1@newshost.mot.com...
> I have applied to Windriver in order to get some timing characteristics.
> Hoping to get some answer from
Don't hold your breath ;-)

> I am using the following tools:
> Tornado 2.02
> Vxworks 5.4
> The target board is with MPC855T (POWERPC) processor of Motorola.
> The BSP is for ADS860 Motorola board and it is ported to our board. The
> information I need is foro MPC8260 processor of Motorola.
>
> 1
> For better design I need to understand better the functionality of netTask
> task.
> We need this information for design purposes. Specifically , I would like
to
> know how the network task operates in case of two Ethernet interfaces
> (without a router).
>
This is rather simple, really. The task is just a "server", executing every
request it gets in a FIFO order, and now it gets requests from two
devices, it will execute them in the order received from the ISR.
Each driver's bottom-half function will be executed which in turn
will call ipintr() which calls ip_input() and then the tcp_input()
or udp_input() if it is not doing routing, and all packets are desined for
the
local host.

> 2
> For example, during reception the motFecHandleRecvInt() function is called
> form netTask. This function also handles all the received buffers of a
> specific interface.
> While doing so, the second Ethernet interface is not being handled.
netTask
> will start handling the second interface after it has competed handling
all
> the incoming packets of the first one. This is my conclusion from reading
> the motFecEnd  driver. Is this correct ?
>
Absolutely right.

> Question 1: Assuming that netTask is the highest priority and assuming
that
> the interrupts come only from the timer (decrementer) and Ethernet, are
> there any benchmarks that indicate the time of processing 1/10/50/100 UDP
> packets (without fragmentation). In other words,  How long does it take
one
> UDP packet to get to a high priority task application from the moment
> motFecReceive() starts handling it ? You can assume that there are no
> interrupts during the packet handling.
> I would appreciate if there is some benchmark, including the processor,
> clock, etc.
>
I doubt there is a specific benchmark, but if this is critical, I would
suggest
to either use WindView, or an external logic anayzer to measure these times.
Also, depending on the driver, the bottom-half function would be executted
by the netTask once for every packet receiver, or will process all packets
currently in Rx buffers in a "batch", depending on the driver
implementation.

> Question 2: What does  netJobAdd() mean when it is called from Ethernet
> interrupt ? Does it mean that control goes to netTask immediately after
the
> return from interrupt?
> What if the netTask is the task that has been interrupted by the interrupt
> from Ethernet controller ? How long can it take till the netTask gets to
the
> requested function buffered by netJobAdd() within Ethernet interrupt?
>
netJobAdd() will make the netTask READY immediately, so if it is highest
priority, it will indeed run upon return from interrupt.
But if netTask wasl already executing some code when the interrupt happened,
it will continue to execute the current request until complete, and
subsequently
fetch the next request from the queue, and execute it in a FIFO order.
Only when the queue is empty of requests, will the netTask go into PEND
mode and yield the CPU.
>
> I must have this information in order to see if I can meet the timing
> requirements I have.
>
Martin, it is very likely that in order to meet your performance
requirements
will you need to modify the Ethernet driver. I have done so several times
for different Ethernet chips, biut never with the PowerQuick-2.
- --
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
Date: 27 Nov 2002 11:30:51 -0700
From: taashlo@sandia.gov
Organization: Sandia National Laboratories, Albuquerque, NM USA
Message-ID: <d6oqg90k.fsf@sandia.gov>
References: <of8dg1kd.fsf@sandia.gov> <Xns92D1EACF570C7jborkhuisproximcom@192.19.193.66> <znrw1j0i.fsf@sandia.gov> <as029c$5pr$1@snoopy.bndlg.de>
Sender: taashlo@TYPHOON

"Michael Lawnick" <michael.lawnick@no_spam.kontron.com> writes:
> Hi Tad,
> 
> but network is up and running, i.e. ftp and/or telnet are working?
> 
> Michael

Yes, I can FTP from the target to the host and from the host to the target.
The tNetTask is running with no errors.

Tad

> <taashlo@sandia.gov> schrieb im Newsbeitrag news:znrw1j0i.fsf@sandia.gov...
> > Johan Borkhuis <JBorkhuis@proxim.com> writes:
> > > taashlo@sandia.gov wrote:
> > >
> > > > I have since upgraded to Tornado 2.1 (VxWorks 5.4.2) and a
> > > > new BSP version.  I didn't change any of the config.h options
> > > > that I thought would relate to having both shells active, but
> > > > the new version only has the target shell.  (When the target
> > > > shell boots up I *don't* see "WDB: Ready" in the banner and
> > > > "tWdbTask" is *not* in the task list.)
> > >
> > > You have to include WDB in your build. After you include this you will
> see
> > > the WDB ready prompt again.
> > >
> > > Kind regards,
> > >         Johan
> > >
> > > --
> > >         o o o o o o o . . .   _____________________________
> > >        o      _____           ||    Johan Borkhuis        |
> > >      .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
> > >     >(________|__|_[_________]_|__________________________|
> > >     _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
> > > === VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===
> >
> >
> > I guess I deserved that. :-(
> >
> > Yes, INCLUDE_WDB is defined.  Just as I had it defined when using
> > Tornado 2.0 and both shells were working.  I guess I'm asking if
> > something changed between Tornado 2.0 and 2.1 that would impact
> > both shells being enabled.  Or, if somebody knows the "official"
> > configuration for having both shells enabled (assuming that my
> > configuration accidently took advantage of a "loophole" in
> > Tornado 2.0).
> >
> > I even put the following in my BSP's sysLib.c to prove to myself
> > that INCLUDE_WDB isn't getting #undef'd somewhere along the way:
> >
> > #ifdef INCLUDE_WDB
> > #warning *** WDB IS INCLUDED ***
> > #endif
> >
> > The warning message showed up during compilation so I believe
> > that INCLUDE_WDB is #defined.  But there is still no host shell,
> > no "WDB: Ready" in the banner, and no "tWdbTask".
> >
> > Thank you,
> >
> > Tad

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: dosfs2-FAT
Date: 25 Nov 2002 13:09:08 -0800
From: zarfus@hotmail.com (Dan)
Organization: http://groups.google.com/
Message-ID: <60fb21d0.0211251309.64793a90@posting.google.com>
References: <c994781b.0211211442.409ddca1@posting.google.com>

yli@transdimension.com (liyi) wrote in message news:<c994781b.0211211442.409ddca1@posting.google.com>...
> Hi, 
> 
> I have a hard driver which is formatted as FAT32 in windows 2000. But
> when I put it in vxWorks system and do a ls, it show me all those old
> files already deleted. After I did a dosFsVolFormat, those garbage
> dispear, but again windows do not recognize that disk.
> Why did that happen, aren't they all FAT?
> 
> Thanks,
> 
> Yi

Hi Yi, 

I can tell you that we took the trouble here to reFDISK our drives to
FAT16.
We didn't really care about size, so that was fine for us.  FAT16
works much better, it seems to me.

Of course, we're newbies.  But if you don't care about big drives,
it'll work fine.

---------------------------

Newsgroups: comp.os.vxworks
Subject: X86 Boot Problem
Date: 27 Nov 2002 17:51:16 -0800
From: jc422@cornell.edu (Jacky Cheung)
Organization: http://groups.google.com/
Message-ID: <484f4f20.0211271751.29c1e6ad@posting.google.com>

Hi all,
   I have just started a project at school using
VxWorks on a x86 board. I have been trying to 
create a boot disk to boot up VxWorks on the board
so that I can set the boot parameter. However, the board
only boots up a certain point after a lot of "+"
signs, and then it would stall:

V1.6++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++
                .
                .
                .

   I used the mkboot utility and the default
VxWorks rom that the Pentium BSP provided. Can anyone
give me a hint on my problem? I would really appreciate
that. Thank you.

Jacky

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: X86 Boot Problem
Date: Thu, 28 Nov 2002 02:19:47 GMT
From: "drdiags" <drdiags@attbi.com>
Organization: AT&T Broadband
Message-ID: <73fF9.158688$nB.12829@sccrnsc03>
References: <484f4f20.0211271751.29c1e6ad@posting.google.com>

Hello Jacky,

   Depending on the BSP and whether this is T2.2/AE or not. In T2.2,
the serial port is the default console port (I think AE also). In earlier
release of the x86 BSP, PC_CONSOLE was for most of the BSPs I have
seen. Looking at your bootloader version (1.6) I am guessing this is
either AE or T2.2, since I remember seeing 1.2 for T2 and 1.5 if I used
T2.0.2 mkboot utility. Anyway, look in your BSP config.h and locate
the macro INCLUDE_PC_CONSOLE and if it is #undef'd, then
your output from the bootloader is being directed to the COM port.
Don't forget to find the link to the vxWorks FAQ, which has a lot
of good information. A google search will point you to it. HTH.

"Jacky Cheung" <jc422@cornell.edu> wrote in message
news:484f4f20.0211271751.29c1e6ad@posting.google.com...
> Hi all,
>    I have just started a project at school using
> VxWorks on a x86 board. I have been trying to
> create a boot disk to boot up VxWorks on the board
> so that I can set the boot parameter. However, the board
> only boots up a certain point after a lot of "+"
> signs, and then it would stall:
>
> V1.6++++++++++++++++++++++++++++++++++++++
> +++++++++++++++++++++++++++++++++++++++++
>                 .
>                 .
>                 .
>
>    I used the mkboot utility and the default
> VxWorks rom that the Pentium BSP provided. Can anyone
> give me a hint on my problem? I would really appreciate
> that. Thank you.
>
>
> Jacky

---------------------------

Newsgroups: comp.os.vxworks
Subject: Macro inclusion verification and proof
Date: 27 Nov 2002 21:29:41 -0800
From: vxnerd@rediffmail.com (subbarayan)
Organization: http://groups.google.com/
Message-ID: <f81c4277.0211272129.1400056@posting.google.com>

dear mentors,
I am using tornado2.0,vxworks 5.4 version and pc486 target,floppy
based bootable target and which is standalone.I would like to know
from any of u mentors ,How to enable pci support for my project.I have
one doubt.I used the tornado project browser and selected the
components tab and included under the components under bus,included
pci bus support.I would like to know from you,the use of prjcomps.h
header file created for a project and also prjparams.h header
file.What are contents in these header files reflecting?I guess,that
when u include any component,it will be automatically defined in
prjparams.h and prjcoms.h header files under the external
dependencies.First can any one let me know whether my guess is
correct,Incase i am correct in guessing,if i include,pci support,I am
unable to find a #define statement for it like #define
INCLUDE_PCI in comps.h and also in prjparams.h.
How can i make sure that the component included in project explorer is
actually built in ur obj file,after it is built.One thing is it
notifies by being bold letters,but i am unsatisfied by that proof and
want to know whether the macros i included is really present in my
bootable obj file or not,after and before my obj file is built.
Kindly let me know,further wrt above said,as the bios will have all
the details of buses and h/w(eg-scsi,pci bus,ata etc..).Will vxworks
read the bios automatically and report back during boot time or
something explicitly need to be done to make it recognise and
display.I am very much interested in particular wrt to pci.
Any pointers or tutorials or suggestion or website help or advice and
solutions ,will be of grt help to me.Advanced thanks to person
replying me.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
Date: Thu, 28 Nov 2002 07:56:47 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <as4eng$dln$1@snoopy.bndlg.de>
References: <of8dg1kd.fsf@sandia.gov> <Xns92D1EACF570C7jborkhuisproximcom@192.19.193.66> <znrw1j0i.fsf@sandia.gov> <as029c$5pr$1@snoopy.bndlg.de> <d6oqg90k.fsf@sandia.gov>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Hi Tad,

I'm using T2.2 and these are my WDB-includes:
#define INCLUDE_WDB
#define INCLUDE_WDB_BANNER
#define INCLUDE_WDB_BP
#define INCLUDE_WDB_COMM_END
#define INCLUDE_WDB_CTXT
#define INCLUDE_WDB_DIRECT_CALL
#define INCLUDE_WDB_EVENTPOINTS
#define INCLUDE_WDB_EVENTS
#define INCLUDE_WDB_EXC_NOTIFY
#define INCLUDE_WDB_EXIT_NOTIFY
#define INCLUDE_WDB_FUNC_CALL
#define INCLUDE_WDB_GOPHER
#define INCLUDE_WDB_MEM
#define INCLUDE_WDB_REG
#define INCLUDE_WDB_START_NOTIFY
#define INCLUDE_WDB_TASK
#define INCLUDE_WDB_TASK_BP
#define INCLUDE_WDB_TSFS
#define INCLUDE_WDB_USER_EVENT
#define INCLUDE_WDB_VIO
#define INCLUDE_WDB_VIO_LIB

I don't expect it to have changed much in the T2.x versions.

HTH
Michael

<taashlo@sandia.gov> schrieb im Newsbeitrag news:d6oqg90k.fsf@sandia.gov...
> "Michael Lawnick" <michael.lawnick@no_spam.kontron.com> writes:
> > Hi Tad,
> >
> > but network is up and running, i.e. ftp and/or telnet are working?
> >
> > Michael
>
> Yes, I can FTP from the target to the host and from the host to the
target.
> The tNetTask is running with no errors.
>
> Tad
>
>
>
> > <taashlo@sandia.gov> schrieb im Newsbeitrag
news:znrw1j0i.fsf@sandia.gov...
> > > Johan Borkhuis <JBorkhuis@proxim.com> writes:
> > > > taashlo@sandia.gov wrote:
> > > >
> > > > > I have since upgraded to Tornado 2.1 (VxWorks 5.4.2) and a
> > > > > new BSP version.  I didn't change any of the config.h options
> > > > > that I thought would relate to having both shells active, but
> > > > > the new version only has the target shell.  (When the target
> > > > > shell boots up I *don't* see "WDB: Ready" in the banner and
> > > > > "tWdbTask" is *not* in the task list.)
> > > >
> > > > You have to include WDB in your build. After you include this you
will
> > see
> > > > the WDB ready prompt again.
> > > >
> > > > Kind regards,
> > > >         Johan
> > > >
> > > > --
> > > >         o o o o o o o . . .   _____________________________
> > > >        o      _____           ||    Johan Borkhuis        |
> > > >      .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
> > > >     >(________|__|_[_________]_|__________________________|
> > > >     _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
> > > > === VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html
===
> > >
> > >
> > > I guess I deserved that. :-(
> > >
> > > Yes, INCLUDE_WDB is defined.  Just as I had it defined when using
> > > Tornado 2.0 and both shells were working.  I guess I'm asking if
> > > something changed between Tornado 2.0 and 2.1 that would impact
> > > both shells being enabled.  Or, if somebody knows the "official"
> > > configuration for having both shells enabled (assuming that my
> > > configuration accidently took advantage of a "loophole" in
> > > Tornado 2.0).
> > >
> > > I even put the following in my BSP's sysLib.c to prove to myself
> > > that INCLUDE_WDB isn't getting #undef'd somewhere along the way:
> > >
> > > #ifdef INCLUDE_WDB
> > > #warning *** WDB IS INCLUDED ***
> > > #endif
> > >
> > > The warning message showed up during compilation so I believe
> > > that INCLUDE_WDB is #defined.  But there is still no host shell,
> > > no "WDB: Ready" in the banner, and no "tWdbTask".
> > >
> > > Thank you,
> > >
> > > Tad

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Download Procedure
Date: 28 Nov 2002 00:35:13 -0800
From: vijay.peshkar@wipro.com (Vijay Peshkar)
Organization: http://groups.google.com/
Message-ID: <bb8c75e1.0211280035.3e8abbee@posting.google.com>
References: <d6e2de0a.0211220343.5f0d758@posting.google.com> <8e6507b.0211250559.662910dc@posting.google.com> <d6e2de0a.0211271942.789def83@posting.google.com>

Raju,

Realtek card is not supported by default. You need to get the driver code
and add the files in drv\end\unsupported. You should be able to get this patch 
from wrs or RTL.
Its a good idea to check up if your rtl card has really been recognised in
your boot. Also the bootline should read rtl and not ene for this card.

Hope this is helpful.
cheers,
Vijay

vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211271942.789def83@posting.google.com>...
> Hi Harry,
> 
> I have succeded in Attaching the interface, But not able to boot and
> the system is giving the same error 0xfd0003. I have changed the IRQ
> to 11 which has been specified by my Admin but I am not able to do the
> same with the address. Please let me know the way I can know the
> address of my ethernet card.
> 
> Thanks a lot and hope you will help me in future also.
> 
> Bye
> 
> V R R Raju
> 
> 
> 
> harry2405@rediffmail.com (Harry) wrote in message news:<8e6507b.0211250559.662910dc@posting.google.com>...
> > Hi 
> > The Realtek family of cards follow the NE2000 standard. So, you need
> > to
> > #define INCLUDE_ENE in config.h. This is already defined for you.
> > 
> > Also, your boot line is wrong. It shows "fd" (which means floppy) and
> > you are trying to get vxWorks from floppy, then FTP from 'c:' on your
> > host. This is whole lot confusing for the target and VxWorks just
> > hangs. Change fd=0,0(0,0) to ene(0,0). Add password (FTP pw) also to
> > the boot line. Your boot line should look something like this:
> > 
> > "ene(0,0)host:c/tornado/target/config/pc486/vxWorks
> >  h=131.200.2.244 e=131.200.2.105 u=target pw=target"
> > 
> > Then 'make' the following:
> > 1.vxWorks, **not** vxWorks.st right now.
> > 2.bootrom_uncmp, 
> > 3.mkboot a: bootrom_uncmp
> > 
> > and reboot the target with the floppy (as you have done already).
> > If you can see "Attaching network interface ... done", be happy... you
> > have almost booted the target.
> > 
> > Now your target **DOESN'T** boot completely, because, you have not
> > configured the I/O and IRQ of the target network card. You get an
> > error 0xfd0003. Catch hold of your admin and get the correct I/O and
> > IRQ of the card with the correct driver floppy.
> > 
> > Edit the config.h file for correct IO_ADRS_ENE and INT_LVL_ENE. Then
> > build all images and make boot floppy and boot the target. This boots
> > the target.
> > 
> > Good luck..!!
> > 
> > Harry.
> > 
> > vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211220343.5f0d758@posting.google.com>...
> > > Dear Friends,
> > > 
> > > I am working on Vxworks 5.4 and Tornado II. I am a newbie and don't
> > > know how to download the bootable image to target from host using FTP.
> > > I did what I was told by my friend and it is as follows:
> > > 
> > > 1. Configure the Vxworks using the tornado and Include and Exclude the
> > > components according to application requirements.
> > > 
> > > 2. I don't know which Ethernet Driver type to include (ELT or ENT or
> > > any other). I am using Realtek processor based Ethernet Card. Please
> > > let me know which Ethernet Drivers should I use.
> > > 
> > > 3. What parameter should I specify DEFAULT_BOOT_LINE for hardware
> > > components properties.
> > > I am specifying the following
> > > 
> > > "fd=0,0(0,0)host:c/tornado/target/config/pc486/vxWorks.st
> > > h=131.200.2.244 e=131.200.2.105 u=target"
> > > 
> > > 4. I am making a bootrom_uncmp image and then copying it to Floppy
> > > Disk using mkboot a:bootrom_uncmp.
> > > 
> > > 5. Then I am trying to boot my target using the floppy.
> > > 
> > > 6. I am making a Vxworks.st standalone image.
> > > 
> > > 7. I am starting the FTP server by giving the username and password
> > > and also the home directory in which my image is stored.
> > > 
> > > 8. I am executing the image in the target using the @ command after
> > > changing any parameters using c and P commands.
> > > 
> > > 9. Target gets started with saying Loading and suddenly some numbers
> > > are displayed and it hangs. Even it is not getting connected to the
> > > FTP server in the Host.
> > > 
> > > Please let me know where I have gone wrong and whether the above
> > > procedure is correct. Also let me know whether there is another way of
> > > downloading and its procedure which will help me a lot .
> > > 
> > > 
> > > Thanks in advance.
> > > 
> > > with regards,
> > > 
> > > Rajneesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Common Interview Questions!!
Date: 28 Nov 2002 02:03:23 -0800
From: psris@yahoo.com (ZZZZZZ)
Organization: http://groups.google.com/
Message-ID: <cbbd6f8c.0211280203.43aa2e75@posting.google.com>

Hi all,
  This is my first post here. Hope someone will help me out.
  Though I can say that I have been working over VxWorks from
  past 2 yrs or so, I havent had a deep knowledge over it,
  may be because of various factors.
  I have worked over Task Handling and Semaphore Handling etc..
  
  I want to know that what kind of question can interviewer ask
  me, if I am applying job else where..
  And some tips and pointers to tune myself up in better manner
  about VxWorks.

Thanks in Adv,
Lean & sexy :)

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Download Procedure
Date: 28 Nov 2002 03:04:30 -0800
From: embd_man@hotmail.com (Russel)
Organization: http://groups.google.com/
Message-ID: <42fa4adc.0211280304.4078728b@posting.google.com>
References: <d6e2de0a.0211220343.5f0d758@posting.google.com> <8e6507b.0211250559.662910dc@posting.google.com> <d6e2de0a.0211271942.789def83@posting.google.com>

Buddy .. give the hex equivalent of 11 ...(0b)

vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211271942.789def83@posting.google.com>...
> Hi Harry,
> 
> I have succeded in Attaching the interface, But not able to boot and
> the system is giving the same error 0xfd0003. I have changed the IRQ
> to 11 which has been specified by my Admin but I am not able to do the
> same with the address. Please let me know the way I can know the
> address of my ethernet card.
> 
> Thanks a lot and hope you will help me in future also.
> 
> Bye
> 
> V R R Raju
> 
> 
> 
> harry2405@rediffmail.com (Harry) wrote in message news:<8e6507b.0211250559.662910dc@posting.google.com>...
> > Hi 
> > The Realtek family of cards follow the NE2000 standard. So, you need
> > to
> > #define INCLUDE_ENE in config.h. This is already defined for you.
> > 
> > Also, your boot line is wrong. It shows "fd" (which means floppy) and
> > you are trying to get vxWorks from floppy, then FTP from 'c:' on your
> > host. This is whole lot confusing for the target and VxWorks just
> > hangs. Change fd=0,0(0,0) to ene(0,0). Add password (FTP pw) also to
> > the boot line. Your boot line should look something like this:
> > 
> > "ene(0,0)host:c/tornado/target/config/pc486/vxWorks
> >  h=131.200.2.244 e=131.200.2.105 u=target pw=target"
> > 
> > Then 'make' the following:
> > 1.vxWorks, **not** vxWorks.st right now.
> > 2.bootrom_uncmp, 
> > 3.mkboot a: bootrom_uncmp
> > 
> > and reboot the target with the floppy (as you have done already).
> > If you can see "Attaching network interface ... done", be happy... you
> > have almost booted the target.
> > 
> > Now your target **DOESN'T** boot completely, because, you have not
> > configured the I/O and IRQ of the target network card. You get an
> > error 0xfd0003. Catch hold of your admin and get the correct I/O and
> > IRQ of the card with the correct driver floppy.
> > 
> > Edit the config.h file for correct IO_ADRS_ENE and INT_LVL_ENE. Then
> > build all images and make boot floppy and boot the target. This boots
> > the target.
> > 
> > Good luck..!!
> > 
> > Harry.
> > 
> > vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211220343.5f0d758@posting.google.com>...
> > > Dear Friends,
> > > 
> > > I am working on Vxworks 5.4 and Tornado II. I am a newbie and don't
> > > know how to download the bootable image to target from host using FTP.
> > > I did what I was told by my friend and it is as follows:
> > > 
> > > 1. Configure the Vxworks using the tornado and Include and Exclude the
> > > components according to application requirements.
> > > 
> > > 2. I don't know which Ethernet Driver type to include (ELT or ENT or
> > > any other). I am using Realtek processor based Ethernet Card. Please
> > > let me know which Ethernet Drivers should I use.
> > > 
> > > 3. What parameter should I specify DEFAULT_BOOT_LINE for hardware
> > > components properties.
> > > I am specifying the following
> > > 
> > > "fd=0,0(0,0)host:c/tornado/target/config/pc486/vxWorks.st
> > > h=131.200.2.244 e=131.200.2.105 u=target"
> > > 
> > > 4. I am making a bootrom_uncmp image and then copying it to Floppy
> > > Disk using mkboot a:bootrom_uncmp.
> > > 
> > > 5. Then I am trying to boot my target using the floppy.
> > > 
> > > 6. I am making a Vxworks.st standalone image.
> > > 
> > > 7. I am starting the FTP server by giving the username and password
> > > and also the home directory in which my image is stored.
> > > 
> > > 8. I am executing the image in the target using the @ command after
> > > changing any parameters using c and P commands.
> > > 
> > > 9. Target gets started with saying Loading and suddenly some numbers
> > > are displayed and it hangs. Even it is not getting connected to the
> > > FTP server in the Host.
> > > 
> > > Please let me know where I have gone wrong and whether the above
> > > procedure is correct. Also let me know whether there is another way of
> > > downloading and its procedure which will help me a lot .
> > > 
> > > 
> > > Thanks in advance.
> > > 
> > > with regards,
> > > 
> > > Rajneesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: WDB debugger timing out ?!
Date: 28 Nov 2002 03:21:58 -0800
From: embd_man@hotmail.com (Russel)
Organization: http://groups.google.com/
Message-ID: <42fa4adc.0211280321.f571543@posting.google.com>
References: <H00000f8002d22d9.1038293822.cruzer5@MHS>

radha@telecruz.com wrote in message news:<H00000f8002d22d9.1038293822.cruzer5@MHS>...
> Hi,
> 
> In Tornado's Target server configuaration, you can set the timeout.
> (in Tornado: tools->Target server->configure-->>)
> 
> -Radha Krishna
> TeleCruz,
> India
> 
> 
> 
> Submitted-by vxwexplo-errs@csg.lbl.gov  Mon Nov 25 20:57:42 2002
> Submitted-by: "Sabarivel S" <sabaris@future.futsoft.com>
> 
> Hi,
> 
> What may be the reasons  for the Tornado WDB timing out ?

  This is really a gruesome and a buggin task.. at times when nothing
but everything goes out of our control ( & the PM is right behind
us)wrong..There could be enumerable reasons for this..
  Most common among would be the backend you select as opposed to the
one you have configured for.. sounds gloomy :-(
  Many a times if u r using a sim ..it could be tgtsvr configuration
which gives the way out.. check out the corefiles is it the right
one..
  The reason can be specifically be gauged on the exact configuration
u r using i.e sim or target etc....

> And how we can increase the WDB timeout value ?

 No need of being overoptimistic by increasing this value.. it serves
no purpose at times.

> Kindly help me out in this regard.
> 
> regards,
> sabari

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Fri Nov 29 04:03:23 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Fri Nov 29 04:03:24 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Fri Nov 29 04:03:19 PST 2002

        Subject: symbols not accesible from target shell?
        Subject: Re: muxDevUnload and the target server (end driver connection)
        Subject: Re: symbols not accesible from target shell?
        Subject: Re: muxDevUnload and the target server (end driver connection)
        Subject: Re: symbols not accesible from target shell?
        Subject: Re: Macro inclusion verification and proof
        Subject: Re: Common Interview Questions!!
        Subject: I want to join in you!!
        Subject: Re: Download Procedure
        Subject: how to recompile the vxWorks using make under command line mode??
        Subject: PPP port for vxworks
        Subject: FDD boot first then see boot is ok ! Re: X86 Boot Problem
        Subject: Re: Tornado 2.2 for target 2.2
        Subject: Re: how to recompile the vxWorks using make under command line mode??
        Subject: strange problem while building bootrom_uncmp.
        Subject: Re: how to recompile the vxWorks using make under command line mode??
        Subject: Re: Large App in Boot ROM
        Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
        Subject: Memory Mapping with cacheDmaMalloc
        Subject: Re: Tornado 2.2 for X86
        Subject: Re: commit_and_inc: VirtualAlloc failed
        Subject: Re: socket call returns an error
        Subject: Re: Marge archives
        Subject: shutdown operation
        Subject: pci detection problems and doubts
        Subject: Re: how to recompile the vxWorks using make under command line mode??

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: symbols not accesible from target shell?
Date: 28 Nov 2002 06:41:16 -0800
From: glenn_is_cool@hotmail.com (Andreas F)
Organization: http://groups.google.com/
Message-ID: <ccd61736.0211280641.72bc97c5@posting.google.com>

Hi...

I have discovered that only some of my downloaded functions are
callable from the target shell, consider the example below(which is
from the target shell)

- -> lkup "test"
routestatShow             0x0016f960 text     (vxWorks.sym)
test                      0x009ed298 text     (simulation.out)
value = 0 = 0x0
- -> test
Test Success
Symbol Located
value = 15 = 0xf
- -> lkup "SimInit"
SimInit(void)             0x009ed36c text     (simulation.out)
value = 0 = 0x0
- -> SimInit
undefined symbol: SimInit

As you can see it seems to find 'SimInit' with lkup, but it doesn't
find it when I want to call it(this works from the host shell).
Why? And what to do about it?

regards

Andreas

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: muxDevUnload and the target server (end driver connection)
Date: 28 Nov 2002 07:51:50 -0800
From: fillmore2@arcor.de (Achim)
Organization: http://groups.google.com/
Message-ID: <9d082700.0211280751.7c86f1f4@posting.google.com>
References: <9d082700.0211190451.75418afc@posting.google.com> <ardfu1$ga7$1@helle.btinternet.com>

David Laight <david@spam.me.l8s.co.uk> wrote in message news:<ardfu1$ga7$1@helle.btinternet.com>...

[...]

> Does your final product require you to be able to unload the
> ethernet driver?
> Does it require wdb?

Unfortunately, the product requires both...

I have to handle up to 4 Ethernet interfaces - and unloading the
driver for one of the Ethernet interfaces seemed to be the "cleaner"
way compared to trying to change the HW under an loaded driver.
Besides that, the use of the tornado tools for debugging is supposed
to work over the ethernet connection - so here comes the wdb.

Interestingly, there's no problem of starting the target server after
a mux-unload/change/reload of the driver for selected interfaces - but
I do loose my Ethernet connection (and maybe cause some further
problems I haven't looked at yet) after the target server shutdown.

Achim.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: symbols not accesible from target shell?
Date: Thu, 28 Nov 2002 17:43:07 +0100
From: "Alberto Pellegrini" <alberto.pellegrini@icn.siemens.it>
Organization: Siemens Business Services
Message-ID: <as5h25$mf7$1@news.mch.sbs.de>
References: <ccd61736.0211280641.72bc97c5@posting.google.com>

If you have written SimInit(void) into a C++ module, this behaviour is quite
normal: the symbol name is changed to contain the 'prototype' of the
function.

To avoid this problem you have to change your source code into:

extern "C" SimInit(void) {....}

Bye

"Andreas F" <glenn_is_cool@hotmail.com> ha scritto nel messaggio
news:ccd61736.0211280641.72bc97c5@posting.google.com...
> Hi...
>
> I have discovered that only some of my downloaded functions are
> callable from the target shell, consider the example below(which is
> from the target shell)
>
> -> lkup "test"
> routestatShow             0x0016f960 text     (vxWorks.sym)
> test                      0x009ed298 text     (simulation.out)
> value = 0 = 0x0
> -> test
> Test Success
> Symbol Located
> value = 15 = 0xf
> -> lkup "SimInit"
> SimInit(void)             0x009ed36c text     (simulation.out)
> value = 0 = 0x0
> -> SimInit
> undefined symbol: SimInit
>
> As you can see it seems to find 'SimInit' with lkup, but it doesn't
> find it when I want to call it(this works from the host shell).
> Why? And what to do about it?
>
> regards
>
> Andreas

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: muxDevUnload and the target server (end driver connection)
Date: Thu, 28 Nov 2002 18:09:22 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as5m4h$hql$1@venus.btinternet.com>
References: <9d082700.0211190451.75418afc@posting.google.com> <ardfu1$ga7$1@helle.btinternet.com> <9d082700.0211280751.7c86f1f4@posting.google.com>

> I have to handle up to 4 Ethernet interfaces - and unloading the
> driver for one of the Ethernet interfaces seemed to be the "cleaner"
 > way compared to trying to change the HW under an loaded driver.

I couldn't convince myself that there was any locking to stop the
mux unload being done while a packet was being transmitted.
(ie while the call stack of some process goes through the mux).

You can just take the interface 'down' - getting rid of the
routes is quite tricky, but needs to be done anyway - and fix
the driver so that it will discard anything that comes its way.

I did this with a pcmcia ethernet card driver.  On card removal
I just marker the interface down.

IIRC wdb uses etherhooks rather than using UDP (or a specific
ethertype from the mux).

I killed wdb - a waste of target memory :-)

	David

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: symbols not accesible from target shell?
Date: 28 Nov 2002 20:55:45 GMT
From: ac151@FreeNet.Carleton.CA (David Clarke)
Organization: The National Capital FreeNet
Message-ID: <as5vsh$lvk$1@freenet9.carleton.ca>
References: <ccd61736.0211280641.72bc97c5@posting.google.com> <as5h25$mf7$1@news.mch.sbs.de>
Reply-To: ac151@FreeNet.Carleton.CA (David Clarke)

"Alberto Pellegrini" (alberto.pellegrini@icn.siemens.it) writes:
> If you have written SimInit(void) into a C++ module, this behaviour is quite
> normal: the symbol name is changed to contain the 'prototype' of the
> function.
> 
> To avoid this problem you have to change your source code into:
> 
> extern "C" SimInit(void) {....}

Also - you can type "cplusDemanglerSet 0" at the shell before doing the
lkup.  Now you'll actually see what the symbol name really is.

- --
- -------------------------------  /'''  --------------------------------
David Clarke                     c-00
ac151@Freenet.carleton.ca           >                 
- -------------------------------    -   --------------------------------

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Macro inclusion verification and proof
Date: Fri, 29 Nov 2002 07:59:35 +0900
From: "Girish Gulawani" <girishvgNOSPAM@yahoo.com>
Message-ID: <3de69fd9$0$22470$44c9b20d@news3.asahi-net.or.jp>
References: <f81c4277.0211272129.1400056@posting.google.com>

Tornado Tools are trying to be friendly with you by putting included
components in Bold, or Red if error, etc. I guess they call it GUI. So that
"What You See What You Get". I am not aware of a case where actually
highlighted component is not being included or so. Moreover there is inbuilt
self check.

Having said that, following test in that case becomes just a paranoid check.

.1 open usrAppInit.c for editing.
.2 suppose you want to check INCLUDE_PCI option.
.3 write the following code in usrAppInit.c
        void great_test(void)
            {
            #ifdef INCLUDE_PCI
                I am just paranoid.
            #endif /*INCLUDE_PCI*/
            }
.4 Re-build all from the menu.
.5 You might just see compilation errors.

Now what goes inside these macro controlled blocks is upto the code. But
your doubt whether Macro itself is included or not, I guess, will be solved
by above dummy code.

Anyway you may check the FAQ of VxWorks for further information.

"subbarayan" <vxnerd@rediffmail.com> wrote in message
news:f81c4277.0211272129.1400056@posting.google.com...
> dear mentors,
> I am using tornado2.0,vxworks 5.4 version and pc486 target,floppy
> based bootable target and which is standalone.I would like to know
> from any of u mentors ,How to enable pci support for my project.I have
> one doubt.I used the tornado project browser and selected the
> components tab and included under the components under bus,included
> pci bus support.I would like to know from you,the use of prjcomps.h
> header file created for a project and also prjparams.h header
> file.What are contents in these header files reflecting?I guess,that
> when u include any component,it will be automatically defined in
> prjparams.h and prjcoms.h header files under the external
> dependencies.First can any one let me know whether my guess is
> correct,Incase i am correct in guessing,if i include,pci support,I am
> unable to find a #define statement for it like #define
> INCLUDE_PCI in comps.h and also in prjparams.h.
> How can i make sure that the component included in project explorer is
> actually built in ur obj file,after it is built.One thing is it
> notifies by being bold letters,but i am unsatisfied by that proof and
> want to know whether the macros i included is really present in my
> bootable obj file or not,after and before my obj file is built.
> Kindly let me know,further wrt above said,as the bios will have all
> the details of buses and h/w(eg-scsi,pci bus,ata etc..).Will vxworks
> read the bios automatically and report back during boot time or
> something explicitly need to be done to make it recognise and
> display.I am very much interested in particular wrt to pci.
> Any pointers or tutorials or suggestion or website help or advice and
> solutions ,will be of grt help to me.Advanced thanks to person
> replying me.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Common Interview Questions!!
Date: 28 Nov 2002 10:58:54 -0500
From: Bill Pringlemeir <spam_account@sympatico.ca>
Organization: Bell Sympatico
Message-ID: <m2r8d5heip.fsf@sympatico.ca>
References: <cbbd6f8c.0211280203.43aa2e75@posting.google.com>
Sender: bpringle@DeadDuck

  > I want to know that what kind of question can interviewer ask me,
  > if I am applying job else where..  And some tips and pointers to
  > tune myself up in better manner about VxWorks.

I have asked the question "What problems did you encounter using
vxWorks and Tornado".  Usually the people say nothing and I am not
impressed.  If they were to tell me that the simulator was buggy or
DosFS wasn't reliable, or a certain Ethernet driver didn't work, etc.
I would then ask how they solved it.  I believe that this is a "past
behavioral" type question.

I would suggest looking at Johan's FAQ for tips and pointers.  If you
have access to the manuals, they are also very useful.

 "http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html"

fwiw,
Bill Pringlemeir.

- -- 
explosion  benelux MILSATCOM  Medco domestic  disruption cryptographic
FBI MIT-LL Manfurov blackjack  Defcon csim computer terrorism LLNL top
secret

---------------------------

Newsgroups: comp.os.vxworks
Subject: I want to join in you!!
Date: 28 Nov 2002 18:28:23 -0800
From: lvdq@163.net (lvdq)
Organization: http://groups.google.com/
Message-ID: <36a8dab4.0211281828.166c6e98@posting.google.com>

i am interested in Vxworks!!

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Download Procedure
Date: 28 Nov 2002 19:30:09 -0800
From: vxworks@india.com (V R R Raju)
Organization: http://groups.google.com/
Message-ID: <d6e2de0a.0211281930.372f0329@posting.google.com>
References: <d6e2de0a.0211220343.5f0d758@posting.google.com> <8e6507b.0211250559.662910dc@posting.google.com> <d6e2de0a.0211271942.789def83@posting.google.com> <bb8c75e1.0211280035.3e8abbee@posting.google.com>

Dear Sir,

I have been told by experts that the Real Tek chip follows the NE2000
standard and I should include ENE netif BSD Driver. The boot is able
to attach the TCP/IP and after that it is indicating that it is not
able to laod the file that is vxWorks. I m not able to find the MAC
address of the Target system so that I can include it in the
config.h.I have given the IRQ 0x0b (11). What else should I have to
configure in the HOST. I am not able to launch the Target Server in
the HOST machine. Please guide me.

Thanks in Advance.

With reagrds,

V.R.R.Raju

vijay.peshkar@wipro.com (Vijay Peshkar) wrote in message news:<bb8c75e1.0211280035.3e8abbee@posting.google.com>...
> Raju,
> 
> Realtek card is not supported by default. You need to get the driver code
> and add the files in drv\end\unsupported. You should be able to get this patch 
> from wrs or RTL.
> Its a good idea to check up if your rtl card has really been recognised in
> your boot. Also the bootline should read rtl and not ene for this card.
> 
> Hope this is helpful.
> cheers,
> Vijay
> 
> vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211271942.789def83@posting.google.com>...
> > Hi Harry,
> > 
> > I have succeded in Attaching the interface, But not able to boot and
> > the system is giving the same error 0xfd0003. I have changed the IRQ
> > to 11 which has been specified by my Admin but I am not able to do the
> > same with the address. Please let me know the way I can know the
> > address of my ethernet card.
> > 
> > Thanks a lot and hope you will help me in future also.
> > 
> > Bye
> > 
> > V R R Raju
> > 
> > 
> > 
> > harry2405@rediffmail.com (Harry) wrote in message news:<8e6507b.0211250559.662910dc@posting.google.com>...
> > > Hi 
> > > The Realtek family of cards follow the NE2000 standard. So, you need
> > > to
> > > #define INCLUDE_ENE in config.h. This is already defined for you.
> > > 
> > > Also, your boot line is wrong. It shows "fd" (which means floppy) and
> > > you are trying to get vxWorks from floppy, then FTP from 'c:' on your
> > > host. This is whole lot confusing for the target and VxWorks just
> > > hangs. Change fd=0,0(0,0) to ene(0,0). Add password (FTP pw) also to
> > > the boot line. Your boot line should look something like this:
> > > 
> > > "ene(0,0)host:c/tornado/target/config/pc486/vxWorks
> > >  h=131.200.2.244 e=131.200.2.105 u=target pw=target"
> > > 
> > > Then 'make' the following:
> > > 1.vxWorks, **not** vxWorks.st right now.
> > > 2.bootrom_uncmp, 
> > > 3.mkboot a: bootrom_uncmp
> > > 
> > > and reboot the target with the floppy (as you have done already).
> > > If you can see "Attaching network interface ... done", be happy... you
> > > have almost booted the target.
> > > 
> > > Now your target **DOESN'T** boot completely, because, you have not
> > > configured the I/O and IRQ of the target network card. You get an
> > > error 0xfd0003. Catch hold of your admin and get the correct I/O and
> > > IRQ of the card with the correct driver floppy.
> > > 
> > > Edit the config.h file for correct IO_ADRS_ENE and INT_LVL_ENE. Then
> > > build all images and make boot floppy and boot the target. This boots
> > > the target.
> > > 
> > > Good luck..!!
> > > 
> > > Harry.
> > > 
> > > vxworks@india.com (V R R Raju) wrote in message news:<d6e2de0a.0211220343.5f0d758@posting.google.com>...
> > > > Dear Friends,
> > > > 
> > > > I am working on Vxworks 5.4 and Tornado II. I am a newbie and don't
> > > > know how to download the bootable image to target from host using FTP.
> > > > I did what I was told by my friend and it is as follows:
> > > > 
> > > > 1. Configure the Vxworks using the tornado and Include and Exclude the
> > > > components according to application requirements.
> > > > 
> > > > 2. I don't know which Ethernet Driver type to include (ELT or ENT or
> > > > any other). I am using Realtek processor based Ethernet Card. Please
> > > > let me know which Ethernet Drivers should I use.
> > > > 
> > > > 3. What parameter should I specify DEFAULT_BOOT_LINE for hardware
> > > > components properties.
> > > > I am specifying the following
> > > > 
> > > > "fd=0,0(0,0)host:c/tornado/target/config/pc486/vxWorks.st
> > > > h=131.200.2.244 e=131.200.2.105 u=target"
> > > > 
> > > > 4. I am making a bootrom_uncmp image and then copying it to Floppy
> > > > Disk using mkboot a:bootrom_uncmp.
> > > > 
> > > > 5. Then I am trying to boot my target using the floppy.
> > > > 
> > > > 6. I am making a Vxworks.st standalone image.
> > > > 
> > > > 7. I am starting the FTP server by giving the username and password
> > > > and also the home directory in which my image is stored.
> > > > 
> > > > 8. I am executing the image in the target using the @ command after
> > > > changing any parameters using c and P commands.
> > > > 
> > > > 9. Target gets started with saying Loading and suddenly some numbers
> > > > are displayed and it hangs. Even it is not getting connected to the
> > > > FTP server in the Host.
> > > > 
> > > > Please let me know where I have gone wrong and whether the above
> > > > procedure is correct. Also let me know whether there is another way of
> > > > downloading and its procedure which will help me a lot .
> > > > 
> > > > 
> > > > Thanks in advance.
> > > > 
> > > > with regards,
> > > > 
> > > > Rajneesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: how to recompile the vxWorks using make under command line mode??
Date: Fri, 29 Nov 2002 12:07:05 +0800
From: "Seraph Ma" <seraph.ma@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <as6p59$2j1j$1@mail.cn99.com>

Hey,Guys
    I have to recompile the vxowrks kernel using GNU make under command mode
instead of
Tornado IDE enviorment.( my compile enviorment,OS WIN2000,Tornado
2.0.2,vxworks 5.4)
    I have modified some .c files ,so what should I pay attention to if I
wanna rebuild
the kernel. What enviorment variables should i SET? What else -Ds should I
define other
than CPU,TOOL ??
    I just have been blocked with many 'make' problems now~~
    Eager for your warm-hearted help~~~~

    Thanx a lot.
                                     Seraph Ma

---------------------------

Newsgroups: comp.os.vxworks
Subject: PPP port for vxworks
Date: 28 Nov 2002 21:17:07 -0800
From: raj_rashid@hotmail.com (Rashid)
Organization: http://groups.google.com/
Message-ID: <2a6118da.0211282117.6fc7338@posting.google.com>

Hello Friends, 
              On vxworks FAQs website
(http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html) there is was an 
archive about PPP ported to vxworks as pasted below. 

"  I've ported pppd-1.3 to VxWorks 5.1 if anyone is interested.  The
port
is available via anonymous ftp from netcom.com.  cd to
pub/peacefulstar/dab
and get the file vpppd-1.0.tar.gz.  It's public domain. 

Don Brooks dab@netcom.com 
" 

                       The site netcom.com is no longer accessible.
Does anybody have a copy of the file mentioned (vpppd-1.0.tar.gz). If
you have this file please mail it to me.

Thanks for your help, 

regards, 
Rashid

---------------------------

Newsgroups: comp.os.vxworks
Subject: FDD boot first then see boot is ok ! Re: X86 Boot Problem
Date: Fri, 29 Nov 2002 02:02:10 GMT
From: "Mike Kim" <cskim@fdlab.co.kr>
Organization: Dacom
Message-ID: <CUzF9.56257$rN4.1354694@news.bora.net>
References: <484f4f20.0211271751.29c1e6ad@posting.google.com>

Hi~
I'm currently using T2.0 and Zinc5.0(?).

As drdiags said , your T2 seems to T2.2.

I think it would be a another way for finding problem if you
boot using floopy diskette via network boot.
Because booting from floopy is more easy way to find a problem.

And if you see reboot during boot process.

I also saw that if my x86 boad has no IRQ for LAN card(ex. Realtek8139),
because driver for lan doesn't seed to support IRQ sharing.

I'm afraid this would be helpful for you.

Good Luck !

"Jacky Cheung" <jc422@cornell.edu> wrote in message
news:484f4f20.0211271751.29c1e6ad@posting.google.com...
> Hi all,
>    I have just started a project at school using
> VxWorks on a x86 board. I have been trying to
> create a boot disk to boot up VxWorks on the board
> so that I can set the boot parameter. However, the board
> only boots up a certain point after a lot of "+"
> signs, and then it would stall:
>
> V1.6++++++++++++++++++++++++++++++++++++++
> +++++++++++++++++++++++++++++++++++++++++
>                 .
>                 .
>                 .
>
>    I used the mkboot utility and the default
> VxWorks rom that the Pentium BSP provided. Can anyone
> give me a hint on my problem? I would really appreciate
> that. Thank you.
>
>
> Jacky

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for target 2.2
Date: 26 Nov 2002 03:03:52 -0800
From: harry2405@rediffmail.com (Harry)
Organization: http://groups.google.com/
Message-ID: <8e6507b.0211260303.5f079e16@posting.google.com>
References: <20021121210536.05821.00007701@mb-ms.aol.com>

Hi Mahesh,
Try using a clean and new floppy. This should do the trick. I had this
problem earlier and it worked for me. Also, check if your bootrom
image is 'contiguous'. Boot image can't boot if the file bootrom.sys
is non-contiguous on the floppy.

You may not be able to see what's happening when the boot program is
loading. However, you can do the same when vxWorks is booting. You
need to configure your WDB agent as 'extern'. Refer the VxWorks bible:
VxWorks Programmers' guide, for that !

Also, you needn't include FTP or FTP server. Include this if you want
the target to act as a FTP server. You may also leave it like that.
I hope its clear.

Harry.

maheshv26@aol.com (Maheshv26) wrote in message news:<20021121210536.05821.00007701@mb-ms.aol.com>...
> Hi:
> 
> My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
> target Intel X86 and for windows host.
> I have created a Bootrom Image for Network configuration and When i try to boot
> the kernel through the floppy disk, the screen becomes blank and it
> automatically reboots. 
> 
> I will be happy if somebody can provide me with some informatio. Also, is there
> any way to debug and see what is going on underneath the hood.  
> 
> The configuration and software versions are as follows:
> VxWorks - 5.5
> Tornado - 2.2
> CPU - PENTIUM
> C++Compiler - g++pentium (version - 2.93)
> Host - Windows 2000.
> Ethernet Driver - fei82557End Intel Ethernet Driver.
> 
> The config.h is configured using these macros
> INCLUDE_NETWORK
> INCLUDE_END,
> INCLUDE_FEI_END,
> INCLUDE_FTP,
> INCLUDE_FTP_SERVER.
> 
> thanks
> Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: how to recompile the vxWorks using make under command line mode??
Date: Fri, 29 Nov 2002 07:54:16 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <as72uh$8t3$1@snoopy.bndlg.de>
References: <as6p59$2j1j$1@mail.cn99.com>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Hi Seraph,
open DOS-box and change to host\x86-win32\bin. Now call 'torVars.bat'.
All necessary variables should be set now .
Change to your project directory and call e.g. 'make vxWorks'

HTH
Michael

"Seraph Ma" <seraph.ma@utstar.com> schrieb im Newsbeitrag
news:as6p59$2j1j$1@mail.cn99.com...
> Hey,Guys
>     I have to recompile the vxowrks kernel using GNU make under command
mode
> instead of
> Tornado IDE enviorment.( my compile enviorment,OS WIN2000,Tornado
> 2.0.2,vxworks 5.4)
>     I have modified some .c files ,so what should I pay attention to if I
> wanna rebuild
> the kernel. What enviorment variables should i SET? What else -Ds should I
> define other
> than CPU,TOOL ??
>     I just have been blocked with many 'make' problems now~~
>     Eager for your warm-hearted help~~~~
>
>
>     Thanx a lot.
>                                      Seraph Ma
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: strange problem while building bootrom_uncmp.
Date: 28 Nov 2002 23:04:41 -0800
From: vxnerd@rediffmail.com (subbarayan)
Organization: http://groups.google.com/
Message-ID: <f81c4277.0211282304.2061eb12@posting.google.com>

Dear mentors,
I use tornado2.0,pc486 target,standalone configuration.
1)Can any one point to me when will I get the following message when i
try to build bootrom_uncmp from tornado gui?
make.exe: `bootrom_uncmp' is up to date.
Becos i expect when u change something in ur source or add or remove
some components in GUI or change the userappinit.c file,Bootrom to
build properly.
My case is this:First i made a source code.Then compiled it and made a
bootrom_uncmp.First time it built properly.Next time ,After that I
thought of making some modifications in source and rebuild
bootrom_uncmp,I got the above message.The same case with vxworks.st
file.compilation is fine for source code.Problem is only with
bootrom_uncmp and vxworks.st .
Is this behaviour normal?or theres some error in my way of working and
understanding?what are the dependencies for bootrom_uncmp or when
should i rebuild bootrom_uncmp and also vxworks.st?
2)When ever u add an component in the gui,I guess it reflects in the
prjparams.h and prjcomps.h files.First let me whether my understanding
in this regards is correct or not?Incase I am right,can anyone point
me what will be following problem due to?
I include the pci bus support from gui under hardware.I don't find it
getting reflected in the above header files.What should i do to make
it reflect in the above said header files as soon as i add or remove a
component from GUI?Or is there some duration after which it gets
reflected there?
Advanced thanks to person replying me.Sorry if i look too amature,I am
on learning stage and no one around to help me nearby.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: how to recompile the vxWorks using make under command line mode??
Date: Fri, 29 Nov 2002 15:09:13 +0800
From: "Seraph Ma" <seraph.ma@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <as73qq$2s0n$1@mail.cn99.com>
References: <as6p59$2j1j$1@mail.cn99.com> <as72uh$8t3$1@snoopy.bndlg.de>

Michael
        Of cource should I call 'torVars.bat'. Yeah, I have already call
this bat file.
        What I wanna compile is vxWorks kernel. Our company has bought
WINDRIVER's network
source files( .c and .h,makefile ),I have made some modifications on these
source codes,and now I wanna rebuild the changed files and link these built
.o to vxworks kernel.
        That's what I wanna do .
        But still thank you so much.

"Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message
news:as72uh$8t3$1@snoopy.bndlg.de...
> Hi Seraph,
> open DOS-box and change to host\x86-win32\bin. Now call 'torVars.bat'.
> All necessary variables should be set now .
> Change to your project directory and call e.g. 'make vxWorks'
>
> HTH
> Michael
>
> "Seraph Ma" <seraph.ma@utstar.com> schrieb im Newsbeitrag
> news:as6p59$2j1j$1@mail.cn99.com...
> > Hey,Guys
> >     I have to recompile the vxowrks kernel using GNU make under command
> mode
> > instead of
> > Tornado IDE enviorment.( my compile enviorment,OS WIN2000,Tornado
> > 2.0.2,vxworks 5.4)
> >     I have modified some .c files ,so what should I pay attention to if
I
> > wanna rebuild
> > the kernel. What enviorment variables should i SET? What else -Ds should
I
> > define other
> > than CPU,TOOL ??
> >     I just have been blocked with many 'make' problems now~~
> >     Eager for your warm-hearted help~~~~
> >
> >
> >     Thanx a lot.
> >                                      Seraph Ma
> >
> >
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Large App in Boot ROM
Date: Tue, 26 Nov 2002 16:57:41 +0200
From: "Martin Roth" <bmr006@email.mot.com>
Organization: Motorola
Message-ID: <as0266$lii$1@newshost.mot.com>
References: <3DC7F74D.4090702@minn.teradyne.com> <2222d8d3.0211171329.2f511acc@posting.google.com> <3DD965B7.7000207@minn.teradyne.com> <476efddf.0211260349.10ddef1b@posting.google.com>

Joe,

You do not have to jump to the dual-port memory in order to remap.

You boot from 0x100 in flash. The first instruction jumps to the mapped
area. I assume that CSO by OR0/BR0 cover the range you want to map after
RESET.
If the address is out of the flash memory range, it is rapped around.

Now you need to correct the OR0/BR0 which place the base address at the
correct location and this concludes the mapping.  This how I did for 860.

Martin Roth
Motorola Communications Israel

"Joe DeVincentis" <devoz@appiancom.com> wrote in message
news:476efddf.0211260349.10ddef1b@posting.google.com...
> Another option I haven't seen mentioned is to modify the
> hardware designs to boot to 0x100.  This allows you to
> store the bootstrap image at the base of the flash,
> offset by 0x100.  In the bootstrap code you would need
> to add code that executes from dual-port memory and
> remaps OR0/BR0 to place the flash where you ultimately
> want it to reside in the address map.  You copy that
> sequence to dual-port, jump there, the chip select
> is remapped, you jump to the new address space and
> continue with the bootstrap.  This lets you pretty much
> chose any option, and make the most out of your flash.
>
> I have implemented this technique on 8260 and other powerQuicc
> cpus.
>
> Joe
>
>
>
> Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message
news:<3DD965B7.7000207@minn.teradyne.com>...
> > Brent,
> >
> > Thanks, very helpful.  Caused me to look more closely at the defs.bsp
> > file... Strange, looks like they sort of have the problem surround
automagically,
> > but not entirely, apparently:
> >
> > . . .
> > ## bsp flags
> >
> > LD_LOW_FLAGS    = -Ttext $(RAM_LOW_ADRS)
> > LD_HIGH_FLAGS   = -Ttext $(RAM_HIGH_ADRS)
> > RES_LOW_FLAGS   = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_LOW_ADRS)
> > RES_HIGH_FLAGS  = -Ttext $(ROM_TEXT_ADRS) -Tdata $(RAM_HIGH_ADRS)
> >
> > ROM_ENTRY       = _romInit
> > SYS_ENTRY       = _sysInit
> > USR_ENTRY       = _usrInit
> >
> > LDFLAGS         = -X -N
> > LD_PARTIAL_FLAGS= -X -r
> > . . .
> >
> >
> > It seems to me that the RES_LOW_FLAGS is more or less approprate, as I
want
> > the code loaded to the RAM at that address, but I wonder if I can burn
the
> > Flash with the ice as is... short of two seperate
> > burns with the VisionICE, with two seperate bias and offset values.
> >
> > We recently had to upgrade to a newer gnu compiler to support >32M
> > jumps and have also seen problems with the elfHex (bin to hex) program,
> > any issues you've noticed?
> >
> >
> > Thanks Again,
> > -Keith
> >
> >
> >
> > brentb wrote:
> >
> > > Keith,
> > >
> > > I am also using a MPC8245 and have experienced this problem.  For
example,
> > > the vxWorks_rom image consists of text, data, and bss.  The text
section
> > > consists of romInit.s and romStart.c. During compilation, the actual
vxWorks.o
> > > image is converted entirely to .data, hence the use of binArrayStart
and
> > > binArrayEnd in the copy process in romStart. In the final link line of
the
> > > make file output, there is a flag that specifies where the text
section
> > > will be located (-Ttext fff00100), at fff00100.  You can just add a
line
> > > to the flags to specify the location of the .data section using the
following:
> > > -Tdata <data location>, i.e. -Tdata ff80000.  Let me know if that
helps.
> > >
> > > -Brent
> > >
> > > Keith Obrien <obrienk.spam@minn.teradyne.com> wrote in message
news:<3DC7F74D.4090702@minn.teradyne.com>...
> > >
> > >>We are using a MPC8245 that has a boot vector at fff00100 (~1M) upper
rom
> > >>remaining.  Our application is spread over several projects and is
> > >>on the order of 4 Megabytes.  We have significant ROM and RAM
> > >>resources (e.g., 16M / 128M).
> > >>
> > >>Question:
> > >>--------------------
> > >>1) Is there an easy way to put the image to be copied from ROM to
> > >>RAM in a different location other than contiguously with the BOOT ROM,
> > >>e.g., boots at FFF00100, but copylongs/unzip copies from FF800000.
> > >>
> > >>
> > >>Anyone had any experience with this issue?
> > >>
> > >>
> > >>Thanks,
> > >>Keitho
> > >>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Is It Possible to Have Both Host and Target Shells with Tornado 2.1?
Date: Tue, 26 Nov 2002 16:00:00 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <as029c$5pr$1@snoopy.bndlg.de>
References: <of8dg1kd.fsf@sandia.gov> <Xns92D1EACF570C7jborkhuisproximcom@192.19.193.66> <znrw1j0i.fsf@sandia.gov>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Hi Tad,

but network is up and running, i.e. ftp and/or telnet are working?

Michael

<taashlo@sandia.gov> schrieb im Newsbeitrag news:znrw1j0i.fsf@sandia.gov...
> Johan Borkhuis <JBorkhuis@proxim.com> writes:
> > taashlo@sandia.gov wrote:
> >
> > > I have since upgraded to Tornado 2.1 (VxWorks 5.4.2) and a
> > > new BSP version.  I didn't change any of the config.h options
> > > that I thought would relate to having both shells active, but
> > > the new version only has the target shell.  (When the target
> > > shell boots up I *don't* see "WDB: Ready" in the banner and
> > > "tWdbTask" is *not* in the task list.)
> >
> > You have to include WDB in your build. After you include this you will
see
> > the WDB ready prompt again.
> >
> > Kind regards,
> >         Johan
> >
> > --
> >         o o o o o o o . . .   _____________________________
> >        o      _____           ||    Johan Borkhuis        |
> >      .][__n_n_|DD[  ====_____  |    JBorkhuis@Proxim.com  |
> >     >(________|__|_[_________]_|__________________________|
> >     _/oo OOOOO oo`  ooo   ooo  'o!o!o                o!o!o`
> > === VxWorks FAQ: http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html ===
>
>
> I guess I deserved that. :-(
>
> Yes, INCLUDE_WDB is defined.  Just as I had it defined when using
> Tornado 2.0 and both shells were working.  I guess I'm asking if
> something changed between Tornado 2.0 and 2.1 that would impact
> both shells being enabled.  Or, if somebody knows the "official"
> configuration for having both shells enabled (assuming that my
> configuration accidently took advantage of a "loophole" in
> Tornado 2.0).
>
> I even put the following in my BSP's sysLib.c to prove to myself
> that INCLUDE_WDB isn't getting #undef'd somewhere along the way:
>
> #ifdef INCLUDE_WDB
> #warning *** WDB IS INCLUDED ***
> #endif
>
> The warning message showed up during compilation so I believe
> that INCLUDE_WDB is #defined.  But there is still no host shell,
> no "WDB: Ready" in the banner, and no "tWdbTask".
>
> Thank you,
>
> Tad

---------------------------

Newsgroups: comp.os.vxworks
Subject: Memory Mapping with cacheDmaMalloc
Date: 29 Nov 2002 00:20:30 -0800
From: gregory.holmes@baesystems.com (Greg Holmes)
Organization: http://groups.google.com/
Message-ID: <2592b7d6.0211290020.347c7686@posting.google.com>

Hi there VxWorkers!

I wondered if someone could help me with the problem of using
cacheDmaMalloc.
I'm trying to use cacheDmaMalloc to allocate a buffer of memory below
16mb. The 8237 DMA chip on the Ampro Pentium board I'm using only has
an address 24 bits wide. I have 64mb of memory and cacheDmaMalloc is
returning an address of around 3F0D000 which is beyond what I can
address with the 8237 DMA register. As the argument to cacheDmaMalloc
is the size of the buffer to allocate how can I make it address the
memory below 16mb.

Thanks for you help in advance.

Greg Holmes

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Tornado 2.2 for X86
Date: 26 Nov 2002 09:45:51 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211260945.6043ead4@posting.google.com>
References: <20021121203910.05840.00005962@mb-ms.aol.com> <488e459a.0211221300.549ea28b@posting.google.com> <4f7acce6.0211242056.750e9b6a@posting.google.com>

Hello,

> I have changed the default setting for Vga console to PC Console and
> created a bootrom floppy. If i boot the kernel with that floppy i
> still get the see the same problem. I feel something might be wrong
> with my configuration.

What messages were displayed on the console? Better still, leave the
configuration using the serial port, capture the output and post it
here so we can see it.

In fact, I would suggest that you do the following:

1) Using a fresh (never used, or freshly formatted) floppy disk,
create a boot floppy from the image that was on installed from CD (if
you overwrote this, re-install Tornado and make a copy of the BSP so
that you always have the original BSPs and projects as a reference
set)

2) Connect a PC's serial port to the target's serial port, and run
HyperTerminal.

3) Insert the boot floppy, and reset the target (or switch it on)

You should see the '+' signs on the PC's monitor, then it should
display a message on the serial port and start counting down. Cut and
paste everything from the initial message to the time it reboots (stop
it at the second countdown by pressing a key on host's keyboard). Then
post that output here.

Also, you might want to tell us the following:

a) What kind of network card you are using (what is the exact version
of the controller on the card).

b) What are your bootline settings? Have you set the IP address etc
correctly? Are you host and target on the same subnet? If not, have
you configured the gateway address correctly?

c) Have you configured the ftp server on your host (as was stated in
another response, you don't need the one on the target system to boot,
but you do need to configure Windows to have one since you are using
Windows as a host)? If you have configured it, then, from another PC,
try using ftp to get the boot image - Windows has a command line ftp
client - just open a command prompt, and type ftp followed by the IP
address of your host PC.
 
Rgds,

John...

> Please bear with my lack of experience. Iam attaching the config.h and
> configNet.h for your reference....anything seem blatantly wrong? I
> will be happy if you can have a look at it and letme know if iam
> missing something.
> 
> thanks
> Mahesh
> 
> /*************************** CONFIG.H
> ***************************************/
> /* config.h - template configuration header file */
> 
> /* Copyright 1984-2002 Wind River Systems, Inc. */
> 
> /*
> TODO -	Remove the template modification history and begin a new
> history
> 	starting with version 01a and growing the history upward with
> 	each revision.
> 
> modification history
> --------------------
> 01y,18apr02,rhe  Added C++ Protection
> 01x,20dec01,cjj  Changed RAM_HIGH_ADRS to 0x200000
> 01w,09dec01,dat  Adding USB support for ARM, MIPS, PPC, PENTIUM, SH,
> added
> 		 optional TFFS support for all.
> 01v,15dec00,pai  Simplified the network configuration macros used in
> this file.
>                  References to INCLUDE_BSD, INCLUDE_DEFER_NET_INIT,
> and
>                  INCLUDE_NET_INIT have been removed.  This template
> config.h
>                  now specifies INCLUDE_NETWORK and INCLUDE_END.  The
> remaining
>                  network configuration comes from configAll.h.
> 01u,11dec00,pai  made END driver support the default for new WRN code.
> 01t,11dec00,pai  introduced INCLUDE_DEFER_NET_INIT configuration
> constant for
>                  new WRN code.
> 01s,08apr99,dat  SPR 26491, fixed PCI macro names
> 01r,29mar99,dat  SPR 26125, added INCLUDE_BSD
> 01q,02feb99,tm   added PCI AutoConfig support to template BSPs (SPR
> 24733)
> 01p,28sep98,dat  added default PCI and VME macros
> 01o,07nov98,dat  added note about the values for ROM_TEXT_ADRS, and
> 		 ROM_WARM_ADRS
> 01n,21jul98,db   defined INCLUDE_NETWORK, changed ROM_SIZE to 0x40000.
> 01m,07jul98,db   changed BSP_VERSION to "1.2" and BSP_REVISION to
> "/0".
> 		 added BSP_VER_1_2 macro, defined INCLUDE_END, removed
> 		 END_OVERRIDE(Tornado 2.0 release).
> 01l,25aug97,dat  code review comments from Kitty
> 01k,07jul97,dat  added supported for new END ethernet drivers
> 01j,23apr97,dat  added ROM_WARM_ADRS, INCLUDE_CDROMFS
> 01i,02apr97,dat  more documentation about VME and other macros.
> 01h,12mar97,dat  added VME mapping macros
> 01g,10mar97,dat  comments from reviewers
> 01f,28feb97,dat  added INCLUDE_USER_APPL, USER_APPL_INIT
> 01e,05feb97,dat  incorporated comments from Thierry P.
> 01d,23jan97,dat  moved timer constants to template.h
> 01c,17jan97,dat  added INCLUDE_SERIAL, INCLUDE_MMU, INCLUDE_VME
> 01b,16jan97,dat  added LOCAL_MEM_AUTOSIZE and moved INCLUDE_SCSI2
> outside
> 		 of #if FALSE.
> 01a,22oct96,ms   derived from the mv147 BSP
> */
> 
> /*
> This file contains the configuration parameters for the template BSP.
> This template starts simple - with most facilities excluded by
> default.
> 
> TODO -
> Present the user with simple straight forward options.  Do not ask the
> user to encode values together to form a value to be loaded in a
> register.
> Let the source code, or the pre-processor, do the computational work
> to
> determine what value to load in a particular register.
> */
> 
> #ifndef	INCconfigh
> #define	INCconfigh
> 
> #ifdef __cplusplus
> extern "C" {
> #endif
> 
> /* BSP version/revision identification, before configAll.h */
> 
> #define BSP_VER_1_1	1	/* 1.2 is backward compatible with 1.1 */
> #define BSP_VER_1_2	1
> #define BSP_VERSION	"1.2"
> #define BSP_REV		"/0"	/* 0 for first revision */
> 
> #include "configAll.h"		/* Set the VxWorks default configuration */
> #include "pc.h"
> 
> #define DEFAULT_BOOT_LINE \
> 	"fei(0,0)/distcomp/wind/target/config/pcPentium2_2/vxWorks " \
> 	"h=132.200.200.13 e=132.200.200.84 u=taoadmin pw=tao+oci tn=vx86"
> 
> /* TODO - values in this header file are dummy values, update as
> needed */
> 
> /* memory configuration */
> 
> #define LOCAL_MEM_LOCAL_ADRS	0		/* fixed at zero */
> #undef	LOCAL_MEM_AUTOSIZE			/* run-time memory sizing */
> #define LOCAL_MEM_SIZE		0x400000	/* 4M memory */
> #define	USER_RESERVED_MEM	0		/* see sysMemTop() */
> 
> /*
>  * The constants ROM_TEXT_ADRS, ROM_SIZE, RAM_HIGH_ADRS, and
> RAM_LOW_ADRS
>  * are defined in config.h and Makefile.
>  * All definitions for these constants must be identical.
>  *
>  * TODO - Make sure these values match those in your Makefile.  The
> values
>  * shown below are the defaults for a 68000 series system.  Pay
> particular
>  * attention to ROM_TEXT_ADRS and ROM_WARM_ADRS.  The correct default
> values
>  * are in the Makefile for each template BSP.
>  */
> 
> #define ROM_BASE_ADRS		0xff800000	/* base address of ROM */
> #define ROM_TEXT_ADRS		(ROM_BASE_ADRS+8) /* with PC & SP */
> #define ROM_WARM_ADRS		(ROM_TEXT_ADRS+8) /* warm reboot entry */
> #define ROM_SIZE		0x00040000	/* 256KB ROM space */
> #define RAM_HIGH_ADRS		0x00200000	/* RAM address for bootrom */
> #define RAM_LOW_ADRS		0x00010000	/* RAM address for vxWorks */
> 
> /* Serial port configuration */
> 
> /* Commented for Now */
> /* #define	INCLUDE_SERIAL */
> #define INCLUDE_PC_CONSOLE
> 
> #ifdef  INCLUDE_PC_CONSOLE
> #define PC_CONSOLE              0
> #undef  N_VIRTUAL_CONSOLES
> #define N_VIRTUAL_CONSOLES      2
> 
> #define KBD_INT_VEC             (INT_VEC_GET (KBD_INT_LVL))
> 
> #endif
> #undef	NUM_TTY
> #define	NUM_TTY			(N_UART_CHANNELS)	 /* defined in template.h */
> 
> #define PC_KBD_TYPE             PC_PS2_101_KBD
> 
> /* Timer configuration */
> 
> #undef  INCLUDE_TIMESTAMP		/* no timestamp driver support */
> 
> /*
>  * Cache configuration
>  *
>  * TODO -
>  * All cache is turned off to begin with. Activate caching after basic
>  * BSP functionality is achieved.  Start with instruction caching,
> followed
>  * by data caching.  Begin without snooping options; and turn those on
>  * later if the board supports it.
>  *
>  * Note that when MMU is enabled, cache modes are controlled by
>  * the MMU table entries in sysPhysMemDesc[], not the cache mode
>  * macros defined here.
>  */
> 
> #undef	INCLUDE_CACHE_SUPPORT	/* no cacheLib support */
> #undef	USER_I_CACHE_ENABLE
> #undef	USER_I_CACHE_MODE
> #define	USER_I_CACHE_MODE	CACHE_DISABLED
> #undef	USER_D_CACHE_ENABLE
> #undef	USER_D_CACHE_MODE
> #define	USER_D_CACHE_MODE	CACHE_DISABLED
> #undef	USER_B_CACHE_ENABLE
> 
> /* MMU configuration */
> 
> #undef	INCLUDE_MMU_BASIC	/* no MMU support */
> #undef	INCLUDE_MMU_FULL	/* no MMU support */
> 
> /* Network driver configuration */
> 
> #define	INCLUDE_NETWORK
> #define	INCLUDE_END		/* Enhanced Network Driver (see configNet.h) */
> 
> #undef	INCLUDE_EX
> #undef	INCLUDE_ENP
> #undef	INCLUDE_SM_NET
> 
> /* VME configuration */
> 
> /*
>  * TODO -
>  * Only those options that are actually user changeable should be
> defined
>  * here.  Options that cannot be changed should be moved to
> template.h.
>  */
> 
> #undef	INCLUDE_VME
> 
> /* A16 master window maps all of A16 to 0xff800000 locally */
> 
> #define	VME_A16_MSTR_BUS	0x0
> #define	VME_A16_MSTR_SIZE	0x00010000
> #define	VME_A16_MSTR_LOCAL	0xff800000
> 
> /* A24 master window maps all of A24 to 0xf8000000 locally */
> 
> #define	VME_A24_MSTR_BUS	0x0
> #define	VME_A24_MSTR_SIZE	0x01000000
> #define	VME_A24_MSTR_LOCAL	0xf8000000
> 
> /* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
> local. */
> 
> #define	VME_A32_MSTR_BUS	(0x80000000)
> #define	VME_A32_MSTR_SIZE	(0x02000000)
> #define	VME_A32_MSTR_LOCAL	(0x80000000)
> 
> /* A16 slave window is not supported */
> 
> #define	VME_A16_SLV_LOCAL	0x0
> #define	VME_A16_SLV_BUS		0x0
> #define	VME_A16_SLV_SIZE	0x0
> 
> /* A24 slave window maps 1st 8MB of local memory to bus address
> 0x00800000 */
> 
> #define	VME_A24_SLV_LOCAL	LOCAL_MEM_LOCAL_ADRS
> #define	VME_A24_SLV_BUS		0x00800000
> #define	VME_A24_SLV_SIZE	0x00800000
> 
> /* A32 slave window maps all local memory to bus address 0x80000000 */
> 
> #define	VME_A32_SLV_LOCAL	(LOCAL_MEM_LOCAL_ADRS)
> #define	VME_A32_SLV_BUS		0x80000000
> #define	VME_A32_SLV_SIZE	((UINT)sysPhysMemTop() -
> LOCAL_MEM_LOCAL_ADRS)
> 
> /* PCI configuration */
> 
> #undef	INCLUDE_PCI
> #undef  INCLUDE_PCI_AUTOCONF
> 
> #ifndef PCI_CFG_TYPE
> #   ifdef INCLUDE_PCI_AUTOCONF
> #      define PCI_CFG_TYPE PCI_CFG_AUTO
> #   else
> #      define PCI_CFG_TYPE PCI_CFG_FORCE
> #   endif /* INCLUDE_PCI_AUTOCONF */
> #endif /* PCI_CFG_TYPE */
>  
> 
> /*
>  * TODO -
>  * Only those options that are actually user changeable should be
> defined
>  * here.  Options that cannot be changed should be moved to
> template.h.
>  */
> 
> /* PCI I/O master window */
> 
> #define	PCI_MSTR_IO_LOCAL	0xff800000
> #define	PCI_MSTR_IO_BUS		0x0
> #define	PCI_MSTR_IO_SIZE	0x00010000
> 
> /* PCI MEMIO master (non-prefetch memory) window */
> 
> #define	PCI_MSTR_MEMIO_LOCAL	0xf8000000
> #define	PCI_MSTR_MEMIO_BUS	0x0
> #define	PCI_MSTR_MEMIO_SIZE	0x01000000
> 
> /* PCI MEM master (prefetchable memory) window */
> 
> #define	PCI_MSTR_MEM_LOCAL	0xfa000000
> #define	PCI_MSTR_MEM_BUS	0x0
> #define	PCI_MSTR_MEM_SIZE	0x01000000
> 
> /* A32 master window maps 32MB from bus 0x80000000 to 0x80000000
> local. */
> 
> #define	VME_A32_MSTR_BUS	(0x80000000)
> #define	VME_A32_MSTR_SIZE	(0x02000000)
> #define	VME_A32_MSTR_LOCAL	(0x80000000)
> 
> /* A16 slave window is not supported */
> 
> #define	VME_A16_SLV_LOCAL	0x0
> #define	VME_A16_SLV_BUS		0x0
> #define	VME_A16_SLV_SIZE	0x0
> 
> /* A24 slave window maps 1st 8MB of local memory to bus address
> 0x00800000 */
> 
> #define	VME_A24_SLV_LOCAL	LOCAL_MEM_LOCAL_ADRS
> #define	VME_A24_SLV_BUS		0x00800000
> #define	VME_A24_SLV_SIZE	0x00800000
> 
> /* A32 slave window maps all local memory to bus address 0x80000000 */
> 
> #define	VME_A32_SLV_LOCAL	(LOCAL_MEM_LOCAL_ADRS)
> #define	VME_A32_SLV_BUS		0x80000000
> #define	VME_A32_SLV_SIZE	((UINT)sysPhysMemTop() -
> LOCAL_MEM_LOCAL_ADRS)
> 
> /* SCSI driver configuration */
> 
> #if	FALSE			/* change FALSE to TRUE for SCSI interface */
> #define	INCLUDE_SCSI		/* include SCSI interface */
> #define	INCLUDE_SCSI_DMA	/* include SCSI DMA interface */
> #define	INCLUDE_SCSI_BOOT	/* include SCSI for boot option */
> #define	INCLUDE_DOSFS		/* DOS file system */
> #undef	INCLUDE_TAPEFS		/* tape file system */
> #undef	INCLUDE_CDROMFS		/* CD-ROM (iso9660) file system */
> #define SYS_SCSI_CONFIG		/* BSP scsi config routine */
> #endif	/* FALSE/TRUE */
> 
> /* Select either SCSI-1 or SCSI-2, independent of INCLUDE_SCSI */
> 
> #define INCLUDE_SCSI2		/* undef for SCSI-1 support */
> 
> /*
>  * User application initialization
>  *
>  * USER_APPL_INIT must be a valid C statement or block.  It is
>  * included in the usrRoot() routine only if INCLUDE_USER_APPL is
>  * defined.  The code for USER_APPL_INIT is only an example.  The
>  * user is expected to change it as needed.  The use of taskSpawn
>  * is recommended over direct execution of the user routine.
>  */
> 
> #undef	INCLUDE_USER_APPL
> #define	USER_APPL_INIT \
> 	{ \
> 	IMPORT int myAppInit(); \
> 	taskSpawn ("myApp", 30, 0, 5120, \
> 		   myAppInit, 0x1, 0x2, 0x3, 0,0,0,0,0,0,0); \
> 	}
> 
> /* Configurable interrupt vectors/levels (static defs go in
> template.h) */
> 
> #if	FALSE
> #define	INT_VEC_ABORT		xxx
> #define	INT_VEC_CLOCK		xxx
> ...
> #define	INT_LVL_ABORT		xxx
> #define	INT_LVL_CLOCK		xxx
> ...
> #endif
> 
> /* Basic USB Support (PPC, PENTIUM, ARM, MIPS, SH only) */
> 
> #if FALSE	/* set TRUE to include USB support */
> 
> /* USB Host Components */
> 
> #   define INCLUDE_USB 			/* Main USB Component */
> #   undef  INCLUDE_USB_INIT		/* USB Initialization */
> #   define INCLUDE_UHCI			/* UHCI Controller Driver */
> #   undef  INCLUDE_UHCI_INIT    	/* UHCI Initialization */
> #   define INCLUDE_OHCI			/* OHCI Controller Driver */
> #   undef  INCLUDE_OHCI_INIT		/* OHCI Initialization */
> #   undef  INCLUDE_OHCI_PCI_INIT 	/* OHCI PCI Initialization */
> #   define INCLUDE_USBTOOL		/* usbTool Application */
> #   undef  INCDLUE_USB_AUDIO_DEMO	/* USB Audio Demo */
> #   define INCLUDE_USB_MOUSE 		/* USB Mouse Driver */
> #   undef  INCLUDE_USB_MOUSE_INIT 	/* Mouse Driver Initialization */
> #   define INCLUDE_USB_KEYBOARD 	/* USB Keyboard Driver */
> #   undef  INCLUDE_USB_KEYBOARD_INIT 	/* Keyboard Driver
> Initialization */
> #   define INCLUDE_USB_PRINTER 		/* USB Printer Driver */
> #   undef  INCLUDE_USB_PRINTER_INIT 	/* Printer Driver Initialization
> */
> #   define INCLUDE_USB_SPEAKER 		/* USB Speaker Driver */
> #   undef  INCLUDE_USB_SPEAKER_INIT 	/* Speaker Driver Initialization
> */
> #   undef  INCLUDE_USB_MS_BULKONLY 	/* USB Bulk Driver */
> #   undef  INCLUDE_USB_MS_BULKONLY_INIT /* Bulk Driver Initialization
> */
> #   undef  INCLUDE_USB_MS_CBI 		/* USB CBI Driver */
> #   undef  INCLUDE_USB_MS_CBI_INIT 	/* CBI Driver Initialization */
> #   undef  INCLUDE_USB_PEGASUS_END 	/* USB Pegasus Network Driver */
> #   undef  INCLUDE_USB_PEGASUS_END_INIT /* Pegaus Driver
> Initialization */
> 
> /*  USB Parameters */
> 
> #   define BULK_DRIVE_NAME "/bd" 		/* Bulk Drive Name */	
> #   define CBI_DRIVE_NAME "/cbid" 		/* CBI Drive Name */
> #   define PEGASUS_IP_ADDRESS "90.0.0.3" 	/* Pegasus IP Address */
> #   define PEGASUS_DESTINATION_ADDRESS "90.0.0.53" /* Destination IP
> Address */
> #   define PEGASUS_NET_MASK 0xffffff00 		/* Pegasus Net Mask */
> #   define PEGASUS_TARGET_NAME "host" 		/* Pegasus Target Name */
> 
> #endif /* End of optional USB support */
> 
> /* Optional TFFS support.  Just define INCLUDE_TFFS to activate */
> 
> #undef	INCLUDE_TFFS
> 
> #include "template.h"		/* Verify user options, specify i/o addr etc */
> 
> #undef INCLUDE_MMU_BASIC      /* bundled mmu support */
> #undef INCLUDE_CACHE_SUPPORT  /* cache support */
> 
> #ifdef __cplusplus
> }
> #endif
> 
> #endif	/* INCconfigh */
> #if defined(PRJ_BUILD)
> #include "prjParams.h"
> #endif
> /******************************************************************************************************/
> 
> /**************************** ConfigNet.h
> ******************************************************/
> /* configNet.h - network configuration header */
> 
> /* Copyright 1984-2002 Wind River Systems, Inc. */
> 
> /*
> TODO -	Remove the template modification history and begin a new
> history
> 	starting with version 01a and growing the history upward with
> 	each revision.
> 
> modification history
> --------------------
> 01e,28may02,dat  exclude driver if NETWORK not defined, 77135
> 01d,18apr02,rhe  Added C++ Protection
> 01c,13dec00,pai  corrected endDevTbl[] definition (SPR #62994) and
> specified
>                  the return type in the END_LOAD_FUNC declaration.
> 01b,21jul98,db   dec21x40End replaced with template END driver. 
> 01a,07jul97,dat  written (from mv2603/configNet.h,ver 01b)
> */
>  
> #ifndef INCnetConfigh
> #define INCnetConfigh
> 
> #ifdef __cplusplus
> extern "C" {
> #endif
> 
> #ifdef INCLUDE_NETWORK /* ignore everything if NETWORK not included */
> 
> #include "vxWorks.h"
> #include "end.h"
> 
> /* This template presumes the template END driver */
> 
> #define FEI82557_LOAD_FUNC	fei82557EndLoad
> #define FEI82557_BUFF_LOAN      1
> 
> /* <devAdrs>:<PCIadrs>:<ivec>:<ilevel>:<memBase>:<memSize>:<userFlags>
> */
> 
> #define	FEI82557_LOAD_STRING	"-1:0x00:0x20:0x20:0x00"
> 
> IMPORT END_OBJ * FEI82557_LOAD_FUNC ();
> 
> END_TBL_ENTRY endDevTbl [] =
>     {
>     { 0, FEI82557_LOAD_FUNC, FEI82557_LOAD_STRING, FEI82557_BUFF_LOAN,
> NULL, FALSE},
>     { 0, END_TBL_END, NULL, 0, NULL},
>     };
> 
> #ifdef __cplusplus
> }
> #endif
> 
> #endif /* INCLUDE_NETWORK */
> #endif /* INCnetConfigh */
> 
> 
> 
> 
> 
> 
> john_94501@yahoo.com (John) wrote in message news:<488e459a.0211221300.549ea28b@posting.google.com>...
> > Hello,
> > 
> > > My name is Mahesh, Iam working on creating and Configuring VxWorks Kernel for
> > > target Intel X86 and for windows host.
> > > I have created a Bootrom Image for Network configuration and When i try to boot
> > > the kernel through the floppy disk, the screen becomes blank and it
> > > automatically reboots. 
> > 
> > You need to change the console settings. In the newer versions of
> > VxWorks, including AE 1.x and 5.5, the default setting for the console
> > is the serial port (COM1 using DOS style naming, /tyCo/0 in VxWorks).
> > 
> > You can switch back to the VGA console if you need to (search the
> > archives for this group - it has been covered before), or you can
> > simply connect a terminal (or PC running HyperTerminal) to the serial
> > port and use that.
> > 
> > HTH,
> > 
> > John...
> >  
> > > I will be happy if somebody can shed some on it. Also, is there any way to
> > > debug and see what is going on underneath the hood.  
> > > 
> > > The configuration and software versions are as follows:
> > > VxWorks - 5.5
> > > Tornado - 2.2
> > > CPU - PENTIUM
> > > C++Compiler - g++pentium (version - 2.93)
> > > Host - Windows 2000.
> > > Ethernet Driver - fei82557End Intel Ethernet Driver.
> > > 
> > > The config.h is configured using these macros
> > > INCLUDE_NETWORK
> > > INCLUDE_END,
> > > INCLUDE_FEI_END,
> > > INCLUDE_FTP,
> > > INCLUDE_FTP_SERVER.
> > > 
> > > thanks
> > > Mahesh

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: commit_and_inc: VirtualAlloc failed
Date: 26 Nov 2002 09:59:54 -0800
From: john_94501@yahoo.com (John)
Organization: http://groups.google.com/
Message-ID: <488e459a.0211260959.3f71f0f@posting.google.com>
References: <3DE33157.61826600@rbg42.siemens.de>

Hello,

I would suspect that you have discovered a compiler problem... You
could try a number of things:

1) Work out which optimisations are enabled by the -Os flag, but not
by -O1 and try them one at a time - most can be enabled/disabled
through -f options.

2) Try -O2 - and disable some of the things that cause the size to
grow (e.g. loop unrolling).

3) Accept that this file causes the compiler to have problems, and
compile just this one file with -O1 (or does the error occur with
many/all of your source files?)

4) Discover why all the error messages are being displayed before the
compiler runs out of memory... Do you get these errors (or even any
warnings) when compiling with -O1?

Finally, try to generate a pre-processed version of the file using the
- -E option, and submit it to Wind River's support folks complete with
the command line that causes it to fail. That way at least they can
check if there is a known workaround for the problem.

HTH,

John...

"Juergen Hahn (S)" <juergen.hahn@rbg42.siemens.de> wrote in message news:<3DE33157.61826600@rbg42.siemens.de>...
> Hi,
> 
> is there anybody out there, who can explain me, why this compile error
> occurs?
> If we use "-O1" instead of "-Os", the problems goes away... but we want
> to use "-Os" for size issues.
> 
> Some info: Tornado 2.1 for Hitach SH, no patches so far installed,
> memory on NT-PC is 256MB Ram, 1GB Swap, but problem occurs every time
> and independent of PC.
> 
> Thanks in advance...
> 
> 
> ======== Rebuilding
> "k:/ahu_sourcefiles/Main/Dev_Env/VxWorks/C6_Std/Target/Release/AhuC6.o"
> ========                                                                                                             
>         k:/ahu_tools/tornado/host/x86-win32/bin/ccsh
> -Ik:/ahu_sourcefiles/Include
> -Ik:/ahu_sourcefiles/System_Interfaces/Include
> -Ik:/ahu_sourcefiles/Swp_Interfaces/Include
> -Ik:/ahu_tools/tornado-pc/target/con
> fig/MMI_AudiHU -Ik:/ahu_tools/tornado-pc/target/proj/MMI_AudiHU
> -Ik:/ahu_tools/Rhapsody/Include/C -Ik:/ahu_tools/Rhapsody/Include/Cpp
> -Ik:/ahu_sourcefiles/System/OS_Abstraction_Layer/OS_Wrapper/Include
> -Ik:/ah
> u_sourcefiles/Swp/Services/Passive/Trace_Support/Include
> -Ik:/ahu_sourcefiles/Swp/Services/Passive/Messaging_System/Source/MsgQueue/Include 
> -Ik:/ahu_sourcefiles/Swp/Services/Passive/Messaging_System/Source/Ms
> gQueue/Source 
> -Ik:/ahu_sourcefiles/Swp/Services/Passive/Messaging_System/Source/MsgQueue/Source/Xcpp 
> -Ik:/ahu_sourcefiles/Swp/GUI/Source/Xcpp 
> -Ik:/ahu_sourcefiles/Swp/Applications/Car_Functions/Source/BLCar
> Functions/Source/Xcpp 
> -Ik:/ahu_sourcefiles/Swp/Applications/Car_Functions/Source/VDCarFunctions/Source/Xcpp 
> -Ik:/ahu_sourcefiles/Swp/Applications/Settings/Source/BLSettings/Source/Xcpp 
> -Ik:/ahu_sourcefiles/
> Swp/Applications/Settings/Source/VDSettings/Source/Xcpp 
> -Ik:/ahu_sourcefiles/Swp/GUI/Source 
> -Ik:/ahu_sourcefiles/Swp/GUI/Source/Include 
> -Ik:/ahu_sourcefiles/Swp/Applications/Car_Functions/Include  -Os -m3 -
> c -fno-weak -ansi -DRW_MULTI_THREAD -D_REENTRANT -fno-rtti
> -fconserve-space -fno-exceptions -fvolatile -fno-builtin -fno-for-scope
> -I. -Ik:/k:/ahu_tools/tornado/target/h  -o
> k:/ahu_sourcefiles/Main/Dev_Env/VxW
> orks/C6_Std/Target/Release/AhuC6.o
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp                                                                                                                                  
> In file included from
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:151:                                                                                                                                          
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_AM.sub: In function `void
> Install_AM()':                                                                                                                                
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_AM.sub:150: `class
> AM_CAudioManagement' has no member named
> `pInAM_IGUI'                                                                                                
> In file included from
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:159:                                                                                                                                          
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DIAG.sub: In function `void
> Install_DIAG()':                                                                                                                            
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DIAG.sub:100: `class
> DIAG_CDiagnosis' has no member named
> `pInSYS_ISubSystem'                                                                                           
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DIAG.sub:108: `class
> DIAG_CDiagnosis' has no member named
> `pInMSF_IKwpReceiver'                                                                                         
> In file included from
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:165:                                                                                                                                          
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DSP.sub: In function `void
> Install_DSP()':                                                                                                                              
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_DSP.sub:173: `class DSP_CBL'
> has no member named
> `pInTM_IExpired'                                                                                                       
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp: In function `void
> ConnectAll_Component2Component()':                                                                                                               
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:694: `class
> DIAG_CDiagnosis' has no member named
> `pOutMSF_IKwpSender'                                                                                               
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:722: `class DSP_CBL' has no
> member named
> `pOutDP_IDataPool'                                                                                                         
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6.cpp:726: `class DSP_CBL' has no
> member named
> `pOutTM_IRequest'                                                                                                          
> (k:\ahu_tools\tornado\host\x86-win32\lib\gcc-lib\sh-wrs-vxworks\gcc-2.96\cc1plus.exe
> 1002) commit_and_inc: VirtualAlloc
> failed                                                                                   
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_TUN.sub: In function `void
> __static_initialization_and_destruction_0(int,
> int)':                                                                                        
> k:/ahu_sourcefiles/Main/Source/Ahu/AhuC6_TUN.sub:57: virtual memory
> exhausted                                                                                                                                    
> *** Error code
> 1

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: socket call returns an error
Date: Tue, 26 Nov 2002 19:24:34 +0100
From: "Mallet, Sebastien [CTF:4927:EXCH]" <mallet@europem01.nt.com>
Organization: Nortel Networks
Message-ID: <3DE3BC62.CA51EDE7@europem01.nt.com>
References: <18775478.0211261012.847646e@posting.google.com>

Hi,
Just have a look at your cluster pool with netStackDataPoolShow or
netStackSysPoolShow on the shwll(windsh  or target shell).
It seems that you don't have any more system or data clusters. you can
increase the number of clusters  in the project manager (NUM_SYS_* or
NUM_*).
HTH
Sebastien Mallet

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Marge archives
Date: Tue, 26 Nov 2002 20:30:52 +0200
From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Organization: Verio
Message-ID: <newscache$gt476h$k18$1@lnews.actcom.co.il>
References: <acaaa989.0211260724.4ec462a8@posting.google.com>
Reply-To: "Leonid Rosenboim" <EDIT_THE_ADDRESS>

"Oded Weissman" <oded.weissman@motorola.com> wrote in message
news:acaaa989.0211260724.4ec462a8@posting.google.com...
> Hello
>
> With what utility and\or command can I marge few archives (.a)
>  to one big archive (created with diab "dar" utility).
>

the way to do this is to extract all objects from one archive and add
them to the other, e.g.

cd $WIND_BASE/target/lib
mkdir tmpd
cd tmpd
dar xv ../libone.a
dar av ../libtwo.a *.o

- -- Again I am curious what wonderful use have YOU found for your
set of Tornadi/Diab toolset manuals ? Looks too nice on the bookshelf to
touch ?
- -----------------------------------------------------------------------
   Leonid Rosenboim     Visit:  http://www.masada2000.org/historical.html
       Consultant                Email: my first name at consultant dot com

---------------------------

Newsgroups: comp.os.vxworks
Subject: shutdown operation
Date: 26 Nov 2002 10:37:11 -0800
From: gabi@tdsoft.com (Gabi)
Organization: http://groups.google.com/
Message-ID: <5607ff2c.0211261037.4433ff02@posting.google.com>

Hi,
Does shutdown operation is a block or non-block operation. Does the
type of the socket "FIONBIO" relevant in this case.
tanks
Gabi

---------------------------

Newsgroups: comp.os.vxworks
Subject: pci detection problems and doubts
Date: 29 Nov 2002 03:56:31 -0800
From: vxnerd@rediffmail.com (subbarayan)
Organization: http://groups.google.com/
Message-ID: <f81c4277.0211290356.4ebc6ace@posting.google.com>

dear pedagougues,
        I have some basic doubts regarding pci support in vxworks.I am
using tornado2.0,vxworks5.4,pc486 target,standalone floppy based
bootable target.
I am now trying to detect the pci cards present in my target system
via vxworks.
I added the pci bus support support component in my application and
built the image.Now heres my actual doubt:
1)Is it enough if i just include the macro for enabling pci support
from GUI?
2)Whats the proof that pci support is present in my image after i
build it?
3)Suppose for a case,assuming,pci support is included in my image,will
it report automatically to the user after booting from the target
side?(some thing like autodetect and similar to what the bios does and
which scans bus automatically and reports back with irq settings for
cards in bus).what system calls are to be used to detect pci card in a
target?what settings need to be done to make it work from pci side?
4)Whats the role of pci library file pciautoconfig files in this
detection part and how actually should these files be used?I directly
compiled the pciautoconfiglib.c file and also pciconfigshow.c files
and tried to call those functions directly from target.But they give
undefined symbol reference error.
Then i created a small .c application source file,from which i called
these functions defined in these pci configuration files supplied by
wrs.I also included these .c files in my source using #includes.That
also did not fetch me any results.
5)Where can I get info abt the way the vxworks interacts with BIOS
with respect to this pci stuff?
Advanced thanks to person replying me.I have been trying lot of things
around with no results.So will be grtful to person really replying me
as early as possible.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: how to recompile the vxWorks using make under command line mode??
Date: 29 Nov 2002 04:01:04 -0800
From: vxnerd@rediffmail.com (subbarayan)
Organization: http://groups.google.com/
Message-ID: <f81c4277.0211290401.6e25e70d@posting.google.com>
References: <as6p59$2j1j$1@mail.cn99.com> <as72uh$8t3$1@snoopy.bndlg.de> <as73qq$2s0n$1@mail.cn99.com>

dear seraph,
   Once u call the torvars file and execute it,goto ur project
directory in dos prompt and then from there type edit makefile.This
will open make file.In the make file,u find MACH_EXTRA there u give
MACH_EXTRA=ursourcefilename.o.Save that makefile and exit.Now in Dos
prompt type make.This will make the file for u.The as usual u can go
for mkboot a: bootrom_uncmp and proceed.
Hope this helps.Let me know if u encounter errors.
Regards,
subbarayan

---------------------------

End of New-News digest
**********************

From vxwexplo-errs@csg.lbl.gov  Sat Nov 30 04:03:18 2002
From: Vxworks Exploder <vx_explo@csg.lbl.gov>
Date: Sat Nov 30 04:03:19 PST 2002
Subject: comp.os.vxworks newsdigest

Comp.Os.Vxworks Daily Digest    Sat Nov 30 04:03:15 PST 2002

        Subject: Re: pci detection problems and doubts
        Subject: Re: Memory Mapping with cacheDmaMalloc
        Subject: Re: X86 Boot Problem
        Subject: Fast sqrt() routine for integers?
        Subject: Re: X86 Boot Problem
        Subject: Re: how to recompile the vxWorks using make under command line mode??
        Subject: Re: Fast sqrt() routine for integers?
        Subject: Re: Fast sqrt() routine for integers?
        Subject: Re: Fast sqrt() routine for integers?
        Subject: Re: pci detection problems and doubts
        Subject: loopback ?
        Subject: Re: Fast sqrt() routine for integers?
        Subject: Re: how to recompile the vxWorks using make under command line mode??

-------------------------------------------------------

Newsgroups: comp.os.vxworks
Subject: Re: pci detection problems and doubts
Date: Fri, 29 Nov 2002 14:00:23 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <as7ode$gq4$1@snoopy.bndlg.de>
References: <f81c4277.0211290356.4ebc6ace@posting.google.com>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Hi,

use INCLUDE_PCI in config.h, AFAIK you can't do that from Workspace (there
is INCLUDE_PCI_CONFIG, that's another trail, don't use it before you are
sure that normal config runs OK)
Now include pci show routines if necessary (on PPC its automatically
included by INCLUDE_PCI ) and you should have commands like pciHeaderShow
and pciDeviceShow.
You shouldn't need pciAutoConfig, as config should already be done by BIOS.
Check that BIOS is set to non-PNP O/S!
Look into your VxWorks manuals for further information.

Regards,
Michael

"subbarayan" <vxnerd@rediffmail.com> schrieb im Newsbeitrag
news:f81c4277.0211290356.4ebc6ace@posting.google.com...
> dear pedagougues,
>         I have some basic doubts regarding pci support in vxworks.I am
> using tornado2.0,vxworks5.4,pc486 target,standalone floppy based
> bootable target.
> I am now trying to detect the pci cards present in my target system
> via vxworks.
> I added the pci bus support support component in my application and
> built the image.Now heres my actual doubt:
> 1)Is it enough if i just include the macro for enabling pci support
> from GUI?
> 2)Whats the proof that pci support is present in my image after i
> build it?
> 3)Suppose for a case,assuming,pci support is included in my image,will
> it report automatically to the user after booting from the target
> side?(some thing like autodetect and similar to what the bios does and
> which scans bus automatically and reports back with irq settings for
> cards in bus).what system calls are to be used to detect pci card in a
> target?what settings need to be done to make it work from pci side?
> 4)Whats the role of pci library file pciautoconfig files in this
> detection part and how actually should these files be used?I directly
> compiled the pciautoconfiglib.c file and also pciconfigshow.c files
> and tried to call those functions directly from target.But they give
> undefined symbol reference error.
> Then i created a small .c application source file,from which i called
> these functions defined in these pci configuration files supplied by
> wrs.I also included these .c files in my source using #includes.That
> also did not fetch me any results.
> 5)Where can I get info abt the way the vxworks interacts with BIOS
> with respect to this pci stuff?
> Advanced thanks to person replying me.I have been trying lot of things
> around with no results.So will be grtful to person really replying me
> as early as possible.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Memory Mapping with cacheDmaMalloc
Date: Fri, 29 Nov 2002 14:09:03 +0100
From: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Organization: Buergernetz Dillingen
Message-ID: <as7otj$ho9$1@snoopy.bndlg.de>
References: <2592b7d6.0211290020.347c7686@posting.google.com>
Reply-To: "Michael Lawnick" <michael.lawnick@no_spam.kontron.com>
Sender: mlawnick@mail.kontron-applications.com

Out of the box:
a) code an own cacheDmaMallocAt() - it should walk along the free list,
fetch the correct junk, split it and put back the parts in free list and
used list. Take a look into libs by nm<arch> before, may be there is already
something like this.
b) do cacheDmaMallocs until you get a block that fits your needs and free
the rest again.
Don't like both ideas, but might help you until you (or any other) have a
better one.

Regards,
Michael

"Greg Holmes" <gregory.holmes@baesystems.com> schrieb im Newsbeitrag
news:2592b7d6.0211290020.347c7686@posting.google.com...
> Hi there VxWorkers!
>
> I wondered if someone could help me with the problem of using
> cacheDmaMalloc.
> I'm trying to use cacheDmaMalloc to allocate a buffer of memory below
> 16mb. The 8237 DMA chip on the Ampro Pentium board I'm using only has
> an address 24 bits wide. I have 64mb of memory and cacheDmaMalloc is
> returning an address of around 3F0D000 which is beyond what I can
> address with the 8237 DMA register. As the argument to cacheDmaMalloc
> is the size of the buffer to allocate how can I make it address the
> memory below 16mb.
>
> Thanks for you help in advance.
>
> Greg Holmes

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: X86 Boot Problem
Date: 29 Nov 2002 10:04:52 -0800
From: akarpov@my-deja.com (Alex)
Organization: http://groups.google.com/
Message-ID: <4f09bb68.0211291004.cbb4dd7@posting.google.com>
References: <484f4f20.0211271751.29c1e6ad@posting.google.com> <73fF9.158688$nB.12829@sccrnsc03>

If you do not see VxWorks version/copyright line, you're not running
VxWorks, that simple...

"drdiags" <drdiags@attbi.com> wrote in message news:<73fF9.158688$nB.12829@sccrnsc03>...
> Hello Jacky,
> 
>    Depending on the BSP and whether this is T2.2/AE or not. In T2.2,
> the serial port is the default console port (I think AE also). In earlier
> release of the x86 BSP, PC_CONSOLE was for most of the BSPs I have
> seen. Looking at your bootloader version (1.6) I am guessing this is
> either AE or T2.2, since I remember seeing 1.2 for T2 and 1.5 if I used
> T2.0.2 mkboot utility....
 
> "Jacky Cheung" <jc422@cornell.edu> wrote in message
> news:484f4f20.0211271751.29c1e6ad@posting.google.com...
> > Hi all,
> >    I have just started a project at school using
> > VxWorks on a x86 board. I have been trying to
> > create a boot disk to boot up VxWorks on the board
> > so that I can set the boot parameter. However, the board
> > only boots up a certain point after a lot of "+"
> > signs, and then it would stall:
> >
> > V1.6++++++++++++++++++++++++++++++++++++++
> > +++++++++++++++++++++++++++++++++++++++++
> >                 .
> >                 .
> >                 .
> >
> >    I used the mkboot utility and the default
> > VxWorks rom that the Pentium BSP provided. Can anyone
> > give me a hint on my problem? I would really appreciate
> > that. Thank you.
> >
> >
> > Jacky

---------------------------

Newsgroups: comp.os.vxworks
Subject: Fast sqrt() routine for integers?
Date: Fri, 29 Nov 2002 20:37:44 +0100
From: "CCA" <cc@cc.cc>
Organization: Utfors AB
Message-ID: <as8f2p$ikq$1@yggdrasil.utfors.se>

Hello,

The provided sqrt() function in VxWorks 5.4 is executing to slow on my
MCF5307 CPU. I just need a simple sqrt() routine for 32-bit unsigned
integers.
Where can I find such routine (simple ans fast).

/CC

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: X86 Boot Problem
Date: Fri, 29 Nov 2002 20:07:13 GMT
From: "drdiags" <drdiags@attbi.com>
Organization: AT&T Broadband
Message-ID: <RNPF9.178361$1O2.12077@sccrnsc04>
References: <484f4f20.0211271751.29c1e6ad@posting.google.com> <73fF9.158688$nB.12829@sccrnsc03> <4f09bb68.0211291004.cbb4dd7@posting.google.com>

"Alex" <akarpov@my-deja.com> wrote in message
news:4f09bb68.0211291004.cbb4dd7@posting.google.com...
> If you do not see VxWorks version/copyright line, you're not running
> VxWorks, that simple...
>
You are not correct with this assertion. The vxWorks version/copyright
line will be directed to the configured console port which for x86
can be the VGA PC adapter or the serial port. A lot of folks are
getting tripped up by what appears to be a hung target, when it is
a redirected console.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: how to recompile the vxWorks using make under command line mode??
Date: Fri, 29 Nov 2002 20:17:14 GMT
From: "drdiags" <drdiags@attbi.com>
Organization: AT&T Broadband
Message-ID: <eXPF9.177150$QZ.27925@sccrnsc02>
References: <as6p59$2j1j$1@mail.cn99.com> <as72uh$8t3$1@snoopy.bndlg.de> <as73qq$2s0n$1@mail.cn99.com>

Hello Seraph,

    If you bought network source, then go to the target/src/netwrs and do
the following
(also target/src/netinet):

0 - Save off the original libPPC604gnuvx.a (as an example).
1 - del the *depend* file, if you haven't done a build before now but there
shouldn't be
one there.
2 - make TOOL=gnu CPU=PPC604 (this will generate the dependency file, and
compile
  and update the libPPC604gnuvx.a file for you).
3 - Or you could just build the particular *.o you want and manually archive
the *.a or
     add the *.o to your BSP for testing as a *.obj MACH_EXTRA item until
you are
     satisfied.
4 - Do as Michael and Subbu suggested, which I gather you are already
comfortable
with. Good luck

"Seraph Ma" <seraph.ma@utstar.com> wrote in message
news:as73qq$2s0n$1@mail.cn99.com...
> Michael
>         Of cource should I call 'torVars.bat'. Yeah, I have already call
> this bat file.
>         What I wanna compile is vxWorks kernel. Our company has bought
> WINDRIVER's network
> source files( .c and .h,makefile ),I have made some modifications on these
> source codes,and now I wanna rebuild the changed files and link these
built
> .o to vxworks kernel.
>         That's what I wanna do .
>         But still thank you so much.
>
>
>
> "Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message
> news:as72uh$8t3$1@snoopy.bndlg.de...
> > Hi Seraph,
> > open DOS-box and change to host\x86-win32\bin. Now call 'torVars.bat'.
> > All necessary variables should be set now .
> > Change to your project directory and call e.g. 'make vxWorks'
> >
> > HTH
> > Michael
> >
> > "Seraph Ma" <seraph.ma@utstar.com> schrieb im Newsbeitrag
> > news:as6p59$2j1j$1@mail.cn99.com...
> > > Hey,Guys
> > >     I have to recompile the vxowrks kernel using GNU make under
command
> > mode
> > > instead of
> > > Tornado IDE enviorment.( my compile enviorment,OS WIN2000,Tornado
> > > 2.0.2,vxworks 5.4)
> > >     I have modified some .c files ,so what should I pay attention to
if
> I
> > > wanna rebuild
> > > the kernel. What enviorment variables should i SET? What else -Ds
should
> I
> > > define other
> > > than CPU,TOOL ??
> > >     I just have been blocked with many 'make' problems now~~
> > >     Eager for your warm-hearted help~~~~
> > >
> > >
> > >     Thanx a lot.
> > >                                      Seraph Ma
> > >
> > >
> >
> >
>
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Fast sqrt() routine for integers?
Date: Fri, 29 Nov 2002 20:43:23 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as8jha$p3s$1@helle.btinternet.com>
References: <as8f2p$ikq$1@yggdrasil.utfors.se>

> The provided sqrt() function in VxWorks 5.4 is executing to slow on my
> MCF5307 CPU. I just need a simple sqrt() routine for 32-bit unsigned
> integers.
> Where can I find such routine (simple and fast).

If it anything like the vxworks for ARM, you are using the foul
C floating point routines supplied with gcc.
They are somewhat slow!

The 'schoolboy' algorithm is probably fast enough!
It is so similar to schoolboy divide that any (simple) division
hardware should be able to do sqrt as well.
I just knocked up the following for you:

	David

unsigned int
sqrt_u(int n)
{
         unsigned int n0 = n;
         unsigned int r, d, q;

         for (d = 0; d < 16; d++, n <<= 2)
                 if (n & 0xc0000000)
                         break;

         for (q = 0, r = 0; d < 16; d++, n <<= 2) {
                 q <<= 1;
                 r = r << 2 | n >> 30;
                 if (r < q + 1)
                         continue;
                 r -= ++q;
         }

         return q >> 1;
}

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Fast sqrt() routine for integers?
Date: Fri, 29 Nov 2002 20:45:58 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as8jm5$p3s$2@helle.btinternet.com>
References: <as8f2p$ikq$1@yggdrasil.utfors.se> <as8jha$p3s$1@helle.btinternet.com>

A line escaped...

> unsigned int
> sqrt_u(int n)
> {
>         unsigned int n0 = n;
>         unsigned int r, d, q;
> 
>         for (d = 0; d < 16; d++, n <<= 2)
>                 if (n & 0xc0000000)
>                         break;
> 
>         for (q = 0, r = 0; d < 16; d++, n <<= 2) {
>                 q <<= 1;
>                 r = r << 2 | n >> 30;
>                 if (r < q + 1)
>                         continue;
>                 r -= ++q;
		  q++;
>         }
> 
>         return q >> 1;
> }
> 

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Fast sqrt() routine for integers?
Date: Fri, 29 Nov 2002 22:21:39 +0000 (UTC)
From: David Laight <david@spam.me.l8s.co.uk>
Organization: BT Openworld
Message-ID: <as8p9i$lh0$1@knossos.btinternet.com>
References: <as8f2p$ikq$1@yggdrasil.utfors.se> <as8jha$p3s$1@helle.btinternet.com> <as8jm5$p3s$2@helle.btinternet.com>

Actually this one is a bit shorter!
Optimise further by setting 'b' first (must be an
even power of 2).

	David

unsigned int
sqrt_u(unsigned int n)
{
         unsigned int r, b;

         for (r = 0, b = 0x40000000; b; b >>= 2, r >>= 1) {
                 if (n < r + b)
                         continue;
                 r += b;
                 n -= r;
                 r += b;
         }

         return r;
}

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: pci detection problems and doubts
Date: 29 Nov 2002 09:51:00 -0800
From: akarpov@my-deja.com (Alex)
Organization: http://groups.google.com/
Message-ID: <4f09bb68.0211290951.1b9d5980@posting.google.com>
References: <f81c4277.0211290356.4ebc6ace@posting.google.com>

Dear subbarayan,

As one of collegues at vxworks newsgroup (not confuse with
"pedagougues"), I can do following general comments:

1. If you're new to VxWorks, please check the following URL:
http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html
I'm sure you'll find a lot of interesting information.
2. Your BSP should provide you with facilities to find and configure
PCI devices (This involves setting memory map, interrupts etc.)
3. If you're developing PCI support for a BSP, have a look at 
WindRiver's AppNote WTN-126 or WTN-49.

My .02 cents
AK

vxnerd@rediffmail.com (subbarayan) wrote in message news:<f81c4277.0211290356.4ebc6ace@posting.google.com>...
> dear pedagougues,
>         I have some basic doubts regarding pci support in vxworks.I am
> using tornado2.0,vxworks5.4,pc486 target,standalone floppy based
> bootable target.
> I am now trying to detect the pci cards present in my target system
> via vxworks.
> I added the pci bus support support component in my application and
> built the image.Now heres my actual doubt:

---------------------------

Newsgroups: comp.os.vxworks
Subject: loopback ?
Date: Sat, 30 Nov 2002 11:36:00 +0800
From: "Jeffrey Chou" <jeffreychou0923@hotmail.com>
Organization: DCI HiNet
Message-ID: <as9bn4$c2p@netnews.hinet.net>

Hi there,
I have one problem of "ping" and "loopback" option.
When I connect the Ethernet port to my LAN, I can "ping" myself (self ip
address).
But After I plug-off or connect the Ethernet port to a standalone hub, I can
not ping
myself !?
Why this happen even I set the interface with "LOOPBACK" option ?

Thank for you help in advance.

Jeffrey.

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: Fast sqrt() routine for integers?
Date: Fri, 29 Nov 2002 23:42:11 +0100
From: "CCA" <cc@cc.cc>
Organization: Utfors AB
Message-ID: <as8psb$k36$1@yggdrasil.utfors.se>
References: <as8f2p$ikq$1@yggdrasil.utfors.se> <as8jha$p3s$1@helle.btinternet.com> <as8jm5$p3s$2@helle.btinternet.com> <as8p9i$lh0$1@knossos.btinternet.com>

I will try this one.
Thank you :-)

"David Laight" <david@spam.me.l8s.co.uk> wrote in message
news:as8p9i$lh0$1@knossos.btinternet.com...
> Actually this one is a bit shorter!
> Optimise further by setting 'b' first (must be an
> even power of 2).
>
> David
>
> unsigned int
> sqrt_u(unsigned int n)
> {
>          unsigned int r, b;
>
>          for (r = 0, b = 0x40000000; b; b >>= 2, r >>= 1) {
>                  if (n < r + b)
>                          continue;
>                  r += b;
>                  n -= r;
>                  r += b;
>          }
>
>          return r;
> }
>

---------------------------

Newsgroups: comp.os.vxworks
Subject: Re: how to recompile the vxWorks using make under command line mode??
Date: Sat, 30 Nov 2002 16:06:45 +0800
From: "Seraph Ma" <seraph.ma@utstar.com>
Organization: Bentium Ltd. (CN99)
Message-ID: <as9rim$25m4$1@mail.cn99.com>
References: <as6p59$2j1j$1@mail.cn99.com> <as72uh$8t3$1@snoopy.bndlg.de> <as73qq$2s0n$1@mail.cn99.com> <eXPF9.177150$QZ.27925@sccrnsc02>

Hey Dear everyone
    You are so warm-hearted!!!
    Thank you very much !!!!
    Hope I will learn more about vxworks and embeded from you in the
future!!
    :-)

"drdiags" <drdiags@attbi.com> wrote in message
news:eXPF9.177150$QZ.27925@sccrnsc02...
> Hello Seraph,
>
>     If you bought network source, then go to the target/src/netwrs and do
> the following
> (also target/src/netinet):
>
> 0 - Save off the original libPPC604gnuvx.a (as an example).
> 1 - del the *depend* file, if you haven't done a build before now but
there
> shouldn't be
> one there.
> 2 - make TOOL=gnu CPU=PPC604 (this will generate the dependency file, and
> compile
>   and update the libPPC604gnuvx.a file for you).
> 3 - Or you could just build the particular *.o you want and manually
archive
> the *.a or
>      add the *.o to your BSP for testing as a *.obj MACH_EXTRA item until
> you are
>      satisfied.
> 4 - Do as Michael and Subbu suggested, which I gather you are already
> comfortable
> with. Good luck
>
> "Seraph Ma" <seraph.ma@utstar.com> wrote in message
> news:as73qq$2s0n$1@mail.cn99.com...
> > Michael
> >         Of cource should I call 'torVars.bat'. Yeah, I have already call
> > this bat file.
> >         What I wanna compile is vxWorks kernel. Our company has bought
> > WINDRIVER's network
> > source files( .c and .h,makefile ),I have made some modifications on
these
> > source codes,and now I wanna rebuild the changed files and link these
> built
> > .o to vxworks kernel.
> >         That's what I wanna do .
> >         But still thank you so much.
> >
> >
> >
> > "Michael Lawnick" <michael.lawnick@no_spam.kontron.com> wrote in message
> > news:as72uh$8t3$1@snoopy.bndlg.de...
> > > Hi Seraph,
> > > open DOS-box and change to host\x86-win32\bin. Now call 'torVars.bat'.
> > > All necessary variables should be set now .
> > > Change to your project directory and call e.g. 'make vxWorks'
> > >
> > > HTH
> > > Michael
> > >
> > > "Seraph Ma" <seraph.ma@utstar.com> schrieb im Newsbeitrag
> > > news:as6p59$2j1j$1@mail.cn99.com...
> > > > Hey,Guys
> > > >     I have to recompile the vxowrks kernel using GNU make under
> command
> > > mode
> > > > instead of
> > > > Tornado IDE enviorment.( my compile enviorment,OS WIN2000,Tornado
> > > > 2.0.2,vxworks 5.4)
> > > >     I have modified some .c files ,so what should I pay attention to
> if
> > I
> > > > wanna rebuild
> > > > the kernel. What enviorment variables should i SET? What else -Ds
> should
> > I
> > > > define other
> > > > than CPU,TOOL ??
> > > >     I just have been blocked with many 'make' problems now~~
> > > >     Eager for your warm-hearted help~~~~
> > > >
> > > >
> > > >     Thanx a lot.
> > > >                                      Seraph Ma
> > > >
> > > >
> > >
> > >
> >
> >
>
>

---------------------------

End of New-News digest
**********************