|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Our C++ is not running out of debug
Whenever I try downloading the code from winriver, it only allows us to download through debug. Whenever I go through the deploy option, it gives me the no code in robot error on the driver's station. Any ideas?
|
|
#2
|
||||
|
||||
|
Re: Our C++ is not running out of debug
We are having the exact same problem, any help would be appreciated
![]() |
|
#3
|
||||
|
||||
|
Re: Our C++ is not running out of debug
Hook up the debug console to see what failed. We had a similar problem last year and found out our code was exceeding the 16-bit "call" distance so we had to add -mlongcall in the linker option to get the code to load.
|
|
#4
|
|||
|
|||
|
Re: Our C++ is not running out of debug
-mlongcall worked great! Thanks!
![]() |
|
#5
|
|||
|
|||
|
Re: Our C++ is not running out of debug
Pro tip: In Window->Preferences you can set default build properties so you never have to worry about these things
![]() |
|
#6
|
|||
|
|||
|
Re: Our C++ is not running out of debug
Hooray! Another error. we are getting a "Relocation value does not fit in 24 bits" message. I added the -mlongcall tag in the build properties>build command. Anyone have any ideas? It worked before after we added the tag, but stopped working suddenly this weekend.
|
|
#7
|
|||
|
|||
|
Re: Our C++ is not running out of debug
We are also getting the same "Relocation value does not fit in 24 bits" message on our NetConsole when the bot attempts to load FRC_UserProgram at startup. Trying to find a solution.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|