We found out that is was imperative that the project be based off of the correct BSP, or the compiler would generate code for the wrong type of processor. By choosing these, we set options in the makefile that directed the compiler, linker, and Board Service Pack (BSP) to create one large piece of binary code at the conclusion of the build process that contained both the operating system and the application code in a format compatible with our board. When choosing project options at the start of our project, we chose to make a project of type "bootable VxWorks image." We also picked the correct BSP to base our project off of in the "Project Options" screen. Figure 1 below shows the build process graphically. By reading the VxWorks Programmer’s Guide we found that unlike operating systems that we have used in the past, VxWorks and its applications are really only one piece of executable code.
One of the more important technical aspects of our project was getting the VxWorks operating system to function on our board. This document contains relevant information about how the web server was implemented on the 403EVB. During the course of the project, it was discovered that the most efficient way to do this was using a web server on-board the 403EVB. The original project’s aim was to develop a web-based diagnosis program using a 403EVB. This document is a subset of a document written detailing a design project done at Texas A&M. Porting a Web Server Running under VxWorks to PPC403GCX
0 kommentar(er)
