Actions
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 329 subscribers
  • Views 447 views
  • Users 0 members are here
Related

UART-0 hangs when UART-1 receive data in AMP

fayyazrafiq

Hi All,

I am using ZEDBoard with AMP application. I configured UART0 receive interrupt for CPU0 and UART1 receive interrupt for CPU1. The program works fine, if I do not have any character receive from UART-1. As soon as, i send some character from the terminal program for UART1, UART0 also stop sending data out. I do not know what is problem, It seems something is shared between the CPU0 and CPU1. Although, it should not be the case because i am using separate UART for each CPU. Any help is highly appreciated.

Regards
Fayyaz

Parents
  • 0

    You didn't supply enough information to fully frame your question.  I see now this is a different problem, so it needs a different solution.  As you state in your question, this could be a problem with the interrupt reaching the processor, but there are also a number of other possibilities.  The first step is to try to narrow down the problem.  I would suggest setting a breakpoint inside the interrupt handler running on the core where you lose UART traffic - you'll have to be a little clever with when you activate it to avoid having it trip before you want it to.  If it does get hit, the interrupt is not the problem.  If it doesn't, then is the interrupt being generated by the UART correctly?  You should be able to check that with ILA/Chipscope.  If it is generated, and the handler doesn't see it, then it must be masked out, so you'll need to look at the low level interrupt function to see what can be done to make sure you don't miss an interrupt while the first handler instance is servicing.  If you are using your own interrupt mechanism, make sure you aren't spending too long inside the handler.

Reply
  • 0

    You didn't supply enough information to fully frame your question.  I see now this is a different problem, so it needs a different solution.  As you state in your question, this could be a problem with the interrupt reaching the processor, but there are also a number of other possibilities.  The first step is to try to narrow down the problem.  I would suggest setting a breakpoint inside the interrupt handler running on the core where you lose UART traffic - you'll have to be a little clever with when you activate it to avoid having it trip before you want it to.  If it does get hit, the interrupt is not the problem.  If it doesn't, then is the interrupt being generated by the UART correctly?  You should be able to check that with ILA/Chipscope.  If it is generated, and the handler doesn't see it, then it must be masked out, so you'll need to look at the low level interrupt function to see what can be done to make sure you don't miss an interrupt while the first handler instance is servicing.  If you are using your own interrupt mechanism, make sure you aren't spending too long inside the handler.

Children