Wi-Fi Combo Forum Discussions

Hi,

I am using Wiced SDK 3.5.2 and E2Studio as a development environment. This version does not support configuring BCM4343 in a Central role. 

I am Using BCM43907WCD2 platform of WICED SDK for my device BCM43907 device.

In WICEDSDK4.0 =>43xx_WiFi=>Platforms=>BCM43907=>Platform.c file =>

const platform_i2c_t platform_i2c_peripherals[] =

{

    [WICED_I2C_1] =

    {

        .port                    = BCM4390X_I2C_0,

        .pin_sda                 = &platform_gpio_pins[WICED_GPIO_28],

        .pin_scl                 = &platform_gpio_pins[WICED_GPIO_29],

        .driver                  = &i2c_gsio_driver,

    },

    [WICED_I2C_2] =

    {

        .port                    = BCM4390X_I2C_1,

        .pin_sda                 = NULL,

        .pin_scl                 = NULL,

        .driver                  = &i2c_gsio_driver,

    },

};

in platform_i2c_peripherals[] array => WICED_I2C_2 port has both sda and sclk pins are assigned to NULL ? Is this Correct.

I have a I2C slave on this I2C Pheripheral on PINS C1 and B2 which correspond to WICED_PERIPHERAL_PIN_9,WICED_PERIPHERAL_PIN_10

const platform_i2c_t platform_i2c_peripherals[] =

{

    [WICED_I2C_1] =

    {

        .port                    = BCM4390X_I2C_0,

        .pin_sda                 = &platform_gpio_pins[WICED_GPIO_28],

        .pin_scl                 = &platform_gpio_pins[WICED_GPIO_29],

        .driver                  = &i2c_gsio_driver,

    },

    [WICED_I2C_2] =

    {

        .port                    = BCM4390X_I2C_1,

        .pin_sda                 = &platform_gpio_pins[WICED_PERIPHERAL_PIN_9],

        .pin_scl                 = &platform_gpio_pins[WICED_PERIPHERAL_PIN_10],

        .driver                  = &i2c_gsio_driver,

    },

};

Still I am Not able To Probe On This Device . Can anyone Help me on this.

Hello,

We are currently using the BCM4343W chip to handle ble and wifi and using SDK 4.1.

In our BLE profile, we have a characteristic that is used to setup the WiFi.

Obviously, this characteristic is quite big and has 114 Bytes (SSID, Password, Security Type, Static config, etc...)

During our tests, we have no issue to write into this characteristic when using an iOS app.

While using an Android app, the writing is made in smaller chunks, therefore, we get:

• 5 write callbacks (each of 20 bytes long and the last one of 14 bytes

As for the read, we were expecting to get an incremental offset in order to copy the data properly in the characteristic value.

But it is not the case... we get at each callback an offset of 0... Therefore we don't know how we can detect that the write request is not completed hence, the action behind fails because of that.

Is that normal? Shouldn't the offset be incremented in such cases?

We are testing with a generic Android app, is that the app that should increase the offset?

Snip of my Write Callback function:

// Verify that size constraints have been met
if ((ble_gatt_db_ext_attr_tbl.max_len >= p_write_request->val_len) && (p_write_request->val_len > 0))
{
     // Value fits within the supplied buffer; copy over the value at position: Offset
     gatt_db_ext_attr_tbl.cur_len = p_write_request->val_len;
     memcpy(ble_gatt_db_ext_attr_tbl.p_data, p_write_request->p_val, p_write_request->val_len);
     status = WICED_BT_GATT_SUCCESS;
     WPRINT_BT_APP_INFO(("[BLE-WRITE]: Write Request: conn_id:%d hdl:0x%x prep:%d offset:%d len:%d\n ", currentConnection.conn_id, p_write_request->handle, p_write_request->is_prep, p_write_request->offset, p_write_request->val_len));
     // Offset is always 0

Thank you for your feedback!

“In Bluetooth Classic (BR/EDR) systems, a Serial Port Profile (SPP) is an adopted profile defined by Bluetooth SIG, to emulate a serial port connection over a Bluetooth wireless connection. For Bluetooth LE, an adopted profile for implementing SPP over BLE is undefined, thus emulation of a serial port must be implemented as a vendor-specific custom profile”

Has anyone on this forum been successful in implementing a BLE to UART bridge (ie. something similar to Bluetooth SPP / serial port profile) for BLE?

Thanks, - Peter