Wi-Fi Combo Forum Discussions

[WICED_SDK-2.3.1]

Im trying to setup a CA store with wiced_tls_init_root_ca_certificates (taking a valid CA cert from my system), but it fails inside x509parse_crt with error -416.

Unfortunately, there is no source for the SSL library bundled with the SDK (besl?).

Is there an API reference for it somewhere to lookup error codes?

SDK has the facade API for TCP (wiced_tcp_stream_*), but the stream read function is missing. Whats the status of this API? Is it being incomplete, or is it deprecated? There is also `wiced_tcp_send_buffer`, which seems to have similar semantics to `wiced_tcp_stream_write` + `wiced_tcp_stream_flush`, hence the confusion.

I was using Wiced 2.3.1 on a WCD8 eval board, running ping_powersave.  This all worked OK.  

I changed the WCD8 makefile to enable wait_mode_support, according to the Readme.txt.

* ^BCM943362WCD8 : OpenOCD Limitations with Power Save       OpenOCD is unable to wake up and halt the ARM Cortex-M3 CPU of the AT91SAM4S       MCU when the MCU enters deep sleep mode. Consequently, the powersave feature       for BCM943362WCD8 is disabled by default. It can be enabled by uncommenting       GLOBAL_DEFINES += WAIT_MODE_SUPPORT in <WICED-SDK>/Wiced/Platform/BCM943362WCD8/BCM943362WCD8.mk.       This issue will be addressed in a future SDK release.

After this, I got OpenOCD errors.

**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

I tried a clean build, unplugged/plugged the board, rebooted PC, no luck.

I tried a USI09 eval board, it worked fine.

Any idea why the Atmel SAM4 board appears to be bricked?

[WICED_SDK-2.3.0]

Hello,

I have ST-Link/v2 JTAG programmer tool. Is it possible to programme 943362 via ST-Link ?

Thanks.

# Environments

- WICED Version 2.3.0

- ThreadX + NetX_Duo

- BCMUSI11 Platform

- BCM43362

Hi

We are trying to use high-speed UART and SPI. The concept is that

when data come from UART or SPI, it is sent through the Wi-Fi (and vice versa).

We are now facing with a critical interrupt problem.

When there is data traffic through the Wi-Fi, If I send a lot of data through the UART,

sometimes interrupt is not called. It is very small but critical. (about 0~30 / 1,000,000 times).

# UART Condition

- baud rate: 921600 or over

- flow-control: None or RTS+CTS

- the other is not changed

# Interrupt count check method

- Add 1 to global counter variable in the usart1_irq function.

  and check it after sending.

# Things I tried (but the problem still exist)

- Changed UART interrupt priority from 57, 68 to 00.

- Removed interrupt-disable function in the stm32f2xx_platform.c and core_cmFunc.h files.

- Uncomment #define WICED_DISABLE_MCU_POWERSAVE in the wiced_defaults.h file.

Do you have any suggestion to solve this problem ?

[WICED-SDK-2.2.1]

Any idea why wiced_tcp_receive() stops receiving after remaining idle for more than 10 seconds?

I have the following simple loop:

while (1) {

        result = wiced_tcp_receive(&cometa_socket, &rx_packet, WICED_NEVER_TIMEOUT);

        if( result != WICED_SUCCESS ) {

            WPRINT_APP_INFO(("TCP packet reception failed

"));

            continue;

        }

        /* Get the contents of the received packet */

         wiced_packet_get_data(rx_packet, 0, (uint8_t**)&rx_data, &rx_data_length, &available_data_length);


         /* Null terminate the received string */

         rx_data[rx_data_length] = x0;

         WPRINT_APP_INFO(("Received:

%s

", rx_data));


         wiced_packet_delete(rx_packet);

  }

The other endpoint can send any number of messages to this loop but if there is a delay of more than 10 seconds between them, nothing is received and the loop hangs at wiced_tcp_receive().

I have an equivalent loop on a linux box connected with the same endpoint that doesnt have this problem.

Any suggestion would be appreciated.

-Marco G.

- WICED SDK 2.3.0

- ThreadX/NetX Duo, BCMUSI11

When <WICED module> receive the mass data via <TCP-connection>, sometimes <NetX or BCM43362> hang up.

Here is my test diagram.

[ATTACH=CONFIG]140[/ATTACH]

Here is the test-screenshots.

[ATTACH=CONFIG]141[/ATTACH]

[ATTACH=CONFIG]142[/ATTACH]

After researching the capture file, I guess that the problem it is related with <TCP Window resize stuff>(WICED_TCP_WINDOW_SIZE). But, because I dont have the NetX source, I could not debug it any more.

Thanks in advance.

Steve

Hello,

I tried to init WICED_UART_2 as seen snip-uart.c application. But it seems it doesnt work, is any other configuration needed ?

[WICED-SDK-2.2.1, 43362]

Why does the softAP interface stop working when I join a network as a client?

Here is what we are trying to do:

1.  Start soft ap server.

2.  On connect send welcome and next button.

3.  On next button press - load the result of wifi scan with select button for each.

4.  User selects the network and types in password which is sent back to app.

5.  AP then calls wifi join.  Right here we get disconnected.