Hi, I have litle problem with Yagarto tools make command in 64 bit Windows. Yagarto tools works ok with 32 bit Windows 7 (laptop) Error: C:\ARM\LEDglow_LPC2138>make make: Interrupt/Exception caught (code = 0xc00000fd, addr = 0x425073) Have anyone seen this error?
Since make is independent of the code generation tools, you might simply replace it with a 64 bit version of make. There is one available here: http://www.equation.com/servlet/equation.cmd?fa=make An alternative but somewhat heavyweight solution may be to run a 32bit version of Windows in a virtual machine on your 64bit platform. Both VMware Server and Virtual PC are free and will allow you to do this. One advantage of a VM is that it provides a consistent and standardised virtual platform regardless of the physical hardware and drivers installed. Because you can have a virtual network between the VM and the host (and the rest of your physical network) accessing files in either environment can be seamless. http://www.microsoft.com/downloads/details.aspx?FamilyID=28C97D22-6EB8-4A09-A7F7-F6C7A1F000B5&displaylang=en http://www.vmware.com/products/server/ If you do not have a spare Windows license to install on the VM, you can use one of the IE compatibility test VHDs for Virtual PC, which are in fact time-limited full OS installations. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=21eabb90-958f-4b64-b5f1-73d0a413c8ef Clifford
I got the same error message, but the solution was plain simple: Don't install the yagarto into a directory containing spaces (like "Program Files(x86)") On my Win7 64bit machine, installing the toolkit in c:\yagarto\ fixed the issues...
XploD wrote: > I got the same error message, but the solution was plain simple: > Don't install the yagarto into a directory containing spaces (like > "Program Files(x86)") Oh yes; never do that with any GNU tools, especially make. You may be a bit late with the suggestion however; thread necromancy is seldom useful.
Thank you very much! I have searched longer days. Now I read this post and my problem is solved! Thanks. Helge
Alternatively, edit the PATH environment variable to use the *short names* for the directories where Yagarto is intalled, e.g.:
1 | PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\yagarto-tools-20100703\bin;C:\Program Files (x86)\yagarto\bin |
becomes:
1 | PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\PROGRA~2\YAGART~1\bin;C:\PROGRA~2\yagarto\bin |
(Use 'dir /x' in the command shell to check the actual short name of each directory, and see http://geekswithblogs.net/renso/archive/2009/10/21/how-to-set-the-windows-path-in-windows-7.aspx for info on editing the PATH) -Owen
Watch this topic
Disable multi-page viewPlease log in before posting. Registration is free and takes only a minute.
Existing account
Do you have a Google/GoogleMail account? No registration required!
Log in with Google account
Log in with Google account
No account? Register here.