Could someone expand it a bit.
For example, I can provide an interrupt table in my start.S file.
So, when interrupts occurs, pc counter is set to the appropriate address in
table entry.
And we have several RTEMS interrupt handlers. And RTEMS handlers table.
How do they relate to each other?
2017-
https://docs.rtems.org/branches/master/cpu-supplement/port.html#interrupt-processing
https://docs.rtems.org/branches/master/bsp-howto.html#set-vector-install-an-interrupt-vector
On Fri, Jun 30, 2017 at 10:49 AM, Denis Obrezkov
wrote:
> Hello all,
> what is the common practice of interrupt imple
Just some quick numbers. LPC3250 running at 208 MHz, 64MB RAM, 512MB FLASH.
Case #1: Disable the RTEMS callout timer in LIBBSD (kern_timeout.c)
IDLE Task CPUUSE: 99.430%
TIME Task CPUUSE: <0.001%
Case #2: Enable the RTEMS callout timer but do not call "callout_process()"
(the timer service rout
Hello all,
what is the common practice of interrupt implementation in RTEMS?
I wasn't able to find much information in RTEMS BSP manual.
My platform RISC-V has vectored interrupts and exceptions.
A cause of an exception or of an interrupt is always available in 'mcause'
register.
But for interrupt
Close #3056.
---
c-user/configuring_a_system.rst | 27 +++
c-user/scheduling_concepts.rst | 7 +++
2 files changed, 34 insertions(+)
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst
index 71c5c71..17c8a85 100644
--- a/c-user/configuring_
I'm not sure but I'll look into it today. I'll need to quantify each callout
handler's processing time to see which one is causing the problem. I know the
USB and Ethernet stacks/drivers use callouts but maybe there is something else.
Kevin Kirspel
Electrical Engineer - Sr. Staff
Idexx Roswell
