Date: Thu, 4 Jan 2018 13:04:26 -0600 From: Kyle Evans <kevans91@ksu.edu> To: Zaphod Beeblebrox <zbeeble@gmail.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: We do serial differently. Message-ID: <CACNAnaFuWp0VF69=n-JCLOTEjZSRUPJx9VLNpeGYHfSG2NRQsg@mail.gmail.com> In-Reply-To: <CACpH0MdAeUQ187hQiO=grQ%2BXaLOrCRZFQ=jbtQMYq=O3DgCD9w@mail.gmail.com> References: <CACpH0Md0ckYH6k5ufAwCoc-_ThtJHrV9%2BdUtp66%2BSSjVuyhpxA@mail.gmail.com> <CACNAnaEu0-mdO9HTgOX8BRF5_FMVsszQzan6RYKEsLzoMgDXjQ@mail.gmail.com> <CACpH0MdpucayKsWzPN86w9tJkydQhhz5eL8GLHfADE1C12kr3A@mail.gmail.com> <CACNAnaGf7yAP6Sc6coNhZVcZyw0OA1ZUvaOu=t3D-tfn4sXwcQ@mail.gmail.com> <CACNAnaFAbKWFJ9NiR=gS8y_9-RDHzNFACZku8mpaphGZHU2Org@mail.gmail.com> <CACpH0Mcacy_REUPUSbfJ=6UnrBuPU09zgVEG6ZnCW4tSmG9Ohg@mail.gmail.com> <CACNAnaFB5yo0bSdKMCSFhkh8GNvS2t4fQA8ujRDxqPQH2GKLWg@mail.gmail.com> <c0ea7c01-271d-3a97-fdb0-8203fe0c3e6f@gmail.com> <CACpH0MdAeUQ187hQiO=grQ%2BXaLOrCRZFQ=jbtQMYq=O3DgCD9w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 2, 2018 at 5:05 PM, Zaphod Beeblebrox <zbeeble@gmail.com> wrote: > To summarize, the app "arduino" that controls arduinos works, but the app > "pronterface" that controls an arduino with a specific application loaded, > do not. Further this seems to be something to do with the handling of the > DTR and/or the actual handling of the DTR signal... and what this all means > to the arduino in question. To confound things, this all works (of course) > on linux. > > If this were a purely work thing, I'd eat my bile and just run linux. Even > now, I have a R-pi attached to it running linux to "get things done" ... but > I want FreeBSD to work. > > So... if I'm charged to fix this, what are my tools? Is ktrace sufficient > to indicate all the calls to the serial? How do I interpret it so that I > can make sense of this. Do I potentially need DTrace or is that overkill? Unfortunately, I'm not much help on the tool side- all of my problems thus far have been diagnosed just by observing behavior. I think this previous statement of yours says much: >> Firstly, when I run "arduino" (the IDE) ... the arduino board resets immediately (I can tell this because it has an LCD screen attached). >> But when I run pronterface, it doesn't reset until 5 seconds (roughly) after pronterface exits. IIRC: If the port gets opened, there will be a reset, full-stop. If there is no reset, the odds that the port actually got successfully opened are slim to none. This should be easily verified with truss or ktrace- you should try and perhaps post the results back here.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaFuWp0VF69=n-JCLOTEjZSRUPJx9VLNpeGYHfSG2NRQsg>