https://devzone.nordicsemi.com/f/nordic-q-a/29011/consecutive-printf-statementsWhen an interrupt with a printf in it triggers while another printf is still occuring the previous message is cutoff to print the next one. Is there a way I can wait for the tx buffer to be empty before writing the next message?en-USTelligent Community 13Sun, 21 Jan 2018 13:18:14 GMThttps://devzone.nordicsemi.com/thread/114754?ContentTypeID=1Sun, 21 Jan 2018 13:18:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:979c5e46-ebf1-43ab-ba21-6aa6e4515c8dstudzinski<p>Not true. In this example nothing is stated about printf, only one character sending is considered...</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/114753?ContentTypeID=1Fri, 07 Aug 2015 12:43:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7f47c123-398f-4e56-91cd-70754660e608&#216;yvind Karlsen<p>Hi,</p> <p>The app_uart example implements what you are asking for. Be aware that printf statements are usually high in CPU usage.</p> <p>Best regards,</p> <p>Øyvind</p><div style="clear:both;"></div>