Changes between Version 66 and Version 67 of boot_procedure


Ignore:
Timestamp:
Dec 7, 2019, 1:57:40 PM (3 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • boot_procedure

    v66 v67  
    106106The core[cxy][0] exécute the following tasks:
    107107    * 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.
    108     * 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]'''
     108    * 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,
     109    * To access the boot code stored in cluster cxy, the core[cxy][0] activates the instruction MMU.
    109110    * The core[cxy][0] copies the ''arch_info.bin'' structure from ARCH_INFO zone in cluster 0 to ARCH_INFO zone in cluster cxy.
    110111    * The core[cxy][0] copies the ''kcode'' and ''kdata'' segments from KERNEL_CODE zone in cluster 0 to KERNEL_CODE zone in cluster cxy.
     
    115116=== B5. Boot-loader fully parallel phase ===
    116117
    117 In this phase all core[cxy][lid] are running.
     118In this phase all cores in all clusters are running.
    118119
    119120Each 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.