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.
To anyone listening. We developed system using a Laird_EWB module. We used the EWB-DevKt to build some basic apps, Dual Mode BT, TCP Server, etc. I am currently using OLIMEX ARM-USB-TINY-H to debug in eclipse. We attempted to make this work with the standard WICED apps with no joy. I have two versions of wiced studio. One is vanilla which allows me to test a small dual mode bt app using the LAIRD DEV kit. The other wiced studio has been modified slightly to allow for the OLIMEX debugger. I am able to build and download in eclipse using OLIMEX with some issues that I have worked out. I begin debugging my app on OUR module and while progressing through the application I keep coming across two unhandled interrupts. The active interrupts are shown to be 33 and 54. I decided to tackle INTERRUPT 33 first. According 8to the STM32F412 manual this is associated with the I2C channel 2 event. When I created my own platform file, I did not include any I2C. I have two USARTS, JTAG header, and power, and a few jumpers. What I am looking for is the steps necessary to override the "unhandled interrupt" using the wiced platform. In fact if there is any manual or detailed document that provides the steps necessary to incorporate interrupts either RTOS or native, please let me know. I have been through WICED-101 but the info that I am looking for appears to be a little more in depth than what WICED-101 provides.
I have also successfully tested our UART app with RTOS with no issues. I would really appreciate if someone could throw me a bread crumb.
Dan TShow Less
Hi everyone I'm trying to flash ISM43903_R48_L54 with a particular test target "flash_emc".
Building apps lookup table
make : *** [download_dct] Error 1
make: *** [main_app] Error 2
make: *** [Makefile.wiced: 428: flash_emc] Error 2
I am under ubuntu 22.04 and the problem is present only with this target, with others the firmware is flashed correctly.
As you will see from the logs the wiced version is 4.1. Do you have any suggestions to try?
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?
I'm trying to build up a test platform for our device off a raspberry pi which is running 32-bit Linux and is an ARM platform. I am trying to j-link flash the device from it. I copied over my build/, my apps/, and my tools/ folders but it looks like the ./tools/OpenOCD/Linux32/openocd-all-brcm-libftdi executible doesn't work on ARM.
Downloading Bootloader ...
./tools/OpenOCD/Linux32/openocd-all-brcm-libftdi: cannot execute binary file: Exec format error
**** OpenOCD failed ****
I don't believe that is built during the normal build process. I think it is just packaged with WICED Studio. Is there any way I can get flashing working on ARM 32-bit? I don't need it to build the full file, just be able to flash it. I'm currently running WICED-Studio 6.6.1
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
I am looking for an app note or more importantly some WICED sample code which will allow me to, firstly connect a generic BT headset/speaker to the Sterling EWB (CYW4343W). Secondly how to stream an audio signal connected to the BT_PCM pin on the CYW4343W to the headset. There is no requirement to send audio from the headset back to the EWB module.
We have a issue with non-working BLE advertisement after exit from Sleep mode.
Our procedures of enter to and exit from sleep mode looks more or less like that:
// turn on powersave mode (enter to sleep mode)
wiced_wlan_connectivity_deinit(); // WIFI module deinitialization
wiced_gpio_init( WIFI_EN, INPUT_HIGH_IMPEDANCE ); // WIFI module power off (LDO disable)
wiced_platform_mcu_enable_powersave(); // enable MCU sleep mode
// here we have very nice power consumption, about 500uA
// device sleep
// device wakeup
// turn off powersave mode (exit from sleep mode)
wiced_platform_mcu_disable_powersave(); // disable MCU sleep mode
wiced_gpio_init( WIFI_EN, OUTPUT_PUSH_PULL ); // WIFI module power on (LDO enable)
wiced_gpio_output_high ( WIFI_EN );
wiced_wlan_connectivity_init( ); // WIFI module initialization
// enable BLE advertisement after exit from sleep mode
wiced_bt_start_advertisements( BTM_BLE_ADVERT_UNDIRECTED_HIGH, 0, NULL );
Deinitialization WLAN connectivity only (without turning off WiFi power cause high power consumption, above 10mA).
Turning OFF WiFi RF power (by external LDO) decrease power consumption below 500uA which is expected.
Reintialization everything in a clear way, together with turning ON WiFi RF works well until start BLE advertisement.
Starting BLE advertisement causes continuous periodic (every 8.5s) receiving BLE_ENABLE_EVT events from bluetooth stack.
And advertisement doesn't work, we are not able to see any advertisement packets.
We definitely would like to turning off/on WiFi power by external LDO, because it gives us additional 1mA of power savings in compare to powersave only without WiFi deinitialization.
What could be a reason for this behaviour?
Are our enter/exit sleep mode procedures correct?Show Less
I just upgraded the version of Wiced we are using from 6.4 to 126.96.36.199. When the code tries to set wwd_wifi_fast_bss_transition_over_distribution_system the result is now WWD_WLAN_UNSUPPORTED.
The chip is a CY43012C0.
Any ideas why this no longer works?Show 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