Hi, I am new to ARM and Open OCD, etc.
I have been working through the jlynch tutorial:
“Using Open Source Tools for SAM7 Cross Development”
I have done everything twice on two computers (one XP and the other 2000)
with the same results.
The Problem…
When I click the build button, nothing happens. The Console window show nothing. The Problem window shows the following:
Error launching external scanner info generator (gcc -E -P -v -dD E:/Data/workspace/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c) demo_at91sam7_blink_flash Unknown 1184344845783 0
And that’s is it. No other clue as to what is going on.
Any Ideas?
Hi Tim.
For starters, make sure you have the very latest JAVA runtime installed on your computer. The latest version of YAGARTO requires this.
Go to the Sun web site and download the very latest version they have.
Let uo know what happens.
Jim Lynch
Hello Jim Lynch,
Yes I did install the latest JAVA. I did everything exactly spelled out in your document “Using Open Source Tools for SAM7 Cross Development”. Apperently this document is not complete because I did some more searching and I found a document on the ATMEL website “doc6310.pdf” entitles “GNU-Based Software Development on AT91SAM Microcontrollers”. In this document, it says to change the “Discovery Options” tab setting “Compiler invocation command” from “gcc” to “arm-elf-gcc”. Your document mentions nothing about this. Now when I do a “clean” (or a “build” for that matter) I get a “make: Error – Configuration file `/etc/startup.mk’ not found” message in the console window.
I tryed the same procedure spelled out in “Using Open Source Tools for SAM7 Cross Development” on my home computer. Until I changed the setting from “gcc” to “arm-elf-gcc”, it did not compiled. But now my home computer does compile but only when I do a “clean”. When I do a regular “build” it does not compile.
My computer here at work still does not compile with this “startup,mk not found” error as discribed above.
I have downloaded the eclipts CDT user’s guild “http://dev.eclipse.org/viewcvs/index.cg … ls_Project” as referenced in your document. This document does not explain the make process in much detail. I was not able to figure out how eclipse runs make files or how it uses “scanner info commands” in conjunction with make files or why it is even asking for a startup.mk file. Is there any documents that detail why/how eclipse deals with make files?
I have limited experiance with make files. Most compilers I have used in the past setup these details for me and I never have to deal with them.
Thank Jim,
Regards,
Tim Avalon
Micro Systems Engineering Inc.
6024 SW Jean Road
Lake Oswego OR 97035
tim.avalon@biotronik.com
Hi Tim.
Some people who’ve had this problem have resolved it by doing the following:
Go to the Project Properties and then select “C/C++ Make Project”.
There go to the tab “Discovery options” and disable the last check box (“Enable generate scanner info command”).
In my setup, I do not have to set the “Compiler Invocation Command” to arm-elf-gcc. In fact, I’ve taken the defaults on the whole “Properties” setup and it still compiled OK. You may notice that the arm-elf-gcc compiler is selected in the make file. When you select the “Build” button, it calls make.exe which uses the default file makefile (no extension). The “Build” button does a “make all” which will compile only those files whose source is “newer” than the object file.
When you do a “Clean”, it runs the make utility first with a “make clean” which erases all the objects, followed by a “make all” which will have to compile everything since the source files are newer than a non-existent object file.
My guess is that you are not “saving” your source files when you make an editing change. Be aware that changes to the editing window effect the source file only when you hit the “save” button. forgetting to save will cause the make facility to run its timestamp comparison with old files and potentially elect not to compile.
You can set Eclipse to “save” all files before compiling. This setting is under “Windows - Preferences - General - Workspace”.
Cheers,
Jim Lynch
I found the problem…
MKS (a source integrety client program) also puts a make utility in the path so when I was running the build, it was running the wrong make.exe program. I just deleted the MKS make.exe file and all works now.
