arm-gcc executable not working. Flashing ok.

[Robert]

Hello ! I am using Red Bear Nano which has nrf51822 and I have connected it to a computer with linux. On the computer I downloaded arm-gcc version 4_9 and I linked it to the nrf51 version 11 sdk. And it compiles great. I wanted to flash an example to see if flashing the Red Bear works and when I flash, the hex resulted from the make command in the pca10028->armgcc folder, I cannot find it when I scan it with NRF Connect app on my Android phone. However, when I flash the already existent hex file from ble_app_hrs->hex directory it works fine. I made a diff between the two hex files and the result of the command says that they differ. Should they differ ? I cannot understand what is the problem. I didn't modify any code of the source files. I compiled them directly.

[Ole Bauck]

The hex differ because the already existing file in the SDK is compiled using ARMCC (Keil), while the one you compiled was with arm-gcc. Did you remember to flash the SoftDevice before flashing the GCC hex (the already existing hex has SoftDevice + application)? Did you reset the device after programming it?

[Robert]

Yes, I flashed the softdevice and then the gcc hex. Yes, I did a reset and a go with the JLink debugger.

[Robert]

I flash the hex to address 0x1B000

[Robert]

I got it to work. It didn't advertise because it was halting in a i2c read that never returned. It's ok now. I commented out that code and compiled and uploaded the code again and it works like magic.