nRF7000 device tree file for custom nRF9160 board

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Mon, 21 Oct 2024 08:30:44 GMT

Hi,

I was able to fix this issue by just copying the full config for nrf7000 from the asset tracker V2 sample.

# Disable modem traces as UART1 is disabled
CONFIG_NRF_MODEM_LIB_TRACE=n

CONFIG_LOCATION_METHOD_WIFI=y

# Align this with CONFIG_NRF_WIFI_SCAN_MAX_BSS_CNT.
# Also see comments for CONFIG_HEAP_MEM_POOL_SIZE.
CONFIG_LOCATION_WORKQUEUE_STACK_SIZE=8192

# Actual configs for the Wi-Fi
CONFIG_WIFI=y
CONFIG_WIFI_NRF700X=y
CONFIG_WIFI_NRF700X_SKIP_LOCAL_ADMIN_MAC=y
# Align this with CONFIG_LOCATION_METHOD_WIFI_SCANNING_RESULTS_MAX_CNT.
# Also see comments for CONFIG_HEAP_MEM_POOL_SIZE.
# Wi-Fi shell sample has 25000 heap size. We need a bit more for location request purposes.
# Heap allocation should be changed when CONFIG_LOCATION_METHOD_WIFI_SCANNING_RESULTS_MAX_CNT
# and CONFIG_NRF_WIFI_SCAN_MAX_BSS_CNT (which should be the same value) are changed.
CONFIG_NRF_WIFI_SCAN_MAX_BSS_CNT=10

# System settings
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

# Scan only using offload API
CONFIG_WPA_SUPP=n

# For nRF9160 the default is socket interface
CONFIG_NET_DEFAULT_IF_ETHERNET=y
CONFIG_MBEDTLS=n
CONFIG_NORDIC_SECURITY_BACKEND=n

# Networking
CONFIG_NET_L2_ETHERNET=y
CONFIG_NET_NATIVE=y
CONFIG_NET_DHCPV4=y
CONFIG_NET_STATISTICS=y
CONFIG_NET_STATISTICS_WIFI=y
CONFIG_NET_STATISTICS_USER_API=y
CONFIG_NET_CONTEXT_SYNC_RECV=y

# Disable unused networking options
CONFIG_NET_IPV6=n

# Memory configurations
CONFIG_NET_BUF_RX_COUNT=8
CONFIG_NET_BUF_TX_COUNT=8
CONFIG_NET_PKT_RX_COUNT=1
CONFIG_NET_PKT_TX_COUNT=1
CONFIG_NET_TX_STACK_SIZE=4096
CONFIG_NET_RX_STACK_SIZE=4096
CONFIG_NET_TC_TX_COUNT=1
CONFIG_NET_MAX_CONTEXTS=5
CONFIG_NET_MGMT_EVENT_STACK_SIZE=1024

The only point I add because of the error was

CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

RE: nRF7000 device tree file for custom nRF9160 board

dejans — Mon, 21 Oct 2024 08:11:56 GMT

Hi,

It seems that Wi-FI interface might have failed. Can you please
1. provide "net iface" output?
2. enable logging using CONFIG_LOG and provide full log? You could also include driver debug logs using CONFIG_WIFI_NRF700X_LOG_LEVEL_DBG=y.

Best regards,
Dejan

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Sun, 20 Oct 2024 13:44:28 GMT

dejans do you have any suggestions to test or check? We stuck with this issue.

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Sun, 20 Oct 2024 06:55:08 GMT

No it is fully custom board with nrf9160 and nrf7000.

RE: nRF7000 device tree file for custom nRF9160 board

dejans — Fri, 18 Oct 2024 13:48:07 GMT

Hi,

Do you use nrf7002EK shield with your nrf9160 custom board?

Best regards,
Dejan

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Fri, 18 Oct 2024 11:37:49 GMT

I also checked if SPI3, which I am using, was not working simultaneously with another peripheral having the same ID. Everything is fine.

UART3 and I2C3 are disabled in the zephyr.dts.

I also tested the build with the following configuration added:

CONFIG_TFM_SECURE_UART=n

CONFIG_TFM_LOG_LEVEL_SILENCE=y

Didn't help also.

I need your support. We have been stuck and unable to solve this issue for more than a week.

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Thu, 17 Oct 2024 17:33:06 GMT

Hello,

We have designed a custom PCB using the nRF9160 as the main IC and the nRF7000 for Wi-Fi scanning. The schematic and layout were reviewed by Nordic technical support before production.

To ensure there were no hardware issues and that all connections were correct, I tested the PCB using the Location and Radio_test samples.

For the Location sample, I built it for the nrf9160dk_nrf9160_ns with the following settings: -DSHIELD="nrf7002ek" and nrf9160dk_nrf9160_ns.overlay.

