Wi-Fi Combo Forum Discussions

I am running BCM94343W AVN with build 3.7.0   The device can publish consistently from device to AWS iOT . No issues. However, once I do a device update from AWS to the device ( update shadow ) , the client will never want to receive another request. Eventually the device will reset itself. This is with the standard build and not code changes other than starting it working. the web MQTT client will happily receive multiple shadow updates.

On the device it will enter into the GET Semiphore code after it parses the JSON and never return on the next item in the delta topic ( which does make it into the queue as the MQTT client at AWS sees the update.

Anyone see this issue before? I did not change the JSON either .. just out of the box stuff. I have code that modifies the JSON parser but its not causing the problems.

thanks

rob

Hello together,

I want to use the BCM4343 together with the STM32F411 and developing with WICED. So I have no practical experience with WICED SDK.

While looking into the platform details in the WICED SDK, I mentioned that I2S always specified for BCM4390x platforms. I'm not sure how to include I2S configuration in my platform description.

Can I also use bare register configuration or the default stm peripheral library to implement hardware configuration?

Best regards,

Lennart

Tried to find an appropriate forum section, but nothing seemed appropriate! My question is, what do I have to program in to develop on the WICED platform?

I'm trying to use rfcomm to communicate between a phone as a client and a BCM943341WCD1 board as the server, and it's possible to open an rfcomm connection once. But when the connection is closed, it's impossible to reopen it.

After I detect a close, I do the reopen procedure on the server side, including the code below, but it's impossible to reconnect.

Anybody know how to do it?

Magnus

    wiced_bt_rfcomm_create_connection( UUID_SERVCLASS_SERIAL_PORT,

                                       BT_RFCOMM_SERVER_APP_SCN,

                                       (wiced_bool_t)TRUE,

                                       BT_RFCOMM_SERVER_APP_MTU,

                                       NULL,

                                       &serverHandle,

                                       connection_cb );

    /* Set data callback RFCOMM */

    wiced_bt_rfcomm_set_data_callback(serverHandle, BTDriver::data_cb);

    /* Set event callback RFCOMM, and events to be notified of */

    wiced_bt_rfcomm_set_event_mask(serverHandle, BT_RFCOMM_SERVER_EVT_MASK);

    wiced_bt_rfcomm_set_event_callback(serverHandle, BTDriver::event_cb);

  /* Enable connectablity (use default connectablity window/interval) */

  int ret = wiced_bt_dev_set_connectability(BTM_CONNECTABLE, 0, 0);

  /* Enable discoverablity (use default discoverablity window/interval) */

  ret = wiced_bt_dev_set_discoverability(BTM_GENERAL_DISCOVERABLE, 0, 0);