nRF52 DK PCA10040 demo not work from GCC build

[bluewishken]

Hi, I got nRF52 DK PCA10040 device(s132) and follow the steps from devzone.nordicsemi.com/.../ to use arm-none-eabi-gcc(version 5.4) to build examples like blinky. I can successfully built out hex file and flash to device. After flashing, I found device not work. But if I flash pre-built hex from the hex folder in each example, the device work as expect. I tried on windows 10 and ubuntu 14.04, and both hex built from source can not work. How can I built out workable hex file?

[bluewishken]

I tried C:\nordic\nRF5_SDK_11.0.0_89a8197\examples\peripheral\blinky\pca10040\blank\armgcc, sound like this is work, but C:\nordic\nRF5_SDK_11.0.0_89a8197\examples\peripheral\blinky\pca10040\s132\armgcc is not work...

what different between s132 and blank?

[bluewishken]

Sorry, I have got answer..... blank means started from flash 0x0, but s132 means from 1c000. If using s132 project, need flash boot loader to co-work example code....

[tesc]

Hi,

As you have already found out yourself: When you use the SoftDevice both SoftDevice and application must be downloaded to the board. When you do not use a SoftDevice then you only download the application.

The location of the application in flash varies depending on SoftDevice, as the application is put after the SoftDevice. This is the difference between the s132 and blank versions of blinky.

Regards, Terje

[vikrant8051]

First of all, we have to flash ->

nRF5_SDK_xxxx/components/softdevice/s132/hex/s132_nrf52_xxx_softdevice.hex

into microcontroller using any programmer. In my case it is ST-Linkv2.

Then we can flash hex file available in s132 after building the project from any available demo project.