• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 715 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

Problems with debugging in C source code

Frank Hennig

Hello,

I evaluate the Keil uVision V3.x (with Ulink and atmel arm7 evaluation board) and want to debug C source code.
Today I learned that all c source files must be in the same directory like uVision project file (*uv2).
Otherwise you cannout debug c source code.
Is this right?
Until now I arranged my source, header and project files in different directories.
For Example: Project_Test Output Source1 Header

That's no problem with other IDEs.

Best Regards

Parents
  • 0 in reply to Andy Neil

    Thank you for your answers.

    The path names have no spaces.
    I use the Keil ARM Tools with Realview Compiler. It is the evaluation version.
    I don't know what's wrong. I spend ours to find a solution. I tested and modified the "Hello world" example application. It's the same behaviour. After copying the C source files into another directory, you cannot debug C source code. uVision jumps to the disassembly window and you cannot insert breakpoints in your c source file.

Reply
  • 0 in reply to Andy Neil

    Thank you for your answers.

    The path names have no spaces.
    I use the Keil ARM Tools with Realview Compiler. It is the evaluation version.
    I don't know what's wrong. I spend ours to find a solution. I tested and modified the "Hello world" example application. It's the same behaviour. After copying the C source files into another directory, you cannot debug C source code. uVision jumps to the disassembly window and you cannot insert breakpoints in your c source file.

Children
No data