[riot-notifications] [RIOT-OS/RIOT] i2c_read_regs / i2c_write_regs and endianess (#11544)

Kees Bakker notifications at github.com
Sun May 19 14:48:44 CEST 2019


@benpicco I'm not sure if this is a bug. The I2C spec doesn't talk about register addresses, as far as I can see, only about device addresses (7 or 10 bit). The spec also doesn't talk about endianness, at all.

Now, there aren't many uses of 16 bit register addresses. So that could be an explanation why nobody bothered. I happen to know of one in the SHT2x driver where the identifier is read from a 16 bit register address. The SHT2x documentation isn't very clear about the actual address. It just gives an example of the bytes to transfer and I have adapted the register address to make it work with the I2C driver.

Could it perhaps be that endianness interpretation is a device issue?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/11544#issuecomment-493754163
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190519/241ed44c/attachment.html>


More information about the notifications mailing list