HAL I2C Transmit then Receive without a stop between

[SnoZek]

Hello,

I’m using an STM32WBA65 and trying to communicate with a peripheral (PTX30W) over I2C1.

The peripheral requires the following I²C sequence:

 

START → WRITE → REPEATED START → READ → STOP

However, using HAL_I2C_Master_Transmit() followed by HAL_I2C_Master_Receive() does not work, because both HAL functions generate a STOP condition, and the PTX30W does not accept a STOP between the write and read phases.

On STM32WBA, I don’t see a HAL equivalent of HAL_I2C_Master_TransmitReceive() that would allow a repeated START without a STOP in between.

My questions are:

• Is there a way to achieve a WRITE + REPEATED START + READ sequence using the HAL on STM32WBA?

• Or is the correct approach to switch to the LL (Low Layer) I2C driver to get finer control over START/STOP conditions?

Any guidance or best practices for this use case would be appreciated.

Thanks in advance.

here is the i2c protocol :

[TDK]

Use HAL_I2C_Mem_Read to write 1-2 bytes, then read a bunch, using a repeated start.

[Andrew Neil]

---

@TDK wrote:

Use HAL_I2C_Mem_Read to write 1-2 bytes, then read a bunch, using a repeated start.

---

@Emil Damkjaer PETERSEN @Loic CHOSSAT this is particularly poorly described in the HAL documentation:

https://www.st.com/resource/en/user_manual/um3140-description-of-stm32wba-hal-and-lowlayer-drivers-stmicroelectronics.pdf#page=327

 

I really don't think it's at all clear from this description that "MEM" is the one to use in this application?

 

Please can we have a clear description like @TDK's in the HAL manuals - this kind of question comes up frequently on the forum!

I suspect that most applications where HAL_I2C_Mem_Read is the correct choice are not actually "memory" devices - as is the case here.

[TDK]

I think the HAL_I2C_Mem_Read naming is appropriate. Most uses of this are for actual memory addresses or register analogs. For example, accelerometers and other sensors, EEPROMs, LCD character displays. Just my opinion.

[Danish1]

I suspect that most I2C peripherals will actually work with a write followed by a read where the data-sheet shows repeated-start.

A major difference between the two is that after a stop-condition (on completion of the write) the I2C bus is released. In a multi-master system, a different I2C master may take control of the I2C bus and do whatever it wants.

If bus-master A sets up the peripheral address that it wants to read-from and then releases the bus before it actually does the read, bus-master B might change that address and so the wrong value will be read by A.

Many I2C systems just have the one bus master, so the problem cannot arise. But because I2C can be multi-master, peripheral data-sheets are written to suggest doing things in a way that is compatible with multi-master.

On reflection, multi-master issues can also arise where there is just the one hardware I2C master (your stm32) but it is running multiple threads and more than one oc those threads communicates over the I2C

[asfand12414141]

 

Hi, I’m on STM32WBA65 and need an I2C sequence START → WRITE → REPEATED START → READ → STOP (no STOP between write/read). But HAL_I2C_Master_Transmit() + HAL_I2C_Master_Receive() inserts a STOP, and my PTX30W rejects that. Is there a HAL way on WBA to do a repeated-start (like TransmitReceive), or is switching to LL I2C the right/best practice here?

Game Anchor: apkleone.com

 

[TDK]

There are HAL_I2C_Master_Seq_Transmit_(IT/DMA) and HAL_I2C_Master_Seq_Receive_(IT/DMA) functions that could be used here. No blocking ones.

 

Writing 4 bytes and then reading a bunch is not a typical use case.