Wi-Fi Combo Forum Discussions
I saw in the below some thread that <WICED SDK 3.0> will be released soon (in a month).
But, yesterday <Broadcom docSAFE> noticed me that <WICED SDK 2.4.1> just released officially.
I'm confused.
Does <WICED SDK 3.0> mean <WICED SDK 2.4.1>, in fact?
or
Will <WICED SDK 3.0> be released, apart from <WICED SDK 2.4.1>?
If so, is there anybody who know the official release schedule of <WICED SDK 3.0>?
Show LessWhen I use 9bits (8bits and parity) data like below, USART doesnt work properly with WICED SDK 2.2.1.
uart_config = { .baud_rate = 115200, .data_width = DATA_WIDTH_9BIT, .parity = EVEN_PARITY, .stop_bits = STOP_BITS_1, .flow_control = FLOW_CONTROL_CTS_RTS, };
In stm32fXxx_platform.c, DMA is configured as following around line.1099.
if ( config->data_width == DATA_WIDTH_9BIT ) { dma_init_structure.DMA_PeripheralDataSize = DMA_PeripheralDataSize_HalfWord; dma_init_structure.DMA_MemoryDataSize = DMA_MemoryDataSize_HalfWord; } else { dma_init_structure.DMA_PeripheralDataSize = DMA_PeripheralDataSize_Byte; dma_init_structure.DMA_MemoryDataSize = DMA_MemoryDataSize_Byte; }
It should be fixed as below I think.
if ( config->data_width == DATA_WIDTH_9BIT ) && ( config->parity == NO_PARITY ) ...
Could you check this and give me your feedback?
Show LessI am interested in using I2C to communicate to a peripheral, however when I look in Wiced/Platform/common/ARM_Cortex_M3/STM32F1xx/stm32f1xx_platform.c, the I2C functions are essentially unimplemented. I am using the Murata SN8200 which has an STM32F103 processor and SDK version 2.4.0.
Are the I2C functions implemented for the ARM M3 in 2.4.1 or 3.0, or should I implement them myself?
*Edit* Looking again, it seems that the STM32F2xx (also ARM Cortex M3) does have I2C implemented. How reasonable is it to assume I could get it working on STM32F103 by copy pasting that code and simply changing the GPIO ports it associates with SCL and SDA?
Show Less
If BCM943362WCD2 was a SoC, the solution will be better.
Hello,
I’m trying to figure out if the WICED module can be put into a “monitor” or “promiscuous” mode, where it sends all packets to the host MCU (regardless of the intended destination of the packet).
Thanks for any assistance!
Show LessOur application sometimes fails to return succes when making calls to wiced_wifi_scan and wiced_wifi_get_rssi. This occurs very rarely but when it does happen, no wiced calls can return. It's also important to mention that when the failures occur, it does not seem to impact our ability to transmit or receive on our lwIP sockets.
Does anyone have insight on what can cause these calls to fail? (i.e. a condition we might be violating)
Show LessWhy download the installation package(WICED-SDK-2.4.1-IDE-Installer.exe) of not more than 3M? Under several times are the same? Please send me a to my mailbox sunshine@sziton.com,Be badly in need of this version to verify a problem,thank you!
Show LessWe have a socket defined as follows:
lwip_setsockopt(SSocket, SOL_SOCKET, SO_RCVTIMEO, &recv_timeout, sizeof(recv_timeout));
lwip_setsockopt(SSocket, IPPROTO_TCP, TCP_NODELAY, &recv_timeout, sizeof(recv_timeout));
It seems that sometimes, when we call
recvLen = lwip_recvfrom( SSocket, receive_buf, sizeof( receive_buf ), MSG_PEEK, NULL, NULL );
we do not always see data that should be on the socket. We have wiresharked the connection to make sure that the data is present. We see our request go out, and quickly see the response come back (100ms or so), but lwip_recvfrom can take up to three seconds before it reports that there is something on the socket.
Has anyone else experienced this? Does the BCM43362 do internal packet stacking because our packets are fairly small (<60 bytes)?
Show LessWICED SDK v2.4.0 (I also looked in v2.4.1 and its still there) in file: WICED\Wiced-SDK-2.4.0\Wiced-SDK\Wiced\Network\NetX_Duo\wiced\tcpip.c, function wiced_tcp_listen(), line 303. Interface is hard-coded to WICED_STA_INTERFACE.
The setup: bring up both the STA and AP network. Start an STA http server. Now attempt to start an AP http server. This will fail with a WICED_ERROR returned from wiced_tcp_listen() because the STA socket has already been initialised, and due to the hard-coded interface, that's the only socket checked by wiced_tcp_listen(). I haven't tried it, but I suspect that you could also erroneously create two or more AP http servers because of this bug.
Effect: Using NetX Duo, I can start both an AP and STA http server only if I start the AP server first, the other way around the AP http server does not start.
Note: This doesn't occur using NetX
Show LessHi All
I found the demo snip.easy_setup/easy_setup_client/easy_setup_cooee.exe was not open source.
And the aes_ccm_decrypt in SDK was not open source also.
For Present Demo Algorithm, we wanna know if the algorithm is standard or encapsulated by broadcom ?
Calculate Base:
nonce(8Bytes) + "wiced"(5Bytes)
Device_secret_key(Device_Vendor_ID)
AAD(Header)
PlainTex
Result: Header+CipherText+MIC.
Result = > Array
Multicast Address 4 and 5 store Cipher data.
802.11Header : Frame:Duration: 01:00:5E:7E:Array[0]:Array[1]:Address2:Adress3
802.11Header : Frame:Duration: 01:00:5E:7E:Array[2]:Array[3]:Address2:Adress3
................
...............
802.11Header : Frame:Duration: 01:00:5E:7E:Array
WICED MODULE filter the Multicast IE header and distill the Array[0-N].
CipherArray= Array
Array[0-9], 10bytes is Plain text, we can get nounce 8byte, content length of cipherText.
Device_secret_key is stored in DCT, we can get, the demo preset value is "abcdabcdabcdabcd"
AAD is from first 10bytes plain text
Array[10-N] is ciphered text.
call "aes_ccm_decrypt" we can get de-encrypted plained text. it is TLV. so we can get ssid and password.
If the Source code for calculating the CipherTex or static lib of algorithm can be released? So that we can develop the Client Configuration APP.
Regards
Harry
Show Less