Studio Bluetooth Forum Discussions
Hi,
According to the datasheet of CYBT_343026, this pin should not control from external CPU.
(Please see attached "DS_CYBT.png")
However, this pin could be used to enter "Recovery Mode" according to EVAL board manual and following link.
Programming an EZ-BT WICED Module – KBA223428
Should the customer connect SPI2_MOSI from host CPU or button and sensed "Low" if data corruption in SPI Flash is happened ?
Thank you.
--TAK
Show LessHello:
I use CYW20706A1 for BR/EDR application.
As we know,there is a HCI command which can get remote device name by its mac addr.
I want to know whether CYW20706A1 can support it. If it does,what functions can I use?
Thank you!
Show LessHi Cypress,
I'm trying to use the NVRAM to store the pairing keys on a CYBT-353027 Eval board using Hello Client project but it doesn't work.
I have added APP_PATCHES_AND_LIBS += FM25Q04_sflash.a in the makefile of my project as requested in the installation process.
It seems that the write NVRAM command works but if I try to read it again the Read NVRAM function returns 4 which is not documented.
-----> My assumption would be that the write NVRAM doesn't work.
I found in the forum that on Wiced smart, there was an api to handle the write protection, is there something similar for Wiced Studio?
Here are the logs:
hello_client_app_init
wiced_bt_gatt_register status 0
wiced_bt_gatt_db_init 0
hello_client_management_cback: 17
Advertisement State Change: 3
wiced_bt_start_advertisements 0
1
2
3
4
5
6
7
8
9
10
hello_client_gatt_callback event 0
hclient_connection_up Conn Id:1 Num conn:1,Addr:<7f 22 c6 9f 4c 50 > role:1
hello_client_management_cback: 17
Advertisement State Change: 0
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 5
peer mtu:185
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 42
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 44
11
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 46
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 62
hello_client_management_cback: d
hello_client_management_cback: a
hello_client_management_cback: 12
--------------------------------------------------------FIRST PAIRING---------------------------------------------------
Read NVRAM at:1 bytes:0 result:4 // Can't read NVRAM, return 4 which is not documented
writing to id:1
Saved 138 bytes at id:1 0 // Seemed to have saved the pairing key
hello_client_management_cback: b
Pairing Complete: 8
--------------------------------------------------------------------------------------------------------------------------------
12
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 16
13
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 16
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
hello_client_gatt_callback event 0
hello_client_connection_down 1 <7f 22 c6 9f 4c 50 >
hello_client_management_cback: 17
Advertisement State Change: 3
wiced_bt_start_advertisements: 0
29
30
31
32
33
34
35
-----------------------------------------------------------------RESET DEV BOARD--------------------------------------------------
áhello_client_management_cback: 15
hello_client_management_cback: 14
hello_client_management_cback: 14
hello_client_management_cback: 0
hello_client_app_init
wiced_bt_gatt_register status 0
wiced_bt_gatt_db_init 0
hello_client_management_cback: 17
Advertisement State Change: 3
wiced_bt_start_advertisements 0
1
2
3
hello_client_gatt_callback event 0
hclient_connection_up Conn Id:1 Num conn:1,Addr:<7f 22 c6 9f 4c 50 > role:1
hello_client_management_cback: 17
Advertisement State Change: 0
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 5
peer mtu:185
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 42
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 44
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 46
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 62
hello_client_management_cback: d
hello_client_management_cback: a
4
5
6
7
hello_client_management_cback: c
--------------------------------------------------------TRY TO RECONNECT ---------------------------------------------------
encryption status: bd ( 7f 22 c6 9f 4c 50 ) res 0
hello_client_encryption_changed 0hello_client_management_cback: 12
Read NVRAM at:1 bytes:0 result:4 // Can't read the NVRAM at he exact same id as it was supposed to be saved in the previous connection
Delete id:1 Result:8109
writing to id:1
Saved 138 bytes at id:1 0 // Write the pairing key at the first Id as done during the previous connection
hello_client_management_cback: b
Pairing Complete: 0
-----------------------------------------------------------------------------------------------------------------------------------------
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 2b
8
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 16
9
10
hello_client_gatt_callback event 4
hello_sensor_gatts_req_cb. conn 1, type 1
read_hndlr conn 1 hdl 16
Show LessHi Cypress,
I've integrated a CYBT-353027 into a custom board and I was developing my custom application piloting the module using HCI USRT and everything was working perfectly until recently when the application didn't start on the CYBT-353027.
I made few tests and it seems that I can write in the the flash but I can't read anymore.
Here are the logical levels on the UART at the end of the firmware upgrade. I send a launch ram command for the application: 0x04 0x4E 0xFC 0x04 0x00 0x00 0x00 0x00,
then I recieve the ACK, RTS goes high and nothing, I can notice few activity on the Cs of the flash but nothing compare to when it was supposed to work.
I send a launch ram command for the application: 0x04 0x4E 0xFC 0x04 0x00 0x00 0x00 0x00
Here are the logical levels on the UART when I send a read flash command at the starting address of the application:
I can see a lot of toggling on the flash Cs when the MCU is writing the firmware but almost nothing when we try to read anything from the flash, like it should do at bootup or when reading a ram chunk.
Have you already seen this issue?
Is it locked in write only?
I have already implemented the recovery mechanism which was also working perfectly before this problem occurred.
Show LessHello, we are developping a product based on module CYBT-353027.
It seems that modules we receive are programmed with a MAC address formatted the following way: "20:70:6A:20:XX:XX".
This looks like the OUI part (Organisationally Unique Identifier) is set to "20706", which looks lke the chipset familly embedded in the module 353027 module.
Looks like a temporary debug MaC address, not like an official one.
My question is the following:
- Can we use this MAC address in our final product or do we have to program a real MAC address on the module during our factory End Of Line process (MAC address that would be provided by Cypress in a SerailNumber-MAC address database/file) ?
Thank you for your help.
Show LessHi,
Q1:
Could you tell me internal pull-up resistor value inside CYBT-343026 on XRES pint?
<Back Ground>
-XRES has internal pull-up according to the datasheet
-My customer would like to drive XRES pin from external CPU.
-They has a plan to put pull-down resistor on this pin in order to sense low during power-up sequence.
(External host has a time that this pin will be set "Un-Specified")
-In order to decide resistor value of pull-down, we need to know resistor value of internal pull-up inside CYBT-343026.
Q2:
If GPIO (0/3/4/6/7) , P4 and P24 pins are not used, can we leave these pins floating(OPEN)?
Thank you.
--TAK
Show LessHello ,
Which hw development kit is available for developing Bluetooth Mesh Solution from Cypress.Can some one please point to the right hardware and the necessary software.
Rgds,
Pedro
Show LessHi,
I'm currently evaluating the CYBT 343026 BT/BLE module and have a question about the PCM audio interface. In the specification for the chipset used (CYW20706 Datasheet ) in section 1.7 it indicates that the PCM interface can run in TDM mode with 1, 2, 4, 8 or 16 slots. I could not find a way to configure how many slots should be present and which slots the module should use within the WICED APIs. Have I missed something?
Thanks
Nigel
Show Less