From: William Thomas <williamjthomas7777@gmail.com>
Subject: Re: Trouble with Timers on the ARM
Date: Sat, 16 Aug 2014 21:43:53 -0700 (PDT)
Date: 2014-08-16T21:43:53-07:00 [thread overview]
Message-ID: <9e4585b7-2d01-4877-a24c-3fd23625fbff@googlegroups.com> (raw)
In-Reply-To: <e4f4ecf9-5d3d-4fb7-81ff-56333051c1f5@googlegroups.com>
On Wednesday, August 13, 2014 12:53:17 PM UTC-4, Mike Silva wrote:
> I've connected an STM32F4 board to an LCD display, and modified the last chance handler to print out the offending file and line number. Your code fails in
>
>
>
> s-taprob.adb line 95
>
>
>
> which is here:
>
> if Caller_Priority > Object.Ceiling then
>
> raise Program_Error;
>
> end if;
>
>
>
> Sorry, don't have the time now to dig deeper.
>
>
>
> Mike
Thanks Mike,
I got the last chance handler to print out the Null terminated string returned at address along with the line number. Sure enough I received the same message coming from System.Tasking.Protected_Objects.
It turns out that I had to set the protected object's priority to System.Max_Interrupt_Priority in order for the timer to work properly.
I would imagine its because the Callback is being called back by something that was being executed as a result of some processor timer which I believe would have to be coming in at Max_Interrupt_Priority.
Thanks for the help.
Bill
next prev parent reply other threads:[~2014-08-17 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 6:24 Trouble with Timers on the ARM williamjthomas7777
2014-08-13 16:53 ` Mike Silva
2014-08-17 4:43 ` William Thomas [this message]
2014-08-17 19:51 ` Mike Silva
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox