When sending data from PC via USB serial port to CYSPP CYBT-483039-EVAL, it appears to be over-running the CYBT, without CYBT ever asserting PUART_RTS low.
- CYSPP CYBT-483039-EVAL is connected to iOS app using EZ-Serial BLE CYSPP
- Data is being sent using the Acknowledged Characteristic (101)
- PUART SW5 are all turned On
- After press reset switch on eval board, I see UART RTS pin Arduino J7-P6 go high on oscilloscope
- I set CYBT and flow control by sending following command to PUART from the PC.
When PC starts sending file data to PUART over USB serial, I see the data being received on the iOS side, however, some data is missing.
I expected PUART RTS to be asserted low to prevent 3 MB of file data from over-running the CYBT, when sending data to PUART_RX ?
I do not see UART_RTS on pin Arduino J7-P6 being set low during the 3MB file transmission.
What are potential solutions to prevent data over-running when sending data to PUART RX for transmission to iOS device?
I suspect I am over-running the CYBT when sending data from the built-in USB virtual COM port. I tried using an oscilloscope, however, I see no signals changing on either J1 or the module solder pads pin 22 (UART_RTS_N) and 24 (UART_RXD ). I know CYBT is sending data because I can see it being received by iOS app. I must be doing something dumb, but cannot figure out how I am over-running the CYBT module from the PC sending USB serial.
What does On and Off states control for CYBT-483039-EVAL SW4 HCI UART?
Should these be On for using USB serial port, and Off for JI HCI UART connected to a FTDI TTL 3V USB cable?
What does setting SW4 to all Off do?
See attached picture of eval board?
When power is applied to a CYBT-483056-02 module as received from the factory, I expected to see the LightBlue mobile app discover "EZ-Serial". I do not see "EZ-Serial" peripheral.
1) Question: Should CYBT-483056-02 be expected to arrive from factory with EZ-Serial firmware installed ?
Should we plan to program CYBT with EZ-Serial firmware in manufacturing?
2) Does using Windows 10 OTA upgrade utility WsOtaUpgrade.exe, require EZ Serial to be pre-installed?
3) Does updating firmware locally through HCI UART, require EZ Serial to be pre-installed?
Thank you for your help,
I am seeking advice on using CYSPP to connect to an iOS app.
What I Am Doing
- EZ-Serial has been installed on CYBT-483039-EVAL board
- CYBT-483039-EVAL board is connected via USB serial port to PC
- PC app is emulating a BLE device that will use a CYBT device
- iOS app connects to CYSPP service
- iOS app sends dumpbinfile command to CYSPP device
- PC app, in response to dumpbinfile, returns number of bytes it is about to send, then dumps contents of a binary log file by sending binary data directly to CYBT-483039-EVAL board, appending a CRC32
- iOS app received data over CYSPP Unacknowledged Data Characteristic
All is good most of the time.
Intermittently, the iOS app does not receive the expected number of bytes. Data loss is more common on a larger 3 MiB file than a 7 kB file.
1) Is problem because I am sending data to CYBT-483039-EVAL over PC USB serial without using any API commands?
2) For reliability do I need to use both the Acknowledged Data characteristic and RX Flow characteristic ?
3) How can send binary data to CYBT-483039-EVAL board, over the USB serial connection, to the Acknowledged Data characteristic and use RX Flow characteristic ?
When I send data to CYBT-483039-EVAL over PC USB serial, it appears by default, to send using Unacknowledged Data Characteristic.
Thank you for your help,
Hi, we are using CYW20706 module with EZ-serial firmware, and we need to print the BT MAC address on device labels, but the module seems to change it every factory reset. I've tried to disable privacy mode by using SPRV,M=0 command, but it seems to have no effect
Some logs of MAC address changing across factory resets:
/RFAC @R,000B,/RFAC,0000 @E,0005,RFAC @E,003B,BOOT,E=01021D1D,S=05020016,P=0103,H=D1,C=00,A=C3EED7B7253C @E,000E,ASC,S=01,R=03 GBA @R,0018,GBA,0000,A=C3EED7B7253C SPRV,M=0 @R,000A,SPRV,0000 GPRV @R,0016,GPRV,0000,M=00,I=012C GBA @R,0018,GBA,0000,A=C3EED7B7253C @E,000E,ASC,S=00,R=03 SPRV,M=0 @R,000A,SPRV,0000 GBA @R,0018,GBA,0000,A=C3EED7B7253C SPRV,M=0 @R,000A,SPRV,0000 GBA @R,0018,GBA,0000,A=C3EED7B7253C /RFAC @R,000B,/RFAC,0000 @E,0005,RFAC @E,003B,BOOT,E=01021D1D,S=05020016,P=0103,H=D1,C=00,A=C567A2615ED9 @E,000E,ASC,S=01,R=03 SPRV,M=0 @R,000A,SPRV,0000 GBA @R,0018,GBA,0000,A=C567A2615ED9
Is it possible to keep the same MAC address across factory resets? Even that it's always public?
We want to use the CYBT-343151-02 (based on the CYW20706 chipset) for two simultaneous SCO connection. How does the PCM slot mapping works ? The CYW20706 datasheet says that the slot is always mapped to the same slot, but it does not give a rule for it :
1/ Do the first SCO connection uses the first slot, then the second SCO uses the next slot ?
2/ If I understand correctly, if the first SCO connection is closed while the other is still in use, then the second SCO data will still be placed on the second slot. Is it correct ?
3/ Is the slot mapping based on the SCO connection creation order or using a fixed scheme (like based on the remote device bd address or anything else) ?
Regards, JeromeShow Less
Does CYBT-483039-EVAL board support sending API commands via serial terminal?
I expected to see serial terminal output when I connect to the eval board and press SW1 reset.
- I never see any output in USB serial terminal.
- I tried 115,200 baud on either of two ports discovered, /dev/tty.usbmodem1421301 and /dev/tty.usbmodem1421303
- I see a MTKDUT739B1 BLE peripheral with zero services advertised when I run a BLE app on my iPhone.
My goal is to figure out how to communicate with CYSPP with an iOS app.
I`ve testing about sniff mode on HID Device, but HID Device seems can`t support the sniff mode.
my test environment are as below.
- Chipset & EVK : CYW20706 & F1DC2076 EVB (made in F1media)
- WICED SDK version : WCIED 6.2.1
- Test application : HID Device & ClientControl & BTSpy
+ added to support none secure connection for connection with Windows PC
+ enabled 'HID_DEV_PM_INCLUDED' for use power management
i add the source code, details are refer the attatched files.
- let the module Enter to Pairing Mode
- connect from windows pc to module
- check the current for enter to sniff or not
i`ve added the debug message to 'hidd_pm_start' and 'BTM_POWER_MANAGEMENT_STATUS_EVT' for check the operation, it doesn`t printed after connected, i think its a not entered to sniff mode. captured current is as below.
i tried to force enter to sniff using 'wiced_bt_dev_set_sniff_mode' after connected, debug message on 'BTM_POWER_MANAGEMENT_STATUS_EVT' are printed. it seems enter to sniff as like as below.
Q1. doesn`t HID Device support to enter sniff mode?
Q2. should i add something more for set to sniff?
Q3. i found the posts on community as HID Device of CYW20706 has a bug about low power and it is fixed a few month ago. is it related?
please could you help me anybody?
While looking for topics and knowledge database to use the CYBT-343151-02 bluetooth module, I found various entries :
* The knowledge database KBA225450 indicate a procedure to start the CYW2070*-A2 based devices (and list the one I'm using) in HCI mode, where all Bluetooth HCI standard commands are available. The interesting part is the SPI2_MOSI signal which must be setup correctly to 'force' the HCI mode when the device has an embedded firmware (which is the case for the CYBT-343151-02 module which is factory programmed with the EZ-Serial firmware).
* This blog article (https://community.infineon.com/t5/Resource-Library/Run-CYW20706-in-HCI-Mode/ta-p/246397) also gives a method to enter HCI mode on the same chipset, but the method is different (this time, the UART CTS pin must be pulled to HIGH during power up to enable HCI mode).
* This topic (https://community.infineon.com/t5/Studio-Bluetooth/CYBT-333047-02-via-HCI-interface-on-Raspberry-Pi/td-p/124669) seems to confirm my observations that I will try to describe bellow.
All tests bellow have been done on a CYBT-343026-EVAL board where the chipset has been replaced with the CYBT-343151-02.
* TEST 1 : With stock firmware (EZ-Serial), the device will most of the time not accept HCI commands (we still have a setup where it seems to work but depends on timings).
* TEST 2 : With stock firmware and CTS pulled high (as per blog article), the behavior is almost the same as with the firmware running (I've observed that the HCI UART RTS stays high after a few seconds, therefore the configuration of the module via HCI H4 is stopped)
* TEST 3: With the stock firmware and only SPI2_MOSI pulled to ground during boot, then the HCI reset command is accepted (using cybluetool), other commands are not acknowledged. Seems like this is the download mode described in the datasheet of the module, the airoc hci protocl manual and the CYW20706 datasheet).
* TEST 4: With the stock firmware, CTS set HIGH and SPI2_MOSI set LOW during power-on (press the recovery button while plugging the USB cable), then all HCI commands are accepted (in the limit of the chipset HCI supported commands). I can do almost all configuration, but the device is not discoverable nor can detect other device (even after using the 'enable radio' vendor command in cybluetootl).
* TEST 5: Same procedure as TEST4, with bluez hciattach/hcitool utilities (to workaround the problem described in the third listed entries at the top of this topic, I've just send a HCI reset command to the module using cybluetool before running the hciattach command, because a hcidump told me that the module was not accepting the commands, and during the numerous tests that I did, I saw that this was due to a missing HCI reset command). This test ends in the same way as the TEST 4, event after sending the radio enable command, I can't detect other devices and the device can't be discovered.
* TEST 6: Using the empty_wiced_bt example from the ModusToolbox software, the HCI interface works (using cybluetool to enable scan, and radio, or using the bluez tools). I can discover the device, do an inquiry
Questions are :
* Why do the device need a firmware to run to make the bluetooth really work ? Is it related to the patched that the firmware embeds (and which might configure the radio properly, which is not the case when the firmware is bypassed using the SPI2_MOSI / CTS pin forced levels) ?
* Can you confirm that the ROM code needs both SPI2_MOSI and CTS pins to be forced to specific levels to boot in HCI mode (or tell me why this is needed, if it is not related to the CYW20706 ROM) ?
* Is there any way to make the module work using HCI commands and the stock EZ-Serial firmware ?
Regards, JeromeShow Less
We have a device using CYBT-343026 module with EZ-Serial Firmware. During initialization the application calls gap_get_device_name to set some application specific name. Using a typical Android BLT scanner/pairing app the device appears in the scan list with the device name that was set by the application. When an attempt is made to pair with the device the name shown in any pairing pop-up boxes is of the form "EZ-Serial E8:B9:12_BT" rather than the device name.
Is there a way to get the pairing operation to use the device name rather the default "EZ-Serial..."?Show Less