Wi-Fi Combo Forum Discussions
We've received reports that CA(Certification Authority) are not being checked, and we're considering taking action.
Since "TLS_VERIFICATION_REQUIRED" is set, I think the SSL certificate verification process is working.
◆ File
wiced_defaults.h
/* WICED TLS Options * /
#define WICED_TLS_DEFAULT_VERIFICATION (TLS_VERIFICATION_REQUIRED)
◆ Environment
・ WICED SDK: 6.4.0
・ OS: ThreadX
◆makefile
In the current situation, to check the Certification Authority (CA), is it enough to set the path of the root CA to "CERTIFICATE" and "PRIVATE_KEY" in the makefile?
Or is this a self-signed certificate for the HTTP server, and there is another way to check for a Certificate Authority?
CERTIFICATE := $(SOURCE_ROOT)resources/certificates/server_cert.cer
PRIVATE_KEY := $(SOURCE_ROOT)resources/certificates/server_cert_key.key
Hello, I'm using CYW954907AEVAL1F.
I develop an app that listen and accept incoming TCP connections on WiFi.
Sometimes when I create socket I obtain error
result = 7
Show LessHi All,
We are planning to create a program with similar functionality to " ble_wifi_introducer " .
[Background]
Our application does not turn off the power once it has been turned on
until something like a power outage occurs.
On the other hand, while checking the WICED Studio Wi-Fi/Combo Forums,
I found the following thread.
https://community.cypress.com/message/156413#156413
It seems that a memory leak occurs when the BT stack is repeatedly
wiced_bt_stack_deinit and wiced_bt_stack_init .
This thread still seems to be open.
[Question]
Is the BT stack memory leak problem solved ?
We believe that our product needs a fix for this issue.
Software environment:
- WICED 6.2.1 or 6.4
Best Regards,
Sakagami
Hello,
In order to respect our cybersecurity requirements, I need to disable the support for TLS 1.0 and TLS 1.1, only keeping TLS 1.2.
I've noticed that this configuration is made from wiced_default.h
However it comes with a comment
/* Note: Please don't try to change TLS MINOR VERSION MIN & MAX values,
* as few wiced prebuilts are compiled using below values changing the values can cause issues
* */
/* TLS major version is assumed to be 1 */
#define WICED_TLS_MINOR_VERSION_MIN (0) /* Refers to TLS version 1.2. Values for TLS Versions: 0 ==> TLS v1.0, 1 ==> TLS v1.1, 2 ==> TLS v1.2 */
#define WICED_TLS_MINOR_VERSION_MAX (2) /* Refers to TLS version 1.2. Values for TLS Versions: 0 ==> TLS v1.0, 1 ==> TLS v1.1, 2 ==> TLS v1.2 */
What would be the correct approach to disable TLS versions that are under 1.2?
Best regards,
Ben
Show LessHi,
With WICED_ENABLE_MCU_RTC, I would expect after setting RTC time and reboot
then I can still get correct rtc time.
However, I found platform_rtc_init will always setting the rtc time to default_rtc_time during boot.
As a result, everytime reboot the device, the rtc time is wrong.
Note, all support platforms has such behavior - always setting the rtc time to default_rtc_time during boot.
Can someone explain this?
Show LessHello,
When could we expect support for the LwIP Chained Buffers?
At the moment, Wiced does not properly support LwIP without this. The Chained Buffers are a core feature of LwIP which cannot be deactivated.
My previous post was closed as Solved but the issue itself is not: https://community.infineon.com/t5/Wi-Fi-Combo/low-level-output-asserting-with-quot-No-chained-buffers-quot/td-p/272447
Thanks for your support,
Best regards
Show Less
In this thread:
https://community.infineon.com/t5/Wi-Fi-Combo/usb-device-cdc-sample-can-not-send-512byte/m-p/240409
The comment says it's a known issue and will update the thread when the fix is available.
However, that thread never get updated.
I'm wondering if this is still an issue in latest sdk or not.
BTW, I have no idea why that topic get locked before updating the fix.
Show LessWe are looking for some information on rough memory footprint data on simultaneous BLE/WLAN examples - using the ST+Cypress part (LBEE5PA1LD). Some things to note:
WLAN in STA or AP mode? (we would need both in the FW, but not simultaneously)
BLE peripheral
Are there some documents out there, or possibly examples we could use for a guestimate? I did find N1-4945_Type1LD-AppNote_Memory_Usage.pdf appnote, which looks like it is the https_server example, but the footprint data isn't broken down to a level that is meaningful from the question "How much space does the WLAN host stack/driver and BLE (HCI) host stack/driver take up?
The WICED-6.6.1.1 is using mbedTLS-2.16.6, which includes some security issues:
https://tls.mbed.org/security
Please upgrade mbedTLS to the latest stable version.
Show Less