• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 102 subscribers
  • Views 864 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

opening files from computer on evaluation board c6416

MN
Intellectual 600 points

I'm trying to open a binary file on computer while running  dsk_app on my c6416 evaluation board.  But it seems everything gets corrupted since the program goes to the hardware interrupt routine at the very beginning of DSK6416_init() when I have only declared the File pointer.  I had been successful with file opening when I did not have EDMA in my program.  Am I not allowed to use both?

  • 0
    TI__Mastermind 43955 points
    Hi Maryam,

    In which memory, does the file reside ? You may check for any PINMUX conflict with EDMA.

    Would you please brief more about the file access, file format and the type of filesystem you use it on the memory in which the file lies etc...
  • 0 in reply to Shankari G
    Intellectual 600 points

    The file is on the computer and it's binary.  The evaluation board is connected to the computer via the USB cable.  I used to do that with regular "fopen" and "fread".  I can't tell if it's a stack overflow problem or it's a conflict of File and EDMA.

    Thanks.

  • 0 in reply to MN
    TI__Guru* 84110 points
    Maryam,

    There is no specific reason why file access and EDMA would interfere with each other. The file access functions may disable interrupts for a long period of time which could introduce problems if the EDMA or any other system feature needed to respond to an external event while interrupts are disabled. Or it could be stack overflow as you have already suggested.

    Have you found the problem since your last post or are you still working on this?

    Regards,
    RandyP
  • 0 in reply to RandyP
    Intellectual 600 points

    Randy,

    Thanks very much for your reply.  It turned out that my problem was just a  debugging issue.  When stepping through the main code it would jump to the breakpoint inside the interrupt routine.  I was thinking that the interrupt is getting activated so soon before initializations.  But when I put breakpoints inside main I figured that it actually does pass through everything!

    Thanks again,

    Maryam