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: on CCS5 simulator console prints nothing

Tool/software: Code Composer Studio

Hello there,

I am using CCS 5.4 simulator for simple EVE programming.

I am able to execute code successfully , even getting expected output ( confirmed with debugging ).

But problem is, on console no logs or printfs are showing!!

More details,

For now example is taken from EVE_example_kernels_1.0.0.0.zip  " array_add_uns_char "

CCS version :- 5.4.0.00091

Vayu Subsystem Simulator

So need your help for the same!!

Regards,

Kajal

  • Kajal,

    One common reason for printfs not appearing in the CCS console is insufficient stack and heap sizes. Please take a look at this article for more details.

    Also please note that CCSv5 and simulators are no longer supported, so we can only provide limited assistance. However, I am hopeful that the above article should be able to point you in the right direction.

  • Hello AartiG,

    Can you please tell us where to edit stack and heap sizes ??

    Regards,
    Kajal
  • It would be in the project's linker options. Project Properties->Build->Linker->Basic Options. The options are --stack_size and --heap_size.
  • Hello Aarti,

    I have increased size to 0x400 and again to 0x1024, though i am not getting logs on console!!
    Just want to know, why the size issue ??
    Also I have created short cut on desktop, but it is also not showing.

    Need help for same

    Regards,
    Kajal
  • Kajal,

    I'm not sure I understand your last statement.

    Maybe your heap needs to be increased even more. It really depends on how many printf statements you have in the code. If you have many, perhaps you could try commenting some of them out while leaving only one or two just to test if keeping just one or two statements works. Try increasing both heap and stack to as much as the memory on your device permits. Once you get the console I/O working you can always reduce the sizes to more optimal values.