• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 2229 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

Call SWI functions from a FIQ Handler using RTX

Robson Bandeira Sales

Hello to all!

Is possible to make a call to a SWI routine from a FIQ Handler when you are using the RTX Kernel?

I try this approach but a UNDEFINED exception occurs on exit of SWI function. See the code below:

void FIQCapture (void) __irq
{
  static U32 ticksCounter = 0;

  ticksCounter++;
  if (ticksCounter > ((U32) 5))
  {
    // Call freqMsrSignal in Fast Interrupt Mode
    freqMsrSignal(0x0001, &taskMeasureLoop);
    ticksCounter = 0;
  }
  // Match 0 asserted. Clear.
  T0IR    = 1 << 0;
}

void __swi(8) freqMsrSignal(U16 event_flags, OS_TID *task);
void __SWI_8               (U16 event_flags, OS_TID *task)
{
  // Increment the SWI_Times in Supervisor Mode
  SWI_Times++;
  // Call a RTX function in Supervisor Mode
  os_evt_set(event_flags, *task);
  /// The context switch was: User->FIQ->Supervisor
  return;
}

With this manner, I can call OS Functions from a FIQ Handler, my goal.

However, after run freqMsrSignal the system are switch to Undefined context

Undef_Handler   B       Undef_Handler

The code run the branch above (in a endless loop).

I use the uVision 3.50. Any suggestions?

Parents
  • 0 in reply to Viktor Bucher

    Thanks a lot for replying.

    I can't make the calls as regular functions. In the FIQ context, we can't make any OS calls (it's RL-ARM specific implementation).

    I need to use the FIQ for priority reasons (the Vectored IRQ may be disable by RTOS in an unpredictable time).

    In the FIQ I will make only very basic services. However they are deterministic services and need to be process with a very low jitter. Another task will be responsable to process the noncritical data. Is like a bottom/top half approach.

    An easy way to make this is set a flag in FIQ context. Another task, in user context, can check the content of this flag by pooling. If is possible, I would like to use a more "polite" way: call OS functions from a FIQ Handler to wakeup a task (using a real IPC communication).

    I try run this code in a MCB2300 board (with LPC2378).

    Any suggestions?

Reply
  • 0 in reply to Viktor Bucher

    Thanks a lot for replying.

    I can't make the calls as regular functions. In the FIQ context, we can't make any OS calls (it's RL-ARM specific implementation).

    I need to use the FIQ for priority reasons (the Vectored IRQ may be disable by RTOS in an unpredictable time).

    In the FIQ I will make only very basic services. However they are deterministic services and need to be process with a very low jitter. Another task will be responsable to process the noncritical data. Is like a bottom/top half approach.

    An easy way to make this is set a flag in FIQ context. Another task, in user context, can check the content of this flag by pooling. If is possible, I would like to use a more "polite" way: call OS functions from a FIQ Handler to wakeup a task (using a real IPC communication).

    I try run this code in a MCB2300 board (with LPC2378).

    Any suggestions?

Children