Eclipse compiled hex file smaller than included hex

RE: Eclipse compiled hex file smaller than included hex

endnode — Fri, 16 Jun 2017 14:23:11 GMT

It sounds logical when think about it now... so merging HEX with SD and then using drug&drop should work next time.

RE: Eclipse compiled hex file smaller than included hex

zolotiyeruki — Fri, 16 Jun 2017 14:16:47 GMT

It looks like using nRFgo Studio to program the application worked. The drag-and-drop method must erase the entire flash when loading the new code.

RE: Eclipse compiled hex file smaller than included hex

endnode — Thu, 15 Jun 2017 22:21:22 GMT

OK. Compilation looks good, I would just stick (for the beginning) to the compilation chain Nordic recommends in nRF5 SDK V13.0.0 release notes: GCC ARM Embedded 4.9 2015q3. When it comes to verifying on PCA10058 bard:

You normally don't need to hook any additional cable like "Serial to USB" adapter, it should go through SEGGER J-Link OB serial port emulation (companion chip on the board which handles USB connection to PC host). All examples are using header files which should automatically use proper PINs to make this work. On PC side you should see J-Link COM port.
I never use this "drug and drop" programming method because I simply cannot control the process;) Setting up proper programming routine in nrfjprog (part of NRFTOOLS bundle) or nRFgo Studio (or anything else) should help. Then you can be sure that nRF52 chip is erased and programmed with both SD + APP HEX files.

RE: Eclipse compiled hex file smaller than included hex

zolotiyeruki — Thu, 15 Jun 2017 22:09:33 GMT

Here's the console output: uart_compile_log

I added a bunch of statements like this after various stages of the initialization in main()

printf("\r\nUART Start!\r\n");

When I copied the .hex file to the JLINK drive, rather than the file disappearing like it often does, the .hex file stays there. I also hooked up a serial adapter to the PDK, and saw nothing when I copied the file over. When I do it with the pre-compiled version, I see the "UART Start" appear, so I know it's all hooked up correctly.

RE: Eclipse compiled hex file smaller than included hex

endnode — Thu, 15 Jun 2017 21:46:31 GMT

Yes, console output. Alternatively build it with UART debug print outs, run some serial terminal (e.g. PuTTY) nd verify if FW boots and if so where it hangs.

RE: Eclipse compiled hex file smaller than included hex

zolotiyeruki — Thu, 15 Jun 2017 21:33:15 GMT

Do you mean the output in Eclipse's Console when I build the project, or some other sort of ourput?

RE: Eclipse compiled hex file smaller than included hex

endnode — Thu, 15 Jun 2017 20:54:15 GMT

Hi,

First of all the HEX files supplied with SDK are already merged with Soft Device (where applicable), you can easily verify that by comparing content with any tool like Kdiff3. Then even if you strip SD part and compare just "APP" you will most probably arrive to different content and size because Nordic compile by default with Keil or IAR and you are using GCC. But that should not be a big problem (and if you like to start with 100% binary compatible output - as I do - you will need to use different compilation chain - which I don't like as well, GCC is great).

The fact that your FW is not working is probably caused by some linking/include error, e.g. not setting RAM and FLASH boundaries properly in LD script or so. If you show us more from GCC output when you build the thing we might give you more hints.

Cheers Jan