cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

Anonymous
Not applicable

Dear Cypress Team,

We have been developing our project using WICED 3.7 (with FreeRTOS as our OS) for a while now and we feel that there are some stability issues that have not been addressed in this SDK version. We Would like to migrate to WICED 5, however we are not sure if our controller (BCM43340) and selected OS (FreeRTOS) is supported.

We are using Azurewave AW-AH640 SiP which contains BCM43340.

Can you please confirm if it is possible to migrate to WICED 5 in our situation.

Regards,
Erik

0 Likes
Reply
1 Solution
Moderator
Moderator

FreeRTOS and the 43340 platform are both supported in WICED Studio 5.0

5.2.0 is the current version: WICED Studio Wi-Fi/Combo Docs & Downloads

View solution in original post

0 Likes
Reply
4 Replies
Moderator
Moderator

FreeRTOS and the 43340 platform are both supported in WICED Studio 5.0

5.2.0 is the current version: WICED Studio Wi-Fi/Combo Docs & Downloads

View solution in original post

0 Likes
Reply
Anonymous
Not applicable

Thank you for your quick response.

Regards,
Erik

0 Likes
Reply
Honored Contributor

eriknorth wrote:

Dear Cypress Team,

We have been developing our project using WICED 3.7 (with FreeRTOS as our OS) for a while now and we feel that there are some stability issues that have not been addressed in this SDK version.

Hi eriknorth​,

Can you share what kind of stability issues you hit?

0 Likes
Reply
Anonymous
Not applicable

Hi axel.lin_1746341,

Most of our issues are related to BT/BLE as the stack is closed sourced. I can list you some of the issues we are having and if required I can provide you with some more details.

1. When BT (not BLE) paired with phone or PC, after power cycling the WICED device, phone or PC requires to repair.

2. iOS or Android is not able to save pairing information of two WICED devices. In the Bluetooth settings of the phone the second device is seen as connected but it lacks the pairing (also on the device side we get errors of failed pairing). As soon as we unpair the first, second is able to pair successfully. We reported this issue quite a while back (https://community.cypress.com/thread/8233) and we did not get any response.

3. We have implemented ANCS service for iOS, and we subscribe to "Notification source" and "Data source" in the service. And the data then is received on GATTC_OPTYPE_NOTIFICATION event. However very often the device Hard fault crashes while executing this event even if we do not put any extra code there for processing the received data. And it has been hard time to debug this because of closed source and sometimes hard reproduction (mostly this happens when there is more incoming data).

Regards,

Erik