NFC and FOTA does not work

RE: NFC and FOTA does not work

Marelcom — Tue, 18 Feb 2025 15:49:55 GMT

Hi Abhijith

thanks a lot for your enhanced demo code.

Finaly i found the issue.
In the main loop the k_sleep was missing. In my demo I did not add a sleep into the mainloop.

	while (true) {
        k_sleep(K_MSEC(10));
	}

After adding k_sleep FOTA is working as expected. I guess bluetooth process did not get any run time while in main loop no sleep instruction is added.

Demo is running with default stack size.

Thanks a lot for your help

best regards
Markus

RE: NFC and FOTA does not work

Menon — Tue, 18 Feb 2025 10:00:36 GMT

Hello,

I tried initializing BLE first, then NFC, and it's working on my side. I have also changed a few config values, but I guess the issue is with the initialization. Please take a closer look and optimize the config values accordingly

devzone.nordicsemi.com/.../Case_5F00_339301.zip

Kind Regards,

Abhijith

RE: NFC and FOTA does not work

Marelcom — Fri, 14 Feb 2025 10:49:24 GMT

Hi Abhijith

I changed the stack size of those two setting, but stack overflow still does happens as soon as trying to read some infos from the nRF52832 over BLE. Wich values would you suggest for those two stack sizes?

#
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_NFC_T4T_NRFXLIB=y

CONFIG_NFC_NDEF=y
CONFIG_NFC_NDEF_MSG=y
CONFIG_NFC_NDEF_RECORD=y
CONFIG_NFC_NDEF_URI_REC=y
CONFIG_NFC_NDEF_URI_MSG=y

CONFIG_MPU_ALLOW_FLASH_WRITE=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_NVS=y
CONFIG_DK_LIBRARY=y


# Enable Bluetooth for FOTA (DFU)
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="NFC+DFU"

# Enable MCUboot and FOTA
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

#use LFRC instead of LFXO --> decrease start up time
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y


#stack size
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=8192

thanks and best regards
Markus

RE: NFC and FOTA does not work

Menon — Fri, 14 Feb 2025 10:30:30 GMT

Hello Markus,

From the shared log, I can see a stack overflow error. The GATT timeout error you are receiving from the mobile app indicates no response from the nRF52832 in time. I guess the stack overflow might be crashing the BLE thread, causing the timeout. Could you try increasing the stack size? See CONFIG_MAIN_STACK_SIZE, CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE

I haven't checked the sniffer logs. Please see if resolving the stack overflow resolves the issue you are seeing.

Kind Regards,

Abhijith

RE: NFC and FOTA does not work

Marelcom — Fri, 14 Feb 2025 09:52:19 GMT

Hi Susheel

Thanks for your replay. You right, something went wrong with the sniffer. No I get some log data. But DFU is still not working. Here is the sniffer log file: /cfs-file/__key/communityserver-discussions-components-files/4/NFC_2B00_DFU_5F00_sniffer-Log.pcapng

This is the serial log from the nRF52832

*** Booting nRF Connect SDK 3758bcbfa5cd ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0xc000
�*** Booting nRF Connect SDK 3758bcbfa5cd ***
Starting Bluetooth Peripheral LBS example
I: SoftDevice Controller build revision: 
I: 36 f0 e5 0e 87 68 48 fb |6....hH.
I: 02 fd 9f 82 cc 32 e5 7b |.....2.{
I: 91 b1 5c ed             |..\.    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
I: Identity: E4:1A:44:1A:4D:96 (random)
I: HCI: version 5.4 (0x0d) revision 0x118f, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x118f
Bluetooth initialized
Advertising successfully started
Starting Nordic NFC Writable NDEF Message example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe0
I: data wra: 0, 18
Found NDEF file record.
Starting NFC Writable NDEF Message example
E: ***** MPU FAULT *****
E:   Stacking error (context area might be not valid)
E:   Data Access Violation
E:   MMFAR Address: 0x200053b0
E: r0/a1:  0x8a66d18c  r1/a2:  0x1f979a1f  r2/a3:  0xd845493a
E: r3/a4:  0x568bc750 r12/ip:  0xe68cb61a r14/lr:  0xe5a48eef
E:  xpsr:  0xf0fa4a00
E: Faulting instruction address (r15/pc): 0x9cb8ce29
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x200019c0 (unknown)
*** Booting nRF Connect SDK 3758bcbfa5cd ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0xc000
�*** Booting nRF Connect SDK 3758bcbfa5cd ***
Starting Bluetooth Peripheral LBS example
I: SoftDevice Controller build revision: 
I: 36 f0 e5 0e 87 68 48 fb |6....hH.
I: 02 fd 9f 82 cc 32 e5 7b |.....2.{
I: 91 b1 5c ed             |..\.    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
I: Identity: E4:1A:44:1A:4D:96 (random)
I: HCI: version 5.4 (0x0d) revision 0x118f, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x118f
Bluetooth initialized
Advertising successfully started
Starting Nordic NFC Writable NDEF Message example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe0
I: data wra: 0, 18
Found NDEF file record.
Starting NFC Writable NDEF Message example

RE: NFC and FOTA does not work

Susheel Nuguru — Fri, 14 Feb 2025 09:11:28 GMT

Markus, I am really sorry for late response, We did not find anything useful in your sniffer trace as it seems like you are not seeing the sniffer by filtering. Also in your second picture we do not see any nearby devices advertising, so it seems like the sniffer is not working right in your second image? Is it possible that you flashed your firmware into sniffer instead of the DK?

You see some sort of timeout after enabling NFC, having some serial logs from the nRF52832 would have been helpful.

RE: NFC and FOTA does not work

Marelcom — Tue, 11 Feb 2025 14:54:44 GMT

can anybody help me to solve this issue, or let me know what I am doing wrong

thanks a lot and best regards
Markus

RE: NFC and FOTA does not work

Marelcom — Mon, 03 Feb 2025 13:52:22 GMT

Hi Hieu

sorry for my late replay, I hade to work on an other project.

Meanwhile I was able to run the BLE sniffer. Attached you will find two test project.
1. Hello World with DFU support (hello_world_dfu) --> DFU is running as expected
/cfs-file/__key/communityserver-discussions-components-files/4/6644.hello_5F00_world_5F00_dfu.zip

2. NFC witfh DFU support (writable_ndef_msg) --> DFU is not running.
/cfs-file/__key/communityserver-discussions-components-files/4/1882.writable_5F00_ndef_5F00_msg.zip

1. In Hello World with DFU project:
DFU is running and the BLE sniffer is able to see the BLE communcation between device and smartphone

/cfs-file/__key/communityserver-discussions-components-files/4/HelloWorld_5F00_ble_2D00_log.pcapng

2. NFC With DFU project:
There is no communication between device and smarphone. Sniffer sees no package. But in the Nordic "Device Manager" App on the smartphone BLE device is visible. When trying to get some infos form device over BLE then a "GATT CONN TIMEOUT" error pops up.

Please help to solve this issiue

Thanks a lot and best regards
Markus

RE: NFC and FOTA does not work

Hieu — Fri, 24 Jan 2025 15:14:19 GMT

Hi Marelcom,

Susheel is out of office, and I am filling in for him.

The attached file unfortunately cannot be downloaded. Perhaps something broke.

If you have difficulty running the sniffer, you can refer to this online lesson: Lesson 6 - Bluetooth LE sniffer - Nordic Developer Academy.

On the other hand, I find it very strange that the NFC functionality interfere with BLE at all. Does the BLE + DFU setup work at all without the NFC feature?

Hieu

RE: NFC and FOTA does not work

Marelcom — Tue, 21 Jan 2025 13:50:46 GMT

I will try to setup the air sniffer. But I have some problems to run the sniffer.

Meanwhile have tried to run the code which is attached in the first post?

RE: NFC and FOTA does not work

Susheel Nuguru — Tue, 21 Jan 2025 12:41:37 GMT

Can you please provide me with the Air sniffer log of the connection and disconnection, so that I have more context to share and analyze?

RE: NFC and FOTA does not work

Marelcom — Tue, 21 Jan 2025 12:28:22 GMT

adding this configs does not fix the problem. I stille receive the "GATT CONN TIMEOUT" error, whil trying to upload a firmware with the "Device Manager" App

CONFIG_FLASH_MAP=y
CONFIG_STREAM_FLASH=y

My prj.conf files looks like this:

#
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_NFC_T4T_NRFXLIB=y

CONFIG_NFC_NDEF=y
CONFIG_NFC_NDEF_MSG=y
CONFIG_NFC_NDEF_RECORD=y
CONFIG_NFC_NDEF_URI_REC=y
CONFIG_NFC_NDEF_URI_MSG=y

CONFIG_MPU_ALLOW_FLASH_WRITE=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_STREAM_FLASH=y
CONFIG_NVS=y
CONFIG_DK_LIBRARY=y


# Enable Bluetooth for FOTA (DFU)
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="TestDevice"

# Enable MCUboot and FOTA
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

#use LFRC instead of LFXO --> decrease start up time
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

As mentioned bevor. When using the code of the FOTA lesson, then FOTA is running correct. But when combining the FOTA Code with the NFC sample project, then FOTA does not run anymore.

Yes please ask the author. Thanks a lot

RE: NFC and FOTA does not work

Susheel Nuguru — Tue, 21 Jan 2025 12:05:40 GMT

I am not an expert in this but looking into other forums it seems like there could be some configs missing in your prj.conf

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

# you did not mention below but seems like this is needed
CONFIG_FLASH_MAP=y
CONFIG_STREAM_FLASH=y

If this did not work, then I can try asking the author of the lesson to give some guidance.