sdk-nrf/samples/cellular/nrf_provisioning: undefined symbol NRF_PROVISIONING_RX_BUF_SZ

[harry4951]

Hi, I am trying to claim and provisioning the SparkFun Thing Plus - nRF9160 device.

My reference is this: https://github.com/nRFCloud/utils/blob/master/python/modem-firmware-1.3%2B/README.md#claim-and-provision-

The SDK is nrf connect sdk 2.4.2, on Windows 10, using VSCode, building for sparkfun_thing_plus_nrf9160_ns.

Even if I switch to build nrf9160dk_nrf9160_ns, errors still exist.

What I did was: create a new application -> nrf_provisioning -> add following config into the prj.conf -> build the board -> get the errors

CONFIG_AT_SHELL=y
CONFIG_NRF_PROVISIONING_RX_BUF_SZ=2048
CONFIG_SHELL_BACKEND_SERIAL_RX_RING_BUFFER_SIZE=2048
CONFIG_SHELL_CMD_BUFF_SIZE=2048

warning: attempt to assign the value '2048' to the undefined symbol NRF_PROVISIONING_RX_BUF_SZ

error: Aborting due to Kconfig warnings

Can you replicate the errors from your side? How can we solve it?

Thanks

/CJ

[Øyvind]

Hello CJ,

I am able to reproduce. The documentation seems to be written for latest version of nRF Connect SDK, also known as the main tag, and not for nRF Connect SDK v2.4.2. I've forwarded to our cloud team responsible for this script.

As you are using nRF Connect v2.4.2, the file path will be different than the main tag. 

nrf/samples/nrf9160/nrf_provisioning

versus

nrf/samples/cellular/nrf_provisioning

Kind regards,
Øyvind

[harry4951]

Hi,

I am now using nrf/samples/nrf9160/nrf_provisioning

1.If I dont do anything extra, just build and flash. And then run the python code from the ref link in the original post.
I got stuck at get response from AT.


2.If I directly access the UART and manully type the command "at AT+CFUN=4"
Command not found:


3.If I add the following part into prj.conf, the same error as before: undefined symbol NRF_PROVISIONING_RX_BUF_SZ

CONFIG_AT_SHELL=y
CONFIG_NRF_PROVISIONING_RX_BUF_SZ=2048
CONFIG_SHELL_BACKEND_SERIAL_RX_RING_BUFFER_SIZE=2048
CONFIG_SHELL_CMD_BUFF_SIZE=2048

4.If I only comment the NRF_PROVISIONING_RX_BUF_SZ but keep the rest in #3, then build and flash, I got the same result as #1

5.If I directly access the UART and manully type the command "at AT+CFUN=4"
There is a response:


For the python code I am using:
1.create_ca_cert.py
2.claim_and_provision_device.py

Can you/team behind it provide me a feasiable solution ASAP, we are in a hurry to make the system run but get stuck at provisioning? 
In other words, how can we make the data be able to send to nrf cloud using custom PCB with unprovisioned nrf9160?
Step1...Step2....Step3...and every steps should work as you describe it.
Now I am using sparfun nrf9160 as the board to try out while waiting for our PCB to be produced.

Thanks
/CJ

[Øyvind]

Hi CJ, 

in order to use the functionality described under Claim and provision device, you must be on the main branch of nRF Connect SDK. You can install the main branch following steps in the the nRF Connect SDK Getting started guide. The main branch is a more unstable branch as it features test functionality, etc. We recommend being on a stable, tagged version. nRF Connect SDK v2.5.0 targeted in Q4 of 2023.

Kind regards,
Øyvind