• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 425 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.

.out file is not getting made

brandon berk
Prodigy 10 points

Hi, I am trying to have both port 1 and port 2 interrupts working. I am able to have either port 1 or port 2, however when I trying enabling both at the same time I get an error stating that my .out file could not be opened. I checked the debug file and it was never made. I have also checked the mps430F2259.h file and the ports do have different interrupt vectors. Is there any kind of fix or work around for this?

  • 0
    TI__Guru 61235 points

    If the .out file is not being made, then there must be a build error, either compiler or linker.  What is that error?  That will tell you what is wrong.  Look at the command console in CCS when you build the project for the build errors.

    - David

  • 0
    Genius 4140 points

    Hi Brendon.

    I had the same problem a couple of days ago. It was stupid tough,

    I have declared a variable as uint64_t  var_temperature = 0; and then duilt it. The code was building fine but there was an saying .out file could not be opened coz it was never created.

    Once I changed it back to uint32_t var_temperature = 0; it was successful.

    This is no where related to you, but what I found was, if there were any declarations, either user or compiler specifics like that please double check them and try to comment out lines in either port1 isr or port 2 ISR and debug them, u will find the problem.

    Cheers.

  • 0
    Guru 227245 points

    brandon berk said:
    . I checked the debug file and it was never made.


    If it was never made, then you either have configured the linker to not output it (and generate something else instead, maybe a TI.TXT file) or you got some kind of error message. Maybe not where you did expect it, but it was there. A linker error, a script error, a compiler error. It might be a special kind of error that wasn’t detected by the IDE for some reason and therefore the IDE proceeded to the debugger, but there must be some hint why the file was not generated.

    If indeed the change to uint64_t was the reason, then you likely got a compiler error for an unsupported type. Or the use of that type somehow caused an internal linker error (e.g. abnormal program termination) which wasn’t detected by the IDE as a build error. Check again. The truth is out there.

**Attention** This is a public forum