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?
We have a platform that uses WICED Version 3.7.0-7. AN STM32F469 processor uses the WiFi/BT module LBEE5KL1DX. We're able to bond with and connect and reconnect to a BTLE 4.0 keyboard without issues. When we do the same with the same model of keyboard that uses BTLE 5.0, we're able to bond with and connect with the keyboard, but upon re connection, the firmware crashes. From the debugger, it seems to be crashing in a pee-compiled module we have: BTE_low_energy.FreeRTOS.LwIP.ARM_CM4.release.a.
Our belief is that something in the firmware is not handling BT 5.0 events correctly and is causing the firmware crash. But it isn't easy to tell what's going on in the project and the .a file is a bit of a mystery too. Are there any clues as to where to look for this issue? Is there perhaps an updated version of WICED or an updated driver file we should be using?Show Less
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,
1GC sends data using UDP, Call wiced_result_t wiced_udp_send(wiced_udp_socket_t * socket, const wiced_ip_address_t * address, uint16_t port, wiced_packet_t * packet), can only send 1472 bytes?
I have changed NX_DONT_FRAGMENT to NX_FRAGMENT_OKAY when I call wiced_UDP_create_socket to create UDP socket. The result is also not supported.
Call wiced_packet_create_udp(socket, 4000, &packet, (uint8_t**) &data, &available_data_length), The value of available_data_length is 1508.
Hi everyone, I am following a firmware development project based on the WICED 4.1 SDK, I need to update the SDK to solve the famous WPA2 KRACK vulnerability.
Unfortunately, between version 4.1 and the latest 6.6.x.y versions there is no bootloader compatibility and this makes an update via OTA impossible.
So, inevitably, to fix the vulnerability I must necessarily update to version 4.1.3 as it is the last one that maintains the compatibility of the bootloaders. Now I have the problem of having to find the SDK for linux versions.
I found this topic on the support page but the links are not working: https://community.infineon.com/t5/Blogs/WICED-Studio-4-3-1-has-been-released-backport-to-address-KRACK/ba-p/129833
Can you help me by providing me the sdk for linux versions?
Thank youShow 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?
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 18.104.22.168. 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
In my application I need to know what beacon period and DTIM interval are set for the AP that my device (CYW4343W in Type1DX with WICED 6.6) is connected to.
I'm calling wiced_get_bss_info to achieve that. Most of the time, it works fine, however, for some unknown reason it sometimes starts to fail and then fails continuously with the error code 2014 (Buffer too short).
What are the possible reasons for such error for this function ? How can I prevent that ? Is there any other way to get the beacon / DTIM information ?
Thanks for your support.