AIROC™ Bluetooth

Hello all,

while out-of-band pairing procedure it is necessary to call the function wiced_bool_t wiced_bt_smp_create_local_sc_oob_data (wiced_bt_device_address_t bd_addr, wiced_bt_ble_address_type_t bd_addr_type) to create local BLE secure connections OOB data. In the documentation it is described, that OOB data will be provided via the BTM_SMP_SC_LOCAL_OOB_DATA_NOTIFICATION_EVT event, but in my case this event is not fired. The return value of the function is FALSE too. Does anybody know what to do to get the OOB data from this function? 

We are submitting an application for the Indian Radio Certification.
We have submitted a radio test report for the radio module EN, and the following statement is on the first page of this test report.
This report must not be used to claim product endorsement by CNAS, TAF or [any agency of the government].

We have negotiated several times to accept the current test report, but they have not listened to us and have requested that we revise the test report.
Therefore, we have been told that the above sentence needs to be deleted or a portion of the sentence needs to be revised.
Could you please confirm if the report does not contain such a statement or if it is possible to modify it?

The required standards are as follows
EN300328-1
EN301489-1
EN301489-17

Translated with www.DeepL.com/Translator (free version)

Hi,

I have an issue such that when I play audio via A2DP or have an open SCO connection the HCI UART interface stops working.

When I stop the audio stream the HCI interface resumes operation.

BR,

Oskar

Hello,

I'd like to ask for opinion/advise on several issues. I will give you the context first:

I am developing an application using the CYW20719B2 in Modustoolbox as officially suggested by Infineon. I am looking into doing a test production series, thus I will need at least several dozens of the MCUs. Unfortunately I cannot find any supply of this chip anywhere nor any expected date of new stock.. However I can see that CYW20719B1 MCUs have still quite high stock availability. Therefore I am considering using the CYW20719B1 in the meantime and then go with the CYW20719B2 when available. I understand that CYW20719B1 is not supported in Modustoolbox and is only supported in WICED Studio. Based on this I would like to ask the following:

1) Is there any official/unofficial way to add the CYW20719B1 target into the Modustoolbox? If so could you please give me some leads where to begin?

2) Is there a way to port the application from Modustoolbox back to WICED studio? Especially how to go about the generated files (COMPONENT_btstack..)?

3) By any chance is there somewhere some available stock of CYW20719B2 MCUs that I am not aware of? Or at least does anyone know about when we can expect CYW20719B2 to be available?

I understand that official advise is not to go back to CYW20719B1, however I do not see any better solution at this time. If you can give me any other advise that I missed on how to go about the current situation I would be very grateful.

Thank you.