Skip to main content
Graduate
August 9, 2024
Question

ST32H750 - I2C_DMAError when using HAL_I2C_Mem_Write_DMA function

  • August 9, 2024
  • 2 replies
  • 687 views

Dear all, in my application I want to send constantly data to an external I2C device in DMA mode. For this I use the function HAL_I2C_Mem_Write_DMA. I have my ADCs and SPI correctly working with DMA but with the I2C I get the error I2C_DMAError  in the XferErrorCallback. I have set up the DMA in Circular mode and run the function before the While(1) loop. I can see the I2C clock being sent. 

I use the function as follows:

 

 HAL_I2C_Mem_Write_DMA(&hi2c1, I2C_DEVICE_ADD, DEST_ADDRESS,I2C_MEMADD_SIZE_8BIT,(uint8_t*)i2c_data,10);

 


where

 

uint16_t i2c_data[5] = {0x0044,0xF021,0x0082,0x0100,0x0000};

 

I2C Init:

 

static void MX_I2C1_Init(void)
{

 /* USER CODE BEGIN I2C1_Init 0 */

 /* USER CODE END I2C1_Init 0 */

 /* USER CODE BEGIN I2C1_Init 1 */

 /* USER CODE END I2C1_Init 1 */
 hi2c1.Instance = I2C1;
 hi2c1.Init.Timing = 0x10C0ECFF;
 hi2c1.Init.OwnAddress1 = 0;
 hi2c1.Init.AddressingMode = I2C_ADDRESSINGMODE_7BIT;
 hi2c1.Init.DualAddressMode = I2C_DUALADDRESS_DISABLE;
 hi2c1.Init.OwnAddress2 = 0;
 hi2c1.Init.OwnAddress2Masks = I2C_OA2_NOMASK;
 hi2c1.Init.GeneralCallMode = I2C_GENERALCALL_DISABLE;
 hi2c1.Init.NoStretchMode = I2C_NOSTRETCH_DISABLE;
 if (HAL_I2C_Init(&hi2c1) != HAL_OK)
 {
 Error_Handler();
 }

 /** Configure Analogue filter
 */
 if (HAL_I2CEx_ConfigAnalogFilter(&hi2c1, I2C_ANALOGFILTER_ENABLE) != HAL_OK)
 {
 Error_Handler();
 }

 /** Configure Digital filter
 */
 if (HAL_I2CEx_ConfigDigitalFilter(&hi2c1, 0) != HAL_OK)
 {
 Error_Handler();
 }
 /* USER CODE BEGIN I2C1_Init 2 */

 /* USER CODE END I2C1_Init 2 */

}

 

DMA Config:

 

void HAL_I2C_MspInit(I2C_HandleTypeDef* hi2c)
{
 GPIO_InitTypeDef GPIO_InitStruct = {0};
 RCC_PeriphCLKInitTypeDef PeriphClkInitStruct = {0};
 if(hi2c->Instance==I2C1)
 {
 /* USER CODE BEGIN I2C1_MspInit 0 */

 /* USER CODE END I2C1_MspInit 0 */

 /** Initializes the peripherals clock
 */
 PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_I2C1;
 PeriphClkInitStruct.I2c123ClockSelection = RCC_I2C123CLKSOURCE_D2PCLK1;
 if (HAL_RCCEx_PeriphCLKConfig(&PeriphClkInitStruct) != HAL_OK)
 {
 Error_Handler();
 }

 __HAL_RCC_GPIOB_CLK_ENABLE();
 /**I2C1 GPIO Configuration
 PB6 ------> I2C1_SCL
 PB7 ------> I2C1_SDA
 */
 GPIO_InitStruct.Pin = SURFACE_SCK_Pin|Surface_SDA_Pin;
 GPIO_InitStruct.Mode = GPIO_MODE_AF_OD;
 GPIO_InitStruct.Pull = GPIO_NOPULL;
 GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOW;
 GPIO_InitStruct.Alternate = GPIO_AF4_I2C1;
 HAL_GPIO_Init(GPIOB, &GPIO_InitStruct);

 /* Peripheral clock enable */
 __HAL_RCC_I2C1_CLK_ENABLE();

 /* I2C1 DMA Init */
 /* I2C1_TX Init */
 hdma_i2c1_tx.Instance = DMA1_Stream5;
 hdma_i2c1_tx.Init.Request = DMA_REQUEST_I2C1_TX;
 hdma_i2c1_tx.Init.Direction = DMA_MEMORY_TO_PERIPH;
 hdma_i2c1_tx.Init.PeriphInc = DMA_PINC_DISABLE;
 hdma_i2c1_tx.Init.MemInc = DMA_MINC_ENABLE;
 hdma_i2c1_tx.Init.PeriphDataAlignment = DMA_PDATAALIGN_BYTE;
 hdma_i2c1_tx.Init.MemDataAlignment = DMA_MDATAALIGN_BYTE;
 hdma_i2c1_tx.Init.Mode = DMA_CIRCULAR;
 hdma_i2c1_tx.Init.Priority = DMA_PRIORITY_LOW;
 hdma_i2c1_tx.Init.FIFOMode = DMA_FIFOMODE_DISABLE;
 if (HAL_DMA_Init(&hdma_i2c1_tx) != HAL_OK)
 {
 Error_Handler();
 }

 __HAL_LINKDMA(hi2c,hdmatx,hdma_i2c1_tx);

 /* I2C1 interrupt Init */
 HAL_NVIC_SetPriority(I2C1_EV_IRQn, 0, 0);
 HAL_NVIC_EnableIRQ(I2C1_EV_IRQn);
 HAL_NVIC_SetPriority(I2C1_ER_IRQn, 0, 0);
 HAL_NVIC_EnableIRQ(I2C1_ER_IRQn);
 /* USER CODE BEGIN I2C1_MspInit 1 */

 /* USER CODE END I2C1_MspInit 1 */
 }

 


these are the registers:

image (6).png

Thanks for the help!

    This topic has been closed for replies.

    2 replies

    Technical Moderator
    August 9, 2024

    Hello @dc_matt and welcome to the Community :)

    This can be caused by several factors: memory allocation issues, D-Cache issues, incorrect I2C or DMA configuration, or improper error handling in callbacks.

    Check the DMA configuration settings. Do you manage cache coherency?

    DMA is not working on STM32H7 devices - STMicroelectronics Community

    dc_mattAuthor
    Graduate
    August 9, 2024

    Hi Imen, thanks, sorry, I accepted the solution by mistake.

    I just realised that when in Normal mode, the interface seems to work. But the xfer ErrorCallback is always I2CError. D and I caches are disabled for the moment being.