更改hts221的控制寄存器没有任何改变

嗨，
 
你能告诉我你正在使用的设置顺序吗？
 
如果要使用单触发模式，则必须在CTRL_REG1（0x20h）或0x84（启用BDU）中写入0x80，并且为了开始转换，您必须在CTRL_REG2（0x21h）中写入0x01。
 
你使用的奴隶地址是什么？
注意：从地址是BFh用于读I2C事务，BEh用于写I2C事务。
 
问候
安东内拉



以下为原文





Hi,

Can you send me the sequence of settings that you are using?

If you want to use the one shot mode,you have to write 0x80 in CTRL_REG1 (0x20h) or 0x84 (BDU enabled) and in order to start a conversion you have to write 0x01  in CTRL_REG2(0x21h).
  
What is the slave address that you are using?
Pay attention : the slave address is BFh for Read I2C transactions and BEh for Write I2C transactions.

Regards
Antonella

嗨，
 
 
 我正在使用C＃和.net微框架，它完成大部分的i2c通信。
 从地址是0x5F + R / W-bit - ＆gt;写入事务为0xBE，读取为0xBF。由于我能够读取涉及写入事务的寄存器，这似乎是正确的。
 我用示波器检查了数据，每一点都检查出来。
 
 WHO_AM_I（0Fh）正确回复BCh。
 AV_CONF（10h）：1Bh
 CTRL_REG1（20h）：0h
 CTRL_REG2（21h）：0h
 CTRL_REG3（22h）：0h
 STATUS_REG（27h）：0h
 
 我首先尝试阅读ctrl_reg，然后写下我的更改，我尝试先写不读。在它检出的总线上，写入传输由从机确认，但没有任何变化。
 我在网上看过一些例子，即使是在不同的编程语言中，但是当我尝试相同的命令序列时，没有任何变化： - /
 
 谢谢你的帮助，
 干杯，
 --Jens



以下为原文





Hi,


I'm using C# and .net micro framework, which does most of the i2c-communication.  
Slave address is 0x5F + R/W-bit --> 0xBE for a write transaction, and 0xBF for a read. And since i'm able to read the registers which involves a write transaction, this seems to be correct.  
I've checked the data with my oscilloscope and every little bit checks out.

WHO_AM_I (0Fh) replies correctly with BCh.
AV_CONF (10h): 1Bh
CTRL_REG1 (20h): 0h
CTRL_REG2 (21h): 0h
CTRL_REG3 (22h): 0h
STATUS_REG (27h): 0h

I tried reading the ctrl_reg first and then write my changes, I tried writing without reading first. On the bus it checks out, the write transmission is acknowledged by the slave but nothing changes.  
I've seen some examples on the web, even in different programming languages, but when i try the same command sequence nothing changes :-/

Thanks for your help,
Cheers,
--Jens

嗨，
 
 
 我只有这个例子，所以我不能尝试另一个例子。
编辑：我应该在一周内收到另一个董事会。我会尝试然后告诉你。
 
 干杯，
 --Jens



以下为原文





Hi,


I only have this one example, so i can't try on another one.
Edit: I should receive another board within a week. I'll try then and tell you about it.

Cheers,
--Jens

嗨，
 
 
 我终于有时间尝试另一个样品。可悲的是，这是完全相同的行为。
 控制寄存器不能写入

嗨，
我回顾过去所有的帖子，我不认为坏的操作是设备的问题，而是I2C连接或总线的实现。
 
如果我理解正确，你使用的是x-nucleo-iks01a1扩展板，其上焊有HTS221和stm32f469迪斯科板。
 
x-nucleo-iks01a1与STM32 Nucleo板兼容，我通常使用这种组合没有任何问题（例如，-Nucleo-L152RE或-NUCLEO-F401RE）。
 
x-nucleo-iks01a1还配备了Arduino UNO R3连接器，我想你最后使用这个连接器将扩展连接到stm32f469迪斯科板。
说实话，我从未使用过这款stm32f469迪斯科板。
 
我建议你再次检查Arduino和amp; morpho连接器上I2C_SDA和I2C_SCL的连接。
 
DISCO-F469NI上的匹配应为PB_8和PB_9。
 
再次检查用于I2C的GPIO配置（必须使用micro的上拉）。
 
问候
安东内拉



以下为原文







Hi,
I reviewing all past posts, I don't believe that the bad operating is a problem of the device, but rather of the I2C connections or implementation of the bus.

If I understand correctly, you are using a x-nucleo-iks01a1 extension board with HTS221 soldered on it and stm32f469 disco board.

The  x-nucleo-iks01a1 is compatible with STM32 Nucleo boards and I usually have used this combination without any problems ( for example ‎Nucleo-L152RE or ‎NUCLEO-F401RE ).

The  x-nucleo-iks01a1 is also equipped with Arduino UNO R3 connector and I suppose that you are using this last to connect the extension to the stm32f469 disco board.
To be honest, I have never  used this stm32f469 disco board.

I suggest you to check again the connections for I2C_SDA and I2C_SCL on Arduino &morpho  connector.

The matching on DISCO-F469NI should be PB_8 and PB_9.

Check again the configurations of GPIO used for I2C (you have to use the pull-up of the micro).  

Regards
Antonella