Wi-Fi Combo Forum Discussions
The compile time to be create a Win32 version of the OpenOCD takes too long time.
When OpenOCD source file is modified the code once, it takes about 30 minutes to create an openocd-all-brcm-libftdi.exe file.
In contrast, the compile time in Ubuntu or OSX doesn't take a long time. (less than five minutes.)
Maybe, It is assumed as a characteristic of Mingw.
Is It possible to build without any problems when the build flag is changed to '-O3' from '-O0'?
Let me know how to increase the compile the speed in MinGW.
Show LessHi! Everyone.
I use WICED-3.5.2 . I want to debug our program. because of no manual about bluetooth in Wi-fi Bluetooth Module.
So I need to debug for program trace.
but debugger directory is only win32. program cannot Debug / arm-none-eabi-gdb.exe --version
How can I do this ?
Thank you!
Show LessUsing BCM943341WCD1.
Trying to look for a good example to upload a pcm file to a cloud endpoint and receiving an mp3 in response.
A bit confused about using wiced_tcp_send_buffer versus wiced_tcp_stream_write.
Show Less
Hello,
i want to ask you a question about wiced_tcp_listen(socket,port). i have created two socket for my application. However, by using wiced_tcp_listen function i want to listen two socket with same port. When i start to compile i have encountered error. if i change port number. There is no error. Do you have any suggestion related with this issue.
Best Wishes
Show LessHello,
We are having discovery kit and connected USI module on SDIO interface. We are using WICED software and eclipse platform. Unfortunately, we are not able to do step by step debugging in this environment. We need to support in enabling this on Discovery Board (STM32F407 Discovery board that embeds a ST-LINK V2 as a JTAG/SWD debugger/programmer) and make sure our custom board supports the right debug interface.
What needs to be enabled in the SDK to enable step by step debugging?
Thank you for your support.
Best Regards.
Nicolas.
Show LessCan someone please confirm that 3.5.2 has an error in the SNTP code in sntp_get_time(...) (libraries/protocols/SNTP/sntp.c:113)? Here, sntp_get_time(...) calls wiced_packet_create_udp( &socket, ...) , but socket is uninitialized (just random stack data). The LwIP code (WICED/network/LwIP/WICED/tcpip.c:664) checks the socket->dtls_context against NULL and dereferences socket->dtls_context (see tcpip.c:669), causing a hard fault.
I saw a similar (but more subtle) error in libraries/protocols/HTTP/http.c:60 in wiced_http_get(...). socket is initialized by wiced_create_socket(...), but wiced_create_socket(...) (WICED/network/LwIP/WICED/tcpip.c:254) does not zero out the structure memory. In fact, it leaves socket->tls_context as a pointer to whatever random data the stack had previously. So the wiced_tcp_connect(&socket, ...) call (http.c:64) fails at when the socket->tls_context is accessed through wiced_tcp_start_tls(socket) call inside wiced_tcp_connect(...) (tcpip.c:1034).
As a user of the API, I expect wiced_create_socket(...) to fully initialize the socket structure to default (ie, non-TLS) operation. Only wiced_enable_tls(&socket) should modify the socket->tls_context variable and change it to a non-NULL value.-- right? I found I can fix the wiced_http_get(...) function and pull it into my application by adding a memset(&socket, 0, sizeof(socket)) call before wiced_create_socket(...).
Most of my ported code works in spite of these issues. But I'm guessing that is because in my application, most connections come from a global .bss memory space and are initialized to zero by libc.
I can fix these problems in the SDK, but I'm concerned about making too many modifications to code outside of my /apps/..., as the code will get clobbered by changes in future SDK versions.
Comments/confirmation of these errors would be appreciated. Or (if unconfirmed), just tell me how to get SNTP working reliably. Thanks!
Show LessBRCM announced this IC. https://www.broadcom.com/products/wireless-connectivity/bluetooth/bcm43012
This looks like a fantastic piece of technology and inquiring minds wondering when we can see the first eval kit and Wiced support becoming available?
Show LessHello,
I am working with SN8205 and Wiced SDK 3.5.2.
For using IBM Bluemix there is perfectly explanation on below link:
WICED IBM IoT Bluemix quickstart
Which i have followed and got worked demo code for Light sensor(I have not attached light sensor but passed random values which is uploaded to web.)
But now when i have changed
Demo application #define MQTT_BROKER_ADDRESS "quickstart.messaging.internetofthings.ibmcloud.com" | |
#define WICED_TOPIC "iot-2/evt/iotsensor/fmt/json" | |
sprintf(clientId_buffer, "d:quickstart:iotqs-sensor:%02X%02X%02X%02X%02X%02X", mac.octet[0],mac.octet[1],mac.octet[2],mac.octet[3],mac.octet[4],mac.octet[5]); |
My application
#define MQTT_BROKER_ADDRESS "0hjmsp.messaging.internetofthings.ibmcloud.com" (Orgnation Id.messaging.internetofthings.ibmcloud.com) | |
#define WICED_TOPIC "iot-2/evt/intex_Mobile/fmt/json" | |
sprintf(clientId_buffer, "d:0hjmsp:intex_Mobile:sigma1"); |
Where client ID is Orgnazation_ID.Device_type.Device_ID.
Then I'm getting below print on Terminal.
===========================Terminal Log===========================
Initializing Light Sensor
[MQTT] Opening connection...Client ID...d:0hjmsp:intex_Mobile:sigma1
Client ID...d:0hjmsp:intex_Mobile:sigma1
---- Success
[MQTT] Publishing...Light value 2021
Message :{"d":{"name":"WICED4343W","amb_light":2021}}
Wait for response error
Wait for response error
Wait for response error Failed publish
===================================================================
On the server side i'm getting error log in device detail
Invalid userID () for device auth: ClientID='d:0hjmsp:intex_Mobile:sigma1', ClientIP=59.95.32.254 | Apr 11, 2016 2:22:05 PM |
Closed connection from 59.95.32.254. The operation is not authorized. 4 times in the last 5 minutes | Apr 11, 2016 2:22:05 PM |
Invalid userID () for device auth: ClientID='d:0hjmsp:intex_Mobile:sigma1', ClientIP=59.95.32.254 | Apr 11, 2016 2:22:07 PM |
Closed connection from 59.95.32.254. The operation is not authorized. | Apr 11, 2016 2:22:07 PM |
Message | Timestamp |
---|---|
Invalid userID (teksun.krishna@gmail.com) for device auth: ClientID='d:0hjmsp:intex_Mobile:sigma1', ClientIP=59.95.32.254 |
I have also tried by using my username and password in mqtt_conn_open even if this error there.
Also tried using Authentication Key and Authentication Token Key.
So how to provide authentication it seems we can pass private key and ca_certificate key but i'm not finding where to get these certificates.
Regards,
Prashant
Show LessHi, BRCM experts,
I am now trying port Wiced-3.1.1 on my STM32F407 board with BCM43341, by adding my own WICED-SDK-3.1.1/platforms/MY43341/platform.c, and would like use USART1 as stdio port, but looks like it is not works. I tracked the code, it trapped into wiced_init() and never turns back. But if I use USART6 as stdio port, it works fine, my app runs without any problem. Any suggestion?
Thanks!
Show LessHello, I started to use wiced 3.5.2 and a lot of lines are mark as error (specifically when I write something like WICED_GPIO_x or WICED_ADC_x), the code compile fine but it's really bothers me.
Anyone got this problem? It can be fix?
Thank you
Show Less