Can you point me to any examples for enabling PDS and SDS Sleep for the CYW20179B2 chip for ModusToolBox V2.1 SDK Version 2.7.1?  Or to a comprehensive guide for implementing & verifying specific Sleep use cases?

I am familiar with the 'low power sensor' example that was provided in WICED Studio (6.4) for the CYW20719B1, ...  and this example seems to demonstrate the exact behavior we are looking to enable in our design:

     - Indefinite / Extended Sleep

- Wake from SDS mode with a GPIO signal and wake with a warm-boot option.

I ported the source code for this demo to the Modus ToolBox environment and am able to compile and load it to the B2 EVB, but the behavior is significantly different in that the application seems to wake itself from the Sleep state automatically after ~10 sec and always wakes in a cold-boot state, ... I assume that this reflect some underlying difference in the SDK behavior between the version in WICED Studio and V2.7.1 in ToolBox 2.1?

I have the App note:  "CYW20706_and_CYW20719_Low-Power_Modes.pdf" and have looked at the sleep.h header file, but both of these provide little actual information about how to enable and verify Sleep functionality through the functions and parameters exposed in the API. 

Hi 

I wish to use btsnd_hcic_write_simple_pairing_mode

I used it in wiced studio sdk.

but  I don't use it in ModusBox.  Why don't I use it??

I want to disable to simple pairing.

How can I use btsnd_hcic_write_simple_pairing_mode? 

or Do you have other solution?

Hi,

I would like to enquire information whether BLE (BT 4) is enough for using the MeshClient app or BT 5 is required.

Furthermore, can I communicate with the network in desktop Java or I must use the C++ examples?

Thank you in advance.

After some time not working with the ModusTool box I am not able to transfer a new build  to my board anymore. Say, I am always getting an error message like: "The file does not exist for the external tool named <project name> Program."

I found out that on my existing project the BUILD files are automatically named "EmptyWicedBluetooth..." now and I do not find any preferences to change that.

To verify the problem I created a new (empty BT) application project on target CYBT-413055-EVAL. Build the program and tried to upload to the board: the result was the same:  "The file does not exist for the external tool named <project name> Program."

What is my mistake ?

Achim

I have been facing the problem that spp_scb.flow_control_on never revert back to FALSE on high-load operation.
It occurs in rare cases when receiving and transmitting are performed at same time.
In this case I cannot transmits data any more.

I'd like to get the information about how to fix it or how to poll flow status.

spp_scb.flow_control_on is set in the following callback.
Is there a possibility that the callback vanishes into nothing?

void spp_port_event_cback(wiced_bt_rfcomm_port_event_t event, uint16_t handle){

if(event & PORT_EV_RXCHAR){
<*snip*>
}
if(event & PORT_EV_FC){
spp_scb.flow_control_on = !(event & PORT_EV_FCS) ? WICED_TRUE : WICED_FALSE;
}
if(event & PORT_EV_TXEMPTY){
spp_scb.flow_control_on = WICED_FALSE;
}

spp_scb.event_error = (event & PORT_EV_ERR) ? 1 : 0;

return;
}

For CYW920719B2Q40EVB-01, using ModusToolbox 2.2,

While trying to build the "empty_project", I get a build error that it can not link to the elf file. Build output is attached.

It is not building the elf file for the empty project. I have no idea why or even where to check the specification that it build the elf file.

Full error log attached. Per the help, this should build "out of the box" with no changes and do something simple, but it doesn't. ALL other projects build just fine, this is the ONLY one that doesn't.

>>>

Compiling V:/Software/MedPatch/MedPatchPer/template/empty_wiced_bt/build/CYW920719B2Q40EVB-01/generated/lib_installer.c  -DWICED_BT_TRACE_ENABLE -DWICED_HCI_TRANSPORT_UART=1 -DWICED_HCI_TRANSPORT_SPI=2 -DWICED_HCI_TRANSPORT=1  -DHCI_UART_MAX_BAUD=4000000 -DHCI_UART_DEFAULT_BAUD=3000000 -DSS_LOCATION=0x500000 -DVS_LOCATION=0x501000 -DDS_LOCATION=0x503000 -DDS2_LOCATION=0x582000 -DCYW20719B2=1 -DBCM20719B2=1 -DBCM20719=1 -DCYW20719=1 -DCHIP=20719 -DAPP_CHIP=20719 -DOTA_CHIP=20719 -DCHIP_REV_A_20719B2=1 -DCOMPILER_ARM -DSPAR_APP_SETUP=application_setup -D__TARGET_CPU_CORTEX_M4 -D__ARMCC_VERSION=400677 -DPLATFORM='"CYW920719B2Q40EVB_01"' -DWICED_SDK_MAJOR_VER=2 -DWICED_SDK_MINOR_VER=5 -DWICED_SDK_REV_NUMBER=0 -DWICED_SDK_BUILD_NUMBER=7341 -g3 -DSPAR_CRT_SETUP=spar_crt_setup -DCOMPONENT_SOFTFP -DCOMPONENT_bsp_design_modus -DCOMPONENT_gatt_utils_lib -DCOMPONENT_hidd_lib -I. -I../../../dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus -I../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include/hal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include/internal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include/stack -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/internal/20719B2 -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01 -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/btsdk-include -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/WICED -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/WICED/common -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/arm -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/arm/cmsis -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/hal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/internal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/stack -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/internal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/internal/20719B2 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/arm/cmsis -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/hal -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/internal -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/stack -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/internal/20719B2 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/btsdk-include -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus/GeneratedSource -I./../../../wiced_btsdk/dev-kit/btsdk-include -I./GeneratedSource

    Linking output file EmptyWicedBluetooth.elf

