Migrating from nrf5_SDK to nrf connect sdk

RE: Migrating from nrf5_SDK to nrf connect sdk

Albrecht Markus Schellenberger — Fri, 24 Sep 2021 11:10:15 GMT

Hello again,

I got some feedback from our development team:

There is a commit in Zephyr that adds a possibility to handle flash-located buffers to i2c. However, I’m not quite sure yet in which NCS release this will be included.
Handling DSP310 requires an extra entry in the devicetree that creates an additional buffer in RAM for a specific i2c instance: flash-buf-max-size; so still an action is required from the DPS310 driver user prior to using it

Regards,

Markus

RE: Migrating from nrf5_SDK to nrf connect sdk

Albrecht Markus Schellenberger — Fri, 24 Sep 2021 09:39:36 GMT

Hello,

[quote user="kclauah"]

And the suggestion from @anangl works for me.

How can I report a bug here?

[/quote]

Thanks for the feedback! I’m glad to hear you could solve the issue. I will report this internally.

Regards,

Markus

RE: Migrating from nrf5_SDK to nrf connect sdk

kclauah — Thu, 23 Sep 2021 07:41:16 GMT

Hello Markus,

I think I found the root cause.

https://github.com/zephyrproject-rtos/zephyr/issues/35550#issuecomment-847745043

And the suggestion from @anangl works for me.

How can I report a bug here?

RE: Migrating from nrf5_SDK to nrf connect sdk

Albrecht Markus Schellenberger — Tue, 21 Sep 2021 08:01:40 GMT

Hello,

[quote user="kclauah"]I still cannot understand why I2C driver does not try to write on SDA pin and directly jump to error code.[/quote]

This is really hard to tell without any more input from your application. But normally Zephyr throws an EIO if the devicetree configuration is not completely correct.

Unfortunately, I’m not able to test this on my side, since I do not have a DPS310 available. But I have tested the BME680 sample with my Thingy:91 and that works fine. Now, the sample does not use exactly the same I2C API as for the DPS310, so I can not exclude that their might be an issue with the sample itself.

[quote user="kclauah"]Can you give me a suggestion on how to create a new sensor driver? Because everything works fine on nRF5_SDK.[/quote]

My approach would have been to get the provided Zephyr sample to work with your board and sensor first, before taking any further steps.

Regards,

Markus

RE: Migrating from nrf5_SDK to nrf connect sdk

kclauah — Tue, 21 Sep 2021 02:28:16 GMT

Can you give me a suggestion on how to create a new sensor driver? Because everything works fine on nRF5_SDK.

Thank you.

RE: Migrating from nrf5_SDK to nrf connect sdk

kclauah — Tue, 21 Sep 2021 01:54:56 GMT

Hello Markus,

"... but the error often occurs when there are configuration mismatches."

I don't think so because I can get the chip ID correctly. Which means

1. The device is working.

2. The connection is correct(pin, I2C address, power...)

3. The initialization code is correct because it is written by manufacturer(tested both ST and Infineon).

I still cannot understand why I2C driver does not try to write on SDA pin and directly jump to error code.

RE: Migrating from nrf5_SDK to nrf connect sdk

Albrecht Markus Schellenberger — Mon, 20 Sep 2021 11:57:09 GMT

[quote user="kclauah"]What does Error I/O means?[/quote]

EIO can basically mean anything ;-) Unfortunately this does not help too much, but the error often occurs when there are configuration mismatches.

[quote user="kclauah"]The oscilloscope does not even triggered with command i2c_write_read(data->i2c_master, config->i2c_addr,
&REG_ADDR_CALIB_COEFF_0, 1, &raw_coef, 18); and return -EIO[/quote]

I assume you are referring to this function?

Can you please provide me with the content of ../zephyr/samples/sensor/dps310/<your build folder>/zephyr/zephyr.dts?

Thanks and regards,

Markus

RE: Migrating from nrf5_SDK to nrf connect sdk

kclauah — Mon, 20 Sep 2021 09:13:00 GMT

Hello Markus,

"Does the sample work with your sensor and DK?"

No. The sample does not work and I am using ../zephyr/samples/sensor/dps310 example for testing.

The oscilloscope does not even triggered with command i2c_write_read(data->i2c_master, config->i2c_addr,
&REG_ADDR_CALIB_COEFF_0, 1, &raw_coef, 18); and return -EIO

What does Error I/O means?

RE: Migrating from nrf5_SDK to nrf connect sdk

Albrecht Markus Schellenberger — Mon, 20 Sep 2021 09:07:37 GMT

Hello,

[quote user="kclauah"]Hello, today I have tested other manufacturer sensor (Infineon DPS310) and similar problem appears.[/quote]

could you please try the DPS310 application, located in ../zephyr/samples/sensor/dps310?

Does the sample work with your sensor and DK?

Regards,

Markus

RE: Migrating from nrf5_SDK to nrf connect sdk

