Can't get WiFi and PSA API to work in the same application using nRF7002DK

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Thu, 11 Jan 2024 09:52:27 GMT

Hi,

To successfully combine PSA with Wi-Fi you need to use non-secure target. When using PSA backend for Wi-Fi credentials, build must be with TF-M (_ns build target). Please refer to point 16 in the lesson 5 exercise 3 of the Wi-Fi Fundamentals Course.

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

MarioDLH — Wed, 10 Jan 2024 13:38:53 GMT

Hi.

Sorry for the insistence. Coming back to the first topic and to sum up everything, the idea at the beginning was to use both WiFi and PSA in the secure target (without *ns), which now I know it's not possible and it has to be done with the non-secure target. This actually was the first option in our project, as we need to use a secure partition in order to have some code executed in the secure environment, but in this ticket I was told that WiFi couldn't be used with this secure/non-secure split and this led us to use the secure target. This is not what it's turned out to be in this case, although the WiFi samples documentation also specify only the secure target as compatible.

So in order to better understand it, should it be possible to combine WiFi, PSA and secure partition using the non-secure target and the configurations you've provided to have some code executed in the secure side without issues? So far I've tried to test that combination and it actually works up to a certain point where the function call to the secure side fails (not the previous calls though), but that may be due to some memory misconfiguration. I'd like to have this clarified before moving forward in this way.

Thanks again for your help.

Best regards.

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Tue, 09 Jan 2024 14:24:41 GMT

Hi,

[quote user="MarioDLH"]I'll try to adapt it to the non-secure target then.[/quote]

This is a correct way forward.

Please let me know if you have any further questions.

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

MarioDLH — Tue, 09 Jan 2024 12:09:52 GMT

Hi.

Thanks for the reply. I'll try to adapt it to the non-secure target then.

Best regards.

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Tue, 09 Jan 2024 08:33:15 GMT

Hi,

[quote user="MarioDLH"]Is there another possible fix for the secure build target?[/quote]

Unfortunately, there is no fix for secure build target. There is a dependency on config BUILD_WITH_TFM on the crypto side. Therefore, it can work only with non-secure builds.

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

MarioDLH — Mon, 08 Jan 2024 12:30:45 GMT

Hi.

Although it works fine with the non-secure target, the full project is being developed currently with the secure one due to memory problems in this SDK version, which is also the one considered in the main issue since the WiFi samples are shown to be compatible only with this one in the documentation. Is there another possible fix for the secure build target?

Thanks.

Best regards.

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Fri, 05 Jan 2024 16:20:06 GMT

Hi,

I tested your combined project by building it with non-secure build target nrf7002dk_nrf5340_cpuapp_ns. As shown in building with *_ns, application is built as non-secure image and TF-M as secure image. In general, if sample is built for non-secure target, it automatically includes TF-M.

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

MarioDLH — Fri, 05 Jan 2024 13:52:21 GMT

Hi.

Thanks for your reply. I've tested the configurations and it works fine. Since those are TF-M configs and the target is the non-secure one, do they make the WiFi sample compatible with it then? The sample only lists the secure target as compatible and is the one I was using at first but it actually works adding those options, so I'd like to clarify that.

Thanks again for the solution.

Best regards.

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Fri, 05 Jan 2024 12:37:04 GMT

Hi,

I have tested potential solution to your problem. You should be able to get both samples to work if you make nrf7002dk_nrf5340_cpuapp_ns.conf file and include it into your build configuration. The content of the file is shown below. Please test it yourself to verify that it is working for you.

CONFIG_WIFI_CREDENTIALS_BACKEND_PSA=y
CONFIG_TFM_PROFILE_TYPE_MEDIUM=y
CONFIG_PM_PARTITION_SIZE_TFM_SRAM=0x18000
CONFIG_MBEDTLS_HEAP_SIZE=16384

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Thu, 04 Jan 2024 17:40:32 GMT

Hi,

I am sorry for a delayed reply. I was out of the office.

There is a functionality implication of disabling 2 mentioned configuration options in the sense that this would potentially make all wifi features unusable. In other words, they would probably not work. WPA_SUPP uses non-PSA calls which might affect PSA SHA 256 sample. I have reported this issue to our developers and they will look into it. I will get back to you with new findings, probably during next week.

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Tue, 12 Dec 2023 15:09:13 GMT

Hi,

I have reproduced your issue. I tested the combination of both samples and observed the same behavior as you reported. The only way crypto sample was able to correctly compute hash was when I disabled 2 wi-fi configuration options shown below.

CONFIG_WPA_SUPP=n
CONFIG_NETWORKING=n

I have also asked internally for more information.

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

MarioDLH — Mon, 11 Dec 2023 11:40:26 GMT

Hi,

