Using to Eclipse instead Atmel studio.

Go To Last Post
16 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

First of all, I'd like to apologize asking ARM question in AVR forum but it seems like the only place with knowledge in Atmel studio...

I'm currently work with one of Atmel's old demo application using Atmel studio 7.0 with sam-avr, the demo application is for both AVR and ARM (SAM20/21) and I'm working with ATSAMD51J20.

I found the IDE not very comfortable for working, we mainly work with Eclipse and I'd like to work too with that environment. I've already asked couple of weeks ago in Eclipse Community Forums (Home » Language IDEs » C / C++ IDE (CDT) » Problems using tool-chain for ATMEL chips) but didn't got an answer.

 

1. Is there a plugin for the ATMEL projects (*.cproj,*.atsln ) that can convert the ATMEL projects to Eclipse format? I've found something called 'de.innot.avreclipse.p2repository-2.4.2.zip' but it's seems it's for AVR chips because the compiler/linker aren't the one in the AtmelStudio folder.
2. How to set correctly the ATMEL tool chain in Eclipse for working with ARM processor? 

3. How can I select ATMEL tool chain manually in an imported project? Currently I've tried the GNU tool chain (with Cross GCC and cygwin using CDT builder) with no success. Somehow it seems the Eclips can't find the tool chain in the AtmelStudio folder, no meter what I tried.

4. Can a JLink can be use instead the sam-avr?

 

Thanks in advance,

Haim.

 

Last Edited: Mon. Aug 10, 2020 - 10:07 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Do yourself a favour and use PlatformIO - is does all the hard work of configuration for you. Not Eclipse, sorry.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Improve your search engine results by using this search term:

eclipse cross compiler prefix

 

I have done this myself when I did an ARM project but that was in a different life and I've forgotten the details.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the advice but actually I'm trying to reduce the number of tools I'm using...

Being in the field (embedded systems) for so long I've use most of the existing tools, the major advance of the Eclipse is that the same IDE can run many different tool chains while keeping UI compatibility.

 

Also, here we (trying to...) to work with a single echo-system for both PC and embedded codes, that is why we all use the Eclipse.  

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks, I've tried eclipse cross compiler prefix and got many of the results I've tried before. In the Eclips forum I've already visited the link (https://www.eclipse.org/forums/index.php/t/1088102/), it didn't help much because it from 2014...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

2014 stuff should still be applicable, perhaps you're being too selective.

 

My top link looks useful:

https://www.codeguru.com/cpp/cpp/getting-started-with-c-for-eclipse.html

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I am sure that Eclipse works.   And if you are comfortable with Eclipse,  it is very wise to stick with one IDE.

 

Personally,   I am not a masochist.    NXP and ST both have Eclipse IDEs.   They make my head hurt.   They are both horrible.

 

As a hobbyist,  I am much happier with a hobbyist licence for Rowley CrossWorks.   It is not expensive.

I only have free "evaluation" version of Keil MDK5

If I was a professional,  I would buy a full licence for Keil or Rowley without hesitation.

 

It is not worth your employer's time and money to mess around with bad tools.

If self-employed it is your time and money.   (unless you enjoy it)

 

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

2014 stuff does not work, when I try to execute it I got stuck in an option that was inactive no meter what I tried.

N.Winterbottom tanks, I'll try it tomorrow (I think I've already done it last month but I'm not sure) 

David, you right. I'm not a hobbyist (actually I do some stuff at home for fun...) but an embedded engineer. But the company is not going to buy a full licence for IAR, they prefers the free tools like Visual Studio + GCC. I don't mind using the GCC but at least give some normal IDE tool, not the annoying Visual Studio.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have you looked at this MC page: https://www.microchip.com/mplab/...

 

 

(Possum Lodge oath) Quando omni flunkus, moritati.

"I thought growing old would take longer"

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Haim wrote:

David, you right. I'm not a hobbyist (actually I do some stuff at home for fun...) but an embedded engineer. But the company is not going to buy a full licence for IAR, they prefers the free tools like Visual Studio + GCC. I don't mind using the GCC but at least give some normal IDE tool, not the annoying Visual Studio.

Seriously,   your employer should buy IAR if it enhances your productivity.

Especially if all the other employees would benefit.

IAR cover a wide range of chips e.g. AVR, Renesas, ARM, ...    Keil only do ARM, 8051.

 

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Sorry if I missed the operating system you use. If you are using windows (my guess since you mention AVRStudio),  you might want to look at https://protostack.com.au/2010/1... .  In the middle, after the section " For some reason the AVR Eclipse plugin doesn’t always detect paths properly. The next few steps describe how to remedy this problem " he gives instructions to set up Eclipse paths to tools.  It might give you a hint about how to setup Eclipse for your ARM Plugin.

 

