• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 747 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.

Printf(stderr) in CCS.

Kummi
Mastermind 6220 points


Hi,

We are using CCSv5 to debug DM8148 based application and we need some
advice on the Printf based on C I/O.

Currently we are using printf, stdout, fprintf etc to debug the DSP(C674x),
and printf, stdout, fprintf works well, but the problem is with the stderr stream.

With "stderr" the CCS prints the processor name "C674X_0" for each and every character as shown below.

[C674X_0] i[C674X_0] n[C674X_0] t[C674X_0] e[C674X_0] r[C674X_0] n
[C674X_0] o[C674X_0] n[C674X_0] _[C674X_0] i[C674X_0] n[C674X_0] i
[C674X_0] i[C674X_0] n[C674X_0] t[C674X_0] e[C674X_0] r[C674X_0] n
[C674X_0] o[C674X_0] n[C674X_0] _[C674X_0] i[C674X_0] n[C674X_0] i　 and so on....

Is there any setting possible to avoid processor name "C674X_0" for every character?
Please let us know if "stderr" cannot be used with C674x.

Best Regards
Kummi

  • 0
    TI__Guru**** 473541 points
    Hello Kummi,
    CCS will prepend the processor name before C I/O messages for multi-core debug sessions. This is because the C I/O console is shared by all cores and the processor name helps identify for which core the message is applicable to. To get rid of the processor name prepending, you can disable the option to use a single C I/O console for all cores. This will create a dedicated console for each core and eliminate the need to prepend the processor name before each message. The option can be found in the Debug Configuration. See Figure 3 in the link below:
    processors.wiki.ti.com/.../Multi-Core_Debug_with_CCSv5

    Thanks
    ki