Smart Bluetooth Forum Discussions

Hi Sir,

When I try to build the apps "ibeacon_device" and "ibeacon_managed" on SDK2.1.

The following error shows, do I miss something?

Hi,

  Is it possible to change the GATT database from SDK for supporting dynamic GATT database change?

  One of the idea is to support "clone" of other BLE device in 2073x. It will be fine if SW reset to SoC is required after such change.

Hi all,

we're developing a BLE application with a MMP20732 chip mounted together with a STM32F4 processor.

I've read on documents that MMP20732 HCI dedicated UART can be used to download application firmware. Purpose is to program only STM32F4 processor letting its firmware program the BLE chip using this UART.

Problem is that I didn't find documentation about MMP20732 firmware programming procedure and protocol.

Can anyone help me?

Thank you

Franco

Hi Sirs,

I have a question about the 20732.

Assume we have a BLE ready device like mobile, hub...whatever.

We use the 20732 on our devices like the BLE block in the photo.

Then, as the subjects, how many BLE devices can be linked at the same time?

Besides, there is a discussion about the mesh network in other thread.

What kind of the topology of the mesh it talk about?

Best regards,

Fran

In SDK 2.1.0 in hello_client app I noticed that interrupt handler is called always twice on very event. Why is that ?

Hello_sensor app from the same SDK does not have this issue.

The button in hello_client is configured additionally with:

GPIO_BOTHEDGE_INT

and as a result the interrupt handler is called twice when the button is pressed and twice when released.

Hello.

We are developing a BLE demo application using WICED SDK 1.0.1 and BCM20732 tag. In such demo, BLE tag is used as peripheral device, while an Android 4.3 smartphone is used as central device. The goal consists in transferring a binary file from the tag to the smartphone in a reliable way. The file contains encoded data from emulated sensors and peripherals.

My questions are:

- which is the best design for BLE profile, in order to transmit a reliable stream of data?

- which is the maximum net throughput I can obtain?

In our current implementation, we are using two characteristics:

- one notification characteristic: it is used to transmit 20 bytes from peripheral to central

- one control characteristic: it is used by central device to request next data

Using such a simple protocol, we reach very low throughput, just 1.3kbps. Please notice my transmission interval is already 12ms.

What I noticed can really drop the throughput is the fact that on central device - the Android smartphone - reception of notification is asynchronous and enqueued: in case peripheral device sends two notifications too closely, Android's callback is called twice, but the value of the last characteristic is read twice. That's why I had to use the control characteristic to slow down the transfer.

I noticed that one simple way to achieve higher throughput is to use 4 characteristics for notification instead of one, but this solution does not scale well.

Please advice.

In our central device, running SDK 2.0.1, does anyone know why

blecen_cen_cfg.filter_duplicates = HCIULP_SCAN_DUPLICATE_FILTER_OFF;

causes a large tracedump leading to a watchdog reset?

Of course, we could enable filtration, but then we would be missing some advertisements.