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!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: STM32F4 GNAT Run Time System - roadmap
Date: Mon, 07 Dec 2015 16:31:27 +0000
Organization: A noiseless patient Spider
Message-ID: <ly1taygqzk.fsf@pushface.org>
References: <lyzj49qecx.fsf@pushface.org> <ml96i2$3qs$2@dont-email.me>
	<lya8pnh1dq.fsf@pushface.org>
	<c6ace540-c022-49d7-b7f6-94405db70b23@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org;
 posting-host="6f4ba2ce0f80cf6975f919f4f22c2ad9";
	logging-data="10034"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19yVf++oWcO/M7kH6vdLF3gdI3R/9s6WGQ="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin)
Cancel-Lock: sha1:NEPMIlJYoZ6ZtGTCWTFSTiUNvkY=
	sha1:0QwLZ/rDseUVPkHU0NsfP9rTxzU=
Xref: news.eternal-september.org comp.lang.ada:28683
Date: 2015-12-07T16:31:27+00:00
List-Id: <comp.lang.ada>

Jere <jere.groups@gmail.com> writes:

> I am fairly new to the ARM arena, so this may be a stupid question but
> what exactly does svd2Ada generate based off of the SVD files?  From
> the description and what I saw in the git repo it sounds like it makes
> something like a BSP?

The SVD corresponds to the chip reference manual, and gives
register/field descriptions for the manufacturer-specific devices (so
not for e.g.NVIC). So the atsam3x8e SVD outputs

atsam3x8e-adc.ads
atsam3x8e-can.ads
atsam3x8e-chipid.ads
atsam3x8e-dacc.ads
atsam3x8e-dmac.ads
atsam3x8e-ebi.ads
atsam3x8e-efc.ads
atsam3x8e-emac.ads
atsam3x8e-hsmci.ads
atsam3x8e-interrupts.ads
atsam3x8e-matrix.ads
atsam3x8e-pio.ads
atsam3x8e-pmc.ads
atsam3x8e-pwm.ads
atsam3x8e-spi.ads
atsam3x8e-ssc.ads
atsam3x8e-sysc.ads
atsam3x8e-tc.ads
atsam3x8e-trng.ads
atsam3x8e-twi.ads
atsam3x8e-uart.ads
atsam3x8e-uotghs.ads
atsam3x8e-usart.ads
atsam3x8e.ads

where atsam3x8e.ads defines types for bitfields and, for example,

   PIOA_Base: constant := 16#400E0E00#;

for device register base addresses; and the others define specific
register definitions for devices.

Not all the generated files compile without error;

   compilation of atsam3x8e-adc.ads failed
   compilation of atsam3x8e-chipid.ads failed
   compilation of atsam3x8e-uotghs.ads failed

and, for the first,

atsam3x8e-adc.ads:525:07: reserved word "in" cannot be used as identifier
atsam3x8e-adc.ads:526:07: reserved word "out" cannot be used as identifier
atsam3x8e-adc.ads:531:15: expecting expression or component association
atsam3x8e-adc.ads:532:07: declaration expected

(the first two are the actual problem). So, work to be done.