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, 7 Jul 2020 06:27:47 -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 067DJGWx018218; Tue, 7 Jul 2020 09:19:40 -0400 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 067DJFPt018215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 7 Jul 2020 09:19:15 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 067DFwUi003656 for ; Tue, 7 Jul 2020 09:18:12 -0400 Received: from oc11expo11.exchange.mit.edu (18.9.4.16) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 7 Jul 2020 09:17:52 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by oc11expo11.exchange.mit.edu (18.9.4.16) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 7 Jul 2020 09:18:42 -0400 Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.177) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 7 Jul 2020 09:18:42 -0400 Received: from DM3PR03CA0002.namprd03.prod.outlook.com (2603:10b6:0:50::12) by BYAPR01MB4456.prod.exchangelabs.com (2603:10b6:a03:a0::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.28; Tue, 7 Jul 2020 13:18:41 +0000 Received: from DM3NAM03FT005.eop-NAM03.prod.protection.outlook.com (2603:10b6:0:50:cafe::b2) by DM3PR03CA0002.outlook.office365.com (2603:10b6:0:50::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.21 via Frontend Transport; Tue, 7 Jul 2020 13:18:40 +0000 Received: from mail-lj1-f181.google.com (209.85.208.181) by DM3NAM03FT005.mail.protection.outlook.com (10.152.82.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.24 via Frontend Transport; Tue, 7 Jul 2020 13:18:40 +0000 Received: by mail-lj1-f181.google.com with SMTP id e8so15573059ljb.0 for ; Tue, 07 Jul 2020 06:18:40 -0700 (PDT) From: "Forrest Christian (List Account)" To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 7 Jul 2020 06:27:28 -0700 Subject: Re: [SPAM 29.15] Re: [SPAM 29.15] [PIC] XC8 PRO Unlocking Thread-Topic: [SPAM 29.15] Re: [SPAM 29.15] [PIC] XC8 PRO Unlocking Thread-Index: AdZUYmfqqcr9wraLSP6soNAcBV3WEQ== Message-ID: References: <9379a928-9bb6-0fb3-a4ce-8d4edbc6fcb9@audiovisualdevices.com.au> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <9379a928-9bb6-0fb3-a4ce-8d4edbc6fcb9@audiovisualdevices.com.au> 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.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.208.181; helo=mail-lj1-f181.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=KbSRw9/pMhSneQaipcEl0SZIx++hQ5GsD6HW/dWDDvE=; b=c+UOPSOYKpx2zGZ8bqvevWduNyfmz3p92C7aitZzArWorkekK7NbQROugeBvkiGxld 7WQIusymALPZymQUWbFsrydqfUnC+XqIb04t29Cary0QKd1A6Gqsp43LgjiryQiNRL/w tl31MlGpZegrFjDl/RcfwcsiStE0tGCycFU/neCdcnmJp94LcLJgfGskunhFF9/cByLm dPE8LZhDSjuWvyKyvE7uX0yhPOwQu+/nnWO2h1zTxB09eYDh3MTVDqsRqCELbCH0fHi2 2x9kTuMd4vkuhydG7KNlf/OEwgwCGtEv4C4TU5L1jMp1LjyAM9bCBChkIzawru2/2wQt qF+A== authentication-results: spf=pass (sender IP is 209.85.208.181) 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; 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:a05:651c:1b5:: with SMTP id c21mr5113650ljn.82.1594127918728; Tue, 07 Jul 2020 06:18:38 -0700 (PDT) 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 ok, that's all 100% valid. I'm also of the opinion that these tools should be free, Apparently microchip management and at least some of the compiler developers have differing opinions on what should be free or not as well. Regardless, there is a .pdf at http://ww1.microchip.com/downloads/en/DeviceDoc/Installing-and-Licensing-MP= LAB-XC-C-Compilers%2520DS50002059.pdf which covers most of the process. One note is that sometimes the script has to be run as administrator. Another note is that the script sometimes refuses to work at all. In those cases I've discovered that the script was using the wrong xclm.exe. I believe last time I relicensed my xc8 compiler I had to manually run xclm from the compiler directory, or perhaps the mplabx directory, using an admin level command prompt and replicating the arguments from the script. On Tue, Jul 7, 2020, 6:09 AM David Duffy (AVD) < david@audiovisualdevices.com.au> wrote: > The existing code I need to recompile was compiled with PRO but the > licence expired. The code doesn't quite fit the chip without PRO mode. > Yes, the customer should have used a bigger chip, but that's not an > option now. I can't modify the code to fit without risking of breaking > stuff. A new 30 day licence was bought and it's refusing to install. At > present I'm over this Microchip foolishness and just need to get the job > done. They don't need to make things hard when we're already buying > their product. > David... > > On 7/07/2020 8:38 pm, Forrest Christian (List Account) wrote: > > Two items: > > > > 1) Many (most?) people don't really need the PRO version of the compile= r, > > as the free compiler produces acceptable code for many/most application= s. > > > > The pro is only needed if you've got an application where the code size > is > > critical (i.e. you're shipping a million units and if you can fit in th= e > > smaller part it could save you lots of $$$), OR if you've got an > > application which needs to be more highly optimized for speed. Anymor= e > > the processors are cheap and fast enough that neither really matters fo= r > > most applications. For hobby use, you can often just move to somethin= g > > with a bit more memory and possibly a faster clock. > > > > 2) I can read your request two ways: One option is that you have a > > legitimate license and are having licensing issues, then if you provide= a > > bit more detail as to what is going on someone might be able to help. > The > > licensing setup can be a little weird. Alternatively, if you are askin= g > > about how to enable XC8 pro without paying for it, someone else will ne= ed > > to reply since I'm of the opinion that one should pay for legitimate > copies > > of software if possible. > > > > On Tue, Jul 7, 2020 at 2:04 AM David Duffy (AVD) < > > david@audiovisualdevices.com.au> wrote: > > > >> Can anyone assist with "unlocking" XC8 ? Direct email me if preferred. > >> David... > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > On Tue, Jul 7, 2020, 6:09 AM David Duffy (AVD) < david@audiovisualdevices.com.au> wrote: > The existing code I need to recompile was compiled with PRO but the > licence expired. The code doesn't quite fit the chip without PRO mode. > Yes, the customer should have used a bigger chip, but that's not an > option now. I can't modify the code to fit without risking of breaking > stuff. A new 30 day licence was bought and it's refusing to install. At > present I'm over this Microchip foolishness and just need to get the job > done. They don't need to make things hard when we're already buying > their product. > David... > > On 7/07/2020 8:38 pm, Forrest Christian (List Account) wrote: > > Two items: > > > > 1) Many (most?) people don't really need the PRO version of the compile= r, > > as the free compiler produces acceptable code for many/most application= s. > > > > The pro is only needed if you've got an application where the code size > is > > critical (i.e. you're shipping a million units and if you can fit in th= e > > smaller part it could save you lots of $$$), OR if you've got an > > application which needs to be more highly optimized for speed. Anymor= e > > the processors are cheap and fast enough that neither really matters fo= r > > most applications. For hobby use, you can often just move to somethin= g > > with a bit more memory and possibly a faster clock. > > > > 2) I can read your request two ways: One option is that you have a > > legitimate license and are having licensing issues, then if you provide= a > > bit more detail as to what is going on someone might be able to help. > The > > licensing setup can be a little weird. Alternatively, if you are askin= g > > about how to enable XC8 pro without paying for it, someone else will ne= ed > > to reply since I'm of the opinion that one should pay for legitimate > copies > > of software if possible. > > > > On Tue, Jul 7, 2020 at 2:04 AM David Duffy (AVD) < > > david@audiovisualdevices.com.au> wrote: > > > >> Can anyone assist with "unlocking" XC8 ? Direct email me if preferred. > >> David... > -- > 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 .