This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF5340 FOTA, system reset after pairing

Hi,

I am trying to evaluate nRF5340 FOTA update via Bluetooth.  I started with the Bluetooth/peripheral code sample as the basis for my project.  I modified the project per notes found in a previous DevZone post nRF5340 FOTA upgrade over Bluetooth and Working with nRF5340 notes for the nRF SDK v1.4.0.

The application will boot and advertise on bluetooth.  The bootloader appears to operate correctly as it will boot to a new image if I write an app_moved_test_update.hex file to the nRF5340 using the nrfjprog tool.

When I try to connect to the nRF5340 using Device Manager on an Android 8.1 phone, the nRF5340 will crash and reset after pairing.  The following is data captured from the serial port of the nRF5340 showing system boot, pairing passkey, error codes and subsequent reboot.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
*** Booting Zephyr OS build v2.4.0-ncs1 ***
[00:00:00.256,317] <inf> mcuboot: Starting bootloader
[00:00:00.262,451] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, cop
y_done=0x3, image_ok=0x3
[00:00:00.272,430] <inf> mcuboot: Boot source: none
[00:00:00.277,862] <inf> mcuboot: Swap type: none
[00:00:00.473,754] <inf> mcuboot: Bootloader chainload address offset: 0xc000
[00:00:00.481,384] <inf> mcuboot: Jumping to the first image slot
*** Booting Zephyr OS build v2.4.0-ncs1 ***
LED0 GPIO initialized
[00:00:00.009,826] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.009,857] <inf> fs_nvs: alloc wra: 0, f88
[00:00:00.009,857] <inf> fs_nvs: data wra: 0, a8
[00:00:00.024,688] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.024,688] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.024Completed : bt_enable()
Bluetooth initialized
,688] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version
207.3932Advertising successfully started
Completed : bt_ready()
Completed : bt_conn_cb_register()
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

On each boot there is a warning for ECC HCI commands not available and a message of No ID address.  App must call settings_load  ( see lines 28 & 29 ).  Do either of these indicate a condition that could lead to the fault?  What needs to be done to eliminate those messages on boot?

Have you seen this type of fault before?

Do you have a complete known good nRF5340 FOTA project that has been tested with Device Manager on Android 8 that I could use as a comparison?

Thank you for your help.

Doug Young