9. Chrom-ART Accelerator controller (DMA2D)

9.1 DMA2D introduction

The Chrom-ART Accelerator (DMA2D) is a specialized DMA dedicated to image manipulation. It can perform the following operations:

• fill a part or the whole of a destination image with a specific color
• copy a part or the whole of a source image into a part or the whole of a destination image
• copy a part or the whole of a source image into a part or the whole of a destination image with a pixel format conversion
• blend a part and/or two complete source images with different pixel format and copy the result into a part or the whole of a destination image with a different color format

All the classical color coding schemes are supported from 4-bit up to 32-bit per pixel with indexed or direct color mode. The DMA2D has its own dedicated memories for CLUTs (color look-up tables).

9.2 DMA2D main features

The main DMA2D features are:

• Single AHB master bus architecture
• AHB slave programming interface supporting 8/16/32-bit accesses (except for CLUT accesses which are 32-bit)
• User programmable working area size
• User programmable offset for sources and destination areas
• User programmable sources and destination addresses on the whole memory space
• Up to 2 sources with blending operation
• Alpha value can be modified (source value, fixed value or modulated value)
• User programmable source and destination color format
• Up to 11 color formats supported from 4-bit up to 32-bit per pixel with indirect or direct color coding
• 2 internal memories for CLUT storage in indirect color mode
• Automatic CLUT loading or CLUT programming via the CPU
• User programmable CLUT size
• Internal timer to control AHB bandwidth
• 4 operating modes: register-to-memory, memory-to-memory, memory-to-memory with pixel format conversion, and memory-to-memory with pixel format conversion and blending
• Area filling with a fixed color
• Copy from an area to another
• Copy with pixel format conversion between source and destination images
• Copy from two sources with independent color format and blending
• Abort and suspend of DMA2D operations
• Watermark interrupt on a user programmable destination line

• Interrupt generation on bus error or access conflict
• Interrupt generation on process completion

9.3 DMA2D functional description

9.3.1 DMA2D block diagram

The DMA2D controller performs direct memory transfer. As an AHB master, it can take the control of the AHB bus matrix to initiate AHB transactions.

The DMA2D can operate in the following modes:

• Register-to-memory
• Memory-to-memory
• Memory-to-memory with pixel format conversion
• Memory-to-memory with pixel format conversion and blending

The AHB slave port is used to program the DMA2D controller.

The block diagram of the DMA2D is shown in the figure below.

Figure 29. DMA2D block diagram

The block diagram illustrates the internal architecture of the DMA2D controller. At the top, an 'AHB MASTER' interface connects to the internal bus. Below it, the 'FG PFC' (Foreground Pixel Format Conversion) block contains an 'Expander' that takes 32-bit RGB input and produces 32-bit output with an 8-bit alpha channel. It also features 'Color mode' and 'α mode' settings, and an 'α' multiplier. A 'FG FIFO' feeds into the expander. The output of the expander goes to a 'CLUT itf' (Color Look-Up Table interface), which is connected to a '256x32-bit RAM'. Below the foreground path, the 'BG PFC' (Background Pixel Format Conversion) block has a similar structure with its own 'Expander', 'Color mode', 'α mode', and 'α' multiplier. A 'BG FIFO' feeds into this expander. Its output also goes to a 'CLUT itf' connected to another '256x32-bit RAM'. Both CLUT interfaces feed into a 'BLENDER' block, which takes 'α', 'Red', 'Green', and 'Blue' inputs and produces a 32-bit output. This output goes to an 'OUT PFC' (Output Pixel Format Conversion) block containing a 'Converter' with 'Color mode' settings. The converter's output goes to an 'OUT FIFO'. At the bottom, an 'AHB SLAVE' interface is shown. The diagram is labeled 'MS30439V1' in the bottom right corner.

Figure 29. DMA2D block diagram

9.3.2 DMA2D control

The DMA2D controller is configured through the DMA2D control register (DMA2D_CR).

The user application can perform the following operations:

• Select the operating mode.
• Enable/disable the DMA2D interrupt.
• Start/suspend/abort ongoing data transfers.

