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; Mon, 27 Jul 2020 23:10:31 -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 06S60Xqo032761; Tue, 28 Jul 2020 02:01:55 -0400 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 06S60WdQ032758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 28 Jul 2020 02:00:32 -0400 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 06S5wjQa015635 for ; Tue, 28 Jul 2020 01:58:45 -0400 Received: from w92expo33.exchange.mit.edu (18.7.74.45) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 28 Jul 2020 02:00:12 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92expo33.exchange.mit.edu (18.7.74.45) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 28 Jul 2020 02:00:31 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.174) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 28 Jul 2020 02:00:31 -0400 Received: from DM5PR07CA0051.namprd07.prod.outlook.com (2603:10b6:4:ad::16) by BN6PR0101MB3138.prod.exchangelabs.com (2603:10b6:405:2e::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.24; Tue, 28 Jul 2020 06:00:30 +0000 Received: from DM3NAM03FT022.eop-NAM03.prod.protection.outlook.com (2603:10b6:4:ad:cafe::24) by DM5PR07CA0051.outlook.office365.com (2603:10b6:4:ad::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.21 via Frontend Transport; Tue, 28 Jul 2020 06:00:30 +0000 Received: from mail-pf1-f181.google.com (209.85.210.181) by DM3NAM03FT022.mail.protection.outlook.com (10.152.82.180) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.10 via Frontend Transport; Tue, 28 Jul 2020 06:00:30 +0000 Received: by mail-pf1-f181.google.com with SMTP id d188so4285473pfd.2 for ; Mon, 27 Jul 2020 23:00:30 -0700 (PDT) Received: from [192.168.1.5] (118-93-164-31.dsl.dyn.ihug.co.nz. [118.93.164.31]) by smtp.gmail.com with ESMTPSA id q6sm16762370pfg.76.2020.07.27.23.00.27 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jul 2020 23:00:28 -0700 (PDT) From: Brent Brown To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Mon, 27 Jul 2020 23:00:25 -0700 Subject: Re: [PIC]: MPLAB XC C Compiler License Change Thread-Topic: [PIC]: MPLAB XC C Compiler License Change Thread-Index: AdZkpcySmaCpkWu5TV+qgXplZalfPw== Message-ID: <5F1FBEF9.1989.17F9DEE@brent.eds.co.nz> References: <5F1F5405.1988.5211C4F@brent.eds.co.nz>, , <5F1F9B43.8040300@narwani.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5F1F9B43.8040300@narwani.org> 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: TempError X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: None (protection.outlook.com: eds.co.nz does not designate permitted sender hosts) dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eds-co-nz.20150623.gappssmtp.com; s=20150623; h=from:organization:to:date:mime-version:subject:message-id:priority :in-reply-to:references:content-transfer-encoding :content-description; bh=ge58IFJIOQdyuYrgAdO9nWCjDGo60yYkrH38fSuqOh8=; b=Gs/vDvCO1skZKgx90ia0tQeBDERXcmxb0ftn/HRwS4TogYsLcPVeL+EpW2kLOlYLQJ u1ds53I2nByckTqMDlIaDA3snuv4B3O8t6ESQlGLtLSwRqyOLb0GG6cEb9jqCVbp4ZFY ZWVqnxZfn20IY1QLK6ZDztz6QqQdzQ3PC/9VjK17UUmvRE8WgUSwy3L32I0UM5d+t0+g dw3vKxnVadL0xuMX8WQkuU4oe5wx9y1U7JgRl44S4cfOIUeXtI9qyKW5WIqVhmyddLvu Fco1l7H79eTH718BhD7PqSuLPeOnvZSjwlcSWQwVDLL8AHQdyzQ5UsYsCAuWli7N1P5/ YsUg== authentication-results: spf=none (sender IP is 209.85.210.181) smtp.mailfrom=eds.co.nz; mit.edu; dkim=pass (signature was verified) header.d=eds-co-nz.20150623.gappssmtp.com; mit.edu; dmarc=none action=none header.from=eds.co.nz; 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:a63:fa15:: with SMTP id y21mr22892293pgh.339.1595916028917; Mon, 27 Jul 2020 23:00:28 -0700 (PDT) x-topics: [PIC] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I just discovered Keil for 8051 for free... Silicon Labs offer a licence ke= y for anyone=20 who registers. It seems to retail for about USD1500. Revived a project that has a SiLabs C8051F120 (no slouch for an 8051, runs = @ up=20 to 100MIPS). Began with HiTech 8051 C about 8 years ago, but Microchip boug= ht=20 them and dropped it, so we switched to SDCC (free). Recently customer menti= oned=20 it was taking them up to 15 minutes to compile, seems chip was getting clos= e to full.=20 Price checked IAR, they wanted AUD5000. Ported to Keil it builds in 20s and code shrunk by 30-40%. (Actually just u= pgraded=20 my CPU/RAM and now it compiles in 3s~!) Not the flashest IDE, but perfectly= =20 usable... and exceptional value for money~! Well, that's my good news compi= ler=20 story, worth sharing. Even though the above example is not Microchip, it does hint at some of the= =20 reasons their licence change doesn't suit me particularly. I have a handful= of longer=20 term projects that get feature additions now via new firmware. Last compile= r=20 upgrade I did was maybe 6 years ago... no hardware changes in at least that= long. I=20 may well use more (newer) Microchip parts in the future and require a compi= ler=20 upgrade... but that introduces an expiry date ~ and forces into on-going ye= arly=20 updates. Similar happened with Altium Designer... for a couple of years I was using = it a lot=20 fopr some contract work and I could justify, but only just, paying ~USD1000= /yr for=20 upgrades and support. They increased that to ~USD1500/yr and I opted out. T= hen I=20 think they started wanting backdated payments to fill in the gaps if/when o= ne=20 wanted to "resume" support. I waited quite a few years until they had a spe= cial=20 "once only" trade-in offer including 2 years upgardes & support. On 27 Jul 2020 at 23:28, Neil wrote: > I would still be a big proponent of Microchip C if it weren't for XC...=20 > and early Harmony. That was when I was getting into PIC32's. > I still do PIC18's with MPLAB 8.x though >=20 > However, I'm now into ARM. Mostly STM32-flavoured because they offer=20 > significant package/feature choices, and pricing is good. >=20 > Some dev options: > - First Keil and IAR offer their ARM tools free for Cortex-M0/M0+=20 > devices, and for limited code side (IIRC 32K). > - However, a couple years ago, ST purchased Atollic TrueStudio and=20 > offered it for free for any of their processors, and they've now=20 > revised/morphed that into STM32CubeIDE. Yes, it's Eclipse-based, but=20 > pretty decent if you take a moment to learn to use it and workspaces. > - There are surprisingly many other development paths, which I've been=20 > capturing in a flowchart. The latest version is here...=20 > http://orlandorobotbuilders.com/stuff/STM32_Getting_Started-v0_6.png >=20 > ST's discussion forum is disappointing, but feel free to join us on=20 > STM32 Developers FB group, >=20 > Cheers, > -Neil >=20 > On 7/27/2020 10:18 PM, Isaac M. Bavaresco wrote: > > Em 27/07/2020 23:06, Bob Blick escreveu: > >> Might I suggest that, rather than outright revolt, perhaps defection a= s an alternate route? AVR and STM32 are both quite capable... > >> > >> Best regards, Bob > > > > That's what I'm doing. Most of my new projects are using ARM devices. > > > > For now I'm still using Cortex-M3 (SAM3) devices, from Atmel/Microchip. > > If they change their compiler's license policy for ARM devices, then I > > will migrate definitively to STM. > > > > Right now I'm experimenting with STM's Cortex-M7 devices. My RTOS is no= t > > ready for Cortex-M7, but soon I will have to byte the bullet and do the > > conversion. > > > > STM's STM32H7xxx are fantastic devices. Much more powerful than > > Microchip's and still less expensive. --=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 .