It seems after installing IAR plugin there’s problem with JavaNullException Error when i try to make new Kientis project. But using 64bit binaries on a 64bit machine is preferred. I planned to collect some numbers and publish them. >Just wondering … have you actually benchmarked 32 v 64 bit tools and, if so, is there really that much of a performance difference? But given that both P&E and Segger work like a charm and are free-of-charge on the FRDM boards, why wasting time with OpenOCD?
I have used 0.8.0, so things might be better with 0.9.0. I’m not using OpenOCD because it never worked out well for me (slow, buggy, nearly unusable). >FWIW I’m still on Luna/CDT 8.6 and use OpenOCD for debugging in case that makes a difference? But I usually always disable that option because installation takes a very long time or even can fail because of this. There might be cases where this is not necessary, probably if you select ‘contact/check all update sites’. So I had to install it, and so I documented this step. I tried to install the GNU ARM Eclipse plugins on ‘plain’ Mars C/C++ package, and it failed to install all the debugging support. and have no problem building and debugging without installing anything extra from the Eclipse CDT update site such as “C/C++ GDB Hardware Debugging”. Eclipse + CDT) from the Eclipse site and then install the GNU ARM Eclipse plugins and the GCC ARM Embedded etc. >Are you sure about that? I always download the Eclipse IDE for C/C++ Developers (i.e. Previous article series how to build a DIY IDE: DIY Free Toolchain for Kinetis: Part 1 – GNU ARM Build Tools.GNU ARM Eclipse build tools on SourceForge:.GNU ARM Eclipse plugins on SourceForge:.And knowing what I do is always a good thing :-). While it takes a little time at the beginning to do such an IDE and tool chain setup, it is very valuable afterwards because I *understand* what I have, and where I have it. Of course it does not stop here: I will add many more plugins: FreeRTOS kernel awareness, static source analysis, doxygen, version control system, …Ĭompared to distributions from vendors like Freescale (Kinetis Design Studio), I have full flexibility: I don’t have to wait for new releases to get a bleeding edge tool chain. Best of all: I have all the packages available so I can repeat the installation again, or simply put my current IDE layout into an archive and use it on another machine.
It only requires to download and install a few standard packages. With this, I have constructed my own DIY IDE to develop application for ARM Cortex based devices. For this, install the EmbSysReg Viewer, see “ Freescale CMSIS-SVD Register Files with Eclipse MARS and EmbSysRegView“. What is missing is a nice way to inspect the device peripheral registers. Now I have pretty much replicated what is in Kinetis Design Studio v3.0.0, but using my DYI Eclipse IDE :-). At the time of this article, the latest release is ‘Mars’ Go to and download ‘Eclipse IDE for C/C++ Developers’ for your operating system. Freescale only: Freescale New Project Wizard, Processor Expert and Kinetis SDK.Debugging: Segger J-Link and/or P&E Multilink.Build tools: GCC ARM Embedded (launchpad) from and.GNU ARM Plugins: GNU ARM Eclipse plugins from.IDE: Eclipse IDE and C/C++ CDT tools from.I’m going to build my toolchain with the following parts: GNU ARM Eclipse with better tool integration: I can use the latest GNU ARM Eclipse plugins (see this discussion).Eclipse CDT 8.7 with new multicore features.KDS uses 32bit Eclipse, I can use the 64bit Eclipse version which has better performance. It only takes about 30 minutes to get it done, but at the end I have something which can be used as IDE for multiple vendors.įor the ones of you using the Freescale Kinetis Design Studio (KDS v3.0.0), it gives the following advantages: Compared to vendor provided tools like Freescale’s Kinetis Design Studio or NXP’s LPCXpresso it requires to download and install several packages. The goal is to build a custom Eclipse IDE and toolchain which can be used to create/build/debug ARM Cortex M based devices. See for a list of steps and additional hints/information. UPDATE: after writing that post, a few things have been changed.