From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.182.91.43 with SMTP id cb11mr15126705obb.13.1408250633640; Sat, 16 Aug 2014 21:43:53 -0700 (PDT) X-Received: by 10.140.91.105 with SMTP id y96mr1626qgd.16.1408250633611; Sat, 16 Aug 2014 21:43:53 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!uq10no844268igb.0!news-out.google.com!e6ni1422qar.1!nntp.google.com!i13no499758qae.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 16 Aug 2014 21:43:53 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.54.29.134; posting-account=YMGx1QoAAABkILZRyRBIC1qEtDwG1Rz1 NNTP-Posting-Host: 69.54.29.134 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <9e4585b7-2d01-4877-a24c-3fd23625fbff@googlegroups.com> Subject: Re: Trouble with Timers on the ARM From: William Thomas Injection-Date: Sun, 17 Aug 2014 04:43:53 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:21792 Date: 2014-08-16T21:43:53-07:00 List-Id: 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