Compiler: BIOS System_printf usage

Tool/software: TI C/C++ Compiler

hello, printing to the console does not occur immediately when stepping beyond printf. At full execution speed, items print to the console.

The code is the same, Why is the behavior difference

thanks

over 5 years ago

0 Keith Barkley over 5 years ago

Guru 42545 points

Probably buffering. Try putting in an fflush().

0 ToddMullanix over 5 years ago in reply to Keith Barkley

TI__Guru* 96960 points

JW,

Are talking about calling printf or System_printf? If it is System_printf, take a look at this FAQ: https://e2e.ti.com/support/processors/f/791/t/883775

Todd

0 jw over 5 years ago in reply to ToddMullanix

Expert 1190 points

Hello, adding System_flush(); after System_printf ("Running task1 function\n");why is this the case?

shouldn't "\n" have the same result as System_flush().

0 Keith Barkley over 5 years ago in reply to jw

Guru 42545 points

AFAICT - I have not looked at the source - the System stdio calls go strictly by the number of characters in the buffer to instigate an automatic flush. '\n' has no effect. I am sure that this is implementation dependent, especially since this is a non-hosted environment.

0 ToddMullanix over 5 years ago in reply to Keith Barkley

TI__Guru* 96960 points

The whole point of the SysMin provider is to minimize real-time impact on the system while still providing a "printf" like functionality. The '\n' is written into the internal buffer and can be seen in ROV. We realized some people would still what the data to come out the console, so we added that functionality into SysMin's flush command.

Remember also that the System_printf functionality is "printf"-like...not exact. If we wanted exact, we would have provided a new implementation of printf.

Todd

Code Composer Studio™︎

Code Composer Studio forum

Compiler: BIOS System_printf usage