Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I agree patching with old version of BESL could cause more issues later since we don't know what's inside the lib file and moreover they are not tested together thoroughly. If Cypress/Broadcom didn't patch it with a beta lib, we should just stick with 3.5.2 for now.
WICED seems to use dynamic memory allocation very heavily, to its detriment.
Even in their host_rtos_create_thread, I don't think there is even an option provided to use statically allocated stacks for tasks. There is a reason that NASA totally disallows dynamic memory in all their embedded code ...
Has anyone tried MALLOC_DEBUG with real code? And/or attacked this problem with a trace probe?
In the BESL archive files, it looks like there are only about 25 calls to malloc in one form or another, only 3 associated with tls_host_malloc. And the code for those is provided, just a wrapper around malloc_named or malloc.