Smart Bluetooth Forum Discussions
Hey Guys,
We have developed a 9-Axis Sensor Fusion Demo using our upcoming Wireless Sensor Platform(WSP). The Sensor Fusion is performed on a SiLabs EFM32 Cortex M3/M4F depending on the Starter Kit plugged into the WSP. The EFM32 is configured as an I2C Master to communicate with the 9-Axis Motion Sensor. The BCM2073xS which is also connected to the kit and we are using this to send the Sensor Fusion data to a PC and soon Mobile Apps is also connected to the Sensor board and also has the I2C lines running to the sensor although there is ZERO I2C firmware running on the BCM2073xS outside of the typical default Boot I2C scenario to the EEPROM. Being that the internal EEPROM address is different than the Motion Sensor this should be fine.
We have seen that when the BCM2073xS SDA/SCL lines are also tied into the Sensor(but should have zero effect) that there appears to be contention for some reason. Upon starting code execution on the EFM32 the I2C comms is corrupted slightly to where the Motion Sensor does not initialize correctly? We have clipped the SDA/SCL lines coming into the Sensor Board and everything works fine. This contention is occurring after the BCM2073xS has been paried/bonded with a Client and there is no where else in the BCM firmware where NVRAM Read/Write functions are being used outside of when Host ID, Bonding info is stored so there should be no activity from the I2C module after BOOT and after pairing.
Question:
1) If there is no I2C configuration on the BCM2076xS is it safe to operate with the I2C lines connected into a system with another I2C
master in the system? I can add a SCL/SDA disconnect switch but it seems unnecessary.
2) After the initial EEPROM boot upon a RESET/POR is there ANY I2C activity that occurs if the I2C module has not been configured
outside of potential NVRAM Read/Writes?
Regards,
Frank
Show LessI'm running a modified version of the hello_sensor and and my application will occasionally loss connection to the client (phone) this happens randomly and I was wandering if there is a way to see who terminated the connection client/server?
thank you
Show Less
I modified hello_client App (BCM20736)
and send notification to Android App.
it works good.
but in iOS, i can't that.
Android application set (CCCD) Client Configuration Characteristic descriptor enabled for Notification
but there is no way to update this descriptor on iOS side.
is it true?
there is no way sending noti enable signal in iOS?
Show LessHi hardy.chen and boont
Per the details in this thread: Disconnected happened right after connection
We are running into the same issue on 20737. Could I get some info on how you were able to resolve this issue,
Thanks
Show LessHi,
Per the issue that Kwang resolved here in this thread: access_tag_interrupt_handler
I'm having a same problem, but I'm implement the button repress/release on hello_sensor.c, which I can't
find where to add the interrupt handler when the button is released. By default, the hello_sensor seems only
handles the button press?
Thanks,
Show LessAs described in the title, any suggestion for this feature?
Hi,
I hope to get answers to the following two questions.
I enabled external 32KHz LPO on TAG03 board by connecting it to BCM20737.
I have the following function call in my app but the app seems to work fine with or without it. Is the call absolutely necessary?
bleapputils_changeLPOSource(LPO_32KHZ_OSC, FALSE, 250);
Also, my app has a part where enters deep sleep.
The part has the following statement before calling devlpm_enterLowPowerMode(). Is this assignment absolutely necessary?
devLpmConfig.wakeFromHidoffRefClk = HID_OFF_TIMED_WAKE_CLK_SRC_32KHZ;
Show LessIs there a date to Update the 2.2.1 installer to fix the JRE version code bug, so it will install on Windows 10?
This has been an open issue for quite a while.
I documented this as an installer bug some time ago. See my other post.
Joe
Show LessThe BCM20732 supports the use of Serial Wire Debug (SWD) debug/trace messages that are output through the HCI UART port that's onboard. The SWD pins are muxed with HCI UART and are used in such a manner that the hardware and firmware can auto-detect the presence of SWD or the HCI host; this means that HCI based download and debugging are mutually exclusive of one another.
In order to use these debug/trace output facilities from the HCI UART, you would need to:
1.) Closest to the BCM20732S (note that the JP1 header resides on the other side of the FTDI USB to USB converter, so it will not work), create a set of jumpers to an external header that contains the following signals: SWCLK = HCI UART_TX, SWIO = HCI UART_RX (the SWD SWO signal is not supported)
2.) Set ble_trace_enable = 0 when initializing the application
3.) Once debugging is complete over SWD, return ble_trace_enable to its default state to enable downloads
Note: Setting ble_trace_enable = 2 will output printf style traces to the HCI uart, which will then interfere with the symbolic debugger over SWD.
Show LessPer your responses here: Hardware Timer (hw_timer.h) usage
I tried to implement the usage of the hw_timer using the functions:
hw_timer_register_timer_expired_callback, hw_timer_start to initialize and the function
bleappevt_serialize within the callback function. Unfortunately the callback function is never called. I checked that with a cntr increment (I passed it via the data context pointer of the serialize function).
Do I have to initialize the event system or do I have to enable a hw_timer interrupt. I would appreciate any help
Thanks
Daniel
Show Less