Wi-Fi Combo Forum Discussions

Hi,

We have our Cypress account registered with Apple MFi account. When we tried to download WICED Studio 6.2.1 and install, we couldn't see the Apple MFI libraries in the SDK. Can you please let us know how we get access to the same?

Regards,

Mani

Hello,

Since two/three days I'm trying to update via the OTA, transition V1 to a V2 by modifying several things:

- transition from WICED5.1 to WICED6.1

- Using the mqtt protocol to communicate with a new server

- plus some minor modification.

However, I can not achieve this update and it seems that this is associated with the size of my file, which increases in large part by the use of mbedTLS Re: MBEDTLS occupies lot of memory space after an upgrade .

Binary file store in external file reach ~530ko (previously 390ko).

I tried to modify the wiced_apps.mk (tools / makefiles) and platform_dct.h (WICED / platform / include) files to enlarge the sectors without success.

Can you guide me to find a solution?

I read a some similar issues (seems to be solved but I do not understand why ?) :

OTA Slots as defined in ota_fr.c

Re: OTA upgrade problem

ota_fr fail @ grater size of update file than DCT_APP0 size

OTA upgrade without FR on 3.1.2

Is there any function to change the clock rate of CYW43907? What is the default clock rate ? To increase the performance of the chip how to set it to 320MHz?

Thanks.

Hi,

   I'm exploring the capability of CYW4343W to enable master(central) and slave(peripheral) mode simultaneously. I can not find the answer from documents or discussions on the forum. Is this software configurable in WICED?

Thank you,

Min-Ching

I am using CYW43907 for development. In this application, large amount of data is moving from SPI to memory and memory to memory. Currently, it take a lot of CPU time for such movement. Are there any SPI DMA and memory to memory DMA example for CYW43907 ?

Thanks.

I'm using Gedday to connect to an Android device.

Gedday works okay most of the time.

Maybe, 5% of the time the gedday_init(...) call fails. I should be more specific. The call blocks & never returns.

Here's the call:

result = gedday_init(

            WICED_STA_INTERFACE,

            "WICED_Gedday_Discovery_Example"

    );

Any insight is helpful.

Thank you.

We have two problems occurring.

• case 1
  • Installing WICED Studio takes a long time to install on a specific PC.
    (It took more than an hour.)
• case 2
  • Full build takes more than 2 hours to complete.

I tried it on some PCs and found that Windows10(1709)

and Core i5-8500 (Coffee Lake-S), It appears to be occurring in combination.

Does anyone know how to solve problems with this combination?

※ Attached file is the result of trial.

Hi.

I am using the BCM43341 reference platform and I am running the WICED-3.5.1 SDK.

Unfortunately, whenever I call the wiced_bt_dev_read_rssi(), the callback from the lower layer never returns with a value ...

       static void                   device_ble_rssi_status_callback  ( wiced_bt_dev_rssi_result_t *p_status );

        wiced_result_t            device_read_rssi_status (wiced_bt_device_address_t remote_bda, wiced_bt_transport_t transport, device_dev_cmpl_cback_t *p_cback);

     wiced_result_t device_read_rssi_status (wiced_bt_device_address_t remote_bda, wiced_bt_transport_t transport, device_dev_cmpl_cback_t *p_cback)

     {

              WPRINT_APP_INFO( ("Got request for RSSI status from remote ble client [%02X:%02X:%02X:%02X:%02X:%02X]\n", remote_bda[0], remote_bda[1],      remote_bda[2], remote_bda[3], remote_bda[4], remote_bda[5]) );

              wiced_bt_dev_read_rssi (remote_bda, transport, p_cback);

              return WICED_SUCCESS;

     }

     /*  device RSSI status report handler */

     static void device_ble_rssi_status_callback( wiced_bt_dev_rssi_result_t *p_status )

     {

         if(p_status != NULL) {

             printf("Got RSSI = %d dB\n", ((wiced_bt_dev_rssi_result_t*)p_status)->rssi); 

         }

         return;

     }

       This is called every 10s ...

        /* read RSSI */

        device_read_rssi_status( p_status->bd_addr, p_status->transport, (wiced_bt_dev_cmpl_cback_t *) device_ble_rssi_status_callback );