cancel
Showing results for 
Search instead for 
Did you mean: 

Getting incorrect data from SDRAM through DMA2D

deinoppa
Associate
Posted on February 02, 2016 at 16:52

I have an 800x600 pixels RGB565 image stored in the SDRAM of my STM32F7-discovery board starting at memory address 0xC0390000.

What I want to do is saving this image to an SD card.

The code for this is as follows:

FIL file; 
//file object
char
file_str[30] = 
''imagebmp''
;
//filename
DMA2D_HandleTypeDef hdma2d_buf;
int32_t i, j;
uint32_t tmp = 0;
uint16_t img_buf[800];
//buffer for one line
UINT
bytes_written;
FRESULT fs_error;
file_str[6] = (
char
)((img_counter % 10) + 48);
//increase the filename
file_str[5] = (
char
)(((img_counter/10) % 10) + 48);
//create a test pattern, black pixels
for
(j = 0; j < 640; j++)
{
if
((j%2) == 0) img_buf[j] = 0x0;
else
img_buf[j] = 0x0;
}
fs_error = SD_Mount();
if
(fs_error != FR_OK) Filesystem_ErrorHandler(fs_error);
fs_error = SD_OpenFile(&file, file_str, F_WR_CLEAR);
if
(fs_error != FR_OK) Filesystem_ErrorHandler(fs_error);
fs_error = f_write(&file, bmp_fileheader800, 70, &bytes_written);
//write the header
if
(fs_error != FR_OK)
{
Filesystem_ErrorHandler(fs_error);
}
for
(i = 0; i < 600; i++)
//600 lines
{
//copy one line in a RAM buffer using DMA2D
/* Enable DMA2D clock */
__HAL_RCC_DMA2D_CLK_ENABLE();
/* Configure the DMA2D Mode, Color Mode and output offset */
hdma2d_buf.Init.Mode = DMA2D_M2M;
hdma2d_buf.Init.ColorMode = DMA2D_RGB565;
hdma2d_buf.Init.OutputOffset = 0;
/* Foreground Configuration */
hdma2d_buf.LayerCfg[1].AlphaMode = DMA2D_NO_MODIF_ALPHA;
hdma2d_buf.LayerCfg[1].InputAlpha = 0xFF;
hdma2d_buf.LayerCfg[1].InputColorMode = CM_RGB565;
hdma2d_buf.LayerCfg[1].InputOffset = 0;
hdma2d_buf.Instance = DMA2D;
/* DMA2D Initialization */
if
(HAL_DMA2D_Init(&hdma2d_buf) == HAL_OK)
{
if
(HAL_DMA2D_ConfigLayer(&hdma2d_buf, 1) == HAL_OK)
{
if
(HAL_DMA2D_Start(&hdma2d_buf, (uint32_t)(CAPTURE_FRAME_BUFFER + tmp), (uint32_t)&img_buf, 800, 1) == HAL_OK)
{
/* Polling For DMA transfer */
HAL_DMA2D_PollForTransfer(&hdma2d_buf, 10);
}
}
}
fs_error = f_write(&file, img_buf, 1600, &bytes_written);
if
(fs_error != FR_OK)
{
Filesystem_ErrorHandler(fs_error);
}
tmp = tmp + 800*
sizeof
(uint16_t);
}
fs_error = SD_CloseFile(&file);
if
(fs_error != FR_OK) Filesystem_ErrorHandler(fs_error);
fs_error = SD_UnMount();
if
(fs_error != FR_OK) Filesystem_ErrorHandler(fs_error);
img_counter++;

As you can see, I always buffer one line of the image in the SRAM before wrting it to the file. This line is stored in

uint16_t img_buf[800]
which is first filled with zeros, so I get black pixels.

After that I want to copy one line to my RAM buffer using DMA2D. This is done 600 times, once for each line.

After each loop iteration I increment my SDRAM base address for the DMA2D by 1600, since each line has 1600 bytes (2 bytes per pixel).

This is where the problems start:

I get incorrect data in my SRAM buffer. I ran a debug session to verify this behaviour.

Here are the contents of the SDRAM and and the line array

img_buf
:

0690X00000605FkQAI.png

0690X00000605MpQAI.png

As you can see the first few array elements stay zeros while the SDRAM content is clearly not zero. Then I get some correct values starting at the yellow marked elements, but after some time zeros agian and so on.

This behaviour is the same for all lines.

The image is displayed correctly on the onboard LCD.

So, the question is: Why am I getting wrong data via DMA2D?

I am pretty desperated right now because the DMA2D works well in several similar applications...

Thank you for any helpful hints.

#stm32-dma2d-dma-image-sdram
2 REPLIES 2
Posted on February 02, 2016 at 17:10

Do you have a large enough stack allocation?

Do you see the same behaviour if the buffer is static?

Do you wait long enough for the transaction to occur?

Do you pay attention to any error codes thrown? HAL_DMA2D_PollForTransfer()

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
deinoppa
Associate
Posted on February 03, 2016 at 10:05

Thank you for the reply.

Making the buffer static solves it, but I do not really understand why.

I understand that the corresponding memory is reserved just once at the first function call, but how does this prevent the DMA from showing that weird behaviour?