i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Wed, 20 Sep 2023 06:06:23 GMT

Thanks for your reply! I can read/write registers now.

static int _lp5861ReadReg(uint16_t regAddr, uint8_t *regVal) {
    printk("tca6424aReadReg(regAddr=0x%x)\n", regAddr);
    const uint16_t devAddr   = LP5861_CHIP_ADDRESS | _lp5861GetRegAddrHigh(regAddr);
    const uint8_t  startAddr = _lp5861GetRegAddrLow(regAddr);
    printk("devAddr=0x%x, startAddr=0x%x\n", devAddr, startAddr);
    uint8_t rbuf[2];
    const int ret = i2c_burst_read(_gI2cDev, devAddr, startAddr, rbuf, sizeof(rbuf));
    if (ret < 0) {
        printk("i2c_burst_read(0x%x) failed, ret=%d\n", regAddr, ret);
        return ERROR_I2C_READ_FAIL;
    }

    printk("rbuf[0]=0x%x, rbuf[1]=0x%x\n", rbuf[0], rbuf[1]);
    *regVal = rbuf[0];
    return 0;
}

static int _lp5861WriteReg(uint16_t regAddr, uint8_t regVal) {
    printk("tca6424aWriteReg(regAddr=0x%x, regVal0x%x)\n", regAddr, regVal);
    const uint16_t devAddr   = LP5861_CHIP_ADDRESS | _lp5861GetRegAddrHigh(regAddr);
    const uint8_t  startAddr = _lp5861GetRegAddrLow(regAddr);
    printk("_lp5861GetRegAddrHigh(regAddr)=0x%x\n", _lp5861GetRegAddrHigh(regAddr));
    printk("devAddr=0x%x, startAddr=0x%x\n", devAddr, startAddr);
    const uint8_t wbuf[2] = { regVal,  0x00};
    const int ret =  i2c_burst_write(_gI2cDev, devAddr, startAddr, wbuf, sizeof(wbuf));
    if (ret < 0) {
        printk("i2c_burst_write(0x%x) failed, ret=%d\n", regAddr, ret);
        return ERROR_I2C_WRITE_FAIL;
    }

    return 0;
}

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

Joakim Jakobsen — Tue, 19 Sep 2023 09:58:18 GMT

Also, you can look at the documentation:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/hardware/peripherals/i2c.html

Br,
Joakim

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

Joakim Jakobsen — Tue, 19 Sep 2023 09:57:26 GMT

Thanks.

I haven't tested that sample.

There are several other tickets regarding i2c already on devzone, that you can take a look at.

I2C samples for nRF9160

Br,
Joakim

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 08:12:43 GMT

The attached file is result of https://github.com/crfosse/ncs_projects/tree/main/peripheral_zephyr/i2c I2C scanner. The result is very strange since it found a lot of I2C devices.

devzone.nordicsemi.com/.../i2c_5F00_scanner.txt

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:05:41 GMT

devzone.nordicsemi.com/.../4834.led_5F00_driver.c

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:05:16 GMT

devzone.nordicsemi.com/.../0654.nrf5340_5F00_cpuapp_5F00_common.dts

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:04:34 GMT

devzone.nordicsemi.com/.../nrf5340_5F00_cpuapp_5F00_common_2D00_pinctrl.dtsi

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:04:07 GMT

devzone.nordicsemi.com/.../5265.prj.conf

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:03:26 GMT

CONFIG_I2C=y
CONFIG_I2C_NRFX=y

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:02:52 GMT

