Wi-Fi Combo Forum Discussions

My project is having a problem connecting to hidden networks.

The normal API flow is wiced_network_up() which calls wiced_wifi_join() which calls either wiced_wifi_join_specific() or wiced_wifi_join() depending on whether the MAC address is known.

We don't know the MAC address of the access point so the code will go the wiced_wifi_join() route, which makes sense I think.

But even that API call asks for the security type which we don't know.

This information is unknown because hidden networks show up with a null string in the ssid field for the wiced's wifi scan. So if there are X hidden networks in the vicinity, how does one figure out which MAC address to choose? You don't know which one is the right one simply from the generic wifi scan.

I'm not entirely well-versed on WiFi but my understanding is that for hidden networks there is a "direct-scan" which takes form as a probe-request that includes the ssid. The network that has that ssid should reply with a probe-response.

How is this done in Wiced? How do I go about joining a hidden network when the user only provides me with the ssid and key?

Hello,

I want to receive multicast packets on a specific address.

I have joined the mutlicast with the following function:

wiced_multicast_join(WICED_STA_INTERFACE,224.0.0.251);

But how do I receive the udp packets for this address after the join?

I was thinking to use udp_receive with a timer but this requires a socket.

I did a search through the apps folder with this function but can't find an example either, can anyone point me to the function I need to receive those packets after join?

Cheers,

Gerard

Is there a method to determine the remote IP address and socket when receiving TCP packets, so that the info can be properly logged? i.e.: "Received xxx from 192.168.1.110:5000\r\n"

UDP packets can make use of wiced_udp_packet_get_info but there doesn't seem to be a way to do this with TCP packets (there isn't a 'wiced_tcp_packet_get_info' function)?

I was digging into the low level wiced_tcp_socket_t implementation but this differents between NetX and lwip, and even hard-coding struct members from the NetX implementation (yuck) I still didn't get meaningful data back for the remote IP address and socket when TCP data arrives on the test echo server.

For reference sake I think the NetX fields are 'nx_tcp_socket_connect_ip' and 'nx_tcp_socket_connect_port', but this is a terrible approach anyway.

Unless I'm fundamentally misunderstanding something, this seems like a pretty big gap in the API that there isn't an easy way to get access to the remote IP address.  If there is an example of how to do this, can you please point me to it or provide a simple code snippet showing how we can log this info in something basic like the TCP echo server provided?

I am using stm32f429 for my custom board which is interfaced to SN8000x module.

I want to use the SPI4, in the STM32F429 , but as per the stm32f4xx_rcc.h file only upto SPI1-3 is supported.

So how can I add the support for SPI4 instm32f4xx_rcc.h file ?

Is that only needed or do I have to edit any other files in order to achieve this(some kind of .ld files).