ModusToolbox Bluetooth SDK

Dear all,

I have a CYW920721B2 Evaluation Board and want to run the Audio_Headset_and_Speaker Example on ModusToolbox IDE,

The point is that i want to extend the MTU size of BLE connection to 247 (Default is 23 byte). I've read some answers on Cypress forum and they recommend to edit "gatt_cfg.max_mtu_size" and also call wiced_bt_gatt_configure_mtu() API when the BLE connection is established to reconfig the MTU size.

I changed gatt_cfg.max_mtu_size to 247 and call wiced_bt_gatt_configure_mtu(p_status->conn_id, 247) inside hci_control_le_connection_up() but it always return 0x80 (WICED_BT_GATT_NO_RESOURCES).

I really appreciate if any one could help me to config the MTU size correctly.

Hi Cypress,

I have some questions and need to your confirm.

Q1) As I know, wiced_bt_dev_delete_bonded_device() API is used to remove bonding information. But I am not sure if wiced_delete_key_info_from_ram() API should be also used. As my test results, it seems that bonding information is also removed from ram by using wiced_bt_dev_delete_bonded_device() only. Right?

Q2) If possible, could you let me know the difference between these APIs?

Thanks,

Liam

Hello @DheerajPK_41 

I had posted a questions a few months back here: https://community.cypress.com/t5/ModusToolbox-Bluetooth-SDK/Device-wake-gpio-and-gpio-irq-with-the-same-pin-for-cyw20719b2/m-p/267341

In that post you posted a answer saying if host is not in connection and want device to go to sleep we should select WICED_SLEEP_MODE_NO_TRANSPORT as sleep mode.

So, I just wanted to clarify, We are having a standalone application and host wake pin is not connected to anything. So we have to use WICED_SLEEP_MODE_NO_TRANSPORT as sleep mode or is it possible to use WICED_SLEEP_MODE_TRANSPORT as sleep mode even though host is not in the picture ? If yes can you point out to any example with such scenario ?

Thanks,

Aniket Jesu

Hello all,

I have the CYBT-213043-MESH kit, and I have the CY8CKIT-005 MiniProg4 Program and debug kit. 

I have connected the debugger (SWDIO pin) to the mesh kit (SWDCK pin) while both connected to my Mac.

I have set the ENABLE_DEBUG?=1 in the appropriate makefile of the application I wish to download onto the board. 

My problem is that when I try to launch the debug, I get this error:

Started by GNU MCU Eclipse

Started by GNU MCU Eclipse

Open On-Chip Debugger 0.10.0+dev-4.2.0.1430 (2021-03-05-16:23)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

adapter speed: 10000 kHz

Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.

cortex_m reset_config sysresetreq

force hard breakpoints

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : CMSIS-DAP: SWD  Supported

Info : CMSIS-DAP: JTAG Supported

Info : CMSIS-DAP: FW Version = 2.0.0

Info : CMSIS-DAP: Interface Initialised (SWD)

Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1

Info : CMSIS-DAP: Interface ready

Info : KitProg3: FW version: 2.21.1005

Info : KitProg3: Pipelined transfers enabled

Info : VTarget = 0.000 V

Info : High speed (adapter speed 10000) may be limited by adapter firmware.

Info : clock speed 10000 kHz

Error: DAP 'CYW20819A1.cpu' initialization failed (check connection, power, transport, DAP is enabled etc.)

Info : CYW20819A1.dap: powering down debug domain...

Warn : Failed to power down Debug Domains

I would appreciate the help on how to proceed!

Thanks

Hello,

I am trying to build a Debug environment using MiniProg4 on CYBT-343026-EVAL and CYBT-353027-EVAL.

The "README.md" included in the Modus sample design has the following description.

------------------------------------

CYBT-343026-EVAL/CYBT-353027-EVAL: SWD signals are routed to P11=SWDCK and P15=SWDIO. Use expansion connectors to connect VDD, GND, SWDCK, and SWDIO to your SWD Debugger probe.

------------------------------------

However, I don't think that pin is assigned in each Module.

[CYBT-343026-EVAL]

 - SWDCK=P11 : Pad 23 (GPIO_6)

 - SWDIO=P15 : There is no Pad

[CYBT-353027-EVAL]

 - SWDCK=P11 : There is no Pad

 - SWDIO=P15 : There is no Pad

I think I need to re-specify the pins for each SWD pin.

I checked the following files and thought that each SWD pin could be assigned.

------------------------------------

