• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 234 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.

TMS320F28384S: CM4 uDMA channel assignment.

Luke Chen
Expert 5090 points
Part Number: TMS320F28384S


Hi champs,

According to TRM, CM4 uDMA μDMA channels 0-31 are assigned to different peripherals according to Table 49-1. The DMA Channel Map (DMACHMAPx) registers can be used to specify the first, second, or third channel mapping assignment.

We don't show detailed CHxxSEL information of register DMACHMAPx, how should we use the 4-bit fields in the registers? Always fill 0 into the fields?

If this is the case, we cannot specify the first, second or third channel assignment, is it correct?

Regards,

Luke

  • 0
    TI__Guru** 115881 points

    Hi Luke,

    You are right. Look like the channel mapping table is missing but on this device we had enough channels to map everything by default ( please see Table 49-1. μDMA Channel Assignment Mapping) hence there is no need to configure DMACHMAPx register other than default value. 

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Expert 5090 points

    Vivek,

    So we do have the channel mapping table, right? How can I get this information please?

    Regards,

    Luke

  • +1 in reply to Luke Chen
    TI__Guru** 115881 points

    Hi Luke,

    It is there but as I mentioned, all the peripheral interrupts are mapped by default. There are some channels where software is mapped for different values but those are also available on some of channels by default so practically you don't need this info. You can just use Table 49-1. μDMA Channel Assignment Mapping and leave the DMACHMAPx configuration to default value or write the default value.

    To fix the TRM, we'll try to update this info in next revision.

    Regards,

    Vivek Singh