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, 29 Jan 2020 08:34:26 -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 00TGN3Lh000953; Wed, 29 Jan 2020 11:25:46 -0500 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 00TGN2Tg000949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 29 Jan 2020 11:23:02 -0500 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 00TGMoiT028125 for ; Wed, 29 Jan 2020 11:22:53 -0500 Received: from oc11expo22.exchange.mit.edu (18.9.4.84) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 29 Jan 2020 11:20:24 -0500 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by oc11expo22.exchange.mit.edu (18.9.4.84) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 29 Jan 2020 11:20:37 -0500 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.174) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 29 Jan 2020 11:20:31 -0500 Received: from SN2PR01CA0009.prod.exchangelabs.com (2603:10b6:804:2::19) by BN8PR01MB5362.prod.exchangelabs.com (2603:10b6:408:b0::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.23; Wed, 29 Jan 2020 16:20:30 +0000 Received: from CO1NAM03FT014.eop-NAM03.prod.protection.outlook.com (2a01:111:f400:7e48::204) by SN2PR01CA0009.outlook.office365.com (2603:10b6:804:2::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2665.23 via Frontend Transport; Wed, 29 Jan 2020 16:20:30 +0000 Received: from mail-yb1-f179.google.com (209.85.219.179) by CO1NAM03FT014.mail.protection.outlook.com (10.152.80.101) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.26 via Frontend Transport; Wed, 29 Jan 2020 16:20:30 +0000 Received: by mail-yb1-f179.google.com with SMTP id o199so107957ybc.4 for ; Wed, 29 Jan 2020 08:20:30 -0800 (PST) From: Manu Abraham To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 29 Jan 2020 08:20:26 -0800 Subject: Re: [PIC] PICkit 2 Thread-Topic: [PIC] PICkit 2 Thread-Index: AdXWwfjNQlN/aRJHSr2gYqo/OzJepA== 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 gmail.com designates 209.85.219.179 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.219.179; helo=mail-yb1-f179.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=QIMRd+06K6vlDSC73aZBSWfCEFNbVjBlH5XHhJcP+n8=; b=OPzEbKRBu7s2fPYq1ZiBo3QNBOuQSdaVd+FV688pOdXEk7Ba4FQS4qk3S85Aewhrsa 4YljlUh0tn1kvvKWvWzEZjfca6aeuJxZjMIiWuH018flmkVIbmif5T6ajnqicSJOwO7N ZII0C6fZmqUfB/9FNdo18GusdzQkBFx3BqcWpxrrzk7O9J6CoIIeP9uhWNNqYwbjo2WV uTsfCoygJYLIEMqpXx1Ls3q+IDRyFqjk9LFg0wSWoqkKhDYXy8cILwj48tKQY0gK0+RN UTuGnYQHKEkxDDQXnEkTcjcq+i2UY+eGqa2PzFySXCIx9kMVNAwjR00Bp18UtB3Hjf1P Gskw== authentication-results: spf=pass (sender IP is 209.85.219.179) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com;mit.edu; dmarc=pass action=none header.from=gmail.com;compauth=pass reason=100 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:a25:6d05:: with SMTP id i5mr196451ybc.520.1580314828679; Wed, 29 Jan 2020 08:20:28 -0800 (PST) x-topics: [PIC] x-mime-autoconverted: from quoted-printable to 8bit by PCH.mit.edu id 00TGN2Tg000949 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Bob, You might want to check the VID/PID of the device, why it does not bind to the driver. Maybe you could possibly bind the device manually, by associating the VID/P= ID. Cheers, Manu On Wed, Jan 29, 2020 at 9:25 PM Bob Blick wrote: > > Hi Wouter, > Interesting. If it doesn't need a driver, and it does show in Device Mana= ger as the correct items, perhaps the PICkit2 application software is confu= sed by the 36 other items listed as HID-compliant devices(whatever they may= be) as opposed to Win7 only showing the entries associated with PICkit2. > I suppose nobody uses the PICkit2 anymore, otherwise I would expect more = people would be having the same problem as me. Since I don't do any new dev= elopment with PICs, I'm not going to go out and buy a new programmer. > Thanks for the reply! > Best regards, Bob > ________________________________________ > From: Wouter van Ooijen > Sent: Tuesday, January 28, 2020 12:41 PM > To: Bob Blick > Subject: Re: [PIC] PICkit 2 > > Op 28-Jan-20 om 6:00 PM schreef Bob Blick: > > 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 softw= are. 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 to try to forc= e 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 r= eally can't use it very much longer. > > > > Anyone been here before and gotten their PICkit2 to work? > > > > Thanks! > > > > Bob > > Not been there, but my pcikit2 (might be a Chinses clone) works like a > charm on W 10. > > It shows as a "HID-compliant vendor-defined device". IIRC a HID device > on W doesn't need a driver. > > > -- > > Wouter "Objects? No Thanks!" van Ooijen > > > -- > 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 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .