• State Not Answered
  • Replies 4 replies
  • Subscribers 62 subscribers
  • Views 2248 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 114913
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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?

Parents
  • 0

    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

Reply
  • 0

    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

Children
No Data
Related