• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 427 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.

EDMA Example Doesn't Work

Brett
Prodigy 40 points

I've been trying to get the C6748_StarterWare_1_20_03_03 EDMA example to work on my C6748 LCDK.  I've tried compiling it myself and using the pre-built binaries.  When I run the program, all I get is via the serial port is: "Welcome to EDMA/QDMA example application."  When I build it myself and run in the debugger, it appears that the first frame of 512 bytes is transfered, but the ISR is never called.  Could this be a problem with my GEL file not configuring something correctly?  I've attached the GEL I'm using.  It came from one of the many TI libraries I've installed recently.

6082.C6748_LCDK.gel

Thanks,
Brett

  • 0
    Prodigy 40 points

    The behavior seems to change depending on how I setup my linker command file.  If I put everything into internal RAM, I get one frame of 512 bytes copied, and no interrupts.  If I put everything into DDR, the destination doesn't appear to be written at all, and I still don't get an interrupt.

    As an experiement, I weaved some of the timer exmaple code into this code, just to verify that interrupts are working and that the vector table is in the correct location.  The timer interrupts are working, and the proper ISR is being called.

  • 0 in reply to Brett
    TI__Prodigy 480 points

    Brett,

    I would like you to try the following:

    Use the gel file "C6748.gel" from the directory "C6748_StarterWare_1_20_03_03\tools\gel"

    Run the prebuilt binary "C6748_StarterWare_1_20_03_03\binary\c674x\cgt\c6748\lcdkC6748\edma\Release\edmaTest.out"

    If prebuilt binary works fine then try to build and run the EDMA example application for LCDK C6748

    Please let me know if it works for you.

    Regards,

    Vinay

  • 0 in reply to Vinay Kumar42
    Prodigy 40 points

    Hi Vinay,

    Thanks for the reply.

    I've tried the pre-built binary that you've suggested, and the only text that comes out of the serial port is "Welcome to the EDAM/QDMA example application."  I believe that more text should be present if the test succeeds.

    When I tried the GEL file you suggest, something goes wrong when I try to connect to the target.  It looks like the call to OnTargetConnect() never completes, and I get the following output:

    C674X_0: Output: Memory Map Cleared.
    C674X_0: Output: ---------------------------------------------
    C674X_0: Output: Memory Map Setup Complete.
    C674X_0: Output: ---------------------------------------------
    C674X_0: Output: Enabling Experimenter PSCs...
    C674X_0: Output: PSC Enable Complete.
    C674X_0: Output: ---------------------------------------------
    C674X_0: Output: PLL0 init done for Core:300MHz, EMIF:25MHz
    C674X_0: Output: mDDR initialization is in progress....
    C674X_0: Output: PLL1 init done for DDR:132MHz
     

    I've also tried the C6748_LCDK.gel file present in that same directory. With that gel file I can connect to the target, but the application still doens't work. As in the other cases, it only prints "Welcom to EDMA/QDMA example application."

    Take care,
    Brett

  • 0 in reply to Brett
    Prodigy 40 points

    I can't explain it, but suddenly the pre-built binary, and my binary are both working.  The trick was doing a system reset:

    Run -> Reset -> System Reset

    I can't explain why that made it suddenly work.  I can't make it fail again either. 

    Any thoughts on why the system reset made it work, and why I can't recreate the failure anymore?

  • 0 in reply to Brett
    TI__Prodigy 375 points

    Hi,

    Basically when you do System reset, it does the following-

    1. All registers are reset to power up reset values means device reset


    2. It clears error interrupts for software debug


    3. This ensures that the device and its related peripherals are reset together apart from debug logic

        and it retains breakpoint and watch points.

    Hope this may help you.