Wi-Fi Combo Forum Discussions
Hi Everyone...I need your help.
I want to implement a Passive Scan Mode using WICED 3.1.1.
So I changed codes as blow
before..
wwd_wifi_scan( WICED_SCAN_TYPE_ACTIVE..
after
wwd_wifi_scan( WICED_SCAN_TYPE_PASSIVE...
But...I think it's not operate as passive scan mode yet..
Please Let me know what i miss..?
Thansks.
Show LessHi,
I am testing a modified tcp_server snip I have configured the device as WICED_AP_INTERFACE. While the connected client sends a TCP packet every 1ms, after some time (in a period of 10 seconds) the application hangs up. You cant even connect to the access point anymore. No Hard fault or error message is received, the rest of my application is still running fine.
Here is the simplified source for demonstartion:
static void tcp_server_thread_main(uint32_t arg)
{
tcp_server_handle_t* server = (tcp_server_handle_t*) arg;
while ( quit != WICED_TRUE )
{
wiced_packet_t* temp_packet = NULL;
/* Wait for a connection */
wiced_result_t result = wiced_tcp_accept( &server->socket );
#ifdef TCP_KEEPALIVE_ENABLED
result = wiced_tcp_enable_keepalive(&server->socket, TCP_SERVER_KEEP_ALIVE_INTERVAL, TCP_SERVER_KEEP_ALIVE_PROBES, TCP_SERVER_KEEP_ALIVE_TIME );
if( result != WICED_SUCCESS )
{
uartDebugString(("Keep alive initialization failed \r\n"));
}
#endif /* TCP_KEEPALIVE_ENABLED */
if ( result == WICED_SUCCESS )
{
/* Receive the query from the TCP client */
if (wiced_tcp_receive( &server->socket, &temp_packet, WICED_WAIT_FOREVER ) == WICED_SUCCESS)
{
/* Process the client request */
tcp_server_process( server, temp_packet );
/* Delete the packet, we're done with it */
wiced_packet_delete( temp_packet );
#ifdef TCP_KEEPALIVE_ENABLED
uartDebugString(("Waiting for data on a socket\r\n"));
/* Check keepalive: wait to see whether the keepalive protocol has commenced */
/* This is achieved by waiting forever for a packet to be received on the TCP connection*/
while(1)
{
if (wiced_tcp_receive( &server->socket, &temp_packet, WICED_WAIT_FOREVER ) == WICED_SUCCESS)
{
tcp_server_process( server, temp_packet );
/* Release the packet, we don't need it any more */
wiced_packet_delete( temp_packet );
}
else
{
uartDebugString(("Connection has been dropped by networking stack\r\n\r\n"));
break;
}
}
#endif /* TCP_KEEPALIVE_ENABLED */
}
else
{
/* Send failed or connection has been lost, close the existing connection and */
/* get ready to accept the next one */
wiced_tcp_disconnect( &server->socket );
}
}
}
uartDebugString(("Disconnect\r\n"));
wiced_tcp_disconnect( &server->socket );
WICED_END_OF_THREAD(tcp_thread);
}
static wiced_result_t tcp_server_process( tcp_server_handle_t* server, wiced_packet_t* rx_packet )
{
char* request;
uint16_t request_length;
uint16_t available_data_length;
wiced_packet_t* tx_packet;
char* tx_data;
char dbg[64];
wiced_packet_get_data( rx_packet, 0, (uint8_t**) &request, &request_length, &available_data_length );
/* Null terminate the received string */
request[request_length] = '\x0';
/* Send echo back */
if (wiced_packet_create_tcp(&server->socket, TCP_PACKET_MAX_DATA_LENGTH, &tx_packet, (uint8_t**)&tx_data, &available_data_length) != WICED_SUCCESS)
{
uartDebugString(("TCP packet creation failed\r\n"));
return WICED_ERROR;
}
/* Write the message into tx_data" */
tx_data[request_length] = '\x0';
memcpy(tx_data, request, request_length);
/* Set the end of the data portion */
wiced_packet_set_data_end(tx_packet, (uint8_t*)tx_data + request_length);
/* Send the TCP packet */
if (wiced_tcp_send_packet(&server->socket, tx_packet) != WICED_SUCCESS)
{
uartDebugString(("TCP packet send failed\r\n"));
/* Delete packet, since the send failed */
wiced_packet_delete(tx_packet);
server->quit=WICED_TRUE;
return WICED_ERROR;
}
uartDebugString(("Echo data: %s\r\n"));
return WICED_SUCCESS;
}
I am using: Wiced SDK 2.4.1 + LwIP + FreeRTOS.
I also tried the tcp_server_async snipped with the same results.
Is this a known issue? At this point of our development it would be expensive to change to the newer SDK. Would the SDK 3.x solve this?
Show LessRecently ran into a problem after migrating to 3.1.0 from 2.4.1
When WICED_DISABLE_MCU_POWERSAVE is defined, power-cycling the board will bring it into a state shown below:
Starting WICED v3.1.0
Platform BCM943362WCD4 initialised
Started ThreadX v5.6
Initialising NetX v5.7_sp1
Creating Packet pools
Could not set AMPDU parameters
Error 2 while starting WICED!
The application used is snip/apsta (same behaviour on other applications)
I am not sure whether this is related to platform restructuring in 3.1.0, and whether this is intentional/intended behaviour. My suspicion comes from the following statement in WICED/WWD/internal/chips/43362A2/wwd_ap.c:
"For SDK 3.0, and beyond, each chip will need it's own function for setting AMPDU parameters."
Any ideas, tips, or pointers to better understand the problem and why it's behaving this way is greatly appreciated.
Show LessHello,
I'm trying out the snip.scan example app and see that it doesn't find all local APs. The scan result produced lists several APs in the area, but not the office AP.
I'm using SDK 3.1.2, and the app is built using `snip.scan-BCM943362WCD4-ThreadX-NetX-SDIO download run`.
The network that's not being found is 2.4GHz, 802.11n, infrastructure, WPA2 Personal, available as 2 APs on channels 1 and 6. S/N ca. -53/95 dBm.
There are about 20 other APs in the area, so it's quite crowded.
Is there anything I can do to fix the problem, such as settings inside the WICED SDK that might help?
Best Regards,
mat.
Show LessHi
I was using SDK 2.4.1 and was able to download the program to STM32F4 Discovery board using JTAG , (I used a simple LED blink program).
Now I have moved to SDK 3.1.0 and facing some issue while programming via JTAG ,finally followed seyhan's comment to add line reset_config trst_and_srst in /tools/OpenOCD/jlink.cfg , and I was able to download the program to STM32F4 .
But the code doesn't seems to be running. THe LED's are not lighting
What might be causing the issue?
Regards
HpC
Show LessHi,
I was trying to implement IR decoder for decoding the ac remote control signals on ISM43362_M3G using wiced. I was facing some difficulties.It would be really helpful if someone can help me out in figuring what is the problem or if they can share their own implemetation.
I have also attached my code below.
Show LessHello,
I would like to create a proof of concept based on WICED WIFI. I have some WICED1 boards that I can use for prototyping and if all goes well I will use the latest board design before going to the next level but as I said I would like to come up with a proof of concept this week so using what I have on hand would save me time.
Thanks very much,
Gil
Show LessHi!
We're evaluating the BCM4334x platform for use in a real time streaming application over 802.11n. We're noticing a 70-millisecond pause in data traffic every 120 seconds. The pause always follows a Clear to Send signal.
What causes this pause every 120 seconds? How can we configure the interval or disable the behavior?
Thanks!
David
Show Less