Smart Bluetooth Forum Discussions
I have an external source that needs to be able to modify the advertisement rate after the device is up and running. What's the right way to do this? All the examples are set-and-forget.
Show Lessi'm in shanghai, i can't download the 2.1.1 SDK IDE, it is very slow and finanlly failed to download, is there some other site to download this?
Show LessHave got the BCM920737TAG board. Am looking to very simply turn on the LED that's connected to P14/P38. Anyone got any quick tips how to initialise the pin then turn the LED on or off?
Really simple code I'm looking for, nothing to do with BTLE stack really.
Cheers!
Show LessHello,
By default the ChipLoad program seems to download the application always on the DS1 of the EEPROM.
I would like to be able to choose the section in order to have 2 different applications in the EEPROM. Is it possible?
Thank you.
Show LessHello,
My customer is evaluating the BCM920737 and has the BCM92073X_LE_KIT
The customer is using the puart_control peripheral example software for the evaluation and is seeing the following results:
Customer comments:
I downloaded the puart_control project in the eval board.
I started client app on the PC.
I press -> start -> device discovery and I can see the address of the Roving module, which I configured as advertising device.
The BCM92073X_LE_KIT cannot see my android phone, Samsung ... but I can see another android phone, LG. Both phones have BLE supporting OS - latest version is on both.
When device (BCM92073X_LE_KIT) sees LG phone it pairs with it without me saying/issuing a command to do that.
I have HTC and I can see on that phone your module (BCM92073X_LE_KIT) when in advertising mode but not the opposite (the BCM92073X_LE_KIT cannot see the phone when board is in device discovery mode ,scanning for nearby devices).
I'll continue to play to see why and how to do what I need for my project.
Please let me know your thoughts.
Thanks,
Belenie
Is there a document or specification of HW random number generator of BCM20737?
I found functions ulp_initRandomSeed(), ulp_nextRand(), ulp_getRand() and ulp_rand() in patch.lst but can't find header file or documents.
Can you provide me the following informations?
* function prototype
* Is it a true random generator or pseudo random number generator?
I have two characteristics which I would like to store in persistent memory. I am a little unclear on how this works. When data is written to the wiced smart the wizard generated "on_write_to" functions are called. In here I am passed a pointer to the string of data that was written in the attrPtr. So where the confusion comes in is writing a recalling from persistent memory at this point.
My first confusion is with the idea of VsID. Under the Using NVRAM section of the Developing an Application for the BCM20732 it says that an application can specify any VsID between 0x10 and 0x6F with a maximum read or write block size of 255 bytes. My interpretation of this is that the VsID is an abstraction which is managed by some underlying framework that should allow me to write a chunk of data at 0x10 which is up to 255bytes, and then write another chunk of data to 0x11 which is also 255bytes without overwriting any of the data that was stored in 0x10. Is this correct? Or do I only have 0x6F - 0x10 = 0x5F bytes of total available contiguous non-volatile memory?
My second confusion is the wizard generated comment above the "on_write_to" function which states that if any persistent memory is changed I should return TRUE. So does this mean that if I make a bleprofile_WriteNVRAM() function call that I need to return a true flag? Or does this imply that I can return a true flag and all the persistence for my characteristics will be handled for me behind the scenes somehow?
Basically I am puzzled because in my "on_write_to" functions I am currently making a bleprofile_WriteNVRAM() function call, returning a TRUE flag to indicate that something has been changed in the persistent memory, and then on start-up during my "my_device_create" function making a bleprofile_ReadNVRAM() function call and storing that data into my characteristic using a "store_in_db_" function call. For some reason my wiced smart will never begin advertising. When I comment out the ReadNVRAM and store_in_db_ function calls everything works properly. So clearly I am missing something here.
Am I maybe trying to read/store at the wrong point during startup? Or am I improperly working with the persistence feature?
Thanks for any info in this regard.
In SDK2.1.1,
I set one characteristic permission as read(authenticated) in hello_sensor.
I added bleprofile_sendReadReq (handle No.) in 1sec app_timer, and log message into response callback function in hello_client.
When I change the permission on hello_sensor from read-authenticated to read, then response works normally,
but in case of read-authenticated in hello_sensor, read response callback in hello_client is not called.
When I set the permission of characteristic as authenticated, which api should I call to get the response from peer?
Show LessHi all
Pls, I have a question on BCM20736S, regards the Antenna external, i read on data sheet that exist the PIN 6 for antenna, is it correct?
So, I can to connect the antenna direct at pin specified.
Thanks a lot.
Pierluigi
Show Less