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; Sun, 15 Nov 2020 16:25:36 -0800 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AG0HUSM020215; Sun, 15 Nov 2020 19:18:01 -0500 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 0AG0HTPO020212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 15 Nov 2020 19:17:29 -0500 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 0AG0HRgQ013687 for ; Sun, 15 Nov 2020 19:17:29 -0500 Received: from w92expo7.exchange.mit.edu (18.7.74.61) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sun, 15 Nov 2020 19:17:23 -0500 Received: from oc11exhyb4.exchange.mit.edu (18.9.1.100) by w92expo7.exchange.mit.edu (18.7.74.61) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sun, 15 Nov 2020 19:17:27 -0500 Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.102) by oc11exhyb4.exchange.mit.edu (18.9.1.100) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sun, 15 Nov 2020 19:17:27 -0500 Received: from BN6PR02CA0038.namprd02.prod.outlook.com (2603:10b6:404:5f::24) by BN7PR01MB3620.prod.exchangelabs.com (2603:10b6:406:8d::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.28; Mon, 16 Nov 2020 00:17:25 +0000 Received: from BN8NAM11FT064.eop-nam11.prod.protection.outlook.com (2603:10b6:404:5f:cafe::12) by BN6PR02CA0038.outlook.office365.com (2603:10b6:404:5f::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.28 via Frontend Transport; Mon, 16 Nov 2020 00:17:25 +0000 Received: from bosmailout02.eigbox.net (66.96.187.2) by BN8NAM11FT064.mail.protection.outlook.com (10.13.176.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.28 via Frontend Transport; Mon, 16 Nov 2020 00:17:25 +0000 Received: from bosmailscan04.eigbox.net ([10.20.15.4]) by bosmailout02.eigbox.net with esmtp (Exim) id 1keSCy-0007vi-Pw for piclist@mit.edu; Sun, 15 Nov 2020 19:17:24 -0500 Received: from [10.115.3.31] (helo=bosimpout11) by bosmailscan04.eigbox.net with esmtp (Exim) id 1keSCy-000330-GB for piclist@mit.edu; Sun, 15 Nov 2020 19:17:24 -0500 Received: from bosauthsmtp19.yourhostingaccount.com ([10.20.18.19]) by bosimpout11 with id soHM230020QhFXN01oHQRg; Sun, 15 Nov 2020 19:17:24 -0500 Received: from 035-134-194-170.res.spectrum.com ([35.134.194.170]:21002 helo=michael2) by bosauthsmtp19.eigbox.net with esmtpa (Exim) id 1keSCv-0006uc-76 for piclist@mit.edu; Sun, 15 Nov 2020 19:17:21 -0500 From: Don Kuenz To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Sun, 15 Nov 2020 16:17:21 -0800 Subject: [PIC] An In-Circuit Serial Programmer application Thread-Topic: [PIC] An In-Circuit Serial Programmer application Thread-Index: Ada7rwGR43PdMa8sTE+jXWu0Iug9Fg== Message-ID: <6c4cb75c-c4d5-43a4-8bb3-5c0613364c98@BN8NAM11FT064.eop-nam11.prod.protection.outlook.com> References: List-Help: List-Subscribe: , List-Unsubscribe: , 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 eigbox.net designates 66.96.187.2 as permitted sender) receiver=protection.outlook.com; client-ip=66.96.187.2; helo=bosmailout02.eigbox.net; dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=crcomp.net; s=dkim; h=Sender:References:Subject:From:To:Date:Reply-To:Message-ID:Cc: MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=EoiohAVgdOq4Wi4GWZSlxczjg+HeF1yRtC1yG+nn6a8=; b=A7aZyFr/iLaXVnQVqb8dxELCQe byO+7FZyJ6/eeR3tadGbeU/WI5eWyUPUkYUs5OzmjjqKCAvD6WUBnc/u/hcRGqFXpMdxIlarVhmoe aA+Nul6DEe84vPgNdcUsmrri0zoMWypEziRwXzCl4vN0I53AhRz2SjsphX0Vijo3logjCr16dHZ4L n42DBzZwtCh99ooxNEHZ68iMKcbMqnkS9jy8dFdxvqdYk9FoRUNAVuiiraYuvjj0eR1y7dlTNa0I3 knvQJWw3HJucPd4K4uGI/szjeln5FdSybynxO2g8gl9XlP65ge/F6fPTfCB9tzEcxVwA8BGHXcVTx FV4Qms6Q==; authentication-results: spf=pass (sender IP is 66.96.187.2) smtp.mailfrom=eigbox.net; mit.edu; dkim=fail (no key for signature) header.d=crcomp.net; mit.edu; dmarc=none action=none header.from=crcomp.net; 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-authority-analysis: v=2.3 cv=DtjNBF3+ c=1 sm=1 tr=0 a=9UqFsMnAB6EOkiq4MrOclQ==:117 a=06cp/ESuOE+YetzzmHXoLw==:17 a=HpEJnUlJZJkA:10 a=nNwsprhYR40A:10 a=kE10iPYx14oA:10 a=B1_QNwyYAAAA:8 a=QejfARXMAAAA:8 a=ZoPaD1RDGQPUCGnIGb8A:9 a=VAZGENgY0A8A:10 a=f3KzUBtQ6mTbyx-YvAwf:22 a=BC3gsuZa1vz2YJYxs7Nf:22 a=Z5ABNNGmrOfJ6cZ5bIyy:22 a=UDnyf2zBuKT2w-IlGP_r:22 x-en-authuser: mail@crcomp.net x-en-userinfo: de154d50cc16294658ed7b7577430c21:931c98230c6409dcc37fa7e93b490c27 x-en-orighost: 035-134-194-170.res.spectrum.com x-en-origip: 35.134.194.170 x-topics: [PIC] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 =20 >> Don wrote: >>> This project shows how to implement an In-Circuit Serial >>> Programmer application. It utilizes the ICSP's 5 VDC >>> (Vdd) pin to toggle the PIC microcontroller between >>> application mode and programming mode. >>> >>> https://crcomp.net/icsp/index.php > Chris wrote: >> Nice, but why not just use two Jumpers or a DPDT switch rather than add >> additional silicon? >> My preference with the more recent PIC's is to use PPS to assign the USA= RT >> to those pins. >> I then use the PICKit as a terminal for debugging as well as a Programme= r. >> The serial interface may even have a use in the target application. >> Have the serial interface use the same pin assignments as the ICSP and y= ou >> have a nice 'Plug and Play' programming/debugging/communications port. Chris wrote: > P.S. - It also works well with a Bootloader. > use the ICSP interface to install the TinyBootloader or an equivalent wit= h > the ICSP Dat and Clk lines set at the Rx and Tx lines and you have a nice > development device with Programming, Debugging and Communications all > achieved via a USB/Serial adapter - Great to hand out to students or use > for casual experimenting as well as in target applications. There's four good reasons (or at least three and a half) for me to use=20 additional silicon. Let's start with the half reason. If you look=20 closely at Figure 4 you see a blue DIP switch near the top, middle. It's a drag to flip those switches each time. A mouse click is so much=20 easier. There's also a dearth of ICSP applications available on the Inet, probably for a very good reason. The wide, inviting, easy route with old MCUs is to simply dedicate RB6 and RB7 to ICSP. The third reason is my application allows all 8 bits of RB to be used. The final reason is actually the best. It motivated you to talk about another way. It's time for me to step up to an MCU with a UART. Danke, --=20 Don, KB7RPU, https://www.qsl.net/kb7rpu There was a young lady named Bright Whose speed was far faster than light; She set out one day In a relative way And returned on the previous night. --=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 .