• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 32 subscribers
  • Views 644 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.

TMS570LS3137 DMA

Alan Day
Intellectual 920 points

Other Parts Discussed in Thread: TMS570LS3137, HALCOGEN

Hi

Could you tell me how the DMA HW requests are set in the TMS570LS3137?

I've looked through the TRM but had no luck, though another has been useful though for another TMS570

http://e2e.ti.com/support/microcontrollers/hercules/f/312/t/155766.aspx

 So when I have set

adcREG2->G0DMACR = 0x00000008;

DMAREQ[14] will be called so if I want channel 0 to service this request  I will need

dmaReqAssign(DMA_CH0,14);

is this correct, is the following still correct in the TMS570LS3137?

for a trigger from ADC1_EV

#define MIBADC1_EV_DMA_REQ         7

for ADC2_EV

#define MIBADC2_EV_DMA_REQ        14


Cheers,

Alan

  • 0
    TI__Genius 11645 points

    Hi Alan,

    can you please check if you have enabled the respective channel for servicing Hardware requests ?

    dmaSetChEnable(DMA_CH0, DMA_HW);

    Apart from that, you can find the example code in halcogen for mibspi (example_mibspiDma.c)

    DMA configuration part should be similar for ADC as well.

    Hope this helps.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Intellectual 920 points

    Hi,

    I've looked through the equivalent registers again ("ADEVDMACR" etc) and it the ADC does not have an equivalent to "TXDMA_MAPx" or "RXDMA_MAPx" for setting the request line.

    Which register is this hidden in?

    cheers,

    Alan

  • 0 in reply to Alan Day
    TI__Genius 11645 points

    Alan,

    Peripheral configuration to enable DMA requests are unique to a given peripheral, those configurations on MIBSPI may not be applicable in ADC(thats specific to MIBSPI where the same request can be brought out on any of the two lines of MIBSPI module which is connected to DMA module).

    But with ADC they go to their dedicated request line, so that step is not necessary.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Intellectual 920 points

    OK, I will restate my original question, maybe it was not clear enough, I can not find any info on the request lines in any of you documentations, I'm currently second guessing from other forum posts.  

    What are the dedicated request lines for the ADC module?  

    Can you give a complete breakdown of which request lines relate to mibADC1/2 -GroupEvent/1/2?

    Alan

     

  • 0 in reply to Alan Day
    TI__Guru 69070 points

    Alan,
    The DMA channel assignment map is in the Datasheet, not the TRM.
    Which device ?

     

  • 0 in reply to Anthony F. Seely
    Intellectual 920 points

    Hi Anthony,

    Thank you, in an almost 2000 page TRM why not just include all info?

    Anyway, thanks again.

    Alan

  • 0 in reply to Alan Day
    TI__Guru 69070 points

    Hi Alan,

    Sounds like you might have found the table in the datasheet then, just in case assuming this is the 3137 as the title says then it's on page 93 of the PDF.

    Your question is a good one and we're working across teams at TI to try to standardize our processor documentation formats to make it better for customers - so I'll take this as an input to that process.   We likely won't change the docs for this generation dramatically as the docs are maturing but for new products this is good input.

    Reason we split is the DMA and VIM assignments as well as memory map, pin out vary across devices in the family so these go into the datasheet.  Whereas we try to keep the TRM a 'family' document that's generic;  so you don't have 2000 pages for each part # to read.   But this does mean flipping around a lot between datasheet and TRM and is not convenient.   Probably there's a middle ground or a different solution using more of a dynamic format (rather than 'printed') - if you have ideas we'd love to hear them.

     

  • 0 in reply to Anthony F. Seely
    Intellectual 920 points

    Hi Anthony,


    I can understand the desired to have the TRM as a family document and if the overriding desire is to keep it that way then for the areas which are device specific why not tell the reader?  Include the section in your table of contents for easy access, explain that the information is in the datasheets and have a list of links to the relevant datasheets on your servers, that way the reader knows where the info is and can either look it up in their copy or click on the link. 


    regards,

    Alan