Wi-Fi Combo Forum Discussions

When the Enterprise supplicant fails to connect (e.g., by employing settings on the radius server that prevent authentication of the WICED device), then I am calling the following function in order to reset things and "start again":

besl_supplicant_stop(&supplicant_workspace)

However, calling the function hangs because it waits indefinitely for the thread to exit when calling:

host_rtos_join_thread( &host_workspace->thread )

This function behaves normally if the WICED client is authenticated and connected to the access point.  For example, if the access point goes down, then up, then I need to call besl_supplicant_stop and besl_supplicant_deinit in order to recover the link.  This works Ok.

Any ideas?

I've been combing through the code and documents trying to figure out if the following added to the make file will enable the AES encryption of data that is written to, and read from, the SPI flash:

PLATFORM_SECUREDCT_ENABLED := 1

PLATFORM_SECURESFLASH_ENABLED := 1

GLOBAL_DEFINES += SECURE_SFLASH

I see many useful functions in the file spi_flash_compatible.c, but it is not clear to me if the above automatically enables these functions, or if they need to be manually employed when an SPI with hardware encryption features is connected.

Any guidance would be appreciated.

Thanks!

Hello,

in order to speed up the downloading process time on the CYW943907AEVAL1F board, is there any way to download code and data directly to the RAM ?

Thank you.

Hi,

In WICED code (43xxx_Wi-Fi) lwip version is 2.0.3.

Here lwip 2.0.3 is modified to support wi-fi drivers.

Is there any document that explains what changes are done in lwip to support wi-fi drivers ?

Hi, I tried to install WICED studio version 6.4.0 on windows from here  WICED-Studio 6.4.0 Installer (Windows) i did everything as described in README.txt file but after chosing directory where i want to install IDE occure error like this:

While i got around 200 GB free space on each partition of disc.

I am using windows 10 education and my java version is 8.

let me know if any information about my system or computer can help you solve this problem.

Thanks, Wojciech

I have implemented a form of OTA and write an image of our WICED binary (new firmware)

to the staging area. We then update the DCT so that it will upgrade on the next boot. So
far everything works fine.

However, I am seeing a problem if I inject a reset after the bootloader has started but
before the file has been completely updated. What I am seeing is that the board
fails to reboot.

Is this a known problem? Do you have any suggestions as to how to debug this
(debugging the bootloader, it seems difficult).

Thanks

Is there support for cortex M33  in the new revision of WICED STUDIO?

If not, is it possible to add it? did the GCC compiler supports it in case we add Cortex M33 to the toolchain?