Thread: Running a .out file from 2009 with a 2010 image
View Single Post
  #4   Spotlight this post!  
Unread 13-01-2010, 13:58
heydowns's Avatar
heydowns heydowns is offline
Registered User
AKA: Jeff Downs
FRC #1511 (Rolling Thunder)
Team Role: Mentor
  
Join Date: Jan 2006
Rookie Year: 2005
Location: Ra-Cha-Cha
Posts: 142
heydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond repute
Re: Running a .out file from 2009 with a 2010 image
Quote:
Originally Posted by GabeRC1717 View Post
Hey,

Can anyone confirm that if I image a cRIO from last year to the new 2010 image with the development environment set to C++ that I will still be able to deploy a .out file using last year's WPILib?
No. Any image which changes the FPGA (most do) will need a corresponding change to the development build environment. The version of WPILib used by Windriver must match the FPGA version in the cRIO.
If not, you will get errors at runtime about missing symbols when your .out is loaded (you'll only see these in debug load, or in console output when deployed).

Quote:
If this is not the case can I use the new cRIO imaging tool with the image .zip from last year to re-apply the 2009 C++ image?
Yes. More precisely, image with the version of the image that corresponds to the WPIlib your .out file was built against.

If you still have your 2009 source code, you may be better off just recompiling it in the 2010 environment. The API changes from 2009->2010 were minimal. Most teams' 2009 code should compile and run as-is in the 2010 environment without changes, enabling the use of a single cRIO image version.
Reply With Quote