EmbDev.net

Forum: ARM programming with GCC/GNU tools WinARM with Windows 7 - not working


Author: Peter Moylan (Company: ResTech) (pmoylan)
Posted on:

Rate this post
0 useful
not useful
[Sorry if this is a FAQ, but I did search]

Has anyone managed to get WinARM working with Windows 7? I have, as far 
as I can tell, exactly the same setup as WinARM on XP, which worked. 
(And the same Makefile.) I'm starting it with the batch file:

[Programmer's Notepad.bat]
@echo off
set ARM=c:\WinARM
set 
PATH=%ARM%\libexec\gcc\arm-elf\4.1.2;%ARM%\bin;%ARM%\arm-elf\bin;%ARM%\u 
tils\bin;
start %ARM%\pn\pn.exe
[/Programmer's Notepad.bat]

pn.exe starts correctly, and I can open a project group and edit files. 
The problem is that Make doesn't work.

Sometimes the error symptom is a popup that says "sh.exe has stopped 
working". This can be resolved to the message "Unhandled exception at 
0x774f8db9 in sh.exe: 0xC0000005: Access violation writing location 
0x00000014." (I've seen this error before, but was able to live with it 
because it was intermittent.)

More often, though, trying to do any Make operation, including even 
"[WinARM_G] Make Clean", results in nothing happening at all, or at 
least nothing visible. There is no output window, even though the output 
window is enabled in the "View" menu.

I emphasize that this is with exactly the same source and project files, 
on a shared drive, as for a project that worked with WinARM under 
Windows XP.

Author: Malagas (Guest)
Posted on:

Rate this post
0 useful
not useful
Hi.

Why don't you try to execute editor in Admin mode or use Compatibility 
Mode for XP on W7?

I worked with me.

Author: Thomas Wedemeyer (twede)
Posted on:

Rate this post
0 useful
not useful
Hallo Peter,

the problem is the "make"-program. The binary included in the 
WinArm-installation doesn't work under Win7. You just have to replace 
the make.exe with another version. I think i replaced the make.exe with 
a version from the Atmel AVR Studio or some where else from the 
internet...
It works perfect.

Regards
Thomas

Author: dave (Guest)
Posted on:

Rate this post
0 useful
not useful
I tried the AVR make program and it didn't fix the problem. One thing 
that did work was removing quotes from an echo message.

-Dave

Author: Martin Thomas (Guest)
Posted on:

Rate this post
0 useful
not useful
The only maintainer of WinARM (=me) just keeps the old WinARM packages 
online since they are a "battery included" distribution (toolchain, 
utilties, examples) which may help beginners. There are enough 
alternatives for the toolchain in WinARM available so I suggest to use 
an up-to-date GNU ARM cross-toolchain package for MS Windows hosts 
(Codesourcery CodeBench/Sourcery G++ for "bare metal" ARM-EABI, Yagarto, 
DevkitARM; links on the WinARM page) and the latest tools (make, echo, 
rm, shell,...) from the MinGW project.

Installing WinAVR is an option to avoid problems with incompatible tools 
(not the cross-toolchain itself) since it installs build-tools from the 
MinGW project. If WinAVR is installed the utils-directory from WinARM 
can be removed from the system search-path and deleted (see WinARM 
readme.txt).

With a few modifications in the makefile the only tools which are 
included in the Codesourcery package (cs-make.exe and cs-rm.exe) will do 
in most cases when using a MS-OS as host-platform. This is the method I 
currently prefer since it avoids conflicts due to tools with the same 
filename in the system's search path but different options and output 
like find.exe and sort.exe from MS-"DOS" or GNU.

General offer (off-topic):
If there is anything in the WinARM-package which is so special that it 
prevents a migration to a more up-to-date toolchain-collection please 
send an e-mail and I will try to help with the update. e-mail address at 
the bottom of the WinARM-page.

Author: Peter Moylan (Company: ResTech) (pmoylan)
Posted on:

Rate this post
0 useful
not useful
Thanks to everyone for the suggestions. Meanwhile, however, I had moved 
on to other approaches. Initially a command-line use of yagarto, and 
frankly I found a command-line approach a lot easier to use than an IDE. 
(But I guess that beginners will indeed find it easier to have 
everything packaged into an IDE.) Now, after a processor and development 
board upgrade (to an LPC1788) I'm finding that I'm having to move to a 
commercial IDE (IAR) just because of the complexity of the directory 
structure used for the code base.

Author: Martin Thomas (mthomas) (Moderator)
Posted on:

Rate this post
0 useful
not useful
Peter Moylan wrote:
> Now, after a processor and development
> board upgrade (to an LPC1788) I'm finding that I'm having to move to a
> commercial IDE (IAR) just because of the complexity of the directory
> structure used for the code base.
This is the only reason? It's not too complicated to handle different 
source directories using make/makefile. But of cause this is a matter of 
taste. I prefer to keep all settings in a single text-file (makefile) 
instead of clicking through various dialogs. The makefiles in the 
examples available from this page might serve as templates: 
http://www.siwawi.arubi.uni-kl.de/avr_projects/arm...

Reply

Entering an e-mail address is optional. If you want to receive reply notifications by e-mail, please log in.

Rules — please read before posting

  • Post long source code as attachment, not in the text
  • Posting advertisements is forbidden.

Formatting options

  • [c]C code[/c]
  • [avrasm]AVR assembler code[/avrasm]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]




Bild automatisch verkleinern, falls nötig
Note: the original post is older than 6 months. Please don't ask any new questions in this thread, but start a new one.