• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 437 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DMC Error Message

Windy
Prodigy 90 points

I work on the DM6446 Simulator "DM6446 Cycle Accurate Simulator" in CCS V3.3.

When I debugging,I've got a error message as below:

 >>DMC Error: Non Aligned access to the configuration space address 0x02df728d

How can I deal with it? 

If any suggesstin would be very appreciated!!

Thanks,

 

  • 0
    TI__Mastermind 37340 points

    what are you running ?  I suspect accessing memory via DMA or VPSS may require 32-byte alignment or similar addressing which is being violated.  Knowing a little bit more about the nature of what you are running may help.

  • 0
    Genius 4530 points

    Hi WIndy,

    Please check your GEL file and cmd file to ensure that the configuration space has been properly mapped as per DM6446 specifications.

    This is related to memory mapping problem in configuration space.

    If possible, post your GEL file here.

    Best of Luck

    Regards

    Sidharth

  • 0
    TI__Intellectual 1380 points

     

     

    I think you are trying to use memcpy or memset function to copy/fill data to a pointer declared in your program. Accidentally, this pointer might have been mapped to configuration-space memory, So, please check your linker command file and ensure that no region maps to  configiuraton-space. I recommend you to use the Internal SRAM regions and/or external memory region in linker command file. 

     

     

     

     

     

     

  • 0 in reply to Nizamudheen A
    Prodigy 90 points

    Thanks for all.

    I used dsp/bios configure file "evmDM6446", some cofigure information about MEM is wrote twice in textual configuation script file.

    I deleted the old tcf file and make a new tcf file.

    This problem is disappeared.