9.3.3 DMA2D foreground and background FIFOs

The DMA2D foreground (FG) FIFO and background (BG) FIFO fetch the input data to be copied and/or processed.

These FIFOs fetch the pixels according to the color format defined in their respective pixel format converter (PFC). They are programmed through a set of control registers:

• DMA2D foreground memory address register (DMA2D_FGMAR)
• DMA2D foreground offset register (DMA2D_FGOR)
• DMA2D background memory address register (DMA2D_BGMAR)
• DMA2D background offset register (DMA2D_BGBOR)
• DMA2D number of lines register (number of lines and pixel per lines) (DMA2D_NLR)

When the DMA2D operates in register-to-memory mode, none of the FIFOs is activated.

When the DMA2D operates in memory-to-memory mode (no pixel format conversion nor blending operation), only the FG FIFO is activated and acts as a buffer.

When the DMA2D operates in memory-to-memory operation with pixel format conversion (no blending operation), the BG FIFO is not activated.

9.3.4 DMA2D foreground and background pixel format converter (PFC)

DMA2D foreground pixel format converter (PFC) and background pixel format converter perform the pixel format conversion to generate a 32-bit per pixel value. The PFC can also modify the alpha channel.

The first stage of the converter converts the color format. The original color format of the foreground pixel and background pixels are configured through the CM[3:0] bits of the DMA2D_FGPFCCR and DMA2D_BGPFCR, respectively.

The supported input formats are given in the table below.

Table 37. Supported color mode in input

CM[3:0]	Color mode
0000	ARGB8888
0001	RGB888
0010	RGB565
0011	ARGB1555
0100	ARGB4444
0101	L8

Table 37. Supported color mode in input (continued)

CM[3:0]	Color mode
0110	AL44
0111	AL88
1000	L4
1001	A8
1010	A4

The color format is coded as follows:

Alpha value field: transparency
0xFF value corresponds to an opaque pixel and 0x00 to a transparent one.
R field for Red
G field for Green
B field for Blue
L field: luminance

This field is the index to a CLUT to retrieve the three/four RGB/ARGB components.

If the original format is direct color mode (ARGB/RGB), the extension to 8 bits per channel is performed by copying the MSBs into the LSBs. This ensures a perfect linearity of the conversion.

If the original format is indirect color mode (L/AL), a CLUT is required and each pixel format converter is associated with a 256 entry 32-bit CLUT.

If the original format does not include an alpha channel, the alpha value is automatically set to 0xFF (opaque).

For the specific alpha mode A4 and A8, no color information is stored nor indexed. The color to be used for the image generation is fixed and is defined in the DMA2D_FGCOLR for foreground pixels and in the DMA2D_BGCOLR register for background pixels.

The order of the fields in the system memory is defined in the table below.

Table 38. Data order in memory

Color Mode	@ + 3	@ + 2	@ + 1	@ + 0
ARGB8888	A ₀[7:0]	R ₀[7:0]	G ₀[7:0]	B ₀[7:0]
RGB888	B ₁[7:0]	R ₀[7:0]	G ₀[7:0]	B ₀[7:0]
	G ₂[7:0]	B ₂[7:0]	R ₁[7:0]	G ₁[7:0]
	R ₃[7:0]	G ₃[7:0]	B ₃[7:0]	R ₂[7:0]
RGB565	R ₁[4:0]G ₁[5:3]	G ₁[2:0]B ₁[4:0]	R ₀[4:0]G ₀[5:3]	G ₀[2:0]B ₀[4:0]
ARGB1555	A ₁[0]R ₁[4:0]G ₁[4:3]	G ₁[2:0]B ₁[4:0]	A ₀[0]R ₀[4:0]G ₀[4:3]	G ₀[2:0]B ₀[4:0]
ARGB4444	A ₁[3:0]R ₁[3:0]	G ₁[3:0]B ₁[3:0]	A ₀[3:0]R ₀[3:0]	G ₀[3:0]B ₀[3:0]
L8	L ₃[7:0]	L ₂[7:0]	L ₁[7:0]	L ₀[7:0]
AL44	A ₃[3:0]L ₃[3:0]	A ₂[3:0]L ₂[3:0]	A ₁[3:0]L ₁[3:0]	A ₀[3:0]L ₀[3:0]
AL88	A ₁[7:0]	L ₁[7:0]	A ₀[7:0]	L ₀[7:0]

