Files and Folders

The screenshot alongside is used to explain the folder structure and some terminology used.

The Application Path (abbreviated to *AppP*) is chosen as described in Quickstart Kit Installation. The *AppP* in the example above is C:\Adi.

The Project Paths and Name (abbreviated to *ProjP*) are chosen when creating a project as described in Project|New. In the example above the *ProjP* is C:\Adi\Examples\cs.

Note that for the example the *ProjP* is on a branch of the *AppP* but for user projects these two are not related. In particular the *ProjP* may not be the same as the *AppP*.

The Device Paths (*GnuDP*) are automatically generated at installation and are as follows : *AppP*\Devices\DN where DN is the numeric part of the device name. In the example above the *GnuDP* is C:\Adi\Devices\7024\. The user should not directly modify anything in this folder

The user can make libraries at any location but it is recommended that User Libraries are located at *AppP*\Libs\User\DN = C:\Adi\Libs\User\7024 since mIDAS will in this case simplify some of the tasks in generating and using libraries.

The ADI library at *AppP*\Libs\Adi\DN contains the libraries for the functions supplied by ADI. This includes the libraries, the source code, header files and all necessary auxilliary files.


The following chart gives more details of the application file structure:

. . . . . . .
*AppP*/ The application Path.
Arm/ This branch is predefined and should not be changed by the user.
Devices/ This branch contains Device definition files supplied by ADI.
7020/ ADuC7020 specific Device definition.
7024/ ADuC7024 specific Device definition.
1612gnuas.inc MMR definition file.
armelfas.x Device definition file.
adc.h ADC definition file.
... etc.
Docs/ This branch contains documentation files in .html format.
mIDAS/ mIDAS specific documentation files in .html format.
7020/ ADuC7020 specific documentation files in .html format.
7024/ ADuC7024 specific documentation files in .html format.
Examples/ This branch contains examples for user reference.
c/ A small example of a C source project.
s/ A small example of an assembly source project.
cs/ A small example of combined C and assembly source project.
Libs/ This branch contains libraries and their source files.
Std/ This branch contains auxiliary files for the GCC supplied C functions.
User/ This branch contains libraries, source files and header files of User supplied C compatible functions as detailed below.
7020/ Contains libraries, header files and library projects of user supplied C compatible functions for the ADuC7020.
7024/ Contains libraries, header files and library projects of user supplied C compatible functions for the ADuC7024.
libAdc7024.a Each peripheral (e.g. ADC) has a library file which is generated using the above peripheral source file.
libAdc7024.h Each peripheral (e.g. ADC) has a header file which combines all function prototypes for that peripheral.
Adc7024Cfg Each function (e.g. ADC configuration) has a function library project e.g.Adc7024Cfg.
Adc7024Cfg.s The function assembly source file.
Adc7024Cfg.ini The function options file.
Adc7024Cfg.asb The function assembly script file.
etc etc.
Adi/ This branch contains libraries generated by ADI.
. . . . . .


The Project file structure for each project is very simple:

. . . . . .
*ProjP*/ All files of this project are contained in this folder.
. . . . . . .