Wi-Fi Combo Forum Discussions

I'm trying to send a UDP packet , so I used the sample code udp_transmit from the SDK , but when I checked the time taken to create and send a UDP packet it was showing 7.8 ms , (I toggled a gpio and measuread the pulse width )

This time is much large comapred to wifi throughput, we are expecting a throughbut of 15Mb/s but this can't be achieved if the UDP packet creation and send is taking too much time.

Why is this so? Is it better in any other SDK ?

We are using 3.1.0 SDK with SN8000x EVB

Having been recently introduced to the Broadcom environment through the generous donation of an eval board, I've been attempting to get the module to talk to an I2C peripheral using the GPIO breakout header.  Unfortunately, however, there seems to be quite a dearth of documentation surrounding this interface.

The eval board itself is labeled as the BCM943362WCD4, and in digging through the WICED 3.1.0 SDK I found a folder containing pictures for various platforms.  Given the way the board was labeled the BCM9WCD4EVAL2 folder appeared to be the closest match, however the "bcm9wcd4eval2.jpg" photo contained therein definitely does not match the board I have in my hands - the GPIO header in the picture goes up to 30 pins, while board I have only goes up to 18.  After some digging, the closest match I can come pu with is the BCM9WCD1EVAL1_P400 eval board, upon which the WCD4 module has been attached.

Therefore, my first suggestion might be to better organize these resources.

After evaluating the schematic and identifying the breakout header labels, I was unable to find anything labeled that suggested which pints to use for I2C.  I therefore turned to grepping the SDK folder for the phrase "I2C" and was ultimately encouraged by the table found in platforms/BCM943362WCD4/platform.h, suggesting that I2C1 was available using pins 11(SCL) and 12(SDA) - great!

My attention then turned to setting up a wiced_i2c_device_t object to pass to wiced_i2c_init, at which point I was promptly confronted with trying to determine the .port attribute of this type definition.  wiced_platform.h defines it as a wiced_i2c_t type, and while wiced_i2c_t seems to be defined in platform.h, there doesn't seem to be a corresponding mapping in platform.c.  In fact, I2C doesn't seem to be addressed at all within platform.c, leading me to believe it's not implemented on this platform.

As such, my somewhat long-winded questions are: 1) is I2C configured and enabled on this platform and, if so, 2) can someone be so kind as to provide example code that illustrates configuring, initializing and interacting with an I2C device using this platform?

[WICED-SDK-2.2.1]

On evaluation board BCM943362WCD4 wiced_pwm_start() and wiced_pwm_stop() used for the onboard LEDs, dont seem to have any effect. Unlike specified in the API documentation, with this board the function wiced_pwm_init() starts the PWM.

I want to communicate between two devices, already look the example code in SDK 3.1.2.but I do not know how to port code to my app,Can you provide a example code?  In my app ,one device is group owner,the other is client, it is non persistent group.
my platform is BCM9WCDUSI09.