(The overlay file is attached in the first message.)

Here is a screenshot from the log. From what I understand, the Wi-Fi is working, but the signal strength is weak. This might be due to the need for tuning the RF path components.

For the Location sample, I built it for the nrf9160dk_nrf9160_ns with the following settings: -DSHIELD="nrf7002ek", -DOVERLAY_CONFIG="overlay-nrf7002ek-wifi-scan-only.conf", and nrf9160dk_nrf9160_ns.overlay.

Below is the log from the Location sample:

[00:00:00.387,634] <inf> wifi_nrf_bus: SPIM spi@b000: freq = 8 MHz
[00:00:00.394,714] <inf> wifi_nrf_bus: SPIM spi@b000: latency = 0
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
Location sample started

Connecting to LTE...
Connected to LTE
Waiting for current time
[00:01:31.652,099] <dbg> location: location_core_init: Initialized 'GNSS' method successfully
[00:01:31.661,651] <dbg> location: location_core_init: Initialized 'Cellular' method successfully
[00:01:31.671,569] <dbg> location: location_core_init: Initialized 'Wi-Fi' method successfully
[00:01:31.681,182] <dbg> location: location_core_init: Initialized 'Wi-Fi + Cellular' method successfully
[00:01:31.691,833] <dbg> location: location_init: Location library initialized
Requesting Wi-Fi location with GNSS and cellular fallback...
[00:01:31.705,627] <dbg> location: location_core_config_log: Location configuration:
[00:01:31.714,324] <dbg> location: location_core_config_log:   Methods count: 2
[00:01:31.722,595] <dbg> location: location_core_config_log:   Interval: 0
[00:01:31.730,407] <dbg> location: location_core_config_log:   Timeout: 300000ms
[00:01:31.738,769] <dbg> location: location_core_config_log:   Mode: 0
[00:01:31.746,215] <dbg> location: location_core_config_log:   List of methods:
[00:01:31.754,455] <dbg> location: location_core_config_log:     Method #0
[00:01:31.762,298] <dbg> location: location_core_config_log:       Method type: Wi-Fi (3)
[00:01:31.771,484] <dbg> location: location_core_config_log:       Timeout: 30000ms
[00:01:31.780,120] <dbg> location: location_core_config_log:       Service: Any (0)
[00:01:31.788,757] <dbg> location: location_core_config_log:     Method #1
[00:01:31.796,569] <dbg> location: location_core_config_log:       Method type: Cellular (1)
[00:01:31.806,030] <dbg> location: location_core_config_log:       Timeout: 30000ms
[00:01:31.814,666] <dbg> location: location_core_config_log:       Service: Any (0)
[00:01:31.823,333] <dbg> location: location_core_config_log:       Cell count: 4
[00:01:31.831,695] <inf> location: Wi-Fi and cellular methods combined
[00:01:31.839,111] <dbg> location: location_request_info_create: Updated location method list:
[00:01:31.848,754] <dbg> location: location_request_info_create:     Method #0 type: Wi-Fi + Cellular (4)
[00:01:31.859,405] <dbg> location: location_core_location_get_pos: Requesting location with 'Wi-Fi + Cellular' method
[00:01:31.871,154] <dbg> location: location_core_location_get_pos: Starting request timer with timeout=300000
[00:01:31.882,202] <dbg> location: scan_wifi_execute: Triggering start of Wi-Fi scanning
[00:01:31.902,313] <dbg> location: scan_wifi_execute: Starting Wi-Fi timer with timeout=30000
[00:01:31.913,482] <dbg> location: scan_cellular_execute: Triggering cell measurements timeout=30000, cell_count=4
[00:01:31.924,957] <dbg> location: scan_cellular_execute: Starting cellular timer with timeout=30000
[00:01:31.935,180] <dbg> location: scan_cellular_execute: Normal neighbor search (NCELLMEAS=1)
[00:01:31.946,441] <dbg> location: scan_cellular_lte_ind_handler: Cell measurements results received: ncells_count=0, gci_cells_count=0, current_cell.id=0x0901B929
[00:01:31.962,402] <dbg> location: scan_cellular_lte_ind_handler: No neighbor cell information from modem
[00:01:31.973,022] <dbg> location: scan_cellular_lte_ind_handler: No surrounding cell information from modem
[00:01:31.983,978] <dbg> location: scan_cellular_execute: RRC already in idle mode
[00:01:31.992,523] <dbg> location: scan_cellular_execute: GCI history search (NCELLMEAS=3,5)
[00:01:32.004,547] <dbg> location: scan_cellular_lte_ind_handler: Cell measurements results received: ncells_count=0, gci_cells_count=0, current_cell.id=0x0901B929
[00:01:32.020,538] <dbg> location: scan_cellular_lte_ind_handler: No neighbor cell information from modem
[00:01:32.031,158] <dbg> location: scan_cellular_lte_ind_handler: No surrounding cell information from modem
[00:01:32.042,144] <dbg> location: scan_cellular_execute: GCI regional search (NCELLMEAS=4,4)
[00:01:32.053,894] <dbg> location: scan_cellular_lte_ind_handler: Cell measurements results received: ncells_count=0, gci_cells_count=0, current_cell.id=0x0901B929
[00:01:32.069,824] <dbg> location: scan_cellular_lte_ind_handler: No neighbor cell information from modem
[00:01:32.080,444] <dbg> location: scan_cellular_lte_ind_handler: No surrounding cell information from modem
[00:01:36.516,601] <dbg> location: scan_wifi_done_handle: Scan request done with 0 Wi-Fi APs
[00:01:36.526,214] <wrn> location: No Wi-Fi scanning results, using only cellular data
[00:01:36.535,827] <dbg> location: cloud_service_location_get: Cloud service location parameters:
[00:01:36.545,715] <dbg> location: cloud_service_location_get:   Service: 0
[00:01:36.553,619] <dbg> location: cloud_service_location_get:   Timeout: 295324ms
[00:01:36.562,164] <dbg> location: cloud_service_nrf_pos_get: Sending positioning request (REST)
[00:01:52.199,890] <dbg> location: location_core_event_cb_fn: Location acquired successfully:

