Hi,
I installed 'NNDKSetup21_rc4a.exe' on drive O not C (don't ask -- long story). Everthing seems to work so far except when I attempt to launch debugger (see result from console below). How do I change the drive it uses?
Thanks.
Best,
Tom
------------------------------------------------------------------------------------------
Source directories searched: $cdir;$cwd
Warning: c:\nburn\system: No such file or directory.
mi_cmd_env_cd: Usage DIRECTORY
Quit (expect signal SIGINT when the program is resumed)
kill
Quit (expect signal SIGINT when the program is resumed)
Debugger won't launch on drive not equal to C
-
- Posts: 11
- Joined: Tue Jul 01, 2008 7:31 am
Re: Debugger won't launch on drive not equal to C
I have a similar problem. Using Windows Vista and version 2p1rc4A of the NDDK on a PK70 module.
Trying to run the TFTP demo program in debug mode. I have added the debugger intitializtion as described in the getting started guide.
Compiles but then comes up with the error:
Failed to set program arguments, environment or working directory.
Unable to set working directory: mi_cmd_env_cd: Usage DIRECTORY
I have the default directory selected in the debugger configuration, which is the same as the run configuration, which works.
What am I doing wrong? I can't find an explanation of what that (mi_cmd_env_cd) is. An environment variable that needs to be explicitly set or what?
I've got my default workspace set to 'C:\Users\user\Desktop\DesignWork\Eclipse Workspace'
and I've tried making a project with the workspace in the 'C:\Nburn\examples\TFTP' directory, and it behaves the same both ways.
Mike Chadwick
Trying to run the TFTP demo program in debug mode. I have added the debugger intitializtion as described in the getting started guide.
Compiles but then comes up with the error:
Failed to set program arguments, environment or working directory.
Unable to set working directory: mi_cmd_env_cd: Usage DIRECTORY
I have the default directory selected in the debugger configuration, which is the same as the run configuration, which works.
What am I doing wrong? I can't find an explanation of what that (mi_cmd_env_cd) is. An environment variable that needs to be explicitly set or what?
I've got my default workspace set to 'C:\Users\user\Desktop\DesignWork\Eclipse Workspace'
and I've tried making a project with the workspace in the 'C:\Nburn\examples\TFTP' directory, and it behaves the same both ways.
Mike Chadwick
Re: Debugger won't launch on drive not equal to C
Is your installation in O:\nburn\system?tpschmit wrote: I installed 'NNDKSetup21_rc4a.exe' on drive O not C (don't ask -- long story). Everthing seems to work so far except when I attempt to launch debugger (see result from console below). How do I change the drive it uses?
Source directories searched: $cdir;$cwd
Warning: c:\nburn\system: No such file or directory.
mi_cmd_env_cd: Usage DIRECTORY
Quit (expect signal SIGINT when the program is resumed)
kill
Quit (expect signal SIGINT when the program is resumed)
This should work. Have you tried doing this with the latest rel22_rc2 release? Same results?
The CDT/Eclipse debugger does not work when spaces exist in the project name or workspace directory. This is an error from the default Eclipse release that has yet to be resolved. I suggest you move to a directory structure that does not contain spacesmrchadwickusa wrote:I have a similar problem. Using Windows Vista and version 2p1rc4A of the NDDK on a PK70 module.
Trying to run the TFTP demo program in debug mode. I have added the debugger intitializtion as described in the getting started guide.
Failed to set program arguments, environment or working directory.
Unable to set working directory: mi_cmd_env_cd: Usage DIRECTORY
Forrest Stanley
Project Engineer
NetBurner, Inc
NetBurner Learn Articles: http://www.netburner.com/learn
Project Engineer
NetBurner, Inc
NetBurner Learn Articles: http://www.netburner.com/learn
-
- Posts: 11
- Joined: Tue Jul 01, 2008 7:31 am
Re: Debugger won't launch on drive not equal to C
Hey thanks for that, that was the issue. I've been debugging using iprintf, so I'm looking forward to learning the debugger!