Developing for nRF52810 - the full story?

RE: Developing for nRF52810 - the full story?

Zaf — Tue, 01 Feb 2022 22:26:10 GMT

I am using IAR compiler with nRF5_SDK_14.0.0_3bcc1f7. I get the same error. I searched for FLOAT_ABI_HARD in all the .h and.c files, but it can't find it.

Below is the compilation error.. Thanks..

app_error_weak.c
iccarm.exe C:\800_bluetooth\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\util\app_error_weak.c -D BLE_STACK_SUPPORT_REQD -D BOARD_PCA10040 -D CONFIG_GPIO_AS_PINRESET -D NRF52810_XXAA -D NRF52_PAN_74 -D NRF_DFU_SETTINGS_VERSION=1 -D NRF_SD_BLE_API_VERSION=5 -D S132 -D SOFTDEVICE_PRESENT -D SVC_INTERFACE_CALL_AS_NORMAL_FUNCTION -D SWI_DISABLE0 -D __HEAP_SIZE=0 -o C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\_build --debug --endian=little --cpu=Cortex-M4 -e --warnings_are_errors --fpu=VFPv4_sp --dlib_config C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.3\arm\inc\c\DLib_Config_Full.h -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\ble\common\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\boards\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\device\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\drivers_nrf\clock\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\drivers_nrf\common\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\drivers_nrf\delay\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\drivers_nrf\hal\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\drivers_nrf\rng\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\atomic\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\balloc\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\bootloader\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\bootloader\ble_dfu\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\bootloader\dfu\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\crc32\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\crypto\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\crypto\backend\micro_ecc\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\crypto\backend\nrf_crypto_sw\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\experimental_log\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\experimental_log\src\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\experimental_memobj\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\experimental_section_vars\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\fstorage\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\hci\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\mem_manager\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\queue\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\scheduler\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\sha256\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\strerror\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\svc\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\timer\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\libraries\util\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\common\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\s132\headers\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\s132\headers\nrf52\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\toolchain\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\toolchain\cmsis\include\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\dfu_req_handling\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\external\fprintf\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\external\segger_rtt\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\external\micro-ecc\micro-ecc\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\..\..\..\vendor\nRF5_SDK_14.0.0_3bcc1f7\external\nano-pb\ -I C:\800_bluetooth\dfu\bootloader_secure_ble\pca800BT\iar\..\config\ -Ohz

IAR ANSI C/C++ Compiler V8.40.1.212/W32 for ARM
Copyright 1999-2019 IAR Systems AB.
C:\800_bluetooth\vendor\nRF5_SDK_14.0.0_3bcc1f7\components\toolchain\cmsis\include\core_cm4.h(165) : Fatal Error[Pe035]: #error directive: "Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)"

Errors: 1
Warnings: none
Error while running C/C++ Compiler

RE: Developing for nRF52810 - the full story?

awneil — Sat, 18 Jul 2020 09:03:14 GMT

Link update for SDK 17.0.0 - It is now:

https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/nrf52810_user_guide.html?cp=7_1_5_0 - "Developing for nRF52810"

RE: Developing for nRF52810 - the full story?

awneil — Wed, 11 Sep 2019 10:48:27 GMT

And a heads-up that there is currently no Gazell library for devices without FPU (nRF52810 & 52811):

https://devzone.nordicsemi.com/f/nordic-q-a/44042/using-nrf52810-with-gzll_nrf52_arm-lib/172741#172741

https://devzone.nordicsemi.com/f/nordic-q-a/51992/struggling-to-link-the-gazell-library-for-the-nrf52811/209130#209130

RE: Developing for nRF52810 - the full story?

awneil — Thu, 06 Jun 2019 10:17:21 GMT

The link in the original post and its DocLib replacement no longer work!

Try this:

https://devzone.nordicsemi.com/f/nordic-q-a/48253/request-a-link-to-the-nrf52810-proting-guide/191295#191295

Although the OP link was broken, the navigation is still the same:

Software Development Kit > nRF5 SDK v15.3.0 > User Guides > Developing for nRF52810

RE: Developing for nRF52810 - the full story?

awneil — Tue, 19 Mar 2019 11:42:40 GMT

[quote userid="6462" url="~/f/nordic-q-a/33812/developing-for-nrf52810---the-full-story"]Are there any others?[/quote]

There are some hardware differences; eg, see: https://devzone.nordicsemi.com/f/nordic-q-a/45002/does-nrf52dk-emulation-of-nrf52810-support-non-fpu-environment/176916#176916

RE: Developing for nRF52810 - the full story?

awneil — Mon, 18 Feb 2019 10:39:19 GMT

Link for the new Doc Lib:

https://www.nordicsemi.com/DocLib/Content/SDK_Doc/nRF5_SDK/v15-2-0/nrf52810_user_guide

RE: Developing for nRF52810 - the full story?

slayer49 — Mon, 22 Oct 2018 20:59:12 GMT

I am still having troubles. I can build the ble_blinky app and run on nrf52810, but I am trying to convert the spi peripheral app for nrf52810 and stuck trying to compile. I made a new ticket for it here:

devzone.nordicsemi.com/.../problem-compiling-spi-example-for-nrf52810

RE: Developing for nRF52810 - the full story?

awneil — Mon, 22 Oct 2018 20:55:56 GMT

Thanks.

IIRC, I was using Keil at the time of the OP ...

RE: Developing for nRF52810 - the full story?

slayer49 — Mon, 22 Oct 2018 20:50:39 GMT

Segger Embedded Studio

RE: Developing for nRF52810 - the full story?

awneil — Mon, 22 Oct 2018 20:14:36 GMT

What IDE ?

RE: Developing for nRF52810 - the full story?

slayer49 — Mon, 22 Oct 2018 19:41:33 GMT

I had to change it both in project settings->code generation and project settings->preprocessor

RE: Developing for nRF52810 - the full story?

awneil — Mon, 22 Oct 2018 19:04:49 GMT

that's the 1st bullet point in the OP!

RE: Developing for nRF52810 - the full story?

slayer49 — Mon, 22 Oct 2018 18:58:12 GMT

In Code Generation, set ARM FP ABI TYPE to Soft

RE: Developing for nRF52810 - the full story?

awneil — Fri, 05 Oct 2018 12:06:04 GMT

[quote userid="2115" url="~/f/nordic-q-a/33812/developing-for-nrf52810---the-full-story/129920"]I'll report this internally[/quote]

It doesn't seem to have got through: https://devzone.nordicsemi.com/f/nordic-q-a/39209/error-compiler-generates-fpu-instructions-for-a-device-without-an-fpu-check-__fpu_present

RE: Developing for nRF52810 - the full story?

Håkon Alseth — Thu, 26 Apr 2018 11:05:31 GMT

Hi Andrew,

You are correct. the user guide does lacks the information about using softfp. I'll report this internally.

The things you list are essential to change in your project in order to make the firmware run.

The HEAP and STACK size shall be set by-default by your startup file (if using GCC atleast):

    .section .stack
#if defined(__STARTUP_CONFIG)
    .align __STARTUP_CONFIG_STACK_ALIGNEMENT
    .equ    Stack_Size, __STARTUP_CONFIG_STACK_SIZE
#elif defined(__STACK_SIZE)
    .align 3
    .equ    Stack_Size, __STACK_SIZE
#else
    .align 3
    .equ    Stack_Size, 2048
#endif
    .globl __StackTop
    .globl __StackLimit
__StackLimit:
    .space Stack_Size
    .size __StackLimit, . - __StackLimit
__StackTop:
    .size __StackTop, . - __StackTop

    .section .heap
    .align 3
#if defined(__STARTUP_CONFIG)
    .equ Heap_Size, __STARTUP_CONFIG_HEAP_SIZE
#elif defined(__HEAP_SIZE)
    .equ Heap_Size, __HEAP_SIZE
#else

Best regards,

Håkon