This is the output log from my application:

*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
[00:00:00.254,638] <inf> app_event_manager: APP_EVT_START
[00:00:00.486,206] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:00.487,335] <dbg> location: location_core_init: Initialized 'Cellular' method successfully
[00:00:00.487,365] <err> location: No Wi-Fi interface found: nordic_wlan0
[00:00:00.487,396] <err> location: Failed to initialize 'Wi-Fi' method
[00:00:00.487,426] <err> location_module: Initializing the Location library failed, error: -14
[00:00:00.487,426] <err> location_module: setup, error: -1

The first issue is that in both the Location and Radio_test samples, I see logs related to SPI, but in my application, I don't. I'm not sure if this is due to log settings or if it indicates that SPI isn't working.

For my application, I used the Assert Tracker v2 as a reference and made some code changes, but I didn’t modify the Location module.

When I check the device tree viewer, it shows that the nRF7000 is assigned to SPI3, and all the necessary pins are set up correctly.

The key point is that I am now building for a custom board, not for the nRF9160DK. All the configurations and devicetree changes I made to support the nRF7000 are mentioned in my first message.

I also noticed that I forget to add CONFIG_SPI but this didn't help.

Maybe there is something I need to add for the MCUboot?

RE: nRF7000 device tree file for custom nRF9160 board

dejans — Thu, 17 Oct 2024 16:10:43 GMT

Hi,

Can you provide more information about your board, especially with regard to nrf7002?

Which application or sample did you use as a starting point for your application?

[quote user="Roman Veselskyi"]Do you have any guide or a sample how to connect nRF700x to custom board? [/quote]

We have cellular location sample and nRF Cloud multi-service sample. Both samples can be run on nrf9160dk with a wi-fi nrf7002 EK shield. If you want to use wi-fi only for scanning and not for connectivity, you can find more information on determining device location using wi-fi webpage.

There is more information about location library, location services features and location services guide available in the documentation.

Best regards,
Dejan

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Thu, 17 Oct 2024 11:41:18 GMT

Hello,

Do you have any update on this?

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Thu, 17 Oct 2024 05:56:24 GMT

Do you have any guide or a sample how to connect nRF700x to custom board?

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Wed, 16 Oct 2024 14:58:51 GMT

*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
[00:00:00.254,699] <inf> app_event_manager: APP_EVT_START
[00:00:00.486,267] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:00.487,548] <dbg> location: location_core_init: Initialized 'Cellular' method successfully
[00:00:00.487,579] <err> location: No Wi-Fi interface found: nordic_wlan0
[00:00:00.487,609] <err> location: Failed to initialize 'Wi-Fi' method
[00:00:00.487,640] <err> location_module: Initializing the Location library failed, error: -14
[00:00:00.487,640] <err> location_module: setup, error: -1

RE: nRF7000 device tree file for custom nRF9160 board

dejans — Wed, 16 Oct 2024 13:11:10 GMT

Hi,

Can you provide complete application log?

Best regards,
Dejan

RE: nRF7000 device tree file for custom nRF9160 board

Roman Veselskyi — Wed, 16 Oct 2024 08:47:18 GMT

nRF SDK 2.6.1