Update to NCS3.0.0 broke wifi WPA2-PSK connect?

[BrianW]

Custom PCB with nrf5340/nrf7002. Currently was using NCS2.9.0, with WPA2-PSK connection to the wifi.

While trying to enable use of WPA2-Enterprise, I updated to NCS3.0.0 (to see if the increased flash requirement of around 45kB! was perhaps less). This turned out to be WAY worse (another 49kB on top for identical prj.conf), but also broke the WP2-PSK connection it seems?

Previous it would connect fine, but now it times out and I see these logs:

[00:02:21.108,764] <err> wpa_supp: Error in pbkdf2_sha1()
[00:02:21.110,382] <err> wpa_supp: Line 0: invalid key_mgmt 'SAE'

Any idea what these mean? I previously had the SAE log from time to time : I assumed this is for WPA3 with SAE key exchange which I wasn't using (WPA2-PSK) and it didn't block the connection.

If anyone has any ideas about how to trim down the wifi stack usage also I'd be interested too as it no longer fits in the flash on my nrf5340 (and yes, I already have the nrf70 fw and all other mcyboot slots in a external flash...)

[Simonr]

Hi Brian

I've forwarded these questions to the developer team now, and will get back to you when I hear from them. I wouldn't hold my breath waiting for a sample project though, as this would take time to make/implement on our end, but I'll let you know what we find out.

Best regards,

Simon

[BrianW]

Simonr said:

take time to make/implement on our end,

I'd push the point that if there is no way to reduce the wifi stack burden in the main flash significantly (either by optimising wpa_supp or by allowing it to be run as an XIP module) then the nrf5340 will not be seen as a viable target to build a wifi endpoint application.

Currently I would not recommend to anyone looking to start a design process to select the nrf5340 if they have a need for even basic wifi STA connectivity due to the very high flash space usage (and I haven't even tried to get the softAP functionality in there, as often used by IOT devices for their setup).