no device npm1300_ek (one button sample) with nRF52 DK on I2C Bus

[nRF52_DK_usr]

I try to get the one button sample to work. There were several details missing to be able to compile and run this sample, which was very frustrating. After editing/updating the

prj.conf: CONFIG_I2C=y

CMakeLists.txt: set(SHIELD npm1300_ek)

nrf52dk_nrf52832.overlay:

 #include <zephyr/dt-bindings/pinctrl/nrf-pinctrl.h>

 &i2c1 {
 status = "okay";
 pinctrl-0 = <&i2c1_default>;
 pinctrl-1 = <&i2c1_sleep>;
 pinctrl-names = "default", "sleep";
 clock-frequency = <I2C_BITRATE_STANDARD>; 
 //clock-frequency = <10000>;
 };
 
 &i2c1_default {
 group1 {
 psels = <NRF_PSEL(TWIM_SDA, 0, 26)>,
 <NRF_PSEL(TWIM_SCL, 0, 27)>;
 bias-pull-up;
 };
};

&i2c1_sleep {
 group1 {
 psels = <NRF_PSEL(TWIM_SDA, 0, 26)>,
 <NRF_PSEL(TWIM_SCL, 0, 27)>;
 low-power-enable;
 };
};

My zephyr.dts i2c1 snippet:

/* node '/soc/i2c@40004000' defined in zephyr/dts/arm/nordic/nrf52832.dtsi:172 */
		i2c1: i2c@40004000 {
			#address-cells = < 0x1 >;      /* in zephyr/dts/arm/nordic/nrf52832.dtsi:181 */
			#size-cells = < 0x0 >;         /* in zephyr/dts/arm/nordic/nrf52832.dtsi:182 */
			reg = < 0x40004000 0x1000 >;   /* in zephyr/dts/arm/nordic/nrf52832.dtsi:183 */
			interrupts = < 0x4 0x1 >;      /* in zephyr/dts/arm/nordic/nrf52832.dtsi:184 */
			easydma-maxcnt-bits = < 0x8 >; /* in zephyr/dts/arm/nordic/nrf52832.dtsi:185 */
			zephyr,pm-device-runtime-auto; /* in zephyr/dts/arm/nordic/nrf52832.dtsi:187 */
			compatible = "nordic,nrf-twi"; /* in zephyr/boards/nordic/nrf52dk/nrf52dk_nrf52832.dts:188 */
			status = "okay";               /* in ../../../../mnt/df01dc22-f3bf-40d5-9858-752a58c9832d/devprojects/nordicsemi/npm13xx_one_button/build/npm13xx_one_button/zephyr/boards/nrf52dk_nrf52832.overlay:9 */
			pinctrl-0 = < &i2c1_default >; /* in ../../../../mnt/df01dc22-f3bf-40d5-9858-752a58c9832d/devprojects/nordicsemi/npm13xx_one_button/build/npm13xx_one_button/zephyr/boards/nrf52dk_nrf52832.overlay:10 */
			pinctrl-1 = < &i2c1_sleep >;   /* in ../../../../mnt/df01dc22-f3bf-40d5-9858-752a58c9832d/devprojects/nordicsemi/npm13xx_one_button/build/npm13xx_one_button/zephyr/boards/nrf52dk_nrf52832.overlay:11 */
			pinctrl-names = "default",
			                "sleep";       /* in ../../../../mnt/df01dc22-f3bf-40d5-9858-752a58c9832d/devprojects/nordicsemi/npm13xx_one_button/build/npm13xx_one_button/zephyr/boards/nrf52dk_nrf52832.overlay:12 */
			clock-frequency = < 0x186a0 >; /* in ../../../../mnt/df01dc22-f3bf-40d5-9858-752a58c9832d/devprojects/nordicsemi/npm13xx_one_button/build/npm13xx_one_button/zephyr/boards/nrf52dk_nrf52832.overlay:13 */
		};

with claudes assistance/support i got it to compile and run. But an i2c scan i2c0 shows no device at all.

What minimal required steps/configuration have to setup to get I2C enabled and detect devices on the bus should be?

Trying with the nrf-connect (Ubuntu) Linux-Desktop app (2x USB -C, 1x LiPo Battery) i get NPM detected, the LiPo Battery to and can change parameters for ex. the LED's live, so the BOARD is working.

Any support/hint/help is appreciated.

[Håkon Alseth]

Hi,

 

You should not need to alter anything when compiling the example:

https://docs.nordicsemi.com/bundle/ncs-3.3.0/page/nrf/samples/pmic/native/npm13xx_one_button/README.html

 

Please note that the "npm1300_ek" shield uses i2c0 on the nrf52dk, and not i2c1.

Same goes for the zephyr sample:

https://docs.nordicsemi.com/bundle/ncs-3.3.0/page/zephyr/samples/shields/npm13xx_ek/index.html#npm13xx_ek

Here you need to set the shield parameter (as you do in CMakeLists.txt):

https://docs.nordicsemi.com/bundle/ncs-3.3.0/page/zephyr/samples/shields/npm13xx_ek/index.html#building_and_running

 

Kind regards,

Håkon

[nRF52_DK_usr]

Hi,

editing an example was my fault. But Using I2c0 is no difference. Tried with the original sample npm1300.overlay.

I additonally enabled the shell in the prj.conf:

CONFIG_PRINTK=y

CONFIG_LOG_CMDS=y

CONFIG_I2C_LOG_LEVEL_DBG=y

CONFIG_SHELL=y

CONFIG_LOG=y

CONFIG_UART_CONSOLE=y

CONFIG_EARLY_CONSOLE=y

CONFIG_I2C_SHELL=y

The result of >device list< is:

uart:~$ device list
devices:
- clock@40000000 (READY)
  DT node labels: clock
- gpio@50000000 (READY)
  DT node labels: gpio0
- uart@40002000 (READY)
  DT node labels: uart0 arduino_serial
- i2c@40003000 (READY)
  DT node labels: i2c0 arduino_i2c
- pwm@4001c000 (READY)
  DT node labels: pwm0
- pmic@6b (DISABLED)
  DT node labels: npm1300_ek_pmic
- gpio-controller (DISABLED)
  DT node labels: npm1300_ek_gpio
- regulators (READY)
  DT node labels: npm1300_ek_regulators
- LDO2 (DISABLED)
  DT node labels: npm1300_ek_ldo2
- LDO1 (DISABLED)
  DT node labels: npm1300_ek_ldo1
- BUCK2 (DISABLED)
  DT node labels: npm1300_ek_buck2
- BUCK1 (DISABLED)
  DT node labels: npm1300_ek_buck1
- leds (READY)
- leds (DISABLED)
  DT node labels: npm1300_ek_leds
- pwmleds (READY)
- temp@4000c000 (READY)
  DT node labels: temp
- charger (DISABLED)
  DT node labels: npm1300_ek_charger

So pmic@6b is disabled despite in the npm1300.overlay:

&npm1300_ek_pmic {

host-int-gpios = <&gpio0 22 0>;

pmic-int-pin = <3>;

};

What am i missing?

[nRF52_DK_usr]

When i compile the original sample, just configuring the required shield in CMakeLists i get the message "Error: led device is not ready". USB-C Cable for USB PMIC and a Battery to Jumper 2. The nrf52 DK can't access/contact the npm1300 EK, wired as in the sample mentioned.