Skip to main content
Kent Swan
Kent Swan
Associate III
March 31, 2019
Question

Why was RX mode for I2S4 and I2S5 removed from CUBEMX 5.1.0 for STM32F?

  • March 31, 2019
  • 1 reply
  • 821 views

STM32F413, CubeMx 5.1.0 plugin to SW4STM32, with Library STMR32Cube_FW_F4_V1.24.0.

In previous versions we were able to set the transfer direction for I2S4,I2S5 half duplex channels. In the above version only transmit can be selected and the ability to select receive mode has been incorrectly removed. This is a regression test failure.

This topic has been closed for replies.

1 reply

I
Imen.D
Technical Moderator
April 2, 2019

Hello @Kent Swan​ ,

After check using same versions of CubeMx and CubeF4, we have the ability to select transmit and receive mode.

0690X0000089iCQQAY.png

Can you please share your ioc file to check more this behavior?

Regards,

Imen

"When your question is answered, please close this topic by clicking ""Accept as Solution"".ThanksImen"
Kent Swan
Kent SwanAuthor
Associate III
April 2, 2019
Thank you. I inadvertently overlooked something that should have been more obvious and got a little frustrated. I'm running 6 I2S channels in slave mode on an STM32F413 at 48K sampling rate of stereo 24bit digital audio using double buffered DMA with the fifo providing adaptive memory access which uses virtually every related feature of the STM32F4. There was only one annoying item in that there was no HAL driver call which supported the full feature set for double buffered I2S DMA which started the I2S and DMA channels in the proper order and allow the required callback handlers to be installed so I went ahead created two new driver calls modeled after existing HAL I2S drivers which do the trick nicely.
I'm using FreeRTOS as well and, with all 6 channels running, the overhead for the audio packet queuing between device endpoints is well within reason.
Terms & ConditionsAccessibility statement