Smart Bluetooth Forum Discussions

Hi,

    I got the kit from Avnet`s online Market. And  could anyone please tell me how could i get the pcb files.

I can create a gatt database with a characteristic value with length 150 bytes. I can then read that value over Bluetooth link with a competing BLE chipset to verify that the database is setup and working correctly. But within the app, I can only find bleprofile_ReadHandle() and bleprofile_WriteHandle() to read and update the gatt database, and the bleprofile_WriteHandle() seems to cause the processor to crash when I try to update a 150 byte characteristic value. Is there any support for long characteristic value read/writes from the app point of view? What is the maximum length characteristic value that is supported?

Using the Broadcom 20732 chip.

Hi,

have downloaded WICED-Smart-SDK-1.0.1.7z to build and flash in WICED Smart device.

My build environment is:

OS: Ubuntu 12.04 -32bit

Made changes in the Makefile(wiced_toolchain_common.mk) for 32-bit linux.

Downloaded required packages mentioned in /Tools/source/ARM_GNU/README.TXT file and build each one successfully.

To OpenOCD build , Ran build_all.sh script

It is giving me the following error.

.

.

ibtoolize: copying file `m4/ltoptions.m4'

libtoolize: copying file `m4/ltsugar.m4'

libtoolize: copying file `m4/ltversion.m4'

libtoolize: copying file `m4/lt~obsolete.m4'

/usr/share/aclocal/dotconf.m4:5: warning: underquoted definition of AM_PATH_DOTCONF

/usr/share/aclocal/dotconf.m4:5:   run info '(automake)Extending aclocal'

/usr/share/aclocal/dotconf.m4:5:   or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal

configure.ac:11: warning: LT_INIT was called before AM_PROG_AR

/usr/share/aclocal-1.11/ar-lib.m4:15: AM_PROG_AR is expanded from...

configure.ac:11: the top level

autoreconf: running: /usr/bin/autoconf --force

configure.ac:11: warning: LT_INIT was called before AM_PROG_AR

aclocal.m4:75: AM_PROG_AR is expanded from...

configure.ac:11: the top level

autoreconf: running: /usr/bin/autoheader --force

configure.ac:11: warning: LT_INIT was called before AM_PROG_AR

aclocal.m4:75: AM_PROG_AR is expanded from...

configure.ac:11: the top level

autoreconf: running: automake --add-missing --copy --force-missing

configure.ac:11: warning: LT_INIT was called before AM_PROG_AR

aclocal.m4:75: AM_PROG_AR is expanded from...

configure.ac:11: the top level

configure.ac:11: installing `build-aux/ar-lib'

configure.ac:4: installing `build-aux/missing'

src/Makefile.am: installing `build-aux/depcomp'

autoreconf: Leaving directory `.'

autoreconf done.

Bootstrap complete. Quick build instructions:

./configure ....

HEAD is now at ab939f3 Add floating point support for [binary]

fatal: /usr/lib/git-core/git-am cannot be used without a working tree.

Please help me out

Thanks in advance.

So I finally got everything up and running on my eval board, connecting with the included BLE USB dongle.

Trying the hello_sensor app with HelloClient x64, I am able to receive notifications when I press the big white button.

However, after I press it about 12-15 times, the notifications stop sending. I have to press "Read" to send a read request to get the new value, and the notifications start sending again. For about 12-15 times. Then they stop again and I have to "Read" again before they work. Rinse, Repeat.

I know the button is working, because when I click "Read", the number changes to the number of times I pressed the button in between the notifications stopping.

Is anyone else getting this same problem? Setting to Indications doesn't help.

Notifications in iOS

On a related note, notifications don't work at all in iOS. I wrote an iOS app to subscribe to the Hello Input notifications. The iPad connects to the device, retrieves the services, and subscribes to the Hello Input notifications all without error. However, I never receive notifications when I press the button. Perhaps this is related?

Is there a setting to improve the robustness of the notifications? Perhaps a longer timeout interval or connection interval or something? The same iOS code works with a Bluegiga BLE112 perfectly, as well as the RedBearLabs BLE Mini (Nordic chip), so I'm wondering if there's some setting on the WICED firmware that I need to change to get it to respond to notifications.

Thanks!

In the example for UART init from the H/W Interfaces page 15 does all that setup need to be performed

Before or after the “bleapp_set_cfg” call in the APPLICATION_INIT ?

Hello all

Is there a driver for the bcm920702DG_FLSH that came in the WICED Smart box?

I downloaded and installed the big WIDCOMM driver, but no dice.  Bluetooth Software Download | Broadcom

Thanks!

Jason

I am using the hello_sensor demo and tried to change the device name, I change all the name in the .c files but when build and load to the device, it is still shown up as "Hello". Does anyone ran into this problem before? Thanks.

I'm trying to use the interrupt from GPIO to trigger a digitization on rising edge.  First of all, what is the latency of the rising edge, and is there a time hysteresis, and if there is can I set it to be minimal, also is there some onboard checking of this to make sure it was high for some period of time so I can bypass this.

I have wired a 10us pulser to the sw1 input (replacing the sw1 input) which I was able to get working manually and write to the uart port. What I don't know is how the system responds to this interrupt, and how can I maximize the bandwidth. Also, how I might give a higher priority to the interrupt.  The FW examples kind of hide how this is done, however, there is an example for the GPIO and interrupts so I'm wondering if setting them up this way might provide less latency.  Also, is there anyway to get a main loop or does that live somewhere in the background and is inaccessible?

Hi,

What is your recommenced solution for programming at factory a WICED smart device?

Thank you