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 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Compiler doesn't respect 'Size for atomic object Date: Thu, 21 Dec 2017 22:02:05 +0000 Organization: A noiseless patient Spider Message-ID: References: <609cb46c-3565-483b-a2b0-2b5d2cfda80a@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="7cd9de1895be944a2f440543cc1b68b7"; logging-data="12297"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX196xw6G0/e66v6QW21Kip8zsDiRMScVspw=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (darwin) Cancel-Lock: sha1:ThXq9MkIhlPCyZrqYVNY/eYcRyo= sha1:wlFvo7RAJwkJTgr8+CTNQz2xRkM= Xref: reader02.eternal-september.org comp.lang.ada:49578 Date: 2017-12-21T22:02:05+00:00 List-Id: Robert Eachus writes: > I am certainly not an expert on the Cortex-M CPUs, but as I read the > documentation, the STIR is write-only, and the upper 24-bits of the > value written there are ignored. It turns out that declaring NVIC_STIR as Unsigned_32 and writing NVIC_STIR := 16#ffff_ff00# or Interfaces.Unsigned_32 (IRQ); doesn't generate an interrupt.