The bluetooth low energy stack calls connection down with a reason of timeout (HCI_ERR_CONNECTION_TOUT) after around 40 seconds to its starting communication. I wonder why it happens and how I disable the timeout.

The callstack when it stops at the breakpoint of connection down would be helpful. The used BTE library was from the old SDK (3.3.1) and the name is "BTE.FreeRTOS.LwIP.ARM_CM4.release.a", size of 1,231,264 bytes.

(gdb) bt
#0 ble_config_gatts_connection_down (p_status=0x2001e7b8)
at ../../third_party/connectedhomeip/src/platform/WI2/wi2_bluetooth.c:534
#1 0x080c217e in ble_config_gatts_conn_status_cb (p_status=0x2001e7b8)
at ../../third_party/connectedhomeip/src/platform/WI2/wi2_bluetooth.c:556
#2 0x080c2336 in ble_config_gatts_callback (event=GATT_CONNECTION_STATUS_EVT, p_data=0x2001e7b8)
at ../../third_party/connectedhomeip/src/platform/WI2/wi2_bluetooth.c:696
#3 0x080d459c in gatt_cleanup_upon_disc ()
#4 0x080d169e in l2cu_process_fixed_disc_cback ()
#5 0x080d18fa in l2cu_release_lcb ()
#6 0x080cf3d6 in l2c_link_hci_disc_comp ()
#7 0x080cc5e2 in btu_hcif_process_event ()
#8 0x080cd048 in btu_task ()
#9 0x08024de8 in pxPortInitialiseStack (pxTopOfStack=0xa5a5a5a5, pxCode=0xa5a5a5a5, pvParameters=0xa5a5a5a5)
at ../../third_party/connectedhomeip/third_party/wiced_sdk/repo/WICED/RTOS/FreeRTOS/ver9.0.0/Source/portable/GCC/ARM_CM3/port.c:231

Hi,

We are trying to check the connection stability of Bluetooth. 

We checked the bluetooth connection with the firmware which was provided by default. We are not sure about the firmware version but there was no connection instability. The default MAC Address was AA:AA:AA:AA:AA:AA.

Then after flashing the new firmware (minidriver.bin, firmware.bin, bt_fw_download) the MAC address got changed to 20:81:9A:1F:4F:50. But after this firmware flash we are facing disconnection issue. The testing procedure is provided below:

1) Enabling the Bluetooth by executing ble.sh. The script file has been attached below.

2) Running the bluetooth.service. 

3) Executing bluetoothctl commands for establishing the Bluetooth connection and the commands are as below:

  :scan on

  : scan off

  : pair<MAC-ADDRESS>

  : connect<MAC-ADDRESS>

5) After following these steps Bluetooth connection is established but within few seconds there is a disconnection. This scenario is not observed when we tested with the default firmware. Please find the below attachment

Regards,

Akshay Naik 

Hi，there：

We are now using CYBT_343026_EVAL which is CYW20706 inside working as a Bluetooth Controller。Our custom board works as a Bluetooth Host。

We noticed that SCO Offload - voice data routing over I2S/PCM interface supported （WICED Bluetooth Software Features - Cypress Developer Community）

Is there any guide or sample to about enable offload mode in our case？

Hello,

I am trying to connect microcontroller  CYW89820 in SPP mode to HC-05 in master role.

I can see in HC-05 the address and device name of CYW89820. But when HC-05 is trying to connect (by bind command AT+BIND=2081,9A,156668), i just get the message from cypress "Pairing Complete: 5app_management_callback 3remote address = 98 d3 b1 fd 8a 86 app_management_callback 11Pairing Complete: 5". I am using the RFCOMM_Serial_Port demo program.

the Error 5 is comming from p_pairing_info-> br_edr.status, can you explain what is this number.

thanks

Hi,

I am trying to use the NVRAM or EFLASH and have run into to some odd behavior on my CYW20719 board

 On Eflash - if I pick a page offset , say 100 and then write to the page, then read from the page , then write again all the values come back as 0 -- 

