Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Wed, 22 Jul 2020 10:05:04 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 06MGquRW021634; Wed, 22 Jul 2020 12:53:34 -0400 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 06MGqtxB021623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 22 Jul 2020 12:52:55 -0400 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 06MGqWHR022971 for ; Wed, 22 Jul 2020 12:52:44 -0400 Received: from w92expo21.exchange.mit.edu (18.7.74.75) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 22 Jul 2020 12:52:32 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92expo21.exchange.mit.edu (18.7.74.75) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 22 Jul 2020 12:52:46 -0400 Received: from NAM12-MW2-obe.outbound.protection.outlook.com (104.47.66.43) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 22 Jul 2020 12:52:46 -0400 Received: from DM5PR13CA0037.namprd13.prod.outlook.com (2603:10b6:3:7b::23) by BYAPR01MB5222.prod.exchangelabs.com (2603:10b6:a03:81::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.20; Wed, 22 Jul 2020 16:52:45 +0000 Received: from DM3NAM03FT034.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:7b:cafe::3) by DM5PR13CA0037.outlook.office365.com (2603:10b6:3:7b::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.15 via Frontend Transport; Wed, 22 Jul 2020 16:52:45 +0000 Received: from mailscanner.virtbiz.com (208.77.216.252) by DM3NAM03FT034.mail.protection.outlook.com (10.152.82.192) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.10 via Frontend Transport; Wed, 22 Jul 2020 16:52:43 +0000 Received: from s18855546.onlinehome-server.com (s18855546.onlinehome-server.com [74.208.193.200]) by mailscanner.virtbiz.com (8.14.7/8.14.7) with ESMTP id 06MGqecb011106 for ; Wed, 22 Jul 2020 11:52:42 -0500 Received: from mai.hallikainen.org (localhost [127.0.0.1]) by s18855546.onlinehome-server.com (8.14.4/8.14.4) with ESMTP id 06MGqeAH030324 for ; Wed, 22 Jul 2020 09:52:40 -0700 Received: (from apache@localhost) by mai.hallikainen.org (8.14.4/8.14.4/Submit) id 06MGqeQf030321; Wed, 22 Jul 2020 09:52:40 -0700 Received: from 75.166.116.185 (SquirrelMail authenticated user harold) by mai.hallikainen.org with HTTP; Wed, 22 Jul 2020 09:52:40 -0700 From: Harold Hallikainen To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 22 Jul 2020 09:52:40 -0700 Subject: Re: [PIC]: 18F47K42 Thread-Topic: [PIC]: 18F47K42 Thread-Index: AdZgSj7TGv0/rjZWRRWryUNQyadtnw== Message-ID: References: <20200721202120.06a56fd6300ec2bfca6379d4e10ab8d2.956b8391e5.wbe@email27.godaddy.com> <8605a19eb88141e8766cdcea714509d6.squirrel@mai.hallikainen.org> <388472011.3736964.1595394760347@mail.yahoo.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <388472011.3736964.1595394760347@mail.yahoo.com> Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of mai.hallikainen.org designates 208.77.216.252 as permitted sender) receiver=protection.outlook.com; client-ip=208.77.216.252; helo=mailscanner.virtbiz.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitprod.onmicrosoft.com; s=selector2-mitprod-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ycB9WkzwmLd16s3GWuipF46QxRcaKZNQ79gP+MZDPIQ=; b=ITbLHAFzrsHpYPa3ZZGO5tWTLeUpCL9z9unvUSdNiwUDkgIsaQNl6apWRwTxxS2+DElW8Nb93wZWAyZ/aKyret/qC4USorWPPVQDBbSu2yA87MgrJ76J4Ej4/SDlZg7pBv6SxAIhqgQCDvrNLAiXtARYjqMUl0/RmZqDlZQbQXI= authentication-results: spf=pass (sender IP is 208.77.216.252) smtp.mailfrom=mai.hallikainen.org; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=permerror action=none header.from=mai.hallikainen.org; user-agent: SquirrelMail/1.4.22-5.el6 errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-authentication-warning: mai.hallikainen.org: apache set sender to harold@mai.hallikainen.org using -f x-greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mailscanner.virtbiz.com [208.77.216.252]); Wed, 22 Jul 2020 11:52:43 -0500 (CDT) x-topics: [PIC] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Also, as I recall, some the BRGH bit did not work on some chips. That may have been fixed in later revisions. As always, it's good to look at the errata! Harold > I had a similar problem - different PIC, different compiler.=C2=A0 On th= at I > looked in the part errataPIC18(L)F27/47/57K42 Family Silicon Errata and > Data Sheet Clarification > Document DS80000773C-page 6=C2=A0for yours it says > 4. Module: Universal AsynchronousReceiver Transmitter (UART)=C2=A0 > 4.1 Baud Rate Generator Speed SelectThe Baud Rate Generator Speed Select > feature(BRGS bit in the UxCON0 register) in DALImode is not functional. > The Baud RateGenerator always operates at normal speedwith 16 baud clocks > per bit in DALI mode.=C2=A0 > Work aroundNone.=C2=A0 > Affected Silicon Revisions=C2=A0 =C2=A0.... this may be the problem ?????= ??? > 4.2 Stop Bit Interrupt Flag=C2=A0 > Stop Bit interrupt flag functionality is notavailable in the CERIF bit in > revision A1.=C2=A0Work aroundUse Timer2 with HLT and connect the UART RXp= ort > to the timer Reset trigger. Set the time-outperiod to the desired Stop bi= t > time (for DALImode, this is equivalent to two Stop bits at 1200baud =3D 1= ..66 > ms). When the Stop bit is received,the timer times out notifying end of > data.Affected Silicon Revisions=C2=A0 > 4.3 Auto-BaudWhen the UART is configured as follows,=C2=A0 > > > Roger > > On Tuesday, July 21, 2020, 08:39:08 PM PDT, Harold Hallikainen > wrote: > > If SOMETHING happens when you send a character to the UAST, I suspect > it's > working, but the bit rate or bits per character is wrong (especially the > bit rate). Also, some chips allow you to invert the transmit data which > will also, of course, mess things up. Can you look at the pin on a logic > analyzer or scope? That way you can see what's going on. > > Good luck! > > Harold > > >> >>=C2=A0 All, >> >>=C2=A0 I am trying to get the EUSART1 on a >>=C2=A0 PIC18F47K42 in a 40 pin dip package >>=C2=A0 to operate. >> >>=C2=A0 This part has the Peripheral Pin Select. >>=C2=A0 functionality that allows you to remap >>=C2=A0 some peripheral input and outputs to more >>=C2=A0 convenient package pins for easier pcb >>=C2=A0 routing. >> >>=C2=A0 I have chosen to make USART1 input on >>=C2=A0 Pin C7 and output on pin C6. >> >>=C2=A0 I am using Mikro C for PIC and have used the. >>=C2=A0 USART library to do the USART setup, and am >>=C2=A0 using the EasyPIC 7 dev board for programming >>=C2=A0 and code development. >> >>=C2=A0 I have set the baud rate to 19200, set USART1 >>=C2=A0 to be active, enabled the USART, transmit and >>=C2=A0 receive on, etc. >> >>=C2=A0 I either get nothing from the USART or >>=C2=A0 gibberish. >> >>=C2=A0 I have been through the code a dozen times >>=C2=A0 have tried various combinations of options >>=C2=A0 etc. >> >>=C2=A0 Does anyone have any experience or ideas >>=C2=A0 about why might this be happening? >>=C2=A0 Or suggestions of what to try? >> >>=C2=A0 Using Microchip C or MAPLB X with the Code >>=C2=A0 Configurator Ap is not possible. >> >>=C2=A0 I want to be able to use this processor >>=C2=A0 without having to rely on Mplab X with code >>=C2=A0 configurator. >> >>=C2=A0 Any insight or suggestions would be greatly >>=C2=A0 appreciated. >> >>=C2=A0 Thanks and Regards, >> >> Jim >> >> >> -- >> http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive >> View/change your membership options at >> http://mailman.mit.edu/mailman/listinfo/piclist >> > > > -- > FCC Rules Updated Daily at http://www.hallikainen.com > Not sent from an iPhone. > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 FCC Rules Updated Daily at http://www.hallikainen.com Not sent from an iPhone. --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .