Hi Markel,
It look that for tests you are using cell phone which use cell connection and WiFi (connected to CC32xx at AP mode) at same moment. And it can be problem how your cell phone resolve DNS (it have set multiple DNS servers at different subnets…
Hi Lince ,
This error is common when device is not at development mode. Use UART connection and Uniflash software to switch device into development mode.
Jan
Hi,
I think you understanding is right. But because I am not a TI employee and I don't have access to NWP source code, you can wait for confirmation from TI side.
Jan
Hi Markel,
I think you shouldn’t be afraid that you’ll need to update your code to a newer version of the CC32xx SDK. I would even bet that there won’t be any newer CC32xx SDK versions anymore.
Jan
Hi,
I have no relation TI, from this reason I don't need to "play for TI team" or not say true about stability issues. By my comment I don't want to harm you anyway, I just talk about my experiences with CC3220 devices (at e2e forum I have 3k+ posts…
Hi Markel,
No is not. CC3220/CC3235 devices are at LTS state. That means no new features, no support for new CCS only critical security fixes. I think latest officially supported CCS is 12.
Jan
Hi,
This feature is not supported by CC3200 by NWP stack. If you need this features, you can use external TLS stack at application processor even it may to be challenge due to memory constrains.
Jan
Hi,
It is not possible scan hidden SSID. This comes from WiFi standards and this can't be overcome by any way. Only way how to say that hidden SSID is alive, is to try connect. Lilley SiLabs and U-Blox modules try connect to selected SSID on background…
