Wi-Fi Combo Forum Discussions

Hi

I try ssl connection and every thing looks good, but when I tested correct certification I saw that Wiced doesn't check the hostname form public serwer certificate with lookup domain.

In wiced_tls_init_simple_context we set peer_cn e.g "mydomain.com"

     context->context.peer_cn = peer_cn;

In wiced_tcp_enable_tls context pointer is assigned to socket.

    socket->tls_context = context;

And until this moment everything looks great but next, in wiced_tcp_connect() when we socket->tls_context != NULL runs wiced_tcp_start_tls() next wiced_tcp_start_tls_with_ciphers() and first line we have

memset( &tls_context->context, 0, sizeof(wiced_tls_context_t) );

Probably in ssl_init performs zeroing of context too

And now my question, is any idea to repair this problem with Wiced function or I must write myself function whitch compare mydomain with decrypted public server certificate because we have this in

tls_context->context.peer_cert->subject.val.p

at the and on wiced_tcp_start_tls_with_ciphers()?

I use SDK 3.1.1.

Best regards

I am using a WICED module in monitor mode filtering for probe requests. I can capture the 802.11 probe request frames but I could not figure out how to obtain the information - specifically the SSI signal - as typically found in the radiotap header.

I understand radiotap is not a standard, and is only a functionality of the driver. Nevertheless, I would appreciate any information on how I can extract the SSI fields in some way through the SDK. I am comfortable in using non-standard and not documented functions, as I am sure such information must be available. I had to resort to non documented functions in the SDK to enable and take advantage of monitor mode in the first place.

Unfortunately, wiced_get_rssi() inside a capture callback host_network_process_raw_packet(), times out. I tried also disabling any filters and in running it from another thread, but it doesn't seem to be working in monitor mode. Perhaps accessing the radio registers is what is needed. I am specifically interested in the RSSI only.

Thanks in advance.

-Marco G.

I am trying to test the sflash wiriting capabilities of wiced.  The tcl script gives an "example" usage:

# source [find mfg_spi_flash/write_sflash.tcl]

# sflash_init "BCMUSI11-SDIO-debug"

# sflash_write_file "example.bin" 0x10 "BCMUSI11-SDIO-debug" 1

# shutdown

However, the first line causes TCL to retrun "FIND: Parameter format not correct"

How do I adapt these scripts for my platform?

Hi Wiced Engineers,

Does the BCM943362WCD4 platform support I2C peripheral access.  I was not able to see initialization of platform_i2c_peripherals in the BCM943362WCD4 platform.c file.   Are there any examples of I2C access.

Thanks

Hi everybody,

I'm working on a murata type YD that includes a BCM43362 (802.11b/g/n) and I would know if there is a possibility to choose one of the b/g/n mode while programming.

I'm using the WICED-SDK-2.4.1 version.

If  you need any further informations please fell free to ask me.

Thank you all

Hi,
  Why Wifi Direct(P2P) is not implemented in SDK 3.1.0 and SDK 3.1.1?
  Is P2P in SDK 2.4.1 reliable?
  Should I go for a P2P in SDK 2.4.1 or a Soft AP implementation from newer SDKs

mcu: stm32f407
chip:bcm43362

Thanks,
Sooraj

Hi,

I am trying to edit the config_http_content in order to achieve following:

At initial startup of the the device, it will run in config mode to allow user to identify the user wifi connection to connect to. This will also be available to the user at any time by pressing a push button. The idea here is that, I would like to automate the connection to STA for the user interactively. I am using appliance app as a basis and making required changes to the library files.

From user's perspective we would like to do the following:

1) User can connect to the Config AP and browse to wiced.com (redirected to AP web server)

2) Goto Wifi scan page

3) Select the Wifi network to connect to and provide password and press "connect" button

4) If connected to the wifi network, the user will be shown the IP address of the device, and the Config AP web server will be shutdown and STA web server started (And if possible the user's browser redirected to the STA interface for other settings that require internet connection)

5) Otherwise, the user will be informed that the connection to the wifi network was not established (Try again)

In Appliance app, first function that is called after wiced_init() is wiced_configure_device(). I have made a new function wiced_configure_device2(), which is a modified version of the original. Also made changes other required functions to achieve the above mentioned behavior.

Now when I press connect, whether with correct password or incorrect one, at the first call XMLHttpRequest returns with readyState 4 and status 0, the ajax fails. When second time connect is clicked, it works. I have defined a new function for connect process which returns the IP address in case of successful connections and "Error" in case of unsuccessful connection, using following:

wiced_tcp_stream_write( stream, "Error", strlen("Error"));

Since I am using library function for STA connection

wiced_network_up( WICED_STA_INTERFACE, WICED_USE_EXTERNAL_DHCP_SERVER, NULL );

it tries is three times before giving up, so can take some time if incorrect password is typed. With correct credentials it is much quicker (obviously). I have noticed that XMLHttpRequest returns status 0 and readyState 4 before the dynamic function has even completed. Thus, the data part is missing (using do_ajax provided). But when the same request is done the second time, it waits until the function completes and then return correct status 200 with data (Error or the IP address).

What could be the cause of this? I have tried to debug this issue but can't figure it out.

Has anyone implemented something similar? Some guidance will be appreciated.

-------------------------------------------------------------------------

Additional information to the original post:

I was able to single out the problematic part of the above process.

wiced_network_up( WICED_STA_INTERFACE, WICED_USE_EXTERNAL_DHCP_SERVER, NULL );

Calling the above function from the dynamic web function (named process_connect2()) makes the request unresponsive. Somehow connecting to an STA interface interferes with the HTTP web server running on CONFIG_AP interface. Is that normal?

I also tried to create a new thread that will take care of STA interface connection setup and return text (via wiced_tcp_stream_t) signifying that thread has been created successfully. Another request is made to another dynamic web function (called process_join_result()) by the client web browser after a 10s delay to retrieve connection status (Error if STA connection was not successful or the new IP address if successful).

But this fix also didn't pan out, as the process_join_result() did not work as it was supposed to and returned the content of the homepage (instead of Error or IP address). It didn't even run this function. The function runs fine if the request is made before the connect request. Also, the device becomes unresponsive and resets by itself, so I am assuming that my thread creation and deletion may not be correct.

--

Omair