5 | | This phase is executed in case of hard reset : all processors execute the ''reset'' code (also called ''preloader'' code) stored in the external ROM. |
6 | | Processor (0,0,0) load the GIET_VM boot-loader code from the external disk (or any other mass storage peripheral), to the physical memory of cluster(0,0). |
7 | | This ''reset'' code is generic. It is entirely defined by the target hardware architecture, and can be used to boot any operating system. |
8 | | 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. |
| 7 | This phase is executed in case of hard reset: all processors execute the ''reset'' code (also called ''preloader'' code) stored in the external ROM, |
| 8 | but the work done depends on the processor global index. This ''reset'' code is generic. It is entirely defined by the target hardware architecture, and can be used to boot any operating system. |
| 9 | * Processor (0,0,0) load the GIET_VM boot-loader code from the external disk (or any other mass storage peripheral), to the physical memory of cluster(0,0). |
| 10 | * 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. |