Kernel Module
If you are building a module that will exist in the kernel space, use a VxWorks downloadable kernel module project.
You can separately build the modules, run, and debug them on a target running VxWorks, loading, unloading, and reloading those modules as you work.
Once your development work is complete, you can statically link the modules into the kernel or store them on a file system, if one is present.
Kernel-mode development is the traditional VxWorks method of development.
All the tasks you spawn run in an unprotected environment, and all have full access to the hardware in the system.
A kernel module that is linked into the kernel starts automatically when the target is booted, as long as the operating system is configured for this purpose.
You can separately build the modules, run, and debug them on a target running VxWorks, loading, unloading, and reloading those modules as you work.
Once your development work is complete, you can statically link the modules into the kernel or store them on a file system, if one is present.
Kernel-mode development is the traditional VxWorks method of development.
All the tasks you spawn run in an unprotected environment, and all have full access to the hardware in the system.
A kernel module that is linked into the kernel starts automatically when the target is booted, as long as the operating system is configured for this purpose.
Real-Time Processes
If you are building an executable that runs in user mode, or outside the kernel space, use a VxWorks real time process project.
You can separately build, run, and debug the executable.
At run time, the executable file is downloaded to a separate process address space to run as an independent process.
VxWorks real-time processes provide the means for executing applications in user mode.
Each process has its own address space, which contains the executable program, the program’s data, stacks for each task, the heap, and resources associated with the management of the process itself (such as memory-allocation tracking).
Many processes may be present in memory at once, and each process may contain more than one task (sometimes known as a thread in other operating systems).
You can separately build, run, and debug the executable.
At run time, the executable file is downloaded to a separate process address space to run as an independent process.
VxWorks real-time processes provide the means for executing applications in user mode.
Each process has its own address space, which contains the executable program, the program’s data, stacks for each task, the heap, and resources associated with the management of the process itself (such as memory-allocation tracking).
Many processes may be present in memory at once, and each process may contain more than one task (sometimes known as a thread in other operating systems).
'험난한 작업' 카테고리의 다른 글
| Difference between vxWorks Kernel Module and Real-Time Processes (0) | 2011/08/17 |
|---|---|
| [C#] 간단한 시리얼 통신 프로그램 (2) | 2011/06/14 |
| TinyOS 관련 참고자료(PDF) 모음 (1) | 2011/06/03 |
| VxWorks 디버깅을 위한 옵션 (0) | 2011/06/03 |
| 우분투(utuntu) 10.04 에서 TinyOS 2.1.1 설치 / 컴파일 하기 (0) | 2011/06/02 |
| 요즘 하고 있는 일 (1) | 2011/05/19 |
SimpleSerialTest.exe
SimpleSerialTest.zip
TinyOS 2.x Boot Sequence.pdf
ICEIC2010_template-word_2003.doc
