invalid suffix "_FULL_NAME" on integer constant

[elektron314]

I'm trying to implement my own driver for our custm made board based onnRF5340-QKAA. Driver is for NCT218 I2C temperature sensor.

I'm implementing it based on the samples in the Zephyr project. I described api and trying to compile but during building it shows me error like below.

/Users/el314biig/biig-fw-ws/biig-fw/NCT218-driver/tmp_nct218.c: At top level:
/Users/el314biig/biig-fw-ws/biig-fw/build/zephyr/include/generated/devicetree_generated.h:15994:49: error: invalid suffix "_FULL_NAME" on integer constant
15994 | #define DT_FOREACH_OKAY_INST_onnn_nct218(fn) fn(0)

I am super newbie in programming especially Zephyr. I don't understand where to dig in. Can anybody help me? I can send any part  of code or even the whole project.

[Einarh]

Hello

I'd be interested to see any files you've defined for your driver; KConfig, dts, overlay, yaml etc

Also the generated devicetree in build/zephyr/zephyr.dts

Best regards,

Einar

[elektron314]

Ok, here you go.Compress.zip

[Einarh]

Hello

Just a few follow-up questions to figure out the root of your issue:

What NCS version are you using?

What Zephyr samples have you based your driver on?

Are you able to compile a project for your custom board without this new driver?

Are you able to compile a program using your driver if you build for the default nRF5340 DK?

Best regards,

Einar

[elektron314]

Hello

nRF SDK 2.2.0

Driver is based on a lot of samples, I used a lot of I2C temperature sensor samples as reference.

Yes, it's compilable without my driver. It's even compilable if I delete below line from the tmp_nct218.c file

#define DT_DRV_COMPAT onnn_nct218

Are you able to compile a program using your driver if you build for the default nRF5340 DK?

Do you mean by that if I will try to integrate my driver to the default nRF5340 firmware like e.g. Blinky? No I didn't try that but I can and I will tell you the result very soon, if so.

[Einarh]

elektron314 said:

Do you mean by that if I will try to integrate my driver to the default nRF5340 firmware like e.g. Blinky? No I didn't try that but I can and I will tell you the result very soon, if so.

Yes that's basically what I meant, just to make sure that your issue is related to only your driver and not your custom board too.

-Einar

[Einarh]

elektron314 said:

Yes, it's compilable without my driver. It's even compilable if I delete below line from the tmp_nct218.c file

#define DT_DRV_COMPAT onnn_nct218

Have you read through this?:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/build/dts/howtos.html#option-1-create-devices-using-instance-numbers

[Einarh]

Comparing to another device driver sample, maybe you're supposed to use SENSOR_DEVICE_DT_INST_DEFINE where you use SENSOR_DEVICE_DT_DEFINE in the end of tmp_nct218.c?

-Einar

[elektron314]

Yes, I read it.
Does it mean that If I exclude this #define my driver will be ignored?

[elektron314]

Now the error about fn(0) is absent and there is no any indication of special error, only the overall conclusion in the end:

collect2: error: ld returned 1 exit status

ninja: build stopped: subcommand failed.

FATAL ERROR: command exited with status 1: /usr/local/bin/cmake --build /Users/el314biig/biig-fw-ws/biig-fw/build


Can you explain the difference between those two and why it doesn't point to any special error in the building?