Wi-Fi Combo Forum Discussions
Hi.
I am trying to migrate to SDK 3.1.2 from SDK 2.4.1
By the way result of snip.scan is showing a lot of difference.
Below are the results of 2.4.1
==================================================================
Starting Wiced v2.4.1
Platform BCM9WCDUSI09 initialised
Started ThreadX v5.5
Initialising NetX_Duo v5.6
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : 40:2C:F4:E8:CE:FD
WLAN Firmware : wl0: Feb 10 2014 11:29:55 version 5.90.230.7 FWID 01-555f783e
Waiting for scan results...
# Type BSSID RSSI Rate Chan Security SSID
----------------------------------------------------------------------------------------------
0 Infra 3C:A3:15:01:27:57 -78 54.0 1 WEP ZIO
1 Infra 74:72:F2:31:B9:5B -81 54.0 1 WEP dsinnocar-120
2 Infra 00:08:9F:66:3C:C5 -80 54.0 7 WPA2 AES ss
3 Infra 00:26:66:CA:7B:3C -50 300.0 11 WPA2 AES iptime_UM
4 Infra E8:AB:FA:10:AF:C1 -72 300.0 11 Open Wifi-Repeater
5 Infra 64:E5:99:87:5F:A8 -65 150.0 9 WPA AES iptime_oh
6 Infra 00:26:66:C8:D5:5A -77 300.0 11 Open iptime
7 Infra 90:9F:33:22:5F:14 -54 300.0 8 WPA2 AES RND
8 Infra 64:E5:99:60:7F:9C -64 300.0 9 WPA2 AES ES_700Z
9 Infra 00:0E:2E:E0:CF:88 -53 300.0 6 WPA2 AES ZIO_smart_Zigbee
10 Infra 00:01:36:9E:E2:08 -51 300.0 4 WPA2 AES
11 Infra 00:01:36:9E:E2:06 -51 300.0 4 WPA2 Mixed SK_WiFiE205
Scan complete in 1295 milliseconds
==================================================================
Below is a result of 3.1.2
==================================================================
Starting WICED v3.1.2
Platform BCM9WCDUSI09 initialised
Started ThreadX v5.6
Initialising NetX_Duo v5.7_sp1
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : 40:2C:F4:E8:CE:FD
WLAN Firmware : wl0: Nov 7 2014 16:03:45 version 5.90.230.12 FWID 01-0
Waiting for scan results...
# Type BSSID RSSI Rate Chan Security SSID
----------------------------------------------------------------------------------------------
0 Infra 00:26:66:CA:7B:3C -82 300.0 11 WPA2 AES iptime_UM
1 Infra 90:9F:33:22:5F:14 -92 300.0 8 WPA2 AES RND
2 Infra 00:0E:2E:E0:CF:88 -82 300.0 6 WPA2 AES ZIO_smart_Zigbee
Scan complete in 1566 milliseconds
==================================================================
Why do I have these differences?
I am using BCM9WCDUSI09 Platform
Thanks
Show Less
I am using WICED-SDK-3.1.0. I used encryption TLS1.2 and has two way authentication, Clients connect simultaneously to Server.
I am using Murata EVB. When the module Murata EVB is in STA mode and this module Murata EVB is a Server. There are two other Murata EVB modules are Client 1 and Client 2, I do about transmit and receive data betweent Client 1, Client 2 with Server. Client 1 connect to Server and Client 1 transmit data to Server, Server received data from Client 1, after Client 2 connect to Server and Client 2 transmit data to Server, Server received data from Client 2. But now, when Client 1 continue to transmit data to Server, Server can not get this data which is transmitted from Client 1.
Server use function wiced_https_get to get data from Client 1 and Client 2.
+
if(wiced_https_get(current_event.socket,buffer_receive,BUFFER_LENGTH)==WICED_SUCCESS)
{
WPRINT_APP_INFO(("Received data from Server: %s\n", buffer_receive));
}
+
wiced_result_t wiced_https_get( wiced_tcp_socket_t *socket, void* buffer, uint32_t buffer_length )
{
wiced_packet_t* reply_packet;
wiced_result_t rx_result;
wiced_result_t result = WICED_ERROR;
char* buffer_ptr = (char*) buffer;
rx_result = wiced_tcp_receive( socket, &reply_packet, WICED_WAIT_FOREVER );
if ( rx_result == WICED_SUCCESS )
{
uint8_t* data;
uint16_t data_length;
uint16_t available;
uint32_t data_to_copy;
// Record the fact we received a reply of some kind
// Copy data into provided buffer
wiced_packet_get_data( reply_packet, 0, &data, &data_length, &available );
data_to_copy = MIN(data_length, buffer_length);
memcpy( buffer_ptr, data, data_to_copy );
buffer_ptr += data_to_copy;
buffer_ptr[0] = '\x0';
buffer_length -= data_to_copy;
WPRINT_APP_INFO(("get data\n"));
wiced_packet_delete( reply_packet );
result = WICED_SUCCESS;
}
else
{
WPRINT_APP_INFO(("get data error\n"));
result = WICED_ERROR;
}
return (result);
}
+ The function wiced_https_get call the function wiced_tcp_receive, The function wiced_tcp_receive call the function wiced_tls_receive_packet
When Client 1 continue to transmit data to Server, Server can not get this data which is transmitted from Client 1, I saw the reason is: In function wiced_tls_receive_packet , there is a the function tls_get_next_record returns WICED_ERROR.
Please help me to fix this error. Why the function tls_get_next_record returns WICED_ERROR ?.
+ This function wiced_tcp_receive at location: E:\Tai Lieu\Work Software\WICED-SDK-3.1.0\WICED-SDK-3.1.0\WICED\network\NetX_Duo\WICED\tcpip.c
wiced_result_t wiced_tcp_receive( wiced_tcp_socket_t* socket, wiced_packet_t** packet, uint32_t timeout )
{
WICED_LINK_CHECK( socket->socket.nx_tcp_socket_ip_ptr );
return wiced_tls_receive_packet( socket, packet, timeout );
}
+ This function wiced_tls_receive_packet at location: E:\Tai Lieu\Work Software\WICED-SDK-3.1.0\WICED-SDK-3.1.0\WICED\security\BESL\host\WICED\ wiced_tls.c
wiced_result_t wiced_tls_receive_packet( wiced_tcp_socket_t* socket, wiced_packet_t** packet, uint32_t timeout )
{
wiced_result_t result;
wiced_tls_context_t* context = &socket->tls_context->context;
/* Check if we already have a record which should only happen if it was larger than a packet which means it's stored in the defragmentation buffer */
if ( context->current_record != NULL )
{
wiced_assert( "Something wrong", (void*)context->current_record == context->defragmentation_buffer );
return tls_packetize_buffered_data( context, packet );
}
else
{
tls_record_t* record;
result = tls_get_next_record( context, &record, timeout, TLS_RECEIVE_PACKET_IF_NEEDED );
if ( result != WICED_SUCCESS )
{
return result;
}
/* Check if this record has been defragmented */
if ( (void*)record == context->defragmentation_buffer )
{
return tls_packetize_buffered_data( context, packet );
}
else
{
tls_record_t* temp_record;
uint8_t* packet_data;
uint16_t length;
uint16_t available;
uint8_t* end_of_data;
/* We have a pointer to the current record so we can move on */
tls_skip_current_record(context);
/* Make sure we process every record in this packet */
end_of_data = record->message + htobe16( record->length );
while ( tls_get_next_record( context, &temp_record, timeout, TLS_AVOID_NEW_RECORD_PACKET_RECEIVE ) == TLS_SUCCESS )
{
/* Make the record data contiguous with the previous record */
uint16_t temp_record_length = htobe16( temp_record->length );
end_of_data = MEMCAT( end_of_data, temp_record->message, temp_record_length );
record->length = htobe16( htobe16(record->length) + temp_record_length );
tls_skip_current_record( context );
}
/* Set the packet start and end */
wiced_packet_get_data( (wiced_packet_t*)context->received_packet, 0, &packet_data, &length, &available );
tls_host_set_packet_start( context->received_packet, record->message );
wiced_packet_set_data_end( (wiced_packet_t*)context->received_packet, end_of_data );
*packet = (wiced_packet_t*)context->received_packet;
context->received_packet = NULL;
context->received_packet_length = 0;
}
}
return WICED_SUCCESS;
}
Show Less
Hi guys,
I would like to keep web content (.html, .js) of the web server on external flash in a filesystem.
How do I do it?
I have tried to comment the following line in the BCM943362WCD4.mk file:
INTERNAL_MEMORY_RESOURCES = $(ALL_RESOURCES)
Once built, resources content appear to be in RESOURCE_IN_FILESYSTEM:
const resource_hnd_t resources_apps_DIR_appliance_DIR_top_web_page_top_html = { RESOURCE_IN_FILESYSTEM, 785, { .fs = { 0, "top_web_page_top.html" }}};
Also wifi_firmware is RESOURCE_IN_FILESYSTEM.
However the device cannot join Wi-Fi network after that.
Not sure how to do it correctly.
I would appreciate any help on this.
Oleg
Show LessHi,
We are using the BCM943362WCD4 eval kit, where it is powered up by the USB connection, which is obviously around 5V.
However when we monitored the UART signal lines, the voltage level found to be 1.8V level, can we know is that the right behaviour or is there any settings to be done to make it 3.3V.
As well how about the SPI lines, what would be the voltage level ??
Show LessSummary Issue or question:
We want to add an 128GB SD storage card to WICED, and then we can using WIFI storing and reading file into the SD card via WICED. We plan to use a SDIO to USB adapter chip connect the SD card and the MCU USB port. I think this need implement FAT32 file system on WICED OS. So any suggestion to implement FAT32 file system?
Example code to recreate the bug
N/A
SDK version
WICED SDK3.0.1
HW Platform (if it is a peripheral or MCU issue)
BCM943341WCD1
Development environment usually agnostic, but needed if you have a installer or toolchain issue)
N/A
Log/console output (if needed)
N/A
Sniffer trace (if needed) as an attachment.
N/A
Show LessIs it possible to store the wifi firmware binary on an external spi flash?
How can I write the binary to flash? How do I configure WICED to read it from the spi flash?
Thanks
3.1.2
Show LessWe are MFI developer currently working on AirPlay product. We are desperately trying to get a BCM9WCD1AUDIO_3 evaluation board to test out Broadcom chip with AirPlay audio. However the board is not immediately available for purchase (8 week lead time).
If there are anyone who has the board to spare, please contact me and I'd like to buy from you.
Thank you,
Aki
Show LessHello,
I'm working on moving to a new STM32 platform. We currently have prototyped on the SN8205 platform from murata with success. Now we are moving towards a SN8000 with a STM32F429 MCU. I have been looking at SN8000 WiFi Module with STM Discovery Board and with some help I have managed to get the basic platform up and running, so I can run ex. the GPIO snip and the UART snip.
The next step is to have the SN8000 working, my hope was to test it using the SCAN snip, but I have yet to get it to run.
It seems to die on the "wiced_wifi_scan_networks" call, looking into it it seems to be the "result = wiced_rtos_get_semaphore( &scan_semaphore, SCAN_LONGEST_WAIT_TIME );" line which is, I assume, crashing the STM32.
The connection to the SN8000 module has been checked, double checked and seems to be OK. Has anybody which has connected the SN8000 to a STM32F4xx MCU seen the same? and even better found a solution?
Regards
-Renejos