Pure64 and interrupts

[42Bastian]

Hi Ian,

just got trapped because pure64 enables the RTC interrupt.

Is this needed for anything useful ?

IMHO, a bootloader should not leave activated any interrupts when starting
the loaded software.

--
42Bastian

[Ian Seyler]

I don't understand what you mean. Pure64 leaves all interrupts disabled once it is finished. BareMetal OS reactivates them when it starts up.

The RTC interrupt increments a clock counter, displaying the system status bar (enabled by default), and also restarting the CLI once a program has finished running. So it is useful but can be disabled.

-Ian

[42Bastian]

Hi

> I don't understand what you mean. Pure64 leaves all interrupts disabled
> once it is finished.

Not quit. You make a "cli", but the rtc still fires. As soon as the loaded
SW enables interrupts, the RTC interrupt fires and (in the case of my
RTOS) an unhandled interrupt occurs because no user handler has been
installed.

> The RTC interrupt increments a clock counter, displaying the system status
> bar (enabled by default), and also restarting the CLI once a program has
> finished running. So it is useful but can be disabled.

Thats for BM. I disabled the RTC code in pure64, and now I have no
problems with the interrupt.

To bad, my attempt to disable the RTC again, did not work, maybe because
it is still pending.

--
42Bastian

[Ian Seyler]

Ah, I see what you mean now. I will adjust Pure64 to disable the RTC periodic interrupt before I disable interrupts globally. Would that be ok?

-Ian

[Ian Seyler]

The fix is in the Pure64 SVN:  http://code.google.com/p/pure64/source/detail?r=101

I hope this helps.

-Ian

[42Bastian]

Thanks Ian

> The fix is in the Pure64 SVN:
> http://code.google.com/p/pure64/source/detail?r=101

I will give it a try.
--
42Bastian