Quote:
Originally Posted by mfalk
Our current crisis is that when we deploy code from Windriver the DS still reads "No Code". I've made sure that all of the IP settings are correct. I can ping the crio, I can ftp into the crio, but I have no idea what I'm looking for. Being able to see more detailed errors than "no code" might help us figure this out.
|
I'm assuming that by "Deploy Code" you're referring to going to the FIRST menu and using the deploy option. If that's the case, you need to power cycle the robot for it to take effect. The deployed executable is only ever started on the initial boot.
This is obviously a pain when doing tweak debugging. Rather than use that method, you should try running your program out of memory rather than flash. Check out page 12 of
this document. While it shows how to set up the debugger, the same setup will allow you to run out of memory without actually attaching the debugger. This will save you a ton of time. Once set up, this is done by clicking the green Run arrow on the tool bar (might have to use the little submenu on the button to select the right deployment type)
When you want to use this option, be sure to do a FIRST->Undeploy and reset the robot so that there isn't anything running .
A couple of warnings
1. Make sure that you correctly delete any memory that you create in the appropriate destructors. If you don't, you will leak when you re-run your code and will eventually run out of memory if the leak is bad enough.
2. Be sure to deploy with FIRST->Deploy when you're done debugging. If you don't, the robot will have no code on it when you power cycle it. Running the code out of memory means that it isn't persistent across a reset.
3. Be very careful if you're using a debugger and breakpoints. If you pause your program, your speed controllers might be latched with the last value they received. This will cause a runaway robot which is bad (even worse if it's on an arm or something that could destroy itself).
Good luck