RE: about wakeup on 5340-DK

Einar Thorsrud — Mon, 18 Dec 2023 11:43:06 GMT

Yes, there could be an issue with your power supply (if that is the reason for the reset). It could be worth logging (and clearing as it is cummulative) the RESETREAS every boot to verify if that is the reason or not, though.

RE: about wakeup on 5340-DK

yoyou — Sat, 16 Dec 2023 05:52:41 GMT

Hi,

I have carefully investigated, only DK no problem,

now DK+21540 model, 21540 power from 5340 VDD, when open the power for 21540 will get a reset..

maybe need increase capacitance 10uF,

thanks

Best regards

RE: about wakeup on 5340-DK

Einar Thorsrud — Fri, 15 Dec 2023 14:58:38 GMT

Hi,

[quote user="yuyou"]it show two start, why?[/quote]

I assume you write "two start" in the beginning of your application? If so, this indicate you got a reset for some reason. Was that not intentional?

RE: about wakeup on 5340-DK

yoyou — Fri, 15 Dec 2023 02:01:37 GMT

Hi,

thanks for reply

i found a preblem.

DK wakeup take 2s, but sleep large then 5min,

wakeup will take 4s, see log as follow:

I: 3 Sectors of 4096 bytes
I: alloc wra: 0, fc8
I: data wra: 0, 2c
started demo....
I: 3 Sectors of 4096 bytes
I: alloc wra: 0, fc8
I: data wra: 0, 2c
started demo....
check data ok

it show two start, why?

the prj.conf

# # Clock Source, internal crystal oscillator
# CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
# CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n
# CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
# RF parameters
CONFIG_SOC_HFXO_CAP_INTERNAL=y
CONFIG_SOC_HFXO_CAP_INT_VALUE_X2=24
CONFIG_BUILD_WITH_TFM=y



# General
CONFIG_DEBUG=n
CONFIG_ASSERT=n # can't do in irq
CONFIG_STACK_USAGE=n
CONFIG_THREAD_MONITOR=n


CONFIG_RELEASE_SNPN=y
CONFIG_RELEASE_AUDIO_DATA_ENCCRYPT=y

CONFIG_I2S=y
CONFIG_NRFX_I2S=y


CONFIG_BT=y
CONFIG_BT_OBSERVER=y  # only sync need
CONFIG_BT_BROADCASTER=n
CONFIG_BT_EXT_ADV=y
CONFIG_BT_PER_ADV_SYNC=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_DEVICE_NAME="headphone"
CONFIG_BT_DEVICE_NAME_DYNAMIC=n


CONFIG_NEWLIB_LIBC=y
# CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_NRF_APPROTECT_LOCK=y
CONFIG_NRF_SECURE_APPROTECT_LOCK=y


CONFIG_THREAD_NAME=y
CONFIG_ISR_STACK_SIZE=8192
CONFIG_HEAP_MEM_POOL_SIZE=28192
CONFIG_MAIN_STACK_SIZE=18192
# CONFIG_PRIVILEGED_STACK_SIZE=8192

# CONFIG_STACK_SENTINEL=y # go to self fun stack_overflow()

CONFIG_GPIO=y
# CONFIG_GPIO_NRFX=y

# CONFIG_BT_LL_SW_SPLIT=y
# CONFIG_BT_USER_PHY_UPDATE=y


# ----------------------------------------------
# Allow for large Bluetooth data packets.
# Increase maximum data length of PDU supported in the Controller
CONFIG_BT_L2CAP_TX_MTU=252
CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=244
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251
CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_BUF_ACL_RX_SIZE=502

# -------------------Log---------------------------
CONFIG_LOG=n
CONFIG_LOG_MODE_MINIMAL=n
# Make sure printk is printing to the UART console (default y=1)
CONFIG_CONSOLE=n
CONFIG_UART_CONSOLE=n
CONFIG_PRINTK=n
CONFIG_RELEASE_NIN_LOG=n


CONFIG_STDOUT_CONSOLE=n
CONFIG_BOOT_BANNER=n

# enable the serial driver (UART driver)
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y

