• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 814 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.

Terminate Debug Session - Leaves CIO Files Open?

Anthony F. Seely
Guru 68950 points
Other Parts Discussed in Thread: RM46L852, HALCOGEN, LAUNCHXL2-TMS57012, ENERGIA

I've been working with CCSv6  (6.0.1.00040) and the XDS110 driver on an ARM target (RM46L852).

Can get more specific if needed, but basically I've got a very long test program logging results to a file, using fprintf() through CCS.

If the test program doesn't complete, but I need to restart it, it never calls fclose(). 

I can't delete the output file before running again because it's in use.

I'd think that terminating a debug session would be the right place for CCS to clean up and close any of these CIO files that are still open,  but it doesn't appear to be doing so because even after terminating the debug session the files still cannot be deleted.

To turn this into a 'question' - is this normal/expected and are there any suggestions on releasing the file so it can be deleted.

  • 0
    TI__Guru**** 171309 points
    Anthony,

    I will surely take a look at it. I vaguely recall seeing a similar scenario but I can't recall exactly the boundary conditions.

    Do you have a ready-to-run code that I could simply try to run on my launchpad? If not, no biggie (if HalCoGen is already supporting this device, which I think it is).

    Cheers,
    Rafael
  • 0 in reply to desouza
    TI__Guru 68950 points

    Hi  Rafael,

    Attaching the program that I was using and running into the problem with.  It runs on a LAUNCHXL2-TMS57012 launchpad (new one that came out in dec.)

    N2HET_ERRATA_CHECK_CHAMP_PGE.zip

    EDIT: corrected the file that I uploaded, initially it was the wrong one.

    To actually run the program to completion,  you need to have jumper wires connecting (in a Y topology)  J2 pin 9 to J4 pins 5 and 6.

    If you use the energia numbering that means booster pack pin 9 jumpered to pins 36 and 37.  (this is the numbering printed on the board).

    It'll probably take overnight to run to completion (maybe an hour or two or three.. so I let it go overnight.) 

    But if you interrupt it and terminate the debug session you can see that the file appears to still be 'open'. 

    -Anthony

  • 0 in reply to Anthony F. Seely
    TI__Guru**** 171309 points
    Anthony,

    Thanks for sending this. I will try to modify and get this running on my RM46.

    Cheers,
    Rafael
  • 0 in reply to desouza
    TI__Guru**** 171309 points
    Anthony,

    I was able to reproduce this and filed today SDSCM00051529. Please check its status on the link SDOWP in my signature below.

    I apologize for the inconvenience,
    Rafael