In (especially) embedded projects, logging to an UART directly may case RT-issues, i.e. creating new problems. This is solved by logging to RAM instead as an intermediate step, there-by decoupling the probing-phase from the print-out/inspection-phase.
(Something needs to pull the logs of-course, but that is not the primary concern in this issue as it may probably be done differently from case-to-case.)
Considerations:
- No complex configuration should be needed
- Can not rely on
malloc (i.e. allocated buffert-pointers). In the deeply embedded case with low RAM boundary protection, and especially considering that logs themselves become imperative for analysing fault's, logs must not be damaged.
In (especially) embedded projects, logging to an
UARTdirectly may case RT-issues, i.e. creating new problems. This is solved by logging to RAM instead as an intermediate step, there-by decoupling theprobing-phasefrom theprint-out/inspection-phase.(Something needs to pull the logs of-course, but that is not the primary concern in this issue as it may probably be done differently from case-to-case.)
Considerations:
malloc(i.e. allocated buffert-pointers). In the deeply embedded case with low RAM boundary protection, and especially considering that logs themselves become imperative for analysing fault's, logs must not be damaged.