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?Show Less
I tried to use Bluetooth_LE_Battery_Server on EVB CY8CKIT-062S2-43012.
But I got error message as below and entire log in attached file.
** Program operation completed successfully **
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Info : SWD DPIDR 0x6ba02477
Error: psoc6.cpu.cm4 -- clearing lockup after double fault
psoc6.cpu.cm4 halted due to debug-request, current mode: Handler HardFault
xPSR: 0x20000003 pc: 0xe000ed00 msp: 0x080ff7e4
Error executing event reset-deassert-post on target psoc6.cpu.cm4:
in procedure 'ocd_process_reset'
in procedure 'ocd_process_reset_inner' called at file "embedded:startup.tcl", line 788
in procedure 'mxs40_reset_deassert_post' called at file "C:/Infineon/Tools/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/psoc6_common.cfg", line 169
at file "C:/Infineon/Tools/ModusToolbox/tools_2.4/openocd/bin/../scripts/target/mxs40/mxs40_common.cfg", line 116
Info : SWD DPIDR 0x6ba02477
psoc6.cpu.cm0 halted due to undefined, current mode: Handler External Interrupt(456)
xPSR: 0x08001fd8 pc: 0x08001fd8 msp: 0x08001fd8
shutdown command invoked
Info : psoc6.dap: powering down debug domain...
I also tried the solution from below link. But It didn't work for me. Any comment to fix this kind of issue???
My ModusToolbox version is 2.4 and with below configuration
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
Translated with www.DeepL.com/Translator (free version)Show Less
I'm using CYW20706,and then download the latest version of Wiced Studio 6.6. But the WICED Platform menu don't have the information about CYW20706.What should I do instead？Show Less
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.
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.Show Less
I want to build a sample application named 'Audio_Headset_and_speaker'
But I failed to build in CYBT-343026-01
I imported Audio_Headset_and_Speaker application and changed some code for adapting CYBT-343026-01 module, for example makefile and library files.
But I failed to build.
I'd like to know whether it can be built in CYBT-340326 succeedingly.
Daniel LimShow Less
What is the first device that supports LE-LR (Coded PHY) as Infineon? Will it be the CYW20829?
Are there any plans for a CYBT module with CYW20829?
What is the MP schedule for each IC and module of the earliest device?
Best Regards,Show Less
I am using the ssp multiport application... I connect my smartphone with the app and I send messages from my smartphone to the client control and they are displayed in BTSpy... how can I modify the sample code to replace BTSpy with Termite 3.4 and it display the PUART port data???Show Less
When I checked the data sheet of CYBLE-014008-00, I could not confirm the MIC mark.
Is the MIC mark displayed on the actual Module?
My perception is that the MIC mark must be displayed on the Module board or shield.
Is this recognition correct?
For example, if the MIC mark cannot be displayed on the Module, is it acceptable if the MIC mark is included in the data sheet (instruction manual)?
I also believe that displaying this mark on the customer's end product is voluntary and not obligatory.
Is this recognition correct?
Let me confirm the meaning of this sentence on the data sheet.
"End product can display the certification label of the embedded module."