Build error for example code of MAX30101 with nRF SDK v1.5.0

[MaxPow]

Hello,

I am using example code of MAX30101 Pulse Oximeter sensor with nRF SDK v1.5.0 on board NRF5240DK. I copied the example from the ncs \ v1.5.0 \ zephyr \ samples \ sensor \ max30101 folder to the ncs \ v1.5.0 \ nrf \ samples \ sensor \ max3010 folder. I also created a file nrf5340dk_nrf5340_cpuapp.overlay in the \board folder and added there:

&i2c0 {
    max30101 @ 57 {
        compatible = "max, max30101";
        reg = <0x57>;
        label = "MAX30101";
    };
};
& gpioa {
status = "okay";
};

Building the example code I am getting macro error in devicetree.h file as mentioned below

#define DT_INST(inst, compat) UTIL_CAT(DT_N_INST, DT_DASH(inst, compat))

with following message in output

error: 'DT_N_INST_0_max_max30101_P_label' undeclared (first use in this function)

Please suggest appropriate solution for the above problem.

Thanks.

[Øivind]

Hi,

Try replacing the contents of your overlay file with:

&i2c1 {
    max30101@57 {
        compatible = "max,max30101";
        reg = <0x57>;
        label = "MAX30101";
    };
};

The extra spaces seem to be the source of your problems.

[MaxPow]

Hello! I did not carefully place the code here, my fault sorry, in the file nrf5340dk_nrf5340_cpuapp.overlay it is written without spaces.

[Øivind]

Make sure that there isn't a space between 'max,' and 'max30101' on the line:

        compatible = "max,max30101";

Since the sample uses logging, and uart0 is the default for the uart console, it would be simplest to use i2c1, like in my previous reply.
My overlay file is only the 7 lines I gave in my previous response and it builds.

[MaxPow]

I have checked the spaces' max, 'and' max30101 are not present. Used i2c1 left only seven lines, but unfortunately it did not help, the same error gets out.

[Øivind]

Ok, could you zip the entire project folder, with the build folder, and send it to me using: Insert->Image/video/file

I can compare it to the one I am using, and the generated files in the build folder should give me an idea what's going on.