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; Tue, 28 Jan 2020 22:23:11 -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 00T67wQK010773; Wed, 29 Jan 2020 01:14:24 -0500 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 00T67fWg010650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 29 Jan 2020 01:07:53 -0500 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 00T69vZP023688 for ; Wed, 29 Jan 2020 01:10:29 -0500 Received: from w92expo31.exchange.mit.edu (18.7.74.43) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 29 Jan 2020 01:04:39 -0500 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by w92expo31.exchange.mit.edu (18.7.74.43) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 29 Jan 2020 01:07:18 -0500 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.175) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 29 Jan 2020 01:07:18 -0500 Received: from CY4PR01CA0024.prod.exchangelabs.com (2603:10b6:903:1f::34) by MWHPR01MB2606.prod.exchangelabs.com (2603:10b6:300:ff::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.22; Wed, 29 Jan 2020 06:07:16 +0000 Received: from CO1NAM03FT059.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::203) by CY4PR01CA0024.outlook.office365.com (2603:10b6:903:1f::34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.24 via Frontend Transport; Wed, 29 Jan 2020 06:07:16 +0000 Received: from mail-lj1-f169.google.com (209.85.208.169) by CO1NAM03FT059.mail.protection.outlook.com (10.152.81.192) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.18 via Frontend Transport; Wed, 29 Jan 2020 06:07:16 +0000 Received: by mail-lj1-f169.google.com with SMTP id f25so4258002ljg.12 for ; Tue, 28 Jan 2020 22:07:16 -0800 (PST) From: "Forrest Christian (List Account)" To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 28 Jan 2020 22:07:03 -0800 Subject: Re: [PIC] PICkit 2 Thread-Topic: [PIC] PICkit 2 Thread-Index: AdXWbJT1D1MTwXcLQ0aVJljw38C/4g== Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: 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 packetflux.com designates 209.85.208.169 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.169; helo=mail-lj1-f169.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetflux-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=KYLRIgC02KOcZATkMh+rLmJQR4qBi+0wZLWfQCrL6Hc=; b=anLDilO/ks1kNm4LXh9cID7RBhlP2eCuZK7B4iHGkdAtxLAt5JJHTQuzm2bp+aTIo4 x6JRrpm5tWKMTbcM9HadjPzHyEhxH72NX02MbP1viKaJxkUrjOOOQanjP9WuMzueEBBA stQs2wBMOFsk17R71RMGLvi09RwlbjpVZXOVZdF4BI5a+oCNJUxHjCuHTX/Sj5Juf6n0 ssIAnZQyvfwi9Wgi0/72xOpD5nkCApftSi+Owzlcc2NE3hZXfNH0UaLeVhza/YU/7qhI WKDsGdb2o+OJNqcwK6kncK6EQoOszeB8JKjDrtGJFJgPsHXfxL2Qn9IIwIPBpdFjtBfC XdMw== authentication-results: spf=pass (sender IP is 209.85.208.169) smtp.mailfrom=packetflux.com; mit.edu; dkim=pass (signature was verified) header.d=packetflux-com.20150623.gappssmtp.com; mit.edu; dmarc=bestguesspass action=none header.from=packetflux.com;compauth=pass reason=109 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-received: by 2002:a2e:9696:: with SMTP id q22mr843160lji.54.1580278033965; Tue, 28 Jan 2020 22:07:13 -0800 (PST) x-topics: [PIC] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I somehow don't think the following is applicable to the PICkit2, but, maybe this will help: https://microchipdeveloper.com/mplabx:switching-usb-drivers On Tue, Jan 28, 2020 at 9:35 PM Bob Blick wrote: > Hi Allen, > When I look in the Windows 7 Device Manager, the only entries under > HID-compliant devices(I forget the exact name) are only two items, and th= ey > are both for the PICkit2, because they disappear when I unplug. But in > Windows 10, there are 38 items that reduce to 36 when I unplug. I can't > really tell which is which. I guess I should try to figure out > vendor/device codes from the Win7 machine and go through "properties" for > the entries in the Win10 machine to see if I can identify the PICkit2. > Best regards, Bob > > ________________________________________ > From: piclist-bounces@mit.edu on behalf of > Allen Mulvey > Sent: Tuesday, January 28, 2020 7:57 PM > To: Microcontroller discussion list - Public. > Subject: Re: [PIC] PICkit 2 > > Have you tried going into the Device Driver and roll back the driver? It > is a button on the Driver tab in the device properties. You can then > prevent future updates although I don't remember how I did that. It has > been a long time since I used my PICkit. > > Allen > > ------ Original Message ------ > From: "piclist-bounces@mit.edu" > To: "Microcontroller discussion list - Public." > Sent: 1/28/2020 12:00:47 PM > Subject: [CAUTION: Failed DKIM Test][PIC] PICkit 2 > > >I am trying to use a PICkit 2 and the PICkit 2 v2.61 application under > Windows 10. I got it to work once. Now it is invisible to the PICkit2 > software. In Device Manager I believe it is showing up as a USB input > device. I tried removing that device but when I plug the PICkit2 back in = it > shows up the same way. Due to my poor understanding of Windows directory > structure I can't seem to find the actual driver folder for the PICkit2 t= o > try to force a particular driver. > > > >I've got two PICkit2's and cables and they both do the same thing. They > work on a Windows 7 machine but that machine has a dying hard drive so I > really can't use it very much longer. > > > >Anyone been here before and gotten their PICkit2 to work? > > > >Thanks! > > > >Bob > > > -- > 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 - Forrest --=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 .