{"id":192,"date":"2015-02-24T22:30:07","date_gmt":"2015-02-24T21:30:07","guid":{"rendered":"http:\/\/www.sevenwatt.com\/main\/?page_id=192"},"modified":"2016-01-10T14:19:56","modified_gmt":"2016-01-10T13:19:56","slug":"picos-arm-eclipse-ide-windows","status":"publish","type":"page","link":"https:\/\/www.sevenwatt.com\/main\/picos-arm\/picos-arm-eclipse-ide-windows\/","title":{"rendered":"Picos ARM – Eclipse IDE for projects on Windows"},"content":{"rendered":"

Step by step guide<\/h2>\n

Especially when you are used to an all-predefined, all-inclusive IDE for Arduino, then getting the 32-bit ARM development environment to work can be challenging. It is more involved to get it going, but with this guide and the convenience plug-ins from sevenwatt.com it is definitely doable.<\/p>\n

To setup a fully functional Eclipse IDE we need the following components<\/p>\n

    \n
  1. Compilers and linkers, called the Tool Chain.<\/span><\/li>\n
  2. Make utility that reads scripts (Makefiles) to tell how to compile and link.<\/li>\n
  3. Some core linux commands, that are not standard in Windows.<\/li>\n
  4. Java Runtime Environment.<\/li>\n
  5. Eclipse IDE \u00a0C\/C++ developers.<\/li>\n
  6. The sevenwatt.com Picos ARM Plug-in for Eclipse.<\/li>\n<\/ol>\n

    Items 1, 2 and 3 are normally not a concern on Linux. They are available in the distribution or can be installed as an optional package with one mouse click. Not on Windows. We have to do some more work. At the end of this guide, you have a working Eclipse IDE where you can build an example LPC8xx program.<\/p>\n

    1. Tool Chain<\/h2>\n

    A suitable toolchain is “GNU Tools for ARM Embedded Processors<\/em>“. Go to the download<\/a> site and download the “Windows Installer”form the first listed (most recent) toolchain:<\/p>\n

    \"GNUARMToolchain\"<\/a><\/p>\n

    Run the installer. Select a language (only for installer itself) and press OK<\/strong>, Confirm \u00a0to run the installer by pressing Yes.<\/strong>\u00a0Press Next<\/strong>, and then accept the License, press Next<\/strong>. Install on the default suggested path (do not change), press Next<\/strong>. Press Next<\/strong> once more to start copying and installing files. On the next screen make sure to deselect<\/strong> both “GCCVAR<\/em>” and “Add path to environment variable<\/em>“:<\/p>\n

    \"GNUARMToolchainInstall2\"<\/a><\/p>\n

    Press Finish<\/strong>, Press\u00a0Close<\/strong> on the readme pop-up and the toolchain is installed.<\/p>\n

    2. Make tool<\/h2>\n

    Various make tools for windows are available. A recent version of make (4.1) is available in the “GNU ARM Eclipse Plug-ins” project. Download version 2.3 of the Windows installer from here<\/a>:<\/p>\n

    \"GNUARMMake\"<\/a><\/p>\n

    Run the installer. select a language, and press\u00a0OK<\/strong>. In the installer press\u00a0Next<\/strong>. Accept the licence by press \u00a0I Agree<\/strong>. Remove the check-mark at “Start Menu Shortcuts<\/em>“:<\/p>\n

    \"GNUARMMake2\"<\/a><\/p>\n

    Press\u00a0Next<\/strong>. Install in the default location (do NOT change), and press Install<\/strong>. After the installation completes press\u00a0Finish<\/strong> and the make utility is installed. Do not worry about PATH settings.<\/p>\n

    3. Core\/file utilities (supporting MakeFiles)<\/h2>\n

    Some linux commands need to get installed as some MakeFiles make use of them. Most notably is mkdir (Also built-in in windows but not accessible from make in Eclipse). Embello scripts also use uname. Step2 already provided some commands (rm, echo), but others need to be downloaded from GNUWin Core Utils project<\/a>. This is a direct download.<\/p>\n

    \"GNUCoreUtils\"<\/a><\/p>\n

    Run the installer. Press\u00a0Next<\/strong> in the setup screen. Accept the license and press\u00a0Next<\/strong>. Install in the default location (do NOT change) and press\u00a0Next<\/strong>. Uncheck<\/strong> “Documentation<\/em>“:<\/p>\n

    \"GNUCoreUtils2\"<\/a><\/p>\n

    and press\u00a0Next<\/strong>.\u00a0Install in the default location (do NOT change), and press\u00a0Next<\/strong>. Do NOT select additional tasks and press\u00a0Next<\/strong> again. Finally press\u00a0Install<\/strong>, After the core utils have been installed press\u00a0Finish<\/strong>. Now the additional linux commands are available.<\/p>\n

    4. Java Runtime<\/h2>\n

    Eclipse requires the Jave Runtime Environment (JRE). It may already be installed on a Windows computer. This step can be skipped until it is clear that there is not yet a JRE available.<\/p>\n

    In this setup we are using JRE 8. It can be downloaded from Oracle<\/a>. Select the latest JRE \u00a0(not the SERVER JRE) This is a direct download page for JRE8<\/a>.<\/p>\n

    \"JRE8Download\"<\/a><\/p>\n

    Make sure to select the x86 version marked in orange of the Windows installer. This is the 32-bits version. This is very common, also on 64-bits Windows installations. It is important to select the 32-bits version<\/strong>, as it needs to match with the 32-bits version of eclipse in the next step!<\/p>\n

    5. Eclipse IDE for C\/C++ developers<\/h2>\n

    Eclipse comes in various forms. What we need is eclipse with the C\/C++ extensions. It can be downloaded from the Eclipse download page<\/a>:<\/p>\n

    \"EclipseCDT\"<\/a><\/p>\n

    Make sure to select the\u00a032-bit version<\/strong>\u00a0(marked red) of the “Eclipse IDE for C\/C++ Developers<\/em>” package. It should match the 32-bit version of the JRE of step 4.<\/p>\n

    To install eclipse it only has to be unzipped. This can best be done directly into “C:\\”, due to a possible limitation of the unzip you are using. A folder C:\/eclipse gets created by the unzipping.<\/p>\n

    It depends on your default unzip tool which step to take, but it can be unzipped with Windows Explorer. Select the\u00a0eclipse-cpp-luna-xxxx-win32.zip<\/em> file in explorer. Right-mouse -> Open with -> Explorer -> Extract all files. Enter C:\\ as path, and press\u00a0Extract<\/strong>.<\/p>\n

    \"EclipseUnzip\"<\/a><\/p>\n

    There is no further need to move the unzipped eclipse to another location, but you can do if you dislike programs directly in C:\\<\/em>. The program can now be started by double clicking eclipse.exe in the folder C:\\eclipse<\/em> in an explorer window. For convenience we can first create a desktop short-cut. Select eclipse.exe<\/em> and Right-mouse -> Create Shortcut. Drag the shortcut to the Desktop.<\/p>\n

    6. First run of Eclipse<\/h2>\n

    Eclipse can now be started. Double click eclipse.exe or the Shortcut on the desktop. A dialogue pops that will ask for the workspace. Create C:\\workspace <\/em>and for convenience\u00a0check<\/strong> “Use this as default and do not ask again<\/em>“.<\/p>\n

    \"EclipseFirstRunWorkspace\"<\/a><\/p>\n

    Press\u00a0OK<\/strong>.\u00a0A welcome screen will appear.<\/p>\n

    \"EclipseWelcome\"<\/a><\/p>\n

    Click on \u00a0Workbench<\/strong>\u00a0in the welcome screen. Now we have an empty workbench. It opens up in the so called C\/C++ perspective, as indicated by the blue line in the image below. This will be our regular workbench:<\/p>\n

    \"EclipseFirstRunWorkspace2\"<\/a><\/p>\n

    Now we have to do one final installment before we can build a demo program:<\/p>\n

    7. Picos ARM Eclipse plug-in<\/h2>\n

    The Picos ARM plug-in provides Jeelabs Embello New Project templates for the LPC810, LPC812 and LPC824. (Further templates are planned). The templates provide ready to run settings for compiler and linker, as well as sample code. Next to this the plug-in provides a configuration tool that figures out the paths to the earlier installed utilities. To install the Picos ARM plugins, we have to go to Install New Software in Eclipse.<\/p>\n

    Menu\u00a0Help -> Install New software…<\/strong><\/p>\n

    Press\u00a0Add<\/strong> in upper right corner:<\/p>\n

    \"EclipsePluginAdd\"<\/a><\/p>\n

    Enter Name: Picos ARM Templates and Tools<\/strong><\/p>\n

    Location: \/\/www.sevenwatt.com\/eclipse\/update<\/strong><\/p>\n

    \"EclipsePluginAdd2\"<\/a><\/p>\n

    Press\u00a0OK<\/strong>. Wait a few seconds and\u00a0check<\/strong> “Picos ARM Tools<\/em>“:<\/p>\n

    Press\u00a0Next<\/strong>. Press\u00a0Next<\/strong> once more.\u00a0Accept the license and press Finish<\/strong>. A warning appears indicating that the content of the plugin is unsigned. Press\u00a0OK, <\/strong>you have to trust me on this\u00a0:-). After the software installation is finished, Eclipse proposes to restart before the plug-in gets activated. Press\u00a0Yes<\/strong>\u00a0to restart.<\/p>\n

    After the restart, a new main menu item appeared: “Picos ARM<\/em>“:<\/p>\n

    \"PicosPluginConfigure1\"<\/a><\/p>\n

    Select<\/strong> “Picos Workspace Settings” from this menu. This menu item start searching for the external tools installed in steps 1, 2 and 3. Normally it finds them within a second:<\/p>\n

    \"PicosPluginConfigure2\"<\/a><\/p>\n

    When all three fields are filled, press\u00a0OK<\/strong>. Now the Eclipse IDE is fully set to start developing Jeelabs Embello applications!<\/p>\n

    8. Build a demo program<\/h2>\n

    A dedictated New Project Wizard can be used that shows only the Picos ARM templates:<\/p>\n

    Menu: Picos ARM<\/strong> -> New Picos ARM Project…<\/strong><\/p>\n

    \"PicosNewProject\"<\/a><\/p>\n

    Enter project Name: “HelloLPC” (This name is used in a following step by step guide). Select the (probably default) “Hello World LPC8xx Project<\/em>” Makefile project. Press Next<\/strong>. Enter an Author and press\u00a0Finish<\/strong>. No need to fill in other fields. In the project explorer the “HelloLPC<\/strong>” project appears.<\/p>\n

    Press the build button in the toolbar (the hammer<\/strong>) and within seconds the first firmware is ready:<\/p>\n

    \"PicosBuildProject\"<\/a><\/p>\n

    References<\/h2>\n
      \n
    1. GNU Tools for ARM Embedded Processors<\/a><\/li>\n
    2. <\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

      Step by step guide Especially when you are used to an all-predefined, all-inclusive IDE for Arduino, then getting the 32-bit ARM development environment to work can be challenging. It is more involved to get it going, but with this guide and the convenience plug-ins from sevenwatt.com it is definitely doable. To setup a fully functional […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":186,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-192","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/pages\/192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/comments?post=192"}],"version-history":[{"count":16,"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/pages\/192\/revisions"}],"predecessor-version":[{"id":591,"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/pages\/192\/revisions\/591"}],"up":[{"embeddable":true,"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/pages\/186"}],"wp:attachment":[{"href":"https:\/\/www.sevenwatt.com\/main\/wp-json\/wp\/v2\/media?parent=192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}