good Luck,

Alan

 

Added: 

Just for my information, what plugin are you using?

Although looking at this site https://mcuoneclipse.com/ is like drinking from a fire hose, I found a lot of helpful suggestions about using Eclipse more effectively.

Last Edited: Mon. Aug 10, 2020 - 02:15 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Its called "AVR Eclipse Plugin    2.4.2    de.innot.avreclipse.feature.group    avr-eclipse.sourceforge.net" according to Eclipse IDE installation Details.

The operating system is windows 10.

Thanks for the link, due to the work load I won't be able to continue this week. Hopefully, I'll try it next week... 

 

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Still having problems... First of all, the AVR plug is for the AVR Chips (as is name hint...), not the ARM.

 

In the Eclipse I've selected toolchain to be Cross GCC.

The builder to be GNU make/CDT Internal builder/GNU make builder. (I've installed the mingw)

 

*While using the Atmel studio the IDE use "C:\Program Files (x86)\Atmel\Studio\7.0\toolchain\arm\arm-gnu-toolchain\bin\arm-none-eabi-gcc.exe" for the compiler

*While using the Eclipse the IDE use          gcc -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"Top/EgmEmbedded.d" -MT"Top/EgmEmbedded.o" -o "Top/EgmEmbedded.o" "C:/Proj/Testing/EgmEmbedded.c" for the compiler
The Eclipse fail using the correct compiler "Cannot run program "gcc": Launching failed"

 

 

How to set it right in the Eclipse? 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Not sure how much I can help.  I have an old configuration (mostly around 2014) using the Eclipse AVR plugin running on Windows XP for the non-X AVR controllers.

 

Did the Protostack link I posted help at all?  It is a step by step guide using (an older) ATMEL tool chain in the example.   Tomorrow, I will take a couple of screen shots of the Eclipse's configuration dialogs for Cygwin and WinAVR tools.  You might be able see how the configuration dialogs point to their respective tools.

 

Have you placed the folder name for your tool chain's executables in your window's path?

 

I do question the wisdom of investing time into configuring tools for AVR controllers when you intend to use Eclipse to develop SW for ARM.  I did a search for "Eclipse ARM Plugin" and found a couple of ARM plugins which are more up to date than the avr plugin we have.

 

Alan

Last Edited: Mon. Aug 17, 2020 - 12:12 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

 

Haim wrote:

 

In the Eclipse I've selected toolchain to be Cross GCC.

The builder to be GNU make/CDT Internal builder/GNU make builder. (I've installed the mingw)

 

*While using the Atmel studio the IDE use "C:\Program Files (x86)\Atmel\Studio\7.0\toolchain\arm\arm-gnu-toolchain\bin\arm-none-eabi-gcc.exe" for the compiler *While using the Eclipse the IDE use          gcc -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"Top/EgmEmbedded.d" -MT"Top/EgmEmbedded.o" -o "Top/EgmEmbedded.o" "C:/Proj/Testing/EgmEmbedded.c" for the compiler
The Eclipse fail using the correct compiler "Cannot run program "gcc": Launching failed"

 

Eclipse appears to want to use the cygwin/mingw gcc compiler and cannot find it.   For what ever toolchain you use, you will want to put the name of its folder of executables in your windows Path:  Mine is set up as follows: C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\cygwin\bin;c:\doxygen;c:\graphviz\release\bin   The WinAVR  entry is for AVR tools while the cygwin entry is for Eclipse's CDT.  In Windows XP,  the path can be found in My Computer, System Properties, the Environment Variables button.  When open, the Path is under System variables

 

When in Eclipse, I assume you will want to use the Atmel compiler I highlighed above.  When in Eclipse, you would have to open the Windows -> Preferences dialog and select AVR -> Paths.  The following dialog will open

 

 

Select the AVR-GCC entry, press the Edit key to the right side of the dialog, browse to the ATMEL tool-chain bin directory, and select the folder where arm-none-eabi-gcc.exe resides.   If you want to use a different compiler (i.e. Cross, sam-avr), then navigate to the executables folder of that tool-chain and select it.  Repeat this procedure for the other tools in the list.  Again, what I have shown above applies to the avr-eclipse plugin, I'm not sure what you will see in Windows 10 for ARM controllers and their associated plugins.

 

And BTW, since you are using an avr plugin, it expects to see avr-gcc, avr-gdb, etc executables, not just gcc (which is most likely the PC's Cygwin version).

 

Hope this information gives you some general direction to solve your problem. I'll check later for your response since you said you are busy with work. 

Alan

Last Edited: Wed. Aug 19, 2020 - 12:42 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Did you have success with any plugin?