nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

Håkon Alseth — Mon, 28 Sep 2020 08:10:44 GMT

Hi,

My apologies for the late reply.

[quote user="ChandraSR K"]&uart1 {status = "disabled";}; -- > adding in nrf9160dk_nrf9160ns.overlay[/quote]

This will disable UART1, but keep UART0 (default used for printing) still enabled. You should not disable CONFIG_SERIAL, as this will disable the uart debug prints as well.

Kind regaerds,

Håkon

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

ChandraSR K — Sat, 26 Sep 2020 03:58:50 GMT

Hi Can you suggest here.

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

ChandraSR K — Tue, 22 Sep 2020 14:22:26 GMT

either one of the below address the issue,

&uart1 {status = "disabled";}; -- > adding in nrf9160dk_nrf9160ns.overlay

CONFIG_SERIAL=n --> addign in prj.conf

But I would be needing serial port as well for printing info. above statements doesn't allow me to print debug messages.

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

Håkon Alseth — Tue, 22 Sep 2020 13:43:53 GMT

Hi,

It seems that you have found an issue in our blog! my apologies, I'll report this to the owner of the post.

The issue can be resolved by disabling uart1 in your overlay:

&uart1 {status = "disabled";};

Could you try adding this and see if it compiles properly now (remember to re-import your project!) ?

Kind regards,

Håkon

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

ChandraSR K — Tue, 22 Sep 2020 13:00:38 GMT

Thanks i could select nrf9160dk_nrf9160ns.

nrf9160dk_nrf9160ns.overlay: content

&i2c1 {
    compatible = "nordic,nrf-twim";
    status = "okay";
    sda-pin = < 30 >;
    scl-pin = < 31 >;
    clock-frequency = <I2C_BITRATE_STANDARD>;  
    
    /* The I2C address could be one of two, here 0x76 is assumed */
    bme280@76 {
        compatible = "bosch,bme280";
        reg = <0x76>;
        label = "BME280";
    };
};

But I am getting following assertion, at the end of compilation:

static assertion failed: "Only one of the following peripherals can be enabled: SPI1, SPIM1, SPIS1, TWI1, TWIM1, TWIS1, UARTE1. Check nodes with status \"okay\" in zephyr.dts."

below is the content of zephyr.dts specific to i2c:

            i2c1: i2c@9000 {
                #address-cells = < 0x1 >;
                #size-cells = < 0x0 >;
                reg = < 0x9000 0x1000 >;
                clock-frequency = < 0x186a0 >;
                interrupts = < 0x9 0x1 >;
                status = "okay";
                label = "I2C_1";
                compatible = "nordic,nrf-twim";
                sda-pin = < 0x1e >;
                scl-pin = < 0x1f >;
                bme280@76 {
                    compatible = "bosch,bme280";
                    reg = < 0x76 >;
                    label = "BME280";
                };
            };

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

Håkon Alseth — Tue, 22 Sep 2020 12:09:10 GMT

You select the board "nrf9160dk_nrf9160" in zephyr/boards/arm, then it should give you a choice on variant under "Board name":

Kind regards,

Håkon

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

ChandraSR K — Tue, 22 Sep 2020 11:58:59 GMT

While choosing nRF Connect options --> Board Directory , I couldn't find find nrf9160dk_nrf9160ns in <SourcePath>/ncs/v1.3.0/zephyr/boards/arm. I could see only nrf9160dk_nrf9160.

Can you help on how to choose nrf9160dk_nrf9160ns.

Thanks

Chandra

RE: nRF Connect SDK Tutorial - Part 3 | NCS v1.3.0 --> 1.2 Walkthrough for BME280 - gives compilation error

Håkon Alseth — Tue, 22 Sep 2020 10:53:56 GMT

Hi,

[quote user=""]nrf9160dk_nrf9160.[/quote]

When configuring the project, did you select the board that corresponds to your overlay file?

If the board is "nrf9160dk_nrf9160" then the overlay should be samples/my-app/nrf9160dk_nrf9160.overlay and contain the corresponding overlay settings for the sensor you're using.

Could you please share your overlay file and which board you're configuring the project for, if it still doesn't work?

Note: its normal to use the board nrf9160dk_nrf9160ns, as the modem can only communicate with an application in the non-secure region.

Kind regards,

Håkon