Wi-Fi Combo Forum Discussions
Hi,
I am using WICED Wifi BCM943362WCD4 eval board to interface with RS 485 through UART. I am using IC SP3485CP (Half duplex RS 485 Tranceiver) based circuit for communication between RS 485 bus and WICED board.
I want to use the RTS pin in WICED_UART_2 to control the direction in Tranceiver (SP3485CP). But whenever I transmit bytes from UART, I cannot see any change in the voltage level of RTS pin .
I have configured UART as shown below.
wiced_uart_config_t uart_config_meter_tx =
{
.baud_rate = 9600,
.data_width = DATA_WIDTH_8BIT,
.parity = EVEN_PARITY,
.stop_bits = STOP_BITS_1,
.flow_control = FLOW_CONTROL_RTS,
};
wiced_uart_init( WICED_UART_2, &uart_config_meter_tx, &rx_buffer_one );
I transmit bytes using the following function.
wiced_uart_transmit_bytes( WICED_UART_2, (const char *)tx_data, 7)
The bytes are getting successfully transmitted as seen on CRO on Tx pin of UART but RTS is not seen to toggle. (As per platform.c WICED_GPIO_11 is the RTS pin which I am monitoring)
Any idea how to get this working or is RTS pin not connected in this board?
Thanks.
Show LessHow can I limit the WiFi-data-rate?
I tested as below but it seems like that it didn't work well.
- WICED SDK 2.4.0
- Application : Apps/test/console
- Test Log
Started ThreadX v5.5
Initialising NetX v5.6
Creating Packet pools
Starting Wiced v2.4.0
WWD SDIO interface initialised
WLAN MAC Address : CC:52:AF:xx:xx:xx
Console app
> set_data_rate 11
> get_data_rate
data rate: 11 Mbps
> join DIR-636L wpa2 12345678 192.168.4.91 255.255.255.0 192.168.4.1
Joining : DIR-636L
Successfully joined : DIR-636L
IPv4 network ready IP: 192.168.4.91
>
But when I checked the rate in the AP(which WICED-module associated to), the rate always was 65M.
What did I do wrong?
Is it a bug or something of "apps/test/console"?
Thanks in advance, Steve
Show Less(1) connect to 192.168.0.1
(2) scan network find webpage block
Hi,
We are using BCM9WCDPLUS114 board and test.bt_smartbridge_console app
Is there any ways to retrieve the rssi value to see how close we are to the peripheral devices?
Thanks~
Ken
Show LessI've been trying to run the WiFi Direct sample application (p2p) in the WICED 2.4.0 SDK but so far without success. After building and loading the application I am unable to discover the WICED board with my smart phone and see no probe requests when I run a wireless trace. The console output looks like:
Platform BCM943362WCD4 initialised
Started ThreadX v5.5
Initialising NetX v5.6
Creating Packet pools
Starting Wiced v2.4.0
WWD SDIO interface initialised
WLAN MAC Address : 02:0A:F7:50:BF:8D
STA MAC: 00:00:00:00:00:00
The zero MAC address looks a bit odd, but I haven't touched anything that would affect it. I've successfully built and run a couple of the other sample applications (scan and ap_clients_rssi) so I know the SDK is installed properly.
Show LessI am having problems using Soft AP for WiFi configuration with iOS7. The iDevice gets a valid IP address in the 192.168.0 network but pages are not loaded. They seem to stop half way through. I have been using the same (WICED SDK 2.4) code with iOS 6 without problems. Does anyone have any suggestions?
Show LessGreetings,
I have refer to SDK 2.3.1 example - tcp_client develop simple program, the behavior just like echo service.
WICED client send data to network server, server response acknowledge and other information to WICED device.
After work finish, close socket and restart new socket connetion.
My build target string is : snip.tcp_client-BCM943362WCD4-FreeRTOS-LwIP-debug download run
It work normal on SDK 2.3.1 but failed on SDK 2.4.0.
SDK 2.4.1 only first request success and others failed.
I compare the function - wiced_tcp_disconnect() between 2.3.1 and 2.4.0.
SDK 2.4.0 use netconn_close() close socket, SDK 2.3.1 use netconn_delete().
SDK 2.4.0 :
if ( netconn_close( socket->conn_handler ) != ERR_OK )
{
return WICED_ERROR;
}
SDK 2.3.1 :
netconn_delete( socket->conn_handler );
socket->conn_handler = NULL;
socket->is_bound = WICED_FALSE;
In debug mode, netconn_close() look success, but next connection request by calling wiced_tcp_connect() always failed.
Could anybody discuss what happened in wiced_tcp_disconnect() and wiced_tcp_connect().
Thank you.
Eugene
Show LessI was reviewing the changelog for wiced 2.4.1 and saw a change that might be interesting for us. The changelog states :
"LwIP wiced_tcp_connect() now connects successfully without socket re-initialization."
We were seeing some failures to create sockets on the first attempts, and so I merged LWIP from wiced 2.4.1 over LWIP from wiced 2.4.0 and nothing significant that would affect wiced_tcp_connect seems to have changed. I also looked at netconn_connect, and nothing changed.
Any insight at what this message in the changelog actually means?
Show Less