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 Newsgroups: comp.lang.ada Subject: Re: Arduino Due vs Mac Date: Mon, 06 Jul 2015 22:29:17 +0100 Organization: A noiseless patient Spider Message-ID: References: <587f5ad7-4507-45d0-8e33-ae39d11b2027@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="c762050aff3a30866fa7e79999b14776"; logging-data="29838"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+vNtrz1GTddbSn8ZTYYVFyvi29GNlIzEY=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Cancel-Lock: sha1:gyZqPrMSqYCHACk9zfIgrznqvb4= sha1:WXO55jJKrDLxebGmyqMfnSgY/QU= Xref: news.eternal-september.org comp.lang.ada:26666 Date: 2015-07-06T22:29:17+01:00 List-Id: Maciej Sobczak writes: >> I'm trying to get my ARTS running on a Due, but have come across a huge >> stumbling block in that I can't use the Bossa tool (or its command-line >> equivalents) to upload the built binary to the target board from the >> Mac. > > Get the Arduino IDE and use the bossac tool that is part of it. I don't see that? (that is, I downloaded the Arduino IDE and there's no file called bossa* there at all). What I did do is look again at https://github.com/shumatech/BOSSA.git and **check out the 'arduino' branch** (and compile with clang, not GCC!) > You should be able to upload any binary to the Arduino Due like this: > > $ bossac -e -w -v -U true -p tty.usbmodemfd131 -b program.bin > > Note: the USB device is a bit unpredictable, it might be > tty.usbmodemfd141 or something - I had to check the availability of > this special file name under /dev before every upload and use the > actual name that was there. If I leave out -U and -p this works (after a long pause while it scans through /dev/cu.Bluetooth- devices before finding /dev/cu.usbmodem1411 (this seems stable for the Due programming port on the USB port nearer the front of the Macbook)). Now I have to find out why I'm getting 'Floating point exception: 8", but this is a huge improvement!