view target-utils/libprintf/README @ 718:098fea21ba13

doc/Host-tools-overview: tiffs-mkfs description updated The first version of tiffs-mkfs did not include a journal file in the created FFS, expecting the firmware to create it on first boot. All historical firmwares prior to a recent FC fix (2020-05) contain a bug in that code path, thus images made with the first version of tiffs-mkfs were only acceptable to very recent FC firmwares. tiffs-mkfs has now been extended to include an empty journal in the created FFS, thus the restriction of working with recent fw only has been lifted.
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 23 Aug 2020 04:55:02 +0000
parents e7502631a0f9
children
line wrap: on
line source

The present libprintf is a very light printf implementation that is well-suited
for simple bare-metal programs like loadagent; in the present case it overrides
the much heavier printf implementation in newlib.  Programs like the present
loadagent only need printf in order to scribble on the serial console port,
and the most sensible implementation is to have the "character output" function
from the guts of printf point directly to the physical UART output routine, or
a trivial wrapper that turns \n into \r\n.  In contrast, newlib's version would
pull in the complete FILE table infrastructure and malloc etc - maybe OK for
more complex embedded programs that use those facilities for other things under
a bona fide RTOS, but it would be disgusting to pull that stuff in for a
minimal program like ours.

The present printf implementation has been used earlier by the same author
(Michael Spacefalcon) in the StarMON family of PowerPC bootloaders, and in my
MC68x302-based SDSL CPE devices (Hack-o-Rocket and OSDCU).