From owner-freebsd-arm@freebsd.org Sun Dec 18 09:42:54 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35171C8576B for ; Sun, 18 Dec 2016 09:42:54 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D45041E78 for ; Sun, 18 Dec 2016 09:42:53 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id uBI9ghTX094768 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 18 Dec 2016 10:42:43 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id uBI9gdGj023150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Dec 2016 10:42:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id uBI9gdCw031765; Sun, 18 Dec 2016 10:42:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id uBI9gc2n031764; Sun, 18 Dec 2016 10:42:38 +0100 (CET) (envelope-from ticso) Date: Sun, 18 Dec 2016 10:42:38 +0100 From: Bernd Walter To: Kyle Evans Cc: Adrian Chadd , "freebsd-arm@freebsd.org" Subject: Re: Arduino Due Message-ID: <20161218094238.GD30676@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20161211034602.3fylwnxfbgl4ehgx@hal9000.meka.no-ip.org> <1752cc8d-fad7-141d-4950-37bb5dde9561@passap.ru> <20161215111151.geyecaxakyn6feau@hal9000.meka.no-ip.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 10.2-RELEASE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-1.507 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2016 09:42:54 -0000 On Sun, Dec 18, 2016 at 01:41:52AM -0600, Kyle Evans wrote: > On Sun, Dec 18, 2016 at 1:14 AM, Adrian Chadd wrote: > > hiya, > > > > can people upload example working / not working code and generated > > binaries? Surely this is something a bit of disassembly should quickly > > show. (eg, some mismatch ABI between runtimes and generated code,.) > > > > > > -a > > > > > > Hi, > > I'm attaching some files that Goran has sent me off list, which I'm > still working up some time to sit down with and examine. Included are > compiled binaries and their associated build logs. I don't think he > explicitly stated and I haven't been able to check, but I assume these > are from the Blink example packaged with the IDE. > > His other problem, not being able to program the Due from the IDE, is > one that I've experienced intermittently and have yet to pin down the > exact cause for. In my experiences, it was that the IDE seemingly > wouldn't perform the 1200 bps open/close after the first time I'd > programmed it. Closing and re-opening the IDE or reconnecting the Due > was fine. It does occur to me that I didn't think to ask if he was > using the native port or the programming port -- I don't think I've > ever had any luck with programming via the native port. I'm pretty amazed that people even got so far. The arduino IDE (which I really hate to be honest) and avr-gcc is in the ports. But how do you install the arm toolchain matching with the arduino expectations? > I would have liked it if this detail was completely moved into > devel/bossa, which is actually programming the device, but that idea > has since been rejected upstream. I'm not entirely convinced that it's > really doing the open/close properly or that there's not simply too > much delay between triggering the bootloader and devel/bossa connecting. Not sure about the arduino case, but with the ESP8266 I saw some USB uarts worked fine (CP2102) and others (CH340) failed to start programming. Adding some retries for the init handshake helped. No idea what happens exactly, because the data itself looked fine when I'd traced it with another USB uart. There might be some timing differences. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.