Zephyr API to read the nRF5340 die temperature

[Learner]

Hello,

I am looking for some some nRF5340 example code that reads the nRF5340 die temperature using zephyr APIs.

I've looked at previous posts but I could only find this one https://devzone.nordicsemi.com/f/nordic-q-a/56171/how-to-get-die-temperature-on-nrf52832-using-zephyr from 10 months ago that stated none existed. I am hoping someone, somewhere musty have done something similar.

Thank you.

Kind regards

[Håkon Alseth]

Hi,

 

The temp peripheral is only accessible on the network core:

https://infocenter.nordicsemi.com/topic/ps_nrf5340/temp.html?cp=3_0_0_6_33

So we need to configure the board nrf5340pdk_nrf5340_cpunet, but since the network core is started from the app cpu, you first need to have something on the app core running with this config set:

CONFIG_BOARD_ENABLE_CPUNET=y

 

I used sample/nrf5340/empty_app_core.

 

For uart output from the network core, connect P0.25 to P0.20.

If you also need UART RXD, connect P0.26 to P0.22.

 

Here's an example that shows how to use the NRF_TEMP peripheral: 

0677.nrf_temp_sample.zip

 

Kind regards,

Håkon

[Learner]

Hi Hakon,

I have built and run the project that reads the die temperature. I can see the see the temperature values going up and down as I heat and cool the device. However, I am still not clear how to read these values from the network core into my application. 

Please advise.

Kind regards

Mohamed

[Håkon Alseth]

Hi,

 

Here's a small example on how to share data between the two cores.

Note that I setup the network core to use RTT for printing, and the app core uses uart.

share_temp_data_nrf5340.zip

 

The above example uses linker sections to share the RAM mapped shared address space, and it is provided as-is.

You can have a look at these samples, if you need to share data between the cores as a part of a larger scheme:

https://github.com/nrfconnect/sdk-nrf/tree/master/samples/nrf_rpc/entropy_nrf53

https://github.com/nrfconnect/sdk-zephyr/tree/master/samples/bluetooth/hci_rpmsg

 

Kind regards,

Håkon

[Learner]

Thank you Hakon.

I have just seen your reply. I have been checking my inbox for a notification email from DevZone informing me you've updated my ticket. However, for some reason I did not get a notification despite the fact Notifications are enabled.

Anyway, I will have a look at your example and let you know how I got on.

Kind regards

Mohamed

[Håkon Alseth]

Hi Mohamed,

 

Learner said:

I have just seen your reply. I have been checking my inbox for a notification email from DevZone informing me you've updated my ticket. However, for some reason I did not get a notification despite the fact Notifications are enabled.

Could you check if the notification is ticked under "settings -> notifications"? Specifically this one?

 

Learner said:

Anyway, I will have a look at your example and let you know how I got on.

as mentioned, it is a very simplistic example, which statically declares a region of RAM, and the network core essentially writes into this RAM address based on when the IPC event occurs. It does not have much error handling wrt. synchronizing.

 

Kind regards

Håkon

[Learner]

Hi Hakon,

Yes, every item is ticked. I did receive notifications in the past, the last one back in January 19 2021. I also received two more on Feb 16 2021 after a password reset request.

Kind regards

Mohamed

[Håkon Alseth]

Hi Mohamed,

 

My apologies for this. Im currently checking with the site administrators to see if we can figure this out.

 

Kind regards,

Håkon

[Learner]

Hi Hakon,

I have received a notification about your previous reply. Have you made any changes on your side? Anyway, Notifications are working now.

I still have not had a chance to try your proposed die temperature solution. While waiting for your response I started another task and I need to complete it before I can go back to the die temperature. I will probably look at it sometimes tomorrow.

Kind regards

Mohamed

[Håkon Alseth]

Hi Mohamed,

 

Learner said:

I have received a notification about your previous reply. Have you made any changes on your side? Anyway, Notifications are working now.

I am glad to hear that the notifications are now working!

 

Learner said:

I still have not had a chance to try your proposed die temperature solution. While waiting for your response I started another task and I need to complete it before I can go back to the die temperature. I will probably look at it sometimes tomorrow.

No worries. If you run into any issues, please let us know.

 

Cheers,

Håkon 

[Learner]

Hi Hakon,

I have implemented the changes in my project as per your example but I am unable to load my project in SES. Below in blue is the error I am getting. Note, I am using SES v5.34a and NCS v1.5.0-rc1.

--------------------------------------------------------------------------------------------------------------------

My CMakeLists.txt file looks like this,

#
# Copyright (c) 2020 Nordic Semiconductor
#
# SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
#

