• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 4594 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Invalid CIO command (**) in the CIO buffer at address (0x****) was not recognized

FENG SUN57683
Intellectual 895 points

hi

   We have got a CIO problem here that drives us crazy.

   What we are using now is CCS5.1.1.00031 and BIOS 6.32.5.54, and the codes runs on the C6747 DSP. We had already built a ccs project that ran without any problem on the DSP, but after we add some flash writing codes into the project, the following message comes out in the console window when we try to load the generated .out file into the DSP:

           Invalid CIO command (**) in the CIO buffer at address (0x****) was not recognized

  I tried to comment some lines of the original codes to decease the size of used memory sections in the .map file, so that overflows may be avoid, and that solves the problem. But that is not what I want.

  From some other threads it seems like a heap size related problem. since the .cmd file is generated by a sys/bios project, I tried to modify the .cfg file and rebuild the project. But whatever  I do, the following three lines in the .cmd file refuse to change:

--args 0x0

-heap 0x0

-stack 0x1000

By the way, We are putting all sections in the internal memory.

  • 0
    TI__Guru**** 168422 points

    Hi,

    Usually these error messages are caused during runtime - i.e., whenever a Console I/O function is used (printf, scanf, etc.). There are some reports showing this across the forum (two very relevant ones are here and here).

    However, they are very uncommon to happen during a program load. In your case it is possible the issue at hand may be related to the emulation package software you are running (the component that connects CCS to the emulator). A few threads hint that this could possibly be the case (here and here).

    In this case, I would either try to update the emulation pack (check this reference) or install a more modern version (v5.5) in a separate directory and try to use it only to debug the project (or migrate everything in steps). If you create a new workspace for the new version, you can still do code development with the older version and therefore prevent any disruption in your current environment.

    Hope this helps,

    Rafael

     

  • 0 in reply to desouza
    Intellectual 895 points

    hi Rafael:

    sorry for the delay.

    However, they are very uncommon to happen during a program load.

    I attached a .gel script to the .ccxml file to do some initialise work when loading the .out file, in which some printf lines are presented.

     I don't  think it is a CCS version related problem, because I have successfully debuged with this version many  times.both the originial project and the flash writting project work fine alone. the only thing that changes may be that when they are put together, the used  memory section size  may get larger, where an stack/heap overflow may occur.

    As I mentioned above, it seems that the heap size in the .CMD file refused to change when I try to modify it in the sys/bios project, I am wondering where I was wrong.