Table 38. Data order in memory (continued)

L4	L ₇[3:0]L ₆[3:0]	L ₅[3:0]L ₄[3:0]	L ₃[3:0]L ₂[3:0]	L ₁[3:0]L ₀[3:0]
A8	A ₃[7:0]	A ₂[7:0]	A ₁[7:0]	A ₀[7:0]
A4	A ₇[3:0]A ₆[3:0]	A ₅[3:0]A ₄[3:0]	A ₃[3:0]A ₂[3:0]	A ₁[3:0]A ₀[3:0]

The 24-bit RGB888 aligned on 32 bits is supported through the ARGB8888 mode.

Once the 32-bit value is generated, the alpha channel can be modified according to AM[1:0] in DMA2D_FGPFCCR/DMA2D_BGPFCCR registers as shown in the table below.

The alpha channel can be:

• kept as it is (no modification)
• replaced by the ALPHA[7:0] value of DMA2D_FGPFCCR/DMA2D_BGPFCCR
• replaced by the original alpha value multiplied by the ALPHA[7:0] value of DMA2D_FGPFCCR/DMA2D_BGPFCCR divided by 255.

Table 39. Alpha mode configuration

AM[1:0]	Alpha mode
00	No modification
01	Replaced by value in DMA2D_xxPFCCR
10	Replaced by original value multiplied by the value in DMA2D_xxPFCCR / 255
11	Reserved

Note: To support the alternate format, the incoming alpha value can be inverted setting AI in DMA2D_FGPFCCR/DMA2D_BGPFCCR registers. This applies also to the Alpha value stored in the DMA2D_FGPFCCR/DMA2D_BGPFCCR and in the CLUT.

The R and B fields can also be swapped setting RBS in DMA2D_FGPFCCR/DMA2D_BGPFCCR registers. This applies also to the RGB order used in the CLUT and in the DMA2D_FGCOLR/DMA2D_BGCOLR registers.

9.3.5 DMA2D foreground and background CLUT interface

The CLUT interface manages the CLUT memory access and the automatic loading of the CLUT.

Three access types are possible:

• CLUT read by the PFC during pixel format conversion operation
• CLUT accessed through the AHB slave port when the CPU is reading or writing data into the CLUT
• CLUT written through the AHB master port when an automatic loading of the CLUT is performed

The CLUT memory loading can be done in two different ways:

• Automatic loading

The following sequence must be followed to load the CLUT:

a) Program the CLUT address in DMA2D_FGCMAR (foreground CLUT) or DMA2D_BGCMAR (background CLUT).
b) Program the CLUT size with CS[7:0] in DMA2D_FGPFCCR (foreground CLUT) or DMA2D_BGPFCCR (background CLUT).
c) Set the START bit in DMA2D_FGPFCCR (foreground CLUT) or DMA2D_BGPFCCR (background CLUT) to start the transfer. During this automatic loading process, the CLUT is not accessible by the CPU. If a conflict occurs, a CLUT access error interrupt is raised assuming CAEIE = 1 in DMA2D_CR.

• Manual loading

The application has to program the CLUT manually through the DMA2D AHB slave port to which the local CLUT memory is mapped. The foreground CLUT (FGCLUT) is located at address offset 0x0400 and the background CLUT (BGCLUT) at address offset 0x0800.

The CLUT format is 24 or 32 bits. It is configured through the CCM bit in DMA2D_FGPFCCR (foreground CLUT) or DMA2D_BGPFCCR (background CLUT) as shown in the table below.

Table 40. Supported CLUT color mode

CCM	CLUT color mode
0	32-bit ARGB8888
1	24-bit RGB888

