AIROC™ Bluetooth Forum Discussions
What is the RF Antenna Port(PIN18) output resistance of Cyw20719B2KUMLG?
I want to debug a sample code but the following error occurs.
Build and program were succeeded.
Could you tell me how to solve it?
Debugger: On board (connected to PC via USB)
OS: Windows 10
IDE: Eclipse IDE for ModusToolbox v2.2.0
Sample Code: HID_Dual_Mode_Keyboard
I am working on interfacing BME680 Bosch sensor to Cypress CYW920719Q40EVB -01 / CYW920819EVB-02 controllers. I need support in interfacing.
Thank you.Show Less
I had assumed that sending less data over BLE in a single connection event would decrease the power consumption.
I decreased the number of bytes sent over BLE by changing the data_length using methods as shown below
- XXXindicationHandle.value.len = data_length/2;
- XXXindicationHandle.value.actualLen = data_length/2;
- decreasing characteristic length in the Configure 'BLE' tab accessible in the top design.
However, the power consumption remains the same.
i have a cyw920706wcdeval board and have a plan to use it for BLE application. It will be ported on freertos or mbed also in next step.
So, my question is
which kind of sw tool you delivered is the best choice for this plan? I’m confused little bit because there are some sw tools such as wiced studio, modustoolbox, and psoc creator in your side.
Colud you please let me know that?
How is EZ-Serial supported on PSoC 63 BLE devices developed with Modus Toolbox?
- EZ-SERIAL™: EZ-BLE MODULE FIRMWARE PLATFORM @ https://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform <== doesn't include CYBLE-4xxxx modules
- AN96841 - GETTING STARTED WITH EZ-BLE™ CREATOR MODULES @ https://www.cypress.com/documentation/application-notes/an96841-getting-started-ez-ble-creator-modules <== doesn't cover ModusToolbox or CYBLE-4xxxx modules
- AN228571 - Getting Started with PSoC 6 MCU on ModusToolbox @ https://www.cypress.com/documentation/application-notes/an228571-getting-started-psoc-6-mcu-modustoolbox <== doesn't cover EZ-BLE
I am trying to run our development kit project on our target project board but the output is different in the way that our target does not establish the secondary connection.
The project sets up 2 connections (1 Headset profile connection and 1 Handsfree profile connection), 1 for audio and 1 for command management. Both connections work on the development board but the Handsfree profile connection does not get established on the target board (the Headset profile connection DOES get established).
We are using the CYW920706WCDEVAL for development kit and the CYW20706 as target chip.
The project is based of of the AUDIO HEADSET example from the MODUSTOOL.
! On our target board the CYW20706 is being managed by a host microcontroller for command management. !
!! When we route the connection from the development board through our programming connector to the target board it does work !!
but in this situation the communications are managed through the CLIENTCONTROL computer program from the MODUSTOOL and the microcontroller on our target board is held in reset.
We checked the communications which are being send by the computer application and our microcontroller application and these match.
So the question is are there functions on the controller which are being enabled/disabled by the CLIENTCONTROL computer program from the MODUSTOOl which are not really obvious or are there pins which control certain functions which would enable/disable connections the for CYW20706?
With kind regards,
We are using the CYBLE-212006-001 in a project with SPI, we have it set for three slaves, on SS0,SS1,SS2.
I must have missed it in the documentation, but if you want three slaves, number three, which should be SS2, is actually SS3, so in the function call SPI_SpiSetActiveSlaveSelect(2); if you specify a 2 as shown no SS if fired. The PIN names, etc are refer to SS2, but regardless it will never work.
If you specify a 3, SPI_SpiSetActiveSlaveSelect(3) it works fine; now it makes sense as that is the SS brought out in this module by carefully noticing that there was no SS2 in the pin assignments.
Going back I found no reference to this in the documentation, and the SPI widget did not issue me a warning, this cost us two days to figure out, do you plan to better document this "feature".
What errata is available between CYBT-483062-02 and CYBT-483039-02?
CYBT-483039-02 appears to be end-of-life or at least NRND.
Recommended replacement appears to be CYBT-483062-02
Is CYBT-483056-02 also being promoted.
Hi, we're doing final verification for a new product design using the CYBLE-222014-01.
I have found the intentional and unintentional radiator test reports for this device here (https://community.cypress.com/t5/Knowledge-Base-Articles/RF-Regulatory-Certifications-for-CYBLE-222005-00-and-CYBLE/ta-p/253142) but the intentional radiator report seems to be missing some tests. Test report 1622078R-RF-US-P06V02 contains:
- 15.247 (b) Maximum peak power output
- 15.247 (d) Emission on band edge
- 15.209 Radiated emissions limits (spurious emissions)
However to comply with the rules my understanding is that the following tests are also needed:
- 15.247 (a) 6dB Bandwidth
- 15.247 (e) Power spectral density
Am I incorrect in my understanding that these additional two tests are required to pass FCC? Is there any reason why these tests have not been performed?
- « Previous
- Next »