CCS/MSP432P401R: How to enable Console printf/puts using FreeRTOS?

System_printf()
e2e.ti.com/.../802003

Thanks for the link, but CCS doesn't support use of XDC tools with FreeRTOS
e2e.ti.com/.../791747

I'm looking for a FreeRTOS console print statement.

More research finds this software-dl.ti.com/.../sdto_cgt_tips_for_using_printf.html
But, for someone still unfamiliar with the specifics of using CCS, some of the directions are extremely vague and offer no help.

Ex1: "Use the option --diag_warning=225 to see warnings for all functions used without a valid prototype."
Q1: Where do I enter this option?

Ex2: "C I/O Communication Buffer Placement ... The .cio data section contains the buffer _CIOBUF_, used by the C I/O functions and ... You must allocate the .cio section to valid read/write data memory."
Q2: Where is this .cio section and how do I allocate .cio to valid read/write data memory?

Keith,

I don't believe any of the freeRTOS examples included with the MSP432 SDK use the printf function from our C runtime library, so I can't say with certainty if that use-case has been tested/verified. The main take-aways from the "Tips for using printf" page you reference above are: including stdio.h, and ensuring there is enough stack and heap size (set in the Linker options).

It may also be worth investigating if freeRTOS provides something equivalent that may be less overhead than the one from our C runtime library. 

Here are a couple of related threads on this topic:

https://e2e.ti.com/support/tools/ccs/f/81/t/797547

https://e2e.ti.com/support/tools/ccs/f/81/p/600345/2219915

You could also create a new post in the MSP Microcontroller forum. It gets more visibility and there may be others in the community that may have attempted other ways of debugging other than UART, and may have additional suggestions. 

Thanks Ki. I think this is a viable alternative to directly printing to the console.

Given the link you posted, I was able to find more detailed info here that describes how to use the ITM Software Messages.

Unfortunately, the example code given above seems to be throwing a warning "Assembly statement "NOP" creates a label, which may not be what was intended. Use a colon after a label or a space before a non-label to silence the warning."

Here's the code that generates the warning.

void ITM_delay(unsigned num_loops) {
  unsigned i;
  for (i=0; i<num_loops; i++)   {
      asm ("NOP");
  }
}

The link didn't come through... Here is is again: http://dev.ti.com/tirex/explore/node?node=AApUdAazM-v07eIyAM5ftg__FUz-xrs__LATEST

Keith Padgett64 said:

Unfortunately, the example code given above seems to be throwing a warning "Assembly statement "NOP" creates a label, which may not be what was intended. Use a colon after a label or a space before a non-label to silence the warning."

To get rid of this warning, insert a space before the NOP instruction, like so: asm (" NOP");