Chief Delphi - Module already loaded on target

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- C/C++ (http://www.chiefdelphi.com/forums/forumdisplay.php?f=183)

- - Module already loaded on target (http://www.chiefdelphi.com/forums/showthread.php?t=113154)

matthewkennedy

09-02-2013 20:59

Module already loaded on target

1 Attachment(s)

This seems like there's something easy that I'm missing.
So, the problem: I'm having a problem debugging to the cRIO from WindRiver. If I debug a project on the cRIO, fix something, recompile, and then hit debug again, I get this dialog box. What is the proper way to debug something, then debug again without rebooting the cRIO?

Kevin Sevcik

09-02-2013 21:03

Re: Module already loaded on target

Are you undeploying code and rebooting first so you don't have anything already running on bootup on the cRIO?

RufflesRidge

09-02-2013 21:27

Re: Module already loaded on target

Quote:

Originally Posted by matthewkennedy (Post 1230732)

What is the proper way to debug something, then debug again without rebooting the cRIO?

The current WPILib will error out even if you solved the current problem. If the ~25 seconds for the cRIO to reboot (you can even do it remotely from WindRiver or the DS software) is a factor in your debugging process, I would seriously suggest you need to slow down and make your changes more methodically.

nightpool

10-02-2013 16:41

Re: Module already loaded on target

Quote:

Originally Posted by RufflesRidge (Post 1230750)

Or use python, which allows for a better and more responsive design cycle ;)

JefferMC

10-02-2013 20:52

Re: Module already loaded on target

Previously I have been able to stop the RobotTask, unload my debug-deployed '.out' file, and then could reload it from the debugger and start it again. This year, I have not been able to; I get strange exceptions. It seems that the only reliable way to deploy a new version for debugging is to Reset the cRio.

All times are GMT -5. The time now is 18:25.