Sevc Dominik wrote:

>> "make" all
> MAKE Version 5.2  Copyright (c) 1987, 1998 Inprise Corp.

Well, this is a FAQ, seems that I've forgotten to include information
about this in the readme.hmtl - sorry.

You are using the wrong make program. make.exe from Borland/Inprise can
not be used with the makefiles provided with the WinARM-examples. You
need a gnu-make (or compatible) like the make.exe that comes with WinARM
(in WinARM\utils\bin). The problem is caused be different programs with
the same filename.

Search your harddisk for programs with the filename make.exe, rename all
but the make.exe in WinARM\utils\bin.

If you type
make --version
the output should start with "GNU make".

> Exist free schematic and software for jtag debugging?

There are a lot of schematics for wiggler-clones. Some are included in
WinARM (search for wiggler*.pdf inside WinARM\). With a
wiggler-type-dongle you can used for example openocd or ocdremote as
GDB-server and insight-dgb as debugging-software. Everything should be
included in the WinARM package.
(ARM-Controller->JTAG-Connector->Wiggler->ParPort->
GDB-Server-Software->(insight-)gdb.

Hope this helps,
Martin Thomas

First of all: did you at least try to read the readme.html that comes
with WinARM?

> Sevc Dominik wrote:
>> Yes I have tre make.exe (1.WinARM,2.Delphi,3.AVR studio)

AVRStudio does not include make, the make which AVRStudio uses comes
with WinAVR.

>> I rename file 2 and 3 , after make show message so file not found
>> make.exe .

Since you have WinAVR installed read the remarks further down in
readme.html.
For now:
- Revert the change of the filename of "3". The make.exe from WinAVR can
be used since it is a GNU make.
- Add C:\WinARM\bin to your path. Since you have WinAVR installed there
is no need to add c:\WinARM\utils\bin
- For WinAVR+WinARM the Path should include c:\WinAVR\bin
C:\WinAVR\utils\bin and c:\WinARM\bin

>> I realy can't where must write path.

Search the net or the Windows online-help for set environment variables.

>> I must self define path to all needet file .

Sorry, I do not understand this remark/question.

> I make easy solution - copy all bin files to Delphi directory
> and all work.

If it works for you it's ok. But it is unneeded.

> Now is basics question is : where can I find result information after
> make.
> code size, used ram,size of user data...
> show same information after make but ... :-) .

The usual example-makefiles include a call to arm-elf-nm which shows the
summary of the sizes (.text, .data, .bss ...) - this is the "some
information" you have mentioned. But the information you are looking for
is included: usualy "Code-Size" = .text + .data and "user data" = .data
+ .bss.

Martin Thomas

> hmm codesize = .text + .data  -> 11828 + 2416 = 14244
>     userdata = .data + .bss -> 2416 + 72 = 2488
>
> I look to source end I thinks so it's easy program but use 14244 byt for
> code?
> Is it goog or I bad understant result size source code.

Take a look into the map-file and use arm-elf-nm to locate the objects
with the high memory-demand. You will see that the iprintf needs a lot
of memory (printf needs even more since floating-point is supported). If
you are using the stdio-functions from the newlib (like i.e. (i)printf
or sscanf) this memory-demand is normal. There are smaller
implementations for printf et al available but they usualy have limited
functionlity or are very target-specific.

Martin Thomas