> On 04 Jun 2015, at 16:03, Peter Maydell <peter.mayd...@linaro.org> wrote: > > ... Splitting out Systick definitely makes sense.
as a first step, I would try to define a separate object (armv7m-systick) and copy/paste the access code. then refer it inside the existing NVIC, to avoid affecting existing functionality. it would be a real time saver if you could provide a hint on the best approach to map the SysTick memory range (E010-E0FF) over the existing NVIC, inside the current code. > On the MPU... I would use a similar approach, a separate object, at first mapped over the ED90-EDEF range inside the existing NVIC. I also need to understand how to configure the memory range, to access the MPU registers, but since similar implementations are already in, it shouldn't be that hard. > ... reimplement the > NVIC properly as an independent bit of code. if the current exception handling implementation is not accurate enough for my needs, I'll consider this. regards, Liviu
