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 2002:a24:3f4c:: with SMTP id d73-v6mr1582007ita.30.1527709980677; Wed, 30 May 2018 12:53:00 -0700 (PDT) X-Received: by 2002:a9d:738f:: with SMTP id j15-v6mr173728otk.6.1527709980190; Wed, 30 May 2018 12:53:00 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!feeder3.usenet.farm!feed.usenet.farm!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!v8-v6no79802itc.0!news-out.google.com!f20-v6ni26itd.0!nntp.google.com!u74-v6no79647itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 30 May 2018 12:52:59 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=140.32.16.3; posting-account=QyztswoAAADMpLjqBKxiGq6giZCkeW04 NNTP-Posting-Host: 140.32.16.3 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <616db519-48be-4969-be11-24096ab9ee47@googlegroups.com> Subject: Re: How to configure GNAT GPL on x86-64 Linux for ARM ELF development From: JLotty Injection-Date: Wed, 30 May 2018 19:53:00 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:52790 Date: 2018-05-30T12:52:59-07:00 List-Id: On Friday, May 25, 2018 at 11:06:41 PM UTC-6, Adam Jensen wrote: > On Fri, 25 May 2018 10:50:07 +0000, Brian Drummond wrote: >=20 > > On Fri, 25 May 2018 04:45:16 +0000, Adam Jensen wrote: > >=20 > >> Is it common for developers to create their own run-time system for > >> embedded platforms? My inclination would be to look for hardware based > >> on 1) RTS availability/quality and 2) toolkit complexity/completeness > >> (completeness implies useful documentation). > >=20 > > Not common, no. But RTS availability (esp. SPARK RTS) has to start > > somewhere, and for the MSP430 I didn't really develop one, just adapt > > from AVR-Ada. > >=20 > > With remarkably little feedback on that project, I admit I've put > > remarkably little effort into pushing it further. But I want it for my > > own purposes, the watch is just a pretty by-product. >=20 > Super cool. Are your project's documents posted/hosted anywhere for=20 > others to view and use?=20 >=20 > >> Given that, which seems like an obvious thing to do, I am surprised > >> that Adacore does not have more apparent associations with hardware > >> vendors where dev-kits and SBC products are promoted. I bought the > >> Nucleo-144 board because I thought there was a BSP, RTS, and a > >> tool-chain configuration tutorial. That turned out to be a bit of a > >> mistake and generally a poor choice. > >=20 > > Not Adacore ... there isn't much hobbyist money for them, given their > > business model. They do publicise occasional hobby-level projects like > > Lego Mindstorms and Certyflie, but I don't see them making money off it= . >=20 > They have the "Make with Ada" competition:=20 > >=20 > And the Adacore University: > >=20 > If there is not a large vibrant community of people who understand and=20 > use the technology it will fade and collapse. It seems like maybe they=20 > recognize this but it doesn't seem like they know what to do. (Only an=20 > idiot would have advertisers involved in technical communication). C'est= =20 > la vie. > =20 > > Meanwhile we have to support each other, perhaps your work on Nucleo ca= n > > feed back into Simon's RTS and expand its supported platforms. >=20 > The Nucleo-144 board was selected as a gentle starter kit to develop some= =20 > confidence and familiarity with the tool-chain and the work-flow. It was= =20 > a total failure in this role. However, I have been keeping notes and at= =20 > some point I might create a tutorial for Ada/Spark development on Ubuntu= =20 > x86_64 targeting the ARM MCU on a Nucleo-144 board. After that, I will=20 > probably move to a platform with more resources. Eventually, I need a=20 > processor coupled with an FPGA - the FPGA is where most of the hard real- > time activity (traction with physics) should take place, IMO. You might also look into these codebases: https://github.com/lambourg/Ada_Bare_Metal_Demos https://travis-ci.org/AdaCore/Ada_Drivers_Library Both are supported by AdaCore and provide runtime systems for STM32F4 board= s, as well as Raspberry Pi. The STM33F4 is a fairly inexpensive board. I = would recommend beginning development on it to build confidence and learn t= he embedded Ada details, then begin porting to the Nucleo-144 board specifi= cations as described in=20 "Porting the Ada runtime to a new ARM board"=20 =20 Both of these repositories worked out of the box for me on GNAT 2017. James