Issue with Implementing BME680 with nRF5340DK Using I2C Protocol

RE: Issue with Implementing BME680 with nRF5340DK Using I2C Protocol

AHaug — Mon, 05 May 2025 09:16:04 GMT

The first error here is a qspi error. Resolve your errors from top to bottom.

[quote user="Yashaswini S"]Yes, I am having a Custom board, Agora_BT40 which is having the nRF5340dk mcu.[/quote]

This does not make any sense to me. Could you clarify the following

Is the Agora_BT40 a module that a third party vendor has created? Is it this module? https://avlis-co.com/bt40-transceiver-802-15-4-bluetooth-bluetooth-v5-1-zigbee-transceiver-module-2-4ghz-pcb-trace-surface-mount/?

[quote user="Yashaswini S"]Is that the issue from the qspi?why it is affecting in BME680?[/quote]

There are two separate issues. One is the QSPI issue that you need to resolve and the second is the I2C issue.

Kind regards,
Andreas

RE: Issue with Implementing BME680 with nRF5340DK Using I2C Protocol

Yashaswini S — Mon, 05 May 2025 08:48:34 GMT

Hi,

Yes, I am having a Custom board, Agora_BT40 which is having the nRF5340dk mcu.

Is that the issue from the qspi?why it is affecting in BME680?

Thank you

RE: Issue with Implementing BME680 with nRF5340DK Using I2C Protocol

AHaug — Mon, 05 May 2025 07:50:09 GMT

Hi again,

You say that you use the nrf5340dk, which has the mx25 external flash. Why have you set up the qspi external flash to use the w25q? Is this a custom board and not a DK? Here's the qspi configuration for the nRF5340DK https://github.com/nrfconnect/sdk-zephyr/blob/83c5c72f4ca9402ad70fd33e471f3fa8a9536614/boards/nordic/nrf5340dk/nrf5340_cpuapp_common.dtsi#L112

Kind regards,
Andreas

RE: Issue with Implementing BME680 with nRF5340DK Using I2C Protocol

Yashaswini S — Thu, 01 May 2025 09:51:57 GMT

HI,

After that in the next, I can get the message like Failed to read Register D0, cross checked the register value in the datasheet is same.

Thank you

RE: Issue with Implementing BME680 with nRF5340DK Using I2C Protocol

Yashaswini S — Thu, 01 May 2025 09:23:48 GMT

Hi,

i2c3 {

status = "okay";

pinctrl-0 = <&i2c3_default>;

pinctrl-1 = <&i2c3_sleep>;

pinctrl-names = "default", "sleep";

bme680:bme680@76 {

compatible = "i2c-device";

reg = <0x76>;

};

i2c3_default: i2c3_default {

group1 {

psels = <NRF_PSEL(TWIM_SCL, 1, 3)>,

<NRF_PSEL(TWIM_SDA, 1, 2)>;

};

These are the pin config for I2C.

&qspi {

status = "okay";

pinctrl-0 = <&qspi_default>;

pinctrl-1 = <&qspi_sleep>;

pinctrl-names = "default", "sleep";

w25q32: w25q32@0 {

compatible = "nordic,qspi-nor";

reg = <0>;

/* MX25R64 supports only pp and pp4io */

//writeoc = "pp4io";

/* MX25R64 supports all readoc options */

//readoc = "read4io";

sck-frequency = <10000000>;

jedec-id = [ef 40 16];

//sfdp-bfp = [];

size = <0x2000000>;

has-dpd;

t-enter-dpd = <3000>;

t-exit-dpd = <30000>;

writeoc = "pp";

readoc = "fastread";

};

qspi_default: qspi_default {

group1 {

psels = <NRF_PSEL(QSPI_SCK, 0, 27)>,

<NRF_PSEL(QSPI_IO0, 1, 5)>,

<NRF_PSEL(QSPI_IO1, 1, 6)>,

<NRF_PSEL(QSPI_IO2, 0, 21)>,

<NRF_PSEL(QSPI_IO3, 0, 26)>,

<NRF_PSEL(QSPI_CSN, 0, 24)>;

nordic,drive-mode = <NRF_DRIVE_H0H1>;

};

These are the pin details Qspi.

Can you explain me the problem in this?

Thank you.

RE: Issue with Implementing BME680 with nRF5340DK Using I2C Protocol

AHaug — Wed, 30 Apr 2025 12:40:05 GMT

Hi,

The error that you get is complaining about the qspi_nor device and not the BME680 sensor over I2C. What changes did you do to your board files (.dts and .overlay)? Which GPIOs are the I2C device using?

Kind regards,
Andreas