• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 663 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/TMS320F28335: I see inconstant data debugging Micrium uCOS-iiI API calls

Luke Reuter
Prodigy 195 points
Part Number: TMS320F28335


Tool/software: Code Composer Studio

I'm not looking for help debugging my program, but I think I have a larger error somewhere in my project setup or memory map.

I have an application that reads serial data from SCI and we use the Micrium uCOS-III RTOS.  I'm packing the data into protocol packets and want to pas them up to a consumer task using uCOS-iiI API queue utilities.  I'm not getting data out of the queue that I'm putting in, so I set a break-point and stepped into the Micium code to see where I'm going wrong.  However, when I step into the header, the parameters im passing bouth simple integers and pointers to OS structures, look ok. But as I step into the body I get invalid addresses in pointers and/or "memory map will not allow access" type errors.  The API calls seem to complete successfuly, but the results are indeterminate.  The uCOS-III functions are in straight C, while my application is C++.  I've surrounded UCOS-III with extern "C" {} definitions.  I'm using CCS  7.2.0.00013

Am I exceeding the capabilities of the debugger stepping out of C++ into C?  Or do I have something askew in my memory map or project configuration?

  • 0
    TI__Guru**** 472171 points

    Hi Luke,

    It is hard to say what the exact issue is without a test case. Would it be possible to obtain the executable (*.out) you are loading to the target? Please start a private conversation if you do not wish to share it on this public forum.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 195 points

    Update:

    We've been using CCS V7 to support legacy programs, but this is a new application.  Upgraded to V9 and I no longer see the problem.  Also, under V7. I had an anoyance I just figured I'd live with: The expression window sometimes comes up with all of the watch expressions blanked.  I could click the mouse and see the variables, but couldn't see their values.

    This seems to be fixed as of version 9.  

  • 0 in reply to Luke Reuter
    TI__Guru**** 472171 points

    Thanks for the update Luke. The out file you provided looked fine. It was likely a bug in earlier versions of CCS that was fixed. We had several bugs with the debugger when debugging C++ code that have been since fixed. Likely your issue was related to one of these.

    Thanks

    ki