The error is basically the output when hash fails, like this:

*** Booting nRF Connect SDK v2.5.OK
0 ***
[00:00:00.451,721] <inf> net_config: Initializing network
[00:00:00.451,721] <inf> net_config: Waiting interface 1 (0x20001508) to be up...
[00:00:00.451,843] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.451,904] <inf> net_config: Running dhcpv4 client...
[00:00:00.452,148] <inf> sta: Starting SHA256 example...
[00:00:00.452,178] <inf> sta: ---- Plaintext to hash (len: 150): ----
[00:00:00.452,178] <inf> sta: Content:
                              45 78 61 6d 70 6c 65 20  73 74 72 69 6e 67 20 74 |Example  string t
                              6f 20 64 65 6d 6f 6e 73  74 72 61 74 65 20 62 61 |o demons trate ba
                              73 69 63 20 75 73 61 67  65 20 6f 66 20 53 48 41 |sic usag e of SHA
                              32 35 36 2e 54 68 61 74  20 75 73 65 73 20 73 69 |256.That  uses si
                              6e 67 6c 65 20 61 6e 64  20 6d 75 6c 74 69 2d 70 |ngle and  multi-p
                              61 72 74 20 50 53 41 20  63 72 79 70 74 6f 20 41 |art PSA  crypto A
                              50 49 27 73 20 74 6f 20  70 65 72 66 6f 72 6d 20 |PI's to  perform 
                              61 20 53 48 41 2d 32 35  36 20 68 61 73 68 69 6e |a SHA-25 6 hashin
                              67 20 6f 70 65 72 61 74  69 6f 6e 2e 00 00 00 00 |g operat ion.....
                              00 00 00 00 00 00                                |......           
[00:00:00.452,209] <inf> sta: ---- Plaintext to hash end  ----
[00:00:00.452,209] <inf> sta: Hashing using SHA256...
[00:00:00.452,239] <inf> sta: psa_hash_compute failed! (Error: -134)
[00:00:00.452,239] <inf> sta: Example exited with error!

To combine both samples, I simply copied the configurations in prj.conf from sha256 sample into the prj.conf file of the station sample, looking like this:

#
# Copyright (c) 2022 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_WIFI=y
CONFIG_WIFI_NRF700X=y

# WPA supplicant
CONFIG_WPA_SUPP=y

# Below configs need to be modified based on security
# CONFIG_STA_KEY_MGMT_NONE=y
CONFIG_STA_KEY_MGMT_WPA2=y
# CONFIG_STA_KEY_MGMT_WPA2_256=y
# CONFIG_STA_KEY_MGMT_WPA3=y
CONFIG_STA_SAMPLE_SSID=""
CONFIG_STA_SAMPLE_PASSWORD=""

# System settings
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_NANO=n

# Networking
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_LOG=y
CONFIG_NET_IPV4=y
CONFIG_NET_UDP=y
CONFIG_NET_TCP=y
CONFIG_NET_DHCPV4=y

CONFIG_NET_PKT_RX_COUNT=8
CONFIG_NET_PKT_TX_COUNT=8

# Below section is the primary contributor to SRAM and is currently
# tuned for performance, but this will be revisited in the future.
CONFIG_NET_BUF_RX_COUNT=16
CONFIG_NET_BUF_TX_COUNT=16
CONFIG_NET_BUF_DATA_SIZE=128
CONFIG_HEAP_MEM_POOL_SIZE=153600
CONFIG_NET_TC_TX_COUNT=1

CONFIG_NET_IF_UNICAST_IPV4_ADDR_COUNT=1
CONFIG_NET_MAX_CONTEXTS=5
CONFIG_NET_CONTEXT_SYNC_RECV=y

CONFIG_INIT_STACKS=y

CONFIG_NET_L2_ETHERNET=y

CONFIG_NET_CONFIG_SETTINGS=y
CONFIG_NET_CONFIG_INIT_TIMEOUT=0

CONFIG_NET_SOCKETS_POLL_MAX=6

# Memories
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
CONFIG_NET_TX_STACK_SIZE=4096
CONFIG_NET_RX_STACK_SIZE=4096

# Debugging
CONFIG_STACK_SENTINEL=y
CONFIG_DEBUG_COREDUMP=y
CONFIG_DEBUG_COREDUMP_BACKEND_LOGGING=y
CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_MIN=y
CONFIG_SHELL_CMDS_RESIZE=n


# Kernel options
CONFIG_ENTROPY_GENERATOR=y

# Logging
CONFIG_LOG=y
CONFIG_LOG_BUFFER_SIZE=2048
CONFIG_POSIX_CLOCK=y

CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.168.1.99"
CONFIG_NET_CONFIG_MY_IPV4_NETMASK="255.255.255.0"
CONFIG_NET_CONFIG_MY_IPV4_GW="192.168.1.1"

# printing of scan results puts pressure on queues in new locking
# design in net_mgmt. So, use a higher timeout for a crowded
# environment.
CONFIG_NET_MGMT_EVENT_QUEUE_TIMEOUT=5000

# The Zephyr CMSIS emulation assumes that ticks are ms, currently
CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000

# Enable nordic security backend and PSA APIs
CONFIG_NRF_SECURITY=y
CONFIG_MBEDTLS_PSA_CRYPTO_C=y

CONFIG_MBEDTLS_ENABLE_HEAP=y
CONFIG_MBEDTLS_HEAP_SIZE=8192

CONFIG_PSA_WANT_ALG_SHA_256=y

I also copied the required code from main.c of sha256 into main.c of the station sample, adding the hash operations before the execution of the original code and giving the output specified before.

This is the case of the combination of both samples, but I also face the other problems I mentioned in other replies when I use both WiFi and hash in my full project, like variables having wrong values while debugging or stack overflows, probably caused by the same memory problems that occur with this combination. I've attached the modified sample.

Thanks.

Best regards.

devzone.nordicsemi.com/.../sta.zip

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Fri, 08 Dec 2023 08:38:47 GMT

Hi,

Could you provide full error log?

Could you also provide information how you combined two mentioned samples?

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

MarioDLH — Thu, 07 Dec 2023 11:54:38 GMT

Hi.

Yes, they both work properly separately. The problem arises when trying to use them in a single application.

Best regards.

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Tue, 05 Dec 2023 14:08:54 GMT

Hi,

Do Wi-Fi station and SHA-256 samples work for you if you use them separately?

Best regards,
Dejan

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

MarioDLH — Fri, 01 Dec 2023 13:43:03 GMT

Hi.

Thanks for your reply. I've tried to follow the guides provided, specifically using the configurations listed under Usage profiles for the memory optimized STA mode. However I still face the same issue with the PSA API, being unable to do the hash operations, as well as other memory problems while running the project (global variables with wrong values). I also decreased the main stack size and used thread analyzer to check memory usage, which constantly shows that there is still enough unused memory. This is an example of the output:

Thread analyze:
 0x20002fa0          : STACK: unused 1256 usage 2840 / 4096 (69 %); CPU: 0 %
      : Total CPU cycles used: 16
 0x20001680          : STACK: unused 564 usage 460 / 1024 (44 %); CPU: 0 %
      : Total CPU cycles used: 14
 0x20003078          : STACK: unused 6168 usage 2024 / 8192 (24 %); CPU: 5 %
      : Total CPU cycles used: 406
 0x200027c8          : STACK: unused 840 usage 184 / 1024 (17 %); CPU: 0 %
      : Total CPU cycles used: 1
 0x200028a0          : STACK: unused 3912 usage 184 / 4096 (4 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x20002360          : STACK: unused 3800 usage 296 / 4096 (7 %); CPU: 0 %
      : Total CPU cycles used: 2
 0x20002a38          : STACK: unused 792 usage 232 / 1024 (22 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x20002e40          : STACK: unused 792 usage 232 / 1024 (22 %); CPU: 0 %
      : Total CPU cycles used: 0
 0x200036e0          : STACK: unused 2280 usage 280 / 2560 (10 %); CPU: 0 %
      : Total CPU cycles used: 21
 0x20002108          : STACK: unused 792 usage 232 / 1024 (22 %); CPU: 0 %
      : Total CPU cycles used: 1
 0x20003130          : STACK: unused 1352 usage 696 / 2048 (33 %); CPU: 3 %
      : Total CPU cycles used: 267
 0x20003208          : STACK: unused 1048 usage 1000 / 2048 (48 %); CPU: 0 %
      : Total CPU cycles used: 41
 0x20001738          : STACK: unused 552 usage 216 / 768 (28 %); CPU: 0 %
      : Total CPU cycles used: 1
 0x20003508          : STACK: unused 224 usage 96 / 320 (30 %); CPU: 62 %
      : Total CPU cycles used: 4740
 0x200035c0          : STACK: unused 3244 usage 1876 / 5120 (36 %); CPU: 22 %
      : Total CPU cycles used: 1726
 ISR0                : STACK: unused 892 usage 1156 / 2048 (56 %)

Is there any other possible approach to this issue?

Thanks.

Best regards.

RE: Can't get WiFi and PSA API to work in the same application using nRF7002DK

dejans — Thu, 30 Nov 2023 13:32:57 GMT

Hi,

For potential memory problems, there are some guides in the documentation which you could look at - memory footprint optimization and memory requirements for Wi-Fi applications.

Best regards,
Dejan