• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1637 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/PROCESSOR-SDK-AM437X: Cannot open output file WTSG_PN.out

Mads Lind Christiansen
Expert 1130 points

Part Number: PROCESSOR-SDK-AM437X

Tool/software: Code Composer Studio

Hi

I have a project in CCSv7 (AM437x IDK), based on the PRU ICSS Profinet example (but replaced with full compiled stacks - PROFINET & SNMP).

1. I open CCS I can compile the project.

2. I start the debugger (load to target)

3. I make some code changes and rebuild

4. Build fails and I get the following compiler error:

c:/ti/gcc-arm-none-eabi-4_9-2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3/../../../../arm-none-eabi/bin/ld.exe: cannot open output file WTSG_PN.out: Invalid argument

It does not matter if I terminate the debugger before the second build. If I close and open CCS I can compile it again.

This must in someway be related to the (GNU?) debugger and CCS. 

It does not help to close and open the project in CCS. I also cannot delete the .out file, when the debugger is terminated.

I  have another project based on a Hercules RM46x with the TI compiler, it does not have any problems.

/Mads

 

  • 0
    TI__Guru**** 171729 points
    Mads,

    Please apologize for the delay. I have seen this issue recently with GCC and CCS in a Hercules project but I can't seem to be able to reproduce it now.

    Among the several things I tried, I think I completely deleted the output directory (in your case AM437x_debug) and rebuilt the project - this will re-create several intermediate build files.

    Also, I recall copying a few compiler options (-march, -mfloat-abi, etc. ) to the linker Miscellaneous options, but at the time I was pursuing another problem and did not pay attention to the exact errors along the process.

    I will keep trying to reproduce this issue here and report back in case I find anything relevant.

    Regards,
    Rafael
  • 0 in reply to desouza
    Expert 1130 points

    Hi Rafael

    It must somehow be related to the GNU debugger and Code Composer Studio (I assume CCS uses GDB when we are using the GNU Compiler toolchain?).

    So it seems that CCS (with GDB) when debugging keeps a lock on the .out and does not ever release it - until I close CCS.

    If I do NOT start the debugger I can recompile without any problems (.out file is not locked).

    Regards,

    Mads