We do serial differently.

[Kyle Evans]

On Tue, Jan 2, 2018 at 5:05 PM, Zaphod Beeblebrox <zbeeble at 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.