Tuesday, November 21st 2017, 7:20am UTC+1

You are not logged in.

  • Login
  • Register

Reply

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Message information
Message
Settings
Automatically converts internet addresses into links by adding [url] and [/url] around them.
Smiley code in your message such as :) is automatically displayed as image.
You can use BBCode to format your message, if this option is enabled.
Security measure

Please enter the letters that are shown in the picture below (without spaces, and upper or lower case can be used).

The last 2 posts

Friday, November 3rd 2017, 11:56am

by SEGGER - Til

Hi Markus,

Quoted

In the RL78 embOS manual it is described that zero-latency interrupts must not execute any embOS function.
Therefore it is not allowed to call the functions OS_EnterIntStack resp. OS_LeaveIntStack, is that correct?

Yes, that's correct.

Quoted

This means that all tasks must preserve some space on their stack for the zero-latency interrupts because the switching is not allowed.
Depending on the zero-latency ISR implementation this can afford large stacks for all tasks...

Unfortunately that's true. Do you really need the zero latency interrupt priority?
The amount of stack also depends on whether the zero latency interrupts are nested or not.
If you don't have nested interrupts you'll need less stack space.

Quoted

Is there any other possibility to switch the stack for zero-latency interrupts?

Yes, there might be a workaround for this. I will contact you directly by email for further details.

Best regards,
Til

Friday, November 3rd 2017, 11:29am

by markusBie

Interrupt-stack switching on RL78 for zero-latency interrupts

Hello!

In the RL78 embOS manual it is described that zero-latency interrupts must not execute any embOS function.
Therefore it is not allowed to call the functions OS_EnterIntStack resp. OS_LeaveIntStack, is that correct?

This means that all tasks must preserve some space on their stack for the zero-latency interrupts because the switching is not allowed.
Depending on the zero-latency ISR implementation this can afford large stacks for all tasks... ;(

Is there any other possibility to switch the stack for zero-latency interrupts?

Thanks in advance!
Markus