The way the CLUT data are organized in the system memory is specified in the table below.

Table 41. CLUT data order in system memory

CLUT color mode	@ + 3	@ + 2	@ + 1	@ + 0
ARGB8888	A ₀[7:0]	R ₀[7:0]	G ₀[7:0]	B ₀[7:0]
RGB888	B ₁[7:0]	R ₀[7:0]	G ₀[7:0]	B ₀[7:0]
	G ₂[7:0]	B ₂[7:0]	R ₁[7:0]	G ₁[7:0]
	R ₃[7:0]	G ₃[7:0]	B ₃[7:0]	R ₂[7:0]

9.3.6 DMA2D blender

The DMA2D blender blends the source pixels by pair to compute the resulting pixel.

The blending is performed according to the following equation:

\text{with } \alpha_{\text{Mult}} = \frac{\alpha_{\text{FG}} \cdot \alpha_{\text{BG}}}{255}

\alpha_{\text{OUT}} = \alpha_{\text{FG}} + \alpha_{\text{BG}} - \alpha_{\text{Mult}}

C_{\text{OUT}} = \frac{C_{\text{FG}} \cdot \alpha_{\text{FG}} + C_{\text{BG}} \cdot \alpha_{\text{BG}} - C_{\text{BG}} \cdot \alpha_{\text{Mult}}}{\alpha_{\text{OUT}}} \quad \text{with } C = R \text{ or } G \text{ or } B

Division is rounded to the nearest lower integer

No configuration register is required by the blender. The blender use depends on the DMA2D operating mode defined by MODE[1:0] in DMA2D_CR.

9.3.7 DMA2D output PFC

The output PFC performs the pixel format conversion from 32 bits to the output format defined by CM[2:0] in DMA2D_OPFCCR.

The supported output formats are given in the table below.

Table 42. Supported color mode in output

CM[2:0]	Color mode
000	ARGB8888
001	RGB888
010	RGB565
011	ARGB1555
100	ARGB4444

Note: To support the alternate format, the calculated alpha value is inverted setting AI bit in DMA2D_OPFCCR. This applies also to the alpha value used in DMA2D_OCOLR. The R and B fields can also be swapped setting RBS in DMA2D_OPFCCR. This applies also to the RGB order used in DMA2D_OCOLR.

9.3.8 DMA2D output FIFO

The output FIFO programs the pixels according to the color format defined in the output PFC.

The destination area is defined through a set of control registers:

• DMA2D output memory address register (DMA2D_OMAR)

• DMA2D output offset register (DMA2D_OOR)
• DMA2D number of lines register (number of lines and pixel per lines) (DMA2D_NLR)

If the DMA2D operates in register-to-memory mode, the configured output rectangle is filled by the color specified in DMA2D_OCOLR which contains a fixed 32-, 24-, or 16-bit value. The format is selected by CM[2:0] in DMA2D_OPFCCR.

The data are stored into the memory in the order defined in the table below.

Table 43. Data order in memory

Color mode	@ + 3	@ + 2	@ + 1	@ + 0
ARGB8888	A ₀[7:0]	R ₀[7:0]	G ₀[7:0]	B ₀[7:0]
RGB888	B ₁[7:0]	R ₀[7:0]	G ₀[7:0]	B ₀[7:0]
	G ₂[7:0]	B ₂[7:0]	R ₁[7:0]	G ₁[7:0]
	R ₃[7:0]	G ₃[7:0]	B ₃[7:0]	R ₂[7:0]
RGB565	R ₁[4:0]G ₁[5:3]	G ₁[2:0]B ₁[4:0]	R ₀[4:0]G ₀[5:3]	G ₀[2:0]B ₀[4:0]
ARGB1555	A ₁[0]R ₁[4:0]G ₁[4:3]	G ₁[2:0]B ₁[4:0]	A ₀[0]R ₀[4:0]G ₀[4:3]	G ₀[2:0]B ₀[4:0]
ARGB4444	A ₁[3:0]R ₁[3:0]	G ₁[3:0]B ₁[3:0]	A ₀[3:0]R ₀[3:0]	G ₀[3:0]B ₀[3:0]

