This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARM uVision 3: Debugging files using relative paths

I am having trouble debugging C source files that are located in a directory outside of the project directory. For example, in a test project I have three files:

c:\temp\file1.c - contains main()l

c:\temp\file2.c - contains a function called from main().

c:\file3.c - contains a function called from main().

The project file is in c:\temp

When I start a debug session in uVision3 (V3.03a) I can step through the code in file1.c and file2.c, but NOT file3.c [which is located in a directory higher than the project files]. The debugger does not associate the C file with the assembler and I can only step through the assembler.

Any advice as to where I am going wrong greatly appreciated.

Regards,
Richard.

Parents
  • Thanks for the fast response ....

    I tried entering SET "SRC = C:\" [where my test file is]in the command window - but no luck :o(

    I'm sure I'm missing something obvious. I'm upgrading a project from an old version of uVision where I didn't have this problem to the latest that came with a eval kit.

    Regards,
    Richard.

Reply
  • Thanks for the fast response ....

    I tried entering SET "SRC = C:\" [where my test file is]in the command window - but no luck :o(

    I'm sure I'm missing something obvious. I'm upgrading a project from an old version of uVision where I didn't have this problem to the latest that came with a eval kit.

    Regards,
    Richard.

Children
No data