Changes between Version 6 and Version 7 of mapping_info

Timestamp:

Oct 26, 2014, 1:14:59 PM (10 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -38 +38 @@
 The ''map.bin'' file must be stored on disk and will be loaded  in memory by the GIET_VM bootloader in the ''seg_boot_mapping'' segment. 
 
-== __Python Mapping General__ ==
+== __Python mapping introduction__ ==
 
 A specific mapping requires at least two python files:
@@ -46 +46 @@
 The various Python Classes used by these these files are defined in the [source:soft/giet_vm/giet_python/mapping.py mapping.py] file.
 
-== Python Architecture description ==
+== __Python architecture description__ ==
 
 To define an architecture, you must use the following constructors:
@@ -83 +83 @@
 || arg          || optionnal argument depending on peripheral type ||
 
-The Peripheral types are defined in the [source:soft/giet_vm/giet_xml/mapping_info.h mapping_info.h] and [source:soft/giet_vm/giet_python/mapping.py mapping.py] files.
+The supported peripheral types and subtypes are defined in the [source:soft/giet_vm/giet_xml/mapping_info.h mapping_info.h] and [source:soft/giet_vm/giet_python/mapping.py mapping.py] files.
 
 === Construct physical memory banks ===
@@ -89 +89 @@
 The ''mapping.addRam( )'' construct adds one physical memory bank, and the associated physical segment. It has the following arguments:
 
-== Application description : appli.py ===
+== __Python application description__ ==