"Executable File" property of an Externally Built Project

Comments

6 comments

  • Avatar
    Chuck Hackett

    Still waiting for some assistance in using an Externally Built project to debug a WinAVR (GCC) compiled executable ...

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    I don't think you're getting any help because this is a community site and you can't debug something built with WinAVR using GCC.  Sorry.  We don't use GCC for AVR.

    0
    Comment actions Permalink
  • Avatar
    Chuck Hackett

    I don't want help debugging WinAVR code, I can do that.

    I understand that Rowley does not support WinAVR, I wouldn't expect you to.  My understanding is that you do support "debugging external applications" which I assume includes files built by WinAVR/GCC.  ... or, does "external" not mean an executable created by another compiler (like I can do with AVR Studio).

    What I'm trying to figure out is how to setup the "Externally Built" project so that I can use the CrossWorks debugger to debug the application via JTAG.  I think I'm ok setting up the JTAG but I don't understand (or at least have not succeeded) how to setup the "External Project" project parameters (particularly the "Executable File" parameter) to accomplish this.  I have searched the Help file.  Please see my original post for more details.

    For the program I have the "elf" file, Intel "hex" file, etc. but neither of these were accepted for the "Executable File" parameter.

    Am I still in the wrong place?

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    >... debugging external applications" which I assume includes files built by WinAVR/GCC

    No, it does not support this.  The "Externally Built" means projects built outside of the IDE by the CrossWorks tools, which are not WinAVR.  We do not say that we support any other tool, just our own. We do not mention WinAVR.

    I don't need to re-read your original post because, as I said in my response, you cannot debug a WinAVR/GCC program as an Externally Built Executable.

    > ...For the program I have the "elf" file, Intel "hex" file, etc. but neither of these were accepted for the "Executable File" parameter

    For good reason.

    0
    Comment actions Permalink
  • Avatar
    Chuck Hackett

    I said that I was not looking for help with WinAVR code, and that I don't expect support from you for other vendors tools.

    Your statements make sense once I understood that "External" does not mean "built by another tool chain" (as it does with AVR Studio for example).  Without that knowledge I don't think it's a stupid question (which you seemed to imply).

    If one searches the CrossWorks Help for "externally built", the first item is "Debugging externally built applications".  In there it says "This section describes how to debug applications that have not been built by CrossStudio." -- I submit to you that WinAVR (or Codeview, IAR, etc.) fits this description.

    Another item "Overview", and under "Projects" it says "Externally Built Executable — an executable that is not built by CrossWorks." -- again non-Rowley compilers fit this description.

    If one lives only in the Rowley product world I can see how "external" might be taken to mean "another Rowley product".  As a potential customer, I have no knowledge of other Rowley products.  In the case of AVR code, I come from an AVR Studio environment where debugging an "externally built executable" means debugging anything that provides elf/dwarf symbol information. 

    So, I assume you can now see where I thought that "debugging and externally built executable" meant that CrossWorks would use the elf/dwarf symbol information to allow me to debug an existing application to see if I liked the debugger.

    Suggestions:

    • Correct the documentation to clarify the meaning of "externally built"
    • Try to look at things from the user's viewpoint and consider that (particularly a new user/evaluator) they do not think only in terms of Rowley products.
    • Consider supporting debugging of "non-Rowley generated" executables with accompanying elf/dwarf symbol information.  If they like the debugger, it may provide them a transition path to use the compiler, etc. which is your goal.

    From what I've seen of the IDE, it looks well done.  I was considering using CrossWorks in addition to, and, eventually as a replacement for AVR Studio, WinAVR, FreeRTOS, etc. but this exchange has not endeared me to the support provided ...

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis
    I have told you what we can't do. You decide that we may be able to do what you want because we don't specifically preclude it. You're free to make your own decisions about CrossWorks. 1. The documentation is not incorrect so cannot be "corrected". It may be clarified, but that is a different matter. 2. CrossWorks is meant to be used as an IDE and we offer the possibility of command line builds using the CrossWorks tools and debugging that build. Building outside CrossStudio is not the norm. 3. That's never going to happen.
    0
    Comment actions Permalink

Please sign in to leave a comment.