Changes between Version 19 and Version 20 of boot_loader

Timestamp:

Feb 5, 2015, 10:42:43 AM (10 years ago)

Author:

alain

Comment:

--

boot_loader

@@ -10 +10 @@
 == Phase 1 : Reset Initialization ==
 
-In case of hard reset, all processors execute the same ''reset'' code (also called ''preloader'' code) stored in the external ROM, but the work done depends on the processor global index. This ''reset'' code is generic, and can be used to boot any operating system:  
- * Processor P(0,0,0) load the GIET_VM boot-loader code from the external disk (or any other mass storage peripheral), to the physical memory bank of cluster(0,0).
+After hard reset, all processors execute the same ''reset'' code (also called ''preloader'' code) stored in the external ROM, but the work done depends on the processor global index: 
+ * Processor P(0,0,0) load the GIET_VM boot-loader code from the external disk (or another bootable mass storage peripheral), to the physical memory bank in cluster(0,0): segments seg_boot_code and seg_boot_data.
  * All other processors initialize their private interrupt controller, to be able to receive an inter-processor interrupt (WTI), and enter ''wait_state'' in low-power mode.
+This ''reset'' code is generic, and can be used to boot any operating system.  
 
 == Phase 2 : Boot Initialisation ==
@@ -27 +28 @@
 
 === step 1 ===
-Processor P(0,0,0) initializes the FAT,  initializes the TTY0 lock, initialises the synchronisation barrier, and load the ''map.bin''file. Then processor P(0,0,0) use inter-processor-interrupts (WTI) to start the parallel execution, and activate processors P(x,y,0) in all clusters containing processors.
+Processor P(0,0,0) initializes the FAT,  initializes the TTY0 lock, initializes the synchronization barrier, and load the ''map.bin''file to the physical memory bank in cluster(0,0). Then processor P(0,0,0) use inter-processor-interrupts (WTI) to start the parallel execution, and activate processors P(x,y,0) in all clusters containing processors.
 
 === step2 ===