I want to test BMI160 connected to NRF52840 over I2C using nrf_connect_sdk 1.4.1

[new]

While using NRF52840 SDK with twi_scanner i am able to see i2c address 0x68, but while using zephyr unable to get the data.

I have seen I can configure i2c pins in board.dts and board.overlay file, but I would like to know the procedure configure the SCL and SDA pin with internal pull ups.

With nrf5 sdk, the i2c SCL and SDA pin are by default configured with internal pull ups but I am not sure of the configuration in zephyr!

Does NRF_CONNECT_SDK i2c SCL/SDA pin are default pulled up or are there any methods to accomplish the same?

[Øyvind]

Hello, 

Have you verified that the BMI160 drivers in Zephyr support I²C? From what I can see the driver is only SPI. Ref. <NCS root>\zephyr\dts\bindings\sensor\bosch,bmi160.yaml.

I see you have another case regarding the same topic (case #261533), where you use ADXL345. Have you been successful in using this sensor? E.g via sensor samples in zephyr\samples\sensor\adxl362, and use drivers for adxl345 instead (zephyr\drivers\sensor\adxl345)? 

Unfortunately I'm currently without any sensors.

Kind regards,
Øyvind

[new]

Yes, I am quite successful in getting response from adxl375. 

I found one sample of BMI160 over i2c; https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/sensor/bmi160/bmi160.c

I have changed in all necessary file to look out for I2C, but unable to get configuration for setting internal pull up resistors. Without connect sdk, over twi sensor I am able to get i2c address but not with connect sdk. Also, it would be great if any multiple i2c slave setup samples are provided! 

[Øyvind]

new said:

I found one sample of BMI160 over i2c; https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/sensor/bmi160/bmi160.c

 Have you also changed NCS to master branch? This is not part of NCS v1.4.1

git checkout master
west update

Note that the master branch may be more unstable as we release tags (e.g. v1.4.1) as stable releases.

-Øyvind

[new]

I haven't updated to master but copied required BMI160 files to the ncs 1.4.1 folder and modified all required variables to refer i2c, but finding error in device_init method in BMI160.c. 

[new]

drivers/sensor/bmi160/bmi160.c : sensor sample. BMI 160 nrf_twim_error and unable to set PMU error.
The sensor is perfectly working with arduino code and nrf sdk. But with zephyr interface using nrf connect sdk, stuck at this! If by pass with directly setting specific register with BMi160_write_byte and bmi160_read_byte ; stopped by vector catch error got to fault_S.s . How to find the specific issue?

[Øyvind]

Hello,

And happy new year.

Please change to master branch in order to fully test this, as this is not implemented in NCS v1.4.1. The nRF Connect SDK uses the Zephyr OS, which means it is far more advanced compared to nRF5 SDK. 

Regarding the fault you get, have you tried to look at the debug output by connecting to the COM port of your device? Please read our nRF Connect SDK documentation on Working with nRF52 series

Kind regards,
Øyvind