https://devzone.nordicsemi.com/f/nordic-q-a/25632/armgcc-compiled-dfu-has-logging-issuesI am using SDK 14.0.0 with Softdevice S132 V5.0.0 and the accompanied DFU libraries. In the examples\dfu\bootloader_secure_ble example I think the logging system has a problem. When compiling the debug version of this project using Keil MDK ( pca10040_debugen-USTelligent Community 13Wed, 14 Mar 2018 09:54:27 GMThttps://devzone.nordicsemi.com/thread/124323?ContentTypeID=1Wed, 14 Mar 2018 09:54:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a4b66555-e7ef-4c88-b258-575d8a3c42b4bjorn-spockeli<p>This is a known issue with SDK v14.0.0 and SDK v14.1.0, which has been fixed in SDK v14.2.0, see the release notes,i.e.<br /><br />&nbsp;- Fixed invalid module names in logger output when LTO was used in the GCC compiler.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/122571?ContentTypeID=1Fri, 02 Mar 2018 09:11:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d7f40dd2-7d0b-41ca-8036-550e537af8c7schef<p>It looks like the loging takes the wrong module name but i dont have that problem using gcc/g++</p><div style="clear:both;"></div>