Smart Bluetooth Forum Discussions
We're using an 20736S and we're trying to differentiate between a single, double, and triple button press. We're getting some extra triggering of the interrupt on the button due to bouncing. We do have a pull down resistor on the pin, and we're configuring the pin using gpio_configurePin (we're using P4 in this case) with:
GPIO_INPUT_ENABLE | GPIO_EN_INT_RISING_EDGE | GPIO_PULL_DOWN, GPIO_PIN_INPUT_LOW
We've also setup the port in the BLE_PROFILE_GPIO_CFG with:
GPIO_INPUT | GPIO_INIT_LOW | GPIO_BUTTON | GPIO_INT
It's my understanding that there's debouncing logic already in the firmware and we'd like to try to use that before writing our own. Do we have to do anything special to use the firmware capability, or should we be using different configuration settings. We've tried a variety of different settings but none seem to make a difference.
Thank you.
Show LessHi folks,
I wonder if WICED Sence supports tracing on OSX.
I use 2.1.1 SDK on Yosimite 10.10.1.
I've used examples from SDK and haven't seen any trace logs in console.
Are any configuration steps need be done in order to tracing work?
Show LessI would like a solution where:
1. P0 can be configured as an output low
2. bleprofile_PrepareHidOff() can still be used to enter deep sleep
I would be fine with fully disabling keyscan and/or quadrature operation. GPIO interrupt wake up should still work (not necessary on P0, if that helps).
Please do not refer me to a "pull P0 high" solution; that is not what I am looking for. Thank you.
Show LessHello,
We have developed a PC application using the BTW API's and dll's included in the WIDCOMM stack to create our own custom DLL. We have everything working except for ONE item which really should be rather simple. It is to merely read the GATT Database UUID16 characteristic that stores the 'DeviceName'. This is simple to do in Mobile apps but we have failed to get this working with using the BTW API's. The specific UUID16 value we are trying to read is the UUID_CHARACTERISTIC_DEVICE_NAME which is 0x2A00 value. Can someone please give us a simple example of how to read this UUID16 using the BTW API's. The API we have currently been trying to us is the BtwGattReadCharacteristic(). Hopefully there is something simple we are missing.
Some questions:
1) Using the BtwGattReadCharacteristic. What are the values we should be using for the pGuidService and dwServiceInstance(typically 0)? Or another way to ask this is the UUID_CHARACTERISTIC_DEVICE_NAME in the SERVICE_GATT or the SERVICE_GAP???
It is interesting to note that none of the SDK BTW examples actually read the DeviceName they always just report the actual BT Address which in an App for a user it is much easier to associate with a user chosen DeviceName.
Regards,
Frank
Show LessHi All,
We are developing an battery powered device based on BCM20736S ble module. In our prototype the BCM consumes round about 65 µA while advertising in intervals of 3 seconds. At this point of development I have a few questions:
>Am I guessing right that the controller enters sleepmode between this advertisements automatically?
>Is it possible to reduce power consumption below 65µA without turning off advertisements or increasing intervals?
>Can power consumption be reduced by entering deep sleep mode between advertisements with 3s intervals?
Thanks a lot,
Udo
Is it possible to make the WICED Smart/Sense kits into a BLE Central Host with windows drivers?
I have a qualcomm bluetooth chipset in my PC desktop that I am using to communicate with the WICED Sense. I've come to realize, however, that Qualcomm seems to limit minimum connection intervals to 30ms+. My application requires 7.5ms. I know the WICED Sense can report at 7.5ms because I have an android tablet which reports 7.5ms timestamps in Android Studio when running the WICED Sense app.
Show LessPer this thread: Issue with i2cm.h - I2C communication
Is there any update on the i2cm problems? We are in need of an API to write to an external EEPROM on the BCM20736S using the I2C interface. If the Apps team doesn't have time to work on it can you release the i2cm source code so we can try to debug it? Will look at CFA but don't know if this will work for us.
thanks.
ehoffman
Show LessPer this thread here: Hello-Client multi-master connection failure.
Hi sorry for the project schedule, not get available time to confirm this one though.
But as I remembered, all connected phone in our firmware log show the handle number from 0x40 and
get role play as "slave" not master and in current hello-client sample code, also can only get 1 master-role play.
So whether or not i need to modify its sample code to let master_count++ as slave_counter++ done in this code.
But I wonder when 2nd master handset is on, from lower-site, I still get its role play as "slave"; is any place to configure master side to allow doing 2nd master test in hello-client sample code. TKS.
Hi akbar501 and arvinds,
Per this thread here: Creating .bin file for WsUartFu.exe
I have same problem in using WsUartFu.exe.
I tested same as akbar's comments below, but it did not work after downloading new f/w.
Moreover, I also tested it using *.ota.bin as arvinds's comments, but it also didn't work.
Did you resolve this problem? If then, could you let me know how did you do?
Test environments : SDK 2.1.1 and SDK 2.2.0, BCM20737TAG
1.) successfully flash board with uart_fimrware_upgrade hex
2.) convert hello_sensor hex to a bin using ihex2bin.exe (c:\ihex2bin.exe hello_sensor.hex hello_sensor.bin)
3.) run WsUartFu.exe (c:\WsUartFu.exe hello_sensor.bin COM1)
4.) get c:\WsUartFu: upgrade status Success
Thanks,
Sung-Mok
Show LessI'm testing hello_client and hello_sensor in SDK2.2.0.
I understand that the simultaneous connection of central and peripheral is possible from 20736.
When I tried to test this with enabled security, I saw the notification handler not working as soon as hello_client is connected with mobile as peripheral.
My test procedure is following,
1. enable security
2. hello_client scans and connects with hello_sensor. During conn up, advertisement is enabled.
3. hello_client gets notification from sensor
4. hello_client is connected with mobile phone.
5. hello_client does not get the notification from sensor.
6. hello_client and hello_sensor are connected yet.
can you give me advice for this?
Show Less