I tent to use low end STM32 processors (ie. STM32F030, STM32F103), the Keil
MDK-ARM toolchain, and the standard $20 ST-link programmer.

The only downside to the ARM is increased complexity. But, generally it is
worth it when comparing the cost, processing power, and relative ease of
development.

The main advantage of the commercial tool suits over command-line GCC is
that debugging is a whole lot easier (I've done plenty both ways).
Although, for me building up a minimal linker script and make-filestaught
me a lot about the compilation process that was helpful later on.

On Mon, May 9, 2016 at 6:05 PM, James Cameron <quozl@laptop.org> wrote:

> On Mon, May 09, 2016 at 01:43:09PM -0400, Neil wrote:
> > Just checking.  Care to share a bit about what chips/tools/etc
> > you're using?
>
> IDE and compiler tool chain is; emacs, ino, python, forth, git, make, gcc=
..
>
> Rest of answer split by project phase.
>
> In sustaining engineering, with;
>
> - Open Firmware Forth to test in production and load Linux on Marvell
>   PXA2128 ARMv7 MP,
>
> - CForth for Freescale MK20DX256 ARM Cortex-M4.
>
> For new projects, waiting for a cheap carrier board with an ARM,
> perhaps with Mbed.  Price point about $15 at qty 10.
>
> While waiting, my other platforms are ATtiny85, Arduino Pro Mini,
> ESP8266 ESP-01, ESP-12.  The latter in Lua.
>
> For old PIC projects, finding the tool chains costly to bring forward,
> so spare PICs are sitting in component draws.  Almost all over ten
> years old.
>
> --
> James Cameron
> http://quozl.netrek.org/
> --
> 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
Jason White
--=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
.