The RGB888 aligned on 32 bits is supported through the ARGB8888 mode.

9.3.9 DMA2D AHB master port timer

An 8-bit timer is embedded into the AHB master port to provide an optional limitation of the bandwidth on the crossbar.

This timer is clocked by the AHB clock and counts a dead time between two consecutive accesses. This limits the bandwidth availability.

The timer enabling and the dead time value are configured through the AHB master port timer configuration register (DMA2D_AMPTCR).

9.3.10 DMA2D transactions

DMA2D transactions consist of a sequence of a given number of data transfers. The number of data and the width can be programmed by software.

Each DMA2D data transfer is composed of up to four steps:

1. Data loading from the memory location pointed by DMA2D_FGMAR and pixel format conversion as defined in DMA2D_FGCR
2. Data loading from a memory location pointed by DMA2D_BGMAR and pixel format conversion as defined in DMA2D_BGCR
3. Blending of all retrieved pixels according to the alpha channels resulting of the PFC operation on alpha values
4. Pixel format conversion of the resulting pixels according to DMA2D_OCR and programming of the data to the memory location addressed through DMA2D_OMAR

9.3.11 DMA2D configuration

Both source and destination data transfers can target peripherals and memories in the whole 4 Gbyte memory area, at addresses ranging between 0x0000 0000 and 0xFFFF FFFF.

The DMA2D can operate in any of the following modes selected through MODE[1:0] in DMA2D_CR:

• Register-to-memory
• Memory-to-memory
• Memory-to-memory with PFC
• Memory-to-memory with PFC and blending

Register-to-memory

The register-to-memory mode is used to fill a user defined area with a predefined color.

The color format is set in DMA2D_OPFCCR.

The DMA2D does not perform any data fetching from any source. It just writes the color defined in DMA2D_OCOLR to the area located at the address pointed by DMA2D_OMAR, and defined in DMA2D_NLR and DMA2D_OOR.

Memory-to-memory

In memory-to-memory mode, the DMA2D does not perform any graphical data transformation. The foreground input FIFO acts as a buffer and the data are transferred from the source memory location defined in DMA2D_FGMAR to the destination memory location pointed by DMA2D_OMAR.

The color mode programmed by CM[3:0] in DMA2D_FGPFCCR defines the number of bits per pixel for both input and output.

The size of the area to be transferred is defined by DMA2D_NLR and DMA2D_FGOR for the source, and by DMA2D_NLR and DMA2D_OOR for the destination.

Memory-to-memory with PFC

In this mode, the DMA2D performs a pixel format conversion of the source data and stores them in the destination memory location.

The size of the areas to be transferred are defined by DMA2D_NLR and DMA2D_FGOR for the source, and by DMA2D_NLR and DMA2D_OOR for the destination.

Data are fetched from the location defined in DMA2D_FGMAR and processed by the foreground PFC. The original pixel format is configured through DMA2D_FGPFCCR.

If the original pixel format is direct color mode, then the color channels are all expanded to 8 bits.

If the pixel format is indirect color mode, the associated CLUT has to be loaded into the CLUT memory.

The CLUT loading can be done automatically by following the sequence below:

1. Set the CLUT address into DMA2D_FGCMAR.
2. Set the CLUT size with CS[7:0] bits in DMA2D_FGPFCCR.
3. Set the CLUT format (24 or 32 bits) with CCM in DMA2D_FGPFCCR.
4. Start the CLUT loading by setting START in DMA2D_FGPFCCR.

Once the CLUT loading is complete, the CTCIF flag in DMA2D_IFR is raised, and an interrupt is generated if CTCIE = 1 in DMA2D_CR. The automatic CLUT loading process can not work in parallel with classical DMA2D transfers.

The CLUT can also be filled by the CPU or by any other master through the APB port. The access to the CLUT is not possible when a DMA2D transfer is ongoing and uses the CLUT (indirect color format).

