Skip to main content
arm
Associate
April 3, 2014
Question

Help CubeMX HAL and DMA2D

  • April 3, 2014
  • 3 replies
  • 1181 views
Posted on April 03, 2014 at 14:41

Hi.

Help is needed for Alpha channel input (CM_A4 an CM_A8) in combination with the HAL_DMA2D_BlendingStart(...) of the CubeMX HAL.

It seems like FGCOLR is not set neither with the call nor with Dma2dHandle.LayerCfg.

Furthermore the entire blending process is not clear to me. How to select / unselect the foreground layer, background layer and background color. What is needed for a simple CM_A4 + Color -> RGB transformation. A code snippet or similar would be great.

Thanks in advance.

#chrom-art-stm32cubemx-dma2d #hal #stm32cubef4 #dma2d
This topic has been closed for replies.

3 replies

stm32cube-t
ST Employee
April 4, 2014
Posted on April 04, 2014 at 09:50

Hello Christian,

Are you using MX to generate the initialization code? If yes, can you provide the IOC.

Have you also checked in the firmware package the DMA 2D code example? It can be found under: STM32Cube_FW_F4_V1.1.0\Projects\STM32F429I-Discovery\Examples\DMA2D\DMA2D_MemToMemWithBlending.

arm
armAuthor
Associate
April 4, 2014
Posted on April 04, 2014 at 11:27

Hi.

I'm using the example you mentioned as well as the other one with PFC copy.

Neither produces the proper output with CLUT or A8/A4 input.

The only help I found is this forum entry but it is for a CooCox Project and not based on the HAL_drivers of the CubeMX.

https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/Flat.aspx?RootFolder=https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/A%20simple%202D%20graphics%20library%20for%20STM32F429%20MCU%20%28CooCox%20project%29&FolderCTID=0x01200200770978C69A1141439FE559EB459D75800084C20D8867EAD444A5987D47BE638E0F&currentviews=187

with kind regards,

Christian

Montassar BEN ROMDHANE_O
Visitor II
June 6, 2014
Posted on June 06, 2014 at 16:42

Hi,

We have already the limitation, with CM_A4/CM_A8 color mode, in the STM32Cube HAL bugs list (DMA2D driver), and it will be fixed in next releases of F4 (early July) , 

Thanks for the report.

With regards.