Smart Bluetooth Forum Discussions

in the hello_sensor app, i tried to change the device name as below:

uint8_t hello_sensor_device_name[]          = "AnLuo";

char    hello_sensor_char_notify_value[]    = { 'A', 'L', ' ', '0', };

after build and download, the device name is still "Hello".

so, how to set the device name of one app?

===

SDK: 2.1.1

Tag: 920737.

app: hello-sensor.

OTA firmware size ~ 11KB.

===

Problem description:

We implement device power-sleep mode (both for low-power and deep-sleep)

we meet some problems that if enabling low-power mode, we dont know how to enable awake
from sleep mode. Besides, if using Hid-off mode, devLpmConfig.wakeFromHidoffInMs = 0 is

to disable timer awake? and GPIO is all off during Hid-off mode?

if in low-power mode, can button interrupt be the awake-trigger for it?

there are some questions summaries:

[low-power mode:]

- What's awake trigger?

- Is any timer awake same as Hid-off like devLpmConfig.wakeFromHidoffInMs for use?

- Can button interrupt be a trigger way?

- GPIO is off or on?

- When into sleep, do we need to kill timer if timer thread is existed before?

[hidd-off]

- What's awake trigger? Ans: use devLpmConfig.wakeFromHidoffInMs = 0 or some value?

- Can button interrupt be a trigger way?

- GPIO is off or on?

- When into sleep, do we need to kill timer if timer thread is existed before?

- it will be like reboot from init code execution?

I'm have a very noise sensitive high gain amplifier for which I'm communicating with via BCM20732s. As I've been designing and debugging trying to keep the RF out of my amplifier, I've found that the biggest problem are transients when the RF transmission power is switched on and switched off. Oddly during the time the RF is on, I don't see disruption. The question I have is what is causing this and how can it be minimized? I believe it must be a very sharp voltage dip/rise on the supply when the RF kicks on/off causing radiation. It is very consistent, always inducing a negative detected impulse when the RF starts up and positive impulse when it turns off. Perhaps someone who works on the PA can comment.  Is there any way to limit the slew-rate of the RF power on transition? I had originally looked for a software solution (i.e. using a gating signal from the chip when the RF is on) unfortunately there is not such signal that can be routed out on the 20732 to indicate the RF is on.  Any help with understanding these transients and minimizing them would be greatly appreciated.

===

SDK: 2.2.1

Tag: 920737.

app: hello-sensor.

===

Description:

Use hello-sensor sample code to test consuming currest (~ uA level) to test how our battery life is.

However, we didn't enable any BT connection and also disable the broadcast of SOC but it still gets

current near 5mA; still high. Is any function call for us to do the SOC power-sleep mode?

Hi

I recently learned that the WICED SDK is integrated with HomeKit from apple. Is there anyway we can make the WICED Sense Bluetooth device integrate with HomeKit using the WICED SDK?

Thanks!

Hi all,

We want to layout a new board using the BCM20737 chip to complete part of our functions. However, we find it extremely difficult to purchase this chip.

I have contacted all the distributors of Broadcom (Mouser, Avnet, Macnica Americans). None of them have this chip in stock. Instead, they have BCM20737S and BCM20736S (48-pin, integrated with crystal etc.).

The BCM20737S (48-pin) has different footprint from BCM20737 (32-pin), also and we cannot find a detailed datasheet of BCM20737S.

So here are the weird things:

1. For the BCM20737 chip, we can find its datasheet from this community, but we cannot purchase it anywhere.

2. For the BCM20737S chip, we can purchase it easily, but we cannot get its datashee so we don't know how to layout.

I also contacted sales office of Broadcom, no one could help. The sale's manager from Mousers try to help me solve this issue. After one and a half hour trying, she gives up finally.

Similar to the thread here: No GATT-Database if bleprofile_Init()

I am runing into this issue as well. The database and the app are completely generated by the designer, yet it won't run. All I am doing is creating a device with a generic heart rate monitor service and enabled notifications. Below is the GATT database.

const UINT8 gatt_database[] = // Define GATT database

