>ARM is ARM, just use GCCSure, unless you need any peripherals or documentation. ;) Cheers Phil Hobbs
Nice MCU for small jobs
Started by ●September 3, 2018
Reply by ●September 3, 20182018-09-03
Reply by ●September 3, 20182018-09-03
>the question I'm unsure of is whether you can use those NXP ARMs with >the toolchain of your choice or if they lock you in to their >LXCNEXpressor C-only/128k limit toolchain (for the free version) somehowThe Code Red tools are modern C++ (g++) and are free up to 256k.IIRC the full version is another $256, gasp. NXP supplies sample code for Keil and IAR as well. Cheers Phil Hobbs
Reply by ●September 3, 20182018-09-03
On 09/03/2018 08:36 PM, pcdhobbs@gmail.com wrote:>> the question I'm unsure of is whether you can use those NXP ARMs with >> the toolchain of your choice or if they lock you in to their >> LXCNEXpressor C-only/128k limit toolchain (for the free version) somehow > > The Code Red tools are modern C++ (g++) and are free up to 256k.IIRC the full version is another $256, gasp. > > NXP supplies sample code for Keil and IAR as well. > > Cheers > > Phil Hobbs >I see, is that how they gitcha? The datasheet doesn't seem to actually tell you all the magic steps/registers/memory locations you need to write bits to to configure the peripherals as you like, it's built-in to their compiler. So it'd be difficult to just say whip up some asm by hand and drop the binary on it and have it actually do anything. I've gotten spoiled using IDE plug-in for the OSS compilers that compile on-the-fly and show you errors and warnings as you type, the actual asm that will be generated highlighted and line-by-line cross referenced to your high-level code, and immediate cycle count estimates for functions
Reply by ●September 3, 20182018-09-03
pcdhobbs@gmail.com wrote...> > The LPC M4s are cheaper than their M3s, and have > more interesting package optionsI'm partial to the Atmel ATSAMD21, a 48MHz M0+, in a 32TQFP package. I like 0.8mm instead of 0.65mm lead spacing, 40 rather 67 cents in reels. -- Thanks, - Win
Reply by ●September 3, 20182018-09-03
On Mon, 3 Sep 2018 13:25:05 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:>LPC804: 15 MHz Cortex M0+, 32kB flash, 4k RAM, 12-bit 2 us ADC with 1 >LSB DNL, 10-bit DAC, the usual serial stuff, 20-TSSOP: 67 cents in >reels, dev board $27.<https://www.digikey.com/product-detail/en/stmicroelectronics/STM32F030F4P6TR/497-17333-2-ND/4755941> $0.55>We're using it for a super-quiet diode laser controller where it will >run the temperature control and automatic power control loops. I'll >never use another ATmega. ;)A Pic with hardware PID controllers sounds like a winner for this application.
Reply by ●September 3, 20182018-09-03
tirsdag den 4. september 2018 kl. 02.56.51 UTC+2 skrev bitrex:> On 09/03/2018 08:36 PM, pcdhobbs@gmail.com wrote: > >> the question I'm unsure of is whether you can use those NXP ARMs with > >> the toolchain of your choice or if they lock you in to their > >> LXCNEXpressor C-only/128k limit toolchain (for the free version) somehow > > > > The Code Red tools are modern C++ (g++) and are free up to 256k.IIRC the full version is another $256, gasp. > > > > NXP supplies sample code for Keil and IAR as well. > > > > Cheers > > > > Phil Hobbs > > > > I see, is that how they gitcha? The datasheet doesn't seem to actually > tell you all the magic steps/registers/memory locations you need to > write bits to to configure the peripherals as you like, it's built-in to > their compiler. So it'd be difficult to just say whip up some asm by > hand and drop the binary on it and have it actually do anything.that is almost never in the datasheet for MCUs, you need the usermanual https://www.nxp.com/docs/en/user-guide/UM11065.pdf
Reply by ●September 3, 20182018-09-03
tirsdag den 4. september 2018 kl. 03.31.47 UTC+2 skrev k...@notreal.com:> On Mon, 3 Sep 2018 13:25:05 -0400, Phil Hobbs > <pcdhSpamMeSenseless@electrooptical.net> wrote: > > >LPC804: 15 MHz Cortex M0+, 32kB flash, 4k RAM, 12-bit 2 us ADC with 1 > >LSB DNL, 10-bit DAC, the usual serial stuff, 20-TSSOP: 67 cents in > >reels, dev board $27. > > <https://www.digikey.com/product-detail/en/stmicroelectronics/STM32F030F4P6TR/497-17333-2-ND/4755941> > > $0.55that only has half the flash
Reply by ●September 3, 20182018-09-03
On 3 Sep 2018 18:24:32 -0700, Winfield Hill <hill@rowland.harvard.edu> wrote:>pcdhobbs@gmail.com wrote... >> >> The LPC M4s are cheaper than their M3s, and have >> more interesting package options > > I'm partial to the Atmel ATSAMD21, a 48MHz M0+, > in a 32TQFP package. I like 0.8mm instead of > 0.65mm lead spacing, 40 rather 67 cents in reels. >The SAM D21 is a lot more expensive in Hobbs' quantities. I prefer the QFN package over the TQFP, though.
Reply by ●September 3, 20182018-09-03
On Mon, 3 Sep 2018 18:35:00 -0700 (PDT), Lasse Langwadt Christensen <langwadt@fonz.dk> wrote:>tirsdag den 4. september 2018 kl. 03.31.47 UTC+2 skrev k...@notreal.com: >> On Mon, 3 Sep 2018 13:25:05 -0400, Phil Hobbs >> <pcdhSpamMeSenseless@electrooptical.net> wrote: >> >> >LPC804: 15 MHz Cortex M0+, 32kB flash, 4k RAM, 12-bit 2 us ADC with 1 >> >LSB DNL, 10-bit DAC, the usual serial stuff, 20-TSSOP: 67 cents in >> >reels, dev board $27. >> >> <https://www.digikey.com/product-detail/en/stmicroelectronics/STM32F030F4P6TR/497-17333-2-ND/4755941> >> >> $0.55 > >that only has half the flashHow much is needed? Let me guess. You're a programmer? ;-)
Reply by ●September 3, 20182018-09-03
On 09/03/2018 09:32 PM, Lasse Langwadt Christensen wrote:> tirsdag den 4. september 2018 kl. 02.56.51 UTC+2 skrev bitrex: >> On 09/03/2018 08:36 PM, pcdhobbs@gmail.com wrote: >>>> the question I'm unsure of is whether you can use those NXP ARMs with >>>> the toolchain of your choice or if they lock you in to their >>>> LXCNEXpressor C-only/128k limit toolchain (for the free version) somehow >>> >>> The Code Red tools are modern C++ (g++) and are free up to 256k.IIRC the full version is another $256, gasp. >>> >>> NXP supplies sample code for Keil and IAR as well. >>> >>> Cheers >>> >>> Phil Hobbs >>> >> >> I see, is that how they gitcha? The datasheet doesn't seem to actually >> tell you all the magic steps/registers/memory locations you need to >> write bits to to configure the peripherals as you like, it's built-in to >> their compiler. So it'd be difficult to just say whip up some asm by >> hand and drop the binary on it and have it actually do anything. > > that is almost never in the datasheet for MCUs, you need the usermanual > > https://www.nxp.com/docs/en/user-guide/UM11065.pdf >I can see why one might want to pay for the macros.
