Closed thedjnK closed 3 years ago
Initial review suggests the nRF53 doesn't behave the same as nRF52 with respect to transfers with no data, which is the mechanism used to detect presence of a device on the bus. The sensor signals an ACK at the end of the address, but the underlying nrfx driver must be continuing to perform a transaction even though the length should be zero, which produces an error instead of a success return.
This seems to be a difference in behavior at the nrfx driver level for the two chip lines. @anangl any ideas?
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.
Describe the bug I2C is working on an nRF53-based system e.g. using sensor sample apps, however the I2C shell itself does not seem to function at all.
To Reproduce Steps to reproduce the behavior:
Expected behavior It to work
Impact Seems like a bit of an annoyance if this doesn't work
Logs and console output Output from BME680 sample app: uart:~$ Booting Zephyr OS build zephyr-v2.4.0-2823-gf4a26837c8cb Device 0x20000234 name is BME680 T: 24.100000; P: 100.585000; H: 42.176000; G: 37582.000000 T: 24.180000; P: 100.585000; H: 42.056000; G: 46444.000000 T: 24.220000; P: 100.586000; H: 41.935000; G: 51387.000000 T: 24.250000; P: 100.585000; H: 41.840000; G: 55226.000000
Output from hello world:
Environment (please complete the following information):
Additional context Add any other context about the problem here.