Why size of S112, nrf52810 softdevice, is bigger than flash memory?

RE: Why size of S112, nrf52810 softdevice, is bigger than flash memory?

neosarchizo — Mon, 30 Oct 2017 08:31:58 GMT

@endnode Thanks. I got it!

RE: Why size of S112, nrf52810 softdevice, is bigger than flash memory?

endnode — Mon, 30 Oct 2017 04:24:28 GMT

I've thought I made it clear but probably not: size of the HEX file on your computer (281kB) has almost nothing to do with binary size on target chip. HEX file is text file which only says which part of the binary should be loaded to what address. In human readable form (just open it in Notepad or similar SW and read). If you have HEX file and you want to know what actual size on target memory model the binary consumes you need to either convert it to some binary format (e.g. GCC has some command line utils) or you need to learn how to read Intel HEX format and do it manually by reading the file basically line by line. Or you just load the file to the chip and let some dump tool tell you what is used memory size. In every case you can trust Nordic documentation: if release notes say that S112 has 100kB it really has 100kB.

RE: Why size of S112, nrf52810 softdevice, is bigger than flash memory?

neosarchizo — Mon, 30 Oct 2017 04:18:46 GMT

I downloaded S112 V5.1.0-2.alpha, too. There is s112_nrf52810_5.1.0-2.alpha_softdevice.hex in it. As you said, isn't it matter that size of the file? Size of the file is 281 kb.

RE: Why size of S112, nrf52810 softdevice, is bigger than flash memory?

endnode — Mon, 30 Oct 2017 03:54:08 GMT

You are mixing size of HEX file on PC (= text file) and binary on the chip. Study how Intel HEX format looks like. The size of S112 V5.1.0-2.alpha is 100kB (as explained also in release notes attached to the HEX file).