• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 904 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.

CIO message error generated upon startup

BrandonAzbell
Guru 64820 points

Customer is using the following software combination, which appears to be a supported combination based on the release notes of SYSBIOS v6.35.03.47.

CCS v5.40
ControlSuite v3.21
Compiler version TI 6.1.3
SYSBIOS v6.35.3.47
XDCTools v3.25.2.70

Device : TMS320F28069

How can we generate a breakpoint when debugging when a CIO message pops up?  This way we might be able to find more information about the specific message.
Our code (attached) generates the following error on startup: “[C28xx] Write error: Invalid File ID (11) in CIO message!”  Please explain what this error means and how to resolve it.

  • 0
    TI__Guru* 96960 points

    Hi Brandon,

    I talked to an CCS engineer and he thinks this is a CCS question. I'll get this move to that forum.

    Todd

  • 0 in reply to ToddMullanix
    TI__Guru 64820 points

    Bumping due to move to CCS forum.

  • 0 in reply to BrandonAzbell
    TI__Expert 5985 points

    Hi,

    CIO works by setting a hidden breakpoint at a specific point and then reading control values and data out of a buffer.  The error means that the buffer requested a write to file id #11, but that file id hasn't previously been opened.

    Currently there's not way to auto-halt when an error like this happens.  I've filed SDSCM00047967 so that we can address that in the future.

    For now, you could set your own breakpoint at the same point (set it at the label C$$IO$$), and keep re-running on each halt until you see the error message.  Once you see the error, then don't re-run and debug from there as normal.  If the breakpoint is hit many times before the error, try setting a skip count on the breakpoint (right click on it in the breakpoints view, select properties, expand the nodes until you find "skip count").  You can use a binary search to find the correct skip count.

    You may find that the CIO target code is built without any symbols.  In that case, you can rebuild it with symbols - I believe the source is located in rtssrc.zip in the lib directory for your compiler.

    Darian