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

Invalid CIO command

gaurav pahuja
Prodigy 100 points

Other Parts Discussed in Thread: TMS320C6745, TMS320C6747

Hi,

I am using TMS320C6745 DSP for developing a board. Using CC studio and selecting the simulator connection I am running the sample projects, but every time I run a program an error comes.

Invalid CIO command (0) in the CIO buffer at address (0x69e8) was not recognized. Please check the device and program memory maps.

Please let me know the reason for this.

Gaurav

  • 0
    TI__Guru**** 480691 points

    Hello Gaurav,

    This issue has been raised in the past. There are several potential causes. You haven't mentioned what version of CCS you are using. If you are not already, the first thing I I recommend is updating to the latest version of CCS. There was a known issue with CCSv5.1.0  regarding CIO that was fixed in 5.1.1. Let me know if this helps or if you are already using 5.1.1.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Expert 7225 points

    Hi Ki

    CCS5.2 is what he is using. Is this fixed here...?

    Best Regards

    Feroz

  • 0 in reply to K Md Feroz Irfan
    TI__Guru**** 480691 points

    I would expect that it is also fixed in 5.2. If the issue persists in 5.2, then there could be other factors involved. The thread referenced below has more details on the issue with some suggestions.

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/76336/376071.aspx

  • 0 in reply to Ki
    Prodigy 100 points

    Sir,

    I am not able to understand much from the thread you provided still I am able to solve the issue. I am explaining you what I did with a vague idea, do correct me if I am wrong. For my DSP(TMS320C6745) there is no Windows Command Script i.e. .cmd file in the software libraries. When I added the the Windows Command Script file of TMS320C6747 in my work-space and linked it with my project it worked fine and there were no C I/O errors this time. But I think the issue is something different as I am not adding the .cmd files in any other processor while running the codes using simulator for ex. TMS320C6713 and still the code is running well. So I want to know that what is the exact issue. it is because of standard C functions used to output text like printf or the fault is in the .ccxml file (target configuration file) which is behaving differently for different devices or its just the absence of .cmd file for my device.

    Gaurav  

  • 0 in reply to gaurav pahuja
    TI__Guru**** 480691 points

    Gaurav - thanks for the follow up.

    yes having a CCS linker command file (*.cmd) would help (note that it is completely unrelated to the windows command script, they just share the same file name extension). In the thread I referenced earlier, having a correct *.cmd file for your project would resolve one of the causes mentioned by MartinS: "This region may not be a valid memory for your device". The linker command file specifies the target memory layout to the compiler so that it know where to properly place your code/data.

    gaurav pahuja said:
    But I think the issue is something different as I am not adding the .cmd files in any other processor while running the codes using simulator for ex. TMS320C6713 and still the code is running well.

    It was fine on simulator because most simulators assume flat memory where all memory is read/write-able. basically that all memory is "valid". This is not the case on real hardware and it is very important you use a correct linker command file for your project if you want to load/run on hardware.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 100 points

    Hi Sir,

    Thanks for the help.

    That's true that the case will be different when I will be working on real hardware but simulator must behave similarly for all the devices either demand for a *.cmd file or assume complete memory as a  read/write-able.

    Best Regards

    Gaurav

  • 0 in reply to gaurav pahuja
    TI__Guru**** 480691 points

    The recommended method is to use a custom startup GEL file that will configure the debugger memory map for the simulator to mimic your target board. That way you would see the same error with the simulator.

    Thanks

    ki