RISC-V interrupts in HiFive1

[Denis Obrezkov]

2017-08-15 20:38 GMT+02:00 Denis Obrezkov <denisobrezkov at gmail.com>:

> 2017-08-15 19:03 GMT+02:00 Denis Obrezkov <denisobrezkov at gmail.com>:
>
>> 2017-08-15 14:57 GMT+02:00 Joel Sherrill <joel at rtems.org>:
>>
>>>
>>>
>>> On Aug 15, 2017 4:32 AM, "Denis Obrezkov" <denisobrezkov at gmail.com>
>>> wrote:
>>>
>>> 2017-08-15 5:44 GMT+02:00 Hesham Almatary <heshamelmatary at gmail.com>:
>>>
>>>> Hi Denis,
>>>>
>>>> You just need to modify riscv_interrupt_disable(). Read the priv-spec
>>>> manual for your RISC-V version, and determine which bit should be
>>>> cleared (it's called MIE in priv-1.10, but you mentioned you work with
>>>> priv-1.9).
>>>>
>>>
>>> Is the bit set correctly for the idle thread?
>>>
>>> I assume this is with a real clock driver so is it maintained properly
>>> across an ISR?
>>>
>>> It is either screwed up by the thread context initialization, context
>>> switch, or ISR code. ISR code has two exit paths. It could be the
>>> preemption path. That would occur about 5 seconds into the execution of
>>> ticker and TA1 will preemption idle.
>>>
>>>
>>>>
>>> I understand this but still can find a mistake.
>> This is what I get:
>>
>>
>> *** LOW MEMORY CLOCK TICK TEST ***
>>
>> TA1 - rtems_clock_get_tod - 09:00:00 12/31/1988
>>
>> TA2 - rtems_clock_get_tod - 09:00:00 12/31/1988
>>
>> TA3 - rtems_clock_get_tod - 09:00:00 12/31/1988
>>
>> TA1 - rtems_clock_get_tod - 09:00:04 12/31/1988
>>
>> TA2 - rtems_clock_get_tod - 09:00:09 12/31/1988
>>
>> TA1 - rtems_clock_get_tod - 09:00:09 12/31/1988
>>
>>
>> After that I can examine: p Clock_driver_ticks
>>
>> $8 = 1001
>>
>> mstatus value is 0x0001800 (interrupts disabled)
>>
>> Instruction for enabling global interrupts is:
>> csrsi mstatus, 0x8
>> for disabling:
>> csrci mstatus, 0x8
>> it atomically changes the fourth bit of mstatus (ie bit).
>>
>> I think that something wrong happens in context switches between TA1, TA2
>> and Idle.
>>
>> This is my context switch file:
>> https://github.com/embeddedden/rtems-riscv/blob/hifive1/
>> cpukit/score/cpu/riscv32/riscv-context-switch.S
>> Interrupt disabling:
>> https://github.com/embeddedden/rtems-riscv/blob/hifive1/
>> cpukit/score/cpu/riscv32/rtems/score/cpu.h#L542
>> Context initialize:
>> https://github.com/embeddedden/rtems-riscv/blob/hifive1/
>> cpukit/score/cpu/riscv32/riscv-context-initialize.c
>> Interrupt context save:
>> https://github.com/embeddedden/rtems-riscv/blob/hifive1/c/
>> src/lib/libbsp/riscv32/hifive1/start/start.S#L200
>>
>> Could have a look?
>>
>>
>>
>>
>> --
>> Regards, Denis Obrezkov
>>
> can't find the mistake*
>
>
> --
> Regards, Denis Obrezkov
>
Also, I found out new strange issue, when I set:
#define FE310_CLOCK_PERIOD 313
#define CONFIGURE_MICROSECONDS_PER_TICK 9552
clock ticks till the 09:00:09 and stops ticking, but with
#define FE310_CLOCK_PERIOD 626
#define CONFIGURE_MICROSECONDS_PER_TICK 9552*2
clock ticks till the end (35 s.) but the duration of a virtual second is
more than a second (appr. 2 s.).

I use onboard 32.768 oscillator as a source of ticks (it is the only
available source).
Also, when I have
#define FE310_CLOCK_PERIOD 512
#define CONFIGURE_MICROSECONDS_PER_TICK 15625
virtual 5 seconds last for about 7-8 real seconds.

Are there any suggestions on this?


-- 
Regards, Denis Obrezkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170815/cd054d1f/attachment.html>