WICED is certainly an open platform so anything can be ported to it.
But duplicating a significant part of the BESL library to add a single function,
well it seems there could be a better use of your time. Would you port a new BLE stack?
Probably not. The goal of WICED is to provide an integrated platform so users can
value add at the application level.
I would also point out that speculation that uSSL is a fork of TropicSSL is incorrect.
To give a little background, as per the README, we are the OEM suppliers of uSSL SDK included in WICED SDK.
The Broadcom WICED team adapted uSSL into WICED, including modifications adding it to the platform framework.
They call the shots on what goes into WICED, including new features and bugfixes, and we don't have any direct control over it.
However, at Cypherbridge our mission is to deliver the best possible leading edge solutions for embedded IoT security and
connectivity. We do offer an option for WICED customers to work with us directly for support and upgrades,
including customized builds. To get the latest and greatest features and direct technical support, please contact us
on our WICED support page, include your company contact information, and we can take it from there.
Thanks Steve, I speculated that BESL was a fork based upon the copyrights in many of the crypto includes:
/* Originally taken from TropicSSL
I regard that as a positive thing, not a negative thing. I noted in the LICENSE.txt file:
SSL/TLS object files and headers are licensed by Broadcom, Inc from Cypherbridge Systems, LLC.
According to a TropicSSL site, TropicSSL is an unofficial fork of PolarSSL/XySSL. PolarSSL is now the mbed TLS, and closely related XySSL. Having a heritage that ARM has endorsed, in my mind is not a bad thing, so my intent was not to insult you or anybody else.
Regarding the effort to port for a single function, that is hard to say. I've merged/ported several different TLS stacks recently on various projects. The effort is time consuming, but not impossible and I'd much rather figure out how to get access to the function if that is possible. Based upon studying the files where source is included, I also speculated that the BESL stack supported PSK and it might not be impossible to use PSK, and it might just be an issue of knowing how. Anyway, I'm open to ideas as to how I might get there. I am currently using the system as designed but I certainly believe that in my application, PSK is a better answer.
Hi Chuck, no offense given or taken. I get it. You need a solution to add PSK
Please register at
You mentioned wolfSSL is not documented anywhere, were you referring to the process of porting wolfSSL to WICED specifically or just the library itself?
If the library, documentation can be found here: https://www.wolfssl.com/wolfSSL/Docs.html
If you were referring to the overall process and you can not get TropicSSL working please shoot us a note firstname.lastname@example.org. We'll see what we can do to help! wolfSSL has full PSK support.
i was not referring to WolfSSL documentation, I was referring to the WICED library that is provided only as object code and certain aspects were not fully documented.
I have evaluated WolfSSL in other platforms and I fully believe that WolfSSL is one of the premier TLS implementations for embedded.
You will ill find my details in your DB. we could talk offline about my focus. Anyway, I have very high regard for your products.