AIROC™ Bluetooth Forum Discussions
One of My clients asked the suggestion of model for BLE.
They are looking for ble multi connection model.
- One client have to communicate with Mobile and should communicate with more than 10 Server devices.
- They want to design bluetooth light bulb.
- Their reference board is nRF52832.
- Client <-> Server (Both communication)
- Client<-> Client ( No Communication)
- Server <-> Server (No communication)
- --> Server <-> Client <-> Server2(Client arbitrator needed)
Thank you for your help
is it possible to program a CYW20820 MCU using a CYW920819-EVB Development Kit? I had to use the CYW20820 because I wasn't able to purchase the CYW20819 anywhere and now I have troubles programming it.
For better understanding of the chip behaviour:
In which states is the chip before I am writing the first program on it? And for the first flashing process - does the recovery sequence (Holding Pulling down the CTS button while resetting) need to be executed there as well?
Thank you and BR,
IDE: modustool box version 2.4.0
I want to control Pin BT_DEV_WAKE(GPIO36, WICED_P36) as a IO output Pin,
but when I call wiced_sleep_config (TRUE, WICED_WAKE_GPIO_ACTIVE_LOW, WICED_WAKE_GPIO_ACTIVE_LOW); in APPLICATION_START()
the PIO36 is difficult to control output HI, output LO,
I am confuse about is wiced_sleep_config () limited the control of PIO36?
so, I want to set wiced_sleep_config (TRUE, NULL, NULL),
but build project error.
I don't know any step go wrong.
We are developing a product based on the CYBT-343026-01. We've programmed it with the EZ-Serial firmware version 1.2.29 and are testing communication with a host MCU via serial.
The engineer doing the testing reports that when the EZ-Serial firmware is sent the command to enable hardware flow control that the RTS line is activated only when there is a BT/BLE connection. This is the case even when the CYBT is in command mode. This has the effect of stopping command communication with the host MCU.
We can't find release notes for version 1.2.29 of the firmware. The most recent notes cover release 1.2.27 which states that UART CTS is not implemented.
We have a few questions about the EZ-Serial firmware
1. Is there an update in progress that will address hardware handshaking?
2. Are there release notes available for version 1.2.29?
3. Is EZ-Serial for CYBT-343026-01 available in source form so we could make necessary fixes?
Hi, Cypress team
I am working on CYBT-343026 and trying to register hci uart tx callback by modifing wiced_transport_cfg_t transport_cfg :
const wiced_transport_cfg_t transport_cfg =
.type = WICED_TRANSPORT_UART,
.mode = WICED_TRANSPORT_UART_RAW_MODE,
.baud_rate = HCI_UART_DEFAULT_BAUD
.buffer_size = TRANS_UART_BUFFER_SIZE,
.buffer_count = 1
.p_status_handler = NULL,
.p_data_handler = getUartData,
.p_tx_complete_cback = uartTxComplete
But when I call wiced_transport_send_data()
My callback function is never be executed.
What could be the problem?
Hello @DheerajPK_41 ,
I have installed Modus Toolbox v2.4, i want to use CYBT-413034_02. I have successfully installed the IDE, when I create a New application, in project creator I couldn't find CYBT-413034_02 BSP, so I tried to use CYW920719B2Q40EVB-01 and created a RFCOMM project. While downloading, the serial port is not detecting, i tried to put it into recovery mode, still no luck.
I even tried to make a custom BSP, with the help of this link https://community.infineon.com/t5/Knowledge-Base-Articles/ModusToolbox-2-2-and-later-Make-a-Custom-BSP-KBA231373/ta-p/251107
I didn't understood this point, which directory should I select?
Go to the top level of your new application directory where the makefile is located and use the make bsp command.
i change the directory location to this, and change my folder name to TARGET_MyBSP
make bsp TARGET_GEN=MyBSP DEVICE_GEN=CYBT_413034-02
I am getting error as make: *** No rule to make target 'bsp'. Stop.
I am developping an IOT devices based on the cybt-213043-02 modules. For the developpement, I use the cybt-213043-EVAL Mesh kit.
Is-it possible to update the nodes in the mesh network using DFU OTA without using the GATT ? If yes , how ?
The network is composed of provisionner and auto configured nodes.
It doesn't matter if the update is mada node by node or all the network at once.
recently I noticed that during initialization I am getting "WICED_BT_GATT_INVALID_ATTR_LEN" from "wiced_bt_gatt_register" and "wiced_bt_gatt_db_init". I noticed that in the "wiced_bt_cfg_settings_t" the "gatt_cfg" specifies that the MTU should be max_att_len + 5 (/**< Maximum MTU size for GATT connections, should be between 23 and (max_attr_len + 5) */).
I used the throughput example to configure my application - https://github.com/Infineon/mtb-example-btsdk-ble-throughput/blob/master/GATT_server/app_bt_cfg.c
MTU and max attribute length are set to 247 and 244 respectively, considering that the attribute header is supposed to be 3.
Any ideas why the documentation says difference between the two should be 5?
And also if this is the cause for the WICED_BT_GATT_INVALID_ATTR_LEN?
I would like to get startup traces from my application. My current setup is such that PUART is used in connection to other other MCU so I am routing the traces to HCI UART. The obvious problem is that when I program the device I cannot have the HCI port opened therefore I will miss on the startup traces. If I leave the port opened and I reset the device via button it enters recovery mode as the CTS pin is asserted. I have found in this thread https://community.infineon.com/t5/Bluetooth-SDK/CYW20719-HCI-UART-Raw-Mode/td-p/149812 that if I input "n" "w" or "r" into the terminal, it will exit recovery mode and start the application. However this is where the behavior becomes very confusing.
Here's what I do exactly and what output I am getting:
- I close all open HCI UART ports.
- I program the device. (programming complete the device is running)
- I open the HCI UART (eclipse terminal or hterm) and restart the device with a button - it enters recovery mode as CTS is asserted.
- I input "n" "w" or "r" (only one of them) into the terminal. Behavior here is unpredictable.
The application starts running every time ( no matter which letter I send) - that I have verified because phone can connect to the app and I can get traces. However the startup traces are more or less random. Sometimes they appear sometimes not. I have tried almost every combination of reprogramming the device, using different letters, reopening the HCI UART port, resetting the device but I cannot seem to produce a predictable outcome (sometimes the traces are there sometimes not).
Moreover I only get part of the startup traces. My program looks like this:
wiced_transport_init( &transport_cfg );
/* Select Debug UART setting to see debug traces on the appropriate port */
WICED_BT_TRACE("**** App Start **** \n\r");
/* Initialize Stack and Register Management Callback */
if(WICED_BT_SUCCESS != wiced_bt_stack_init(bt_management_callback ,
WICED_BT_TRACE("Bluetooth stack initialization failed!\r\n");
wiced_result_t bt_management_callback( wiced_bt_management_evt_t event,
WICED_BT_TRACE("BT CB event: %d\r\n ", event);
I would expect that the very first trace I would receive is
"**** App Start ****"
However these are the first messages I receive:
BT CB event: 21
BT CB event: 0
I have tried to look into here
for some leads on how to exit the recovery mode with the HCI commands but I found no mention of the "n" "r" or "w" commands (0x6E 0x72 0x77) and I did not figure out if there is another way.
So to recap my main questions:
1) How to exit the recovery mode with the HCI commands and HCI UART still connected so I can get the startup traces?
2) Why it is not showing the startup traces, but only the bluetooth stack traces (which are supposed to run on startup)?
I would also appreciate any other suggestions on how to deal with this.
I'm implementing out of band pairing with the CYBT-413055-EVAL as peripheral and a smartphone as central. During negotiated handover a bidirectional communication is needed to exchange the data. So far I only found tags which implement the NDEF-protocol. I think that this type of tags only allow static handover, where only the peripheral sends OOB-data to the central. Does anybody know which external hardware is recommended to perform this bidirectional exchange and does Infineon provide an additional library for NFC communication?Show Less