Hello,
I need to develop in my Diploma Thesis an application with a LPC2129, so
I decided to install WinARM (I have read that in the Thesis that I have
to continue with it).
I have installed all and I have download an example...I have tried to
compile it, but it doesn't work.
I have found this page
http://www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/ and I have
added the needed path variables. But it doesn't still work. The error
message is:
> "make" main_CANAll.c> Failed to create process: El sistema no puede encontrar el archivo especificado.> Process Exit Code: 0> Time Taken: 00:00
Thank you in advance!
Nazandy Perez wrote:
>> "make" main_CANAll.c>>> Failed to create process: El sistema no puede encontrar el archivo
especificado.
Spanish(?), please translate into English.
make xzy.c may not be an a valid make target, check the makefile. Did
you try make all?
Is the package unpacked into C:\WinARM? (do not unpack into the
%ProgramFiles%, AFAIK there is some "magic" in Vista to "vitualize" this
directory)
Check if the path to the build-tools is in the system-search path
(C:\WinARM\utils\bin).
Output of make --version and arm-elf-gcc --version ?
If the code does not depend on the
"newlib-reentrant-syscalls"-configuration as in WinARM 6/2006 you can
use the latest Yagarto package. There should be no "path-tricks" needed
for Vista.
Excuse but I didn't have realised that there was something in Spanish...
Failed to create process: El sistema no puede encontrar el archivo
especificado.
in English: Failed to create process. The system can't find the specific
file.
Thank you
Martin Thomas wrote:
> Nazandy Perez wrote:>>> "make" main_CANAll.c>>>>> Failed to create process: El sistema no puede encontrar el archivo
especificado.
>> Spanish(?), please translate into English.>> make xzy.c may not be an a valid make target, check the makefile. Did> you try make all?>> Is the package unpacked into C:\WinARM? (do not unpack into the> %ProgramFiles%, AFAIK there is some "magic" in Vista to "vitualize" this> directory)>> Check if the path to the build-tools is in the system-search path> (C:\WinARM\utils\bin).>> Output of make --version and arm-elf-gcc --version ?>> If the code does not depend on the> "newlib-reentrant-syscalls"-configuration as in WinARM 6/2006 you can> use the latest Yagarto package. There should be no "path-tricks" needed> for Vista.
WinARM 20060606 is based on GCC 4.1.0 or 4.1.1 isn't it?
You need at least GCC 4.1.2 to work with Vista. I don't remember if
thats the error message I got before upgrading to 4.1.2, but I do know
that you will have to do it at some point to get it to compile properly.
Martin Thomas wrote:
>> Is the package unpacked into C:\WinARM? (do not unpack into the> %ProgramFiles%, AFAIK there is some "magic" in Vista to "vitualize" this> directory)>> Check if the path to the build-tools is in the system-search path> (C:\WinARM\utils\bin).>> Output of make --version and arm-elf-gcc --version ?>
What is the answer of thoses question ?
That can help us to help you
Jonathan
In C:\WinARM\utils\bin there are some applications files: make, mkdir,
cp, echo, rm, sh, sed_winARM and terminal.
I think the version of my gcc is 4.1.1. I don't know if I need at least
4.1.2...
Thank you very much
Jonathan Dumaresq wrote:
> Martin Thomas wrote:>>>> Is the package unpacked into C:\WinARM? (do not unpack into the>> %ProgramFiles%, AFAIK there is some "magic" in Vista to "vitualize" this>> directory)>>>> Check if the path to the build-tools is in the system-search path>> (C:\WinARM\utils\bin).>>>> Output of make --version and arm-elf-gcc --version ?>>>> What is the answer of thoses question ?>> That can help us to help you>> Jonathan
I have installed a new version WinAVR-20080512, I think it is the last
avaible. The version of the gcc is 4.3.0. I have checked that in
C:\WinAVR-20080512\utils\bin there are a lot of applications files:
make, mkdir, date, etc.
And now when I try to compile the same project I find another error:
> "make.exe" all
makefile:227: *** missing separator. Stop.
> Process Exit Code: 2> Time Taken: 00:01
Theoretically this project was compiled and the makefile I supposed that
it is correct. The makefile is:
225 # Eye candy.
226 begin:
227 @echo
228 @echo $(MSG_BEGIN)
229
230 finished:
231 @echo $(MSG_ERRORS_NONE)
232
233 send:
234 @echo $(MSG_END)
235 @echo
Thank you!
Nazandy Perez wrote:
> In C:\WinARM\utils\bin there are some applications files: make, mkdir,> cp, echo, rm, sh, sed_winARM and terminal.>> I think the version of my gcc is 4.1.1. I don't know if I need at least> 4.1.2...>> Thank you very much>> Jonathan Dumaresq wrote:>> Martin Thomas wrote:>>>>>> Is the package unpacked into C:\WinARM? (do not unpack into the>>> %ProgramFiles%, AFAIK there is some "magic" in Vista to "vitualize" this>>> directory)>>>>>> Check if the path to the build-tools is in the system-search path>>> (C:\WinARM\utils\bin).>>>>>> Output of make --version and arm-elf-gcc --version ?>>>>>>> What is the answer of thoses question ?>>>> That can help us to help you>>>> Jonathan
Nazandy Perez wrote:
> I have installed a new version WinAVR-20080512, I think it is the last> avaible. The version of the gcc is 4.3.0. I have checked that in> C:\WinAVR-20080512\utils\bin there are a lot of applications files:> make, mkdir, date, etc.
O.k. so you are using the tools from WinAVR with the GNU arm-toolchain
from a WinARM package. This should work.
>> And now when I try to compile the same project I find another error:>>> "make.exe" all> makefile:227: *** missing separator. Stop.>>> Process Exit Code: 2>> Time Taken: 00:01>> Theoretically this project was compiled and the makefile I supposed that> it is correct. The makefile is:
IRC WinAVR includes another version of make than WinARM 20060606. Look
like a problem with the used shell. Maybe cmd.exe instead of the bash
included in WinAVR or the zsh-Win32 port included in most versions of
WinARM.
> 225 # Eye candy.> 226 begin:> 227 @echo> 228 @echo $(MSG_BEGIN)
Check the formating it has to be:
begin:
(TAB)@echo
(TAB)@echo $(MSG_BEGIN)
where (TAB) is a "real tabulator" (ASCII-Code 9). For a test you may
just remove the @echo lines without output since this may cause probelms
If you still have problems create a package with a minimal example
(makefile, linker-script, startup-code, some C-Code) to reproduce the
issue and attach it to a message to this forum-thread.
Martin Thomas wrote:
> Nazandy Perez wrote:>> I have installed a new version WinAVR-20080512, I think it is the last>> avaible. The version of the gcc is 4.3.0. I have checked that in>> C:\WinAVR-20080512\utils\bin there are a lot of applications files:>> make, mkdir, date, etc.>> O.k. so you are using the tools from WinAVR with the GNU arm-toolchain> from a WinARM package. This should work.>>>>> And now when I try to compile the same project I find another error:>>>>> "make.exe" all>> makefile:227: *** missing separator. Stop.>>>>> Process Exit Code: 2>>> Time Taken: 00:01>>>> Theoretically this project was compiled and the makefile I supposed that>> it is correct. The makefile is:>> IRC WinAVR includes another version of make than WinARM 20060606. Look> like a problem with the used shell. Maybe cmd.exe instead of the bash> included in WinAVR or the zsh-Win32 port included in most versions of> WinARM.
I couldn't understand that...Could you explain with more detail please?
>> 225 # Eye candy.>> 226 begin:>> 227 @echo>> 228 @echo $(MSG_BEGIN)>> Check the formating it has to be:> begin:> (TAB)@echo> (TAB)@echo $(MSG_BEGIN)>> where (TAB) is a "real tabulator" (ASCII-Code 9). For a test you may> just remove the @echo lines without output since this may cause probelms
I have already checked and it is a correct tabulator.
> If you still have problems create a package with a minimal example> (makefile, linker-script, startup-code, some C-Code) to reproduce the> issue and attach it to a message to this forum-thread.
In the project I have there istn't a startup-code and linker-script. are
they obligatory?
Nazandy Perez wrote:
> I realised that the function make all doesn't work:>>> "make.exe" all>> -------- begin --------> process_begin: CreateProcess(NULL, arm-elf-gcc --version, ...) failed.> make (e=2): The system can't find the specific file.
(1) Check if the path to the compiler-frontend (arm*-gcc.exe) is in the
system search-path.
(2) If you are using a GNU toolchain with another prefix than arm-elf
replace arm-elf in the makefile with the prefix of the used toolchain
(i.e. s/arm-elf/arm-eabi/g for DevkitARM R23, WinARM-testing 3/08 or
s/arm-elf/arm-none-eabi/g for Codesourcery G++).
If the code does not depend on the WinARM newlib-configuration just wipe
WinARM and install Yagarto, newer versions of Yagarto should be
Vista-compatible out of the box, the prefix is arm-elf so no changes
needed and the Yagarto setup-software extends the PATH variable AFAIK.
Martin Thomas wrote:
> Nazandy Perez wrote:>> I realised that the function make all doesn't work:>>>>> "make.exe" all>>>> -------- begin -------->> process_begin: CreateProcess(NULL, arm-elf-gcc --version, ...) failed.>> make (e=2): The system can't find the specific file.>> (1) Check if the path to the compiler-frontend (arm*-gcc.exe) is in the> system search-path.
I have looked for this file and I have three files:
- avr-gcc.exe in C:\WinAVR-20080512
- avr-gcc.4.3.0.exe in C:\WinAVR-20080512
- gcc.exe in C:\WinAVR-20080512\avr
> (2) If you are using a GNU toolchain with another prefix than arm-elf> replace arm-elf in the makefile with the prefix of the used toolchain> (i.e. s/arm-elf/arm-eabi/g for DevkitARM R23, WinARM-testing 3/08 or> s/arm-elf/arm-none-eabi/g for Codesourcery G++).
How can I see exactly the name of the GNU tollchain?
> If the code does not depend on the WinARM newlib-configuration just wipe> WinARM and install Yagarto, newer versions of Yagarto should be> Vista-compatible out of the box, the prefix is arm-elf so no changes> needed and the Yagarto setup-software extends the PATH variable AFAIK.
Thank you in advance!
You cannot use an AVR compiler to make code for an ARM. They are too
totally separate types of chip.
As martin said before things like make.exe and other build tools are the
same for ARM, AVR or x86 for that matter, but you need a specific cross
compiler for your chip series.
I would recommend removing all you have done so far and starting again.
Have you seen the Jim (James) Lynch tutorial guides ????
If you have not then get one and follow it closely.
I do not have Vista and I hope I never have to use it ;)