Changes between Version 28 and Version 29 of boot_loader

Timestamp:

Feb 17, 2016, 5:53:34 PM (9 years ago)

Author:

alain

Comment:

--

boot_loader

@@ -11 +11 @@
 
 After hard reset, all processors execute the same ''reset'' code (also called ''preloader'' code) stored in the external ROM. The work done depends on the processor global index: 
- * Processor P(0,0,0) loads the GIET_VM boot-loader code from the external block device, to the physical memory bank in cluster(0,0). It load the two segments seg_boot_code and seg_boot_data from the ''boot.elf'' file that must be stored at (lba = 2) on the block device. 
- * 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.
+ * Processor P(0,0,0) loads the GIET_VM boot-loader code from the external block device, to the physical memory bank in cluster(0,0). It load the two segments seg_boot_code and seg_boot_data from the ''boot.elf'' file. This ''boot.elf'' file must be stored at (lba = 2) on the external block device. The two first BPPs (Big Physical Page) in cluster (0,0) are reserved for the four segments used by the boot-loader: ''seg_boot_mapping'', ''seg_boot_code'', ''seg_boot_stack'', and ''seg_boot_data'', and the base addresses ans sizes defined in the mapping must fit in these reserved 4 Mbytes.
+ * All other processors initialize their private interrupt controller, to be able to receive an inter-processor interrupt (WTI), and enter the ''wait_state'', in low-power mode.
 This ''reset'' code is generic, and can be used to boot any operating system.