kclauah — Mon, 20 Sep 2021 07:14:46 GMT

Hello, today I have tested other manufacturer sensor (Infineon DPS310) and similar problem appears.

On one hand, nrf52832 read register correctly.

	int res = i2c_reg_read_byte(data->i2c_master, config->i2c_addr,
				 IFX_DPS310_REG_ADDR_PRODUCT_ID, &product_id);

On the other hand, it does not generate waveform when read and write register.

	res = i2c_write_read(data->i2c_master, config->i2c_addr,
			     &REG_ADDR_CALIB_COEFF_0, 1, &raw_coef, 18);

1. The above are calling the same command i2c_write_read. I think something is wrong with I2C and nordic twim library because it is impossible that both example code from two different manufacturers do not work.

2. I have found similar problem on devzone: https://devzone.nordicsemi.com/f/nordic-q-a/74704/dps310-zephyr-example-not-working-with-the-nrf9160-sdk

Is he able to tackle this problem?

RE: Migrating from nrf5_SDK to nrf connect sdk

kclauah — Sun, 19 Sep 2021 13:52:27 GMT

Hello Markus,

Thank you so much for responding. I can confirm that the device is properly binded because the device pointer does not return NULL. But I have few questions as follow.

1. LSM6DSO contains a set of registers to control sensor behavior.

What I does in nRF5_SDK looks like the following,

    uint8_t reg[2] = {0x10, 0b00010000};
    nrf_drv_twi_xfer_desc_t xfer = NRF_DRV_TWI_XFER_DESC_TX(0x6a, reg, sizeof(reg));
    err_code = nrf_drv_twi_xfer(&m_twi, &xfer, 0);
    APP_ERROR_CHECK(err_code);
    while (m_xfer_done == false);

How can I achieve the same effect using the high level Sensor API or low level I2C API?

2. What is wrong with the following code? It is hard to debug as it crashes without any error code. I think the code should be corrected by following the readme.

    // @brief Write internal register of an I2C device.
    //
    // @param dev       Pointer to the device structure for an I2C controller driver configured in master mode. 
    // @param dev_addr  Address of the I2C device for writing.
    // @param reg_addr  Address of the internal register being written.
    // @param value     Value to be written to internal register.
    
    int ret = i2c_reg_write_byte(dev, 0x6a, 0x10, 0x10);
    if (ret < 0){
        printf("cannot i2c_burst_write");
    }else {
        printf("custom i2c_burst_write");
    }

2021-09-20T03:14:23.225Z DEBUG modem << *** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
2021-09-20T03:14:24.666Z DEBUG modem << Testing LSM6DSO sensor in polling mode.
2021-09-20T03:14:25.584Z DEBUG modem << [00:00:00.320,770] [0m<inf> LSM6DSO: chip id 0x6c[0m
2021-09-20T03:14:25.609Z DEBUG modem << [00:00:02.690,612] [1;31m<err> os: ***** USAGE FAULT *****[0m
2021-09-20T03:14:25.641Z DEBUG modem << [00:00:02.690,612] [1;31m<err> os:   Illegal use of the EPSR[0m
2021-09-20T03:14:25.673Z DEBUG modem << [00:00:02.690,612] [1;31m<err> os: r0/a1:  0x200000d8  r1/a2:  0x200010fc  r2/a3:  0x00000001[0m
2021-09-20T03:14:25.716Z DEBUG modem << [00:00:02.690,643] [1;31m<err> os: r3/a4:  0x0000006a r12/ip:  0x0000000a r14/lr:  0x00001621[0m
2021-09-20T03:14:25.758Z DEBUG modem << [00:00:02.690,643] [1;31m<err> os:  xpsr:  0x00000000[0m
2021-09-20T03:14:25.786Z DEBUG modem << [00:00:02.690,643] [1;31m<err> os: Faulting instruction address (r15/pc): 0x00000000[0m
2021-09-20T03:14:25.822Z DEBUG modem << [00:00:02.690,643] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0[0m
2021-09-20T03:14:25.859Z DEBUG modem << [00:00:02.690,643] [1;31m<err> os: Current thread: 0x20000250 (unknown)[0m
2021-09-20T03:14:25.890Z DEBUG modem << [00:00:02.997,009] [1;31m<err> fatal_error: Resetting system[0m

Also, Sensor API looks good that abstract sensor sampling. I would try this after sensor reporting the correct sensor readings.

-- Updated the hard fault debug message

RE: Migrating from nrf5_SDK to nrf connect sdk

Albrecht Markus Schellenberger — Fri, 17 Sep 2021 11:38:50 GMT

Hello,

I refer to LSM6DSO: IMU Sensor Monitor sample of Zephyr.

If you add the sensor via the devicetree (which I by the way recommend you do via an overlay file and not directly in the .dts), you have to use the Sensor API. One fundamental step is to bind the device probably, as shown here.

I hope this will help you :-)

Regards,

Markus