As there is no help file yet you can find some hints here.
Run basic setup.exe to install AvrSide for the first time. Update to current version
replacing AvrSide.exe in [AvrSide\bin] folder with the last one from downloads ( it is
recommended to backup the previous one of course). Some new auxiliary files are also
required - copy them to [AvrSide\bin]. By default AvrSide is installed in [c:\WinAvr\
AvrSide] but you can choose your own suitable location (for example c:\AvrSide).
2.First project :
Create a new subfolder in [AvrSide\Projects] directory, for example \AvrSide\Projects\
Test01. For the first time AvrSide starts with default settings and one empty "noname"
tab in "noname project". Resize editor window and set favourite colours (Options ->
Display). Using CTRL+J insert "mainmod" code template. Save file as ( for example )
"main.c" in your new folder, then save project as (for example) "Test01.gcp" in the
same folder ("Save project as" dialogue will launch automatically after saving file).
Now try to make the project with F9 shortcut. As AvrSide doesn't know where avr-gcc
is, you should set an appropriate path - by default c:\WinAvr\bin (but you can use
your own avr-gcc setup of course).
Look into [Test01] folder. Avr-gcc output files should appear here (according to
compiler options). Check Test01.txt log file with some text viewer : here you will
find all the avr-gcc commands used to build project.
2.Playing with AvrStudio :
We can use some different options : AvrStudio 3 with coff-avr debug format,
AvrStudio 4 with coff-ext-avr format or AvrStudio 4.11 with elf-dwarf2 format.
Using coff requires binutils compiled with elf-coff patch (WinAvr supports this of
course). However, it is strongly recommended to use the last Studio version and elf-
dwarf2 debug info as it gives much more possibilities.
F11 shortcut launches Studio. Only for the first time we are informed to manually
start Studio, load our *.elf file and configure simulator. Next time AvrStudio
*.aps configuration file is used to restore the project debugging session quite
automatically. When AvrStudio already runs F11 simply sets focus to it.
3.Launching .gcp extension files :
We could configure system DDE engine to run AvrSide with double click on *.gcp
project file. It must be done manually (installer automatic option is not prepared
yet) but it is not difficult :
4.Playing with Hapsim :
- Open Windows Explorer > Tools > Folders options > File types - add a new GCP
- Set Avrside.exe as default application.
- Edit advanced options :
- add 'open' action,
- application command for 'open' :"C:\AvrSide\bin\AvrSide.exe" "%1",(insert
your real AvrSide.exe path),
- using DDE - yes,
- DDE message - %1 ,
- application - AvrSide ,
- not launched DDE application (or similar) - leave empty,
- topic (or similar) - System
To use Hapsim (AvrStudio 4 plug-in to simulate AVR peripherals) we must download it
hapsim.htm and unpack into folder \AvrSide\Hapsim. An auxiliary file
"haptemplate.xml" should also be installed in \AvrSide\bin. Then we could launch
Hapsim from AvrSide menu with current project settings (settings are stored in
project_name.xml file; if such a file does not exist yet it is created getting
default configuration just from \bin\haptemplate.xml).Note that Hapsim requires
running AvrStudio. To avoid warning alert AvrSide menu command checks Studio
presence and launch it first if necessary.
AvrStudio with Hapsim works significantly slower. Then, a HAPSIM checkbox is added
in compiler options dialogue. It simply defines HAPSIM symbol which may be used
in code to compile normal or Hapsim versions (for example in timers configuration).