element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Energy Harvesting Design Challenge
  • Challenges & Projects
  • Design Challenges
  • Energy Harvesting Design Challenge
  • More
  • Cancel
Energy Harvesting Design Challenge
Blog A Very Compact Guide to Energy Harvesting - Part 009
  • Blog
  • Forum
  • Documents
  • Files
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: COMPACT
  • Date Created: 2 May 2013 9:09 PM Date Created
  • Views 402 views
  • Likes 1 like
  • Comments 0 comments
  • energy_harvesting
  • energy_harvesting_challenge
Related
Recommended

A Very Compact Guide to Energy Harvesting - Part 009

COMPACT
COMPACT
2 May 2013

What's in a Name?

Previously in Part 007 (I'm feeling so remote) I described a procedure to take the STK3700 blink example and use it for a new project.

In it I mentioned that the its references to the work blink could be changed to a word of your choice.

These procedures are for use with IAR Embedded Workbench for ARM.

 

A bit like Fermat's Last Theorem I could not fit this procedure in the margins so here it is as a separate post.

 

I hope you find that both of these procedures will help you with using your Energy Harvesting to Go Kit.

 

Renaming an IAR Workbench Workspace and Project for EFM32 from the STK3700 Blink Example

Like my procedure I formulated to use the Blink example as a template this procedure has been tested.

image This procedure must be followed in stipulated order to accomplish the desired result.

 

 

From the ..\IAR  folder of the copied and renamed Blink example project;
1. Open Windows Explorer and from it;
   a. Rename blink.eww as <yourchoice>.eww
   b. Delete the blink.dep, blink.ewd files

 

image .eww files are IAR Embedded Workbench Workspace files.

 

 

2. Launch IAR Embedded Workbench and open <yourchoice>.eww by double clicking <yourchoice>.eww. From it;
   a.  From workspace, right-click and remove from workspace
   b.  Confirm removal

 

 

3. From Windows Explorer;
   a. Rename blink.ewp as <yourchoice>.ewp
   b. Delete the settings folder

 

image .ewp files are IAR Embedded Workbench Project files.

 

 

4. From IAR Embedded Workbench;
   a. (Menu)Project, Add existing project add, choose <yourchoice>.ewp
   b. Right click your project, options,
   c. General Options, Output (tab) - change the 3 occurences of blink to <yourchoice> leaving the remainder of the path unchanged (it is best to match your .eww name) for;
     i.   Executables/libraries
     ii.  Object files
     iii. List files
   d. Output Converter, Output file - change blink to <yourchoice> leaving the remainder of the existing text value intact.
   e. Linker, Output filename - change blink to <yourchoice> leaving the remainder of the existing text value intact.
   f. Debugger, Setup, Driver - Select J-Link/J-Trace
   g. Click OK to accept changes.

  
5. From Windows Explorer;
   a. Remove the blink folder

 

 

6. From IAR Embedded Workbench;
   a. (menu)File, Save Workspace

 


Now if all the above has been completed correctly the project is ready to "Download and Debug" as <yourchoice> (and all unwanted files and folder are removed) but with the original blink.c as the source code.

To change this and use your own .c source code file.

 

Here is the procedure just to rename blink.c as <yourchoice>.c and include it in the project

7. From IAR Embedded Workbench;

   a.  From Workspace tree, Source group, right-click and remove blink.c

 

 

8. Assuming you want to use blink.c but want to rename it.

   From Windows Explorer;

   a. Rename blink.c as <yourchoice>.c

image The .c file is in the same folder as the .../IAR folder

 

 

9. From IAR Embedded Workbench;

   a. From Workspace tree, Source group, right-click and add, add existing file, choose <yourchoice>.ewp

 

Now your project and workspace is devoid of all references to blink.

  • Sign in to reply
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube