• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 3409 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

Source code level debugging on Fast Models

James White
Note: This was originally posted on 27th November 2012 at http://forums.arm.com

I'd like to know how I can enable source code debugging with the Fast Model simulator. It allows me to load source code directories, but I don't seem to be able to load any source code files. Does it only enable debugging of actual component code, or can I not also debug what I run *on* the model itself, e.g. application/OS kernel code? Any pointers would be really appreciated.
Parents
  • Arm Employee Badge
    Note: This was originally posted on 28th November 2012 at http://forums.arm.com

    Ahh, ok - I think I understand what you're doing.

    To do source level debug of the code running on the ARM processor you will need debug data.  This is data that the build tools generate so that a debugger can map the source level statements to the generated assembly code.  Debug data is held within the objects (.o), and later the linked image (.elf/.axf).

    First check that you are compiling your code with debug data.  If you're using armcc/armasm this means passing "--debug" or "-g".  For GCC I think it's "-g". 

    Next, how are you loading the code/data into the simulation?  Raw binary or image (.axf/.elf)?

    If it's a raw binary you'll need to separately load the debug data.  To do this go to File --> Load Application (Debug Info Only) and select the image being used.
Reply
  • Arm Employee Badge
    Note: This was originally posted on 28th November 2012 at http://forums.arm.com

    Ahh, ok - I think I understand what you're doing.

    To do source level debug of the code running on the ARM processor you will need debug data.  This is data that the build tools generate so that a debugger can map the source level statements to the generated assembly code.  Debug data is held within the objects (.o), and later the linked image (.elf/.axf).

    First check that you are compiling your code with debug data.  If you're using armcc/armasm this means passing "--debug" or "-g".  For GCC I think it's "-g". 

    Next, how are you loading the code/data into the simulation?  Raw binary or image (.axf/.elf)?

    If it's a raw binary you'll need to separately load the debug data.  To do this go to File --> Load Application (Debug Info Only) and select the image being used.
Children
No data