Wi-Fi Combo Forum Discussions
I am trying to run the snip\ping_deepsleep example with FreeRTOS and LWIP. The application is crashing (hitting assert) right after getting the DHCP address.
In LwIP, pbuf.c, pbuf_free function, the application stops at LWIP_ASSERT("pbuf_free: p->ref > 0", p->ref > 0) where p->ref == 0.
The issue occurs in SDK 6.1 (lwIP 2.0.2) and 6.2 (lwIP 2.0.3).
Device: CYW43907
Console out
Application started: cur_rtos_time=0 cur_slow_time=92403407 rtos_time_since_deep_sleep_enter=2800103 wakeup_count=1
Cold boot.
Initialising LwIP v2.0.2
DHCP CLIENT hostname WICED IP
WLAN MAC Address : B8:D7:AF:28:B6:72
WLAN Firmware : wl0: Feb 12 2018 23:35:27 version 7.15.168.108 (r683813) FWID 01-81fd72af
WLAN CLM : API: 12.2 Data: 9.10.74 Compiler: 1.31.3 ClmImport: 1.36.3 Creation: 2018-02-12 23:30:46
WICED inited: rtos_time_since_deep_sleep_enter=2800787
Networking is about to bring up
Setting IPv6 link-local address
Obtaining IPv4 address via DHCP
IPv6 Network ready IP: FE80::BAD7:AFFF:FE28:B672
IPv4 Network ready IP: 192.168.1.100
Call tree (using lwip v2.0.2)
tcpip_thread, msg->msg.inp.input_fn(msg->msg.inp.p, msg->msg.inp.netif); ( line 134)
ethernet_input, etharp_input(p, netif); (line 199)
etharp_input, pbuf_free(p); (line 739)
I tried the same example with ThreadX and NetX Duo (my application needs FreeRTOS btw). If i run the application I get the stats message repeating:
stats: up_num=94 up_time=13165 max_up_time=0 wait_up_time=696 cpu_timer(cold=115601560 warm=0) pmu_timer(cold=112578747 warm=0)
wiced_network_save_dhcp_state_for_deep_sleep
If i debug the application then I hit an assert statement in wiced_network_resume_layers: wiced_assert("WICED can't resume DHCP client", 0 != 0 );
I have verified that pings do not work through wireshark monitoring and monitoring current consumption on a scope.
Show LessHi,
During my tests SMTP, we used several email servers. In one of them we noticed that the TLS protocol simply hangs.
This happens while using smtp.office365.com server. I debugged the code and discovered that I got stuck in function wiced_tcp_start_tls function, more specifically in the ssl_handshake_client_async call that is inside the wiced_generic_start_tls_with_ciphers (WICED\security\BESL\host\WICED\wiced_tls.c) function.
I sniffed the communication with Wireshark and compared it to other TLS connections that worked without any flaw. See the comparisson below:
OK connection (10.0.2.105 is our SMTP client):
# Time Source Destination Protocol Len Info
80 200.741399186 10.0.2.105 64.233.190.108 TLSv1.2 166 Client Hello
81 200.806354972 64.233.190.108 10.0.2.105 TCP 54 587 → 44159 [ACK] Seq=250 Ack=137 Win=60928 Len=0
82 200.807557616 64.233.190.108 10.0.2.105 TLSv1.2 1484 Server Hello
83 200.807665543 64.233.190.108 10.0.2.105 TLSv1.2 1362 Certificate, Server Key Exchange, Server Hello Done
84 200.812398331 10.0.2.105 64.233.190.108 TCP 60 44159 → 587 [ACK] Seq=137 Ack=1680 Win=7168 Len=0
85 200.963590875 10.0.2.105 64.233.190.108 TCP 60 44159 → 587 [ACK] Seq=137 Ack=2988 Win=7168 Len=0
86 201.027162462 10.0.2.105 64.233.190.108 TLSv1.2 129 Client Key Exchange
87 201.034224390 10.0.2.105 64.233.190.108 TLSv1.2 60 Change Cipher Spec
...... communication goes on.....
Failed connection (10.0.2.105 is our SMTP client):
# Time Source Destination Protocol Len Info
31 39.003257162 10.0.2.105 52.97.71.146 TLSv1.2 166 Client Hello
32 39.024934963 52.97.71.146 10.0.2.105 TCP 1514 587 → 63509 [ACK] Seq=344 Ack=137 Win=1048560 Len=1460 [TCP segment of a reassembled PDU]
33 39.027059613 10.0.2.105 52.97.71.146 TCP 60 63509 → 587 [ACK] Seq=137 Ack=1804 Win=7168 Len=0
34 39.046741405 52.97.71.146 10.0.2.105 TCP 1514 587 → 63509 [ACK] Seq=1804 Ack=137 Win=1048560 Len=1460 [TCP segment of a reassembled PDU]
35 39.046814461 52.97.71.146 10.0.2.105 TLSv1.2 1048 Server Hello, Certificate, Server Key Exchange, Certificate Request, Server Hello Done
36 39.070273930 10.0.2.105 52.97.71.146 TCP 60 63509 → 587 [ACK] Seq=137 Ack=4258 Win=7168 Len=0
...... firmware hangs. No further message from client
Notice that in second example the 'Server Hello' is sent in same message as certificate, key Exchange ... 'Server Hello Done'.
Did anybody face the same problem? Is there any reported issue in TLS implementation for this case?
My environment:
- BCM94343W_AVN
- WICED Version: 5.0.0
Thanks in advance,
Reynaldo
Show LessHi all,
I have a requirement to read the Wifi password on a WICED device, then pass it to another WICED device using a non-wifi communication link. However, it looks like I always read out a ciphered password of length 64 (using wiced_dct_read_lock), although a plain-text password is written to DCT_WIFI_CONFIG_SECTION (using wiced_dct_write). I am using WICED SDK 3.1.2 and WPA2 security.
Questions:
1. I supposed this is the correct behavior of a WICED device. If not, please explain.
2. How do I get a plain-text password by reading from DCT_WIFI_CONFIG_SECTION?
Thank you!
Show LessI am working on a project using an the ISMART43340-C from Inventek Systems. This evaluation board has a CYW43340 module. This module is suppose to replace a different module currently used in the host device. The host device sends the raw data frames over UART to the module which has to pass them along to lwIP. It does so by accessing the link output and input from the set netif. Can I do the same with the WICED SDK? Are there any examples that can help me get on the right path?
Show Lesswhich two of the default I/O controls of CYW54907 are specifically used to control T/R switch?
what's 1ps module I/Os to control the Pin 233 and pin 239 TR switch?
hi,
currently i'm using CYW954907AEVAL1F development board with wiced IDE. it's based on CYW54907 chip which is inside LBWA1UZ1PS-241 module.
but now i want to make my custom board by using CYW54907 chip. but when i refer CYW954907AEVAL1F board schematic then it have a LBWA1UZ1PS-241 module.
as per i check LBWA1UZ1PS-241 module details in Murata.
LBWA1UZ1PS-241 = CYW54907 + 37.4MHz external oscillator section + TR Switch section(SPDT + Diplexer) //as per below link
https://wireless.murata.com/datasheet?/RFM/data/lbwa1uz1gc-958.pdf
now, i know about 37.4MHz oscillator section..
but.. now i need to some more information for TR switch section. it's i think that a simply logic for make a common antenna for 5G and 2.4G frequncy.
i'm worried about "ANT0_DIV_RF_SW_CTRL_4" and "ANT1_DIV_RF_SW_CTRL_5" pins about antenna which is comes from "WRF_PAOUT_2G", "WRF_RFIN_2G" and "WRF_PAOUT_5G" , "WRF_RFIN_5G"..
have you any reference design for this things(TR switch)..
or have you reference design or application circuit for CYW54907 with this TR switch section. so, we can make our own product.
thanks
jignesh narola
Show LessHello support,
I have a doubt related to Vbat and Vddio:
- What is the purpose of Vbat? And the purpose of Vddio?
- What is the difference between them?
I've done the measurements of power consumption according to Low Power Current Measurements Using CYW943907AEVAL1F, but the lowest power consumption I obtained/measured was 30.7uA (on Hibernation, with attached hibernation.c). Is this correct? According to datasheet it has to consume 3uA when Hibernation...
Additional doubt
Furthermore, I would like to know if the current consumption measurements have necessarily to be done as it is specified on Low Power Current Measurements Using CYW943907AEVAL1F. If so, then, what is the purpose of the following pins?:
Thanks in advance,
Kepa
Show LessHi!
I try to adapt "the flagship" demo firmware of PSoC 6 WiFi-BT Pioneer Kit:
"CE222494_PSoC6_WICED_WiFi_Demo"
My first change will be simply modification of initial IP address of PSoC (used when it starts and temporary works as the AP).
By default we have 192.168.0.1. I intend to play with last figures.
I tried to dig a little in the codes to find that phrase... but honestly i feel lost now
I found a lot of instances which appear to be the target of modification…
C:\Users\____\WICED-Studio-6.2\43xxx_Wi-Fi\apps\demo\wifi_onboarding\wifi_onboarding.c
C:\Users\____\WICED-Studio-6.2\43xxx_Wi-Fi\libraries\utilities\connection_manager\connection_manager.c
C:\Users\____\WICED-Studio-6.2\43xxx_Wi-Fi\libraries\daemons\device_configuration\device_configuration.c
C:\Users\____\WICED-Studio-6.2\43xxx_Wi-Fi\libraries\daemons\DHCP_server\unit\dhcp_server_unit.cpp
C:\Users\____\WICED-Studio-6.2\43xxx_Wi-Fi\libraries\utilities\command_console\wifi\command_console_wifi.c
INITIALISER_IPV4_ADDRESS( .ip_address, MAKE_IPV4_ADDRESS( 192,168, 0, 1 ) ),
Which one is correct? Is there one definition of that address?
I couldn’t find it…
Just to avoid some obvious questions:
The purpose of that silly modifications... is just the conflict with one of the router I use (I was to lazy to change its default address…)
Show LessI have been storing user data in APP DCT. However, it appears that the avail. space is limited to ~ 4KB on the CYW943907AEVAL1F.
Therefore, I am interested in using free sectors in the 8MB of SPI Flash for storing nonvolatile data. I have dug around the forum and the SDK code and haven't come up with a good strategy for this. I have come across spi_flash.c, but it isn't clear to me how to preserve sectors in Flash during the build for this, or how to access this space using the routines provided.
Has anyone done this, and if so, do you have any recommended methods/function calls? I think the minimum would be:
1. Allocate sectors in SPI flash during build.
2. SPI flash functions to: erase sector, read sector and write sector.
Thanks!
Show Less