Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
As you have correctly pointed out that the changes are not being correctly linked against the pre-compiled libraries (which is expecting the baud rate to be 115200) and also with the BT firmware which is by default compiled for 115200 baud rate (location for the firmware: 43xxx_Wi-Fi/libraries/drivers/bluetooth/firmware/43438A1/37_4MHz/bt_firmware_controller.c). Please mention the use-case for the higher baud-rate and also mention a stripped down version of our application for us to easily reproduce the issue.
I am using a modified version of ble_hello_client.
The modifications I have made connect to a Nordic PCA10040 running a ATT_MEU throughput example [via device name filtering].
In this example the Nordic device advertises as a connectable peripheral. There is a characteristic that, when notifications are enabled, spams notifications to the conneced central (My CY8CKIT-062) to get a throughput test.
I'm able to achieve 370kbps with my telephone, and around 250kbps with my PC.
Through connection interval tuning, I'm able to achieve a maximum of 72kbps on the Cypress CY8CKIT-062. I believe I am being limited by the UART HCI link.