This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Eclipse compiled hex file smaller than included hex

I've managed to overcome all the quirks in setting up Eclipse/gcc development with the nRF52 PDK (PCA10056), and I can build the sample projects just fine. Here's my issue: If I compile and load the "blinky" example project, it runs perfectly. If I try to do the same with ble_app_uart, it compiles just fine, but when I load the resulting hex file, it doesn't work--the nRF Connect app can't see it, there's no blinking LED on the PDK, etc.

I also noticed that the .hex file that results from the build is only 84kB, whereas the pre-compiled .hex in the SDK is 421kB. I suspect there's something wrong with the build, so when it loaded onto the chip, it doesn't run correctly, but I have no idea where to start looking for issues--there are no problems in the build process.

I programmed the s140 SoftDevice to the target earlier, and have verified (using nRFGo Studio) that it's still there.

Where should I look in order to figure out what I'm doing wrong?

Related