Re: VxWorks
- From: sushmak2k6@xxxxxxxxx
- Date: Fri, 30 Nov 2007 18:24:45 -0800 (PST)
On Nov 30, 5:42 pm, "Michael R. Kesti" <michaelke...@xxxxxxxxxx>
wrote:
sushmak...@xxxxxxxxx wrote:
Hi Everybody,
Hello.
Iam new to VxWorks. I know programming in VxWorks but iam new to
VxWorks BSP. Can anyone help aboyt this.
This is a very open ended question and is therefore not likely to
generate much response. You can expect better if you ask more specific
questions.
That said, perhaps this will help.
A BSP, or board support package, consists of the code and documentation
files that are specific to a particular target (hardware environment) and
serve as the interface between the hardware specific and generic portions
of vxWorks. Its code is where system initialization begins, device
drivers are incorporated, and other hardware specific issues are handled.
The BSP is used in a variety of ways. One of these is to build boot ROM
images that can be programmed into ROM devices and installed on the target.
These provide the code that runs after reset, minimally initializes the
hardware, and attempts to load and execute an image of a customized and
more fully featured operating system from a flash memory, a disk, or via
a network connection. This program also provides the ability to interrupt
the boot process and specify boot parameters that control several factors
including where to find and how to load that customized, full featured OS.
This is very much like interrupting a PC's BIOS with the DEL key and
configuring Windows to boot in different ways.
The BSP also serves as the basis for rhose custom vxWorks images that can
be built in a variety of ways to support different uses. They can, for
example, be built to be loaded and executed on a target by its BSP boot
ROM. Such builds typically include debugging support, allowing application
programs to be loaded, executed, and debugged.
Custom vxWorks images can also be built to provide still more boot ROM
images. These typically boot the system in a specific way, as opposed
to the configurable boot provided by the BSP boot ROM. These images might
exclude debugging support but include debugged application programs that
execute once the boot process is complete.
Thanks In advance.
HTH
--
========================================================================
Michael Kesti | "And like, one and one don't make
| two, one and one make one."
mrkesti at hotmail dot com | - The Who, Bargain
Hi Michael ,
Thanks for your information.
.
- References:
- VxWorks
- From: sushmak2k6
- Re: VxWorks
- From: Michael R. Kesti
- VxWorks
- Prev by Date: Re: VxWorks
- Next by Date: Re: Why is the "name" parameter for taskSpawn a "char *"?
- Previous by thread: Re: VxWorks
- Next by thread: Re: Why is the "name" parameter for taskSpawn a "char *"?
- Index(es):
Relevant Pages
|
