Changes between Version 74 and Version 75 of WikiStart
- Timestamp:
- May 26, 2015, 6:26:31 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v74 v75 20 20 21 21 22 == __ A) [wiki:mapping_info Mapping]__ ==22 == __1) [wiki:mapping_info Mapping]__ == 23 23 24 24 Both the target hardware architecture and the mapping directives (placement of software tasks on the physical processors / placement of the software objects on the physical memory banks) must be described in a python script. This section describes the Python constructs used to describe the mapping. This python script generates the ''map.bin'' C binary file, that is used by the boot-loader to initialise the system. 25 25 26 == __ B) [wiki:boot_loader Boot Procedure]__ ==26 == __2) [wiki:boot_loader Boot Procedure]__ == 27 27 28 28 This section describes the three phases boot procedure. 29 29 30 == __ C) [wiki:common_functions Common Functions]__ ==30 == __3) [wiki:common_functions Common Functions]__ == 31 31 32 32 Here are presented the utility functions that can be used by both the bootloader (in the boot phase), and by the kernel (in the execution phase). 33 33 34 == __ D) [wiki:kernel_functions Kernel Services]__ ==34 == __4) [wiki:kernel_functions Kernel Services]__ == 35 35 36 36 Here are presented the functions implementing the main services provided by the GIET_VM in the execution phase: syscall handler, interrupt handler, exception handler, and context switch handler. 37 37 38 == __ E) [wiki:library_stdio System calls]__ ==38 == __5) [wiki:library_stdio System calls]__ == 39 39 40 40 Here are presented all the C functions that can be used by an user application (in the execution phase) to require a service to the operating system. All these functions contain a ''syscall'' instruction that force the processor to enter the kernel mode. 41 41 42 == __ F) [wiki:user_libraries User level libraries]__ ==42 == __6) [wiki:user_libraries User level libraries]__ == 43 43 44 44 Here are presented various libraries of C functions that can be used by an user application for synchronization, inter-task communications, or for dynamic memory allocation. 45 45 All these services are provided at user level, and do not require the processor to enter the kernel mode. 46 46 47 == __ G) [wiki:peripherals_drivers Peripherals Drivers]__ ==47 == __7) [wiki:peripherals_drivers Peripherals Drivers]__ == 48 48 49 This section defines the software drivers APIs for the peripherals supported by he GIET_VM.49 This section defines the software drivers APIs for the peripherals supported by the GIET_VM. 50 50 51 == __H) [wiki:user_applications User Applications]__ == 51 == __8) [wiki:file_system Peripherals File System]__ == 52 53 This section describes the FAT32 file system supported by the GIET_VM. 54 55 == __9) [wiki:user_applications User Applications]__ == 52 56 53 57 This section describes the user applications that have been developed to analyse the TSAR many-cores architecture an the GIET_VM OS scalability. 54