Question about built hex from segger

[rsoc16]

Hi--

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's with the random short lines?

Additionally, when I examined what was programmed against what was in this hex, it didnt line up (had some extra zeros after the first short line)

First section of code is the hex. Second is what is programmed based on that section. The extra zeros are evident in the first line based on the combination of the first two lines in the sample hex.

Is this normal? Can someone tell me why?

:06AA6000A0EB01007047AD
:10AA6800F9E401000000000001EF0100000000000F
:10AA7800658C0300000000002D3802000000000073
:10AA8800F1940300D42D0020A1840300F02D0020B0
:10AA9800658A030000000000D75202004823002006
:10AAA80097970300E42D0020014A020000000000EF
:10AAB800DDE501000000000029EF010000000000B2
:10AAC80089A00300000000003DA103000000000071
:08AAD800B5E5010000000000DB
:10AAE000F8240020302400203824002038240020BE
:04AAF000180000004A
:10AAF4007CB503000000000084B5030000000000E2
:10AB0400B0B50300000000008CB503000000000095
:10AB1400B4B5030000000000A8B503000000000065
:10AB240090B50300000000009CB503000000000085
:10AB3400E4AB030000000303A8AC03000000000022
:10AB4400D0AC03000000000074B503000000000056
:10AB5400F8C7030000000303C4B2030000000303AA
:10AB64006CC80300000003039CC803000000030337
:10AB740034CB03000000030378AD030000000000A1
:08AB840090AD03000000000089
:10AB8C00B0AB030000000000C8AB0300DC220020C7
:10AB9C0000000000000000003D8802000090010051
:04ABAC00000007009E

:10AA6000A0EB010070470000F9E4010000000000C5
:10AA700001EF010000000000658C030000000000F1
:10AA80002D38020000000000F1940300D42D0020B6
:10AA9000A1840300F02D0020658A0300000000005F
:10AAA000D75202004823002097970300E42D00208E
:10AAB000014A020000000000DDE501000000000086
:10AAC00029EF01000000000089A003000000000041
:10AAD0003DA1030000000000B5E5010000000000FA
:10AAE000F8240020302400203824002038240020BE
:10AAF000180000007CB503000000000084B50300CE
:10AB000000000000B0B50300000000008CB5030099
:10AB100000000000B4B5030000000000A8B5030069
:10AB20000000000090B50300000000009CB5030089
:10AB300000000000E4AB030000000303A8AC030026
:10AB400000000000D0AC03000000000074B503005A
:10AB500000000000F8C7030000000303C4B20300B4
:10AB6000000003036CC80300000003039CC803003B
:10AB70000000030334CB03000000030378AD03009F
:10AB80000000000090AD030000000000B0AB030027
:10AB900000000000C8AB0300DC2200200000000021
:10ABA000000000003D880200009001000000070046

[haakonsh]

See the Record structure of the Intel hex file format. 

[rsoc16]

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.

[haakonsh]

It's 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.