NRF_LOG preprocessor code created incorrectlyhttps://devzone.nordicsemi.com/f/nordic-q-a/65134/nrf_log-preprocessor-code-created-incorrectlyI&#39;ve been having problems trying to get any of your example project to use NLOG to a uart port that we have made available for production test on our new product. I&#39;ve chosen the temperature example as one of the simplest so less likely to have otheren-USTelligent Community 13Sun, 30 Aug 2020 21:18:05 GMTRE: NRF_LOG preprocessor code created incorrectlyhttps://devzone.nordicsemi.com/thread/267104?ContentTypeID=1Sun, 30 Aug 2020 21:18:05 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3185268a-86ed-45d5-b0c5-dec96b43cfb7Simon<p>Based on your debugging it seems like it is a SEGGER specific issue. You could&nbsp;<a href="https://www.segger.com/support/technical-support/">file a&nbsp;ticket</a>&nbsp;to SEGGER&#39;s technical support and ask about it.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>RE: NRF_LOG preprocessor code created incorrectlyhttps://devzone.nordicsemi.com/thread/265942?ContentTypeID=1Mon, 24 Aug 2020 11:15:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:028d19e5-2c0f-48bd-8e01-7c088d5a73ecBrian Shankland<p>Further information:</p> <p>When stepping through the code the debugger steps into the &quot;not-included&quot; arm i.e. the correct code for the definitions, so this may be a Segger Studio display issue.</p><div style="clear:both;"></div>