Changes between Version 33 and Version 34 of boot_procedure


Ignore:
Timestamp:
Jan 18, 2018, 8:07:30 PM (4 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • boot_procedure

    v33 v34  
    3232
    3333The TSAR boot-loader uses an OS-independent '''pre-loader''', stored in an external ROM, and in charge of loading the TSAR
    34 '''boot-loader''' code from an external block-device to the memory. This preloaded is specific for the TSAR architecture, but independent on the Operating System. It is used by ALMOS-MKH, but also by LINUX, NetBSD, or the GIET-VM. 
     34'''boot-loader''' code from an external block-device to the memory. This preloader is specific for the TSAR architecture, but independent on the Operating System. It is used by ALMOS-MKH, but also by LINUX, NetBSD, ALMOS_MKH, or the GIET-VM. 
    3535
    3636The TSAR boot_loader allocates - in each cluster containing a physical memory bank - five fixed size memory zones, to store various
     
    4949
    5050
    51 
    52 Le chargement d'ALMOS-MK sur l'architecture TSAR se fait donc en 4 phases:
    5351A core is identified by  two indexes[cxy][lid] : ''cxy'' is the cluster identifier, an ''lid'' is the core local index in cluster cxy.
    5452In all clusters, the core with local index 0 is called ''CP0''.
     53
     54
     55
     56Le chargement d'ALMOS-MK sur l'architecture TSAR se fait donc en 4 phases décrites ci-dessous
    5557
    5658=== B1. Preloader phase ===
     
    5860At reset, the extension address registers (for both data and instructions) in all cores[cxy][lid] contain the 0 value.
    5961Therefore, all cores can only access the physical address space of cluster 0.
    60 If the  preloaded is stored in an external ROM, the I/O cluster must be cluster 0, to access the external ROM.
     62 * In the TSAR_LETI architecture, the preloader is loaded in the first 16 kbytes of the RAM located in cluster 0.
     63 * In the TSAR_IOB architecture, the preloader is stored in an external ROM, that is accessed throug the IO_bridge located in cluster 0.
    6164
    6265All cores execute the same preloader code, but the work done depends on the core identifier. The core[0][0] (i.e. CP0 in cluster 0) load