collect2.exe: error: ld returned 1 exit status

make[1]: *** [../../../wiced_btsdk/dev-kit/baselib/20719B2/make/core/build.mk:470: V:/Software/MedPatch/MedPatchPer/template/empty_wiced_bt/build/CYW920719B2Q40EVB-01/Debug/EmptyWicedBluetooth.elf] Error 1

make: *** [../../../wiced_btsdk/dev-kit/baselib/20719B2/make/core/main.mk:350: secondstage] Error 2

"C:/ModusToolbox/tools_2.2/modus-shell/bin/make CY_MAKE_IDE=eclipse CY_MAKE_IDE_VERSION=2.2 CY_IDE_TOOLS_DIR=C:/ModusToolbox/tools_2.2 -j8 all" terminated with exit code 2. Build might be incomplete.

hi there,

im a newbie at Modus Toolbox, cypress project structures and Bluetooth SDK.

I have to evaluate the Bluetooth Mesh functionality and the SDK of your product. I use 2 CYBT-213043-MESH kits to get an overview.

I download the Mesh_Demp_Smart_Light & Smart_Switch project examples to understand the server & client functionality of the mesh network. I followed all the instructions given by the readme.md at the "smart switch" project, and in general i can see the motion status at the trace of the windows MeshClient tool. But i cant see any trace if i press one of the "user-buttons" of the 2 kits. Of cource the LED is switched on at the smart light app kit, if i press its button, but no trace about any message transfer to smart switch app kit and vice versa.

1. am i wrong with my expectations? Or do i have to change some configurations?

2. How can i activate the trace output of the "smart switch" project? I changed the makefile MESH_MODELS_DEBUG_TRACES ?= 1 & MESH_CORE_DEBUG_TRACES ?= 1 but no output at PUART. I use HTerm with 115200 Baud 8N1. What else do i have to connect / set (jumper)? or configure? I use the USB connector of the board, is this correct?!

Thanks for your help

Nicolai

Hi,

I am really struggling to get i2s microphone to stream to a2dp,

I've looked everywhere including watch example to try get this to work but to no avail. 

I am using a board CYW20706 and have a microphone connected to it via i2s (it is a 24bit microphone). 

Do the gpio pins need to be set? or am I missing a library such as CYW9BT_audio in the watch example for this to work? 

I have configured the board as the i2s slave and a2dp source and the microphone as the master using wiced_audio_start();

Is there anything else I can try to make this work? 

I've looked a this link too and tried other boards such as 20719 and 20819, all seem to not work.

https://community.cypress.com/t5/Resource-Library/PCM-I2S-Clock-setting-in-CYW20706/ta-p/246335?emcs_t=S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEtLMjVFQUVGVEFDTUdBfDI2MzUwNXxTVUJTQ1JJUFRJT05TfGhL

At this point, any help would be greatly appreciated. I've been stuck with this problem for the last 2months 😞 

Thankyou so much in advance!

Hello Support,

I have problem with control of Cypress module. When I am trying to run A2DP profile by play YT music on paired phone it periodical change state player play-pause-play-pause-... on my phone.

I tried to debug where is the case and i found this #define function

#define GKI_send_msg(a,b,p_msg) wiced_bt_a2dp_sink_hdl_event((BT_HDR *)p_msg)

It is in library storage, and i dont think so that i should modify anything in here.

debug1 - screen from terminal to check where is the problem. When module going to play<>pause state UART debug stuck.

debug2 - code fragment with last used function.

When module start wiced_bt_a2dp_sink_send_start_response function everyting stuck.

Have you case like that with this module?

Best Regards

Piotr

hi,

we want to do the PIN pairing with mobile application on 423054.

we couldn't find any example code for pin based pairing, so we are facing difficulty to do the same.

PIN will be fixed and if user wants they can change and we have no user interface whatsoever, hence the need for each device to have the same PIN.

Thanks & Regards

Rahul