Writing a driver for nrf9160 and getting error in generated file

[paul_tanner]

I have followed various advice to create an SPI/I2C driver an own-designed device using the bme_280 example as a model

As this could be either SPI or I2C I put both configurations in the board overlay file.

The build was throwing many confusing errors beginning with:

```

zephyr/include/generated/devicetree_unfixed.h:4319:56: error: expected declaration specifiers or '...' before numeric constant

#define DT_FOREACH_OKAY_INST_<my device name>(fn) fn(0) fn(1)

```

Given that this is a generated file it's hard to see what caused it.

However, I got lucky and tried commenting out the SPI configuration.  It then built cleanly.

It seems that the clash occurs when both I2C and SPI configurations have the same compatible = "<my device name>"

I only want to test one at a time of course. I thought that setting one to status = "disabled" would avoid any clash.

It would be good to know what's happening here.

[Carl Richard]

Hi, Paul!

Could you elaborate a little? Have you made your own driver and you're testing it with the bme_280 sample?

I need to do some more research into how you can add your own devices in NCS, but from what I can see they need a .yaml file for each possible instance. Using bme280 as an example it has one bosch,bme280-spi.yaml and one bosch,bme280-i2c.yaml. Have you done the same for your device? 

Best regards,
Carl Richard

[paul_tanner]

Thx Carl

Sorry it took a while to see your answer (must check notifications enabled)

Yes, It's a driver for our own peripheral device.  I used the bme280 purely as an example of a device that does both spi and 12c.

Anyway, I added the 2 .yaml files and restored the configs in the overlay and I now get a clean compile.

Back to testing the driver now.

[Carl Richard]

No problem. Great to hear that it compiles properly now!

Best regards,
Carl Richard