Chuck,
Thanks for the feedback. I have added the PDK Project Create wiki article to the getting started guide under examples and demonstrations:
As far as using UART for printf is concerned, all the examples in the PDK use UART for sending log messages to the serial terminal on the PC.
Please refer to the code provided in all the driver examples. Please refer to how this is implemented in SPI driver test code under
C:\ti\PSDK_32_preGA\pdk_k2g_1_0_4\packages\ti\drv\spi\test\src
the file, SPI_log.h defines a MACRO SPI_log which is defined as
#ifndef IO_CONSOLE #define SPI_log UART_printf #else #define SPI_log printf #endif
UART_printf is a function implemented in the UART driver that directs printf messages to UART. In order to do this, you will need to call the Board_Init API in board library with the following settings:
/* Call board init functions */
Board_initCfg boardCfg;
boardCfg = BOARD_INIT_PINMUX_CONFIG |
BOARD_INIT_MODULE_CLOCK |
BOARD_INIT_UART_STDIO;
Board_init(boardCfg);
After this you will need to link to the UART driver and either create a MACRO like SPI_log or API UART_printf to send logs to the serial console at 115.2kbps.
Regards,
Rahul
Chuck,
Ok, It looks like you are trying to override the printf() and gets() functions from the standard compiler IO function. I don`t think this is something that the TI RTOS Semihosting configuration. Adding that module to the configuration simply adds rdimon GCC library as you can see from the file SemiHostingSupport.xdc in that package.
In order to over ride printf, can you remove Semihosting from the configuration and use GCC compile time flags -fno-builtin-fprintf and -fno-builtin-printf. If you now define a local printf function to route output to UART, the compiler should ignore the printf from the runtime GNU library. I haven`t tried this my self but this has been known to work on some GNU forums.
Hope this helps.
Regards,
Rahul