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

[MarekPio]

Hello,

I got Thingy:52-SDK-zip from https://www.nordicsemi.com/Software-and-Tools/Development-Kits/Nordic-Thingy-52/Download

and I did all setps wrote in README.md. Then I did "make -j" in path /home/marek/ARM/thingysdkv210/project/pca20020_s132/armgcc without errors

following nordicsemiconductor.github.io/.../firmware_compile.html

The problem is after programming

nrfjprog --family nrf52 -e

nrfjprog --family nRF52 --program nrf52832_xxaa_s132.hex

nrfjprog --family nRF52 -r

Thingy 52 is not working.

The .hex file generated from SDK is 524,9 kB, the hex from Thingy:52-HEX is 873,3 kB.

What is wrong?

[Jørgen Holmefjord]

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

[MarekPio]

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

to

/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 

[Jørgen Holmefjord]

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