I'm using the NuttX blobs from https://github.com/bouffalolab/bl_blob (not in NuttX but from Rust).
The initial version found in the repository connects fine to my usual access point and my Android hot stop.
However later versions fail to connect to my main access point - however they can still connect to the Android hot spot.
I'm totally aware that the use-case is not officially supported however maybe the problem would also be there when using NuttX.

Parts of the logs of the unsuccessful connect:

...
wpa2/wpa3 pairwise ccmp:1,tkip:0,wep104:0,wep:40:0
wpa2/wpa3 group ccmp:0,tkip:1,wep104:0,wep:40:0
wpa2/wpa3 is_pmf_required:0
AP Security mode: wep:0,wpa:1,wpa2:1,wpa3:0
bl602_net_event called 10 0
------ 250 set default key 0x2201c818, key ptr 0x0
[FW] NULL frame for tx 0x0, len 256
ind ix 0x2201dab4, chan_ctxt is 0x2201bb9c
connect failure, ssid = EasyBox-A50D00, index = 0
from sm_connect_ind to scanu_rm_exist_ssid
start scanu_rm_exist_ssid
delete the existed ssid EasyBox-A50D00
over scanu_rm_exist_ssid
[RX] Connection Status
[RX]   status_code 1
[RX]   reason_code 1
[RX]   connect result: tx auth frame alloc failure
....

How logs of a successful connect to the Android hotspot look like:

...
wpa2/wpa3 pairwise ccmp:1,tkip:0,wep104:0,wep:40:0
wpa2/wpa3 group ccmp:1,tkip:0,wep104:0,wep:40:0
wpa2/wpa3 is_pmf_required:0
AP Security mode: wep:0,wpa:0,wpa2:1,wpa3:0
[WF] find STA vif, index = 0
wpa2/wpa3 pairwise ccmp:1,tkip:0,wep104:0,wep:40:0
wpa2/wpa3 group ccmp:1,tkip:0,wep104:0,wep:40:0
wpa2/wpa3 is_pmf_required:0
AP Security mode: wep:0,wpa:0,wpa2:1,wpa3:0
wpa2/wpa3 pairwise ccmp:1,tkip:0,wep104:0,wep:40:0
wpa2/wpa3 group ccmp:1,tkip:0,wep104:0,wep:40:0
wpa2/wpa3 is_pmf_required:0
AP Security mode: wep:0,wpa:0,wpa2:1,wpa3:0
bl602_net_event called 10 0
------ 250 set default key 0x2201c818, key ptr 0x0
---- 1038 key 0x2201c818, key ptr is 0x0
------------------ [FW] [PSK] [EAPOL] ----------------  diff 8232
---- 1038 key 0x2201c818, key ptr is 0x0
set key:sta_idx:0, inst_nbr:0, key_idx:0,cipher_suite:2,key_len:16
set key:sta_idx:255, inst_nbr:0, key_idx:1,cipher_suite:2,key_len:16
ind ix 0x2201dab4, chan_ctxt is 0x2201bb9c
[RX] Connection Status
[RX]   status_code 0
[RX]   reason_code 0
[RX]   connect result: sm connect ind ok
[RX]   MAC  2:d1:e4:58:df:42
[RX]   vif_idx 0
[RX]   ap_idx 0
[RX]   ch_idx 0
[RX]   qos 1
[RX]   acm 0
[RX]   assoc_req_ie_len 86
[RX]   assoc_rsp_ie_len 99
[RX]   aid 0
[RX]   band 0
[RX]   center_freq 2457
[RX]   width 0
[RX]   center_freq1 2457
[RX]   center_freq2 0
[RX] wifi_mgmr_set_connect_stat_info, wifiMgmr.wifi_mgmr_stat_info:
[RX]   status_code 0
[RX]   reason_code 0
[RX]   MAC  2:d1:e4:58:df:42
[RX]   band 0
[RX]   center_freq 2457
[RX]   type_ind 1
------------------ [FW] [PSK] [EAPOL] ----------------  diff 297225
[WF][SM] Exiting connecting state
[WF][SM] State Action ###connecting### --->>> ###wifiConnected_ipObtaining###
bl602_net_event called
-------------------[FW] Timer is past due to flash operation. Try to fix
4 0
[WF][SM] Exiting wifiConnected_ipObtaining state
[WF][SM] State Action ###wifiConnected_ipObtaining### --->>> ###wifiConnected_IPOK###
-------------------[FW] Timer is past due to flash operation. Try to fix

[WF][SM] Entering wifiConnected_IPOK state
...

As said the initial version of the blob had no problems to connect.
Only obvious difference I see is the tkip:1 for the wpa2/wpa3 group in the failed case.

If this is not the right place for this question, please point me to the right place (GitHub?)