Changes between Version 66 and Version 67 of boot_procedure

Timestamp:

Dec 7, 2019, 1:57:40 PM (4 years ago)

Author:

alain

Comment:

--

boot_procedure

@@ -106 +106 @@
 The core[cxy][0] exécute the following tasks:
     * To access the global data stored in cluster cxy, the core[cxy][0] copies the boot-loader code from BOOT_CODE zone in cluster 0 to BOOT_CORE zone in cluster cxy.
-    * To access the instructions stored in cluster cxy, the core[cxy][0] creates a minimal page table containing two big pages mapping respectively the local BOOT_CORE zone, and the local KERNEL_CODE zone, and activates the instruction MMU. '''[TO BE DONE]'''
+    * The core[cxy][0] creates a minimal page table containing two big pages mapping the local BOOT_CORE zone, and the local KERNEL_CODE zone, 
+    * To access the boot code stored in cluster cxy, the core[cxy][0] activates the instruction MMU.
     * The core[cxy][0] copies the ''arch_info.bin'' structure from ARCH_INFO zone in cluster 0 to ARCH_INFO zone in cluster cxy.
     * The core[cxy][0] copies the ''kcode'' and ''kdata'' segments from KERNEL_CODE zone in cluster 0 to KERNEL_CODE zone in cluster cxy. 
@@ -115 +116 @@
 === B5. Boot-loader fully parallel phase ===
 
-In this phase all core[cxy][lid] are running.
+In this phase all cores in all clusters are running.
 
 Each core must initialise few registers, as described below, and jump to the kernel_entry address. This address is defined in the ''kernel.elf'' file, and registered in the ''kernel_entry'' global variable.