Date: Thu, 19 Oct 2017 11:03:46 +0100 From: Bob Bishop <rb@gid.co.uk> To: Zaphod Beeblebrox <zbeeble@gmail.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: We do serial differently. Message-ID: <E94C8886-3282-432F-A46E-ED0DA83F7B18@gid.co.uk> In-Reply-To: <CACpH0Md0ckYH6k5ufAwCoc-_ThtJHrV9%2BdUtp66%2BSSjVuyhpxA@mail.gmail.com> References: <CACpH0Md0ckYH6k5ufAwCoc-_ThtJHrV9%2BdUtp66%2BSSjVuyhpxA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > On 19 Oct 2017, at 05:25, Zaphod Beeblebrox <zbeeble@gmail.com> wrote: >=20 > How does FreeBSD do serial differently than Linux or MacOS or Windows? Quite likely only in the defaults when a port is opened. > Now... this isn't _exactly_ serial, but the serial that is emulated by = the > arduino driver in ports. >=20 > The issue is that running the arduino IDE works (and it boots with the > loaded code), but then running 'pronterface' fails to connect --- = looking > all-the-while like one-way communication. >=20 > I see someone else basically having the same problem and claiming that > hacking a trace (that affects the DTR response) on the arduino fixes = it for > FreeBSD (see https://plus.google.com/+MiroslavPrymek/posts/6TDdbuoNhzH = )... >=20 > Given this information, can I stty my way out of this problem? Can I = make > a small modification to pronterface? stty -clocal ... might help. All implementations of virtualised serial ports should (IMHO) provide a = software =E2=80=98breakout box=E2=80=99 which is the only sure way of = diagnosing this sort of problem. -- Bob Bishop rb@gid.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E94C8886-3282-432F-A46E-ED0DA83F7B18>