Re: LIBBSD

2017-07-02 Thread Sebastian Huber
On 30/06/17 20:08, Kirspel, Kevin wrote: Case #2: Enable the RTEMS callout timer but do not call "callout_process()" (the timer service routine just resets the timer and quits) . IDLE Task CPUUSE: 93.144% TIME Task CPUUSE: 6.282% In this case you have some low-level problem on your target. Is

Re: LIBBSD

2017-07-02 Thread Sebastian Huber
On 03/07/17 02:03, Kirspel, Kevin wrote: I have rewritten the kern_timeout.c module to use individual RTEMS timers per callout/timeout function. My Idle task CPUUSE is now 99.9%. I still need to validate all the functionality of the kern_timeout.c module with a timeout01 test in the testsuit

Re: RISC-V interrupt vectoring

2017-07-02 Thread Hesham Almatary
On Mon, Jul 3, 2017 at 3:36 PM, Denis Obrezkov wrote: > 2017-07-03 4:59 GMT+02:00 Hesham Almatary : >> >> You can have a look at riscv-pk [1] as a RISC-V reference how to >> handle interrupts. RTEMS-wise, you can look at or1k and ARM code and >> how the platform-dependent interrupt handling code i

Re: RISC-V interrupt vectoring

2017-07-02 Thread Denis Obrezkov
2017-07-03 4:59 GMT+02:00 Hesham Almatary : > You can have a look at riscv-pk [1] as a RISC-V reference how to > handle interrupts. RTEMS-wise, you can look at or1k and ARM code and > how the platform-dependent interrupt handling code is linked to > platform-independent one. > > mcause value can b

Re: RISC-V interrupt vectoring

2017-07-02 Thread Hesham Almatary
You can have a look at riscv-pk [1] as a RISC-V reference how to handle interrupts. RTEMS-wise, you can look at or1k and ARM code and how the platform-dependent interrupt handling code is linked to platform-independent one. mcause value can be used as an index to a software vector table that you s

RE: LIBBSD

2017-07-02 Thread Kirspel, Kevin
I have rewritten the kern_timeout.c module to use individual RTEMS timers per callout/timeout function. My Idle task CPUUSE is now 99.9%. I still need to validate all the functionality of the kern_timeout.c module with a timeout01 test in the testsuite. I don't think the existing kern_timeout.

RISC-V interrupt vectoring

2017-07-02 Thread Denis Obrezkov
Hello all, I am trying to enable vectored interrupts on my HiFive1 board. I was able to install interrupt vector base address, but it didn't work. And I wasn't able to generate a software interrupt. Though, it seems that interrupts works - at some moment of execution, I catch the exception 'Illegal