Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
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.
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
The biggest thing that sticks out to me is the pull up resistors. On the 20736S chips there are 10K pull up resistors external to the die. If you are pulling the line up on the other side, with a 4.7k, for instance, this may be detrimental to the timing of the I2C bus.
To my knowledge, there should be no activity on the i2c bus between nvram writes. I've had logic analyzers hooked up to a running app for hours without activity.
Do you get any successful reads/writes once the 20736S is connected (after init, to nvram, etc)?
Note here that the I2C spec requires an external pull up on SCL and SDA. The internal pullup is not sufficient because the part will not be configured until an I2C slave is detected (i.e. external pullup), which is a chicken-egg situation.
However, this only applies to the SoC. The pullups inside the SIP modules (shown on the internal schematic) are still external to the die, so the modules don't need pullups outside the module.
Thanks for the response. The issue happens upon POR when both sides a MCU and the BCM2073xS are initializing as we also initialize some sensors. For this sensor platform I have added a switch to disconnect the BCM2073xS I2C from the Sensor Board I have developed if the MCU is the I2C Master.