Smart Bluetooth Forum Discussions

hi sir,

I use two BCM92073X kit do test,

I add a characteristic and handle 0x001A like this :

then I open two smart UART Controller ,

and I write "aaaaaaaaaaaaaaaaaaaa"(length 20) to handle 0x001A , Written correctly :

But when I write "aaaaaaaaaaaaaaa"(length 15) to handle 0x001A, Write value Weird :

why appear  "9f" ??

and sometimes i write any value(such as "hhhhh") to handle 0x001A ,the peer device 

No value is written

How can I solve this problem ?

thanks Sir !

I tried to modify the hello_client and hello_sensor and make them connect via "directed" advertising.  However, I cannot make it connect.  From the sniffer, I can see the advertising packets, but there is no connection.  Could you please confirm that Directed Advertising works for SDK 2.2.1 ?   If so, do you have an example?

Also, what is the  unit of the parameter  "low_direct_adv_interval"?   Is it in second of time slot?  What is the range of values?   Thank you.

Good afternoon

i added a USB to BLE dongle on my PC (based with TI CC2540). With this dongle i can successfuly connect to TI sensorTAG but not with BROADCOM Wiced sense.

I see advertisement datas, i successfully list the WICED sense in the slave BDA but impossible to establish a connection.

Is there anybody who already got this problem ? is there any work around ?

thank you

best regards

If any services and characteristics are not displayed in LightBlue app, is there the way to regain them?

Best regards

Changes for WICED-Smart-SDK-2.2.1

• Added indoor positioning server and automation IO client and server sample applications
• Improved RF performance for some parts with temperature variation
• Updated patches to the latest version.
• Updated cgs and chipload tools to the latest version.
• Added new/improved optional libraries: runtime_stats, additional_advertisement_control, single_channel_scan,hci_uart_pins_as_gpio
• A number of bug fixes

The Windows installer version is available here: WICED-Smart-SDK-2.2.1-IDE-Installer (Windows)

Linux and OSX versions to follow.

In our design,It using SPI to connect serial flash and I2C to connect a sensor IC.When download,it will fail,but if remove sensor,download will be ok.

I think the reason is SPI and I2C conflict.

How are we resovle this issue?

Hi,

BLE 4.2 has been finalized, and I want to check when BRCM can deliver full support for BLE 4.2.

Thanks in advance!

I was pointed to this post from a discussion of long boot times: Wake up time from sleep/deep sleep

You mention in the post that the boot time can be improved by changing the I2C speed from 400 khz to 1MHz, and this would cut down the time a lot.

Two questions:

1. How do you make this change?  Is this a matter of changing a value in a CGS file?

For SDK 2.2.1 I see there is a speed setting in the BCM920736 platform directory, but not in the _TAG directory, which is the one I am using.  Note that I have a custom board based on the 20736S -- which platform directory should I be using?

2. What is the maximum speed allowed for the EEPROM in the 20736S?

Thanks for your help!

Hello,

Working on BCM20737 I need to keep some state information when the device enters Deep Sleep (HID off). what I need to keep is a pointer and a write buffer with values changing frequently therefore the NVRAM wouldn't help due to limited write cycles.

is there any way to keep this information in some special memory bank or buffer that won't be cleared when the device enters Deep sleep ?

Thanks !

Hi JT,

Regarding the Android work-around you posted here: WICED Sense Android Pairing Work-Around

First off, thanks for your workaround suggestion....

is this issue still valid, are there any updates ?

That workaround didn't work for my case,

I am using a Galax S5.

I can connect from the android application directly every time, but after at least two or three retries, and I figured out, that I have to start the phone connection (press connect button) at a very specific moment as soon as I wake the Tag, that gives more chances to succeed.

I thought bluetooth is a standard to avoid such incompatibilities, do you have any hints if this is an Android issue, will be fixed in future versions of android, or if it is a Wiced sense, hardware, BLE stack or application issue, if then, it would be nice to know if any other Broadcom devkit has this issue solved ?

Do you have any recommended advertising parameters duration or other setup that can help ?

Thanks in advance.

Wassim