This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

#20 identifier DMA0DA undefined..

Other Parts Discussed in Thread: MSP430G2553

hai,

    i am new to this forum..and i am new to this controller too...i m trying to run a program on DMA using ccs v6..but this throws an error like...

Description Resource Path Location Type
#20 identifier "DMA0TSEL7" is undefined main.c /dma line 20 C/C++ Problem
#20 identifier "DMA0SZ" is undefined main.c /dma line 19 C/C++ Problem
#20 identifier "DMA0DA" is undefined main.c /dma line 18 C/C++ Problem
#20 identifier "DMA0SA" is undefined main.c /dma line 17 C/C++ Problem
#20 identifier "DMA0CTL" is undefined main.c /dma line 28 C/C++ Problem

need the help from you all..to fix this problem..

thanks & regards,

senthil

  • Three possible reasons for that:

    1) You did not include the proper header-file for your specific controller.

    2) If the proper header-file is included, your device has no DMA.

    3) You included the header-file where your main.c can't "see" it.

  • hai dennis,
    thanks for your suggestion...and i verified it...your first reason suits my problem...i didnt include the proper header file for the controller..
    i am using msp430g2553...i modified the file..got the thing work..


    thanks & regards,
    senthil
  • The second reason mentioned by Dennis is your problem: The G2553 does not have a DMA controller. Changing the header file will make the compiler generate code to access the memory where the DMA controller registers would be, but this doesn’t make your DMA work. You can’t add a missing hardware capability by changing the header file.
    Not all modules described in the users guide are available on each MSP. If in doubt, check the datasheet.
    The G2553 only has a stripped-down ADC10-specific DMA controller called “DTC”, which can only move ADC10 results to memory.
    If you think you need to change something in the compiler-provided header files for a device, then in 99.99% of all cases, the header file is correct and you are wrong.

**Attention** This is a public forum