Studio Bluetooth Forum Discussions
Hello,
I am trying to build a Bluetooth headset with the CYW20706. I am new to PSoCs but I have been able to get the transducer output working via a DAC/AMP combo. However, we have been unable to get the our MEMS microphone to work consistently: https://media.digikey.com/pdf/Data%20Sheets/Knowles%20Acoustics%20PDFs/SPH0645LM4H-B.pdf
I found out that the I2S clock is only ~512kHz whereas the mic requires 1.024 MHz to go into active mode (even though the spec sheet says it runs at 1.5 MHz or 2.4 MHz?) I found out another potential issue is that the CYW20706 only takes 16 bits while the microphone outputs 24 bits, however we should be getting some kind of noise at all times? The microphone does not output anything even when its output pin is not connected to the eval board's I2S input pin. However, sometimes we are able to get audio SOMETIMES by first physically floating the LRC and SEL pins on the mic, which creates some noise, then plugging both into VCC. Occasionally after the noise appears it is able to pick up human audio. We are stumped as to what the issue is as we cannot repeat this phenomenon. We are using HFP. Any guidance would be greatly appreciated.
Show LessIs there documentation or a stand-alone tool that provides options for GPIO Pin-muxing for the CYW20179? I am aware of the SuperMux Wizard in WICED Studio, but wondering if there is any other resource.
Show LessWe are using a CYBT-333047 module based on the CYW20206 silicon. The .hex files for the EZ-Serial module platform are located here. There is a .zip archive with the up-to-date .hex files for this platform.
The Release.txt says the following:
This folder contains the EZ-Serial WICED Firmware V1.1.14 Release images for the
CYBT-343026-01 series modules. These images may be used on the following modules:
- CYBT-343026-01
- CYBT-333032-02
- CYBT-333047-02
- CYBT-343151-02
The xxx-rom-ram-Wiced-release.hex file is the complete firmware image suitable for flashing via HCI UART.
The xxx-rom-ram-Wiced-release.ota.bin files is suitable for BLE firmware update
Like mentioned in the Release.txt file, we can use the .hex file to completely update the module via WICED Module Programmer (HCI-Interface) and the .ota.bin file to update BLE firmware OTA via btsdk-peer-apps-ota.
But there is another file within the archive with an .ota.hex ending (ezserial_343026-CYBT_343026_EVAL-rom-ram-Wiced-release.ota.hex). What can we do with this file? It is not possible to use the WICED Module Programmer to flash our module with this .ota.hex file.
Best Regards!
Show LessI have a CYBT-423028-EVAL and a CYBT-423028-02. I'm running a Mesh Level Server on the EVAL board and want to run a Level Client on the 423028-02, which changes the level of the level server. I'm doing the provisioning with a mobile app. Which API function should I use to send the message and which configurations do I need while provisioning?
What I do for provisioning: Provision both devices(Level Server gets unicast address 0x0002 and Level Client gets 0x0004), bind app key to Generic Level Server(model ID 0x1002) in element 0x0002 of the Level Server, bind the same app key to Generic Level Client (model ID 0x1003) in element 0x0004 of the Level Client, set publish address of Generic Level Client (model ID 0x1003) to 0xFFFF for all nodes. Am I missing any steps or doing anything unnecessary?
I'm using WICED Studio v6.2 because apparently there are missing platform files on v6.4 (BugS Report: WICED6.4.0/Missing files )
I can change the level of the server and read the current state using the mobile app.
I can provide additional details if required.
Show Lesswiced_bt_mesh_event_t *p_event = wiced_bt_mesh_create_event(0x00, MESH_COMPANY_ID_CYPRESS, WICED_BT_MESH_CORE_MODEL_ID_GENERIC_LEVEL_SRV, 0, 0);
I am trying to create an event to send a Mesh message, but the function always seems to return NULL. Does anyone have an idea why this might be or how to fix this?
The device is provisioned and the Level Client element of the device has an app key and a publish address.
Show LessHi, I am using cybt-343026-01 module only and communicating with my microcontroller. Can I send HCI command using puart. (P24 as Rx and GPIO_5 as TX). Or to send HCI command I need to interface with HCI uart? And I want to change the name of bluetooth device. How to change it. I have used this command 0x01 0x13 0x0C 0x00 xxxxx. But I am not getting any reply.
Show LessHi, I am using CYBT-343026-10 module with external MCU. communicating successfully using HCI command. But I have some doubt.
1. I am getting response but after sending the same reset command 4-5 times and sometimes I get 04 0E 04 01 03 0C 0C. Instead of getting 00 as my last byte I am getting 0C Which is command disallowed.
2. Here how i send commands.
RTS = 0;
//hardware reset
BT_RESET = 0;
delay(1000);
BT_RESET = 1;
//THEN I SEND RESET COMMAND
01 03 0C 00
//CHANGE LOCAL NAME
01 13 0C 04 XYZT
// SCAN ENABLE COMMAND
01 1A 0C 01 03
//WIRTE PAIRING MODE TO ENABLE THE PAIRING MODE
01 56 0C 01 01
I get correct response, but when i try to pair the BLE with my phone it doesnt connect and even sometimes it asked for 16-bit pin.
Do i need to send some other commands too? or i need to get out of command state of the module?
3. Can i used HCI uart to run further application?
Thank you.
Show LessHello,
I'm trying fixed passkey on BT Classic, see below.
Refer to https://www.cypress.com/file/452971/download (p.48 Example 22)
However, the input screen of the PIN code did not appear on the tablet (Master) during pairing.
My settings are:
SSBP$,M=4D,I=0,F=3
@R,000B,SSBP$,0000
GSBP
@R,0028,GSBP,0000,M=4D,B=01,K=10,P=00,I=00,F=03
SFPK$,P=1E240
@R,000B,SFPK$,0000
GFPK
@R,0015,GFPK,0000,P=0001E240
[Question]
Can EZ-Serial use BT classic's fixed passkey?
Also, when I tried it on the BLE side, the PIN code input screen appeared, but when I entered the PIN code, "PIN code is incorrect" is displayed.
I think this is the same phenomenon as below.
EZ-Serial: BLE pairing with fixed passkey
Best regards,
Takahashi
Show Less