Why DMA is needed in Embedded C - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a DMA transfer.

Embedded C

DMA_StartTransfer([1]);

Drag options to blanks, or click blank then click option'

Adata

Bbuffer

Clength

Daddress

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the length instead of the data buffer.

Using the address variable which is not defined here.

The function DMA_StartTransfer needs the data buffer to begin the transfer.

2fill in blank

medium

Complete the code to check if DMA transfer is complete.

Embedded C

if (DMA_Status() == [1]) {
    // Transfer done
}

Drag options to blanks, or click blank then click option'

ADMA_DONE

BDMA_BUSY

CDMA_ERROR

DDMA_IDLE

Attempts:

3 left

💡 Hint

Common Mistakes

Checking for DMA_BUSY instead of DMA_DONE.

Using DMA_ERROR which means a problem occurred.

The status DMA_DONE indicates the DMA transfer has finished.

3fill in blank

hard

Fix the error in the DMA initialization code.

Embedded C

DMA_Init([1]);
DMA_StartTransfer(buffer, size);

Drag options to blanks, or click blank then click option'

Asize

Bbuffer

Cconfig

Daddress

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the data buffer to DMA_Init instead of config.

Passing size or address which are not config structures.

The DMA_Init function requires a configuration structure, not the buffer or size.

4fill in blank

hard

Fill both blanks to create a DMA transfer that moves data from memory to peripheral.

Embedded C

DMA_SetSource([1]);
DMA_SetDestination([2]);

Drag options to blanks, or click blank then click option'

Amemory_address

Bperipheral_address

Cbuffer

Dsize

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping source and destination addresses.

Using buffer or size instead of addresses.

The source is the memory address and the destination is the peripheral address for this transfer.

5fill in blank

hard

Fill all three blanks to configure DMA with correct parameters.

Embedded C

DMA_Config config = {
    .source = [1],
    .destination = [2],
    .length = [3]
};

Drag options to blanks, or click blank then click option'

Amemory_addr

Bperipheral_addr

Ctransfer_size

Dbuffer

Attempts:

3 left

💡 Hint

Common Mistakes

Using buffer instead of addresses.

Mixing up source and destination.

The DMA config needs source and destination addresses and the transfer size.

Practice

1. Why is DMA (Direct Memory Access) needed in embedded systems?

easy

A. To transfer data directly between memory and peripherals without CPU involvement

B. To increase the CPU clock speed automatically

C. To reduce the size of the memory

D. To replace the CPU in executing instructions

Solution

1. Step 1: Understand DMA's role

   DMA allows data transfer between memory and peripherals without using the CPU.

2. Step 2: Compare other options

   The other options describe unrelated functions not performed by DMA.

3. Final Answer:

   To transfer data directly between memory and peripherals without CPU involvement -> Option A

4. Quick Check:

   DMA moves data without CPU = C [OK]

Hint: DMA moves data without CPU, freeing CPU for other tasks [OK]

Common Mistakes:

• Thinking DMA increases CPU speed
• Confusing DMA with CPU instruction execution
• Believing DMA reduces memory size

2. Which of the following code snippets correctly enables DMA transfer in embedded C?

easy

A. DMA_StartTransfer();

B. enableDMA();

C. DMA_Enable();

D. DMA_TransferEnable();

Solution

1. Step 1: Identify common DMA function naming

   Typical DMA APIs use names like DMA_StartTransfer() to begin data transfer.

2. Step 2: Check other options

   The other options are not standard or correct function names in embedded C DMA libraries.

3. Final Answer:

   DMA_StartTransfer(); -> Option A

4. Quick Check:

   Correct DMA start function = A [OK]

Hint: DMA functions usually include 'Start' or 'Transfer' in name [OK]

Common Mistakes:

• Using incorrect or non-standard function names
• Confusing enabling DMA with starting transfer
• Assuming function names without checking documentation

3. Consider this embedded C code snippet using DMA:

DMA_Config(0x2000, 0x4000, 256);
CPU_Busy = 1;
while(CPU_Busy) {
  // CPU does other tasks
}
// DMA transfers 256 bytes from 0x2000 to 0x4000

What is the main benefit of using DMA here?

medium

A. CPU is idle and waits for DMA to finish

B. DMA copies data faster but blocks CPU completely

C. DMA slows down the CPU to avoid errors

D. CPU can perform other tasks while DMA transfers data

Solution

1. Step 1: Analyze CPU and DMA interaction

   CPU_Busy flag suggests CPU can do other tasks while DMA transfers data.

2. Step 2: Understand DMA advantage

   DMA transfers data independently, freeing CPU to work concurrently.

3. Final Answer:

   CPU can perform other tasks while DMA transfers data -> Option D

4. Quick Check:

   DMA frees CPU for other tasks = D [OK]

Hint: DMA allows CPU multitasking during data transfer [OK]

Common Mistakes:

• Assuming CPU waits idly for DMA
• Thinking DMA slows CPU
• Believing DMA blocks CPU completely

4. This embedded C code intends to use DMA but has a bug:

DMA_Config(src, dest, size);
while(!DMA_Complete()) {
  // wait
}
ProcessData(dest);

What is the likely problem here?

medium

A. DMA_Config() does not set source and destination correctly

B. ProcessData() is called before DMA transfer finishes

C. DMA_Complete() is checked before DMA starts transfer

D. The while loop causes CPU to freeze

Solution

1. Step 1: Check DMA transfer start

   DMA_Config() usually configures but does not start transfer; missing start call.

2. Step 2: Analyze DMA_Complete() check

   Checking DMA_Complete() before starting transfer causes infinite wait.

3. Final Answer:

   DMA_Complete() is checked before DMA starts transfer -> Option C

4. Quick Check:

   Start DMA before checking completion = A [OK]

Hint: Always start DMA transfer before checking completion [OK]

Common Mistakes:

• Not starting DMA transfer before waiting
• Calling processing function too early
• Assuming DMA_Config starts transfer automatically

5. You need to transfer a large continuous data stream from a sensor to memory without slowing down the CPU. Which approach best uses DMA to achieve this?

hard

A. Use CPU to copy data byte-by-byte in a loop for precise control

B. Configure DMA in circular mode to continuously transfer data while CPU processes other tasks

C. Disable DMA and use interrupts to handle each data byte

D. Transfer data only when CPU is idle to avoid conflicts

Solution

1. Step 1: Identify continuous data transfer need

   Large continuous data requires efficient, ongoing transfer without CPU blocking.

2. Step 2: Choose DMA mode

   Circular DMA mode allows continuous data streaming while CPU works on other tasks.

3. Step 3: Evaluate other options

   The other options cause CPU overhead or inefficient transfer.

4. Final Answer:

   Configure DMA in circular mode to continuously transfer data while CPU processes other tasks -> Option B

5. Quick Check:

   Continuous DMA circular mode = B [OK]

Hint: Use DMA circular mode for continuous data without CPU blocking [OK]

Common Mistakes:

• Using CPU loops for large data causing slowdowns
• Disabling DMA for interrupt handling overhead
• Waiting for CPU idle wasting time