4.5. CDD DMA Module
4.5.1. Acronyms and Definitions
Abbreviation/Term |
Explanation |
|---|---|
AUTOSAR |
Automotive Open System Architecture |
BSW |
Basic Software |
DET |
Default Error Tracer |
CDD |
Complex Device Driver |
DMA |
Direct Memory Access |
ISR |
Interrupt Service Routine |
INT |
Interrupt |
HW |
Hardware |
SW |
Software |
MCU |
Micro Controller Unit |
OS |
Operating System |
API |
Application Programming Interface |
4.5.2. Introduction
This document describes the functionality and configuration of the Cdd_Dma module.
Supported AUTOSAR Release |
4.3.1 |
|---|---|
Supported Configuration Variants |
Pre-Compile |
Vendor ID |
DMA_VENDOR_ID (44) |
Module ID |
DMA_MODULE_ID (255) |
Supported Platform |
AM263Px |
The Cdd_Dma module initiates memory transfer without the intervention of the CPU and used in data transfer within peripheral, based on DMA channel configured.
4.5.3. Functional Overview
Cdd_Dma Driver using HW IP “EDMA”(Enhanced DMA). EDMA performs high-performance data transfer between two target endpoints, memories and peripheral devices without microcontroller support during transfer. EDMA transfer is programmed through a logical EDMA channel which allows the transfer to be optimally tailored to the requirements of the application.
The EDMA controller is based on two major principal blocks:
• EDMA third-party channel controller (EDMA_TPCC)
• EDMA third-party transfer controller (EDMA_TPTC)
Fig. 4.25 Basic Working Principle
The TPCC is a high flexible channel controller that serves as both a user interface and an event interface for the EDMA controller. The EDMA_TPCC serves to prioritize incoming software requests or events from peripherals, and submits transfer requests (TRs) to the transfer controller.
The TPTC performs read and write transfers by EDMA ports to the target peripherals, as programmed in the Active and Pending set of the registers. The transfer controllers are responsible for data movement, and issue read/write commands to the source and destination addresses programmed for a given transfer in the EDMA_TPCC.
The Cdd_Dma module has 64 EDMA channels, which serves the purpose of driving transferring of data.
4.5.3.1. Initialization
Cdd_Dma_Init() has to be called to initialize the Cdd_Dma driver.
4.5.3.2. States
None
4.5.3.3. Assumptions
None
4.5.3.4. Limitations
Below are the IP’s that needed software workaround with EDMA because of the HW Limitations -
UART : A dummy PaRAM needs to be linked to the actual TX PaRAM. This is because UART generates TX empty event after the last character is transferred and it results in an event miss error being set in EDMA (since the TX PaRAM has already been used up for the transfer). A dummy PaRAM set is linked to the actual TX PaRAM to service the extra event generated.
McSpi : Above scenario also applies to McSPI. A dummy PaRAM set is linked to solve the issue.
NOTE: Both of these above limitations are taken care internally by UART and McSpi driver respectively.
4.5.3.5. Design overview
Will be updated in future release
4.5.4. Hardware Features
4.5.4.1. IP Supported Features
EDMA channels are supported.
Both memory transfer and transfer within peripheral is supported.
Both interrupt mode and polling mode are supported.
Linking of multiple params are supported.
Chaining of multiple channels are supported.
4.5.4.2. Not supported Features
QDMA is not supported.
4.5.4.3. Non compliance
4.5.4.3.1. Deviations to requirements (Requirement Traceability)
4.5.4.3.1.1. Deviation of requirements against AUTOSAR specification requirements
None
4.5.5. Source files
Static source C Files are defined below
📦AM263Px
┣ 📂build
┣ 📂mcal
┃ ┣ 📂Dma
┃ ┃ ┣ 📂include
┃ ┃ ┃ ┣ 📜Cdd_Dma.h : Contains the API’s of the Cdd_Dma driver to be used by upper layers.
┃ ┃ ┃ ┣ 📜Cdd_Dma_cslr_tpcc.h : Contains Internal functions definition and initialization of Cdd_Dma driver.
┃ ┃ ┃ ┣ 📜Cdd_Dma_cslr_tptc.h : Contains Internal functions definition and initialization of Cdd_Dma driver.
┃ ┃ ┃ ┣ 📜Cdd_Dma_edma.h : Contains Internal functions definition and initialization of Cdd_Dma driver.
┃ ┃ ┃ ┣ 📜Cdd_Dma_Irq.h : Contains ISR function declaration.
┃ ┃ ┃ ┗ 📜Cdd_Dma_Priv.h : Contains Internal functions definition and initialization of Cdd_Dma driver.
┃ ┃ ┣ 📂src
┃ ┃ ┃ ┣ 📜Cdd_Dma.c : Contains the implementation of the API’s for Cdd_Dma driver.
┃ ┃ ┃ ┣ 📜Cdd_Dma_Irq.c : Contains ISR function definitions.
┃ ┃ ┃ ┗ 📜Cdd_Dma_Priv.c : Contains Internal functions definition and initialization of Cdd_Dma driver.
┃ ┃ ┣ 📂V0
┃ ┃ ┃ ┗ 📜Cdd_Dma_dmaxbar.h : Contains DMA cross bar interrupt information.
┃ ┃ ┃ ┣ 📜Cdd_Dma_soc.c : Contains device specific a function definition, data types and definitions.
┃ ┃ ┃ ┗ 📜Cdd_Dma_trig_xbar.h : Contains DMA cross bar interrupt information.
┃ ┃ ┃ ┣ 📜Cdd_Dma_xbar.h : Contains DMA cross bar interrupt information.
┃ ┃ ┗ 📜Makefile
┃ 📂mcal_config
┃ 📂mcal_docs
┃ 📜README.txt
Plugin files are defined below in the table.
Plugin Files |
Description |
|---|---|
CDD_Dma_Cfg.h |
Contains the Precompile switches, Symbolic names of the handles and xbar, HW units |
CDD_Dma_Cfg.c |
contains the configuration parameters |
4.5.6. Module requirements
Please refer Software Product Specification document provided as part of CSP.
4.5.6.1. Memory Mapping
Memory Mapping Sections |
CDD_DMA_CODE |
CDD_DMA_CODE_ISR |
CDD_DMA_VAR_NO_INIT |
CDD_DMA_VAR |
CDD_DMA_CFG |
|---|---|---|---|---|---|
CDD_DMA_START_SEC_VAR_INIT_8 (.bss) |
x |
||||
CDD_DMA_STOP_SEC_VAR_INIT_8 |
x |
||||
CDD_DMA_START_SEC_CONFIG_DATA (.const) |
x |
||||
CDD_DMA_STOP_SEC_CONFIG_DATA |
x |
||||
CDD_DMA_START_SEC_CODE (.text) |
x |
||||
CDD_DMA_STOP_SEC_CODE |
x |
||||
CDD_DMA_START_SEC_VAR_INIT_32 (.bss) |
x |
||||
CDD_DMA_STOP_SEC_VAR_INIT_32 |
x |
||||
CDD_DMA_START_SEC_VAR_NO_INIT_UNSPECIFIED (.data) |
x |
||||
CDD_DMA_STOP_SEC_VAR_NO_INIT_UNSPECIFIED |
x |
||||
CDD_DMA_START_SEC_ISR_CODE |
x |
||||
CDD_DMA_STOP_SEC_ISR_CODE |
x |
4.5.6.2. Scheduling
There are no scheduled functions within the CDD DMA driver
4.5.6.3. Error handling
4.5.6.3.1. Development Error Reporting (DET)
In development mode, the Cdd_Dma module reports development error through the Det_ReportError function of module DET. The errors reported to DET are described in the following table
Type of Error |
Related Error code |
Value (Hex) |
|---|---|---|
API service called without module initialization. |
CDD_DMA_E_UNINIT |
0x01 |
API service for initialization is called when already initialized. |
CDD_DMA_E_ALREADY_INITIALIZED |
0x02 |
API parameter checking: invalid value. |
CDD_DMA_E_PARAM_VALUE |
0x03 |
API parameter checking: invalid pointer. |
CDD_DMA_E_PARAM_POINTER |
0x04 |
API service for indicating callback is already registered |
CDD_DMA_E_ALREADY_REGISTERED |
0x05 |
API service for indicating DMA handle already in use |
CDD_DMA_E_ALREADY_IN_PROGRESS |
0x06 |
4.5.6.3.2. Runtime Errors
None
4.5.7. Used resources
4.5.7.1. Interrupt Handling
Cdd_Dma driver provides ISR for transfer completion detection. The interrupt category must be configured in Cdd_Dma Driver and OS modules.
Respective ISR for each Cdd_Dma Instance in AM263Px are as follows:
Cdd_Dma Instances |
ISR Routines |
|---|---|
CDD_DMA_MSS_A |
CDD_EDMA_lld_transferCompletionMasterIsrFxn() |
CDD_DMA_MSS_A instance of Cdd_Dma has interrupt number as “72” in AM263Px.
4.5.8. Integration description
4.5.8.1. Dependent modules
4.5.8.1.1. MCU
The module MCU powers up the microcontroller’s peripherals at startup time and initializes the PLL as well as the internal clock domains which is connected to the Cdd_Dma unit.
The Cdd_Dma module will not take care of settings which configure the clock and PLL for channels in its init function. This must be done by the MCU module.
4.5.8.1.2. PORT
The Port driver configures the port pins used for the Cdd_Dma driver as input or output. Hence, the Port driver has to be initialized prior to the use of Cdd_Dma functions. Otherwise, Cdd_Dma driver functions will exhibit undefined behavior.
4.5.8.1.3. OS
An operating system can be used for task scheduling, interrupt handling, global suspend and restore of interrupts and creating of the Interrupt Vector Table.The Cdd_Dma module may use AUTOSAR OS to suspend and restore global interrupts.
4.5.8.1.4. DET
The module PWM depends on the DET (by default) in order to report development errors.
4.5.8.1.5. DEM
None
4.5.8.1.6. Callback Functions
None
4.5.8.1.7. Callback Notification
None
4.5.8.1.8. SchM (Optional)
If multiple AUTOSAR runnables have access to the same Data Store Memory block, the exported AUTOSAR specification enforces data consistency by using an AUTOSAR exclusive area. With this specification, the runnables have mutually exclusive access to the per-instance memory global data, which prevents data corruption. Beside the OS, the BSW Scheduler provides functions that DMA module calls at begin and end of critical sections. This implementation requires 1 level of exclusive access to guard critical sections.
The data consistency mechanism that has to be applied to an ExclusiveArea might be domain, ECU or even project specific. The decision which mechanism has to be applied by RTE / Basic Software Scheduler is taken during ECU integration by setting the Exclusive Area configuration parameter RteExclusiveAreaImplMechanism. This parameter is an input for RTE generator. For DMA Module, data consistency and exclusive access to critical sections are required for the following sections as shown in the table below:
Exclusive Area Functions used |
DMA Function calling Exclusive Area |
Need for Exclusive Area |
Recommended Exclusive Area Mapping |
|---|---|---|---|
DMA_EXCLUSIVE_AREA_0 |
Cdd_Edma_lld_intrRegister |
To protect against multiple access for shared resources |
ALL_INTERRUPT_BLOCKING : All interrupts should be blocked as this API’s can be called in the interrupts |
4.5.8.2. Multi-core support
Not supported
4.5.9. Configuration
4.5.9.1. CddDmaDriverHandler
This container contains the configuration parameters and sub containers of the AUTOSAR Complex device driver (CDD) module.
4.5.9.1.1. CddDmaTransferType
Item |
|
|---|---|
Name |
CddDmaTransferType |
Description |
This parameter selects the desired Transfer Type. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
CDD_DMA_TRANSFER_TYPE_MEMORY_TRANSFER |
Range |
CDD_DMA_TRANSFER_TYPE_UART_TX |
4.5.9.1.2. CddDmaInstance
Item |
|
|---|---|
Name |
CddDmaInstance |
Description |
This parameter selects the desired instance for DMA. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
CDD_DMA_MSS_A |
Range |
CDD_DMA_MSS_A |
4.5.9.1.3. CddDmaRegionID
Item |
|
|---|---|
Name |
CddDmaRegionID |
Description |
This parameter specifies the Region ID for EDMA. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
0 |
Max-value |
7 |
Min-value |
0 |
4.5.9.1.4. CddDmaTccNumber
Item |
|
|---|---|
Name |
CddDmaTccNumber |
Description |
This parameter specifies the TCC number for EDMA. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
0 |
Max-value |
63 |
Min-value |
0 |
4.5.9.1.5. CddDmaQueueNumber
Item |
|
|---|---|
Name |
CddDmaQueueNumber |
Description |
This parameter specifies the Default Queue Number for EDMA. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
0 |
Max-value |
1 |
Min-value |
0 |
4.5.9.1.6. CddDmaEnableInterrupt
Item |
|
|---|---|
Name |
CddDmaEnableInterrupt |
Description |
This determines whether interrupt needs to be registered. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
true |
4.5.9.1.7. CddDmaTransferModeSelect
Item |
|
|---|---|
Name |
CddDmaTransferModeSelect |
Description |
This parameter selects the desired Transfer Modeselect either normal or linking or chaining. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
CDD_DMA_TRANSFER_MODE_NORMAL |
Range |
CDD_DMA_TRANSFER_MODE_NORMAL |
4.5.9.1.8. CddDmaChannelGroup
This container contains the DMA Channel Group.
4.5.9.1.8.1. CddDmaChannel
Item |
|
|---|---|
Name |
CddDmaChannel |
Description |
This parameter select the channel number to be used. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
0 |
Max-value |
63 |
Min-value |
0 |
4.5.9.1.9. CddDmaParamSets
This container contains the DMA params.
4.5.9.1.9.1. CddDmaPramNumber
Item |
|
|---|---|
Name |
CddDmaPramNumber |
Description |
This parameter select the param number to be used. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
0 |
Max-value |
255 |
Min-value |
0 |
4.5.9.1.10. CddDmaChannelTriggerConfiguration
This container contains the DMA Channel Trigger reasource.
4.5.9.1.10.1. CddDmaDmaChannelModule
Item |
|
|---|---|
Name |
CddDmaDmaChannelModule |
Description |
The DMA channel selected for module. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
CDD_DMA_TRIG_XBAR_EDMA_MODULE_0 |
Range |
CDD_DMA_TRIG_XBAR_EDMA_MODULE_0 |
4.5.9.1.10.2. CddDmaChannelTriggerSource
Item |
|
|---|---|
Name |
CddDmaChannelTriggerSource |
Description |
Source to Trigger DMA Channel. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
CDD_DMA_TRIG_XBAR_DMA_XBAR_OUT_0 |
Range |
CDD_DMA_TRIG_XBAR_LIN0_RXDMA |
4.5.9.1.10.3. CddDmaDmaChannelXbar
Item |
|
|---|---|
Name |
CddDmaDmaChannelXbar |
Description |
DMA Channel Cross bar source. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
CDD_DMA_XBAR_DMA_TRIG_XBAR_0 |
Range |
CDD_DMA_XBAR_DMA_TRIG_XBAR_0 |
4.5.9.1.10.4. CddDmaDmaChannelXbarMap
Item |
|
|---|---|
Name |
CddDmaDmaChannelXbarMap |
Description |
DMA Channel Cross bar source. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
CDD_DMA_XBAR_ADC0_INT1 |
Range |
CDD_DMA_XBAR_EPWM0_SOCA |
4.5.9.2. CddDmaGeneral
General configuration settings for the Complex Device Driver
4.5.9.2.1. CddDmaVersionInfoApi
Item |
|
|---|---|
Name |
CddDmaVersionInfoApi |
Description |
Switches the Cdd_Dma_GetVersionInfo function ON or OFF. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
true |
4.5.9.2.2. CddDmaDeinitApi
Item |
|
|---|---|
Name |
CddDmaDeinitApi |
Description |
Switches the Cdd_Dma_DeInit function ON or OFF. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
true |
4.5.9.2.3. CddDmaDevErrorDetect
Item |
|
|---|---|
Name |
CddDmaDevErrorDetect |
Description |
Switches the Development Error Detection and Notification ON or OFF. |
Origin |
Texas Instruments |
Post-build-variant-multiplicity |
false |
Post-Build-Variant-Value |
false |
Value-Configuration-Class |
– |
Pre-Compile-Time |
VARIANT-PRE-COMPILE |
Default-value |
true |
4.5.10. Examples
4.5.10.1. Overview
Below 4 modes shall be verified using the examples
Chaining Mode
Interrupt Mode
Linking Mode
Polling Mode
Initialize the Timer using AppUtils_TimerInit()
Initialize the MCU for Clock configuration using Mcu_Init() and port using Port_Init()
Initialize the interrupt using Cdd_Dma_InterruptConfig() (Not applicable for Polling mode)
Start the timer using API start_timer()
Get the DMA version using Cdd_Dma_GetVersionInfo()
Initialize the DMA using Cdd_Dma_Init()
Set the DMA parameters using Cdd_Dma_ParamSet()
For Chaining Mode example,
Configure the Chaining Option
Link multiple DMA channels using Cdd_Dma_ChainChannel()
For Linking Mode example, link the DMA channels using Cdd_Dma_LinkChannel()
Register the callback function to be called once the transfer completed using Cdd_Dma_CbkRegister() (Not applicable for Polling Mode)
Enable the transfer region of the DMA transfer using API Cdd_Dma_EnableTransferRegion()
For Polling Mode example, status of the transfer is polled using API Cdd_Dma_GetStatus()
Verify the transfer status
4.5.10.2. Hardware Software Setup and Tools
None
4.5.10.3. Steps to build and run example
Cdd_Dma example applications demonstrates the MCAL CDD_DMA driver features, which is referred from folder <MCAL_ROOT>/examples/Dma.
There are 4 example applications provided to verify all the features of the module.
These applications can be built from the build folder by giving :
“gmake –s dma_pollingmode_app PLATFORM=am263px” for polling mode example
“gmake –s dma_interruptmode_app PLATFORM=am263px” for interrupt mode example
“gmake –s dma_linkingmode_app PLATFORM=am263px” for linking mode example
“gmake –s dma_chainingmode_app PLATFORM=am263px” for chaining mode example
In case of linking mode example multiple params are configured within the channel and once the execution gets completed with first paramSet then automatically second paramSet data will be loaded.
In case of chaining mode example multiple channels are chained together so in this case once the trigger for first channel happen for transmission it will internally trigger for second channel as well.So in this way with less number of trigger transmission happens.
Once the build is completed we get a binary file,which is loaded in our controller and executed.
4.5.10.4. Example Logs
=================================
DmaInterruptModeApp: Sample Application - STARTS !!!
DMA_CHAININGMODE_APP: DMA MCAL Version Info
---------------------
DMA_CHAININGMODE_APP: Vendor ID: 44
DMA_CHAININGMODE_APP: Module ID: 255
DMA_CHAININGMODE_APP: SW Major Version: 10
DMA_CHAININGMODE_APP: SW Minor Version: 0
DMA_CHAININGMODE_APP: SW Patch Version: 0
DMA_CHAININGMODE_APP: Variant - Pre Compile being used !!!
DMA_CHAININGMODE_APP: All tests have passed
===============================================
DmaInterruptModeApp: Sample Application - STARTS !!!
DMA_INTERRUPTMODE_APP: DMA MCAL Version Info
---------------------
DMA_INTERRUPTMODE_APP: Vendor ID: 44
DMA_INTERRUPTMODE_APP: Module ID: 255
DMA_INTERRUPTMODE_APP: SW Major Version: 10
DMA_INTERRUPTMODE_APP: SW Minor Version: 0
DMA_INTERRUPTMODE_APP: SW Patch Version: 0
DMA_INTERRUPTMODE_APP: Variant - Pre Compile being used !!!
DMA_INTERRUPTMODE_APP: All tests have passed
========================================
DmaInterruptModeApp: Sample Application - STARTS !!!
DMA_LINKINGMODE_APP: DMA MCAL Version Info
---------------------
DMA_LINKINGMODE_APP: Vendor ID: 44
DMA_LINKINGMODE_APP: Module ID: 255
DMA_LINKINGMODE_APP: SW Major Version: 10
DMA_LINKINGMODE_APP: SW Minor Version: 0
DMA_LINKINGMODE_APP: SW Patch Version: 0
DMA_LINKINGMODE_APP: Variant - Pre Compile being used !!!
DMA_LINKINGMODE_APP: All tests have passed
==============================================
DmaPollingModeApp: Sample Application - STARTS !!!
DMA_POLLINGMODE_APP: DMA MCAL Version Info
---------------------
DMA_POLLINGMODE_APP: Vendor ID: 44
DMA_POLLINGMODE_APP: Module ID: 255
DMA_POLLINGMODE_APP: SW Major Version: 10
DMA_POLLINGMODE_APP: SW Minor Version: 0
DMA_POLLINGMODE_APP: SW Patch Version: 0
DMA_POLLINGMODE_APP: Variant - Pre Compile being used !!!
DMA_POLLINGMODE_APP: All tests have passed
=================================================
4.5.10.5. File Structure
📦AM263Px
┣ 📂build
┣ 📂mcal
┃ ┣ 📂examples
┃ ┃ ┣ 📂Dma
┃ ┃ ┃ ┣ 📂Dma_ChainingMode
┃ ┃ ┃ ┃ ┣ 📂soc
┃ ┃ ┃ ┃ ┣ 📜DmaChainingModeApp.c : Contains DMA test example.
┃ ┃ ┃ ┃ ┣ 📜DmaChainingModeApp.h : Contains DMA test example header.
┃ ┃ ┃ ┃ ┣ 📜Makefile
┃ ┃ ┃ ┣ 📂Dma_InterruptMode
┃ ┃ ┃ ┃ ┣ 📂soc
┃ ┃ ┃ ┃ ┣ 📜DmaInterruptModeApp.c : Contains DMA test example.
┃ ┃ ┃ ┃ ┣ 📜DmaInterruptModeApp.h : Contains DMA test example header.
┃ ┃ ┃ ┃ ┣ 📜Makefile
┃ ┃ ┃ ┣ 📂Dma_LinkingMode
┃ ┃ ┃ ┃ ┣ 📂soc
┃ ┃ ┃ ┃ ┣ 📜DmaLinkingModeApp.c : Contains DMA test example.
┃ ┃ ┃ ┃ ┣ 📜DmaLinkingModeApp.h : Contains DMA test example header.
┃ ┃ ┃ ┃ ┣ 📜Makefile
┃ ┃ ┃ ┣ 📂Dma_PollingMode
┃ ┃ ┃ ┃ ┣ 📂soc
┃ ┃ ┃ ┃ ┣ 📜DmaPollingModeApp.c : Contains DMA test example.
┃ ┃ ┃ ┃ ┣ 📜DmaPollingModeApp.h : Contains DMA test example header.
┃ ┃ ┃ ┃ ┣ 📜Makefile
┃ ┣ 📂examples_config
┃ ┃ ┣ 📂Dma_Demo_Cfg
┃ ┃ ┃ ┣ 📂soc
┃ ┃ ┃ ┃ ┣ 📂am263px
┃ ┃ ┃ ┃ ┃ ┣ 📂r5f0_0
┃ ┃ ┃ ┃ ┃ ┃ ┣ 📂include
┃ ┃ ┃ ┃ ┃ ┃ ┃ ┣ 📜Cdd_Dma_Cfg.h : Contains the Precompile switches, Symbolic names.
┃ ┃ ┃ ┃ ┃ ┃ ┣ 📂src
┃ ┃ ┃ ┃ ┃ ┃ ┃ ┣ 📜Cdd_Dma_Cfg.c : Contains all Pre-Compile Configured parameters
┃ 📂mcal_config
┃ 📂mcal_docs
┣ 📜README.txt
4.5.11. FAQ’s
None