Win driver c++ on cRIO-ii only partially deploys app code

[jglassy]

Hello Delphi folks,

Our FRC team 3216 has decided to use c++ this year, using wind-river v3.3.1 from KOP 2012, and VxWorks 6.3, on Eclipse 3.6.2, on win 7. We have achieved network comm with cRIO ok, can ping it via cmd and driver son ok, and deployed the core VxWorks OS on platform. We have an FRC app that seemed to run once, but now cannot get to correctly deploy and run. The build itself goes almost too fast, resulting in an executable, but won't run due to lack of a entry point (e.g. Missing a EXE header on the assembly?) or unresolved link object. Can anyone using 2012 wind river c++ give us concise stepwise guidance on how to verify that a build with app code succeeded? It appears to succeed , but app does not run. Note: our mentors have experience with c and c++ and Linux Gcc compile,link, build processes but no specific experience with FRC wind river c++. Thanks in advance....

Team 3216

[Fifthparallel]

So a couple things, in case you didn't catch it. (hah, try {} catch{} -moving right along).

Read through this getting started with C/C++ pdf. Seriously though, read through the entire thing and then go through it step by step, kinda like putting together a model airplane.
The second thing I want to ask is persuant to that pdf above, it sounds like you were running the Debug configuration. I skipped over this earlier today when I tried the same thing you did (although it's entirely necessary during the build season proper).
The entry point error you mention can be remedied by first making sure you are connected to the cRio remote target with vxworks, right clicking the project in the project tree, and selecting Vxworks Debug Kernel (something like that). This should open another window that has an option tree on the left with a Kernel Task option. Click/expand this and choose the corresponding option for your remote target -- The cRio communications "server" you set up earlier. From there, you can type FRC_UserProgram_StartupLibraryInit into the entry point text field, and follow the rest of the instructions in the "Getting Started" guide linked above.
You should note that the debugging process only runs the program in the cRio's RAM through the Wind River debugger -- which allows you to set breakpoints and whatnot, in addition to immediately test your code and provide diagnostics on it. The section immediately after in the guide tells you how to permanently store a robot program and run it at startup.