大佬们好!
请问怎样将CYW20706模块 PUART的TX和RX管脚配置为内部上拉或下拉?上拉与下拉在功能上的区别有哪些?
Hello,
We are developing CYBT-483056-02 with MTB2.2.
On CYBT-483039-02 with CYW20719B1, it was necessary to add the following settings in WICED.
Do I need to make similar settings when developing CYBT-483056-02 with MTB?
Should I set the output setting of CYW20719B2 to -2dBm (because PA / LNA is 22dBm) in order to obtain POUT of 20dBm?
Best regards,
TK
Show Less
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.
I compared the empty project to the "Hello_senor" project. Makefile, and all settings look similar (save directory changes).
Show Less
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.
Show Lesshi 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
Show LessHi,
I have a microphone connected to my CYW920819 board via i2s.
Unfortunately I am unable to get it to stream to my bt headphones via a2dp (is it even possible?)
I am using the watch example for this board and followed the blog below to route i2s.
Could it be a codec issue/sampling rate issue?
Any help would be greatly appreciated.
Thanks in advance!
Show LessDear Sir,
Please provide the latest data sheet for BT, as below image they are not link to latest data sheet,
for example: CYW20706 support BT5.2 but the data sheet shows BT4.2.
Could you please help to provide the latest data sheet for CYW20706/CYW20719B2/CYW20735/CYW20721B2/CYW20819/CYW20820?
Thank you.
Ryan
Show Less
Hello guys,
I have a custom board with cyw20719b2, with a build setup using modus toolboox 2.1 and wiced bt sdk v2.7.1 fdb3982. As this is a custom board for embedded environment, the host is not really connected.
I have sleep configuration like this:
wiced_sleep_configure(
&(wiced_sleep_config_t) {
.sleep_mode = WICED_SLEEP_MODE_TRANSPORT,
.device_wake_gpio_num = WICED_P28,
.device_wake_mode = WICED_SLEEP_WAKE_ACTIVE_HIGH,
.device_wake_source = WICED_SLEEP_WAKE_SOURCE_GPIO,
.host_wake_mode = WICED_SLEEP_WAKE_ACTIVE_HIGH,
.sleep_permit_handler = m_shutdown_handler,
}
);
Here in the sleep configuration WICED_P28 is connected to interrupt pin coming from PMIC (Which gives push button / charger connect etc interrupts coming from PMIC).
So my problem is that, I also need the WICED_P28 pin for GPIO interrupt to handle various interrupts coming from PMIC.
When I tried to configure WICED_P28 for both (wiced_sleep_configure() & wiced_hal_gpio_register_pin_for_interrupt()), the gpio interrupt never gets called.
My question is, if it is possible to use same gpio pin for wiced_sleep_configure() & wiced_hal_gpio_register_pin_for_interrupt() ?
Thanks,
aniket
Show LessHello
I have a cybt-213043eval and a cybt-213043-mesh board
I want to know how I can load the examples of Modus Tool box, Empty_213043EVAL, Empty_213043EMESH, Hello sensor etc etc on the 2 cards instead of OTA or another way that does not use UART
Hello,
Using a Cypress CYW20819 controller on a custom board, we are trying to customize BLE pairing method.
Cypress firmware is compiled using ModusToolBox 2.0/2.1 workflow and `wiced_btsdk` 2.4.
During pairing, we want the cypress controller to print a passkey (randomly generated), then, the peering device (a Linux 4.19.80 with bluez 5.50) will have to type this passkey to validate pairing.
By setting cypress controller pairing IO capabilities to `BTM_IO_CAPABILITIES_DISPLAY_ONLY`, this works fine, a random 6 digits number is correctly printed, and peering device can correctly pair.
At this stage, the peering device has 30 seconds to type the passkey, otherwise, pairing will fail returning `SMP_RSP_TIMEOUT` error.
However, we now want to set the pairing passkey to 4 digits :
* Is it possible using cypress SDK ?
* I read that BLE passkey has to be a 6 digits number, so an acceptable workaround would be to use a 6 digits passkey between '000000' and '009999' (a '00' prefix can be set on peering device). Can we set pairing passkey manually at runtime using cypress SDK ?
We also to be able to set the pairing passkey timeout to 60 seconds. Is it possible using cypress SDK ?
Best Regards,
Jean Martin.
Show LessEmployee
Contributor
Contributor II
Contributor II
Employee
Employee
Honored Contributor
New Contributor
New Contributor II
New Contributor II