static int _lp5861ReadReg(uint16_t regAddr, uint8_t *regVal) {
    printk("tca6424aReadReg(regAddr=0x%x)\n", regAddr);
    //printk("LP5861_REG_ADDR_HIGH(regAddr)=0x%lx, LP5861_REG_ADDR_LOW(regAddr)=0x%lx\n", LP5861_REG_ADDR_HIGH(regAddr), LP5861_REG_ADDR_LOW(regAddr));
#if 1
    uint8_t addrBuf[2];

    addrBuf[1] = regAddr & 0xFF;
    addrBuf[0] = regAddr >> 8;
    const int ret = i2c_write_read(_gI2cDev, LP5861_CHIP_ADDRESS, addrBuf, sizeof(addrBuf), regVal, 1);
#else
    const uint16_t devAddr   = LP5861_CHIP_ADDRESS | LP5861_REG_ADDR_HIGH(regAddr) >> 7 | LP5861_REG_READ_MSK;
    const uint8_t  startAddr = LP5861_REG_ADDR_LOW(regAddr);
    printk("devAddr=0x%x, startAddr=0x%x\n", devAddr, startAddr);
    const int ret = i2c_burst_read(_gI2cDev, LP5861_CHIP_ADDRESS, regAddr, regVal, 1);
#endif
    if (ret < 0) {
        printk("i2c_burst_read(0x%x) failed, ret=%d\n", regAddr, ret);
        return ERROR_I2C_READ_FAIL;
    }

    return 0;
}

static int _lp5861WriteReg(uint16_t regAddr, uint8_t regVal) {
    printk("tca6424aWriteReg(0x%x, 0x%x)\n", regAddr, regVal);
#if 1
    uint8_t addrBuf[2];
    struct i2c_msg msg[2];

    addrBuf[1] = regAddr & 0xFFU;
    addrBuf[0] = regAddr >> 8U;
    msg[0].buf = addrBuf;
    msg[0].len = 2UL;
    msg[0].flags = I2C_MSG_WRITE;

    msg[1].buf = (uint8_t *)&regVal;
    msg[1].len = sizeof(regVal);
    msg[1].flags = I2C_MSG_WRITE | I2C_MSG_STOP;

    const int ret = i2c_transfer(_gI2cDev, msg, 2, LP5861_CHIP_ADDRESS);
#else
    const uint8_t buf[1] = { regVal };
    const int ret =  i2c_burst_write(_gI2cDev, LP5861_CHIP_ADDRESS, regAddr, buf, 1);
#endif
    if (ret < 0) {
        printk("i2c_burst_write(0x%x) failed, ret=%d\n", regAddr, ret);
        return ERROR_I2C_WRITE_FAIL;
    }

    return 0;
}

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:02:13 GMT

i2c1_default: i2c1_default {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 1, 2)>,
				<NRF_PSEL(TWIM_SCL, 1, 3)>;
		};
	};

	i2c1_sleep: i2c1_sleep {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 1, 2)>,
				<NRF_PSEL(TWIM_SCL, 1, 3)>;
			low-power-enable;
		};
	};
	
	&i2c1 {
	compatible = "nordic,nrf-twim";
	status = "okay";
	clock-frequency = <I2C_BITRATE_STANDARD>;
	pinctrl-0 = <&i2c1_default>;
	pinctrl-1 = <&i2c1_sleep>;
	pinctrl-names = "default", "sleep";
};

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 07:00:41 GMT

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 06:59:56 GMT

Thanks for your reply! I am using nRF5340 DK. And I can't find I2C clock from logical analyzer snapshot.

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

Joakim Jakobsen — Tue, 19 Sep 2023 06:58:12 GMT

Hi.

As you can see, error code -5 is a general input / output error:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/hardware/peripherals/i2c.html#c.i2c_burst_read

Are you using an nRF52-DK or a custom device?

Br,
Joakim

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 02:01:50 GMT

devzone.nordicsemi.com/.../1172.prj.conf

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Tue, 19 Sep 2023 02:01:16 GMT

Another question is that I added CONFIG_I2C_DUMP_MESSAGES=y in prj.conf file. But I can't see any dump messages related to I2C.

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Mon, 18 Sep 2023 08:13:56 GMT

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Mon, 18 Sep 2023 08:13:13 GMT

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Mon, 18 Sep 2023 08:11:41 GMT

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Mon, 18 Sep 2023 08:10:47 GMT

devzone.nordicsemi.com/.../minimal_5F00_log_5F00_led.zip

RE: i2c_burst_read(0x0) failed, ret=-5 on ncs v2.4.2

snowuyl — Mon, 18 Sep 2023 08:10:32 GMT

devzone.nordicsemi.com/.../73678.custom_5F00_nrf52832.zip