AIROC™ Bluetooth Forum Discussions

Hi,

Could someone possibly tell me what would happen to the currently valid CMIIT ID?

It seems to expire in september this year.

Provided that the certification gets updated, will the ID remain the same even after trasition from Cypress to Infineon?

Hi

iam using CYW920721M2EVK-02' with cybt413061 module ,using hfp example code when i connect android/IOS device

when i receive a whatsapp call am receiving an incoming call event ,as i want to modify that i don't want to send any events like incoming or outgoing events . i want to send events only during normal call.

thanks and regards

chandruu 

Hello,

I have designed a custom board with cyble-022001-00 module. I want to program a bootloader project to cyble-022001-00 so that the firmware of cyble-022001-00 can be upgraded over the air.

I see some bootloader examples. However, these examples require that the cyble-022001-00 module is interfaced with a switch which the user need to press for bootloading a new firmware.

My question,

Is there a bootloader example project for cyble-022001-00 that allows cyble-022001-00 firmware to be upgraded over the air without the user requiring to press any switch connected to cyble-022001-00.

I am trying to make an application to be scanning and at the same time save as much energy as possible for a bluetooth device type 2. So that the device stays on as long as possible with low power consumption but still receiving packets through the scanner. could you give me information on an example that covers this topic or where to find information on this, thanks.

We are using the CYBT-343026-01 module in a number of our products. We are able to upgrade the firmware in our products by via a customer software update but so far it does not update the Bluetooth module. We would now like to extend this to also upgrade the Bluetooth module. 

The module is connected to the host via the 2 UARTs as well as GPIOs controlling power and the recovery line (SPI2-MOSI). There is a procedure given in the following link but that uses your Chipload.exe program. In our case we need to drive the UART in our embedded application, i.e. we need to write our own chipload program. Please send me the documentation/example code for the flashing procedure in recovery mode.

https://community.infineon.com/t5/Knowledge-Base-Articles/Programming-an-EZ-BT-WICED-Module-KBA223428/ta-p/254274

We are using CYW920721 chip in our product and we are using the audio watch application as our base, we wanted to find device currently bonded to our device, we found an API wiced_bt_dev_get_bonded_devices always returns unsupported. I wonder how do we find the peer device bonded ?

Hi all,

I'm trying to store the bonding information in a DFU OTA project. To clarify, I'm trying to store the bond information when App1 is connected, not App0. That is, once the firmware is updated over-the-air, and the Bootloader hands over control to App1, and I connect a central device (a phone) to App1, I would like to store the bonding info. I'm using:

#if(CY_BLE_BONDING_REQUIREMENT == CY_BLE_BONDING_YES)
        /* Store bonding data to flash only when all debug information has been sent */    
        if(cy_ble_pendingFlashWrite != 0u) 
        {   
            apiResult = Cy_BLE_StoreBondingData();    
            DEBUG_PRINT("Store bonding data, status: %x, pending: %x \r\n", apiResult, cy_ble_pendingFlashWrite);
        }
    #endif /* CY_BLE_BONDING_REQUIREMENT == CY_BLE_BONDING_YES */

 
However, I get the following output:

Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
Store bonding data, status: 140001, pending: 3
.
.
.
.
Store bonding data, status: 140001, pending: 3

 I continuously get CY_BLE_INFO_FLASH_WRITE_IN_PROGRESS (140001) without it ever succeeding to store the bond information. After trying for a while, the connection drops.

It should be noted that I created a separate project and I ported only App1 to it, and the code works fine. So it must have something to do with the fact that the Bootloader (App0) is also present.

Do you guys have any insight into what's going wrong and how to fix it?

Best,

Ricky

Does the CYBT-413061-02 module will support pairing with multiple devices simultaneously?

If it is possible, please provide some examples for how to store multiple paired device parameters in NVRAM.

What is the maximum number of devices can pair with this module ?

It's happening when we tried to connect with new device without unpair the old device.(Again that old paired device is not getting connected)

in sfi.h