• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 101 subscribers
  • Views 623 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.

PSP Questions

Herb
Prodigy 675 points

I’m attempting to convert a 6455 project for use on the 6748 platform. Because I use McBSP/EDMA3, I need to replace the fCSL definitions with their PSP/LLD equivalents. I’ve reviewed the information you sent and decided to try to use your McBspSampleMaster project as an example on how to do this. However, what I quickly noticed is that all the EDMA configuration is encapsulated in a function called “edma3init” that is not in the project. How is this function linked into the project if there are no included libraries and no source code definitions to this function? Also, I noticed in the tci file there is a device definition for the McBsp and a DIO object. Do I have to define my McBsp driver this way? Is this something new for PSP?

  • 0
    TI__Intellectual 1520 points

    Hi,

    Herb said:
    what I quickly noticed is that all the EDMA configuration is encapsulated in a function called “edma3init” that is not in the project

    the EDMA Low Level Driver is a separate package, which is linked with the PSP package where ever EDMA APIs is required. PSP driver use the EDMA peripheral via EDMA LLD only. EDMA package can be downloaded from here:

    http://software-dl.ti.com/dsps/dsps_public_sw/psp/edma3_lld/

    Herb said:
    How is this function linked into the project if there are no included libraries

    Please refer to the .pjt files in the build folder (CCS project files). There is a reference for EDMA3 linking in the linker section. Further information about dependencies are mentioned in the Release notes and user guide.

    Herb said:
    I noticed in the tci file there is a device definition for the McBsp and a DIO object. Do I have to define my McBsp driver this way? Is this something new for PSP?

    If the stream model is used (SIO layer), then DIO device creation is mandated by DSP/BIOS driver framework. This can be referred to from the DSP/BIOS driver developer's guide and the DSP/BIOS API reference guide.

  • 0 in reply to Sriram9339
    TI__Prodigy 675 points

    Sriram,

    My customer is now asking:

    "At some point we installed PSP 01.30.01 for the 6748, but today I only see the install for version 01.30.00.05 and older on the update advisor. Can you send the link for PSP 01.30.01?  I also cannot seem to find the matching 01.11 version of the EMDA3 LLD."

    How can I obatin these files for them?

    H

  • 0 in reply to Herb
    TI__Intellectual 1520 points

    Hi,

    Please find all the links from here:-

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/index.html

  • 0 in reply to Sriram9339
    Prodigy 35 points

    Where is the EDMA congifuration (for example, buffer lengths, linking, number of buffers, memory location, etc) for the McBspSampleMaster Project defined? Does the EDMA configuration somehow infer the necessary parameters from the McBsp setup? Is it using some default parameters defined in the LLD?

    Posing the question in a different way: if I were to use this example to design my own McBsp application, where would I adjust the size, linking, location and count of the EDMA3 buffers for my project?

  • 0 in reply to DR53000
    TI__Intellectual 1245 points

    You might look at the material and lab from our Multi-day training workshop give more insight on how the set-up a DMA-McBSP transfer.  The material for the workshop and labs can be found at: http://processors.wiki.ti.com/index.php/TMS320C64x%2B_DSP_System_Integration_Workshop_using_DSP/BIOS

    In general you need to set-up both the McBSP and the DMA with the proper set of register and " transfer" values. The EDMA driver does not set-up the McBSP for you. The DMA/McBSP parameters may not be exactly the same either, but they need to be matched so the McBSP can accept the data coming from the EDMA. You also need to set-up the right sync/transfer events. Once initialized and set-up typically your application will only service the DMA buffers/interrupts. 

    13. EDMA3 and Low Level Driver (LLD) Programming

    • Provide an overview of the EDMA and its capablitis
    • Compare/contrast EDMA, DMA, QDMA, IDMA and peripheral DMAs
    • Demonstrate how the Low Level Driver (LD) can be used to program DMA transfers
    • Describe all the possible "events", "transfers", and "actions" within the EDMA
    • Define and then demonstrate capabilities such as linking, chaining, channel sorting, interrupt gen