Wi-Fi Combo Forum Discussions

I am trying to get one of the make targets downloaded to a Murata SN8200 module using a Segger J-Link JTAG probe but I only get the error message starting with:

**** OpenOCD failed - ...

There seems to be some configuration info missing for using J-Link.

I have tried this on both OS X and Windows and get the same kind of error message. My JTAG i a J-Link Ultra+.

in the C file:

#include "sntp.h" 

    sntp_start_auto_time_sync( 1 * DAYS );

in the makefile:

$(NAME)_COMPONENTS := protocols/sntp

Compiles fine, but the linker cannot find the function I called: "undefined reference to `sntp_start_auto_time_sync'"

I looked in the build directory (Modules/Library/protocols/sntp) and I can see the snap.o file, compiled at the right timestamp.

The .o contains the string "sntp_start_auto_time_sync"

What's missing? What other info does the linker need?

[Update: If I run make clean, and then try again, the compilation is successful. Why?]

Please find SDK Version 3.1.1 here:

Broadcom WICED Software Development Kit 3.1.1

Please find SDK Version 3.1.1 w/HomeKit Version is here:

Broadcom WICED Software Development Kit 3.1.1 with HomeKit

If you had access to previous HomeKit versions, you should not have any issue.

If you need access please send a message to gangi with your MFi Account number which can be found in the upper left hand corner of the Apple MFi portal at mfi.apple.com.

Enjoy!

Hi,

We have Discover Wi-Fi SN8200X module eval board from Element14 and WICED SDK-2.4.0 patched with SN8200x patch in Linux.

We are using UART to communicate with an external device (Baud - 9600, Parity - even, 1 stop bit,  Flow control disabled). The board sends command and device responds with requested bytes. This happens fine initially.

But after some random time (may be 10 mins, 1 hr, 4 hrs or never - Very inconsistent), we observe that the wiced_uart_receive_bytes() function fails (returns WICED_ERROR).  Through CRO we can see that UART is actually seeing the bytes at its input lines.

We are not using ring buffer in code (optional_ring_buffer is NULL) to receive bytes.

Once the above stated problem happens, we had to reset the board to make it working (but soft reset does not work).

When we saw the definition of wiced_uart_receive_bytes() function, we found that when not using ring buffer, the wiced_uart_receive_bytes() function calls platform_uart_receive_bytes() function which always returns WICED_SUCCESS in definition.

But we are facing  WICED_ERROR from the function after sometime. How this happens ? Are we missing something? Please help in this regard.

Thanks in advance.

Hi sir,

I want to use WICED_SPI_1 interface to connect to a slave devcei. And I have some questions as below,

1. Does MISO and MOSI need to combine, then connect to slave's SDO pin?

2. Does software need to modify for 3-wire SPI communication?

The SDK version that I used is 2.4.1.

The board that I used is BCM9WCDPLUS114.

Thanks.

Hi

I see from the latest release notes that the STM32F1XXX are currently not supported. Is there any advance information about when support for those devices might be added? My situation is such that i need to find a module to which i can communicate to with SPI ( i cannot use the SDIO interface as those pins are occupied) on an STM32F103VF running FreeRTOS. Im currently aiming for a muRata sn8000ufl module for my product.

Best regards

Martin