If I try to issue an erase - I get an 0x28 error which is the generic WICED_BT_ERASE

Can someone point me to an example of how to use eflash properly? (Code snippet below)

I also see that there is a note that a Sector is 512, but there is 1 meg of memory to use, and pages are 4096bytes and there are 256 pages?

For NVRAM - how much usable memory is there actually to use, the SDK pages seem to say 3 megs, but then I see quotes on 4k only - and then NVRAM can be overrun by SRAM?  Can someone point me to the addressable area that I can actually use and won't be impacted by other SRAM or areas?

writeDriverDataFlash(tbuf, 512, 0);

WICED_BT_TRACE("Test before %d %d %d %d %d \n\r", tbuf[0], tbuf[1],
tbuf[2], tbuf[3], tbuf[4]);
memset(tbuf, 0, 1280);
readDriverDataFlash(tbuf, 512, 0);

WICED_BT_TRACE("Test after %d %d %d %d %d \n\r", tbuf[0], tbuf[1],
tbuf[2], tbuf[3], tbuf[4]);

writeDriverDataFlash(tbuf, 512, 2);

memset(tbuf, 6, 1280);
WICED_BT_TRACE("Test before %d %d %d %d %d \n\r", tbuf[0], tbuf[1],
tbuf[2], tbuf[3], tbuf[4]);
//readDriverDataFlash(tbuf, 1280, 0);

writeDriverDataFlash(tbuf, 512, 0);

memset(tbuf, 2, 1280);
readDriverDataFlash(tbuf, 512, 0);
WICED_BT_TRACE("Test after %d %d %d %d %d \n\r", tbuf[0], tbuf[1],
tbuf[2], tbuf[3], tbuf[4]);

int writeDriverDataFlash(uint8_t *data, uint16_t size, uint8_t off) {

wiced_result_t result;
if (size <= 4096) {
result = wiced_hal_eflash_erase(eflashstart + off, 512);
WICED_BT_TRACE("Erase 0x%02x\n\r",result);
result = wiced_hal_eflash_write(eflashstart + off, data, size);
if (result == WICED_BT_SUCCESS) {
WICED_BT_TRACE("Sucess in writing\n\r");
return 1;
}
}

return 0;

}

int readDriverDataFlash(uint8_t *data, uint16_t size, uint8_t off) {
wiced_result_t result;
if (size <= 4096) {
result = wiced_hal_eflash_read(eflashstart + off, data, size);
if (result == WICED_BT_SUCCESS) {
WICED_BT_TRACE("Sucess in Reading\n\r");
return 1;
}
}

return 0;
}

We have used CWY920719 device on a custom board with additional peripherals such as a NAND Flash Module, and an NTAG module.  We can successfully download our hex file to the board using Cypress Programmer version 4.0.0. Also, we can verify the device successfully using the 'Verify' button on Cypress Programmer tool bar. After that, we expect that our code runs on the device. But we have no indication that our code is running: we do not see the traces come out on PUART console. Even after a power on reset, we see nothing come out.

a. Is there some setting we have to enable in our code or in makefile to cause our board to run the code from on-chip flash on CWY920719 device?

b. The Cypress Programmer shows the launch address as 0x00000000 in the parameter for ChipLoad.exe command. E.g.,

    ChipLoad.exe -BLUETOOLMODE -PORT COM4 -LAUNCHADDRESS 0x00000000 -BAUDRATE 115200 ....

Does this value have to be different for our custom board? If yes, how do I know what it has to be?

We have prototyped using the CYW920719Q40EVB_01 board. We are able to run the same code just fine on this Evaluation board. We have been able to hook up our additional peripherals to the Evaluation board, and again  our code with all the same peripherals run just fine on the Evaluation board.

Thanks in advance for your reply. We are eagerly waiting for an answer.

Best regards,

PK

Hello,
I have a question about CYW920819EVB-02.

This development board has a start guide and a user guide here.
https://www.cypress.com/documentation/development-kitsboards/cyw920819evb-02-evaluation-kit

Is there another document containing a description of the registers on this development board?

Regards,
Sugino