Wi-Fi Combo Forum Discussions
Hi All,
I am planning to make a client to connect to the https server with WiCED.
Then I hope to disable the server certificate validation check.
The SSL/TLS handshake process I have mentioned is as follows.
I checked the URL "The SSL/TLS Handshake: an Overview - SSL.com" .
https://www.ssl.com/article/ssl-tls-handshake-overview/
In the third step
"Client verifies the server's certificate, then extracts the public key ....... .......
..................... then sends it to the server."
I want that the Client does not verify the server's certificate.
Is there any client-side sample code like this ?
Best Regards,
Sakagami
Show LessHello,
We are employing your CYW4356 WiFi transceiver to connect our android device to our WiFi network.
The objective is to use 802.11ac standard to benefit it's transmission speed.
We are using a Technicolor TC7230 WiFi router.
WiFi router specification: 5.0 GHz (3x3) IEEE 802.11ac AP with IEEE 802.11ac compliant transmit beamforming
Technical Datasheet:
https://www.normann-engineering.com/products/product_pdf/premise_equipment/technicolor/tc7230.pdf
Specifically we use an AMPAK AP6356 module (integrates a BCM4356/CYW4356), our android device's CPU is an Amlogic S905X2 and our device has 2 physical antennas.
AMPAK AP6356 Technical Datasheet:
http://rockchip.fr/ampak/AP6356_datasheet_V1.0_07252014.pdf
We perfomed multiple speed tests and used different WiFi network analyzers to know what was the transmission speed and MIMO,Modulation and Encoding used.
WiFi network analyzers informed us PHY speed 866.66 Mbps, which means 2x2 MIMO 256QAM 5/6 Encoding.
But real speed is 200 Mbps (we never obtained greater than 250 Mbps)
We performed the same test (same test conditions) with another android 2x2 MIMO device (PHY speed 866.66 Mbps) and real speed was 446.6 Mbps (always around 400-450 Mbps)
We know MAC efficieny determines real speed, reducing PHY speed around 50%-70% (such as the other android device tested)
We are trying to understand why speed is so low.
Is it due overheads such as interframe space, ACKs or MAC headers?
Is there any other cause that can reduce the real speed?
Thank you for supports,
Kind regards,
Antonio Valbuena Sánchez
Show LessWe are currently developing our design using 1DX Murata module based on CYW4343W chipset. But later we are planning to use 1FX module based on CYW43364 chipset. Both 1FX & 1DX are drop in replacement while 1DX gives additional feature of Bluetooth which are no connect lines for 1FX.
Are both the modules software compatible? We are currently trying with NXP iMx Series Parts which are using WICED drivers.
Show LessHello,
I have completed the WICED WiFI Tutorial. https://www.cypress.com/training/wiced-wi-fi-101-video-tutorial-series
I am working on AWS application using the development kit CYW954907AEVAL1F. in Chapter 8 of the AWS tutorials, there are three versions for establishing connection with AWS Cloud. When I run the code MQTT, I am catching some error with initialization of MQTT.
I have checked my policies are consistent with following this post (AWS MQTT TCP receive error )
I am not sure what is error code 4, and I am also not sure how to debug this as the code was written for the dev kit, and I have only changed wifi access SSID/PC, and the endpoints, and Topic related information in AWS. My certificates and Thing are working as desired with other scripts, but the MQTT code provided on GitHub is providing this error.
Thanks for any guidance on this issue.
Jerome
Show LessRecently a couple of documents surfaced both on Cypress's site and Murata's, claiming the CYW4343W supports BT5.1. The datasheet still only claims support up to BT 4.1. Does anyone know what features of BT5/5.1 the CYW4343W actually supports, if any? Or is this a copy n' paste error that got out of control?
Product brief referencing BT 5.1:
https://www.cypress.com/file/449611/download
Murata module page also claiming BT 5.1 (type 1DX module):
https://wireless.murata.com/products/rf-modules-1/cypress-based-modules.html
And actual Murata datasheet for the 1DX module, with CYW4343W, claiming BT 5.1:
https://wireless.murata.com/pub/RFM/data/type1dx.pdf
Thanks!
Show LessHi All,
What should I do if I would like use TLS without server authentication ?
Should I just build without a root certificate?
In the TLS Security related API, authentication is done explicitly,
so should I give up that API function?
Best Regards,
Sakagami
I would like to make use of server side events (SSE), and have compiled/run the example on a CYW943907AEVAL1F eval board: snip/http_server_sent_events
(Side note: I can get it to run reliably once I comment out the line "wiced_rtos_delay_milliseconds(300 * (unsigned int)random_initial);" in sntp.c. -- Minor issue).
Now, I can see the time updates being sent to the browser page and it all appears to work well:
This webpage demonstrates how a webserver notifies its clients using Server-Sent Event (SSE).
2018-12-29T18:06:38.388000Z
2018-12-29T18:06:39.388000Z
2018-12-29T18:06:40.388000Z
2018-12-29T18:06:41.388000Z
...etc
However, when I close the browser page, then the server crashes and reboots. Apparently it is crashing in the function wiced_http_response_stream_write in the function wiced_result_t send_event:
static wiced_result_t send_event( void* arg )
{
wiced_iso8601_time_t current_time;
char time_string[28];
wiced_result_t result;
UNUSED_PARAMETER( arg );
if ( http_event_stream == NULL )
{
WPRINT_APP_INFO( ( "No stream!\n" ) );
return WICED_ERROR;
} else {
WPRINT_APP_INFO( ( "Event stream is present...good!\n" ) );
}
/* SSE is prefixed with "data: " */
result = wiced_http_response_stream_write( http_event_stream, (const void*)EVENT_STREAM_DATA, sizeof( EVENT_STREAM_DATA ) - 1 ); <- it croaks here
...
}
The console output is:
Event stream is present...good!
...the web page is closed, then the processor croaks and reboots...
Starting WICED vWiced_006.002.001.0002
Platform CYW943907AEVAL1F initialised
Started ThreadX v5.8
Initialising NetX_Duo v5.10_sp3
Creating Packet pools
...etc
I think the function wiced_http_response_stream_write should be robust against client page closure. For some reason it isn't happy. I am wondering if anyone has seen this behaviour, and if so, what their solution might have been?
Thanks!
Show LessThis is a strange problem. I have found at least two devices, one in our lab and one in the field which gets stuck in a loop of wiced_tcp_receive returning an error code of 9.
The module is connected to an AP
The module is pulling valid NTP timesyncs and reaching public DNS servers so the networking stack seems okay, at least UDP.
I am trying to connect to a MQTT broker (AWS MQTT library) and the TCP connection and TLS handshake to the broker passes (good). I then see the CONNECT request go out but then the library starts polling wiced_tcp_receive for the CONNACK response but returns error code 9.
From wiced_results.h, an error code 9 is WICED_NOTUP which indicates that the interface is not valid but yet previous TCP/IP actions are working and passing the same checks.
What is weird is that these devices were communicating just fine, publishing messages to the MQTT broker every minute and then all of a sudden it got the error 9. In my code, this disconnected the device from the broker and tried to reconnect but only could once the module was rebooted.
Has anyone seen this? I am guessing something has happened to the socket variable being passed into wiced_tcp_receive, which provides an invalid interface to WICED_LINK_CHECK_TCP_SOCKET, but is odd that it cannot recover on following connect attempts.
SDK 6.2.1
LWIP + FreeRTOS
Show LessHi All,
We would like to implement dts of CYW43455 on i.MX8M Mini.
After refering to the following post >> CYW43455 with i.MX8M Mini, we find "usdhc1_pwrseq_wifibt" is not defined, could you help us what is the content of "usdhc1_pwrseq_wifibt" ? Thanks for your help.
DTS:
pinctrl_wlan: wlangrp {
fsl,pins = <
MX8MM_IOMUXC_GPIO1_IO00_ANAMIX_REF_CLK_32K 0x141
MX8MM_IOMUXC_SD1_RESET_B_GPIO2_IO10 0x1c4 /* WL_REG_ON */
MX8MM_IOMUXC_SD1_DATA5_GPIO2_IO7 0xC6 /* BT_DEV_WAKE */
>;
};
&usdhc1 {
#address-cells = <1>;
#size-cells = <0>;
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <&pinctrl_usdhc1>, <&pinctrl_wlan>;
pinctrl-1 = <&pinctrl_usdhc1_100mhz>, <&pinctrl_wlan>;
pinctrl-2 = <&pinctrl_usdhc1_200mhz>, <&pinctrl_wlan>;
bus-width = <4>;
pm-ignore-notify;
keep-power-in-suspend;
non-removable;
status = "okay";
enable-sdio-wakeup;
wifi-host;
mmc-pwrseq = <&usdhc1_pwrseq_wifibt>;
brcmf: bcrmf@1 {
reg = <1>;
compatible = "brcm,bcm4329-fmac";
};
};
Show Lessi want to test coexistence with cypress wifi. ( i'm bt developer)
i have cyw43012(murata module) and cyw43364(cypress module).
Can both module test external bt coexisttence (3-wire)?
I will buy linux host board and get default nvram.txt(from cypress support?).
how i change nvram.txt for ext 3-wire coex?
I red below document. but I could'nt find coexistence.
https://www.cypress.com/file/456086/download
Show Less