|
Debugging C++ code in Windriver
We've been having sporadic issues with all sorts of random issues from CAN programming to holonomic drive modes and everything in between. For our programmers, the only way that we've been able to test anything has been to build, deploy, fiddle with the robot, change the code, build again, deploy again, etc.
How exactly can we go about testing this while viewing console output and detailed errors?
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.
Thanks in advance for any assistance.
|