• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 21 subscribers
  • Views 1087 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RTX and EINT3

Christian E

Dear all,

I use Keil RTX and want to use the EINT3. I initialized the IRQ as followed:

  PINSEL1 |= (1<<9);
  PINSEL1 |= (1<<8);
  EXTMODE  |= (1<<3);
  EXTPOLAR &= ~(1<<3);
  VICVectAddr14 = (unsigned)UartISR;
  VICVectCntl14 |= (1 <<17);
  VICIntEnable = ( 1 << 17 );

Now the problem is that the system jumps to the

os_def_interrupt

in the RTX_Config.c and not to my UartISR-Funktion. Is this the normal way to handle interrupts with RTX? As I seen the Traffic Sample they do not use the os_def_interrupt. Is there any chance to jump directly to my UartISR?

Big Thanks for the help,

Christian

Parents
  • 0 in reply to Christian E

    normally, you register the default vector to catch spurious interrupts that might originate from the interaction between your processor and VIC. this happens MOSTLY when working with interrupt driven serial port and RTC (I think). If your interrupt is not invokes at all then it is probably an initialization issue.

Reply
  • 0 in reply to Christian E

    normally, you register the default vector to catch spurious interrupts that might originate from the interaction between your processor and VIC. this happens MOSTLY when working with interrupt driven serial port and RTC (I think). If your interrupt is not invokes at all then it is probably an initialization issue.

Children