cmake_minimum_required(VERSION 3.8.2)

set(NRF_SUPPORTED_BOARDS
nrf5340pdk_nrf5340_cpuapp
)

find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(empty_app_core)

FILE(GLOB app_sources src/*.c src/radio/*.c src/lr1110_driver-master/*.c src/crypto/*.c src/adc/*.c src/timer/*.c src/mcu_temp/*.c)
#FILE(GLOB app_sources src/radio/*.c)
target_sources(app PRIVATE ${app_sources})
#target_sources(app PRIVATE src/radio/*.c)
#arget_sources(app PRIVATE src/*.c)
#target_sources(app PRIVATE src/lr1110_driver-master/lr1110_driver_version.c)

--------------------------------------------------------------------------------------------------------------------

My project file prj.conf looks like this,

#
# Copyright (c) 2020 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-BSD-5-Clause-Nordic
#

### Logging ####
# For the PID 4 hardware we must set CONFIG_SERIAL=n because otherwise the SPI CS/BUSY
# pins will be allocated to UART0 CTS/RTS pins.
CONFIG_SERIAL=n
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
#CONFIG_UART_CONSOLE=n
CONFIG_DEBUG_OPTIMIZATIONS=y

CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_PRINTK=y

# This will be needed when using to NCS v1.40 or higher, #ifdef ZEPHYR_V_1_50
CONFIG_DEPRECATED_ZEPHYR_INT_TYPES=y

### NETWORK core ###
# needed when measuring the SoC die temperature
#CONFIG_BOARD_ENABLE_CPUNET=n

### GPIOs ###
CONFIG_GPIO=y

# ADC
CONFIG_ADC=y
# No need for this as it is alresdy enabled by default in ...\adc\Kconfig.nrfx
#CONFIG_ADC_NRF5_SAADC = y

### SPI ###
CONFIG_SPI=y
#CONFIG_SPI_ASYNC=y
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_SPI_1=y

### TEMPERATURE SENSOR ###
#CONFIG_BOARD_ENABLE_CPUNET=y
#CONFIG_SENSOR=y
#CONFIG_TEMP_NRF5=y
### IPC stuff ###
CONFIG_IPM=y
CONFIG_IPM_NRFX=y
CONFIG_IPM_MSG_CH_0_ENABLE=y
CONFIG_IPM_MSG_CH_0_TX=y
CONFIG_IPM_MSG_CH_1_ENABLE=y
CONFIG_IPM_MSG_CH_1_RX=y
# CONFIG_NRF_RPC=y

### I2C ###
#CONFIG_LIS2DE12=y
#CONFIG_I2C_1=y

### RTC ###
# The RTC on nRF5340 is not really an Real Time Clock but it's a real time counter.
# Timers will be used instead.
#CONFIG_COUNTER_NRFX_RTC0=y

### RANDOM NUMBER GENERATION ###
CONFIG_TIMER_RANDOM_GENERATOR=n
CONFIG_ENTROPY_DEVICE_RANDOM_GENERATOR=n
CONFIG_XOROSHIRO_RANDOM_GENERATOR=n
# Cryptographically secure random number generators
CONFIG_HARDWARE_DEVICE_CS_GENERATOR=n
CONFIG_CTR_DRBG_CSPRNG_GENERATOR=n
#CONFIG_CS_CTR_DRBG_PERSONALIZATION=n

--------------------------------------------------------------------------------------------------------------------

while my overlay file nrf5340pdk_nrf5340_cpunet.overlay looks like this,

// SEGGER Embedded Studio auto generated

/// {
// chosen {
/*
* In some default configurations within the nRF Connect SDK,
* e.g. on nRF52840 and nRF9160, the chosen zephyr,entropy node
* is &cryptocell. This devicetree overlay ensures that default
* is overridden wherever it is set, as this application uses
* the RNG node for entropy exclusively.
*/
// zephyr,entropy = &rng;
// };
//};

&temp {
compatible = "nordic,nrf-temp";
status = "okay";
};

//&led0 { gpios = < &gpio1 9 GPIO_ACTIVE_LOW >; };

// nRF5340PDK board
//&spi1 {
// cs-gpios = <&gpio1 9 0>;
//
// compatible = "nordic,nrf-spim";
// status = "okay";
// sck-pin = < 47 >;
// mosi-pin = < 45 >;
// miso-pin = < 46 >;
//};

// PID-4 board
&spi1 {
cs-gpios = <&gpio0 19 0>;

compatible = "nordic,nrf-spim";
status = "okay";
sck-pin = < 13 >;
mosi-pin = < 9 >;
miso-pin = < 40 >;
};

/ {
aliases {
//Didn't work with alias spi-1=&spi1 as defined in dts\...\nrf5340_cpuapp.dtsi and build\zephyr.dts;
spi1 = &spi1;
};
};

--------------------------------------------------------------------------------------------------------------------

Creating solution spi_test_LR1110-2-TX-RX-CMAC-AES.emProject

C:/Zypher/v1.5.0-rc1/toolchain/opt/bin/cmake.exe -GNinja -DBOARD=nrf5340pdk_nrf5340_cpuapp -DBOARD_DIR=C:\Zypher\v1.5.0-rc1\zephyr\boards\arm\nrf5340dk_nrf5340 -BC:\Dev\PID-4\spi_test_LR1110-2-TX-RX-CMAC-AES\build_nrf5340pdk_nrf5340_cpu_net -SC:\Dev\PID-4\spi_test_LR1110-2-TX-RX-CMAC-AES -DNCS_TOOLCHAIN_VERSION=1.5.0 -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:\Zypher\v1.5.0-rc1\toolchain\segger_embedded_studio/html/configure_nordic_project_menuconfig.py
-- Application: C:/Dev/PID-4/spi_test_LR1110-2-TX-RX-CMAC-AES
-- Zephyr version: 2.4.99 (C:/Zypher/v1.5.0-rc1/zephyr)
-- Found Python3: C:/Zypher/v1.5.0-rc1/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Found west (found suitable version "0.9.0", minimum required is "0.7.1")
-- Board: nrf5340pdk_nrf5340_cpuapp
-- Cache files will be written to: C:/Zypher/v1.5.0-rc1/zephyr/.cache
-- Found dtc: C:/Zypher/v1.5.0-rc1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Zypher/v1.5.0-rc1/toolchain/opt)
-- Found BOARD.dts: C:/Zypher/v1.5.0-rc1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340pdk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/Dev/PID-4/spi_test_LR1110-2-TX-RX-CMAC-AES/build_nrf5340pdk_nrf5340_cpu_net/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Dev/PID-4/spi_test_LR1110-2-TX-RX-CMAC-AES/build_nrf5340pdk_nrf5340_cpu_net/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Dev/PID-4/spi_test_LR1110-2-TX-RX-CMAC-AES/build_nrf5340pdk_nrf5340_cpu_net/zephyr/include/generated/device_extern.h
Parsing C:/Zypher/v1.5.0-rc1/zephyr/Kconfig
Loaded configuration 'C:/Zypher/v1.5.0-rc1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340pdk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/Dev/PID-4/spi_test_LR1110-2-TX-RX-CMAC-AES/prj.conf'
Configuration saved to 'C:/Dev/PID-4/spi_test_LR1110-2-TX-RX-CMAC-AES/build_nrf5340pdk_nrf5340_cpu_net/zephyr/.config'
Kconfig header saved to 'C:/Dev/PID-4/spi_test_LR1110-2-TX-RX-CMAC-AES/build_nrf5340pdk_nrf5340_cpu_net/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/Zypher/v1.5.0-rc1/toolchain/opt/bin/arm-none-eabi-gcc.exe
-- Configuring done
Including boilerplate (Zephyr base): C:/Zypher/v1.5.0-rc1/zephyr/cmake/app/boilerplate.cmake
-- Using NCS Toolchain 1.5.0 for building. (C:/Zypher/v1.5.0-rc1/toolchain/cmake)

warning: UART_CONSOLE (defined at drivers/console/Kconfig:47) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: SERIAL (=n), SERIAL_HAS_DRIVER (=n). See
docs.zephyrproject.org/.../CONFIG_UART_CONSOLE.html and/or look up
UART_CONSOLE in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

CMake Warning at C:/Zypher/v1.5.0-rc1/zephyr/CMakeLists.txt:1354 (message):

WARNING: The board 'nrf5340pdk_nrf5340_cpuapp' is deprecated and will be
removed in version v2.6.0

CMake Error at C:/Zypher/v1.5.0-rc1/zephyr/cmake/extensions.cmake:416 (add_library):
No SOURCES given to target: drivers__spi
Call Stack (most recent call first):
C:/Zypher/v1.5.0-rc1/zephyr/cmake/extensions.cmake:393 (zephyr_library_named)
C:/Zypher/v1.5.0-rc1/zephyr/drivers/spi/CMakeLists.txt:3 (zephyr_library)

CMake Generate step failed. Build files cannot be regenerated correctly.

error: cmake failed
create_nordic_project.py failed (1)

Kind regards

Mohamed