Hi Cypress,
I purchased the devkit for the CYBT-343026-01 modules (CYBT-343026-EVAL) and was able to use it for my specific needs (run it in SPP mode) in an instant. Consequently I used the module in a design (replicated the evaluation board's schematic), received the boards, but the modules will not communicate through the PUART which leaves me unable to send/receive HCI commands for configuration. On top of that the name of the Bluetooth device is "MTK DUT 706" which is different from what the datasheet says.
I have not found anything related to this online and I am starting to be suspicious that there is a problem with the factory firmware.
Best,
Simon.
Show Less
Hello,
Could you let me know some delay functions for microseconds for CYW20706?
Thanks
Hi We are working on imx6ul. There is an issue with bluetooth connection , as we are able to pair, scan but not able to connect with bluetooth devices
below are the logs
root@imx6ulevk:~# bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller D4:53:83:05:49:D5 Discovering: yes
[NEW] Device 70:BB:E9:4C:C5:79 Redmib
[NEW] Device 70:1C:E7:96:52:11 90100--IOT--GGN
[bluetooth]# scan off
Discovery stopped
[CHG] Controller D4:53:83:05:49:D5 Discovering: no
[CHG] Device 70:1C:E7:96:52:11 TxPower is nil
[CHG] Device 70:1C:E7:96:52:11 RSSI is nil
[CHG] Device 70:BB:E9:4C:C5:79 RSSI is nil
[bluetooth]# pair 70:BB:E9:4C:C5:79
Attempting to pair with 70:BB:E9:4C:C5:79
[CHG] Device 70:BB:E9:4C:C5:79 Connected: yes
Request PIN code
[agent] Enter PIN code: 1234
[CHG] Device 70:BB:E9:4C:C5:79 Modalias: bluetooth:v000Fp1200d1436
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 0000112d-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 70:BB:E9:4C:C5:79 UUIDs: 98b97136-36a2-11ea-8467-484d7e99a198
[CHG] Device 70:BB:E9:4C:C5:79 ServicesResolved: yes
[CHG] Device 70:BB:E9:4C:C5:79 Paired: yes
Pairing successful
[CHG] Device 70:BB:E9:4C:C5:79 ServicesResolved: no
[CHG] Device 70:BB:E9:4C:C5:79 Connected: no
[bluetooth]# connect 70:BB:E9:4C:C5:79
Attempting to connect to 70:BB:E9:4C:C5:79
Failed to connect: org.bluez.Error.Failed
[bluetooth]#
Kindly help
Hi,
We are using CYBT-353027 EVAL for communicating with I2C slave device. So, configuring CYBT-353027 EVAL as an I2C master. But, we are not able to communicate with I2C slave device.
While observing waveform over logic analyzer, we found that clock(SCL) is not generated properly. The frequency observed in waveform is not actually clock but just a pulse.
we are setting frequency using "wiced_hal_i2c_set_speed()" API.
Can you please suggest what should be done to resolve this? I have also attached are the screenshots from logic analyzer.
Below is the snippet of code we are using for I2C communication
-----------
#include "wiced_hal_i2c.h"
#define I2C_SLAVE 0x10
UINT8 status = 0xFF;
UINT8 data[2] = {0xAA,0x55};
UINT8 data_read[3];
enum
{
I2CM_SPEED_100KHZ = 240,
I2CM_SPEED_400KHZ = 60,
I2CM_SPEED_800KHZ = 30,
I2CM_SPEED_1000KHZ = 24,
};
// For Initializing I2c as master
wiced_hal_i2c_init(WICED_I2C_SDA_I2S_DOUT_PCM_OUT_SCL_I2S_DIN_PCM_IN);
// Set Speed
wiced_hal_i2c_set_speed(I2CM_SPEED_100KHZ);
// To write data to slave
wiced_hal_i2c_write((UINT8 *)&data,sizeof(data), I2C_SLAVE);
// To read data from slave
wiced_hal_i2c_read((UINT8 *)&data_read,sizeof(data_read), I2C_SLAVE);
Thanks,
Pratik
Show LessHello,
I've been worked long time in field of mobile platform and have a plentiful career about low level system driver on mobile BB SW with commercial RTOS such as Nucleus and ThreadX.
Nowadays, I got a chance to get a job to develop BLE module using Cypress chip.
So, I'm gathering useful information for this stuff from your site and bought your CYW920706WCDEVAL board already.
However, I have a question about basic concept of development using WICED studio.
Basically, FW/driver engineer code and debug in full source level with OS API under RTOS environment. we compile and link it using ARMCC/ARMLNK to get bin file.
What's the difference between upper case and WICED studio environment?
what kinds of RTOS delivered from WICED studio environment? I couldn't find any information about RTOS used in your environment. otherwise, do I need to port any RTOS I have on your SDK env.?
It's a very simple question for you, but I've been confused about this basic concept. think my brain was harden due to long time career in one platform.
Please give me your basic concept regarding dev. environment with your studio/SDK.
Thanks!
Show Less
Hello,
Please tell me about the p_cyspp_status (.CYSPP, ID = 10/1) event of EZ-Serial FW.
I understand the following Bit mask in "S (status)" of Event Parameters.
- Bit0 (0x01) = Unacknowledged data subscribed
.CYSPP,S=01
=> Indicates that 0x01(Notify) was written to the Configuration Descriptor(UUID 0x2902) of "Unacknowledged Data Characteristic(UUID 65333333-A115-11E2-9E9A-0800200CA102)".
- Bit1 (0x02) = Acknowledged data subscribed
.CYSPP,S=02
=> Indicates that 0x02(Indicate) was written to the Configuration Descriptor(UUID 0x2902) of "Acknowledged Data Characteristic(UUID 65333333-A115-11E2-9E9A-0800200CA101)".
- Bit2 (0x04) = RX flow subscribed
.CYSPP,S=04
=> Indicates that 0x02(Indicate) was written to the Configuration Descriptor(UUID 0x2902) of "RX Flow Characteristic(UUID 65333333-A115-11E2-9E9A-0800200CA103)".
However, I don't know when the following Bits will be effective.
Please tell me the conditions under which these Flags are set.
- Bit 3 (0x08) = RX flow blocked by remote Server
- Bit 4 (0x10) = CYSPP peer support verified
- Bit 5 (0x20) = Data mode active (used internally)
Best regards,
TK
Hello,
I'm testing Pairing on BLE using the new Firmware Version (v1.2.27).
The following settings are made.
- smp_set_security_parameters (SSBP, ID=7/11)
SSBP,M=4D (D = 0x08|0x04|0x01= LE Secure Connection, MITM, Bonding)
- smp_set_fixed_passkey (SFPK, ID=7/13)
SFPK,P=1E240 ( = 123456 [6-digit])
The terminal to connect to uses an Android tablet.
Pairing (1 to 3) is performed according to the following procedure.
1. Connection request from Android device
=> C event is output (Tablet address is random address)
E,0035,C,C=01,A=4FA62934D02D,T=01,I=0028,L=0000,O=02BC,B=00
2. Execute "smp_pair (/P,ID=7/3)" for the Connection Handle to request pairing.
/P,C=01,M=4D,B=01,K=10,P=00
3. Pair and Encryption completed
E,000F,PR,C=01,R=0000
E,000E,ENC,C=01,S=00
4. Execute "smp_query_bonds (/QB,ID=7/1)" and check the Bonding list.
/QB
R,000E,/QB,0000,C=01
E,001B,B,B=01,A=4FA62934D02D,T=01
After completing this pairing, disconnect once and reconnect from the tablet.
Then, in the C event, a different address will be output.
E,0035,C,C=01,A=7BEF6766B766,T=01,I=0028,L=0000,O=02BC,B=00
On my system, the addresses listed in /QB are paired addresses and I try not to perform step 2 above.
However, every time I reconnect, the address of the C event changes, and pairing (/P) is executed every time.
[Question]
Is there a way to identify the address of the Central Device once paired?
If it is a public address, it is a fixed value.
However, in BLE, it is a random address, so it would be nice if I knew the IRK.
Is there a way to do that?
Best regards,
TK
Show LessHello,
I am trying Deep sleep mode with the new FW (v1.2.27) of CYBT-353027-02.
https://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform
The settings are as follows.
SSLP$,L=02
.CYSPPSP$,P=1 (Default)
* I use CYBT-353027-02 EVB.
When entering deep sleep mode, LP_Mode pin is set to High.
(The current value of Module is several uA, so I think it is Deep Sleep.)
However, returning this LP_MODE pin to Low does not return the Module.
(The condition for returning is determined by issuing a BOOT Event from Module)
On the other hand, a similar test was performed with CYBT-343026-01 EVB.
(The LP_MODE pin is set to Active Low.)
In this Module, when LP_MODE is changed to Low, a Boot Event is issued and the original Active state is restored.
Why doesn't CYBT-353027-02 EVB return to active mode?
Best regards,
TK
Hello,
What is the API to get the packet statistics (Tx and Rx) on a SCO session?
I am using WICED SDK 6.4 on 20706 based module. I have implemented an HFP Audio Gateway. This was based on the demo hci_audio_gateway. The PCM is routed to I2S.
During the testing we are encountering the audio loss after a long run in one direction. Audio codec is negotiated as mSBC. Looking for packet stats to assist with debugging.
Thankyou
Praveen
Hello,
I am looking for information on how to program a new module in-system at our factory. Since SWD is not accessible, where can i find information about the proper interface to use? (would like to confirm our assumption that the ROM code allows programming over the UART TX/RX pins on the CYBT-483062-02 module.)
Thanks!
-Zach
Show LessEmployee
Employee
Employee
Contributor
Employee
Employee
Employee
Contributor