In parallel to the color conversion process, the alpha value is added or changed depending on the value programmed in DMA2D_FGPFCCR. If the original image does not have an alpha channel, a default alpha value of 0xFF is automatically added to obtain a fully opaque pixel. The alpha value is modified according to AM[1:0] in DMA2D_FGPFCCR:

• It can be unchanged.
• It can be replaced by the value defined by ALPHA[7:0] in DMA2D_FGPFCCR.
• It can be replaced by the original value multiplied by ALPHA[7:0] divided by 255.

The resulting 32-bit data are encoded by the OUT PFC into the format specified by CM[2:0] in DMA2D_OPFCCR. The output pixel format cannot be the indirect mode since no CLUT generation process is supported.

The processed data are written into the destination memory location pointed by DMA2D_OMAR.

Memory-to-memory with PFC and blending

In this mode, two sources are fetched in the foreground and background FIFOs from the memory locations defined by DMA2D_FGMAR and DMA2D_BGMAR.

The two pixel format converters have to be configured as described in the memory-to-memory mode. Their configurations can be different as each pixel format converter is independent and has its own CLUT memory.

Once each pixel has been converted into 32 bits by its respective PFC, all pixels are blended according to the equation below:

\text{with } \alpha_{\text{Mult}} = \frac{\alpha_{\text{FG}} \cdot \alpha_{\text{BG}}}{255}

\alpha_{\text{OUT}} = \alpha_{\text{FG}} + \alpha_{\text{BG}} - \alpha_{\text{Mult}}

C_{\text{OUT}} = \frac{C_{\text{FG}} \cdot \alpha_{\text{FG}} + C_{\text{BG}} \cdot \alpha_{\text{BG}} - C_{\text{BG}} \cdot \alpha_{\text{Mult}}}{\alpha_{\text{OUT}}} \quad \text{with } C = R \text{ or } G \text{ or } B

Division are rounded to the nearest lower integer

The resulting 32-bit pixel value is encoded by the output PFC according to the specified output format, and the data are written into the destination memory location pointed by DMA2D_OMAR.

Configuration error detection

The DMA2D checks that the configuration is correct before any transfer. The configuration error interrupt flag is set by hardware when a wrong configuration is detected when a new transfer/automatic loading starts. An interrupt is then generated if CEIE = 1 in DMA2D_CR.

The wrong configurations that can be detected are listed below:

• Foreground CLUT automatic loading: MA bits in DMA2D_FGCMAR are not aligned with CCM in DMA2D_FGPFCCR.
• Background CLUT automatic loading: MA bits in DMA2D_BGCMAR are not aligned with CCM in DMA2D_BGPFCCR.
• Memory transfer (except in register-to-memory mode): MA bits in DMA2D_FGMAR are not aligned with CM in DMA2D_FGPFCCR.
• Memory transfer (except in register-to-memory mode): CM bits in DMA2D_FGPFCCR are invalid
• Memory transfer (except in register-to-memory mode and except in memory-to-memory mode with blending and fixed color FG): PL bits in DMA2D_NLR are odd while CM in DMA2D_FGPFCCR is A4 or L4.
• Memory transfer (except in register-to-memory mode): LO bits in DMA2D_FGOR are odd while CM in DMA2D_FGPFCCR is A4 or L4.
• Memory transfer (only in blending mode): MA bits in DMA2D_BGMAR are not aligned with CM in DMA2D_BGPFCCR.
• Memory transfer: (only in blending mode): CM bits in DMA2D_BGPFCCR are invalid
• Memory transfer (only in blending mode): PL bits in DMA2D_NLR odd while CM in DMA2D_BGPFCCR is A4 or L4.
• Memory transfer (only in blending mode): LO bits in DMA2D_BGOR are odd while CM in DMA2D_BGPFCCR is A4 or L4.
• Memory transfer (except in memory-to-memory mode): MA bits in DMA2D_OMAR are not aligned with CM bits in DMA2D_OPFCCR.
• Memory transfer (except in memory to memory mode): CM bits in DMA2D_OPFCCR are invalid.
• Memory transfer: NL = 0x0 in DMA2D_NLR
• Memory transfer: PL = 0x0 in DMA2D_NLR

