Preferred toolchain for FRDM-K28F board?

[fastwalker2]

Hi All,

I have a new FRDM-K28F board.  I am looking for an IDE that will allow setting of breakpoints and single step debugging (e.g. something Eclipse based) and a toolchain that will also allow CLI driven development of C code using Makefiles.

Can anyone suggest the best set of tools to achieve the above?  I've just downloaded MCU Expresso and wanted to try out a quick "hello world" demo, but when I click on "New Project" only the LPC based boards are listed.  I was hoping to load some ready to go samples for my FRDM board.

On a higher level, since the NXP takeover should I be looking at using NXP chips now instead of Freescale?  I have a new design coming up and there's nothing at this point locking me into a particular vendor.  If support on the software side is going to focus mainly on NXP chips then it'd prob. make sense to just focus on that silicon from now on?

Thanks,

Sean

[mjbcswitzerland · Accepted solution]

Hello Sean

For MCUXpresso see the following: https://community.nxp.com/thread/474390

Also take a look at http://www.utasker.com/kinetis/FRDM-KL28Z.html

The uTasker KL28 project includes complete projects for most IDEs:
    NXP's MCUXpresso
    NXP's Kinetis Design Studio (KDS)
    Freescale's CodeWarrior 10.x
    S32 Design Studio for ARM
    Rowley Associate's Crossworks
    CooCox CoIDE
    IAR Embedded Workbench
    Keil µVision
    Green Hills
    Atollic TrueSTUDIO for ARM
    Standalone GCC from Makefile
    VisualStudio for Kinetis simulation

and allows complete project simulation (including peripherals, interrupt, DMA etc.) and CGG make file building directly from Visual Studio.

Beware however that the KL28 presently has a lead time of about 40 weeks so you will may need to keep your options open if you need to produce fast turnaround developments.

"NXP = Freescale" so there is no general problem with Kinetis parts (NXP is, or will be, Qualcomm - and Broadcom is also biding on Qualcomm, so best close your eyes if stability is an input to your choice of silicon)

Regards

Mark

uTasker developer and supporter (+5'000 hours experience on +60 Kinetis derivatives in +80 product developments)
Kinetis: http://www.utasker.com/kinetis.html