MIME-Version: 1.0
Date: Thu, 7 Apr 2016 11:09:42 +0100
Message-ID: <CAA8k23Qu9=9LgBr+FzqB55LKjSiiKimZBHJ1=gwfi70cYDdcrw@mail.gmail.com>
From: Andy Talbot <andy.g4jnt@gmail.com>
To: rsgb_lf_group@yahoogroups.co.uk, rsgb_lf_group@blacksheep.org
Subject: LF: Fast Serial Interfacing with PICs
Content-Type: multipart/alternative; boundary=001a1143adccefaa2b052fe246b1
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

--001a1143adccefaa2b052fe246b1
Content-Type: text/plain; charset=UTF-8

I know the subject is nothing to do with LF, but I didn't keep the original
thread...

A few months ago someone on one of these two LF reflectors pointed me at
the Enhanced USART in the 16F688 and later PIC devices, saying how the baud
rate could be set as high as Fosc / 4. So getting 3M Baud with a 12MHz Xtal
for compatibility with FTDI chip COM ports at thier highest setting.

Who was it and have you managed to do this?   I finally got round to
testing a 16F688 at 3Meg   and am getting some funny results that mean
sometimes the PIC's EUSART sends the right data, and sometimes it gets
itself tied up in knots, sending one character several times

It is not a programming error either, as the code works perfectly at lower
baud rates, by just changing the divider.   The nature of the problem looks
and feels like something inherent to the internals of the chip

Andy  G4JNT

--001a1143adccefaa2b052fe246b1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I know the subject is nothing to do with LF, but I didn=
9;t keep the original thread...<div><br></div><div>A few months ago someone=
 on one of these two LF reflectors pointed me at the Enhanced USART in the =
16F688 and later PIC devices, saying how the baud rate could be set as high=
 as Fosc / 4. So getting 3M Baud with a 12MHz Xtal for compatibility with F=
TDI chip COM ports at thier highest setting.</div><div><br></div><div>Who w=
as it and have you managed to do this? =C2=A0 I finally got round to testin=
g a 16F688 at 3Meg =C2=A0 and am getting some funny results that mean somet=
imes the PIC&#39;s EUSART sends the right data, and sometimes it gets itsel=
f tied up in knots, sending one character several times</div><div><br></div=
><div>It is not a programming error either, as the code works perfectly at =
lower baud rates, by just changing the divider. =C2=A0 The nature of the pr=
oblem looks and feels like something inherent to the internals of the chip=
=C2=A0</div><div><br></div><div>Andy =C2=A0G4JNT</div><div><br></div></div>

--001a1143adccefaa2b052fe246b1--