Sample - "Bluetooth: Central NFC pairing" - Start-up errors - only on this sample

I've been tinkering with my Dev Kits (3 @ nrf52840-dk and 1 @ nrf5340-dk) as I try to find the right software/hardware architecture for my use case.

I made a lot of progress starting with just how to use the NRF Connect SDK, building samples, the differences between Thread and Mesh, etc etc.  Including how to monitor the Zephyr output o the serial ports.  It has been a good week.

One problem I am having now has me stumped.

When building  the Central NFC Pairing sample and flashing it onto my nrf52840-dk then watching my serial output, I see the following:

*** Booting Zephyr OS build v2.7.0-ncs1  ***
Starting NFC Central Pairing example
I: 8 Sectors of 4096 bytes
I: alloc wra: 1, ba8
I: data wra: 1, 750
I: SoftDevice Controller build revision:
I: df c0 4e d6 1f 7c 66 09 |..N..|f.
I: 0a f5 2b a0 98 f2 43 64 |..+...Cd
I: 62 c5 a6 2a             |b..*
I: No ID address. App must call settings_load()
Bluetooth initialized
Generating new pairing keys.
E: Voltage measure failed
E: st25r3911b initialization failed
NFCA initialization failed err: -6.
NFC Poller initialization error: -6

I do not see the No ID or Voltage errors when using any of the other samples.  Can you think of any prj.conf settings that might be causing this?

For example I see this on my Thread COAP Client

uart:~$ *** Booting Zephyr OS build v2.7.0-ncs1  ***
[00:00:00.133,544] <inf> net_l2_openthread: OpenThread version: OPENTHREAD/69eb7030c; Zephyr; Feb 11 2022 10:01:06
[00:00:00.135,284] <inf> net_l2_openthread: Network name: ot_zephyr
[00:00:00.230,407] <inf> net_l2_openthread: State changed! Flags: 0x0100103d Current role: 1
[00:00:00.341,003] <inf> net_l2_openthread: State changed! Flags: 0x00001084 Current role: 3
[00:00:00.376,892] <inf> net_l2_openthread: State changed! Flags: 0x00000200 Current role: 3
uart:~$

Related