mtb_shared\wiced_btsdk\dev-kit\baselib\20706A2\release-v3.0.0\COMPONENT_20706A2\WICED\common\wiced_swd_interface.h

------------------------------------

[CYBT-343026-EVAL]

 - SWDCK=P11 : Pad 23 (GPIO_6)

 - SWDIO=P12 : Pad 04 (I2C_SDA)

[CYBT-353027-EVAL]

 - SWDCK=UART_TXD : Pad 10 (UART_TXD)

 - SWDIO=UART_RXD : Pad 12 (UART_RXD)

I modified the following make file to reflect the modified settings above.

------------------------------------

[CYBT-343026-EVAL]

mtb_shared\wiced_btsdk\dev-kit\bsp\TARGET_CYBT-343026-EVAL\release-v3.1.0\CYBT-343026-EVAL.mk

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ifeq ($(ENABLE_DEBUG),1)

CY_CORE_DEFINES+=-DSWD_CLK=SWDCK_ON_P11

#CY_CORE_DEFINES+=-DSWD_IO=SWDIO_ON_P15

CY_CORE_DEFINES+=-DSWD_IO=SWDIO_ON_P12

endif

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[CYBT-353027-EVAL]

mtb_shared\wiced_btsdk\dev-kit\bsp\TARGET_CYBT-353027-EVAL\release-v3.1.0\CYBT-353027-EVAL.mk

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ifeq ($(ENABLE_DEBUG),1)

#CY_CORE_DEFINES+=-DSWD_CLK=SWDCK_ON_P11

CY_CORE_DEFINES+=-DSWD_CLK=SWDCK_ON_UART_TXD

#CY_CORE_DEFINES+=-DSWD_IO=SWDIO_ON_P15

CY_CORE_DEFINES+=-DSWD_IO=SWDIO_ON_UART_RXD

endif

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

------------------------------------

When I tried the above, I was able to connect with [CYBT-343026-EVAL].

However, [CYBT-353027-EVAL] cannot connect and the FW cannot be reprogrammed.

I have a question based on the above.

Q1.

Since the debugger was able to connect with [CYBT-343026-EVAL], I think that this method is good for changing the pin assignment.

Is that recognition?

Q2.

Is the phenomenon that [CYBT-353027-EVAL] cannot be connected and cannot be reprogrammed due to the use of HCI_UART?

In that case, is there a way to debug with [CYBT-353027-EVAL]?

Best regards,

TK

Test case:
1. the keys of the previously paired headset have been deleted from memory
2. when turning on the headset, I get only the BTM_PAIRED_DEVICE_LINK_KEYS_REQUEST_EVT event

How do I connect the headset knowing only the address of the headset?

Hi

I'm trying to implement HIDOFF using GPIO.
It worked fine with WICED Studio 6.x.
However, it does not work well with ModusTollbox2.3 + BT SDK (3.0 / 3.1).
In the case of Modus, 20706 go to HIDOFF, but it wakes up after 5 seconds without GPIO operation.

For Example

wiced_hal_gpio_register_pin_for_interrupt( WICED_GPIO_BUTTON, NULL, NULL );
wiced_hal_gpio_configure_pin( WICED_GPIO_BUTTON,WICED_GPIO_BUTTON_SETTINGS(GPIO_EN_INT_FALLING_EDGE), WICED_GPIO_BUTTON_DEFAULT_STATE );
wiced_power_save_start(WICED_WAKE_SOURCE_GPIO, 0);

Please tell me the correct setting of HIDOFF for ModusToolbox/BTSDK.

I am testing with the CYBT-343026-EVAL01 board. GPIO uses P0.

Best Regards,

Hello all,

I have the CYBT-213043-MESH kit, and I have the CY8CKIT-005 MiniProg4 Program and debug kit. 

I have connected the debugger (SWDIO pin) to the mesh kit (SWDCK pin) while both connected to my Mac.

I have set the ENABLE_DEBUG?=1 in the appropriate makefile of the application I wish to download onto the board. 

My problem is that when I try to launch the debug, I get this error:

* KitProg firmware is out of date, please update to the latest version (2.21.1005)

* using fw-loader tool which can be found in the following folder

* /Applications/ModusToolbox/tools_2.3/fw-loader

I believe that I need to run this commands below, but I am not sure where the appropriate command line is. And if on terminal, which directory do I need to be in for this to work?

[install_path]/fw-loader/bin/fw-loader

--update-kp3 CY8CKIT-005