Issues with nRF51 4.3 SDKhttps://devzone.nordicsemi.com/f/nordic-q-a/180/issues-with-nrf51-4-3-sdkHi, I upgraded to the 4.3 nRF51 last night and am suddenly having a whole slew of issues: (1) When flashing the EK, the Segger now reports 257K of Flash (maybe it did this before and I never noticed?). Symptom is not being able to Flash. I&#39;ve checkeden-USTelligent Community 13Thu, 01 Aug 2013 11:49:01 GMTRE: Issues with nRF51 4.3 SDKhttps://devzone.nordicsemi.com/thread/1001?ContentTypeID=1Thu, 01 Aug 2013 11:49:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ee31f5e0-4b9f-4ac7-bc96-195cad8ecceeOle Morten<p>As I said, feel free to accept your own answer, since that explains clearly what was wrong.</p><div style="clear:both;"></div>RE: Issues with nRF51 4.3 SDKhttps://devzone.nordicsemi.com/thread/1000?ContentTypeID=1Mon, 29 Jul 2013 11:49:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e97b83f1-1f2b-43ab-84f8-e8fab659ee27Ole Morten<p>If this was the problem and everything now works nicely, I suggest that you accept your own answer. :-)</p> <p>The device error messages are BTW intended, and are there to make sure that workarounds for the appropriate PANs are used. Currently the use is mostly the two lines you&#39;ve found, but this may expand in future SDK and chip releases. Currently it&#39;s mostly a way to at least try to future-proof things.</p><div style="clear:both;"></div>RE: Issues with nRF51 4.3 SDKhttps://devzone.nordicsemi.com/thread/999?ContentTypeID=1Sun, 28 Jul 2013 14:13:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e4ce7610-4937-441f-83d0-e51952a55a4eMarc Nicholas<p>I fixed this....for some reason my memory offsets got defaulted when I imported an existing project. uVision issue?</p> <p>-m</p><div style="clear:both;"></div>