The nRF52805 SoC is a low-cost member of the nRF52 Series with a subset of the features of the nRF52811 and nRF52810 SoCs. As the nRF52805 has a feature subset of the nRF52810/11 SoCs, which in turn has a feature subset of the nRF52832, you can use the nRF52832 on the nRF52 DK to emulate the functionality of nRF52805 during development.
This blog post will show you how to emulate the nRF52805 on the nRF52 Development Kit and show you how to transfer the emulated project to nRF52805 hardware.
Detailed information on the SoC can be found in the nRF52805 Product Specification and a detailed comparison of the features of the various nRF52 Series chips can be seen in the nRF52 Series comparison table on the Nordic Infocenter.
To support development for the nRF52805 the following versions are required.
Hardware emulation of nRF52805 on the nRF52 DK
You can fully emulate nRF52805 features using an nRF52 Development Kit (PCA10040), there are however, some differences that developers should be aware of when transferring emulated projects to nRF52805 hardware.
The EasyDMAbit MAXCNT bit length for some of the digital serial interfaces differs between the nRF52832 and the nRF52805. This means that the emulated project running on the nRF52 832 may only be able to use an EasyDMA MAXCNT bit length of 8 bits, while on the nRF52805 you may use EasyDMA MAXCNT bit length of up to 14 bits, see the table below for which peripherals that are affected.
The SAADC on the nRF52805 only has a limited number of channels compared to the nRF52832
The number of PPI channels on the nRF52805 is lower than on the nRF52832
The number of GPIOs available on the nRF52805 is lower than the nRF52805.
When running an emulated nRF52805 example on the nRF52 DK you will be able to use the buttons and LEDs, but when transferring the emulated project to nRF52805 hardware you will need to remap the GPIOs used on the nRF52832 to available GPIOs on the nRF52805 wlCSP package, see table below.
General purpose I/O
Connection for 32.768 kHz crystal (LFXO)
Configurable as pin reset
Software emulation of nRF52805
All examples that are hardware compatible with the nRF52805 can be set up to emulate the nRF52805 on the nRF52832. Hardware compatibility means that a project uses only the resources present in nRF52805, including peripherals and memory. Note that the nRF52805 does not have cache and hardware floating-point support. It is also important to note that the nRF52805 has reduced flash and RAM size compared to the nRF52832, hence not all nRF52 DK examples may fit on the nRF52805.
See the nRF52 Series comparison table on the Nordic Infocenter for a full overview of which peripherals that are present on the nRF52805 compared to the nRF52832.
The following SoftDevices are supported on the nRF52805
this is also listed in the SDKs and SoftDevices Compatibility Matrix for the nRF52805.
Patching nRF5 SDK v17.0.0 to support the nRF52805
The following files in the nRF5 SDK v17.0.0 need to be patched or added to support the nRF52805:
The patched and added files are available in this zip: SDK_v17.0.0_nRF52805_Patch.zip
Creating an emulated project for the nRF52805 on the nRF52 DK
This section will show you how to convert the emulated nRF52810 (pca10040e) examples in the nRF5 SDK to emulated nRF52805 (pca10040e_nrf52805) examples. Instructions for Keil, Segger Embedded Studio, and GCC with Makefiles are given below.
Segger Embedded Studio
GCC and Makefiles
DNRFX_COREDEP_DELAY_US_LOOP_CYCLES=7ASMFLAGS += -DNRFX_COREDEP_DELAY_US_LOOP_CYCLES=7
Transferring an emulated project to nRF52805 hardware
If you have developed your application using the emulated project as a starting point, there are only two steps you need to perform before you can run it natively on nRF52805:
Emulated nRF52805 (pca10040e_nrf52805) Project examples
Below you will find some of the BLE examples from SDK v17.0.0 where a pca10040e_nrf52805 project has been added with support for Keil 5, Segger Embedded Studio.
Peripheral UART/Serial Port Emulation over BLE (ble_app_uart)
Secure BLE Bootloader
Secure UART Bootloader
The __RAM1_segment_end__ error can be resolved by following the instructions here: https://devzone.nordicsemi.com/f/nordic-q-a/66297/linker-error-when-upgrading-to-sdk-17-0-from-15-2/271251#271251 Here is…
All the above would be useful if they worked under sdk17.0.2.!!!!I I have NOT managed to get ANY of the 4 above examples, or the mods described above this, to lead to code that can be successfully built…
Same issue as below for SES, it says to remove files, they are not in the project, then add firles, where are the files, I cannot locate them. There was no answer below, is someone at Nordic looking at this?
I develop with NRF52840DK; Segger 5.42a; sdk 17.0.2; sdk for mesh 5.0.0.
My memory segment: FLASH RX 0x0 0x100000;RAM1 RWX 0x20000000 0x40000;mbr_params_page RX 0x000FE000 0x1000;bootloader_settings_page RX 0x000FF000 0x1000;uicr_bootloader_start_address RX 0x10001014 0x4;uicr_mbr_params_page RX 0x10001018 0x4My segment macros:
I have a problem: I integrating Scure bootloader dfu into example Light_Switch mesh and my problem is there. I can't fix it, please help me, thanks!!!
I followed this guide and it worked for the blinky example, but its just a simple GPIO example, when I try to compile other examples like ADC or UART it throws an error. Do you have some tips to begin develop with the nRF52805 and its basic peripherals?