AIROC™ Bluetooth Forum Discussions
I have a project that is based off DFU_BLE_Upgradable_Stack (CE220960), and I have made a few adjustments to make the the projects to work with PDL v3.1.5. I am having a lot of weird issues with BLE, so I am trying to understand everything going on in the example to see if there is anything else needed to change. Are all the function referenced in the BLE_coreX_shared.s file generated by the post build .bat script in App1 supposed to be 1 byte off from their addresses defined in the .map file?Show Less
ネクスティ 渋谷Show Less
Tôi đang xây dựng một dự án sử dụng PSoC 63 BLE và Modustoolbox để đọc dữ liệu từ các cảm biến và sử dụng Bluetooth để truyền dữ liệu qua một ứng dụng Android riêng biệt mà không cần sử dụng CySmart và điều khiển thiết bị.
Tôi phải làm nó như thế nào?
Hy vọng bạn có thể giúp đỡ!
Cảm ơn bạn!
I can't reply to the thread below, so I'm creating a new question.
Am I correct in understanding that if the firmware hangs, there is no way to know and initialize the LSI?
I am working with the 202007 BLE module and I have an external antenna connected to the uconnector and am receiving signal strength of -80dBm to -90dBm. I have done nothing to modify this device. Had anyone else had this issue?
I am looking for an alternative to a Bluetooth module (PN: BT121 @ Silicon Labs).
Our Requirements are:
1. It should support both BLE and Bluetooth Classic.
Kindly suggest to us if any part is available in Infineon.Show Less
For our product under development, we need to implement some basic tests commands, and I've been able to implement the Set_Tx_Carrier_Frequency_ARM Cypress Vendor Specific HCI Command (as per described in "BLUETOOTH RADIO TEST CASES AND PROVISIONING HCI COMMANDS" documentation from infineon/cypress).
I call this command from the embedded application in the CYBT-483056-02 CPU using wiced_bt_dev_vendor_specific_command API call. I've observed that the command was running fine only if there's no call to wiced_bt_dev_set_connectability or wiced_bt_dev_set_discoverability commands with page_mode different from BTM_NON_CONNECTABLE and/or inq_mode different from BTM_NON_DISCOVERABLE. I mean that if I call one of this function to enable discoverability or connectability, then the test command will not work (there's no TX on the antenna in this case). I've also tried to reset the discoverability and connectability to BTM_NON_CONNECTABLE and BTM_NON_DISCOVERABLE before sending the hci test command, but it do not work. We need to reset the device before being able to issue the test mode hci command.
Also, the call to wiced_bt_dev_vendor_specific_command will not return an error when the TX is not working (after discoverability or connectability) so there's no way for us to warn the test tool that something is wrong with the configuration...
Can you help us by looking at the ROM code to find out what can cause the problem and maybe find a workaround ?
The HCI code that I send is OGF:0x3F, OCF:0x0014, which result in opcode 0xfc14.
Also, I can reproduce the same behavior in the following cases :
* On the eval board with modificed empty wiced app (only call the two functions wiced_bt_dev_set_connectability and wiced_bt_dev_set_discoverability to enable discoverability and connectability, the send the test command using wiced_bt_dev_vendor_specific_command call)
* By using the empty wiced app without modification and using CyBluetool to drive the eval board through HCI commands and agian, setting discoverability on or connectability on then sending the test command...
All this indicate that it's not related to our software, but rather to some ROM code behavior that might be normal, but is not described in the documentation, and for which we would like to find a workaround.
Regards, JeromeShow Less
We are experiencing unexpected reboot of a CYBT-483056-02 module used on a CYBT-403056-EVAL board under some circumstance (two connection created). We have no clue of what is happening, and during the research for debugging options, I came accross this topic (https://community.infineon.com/t5/Resource-Library/CYW20719-and-CYW20735-Clocks-RTC-WatchDog-Timer-Application-Timer-and-PWM/ta-p/246352) where it's stated that when the device crash, there's a core dump output on the HCI Uart.
Indeed, looking at the data output on HCI Uart, I can see strings that belong to the firmware (version string and also some libraries strings). The HCI format seems to start with a pattern (0x04 0xFF 0xF4 0x1B 0x03), followed by what seems to be a memory address. Unfortunately I couldn't find any document that describe the HCI vendor command for this, and BT-Spy do not seem to identify that this is a core dump (simply print some weird chars).
Can you please help me converting the core-dump to an file that I can examine with GDB ? We already played with many parameters to find the issue.
Also, I found out that using the wiced_bt_printf API will corrupt the traces send on HCI-uart for debug (I used this API to format some strings that we use for our software usage, and found that this was generating some partial repetitions on the traces send to wiced_bt_trace). I've used a custom printf/snprintf implementation and the problem is solved.
Regards, JeromeShow Less
Because of the standard Serial Port Profile (SPP) is not supported by BLE, i need to create a BLE custom service to be able to send/receive UART data over Bluetooth. I want to transfer uart data over bluetooth(psoc6 to PC Serial Comport). Is there a reference project to do so.
I'm using PSoC 62 with LBEE5KL1DX (with CY4343W). The advertisement name comes from the Bluetooth Configurator's GAP settings. But because we will be having multiple devices with the same firmware, I'd like to change the advertisement name based on the MAC address or something unique dynamically during run-time.
I can get the MAC id of the device using wiced_bt_dev_read_local_addr(). The advertisement name seems to be coming from wiced_bt_cfg_settings.device_name. When I call the wiced_bt_dev_read_local_addr() before I do the wiced_bt_stack_init(), the wiced_bt_dev_read_local_addr() function hangs; but when I call it after the stack init function, its OK, but it looks like it is too late to set the device name after the stack init is called.
Can someone suggest a proper way to change the advertisement name on startup instead of using the static name that comes from the gap settings page of the bluetooth configurator?
Appreciate any advice/suggestions you can provide.Show Less