Thingy:52-SDK generate smaller hex than precompiled Thingy:52-HEX

RE: Thingy:52-SDK generate smaller hex than precompiled Thingy:52-HEX

Jørgen Holmefjord — Tue, 23 Apr 2019 07:24:35 GMT

Yes, 4.0.4 is just a bugfix release. It is compatible with 4.0.2 and can be used as replacement.

RE: Thingy:52-SDK generate smaller hex than precompiled Thingy:52-HEX

MarekPio — Sat, 20 Apr 2019 15:26:00 GMT

Hello,

I need softdevice s132 v4.0.2 according to https://github.com/NordicSemiconductor/Nordic-Thingy52-FW

But this version is no longer available https://www.nordicsemi.com/?sc_itemid=%7B10F110DE-001B-4C79-8E5E-1851FC80F751%7D

Can i use s132 v4.0.4? If i copy

s132_nrf52_4.0.4_softdevice.hex

/Thingy_52-SDK/project/pca20020_s132/armgcc/_build

can I merge them using command below?

mergehex -m nrf52832_xxaa_s132.hex s132_nrf52_4.0.4_softdevice.hex -o nrf52832_xxaa_s132.hex

Is that all I need to prepare working .hex for Thingy:52 example?

-----------------

The steps works. Thank you 🙂

RE: Thingy:52-SDK generate smaller hex than precompiled Thingy:52-HEX

Jørgen Holmefjord — Mon, 15 Apr 2019 13:10:27 GMT

Hi,

Most likely the precompiled HEX-file have the softdevice merged in, while your compiled HEX does not. You can merge the softdevice using our mergehex command line tool.

Also note that different compilers can produce different sized output. Optimization configuration in the project will also affect the buildsize.

Best regards,
Jørgen