https://devzone.nordicsemi.com/f/nordic-q-a/66115/question-about-built-hex-from-seggerHi-- I noticed something rather peculiar on the built hex from segger that is programmed onto my nrf52832 chip (firmware image). The hex looked as expected, until i got to this section, which threw me for a loop...what&#39;s with the random short linesen-USTelligent Community 13Wed, 23 Sep 2020 13:50:07 GMThttps://devzone.nordicsemi.com/thread/271129?ContentTypeID=1Wed, 23 Sep 2020 13:50:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bd41f25e-c39e-4496-9954-a86972f0c3bchaakonsh<p>It&#39;s&nbsp;probably zero padding. If the second hex you posted was a flash read-back then the resulting hex file is created without the context of the original hex file and therefore it cannot contain short records.<br /><br /><br /></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/270943?ContentTypeID=1Tue, 22 Sep 2020 19:54:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c8698a23-2dbc-4dbf-82a0-776d601cb394rsoc16<p>So the thing I am hung up on is zero padding. Is that a normal thing for nordic or segger? Ive never run into it for stm chips or keil.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/270479?ContentTypeID=1Mon, 21 Sep 2020 08:02:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:960bcec6-d225-42d9-9566-226f861d7bbcKenneth<p>I notice the data between AA66-AA67 is undefined (not used) in the hex file, likely they are zero padded by the programmer.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/270476?ContentTypeID=1Mon, 21 Sep 2020 07:56:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:555b1862-8729-4e13-82f9-af773fb3ec2dhaakonsh<p>See the&nbsp;<span><a href="https://en.wikipedia.org/wiki/Intel_HEX#Record_structure">Record structure</a>&nbsp;of the Intel hex file format.&nbsp;</span></p><div style="clear:both;"></div>