https://devzone.nordicsemi.com/f/nordic-q-a/21487/openocd-and-the-nrf-not-flashing-complete-hex-fileI&#39;m trying to flash a nRF518122 with a St-Link V2 programmer via Open OCD. The process seems to goes smooth, but comparing the number of written bytes to the actual HEX size are not the same (about a third) and (of course) the nRF51 does nothing. en-USTelligent Community 13Thu, 20 Apr 2017 12:13:59 GMThttps://devzone.nordicsemi.com/thread/84312?ContentTypeID=1Thu, 20 Apr 2017 12:13:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7750c18d-1bef-4f35-8bb3-b3272e5c2a3dRonaldo Pace<p>and I thought I was going crazy. Thanks a lot. Now I&#39;m using the generated .bin file to flash (instead of the hex) and managed to call <code>flash read_bank</code> and md5 the two. They match. I&#39;m in talks to the hardware guy as the problem seems to be on hardware. Thanks.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/84311?ContentTypeID=1Thu, 20 Apr 2017 10:21:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:74705cf8-8f4a-41e8-ab14-8e42d7032c20RK<p>Well your file is likely only 47164 bytes long. The size of the HEX file and the size of the actual binary it represent of course are radically different because HEX files are an ascii encoded format. The file transferred is the binary file. HEX files are about 2.5-3 times the size of the underlying binary.</p> <p>Look at the map file created, that will tell you how big the application actually is.</p><div style="clear:both;"></div>