Other Parts Discussed in Thread: MSP-FET
I'm a bit confused by the purpose of the DisplayHost driver provided in the SimpleLink MSP432P4 SDK (docs at http://dev.ti.com/tirex/explore/content/simplelink_msp432p4_sdk_3_40_01_02/docs/tidrivers/doxygen/html/_display_host_8h.html).
Looking at its source within the SDK's install path, it looks like it ultimately just calls `fwrite(…, stdout);` with the formatted result of whatever I would `Display_printf(…)` as a user. But what does `fwrite` do on the MSP432?!
It's clear that TI has set up stdio to be conformant with what I presume would be relevant C or C++ standards (i.e. rather than POSIX since this isn't dependent on the SimpleLink POSIX wrapper stuff). Is the implementation of the stdio functions available somewhere? Is it just a stub implementation, e.g. an fwrite() to stdout just gets discarded, or is there builtin debugger support or something? Is there a documented way to overwrite these so that DisplayHost will write somewhere useful?
Basically wondering if/why/how one would ever use DisplayHost (versus e.g. DisplayUART on a LaunchPad or custom serial backchannel port) and that's leading me to wonder the same regarding the compilers stdio stuff as well -- is it just there so code can compile, or would said code also "work" somehow with a default stdin/stdout actually hooked up? And if so can I change what writing to those std descriptors does?