9.3.12 DMA2D transfer control (start, suspend, abort and completion)

Once the DMA2D is configured, the transfer can be launched by setting START in DMA2D_CR. Once the transfer is completed, START is automatically reset and TCIF flag in DMA2D_ISR is raised. An interrupt can be generated if TCIE is set in DMA2D_CR.

The user application can suspend the DMA2D at any time by setting SUSP in DMA2D_CR. The transaction can then be aborted by setting ABORT in DMA2D_CR, or can be restarted by resetting SUSP in DMA2D_CR.

The user application can abort at any time an ongoing transaction by setting ABORT in DMA2D_CR. In this case, the TCIF flag is not raised.

Automatic CLUT transfers can also be aborted or suspended by using ABORT or SUSP in DMA2D_CR.

9.3.13 Watermark

A watermark can be programmed to generate an interrupt when the last pixel of a given line has been written to the destination memory area.

The line number is defined by LW[15:0] in DMA2D_LWR.

When the last pixel of this line has been transferred, the TWIF flag in DMA2D_ISR is raised, and an interrupt is generated if TWIE is set in DMA2D_CR.

9.3.14 Error management

Two kind of errors can be triggered:

• AHB master port errors signaled by TEIF in DMA2D_ISR
• conflicts caused by a CLUT access (CPU trying to access the CLUT while a CLUT loading or a DMA2D transfer is ongoing) signaled by CAEIF in DMA2D_ISR.

Both flags are associated to their own interrupt enable flag in DMA2D_CR to generate an interrupt if need be (TEIE and CAEIE).

9.3.15 AHB dead time

To limit the AHB bandwidth use, a dead time between two consecutive AHB accesses can be programmed.

This feature can be enabled by setting EN in DMA2D_AMTCR.

The dead time value is stored into DT[7:0] in DMA2D_AMTCR. This value represents the guaranteed minimum number of cycles between two consecutive transactions on the AHB bus.

The update of the dead time value while the DMA2D runs is taken into account for the next AHB transfer.

9.4 DMA2D interrupts

An interrupt can be generated on the following events:

• Configuration error
• CLUT transfer complete
• CLUT access error
• Transfer watermark reached
• Transfer complete
• Transfer error

Separate interrupt enable bits are available for flexibility.

Table 44. DMA2D interrupt requests

Interrupt event	Event flag	Enable control bit
Configuration error	CEIF	CEIE
CLUT transfer complete	CTCIF	CTCIE
CLUT access error	CAEIF	CAEIE
Transfer watermark	TWF	TWIE
Transfer complete	TCIF	TCIE
Transfer error	TEIF	TEIE

9.5 DMA2D registers

9.5.1 DMA2D control register (DMA2D_CR)

Address offset: 0x000

Reset value: 0x0000 0000

31	30	29	28	27	26	25	24	23	22	21	20	19	18	17	16
Res.	Res.	Res.	Res.	Res.	Res.	Res.	Res.	Res.	Res.	Res.	Res.	Res.	Res.	MODE[1:0]
														rw	rw
15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
Res.	Res.	CEIE	CTCIE	CAEIE	TWIE	TCIE	TEIE	Res.	Res.	Res.	Res.	Res.	ABORT	SUSP	START
		rw	rw	rw	rw	rw	rw						rs	rw	rs

Bits 31:18 Reserved, must be kept at reset value.

Bits 17:16 MODE[1:0] : DMA2D mode

These bits are set and cleared by software. They cannot be modified while a transfer is ongoing.

00: Memory-to-memory (FG fetch only)

01: Memory-to-memory with PFC (FG fetch only with FG PFC active)

10: Memory-to-memory with blending (FG and BG fetch with PFC and blending)

11: Register-to-memory (no FG nor BG, only output stage active)

Bits 15:14 Reserved, must be kept at reset value.

Bit 13 CEIE : Configuration error interrupt enable