{

    /* Primary Service 'Generic Access' */

    //<Name>Generic Access</Name>

    //<Uuid>1800</Uuid>

    //Service handle: HDLS_GENERIC_ACCESS

    //Service UUID: UUID_SERVICE_GAP

    PRIMARY_SERVICE_UUID16 (HDLS_GENERIC_ACCESS, UUID_SERVICE_GAP),

        /* Characteristic 'Device Name' */

        //<Name>Device Name</Name>

        //<Uuid>2A00</Uuid>

        CHARACTERISTIC_UUID16 (HDLC_GENERIC_ACCESS_DEVICE_NAME,

            HDLC_GENERIC_ACCESS_DEVICE_NAME_VALUE,

            UUID_CHARACTERISTIC_DEVICE_NAME,

            LEGATTDB_CHAR_PROP_READ,

            LEGATTDB_PERM_READABLE,

            8),

            'B','a','t','m','a','n','_','1',

        /* Characteristic 'Appearance' */

        //<Name>Appearance</Name>

        //<Uuid>2A01</Uuid>

        CHARACTERISTIC_UUID16 (HDLC_GENERIC_ACCESS_APPEARANCE,

            HDLC_GENERIC_ACCESS_APPEARANCE_VALUE,

            UUID_CHARACTERISTIC_APPEARANCE,

            LEGATTDB_CHAR_PROP_READ,

            LEGATTDB_PERM_READABLE,

            2),

            BIT16_TO_8(APPEARANCE_GENERIC_HEART_RATE_SENSOR),

    /* Primary Service 'Generic Attribute' */

    //<Name>Generic Attribute</Name>

    //<Uuid>1801</Uuid>

    //Service handle: HDLS_GENERIC_ATTRIBUTE

    //Service UUID: UUID_SERVICE_GATT

    PRIMARY_SERVICE_UUID16 (HDLS_GENERIC_ATTRIBUTE, UUID_SERVICE_GATT),

    /* Primary Service 'Heart Rate' */

    //<Name>Heart Rate</Name>

    //<Uuid>180D</Uuid>

    //Service handle: HDLS_HEART_RATE

    //Service UUID: UUID_SERVICE_HEART_RATE

    PRIMARY_SERVICE_UUID16 (HDLS_HEART_RATE, UUID_SERVICE_HEART_RATE),

        /* Characteristic 'Heart Rate Measurement' */

        //<Name>Heart Rate Measurement</Name>

        //<Uuid>2A37</Uuid>

        CHARACTERISTIC_UUID16 (HDLC_HEART_RATE_HEART_RATE_MEASUREMENT,

            HDLC_HEART_RATE_HEART_RATE_MEASUREMENT_VALUE,

            UUID_CHARACTERISTIC_HEART_RATE_MEASUREMENT,

            LEGATTDB_CHAR_PROP_NOTIFY,

            LEGATTDB_PERM_NONE,

            2),

            0x87,0x00,

            /* Client Characteristic Configuration Descriptor */

            //<Notification>true</Notification>

            //<Indication>false</Indication>

            CHAR_DESCRIPTOR_UUID16_WRITABLE (HDLD_HEART_RATE_HEART_RATE_MEASUREMENT_CLIENT_CONFIGURATION,

                UUID_DESCRIPTOR_CLIENT_CHARACTERISTIC_CONFIGURATION,

                LEGATTDB_PERM_READABLE | LEGATTDB_PERM_WRITE_CMD | LEGATTDB_PERM_WRITE_REQ | LEGATTDB_PERM_RELIABLE_WRITE | LEGATTDB_PERM_AUTH_WRITABLE,

                2),

                BIT16_TO_8(CCC_NOTIFICATION),

};

Are there  Weight Scale service and Body Composition service support within BCM20737 ROM? Or we need to build them ourselves based on GATT? Thanks.

Is there a list of the errors generated by emconinfo_getDiscReason()?

Central attempted connection (connUP) to peripheral,

but instead of connUP callback, central got connDown callback, in which emconinfo_getDiscReason() reported disconnect reason was "08".