CONFIG_USE_SEGGER_RTT=n
CONFIG_LOG_BACKEND_RTT=n
CONFIG_I2S_LOG_LEVEL_DBG=y
CONFIG_I2S_LOG_LEVEL_INF=y
CONFIG_SPI_LOG_LEVEL_DBG=y
CONFIG_SPI_LOG_LEVEL_INF=y

# ----------------------------------------------
CONFIG_WDT_LOG_LEVEL_DBG=y
CONFIG_WATCHDOG=y
CONFIG_WDT_DISABLE_AT_BOOT=y

# ----------------------------------------------
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_NVS=y
CONFIG_NVS_LOG_LEVEL_DBG=n
CONFIG_REBOOT=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y

# ----------------------------------------------
CONFIG_PM=y
CONFIG_PM_DEVICE=y
# CONFIG_IS_SPM=y
# CONFIG_FW_INFO=y

# ----------------------------------------------
#use P0.09 and P0.10 as gpio
CONFIG_NFCT_PINS_AS_GPIOS=y

# CONFIG_NFC_NDEF=y
# CONFIG_NFC_NDEF_MSG=y
# CONFIG_NFC_NDEF_RECORD=y
# CONFIG_NFC_NDEF_TEXT_RECORD=y

# ----------------------------------------------
CONFIG_ADC=y
CONFIG_ADC_ASYNC=y
CONFIG_ADC_NRFX_SAADC=y
# CONFIG_ADC_CONFIGURABLE_INPUTS=y


# ----------------for_set------------------------------
# Enable the NUS service
CONFIG_BT_NUS=y
CONFIG_BT_DEVICE_APPEARANCE=833

# Enable bonding
CONFIG_BT_SETTINGS=n
CONFIG_SETTINGS=n

CONFIG_BT_NUS_SECURITY_ENABLED=n


# --------------------------------------DFU  OTA----------------------------------------
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
# CONFIG_BT_DEVICE_NAME="Earphone_Update"


# Enable mcumgr.
CONFIG_MCUMGR=y
# Enable the Bluetooth (unauthenticated) and shell mcumgr transports.
CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n

# Enable most core commands.
CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_CMD_OS_MGMT=y

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y     # no this y, maybe will 'PM_MCUBOOT_PRIMARY_ID' undeclared
# CONFIG_SECURE_BOOT=y
# CONFIG_BUILD_S1_VARIANT=y
# ECDSA     python3 bootlooader/mcuboot/scripts/imgtool.py keygen -t ecdsa-p256 -k priv.pem
# RSA-2048  python3 bootlooader/mcuboot/scripts/imgtool.py keygen -t rsa-2048 -k priv.pem


# Allow for large Bluetooth data packets.
CONFIG_BT_L2CAP_TX_MTU=252
CONFIG_BT_BUF_ACL_RX_SIZE=502

# Some command handlers require a large stack.
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

CONFIG_BT_PERIPHERAL_PREF_TIMEOUT=800
CONFIG_BT_CONN_PARAM_UPDATE_TIMEOUT=5000

Best regards

RE: about wakeup on 5340-DK

Einar Thorsrud — Mon, 04 Dec 2023 08:22:57 GMT

I see. So P0.26 is you wakeup pin (form system off), I assume. With startup-time we normally mean the time between the reset until code is executed. However, here you are measuring the time until some high-level activity happens. And a lot of things will happen before that, both things handled by Zephyr (including waiting for the LFCLK to start which can take several hundred milliseconds if you are using an LFXO), and other tasks.

I suggest you start toggling pins at strategic locations in your code and measure with a logic analyzer to try to narrow down which parts or your application (and enabled features handles by Zephyr) that consumes the most time during startup.

RE: about wakeup on 5340-DK

yoyou — Mon, 04 Dec 2023 00:13:11 GMT

thanks for reply

How do you measure the wakeup time?

start timer when press button P0.26. and end timer when see de first log in Serialport..

RE: about wakeup on 5340-DK

Einar Thorsrud — Fri, 01 Dec 2023 15:32:53 GMT

Hi,

How do you measure the wakeup time?

[quote user=""]means: tow 5340-DK, one goto sleep, another wake up it wirelessly.[/quote]

No, that would mean that the radio would have to be in Rx all the time, and that would consume a lot of power and not constitute "sleeping".