NPM1300 Integration with custom board

RE: NPM1300 Integration with custom board

Naeem Maroof — Mon, 22 Jan 2024 21:00:40 GMT

After setting the shield, you can extract the same information from compiled dts and put it in the overlay for your board. Remember to add overlay for the build configuration.

As we are using EK, so the shield variable provides the dts info for the shield.

RE: NPM1300 Integration with custom board

Naeem Maroof — Mon, 22 Jan 2024 20:58:42 GMT

I got the dts info from the compiled zephyr dts, and simply put it in the overlay. I didn't have to mention Arduino:

RE: NPM1300 Integration with custom board

robsrick — Thu, 18 Jan 2024 16:38:09 GMT

Okay thanks i've made a bit of progress here. So to get it to compile i had to

1. update my root CMakeLists.txt to include the line

set(SHIELD npm1300_ek)

2. ensure the I2C i've got my npm1300 connected to is defined as an arduino_i2c like so:

arduino_i2c: &i2c1 {
    compatible="nordic,nrf-twim";
    status = "okay";
    pinctrl-0 = <&i2c1_default>;
    pinctrl-1 = <&i2c1_sleep>;
    pinctrl-names = "default", "sleep";
};

it then adds the npm1300 definitions to the compiled zephyr.dts in the build folder.

Could you explain how this works? I'm not really clear why i have to use arduino_i2c or set a shield rather than just adding my own definitions for the NPM1300 in the device tree directly.

RE: NPM1300 Integration with custom board

Naeem Maroof — Thu, 18 Jan 2024 15:27:42 GMT

Hello,

I suggest you to start with the fuel-gauge sample

and build for one of the supported boards,

and then build for your custom board after modification on the dts through overlay.

I am also not sure about your custom code.

Nonetheless, as per the log message you have attached:

It looks like something missing in the dts. Please check what ord_115 is in the generated devicetree and then see if it is correctly configured in the dts.

/BR, Naeem