Feature #590

System (de)initialization with disabled bootloader

Added by Thomas Schöpping 9 months ago. Updated 21 days ago.

Status:ResolvedStart date:2019-03-08
Priority:LowDue date:
Assignee:Thomas Schöpping% Done:

100%

Category:-Estimated time:20.00 hours
Target version:-

Description

Introduce a possibility to configure AMiRo-OS to not use a bootloader, so that the OS will fully initialize the hardware, including SSSP related signal handling and synchronization (if SSSP is enabled).

History

#1 Updated by Thomas Schöpping 9 months ago

  • Parent task set to #593

#2 Updated by Thomas Schöpping 9 months ago

  • Parent task deleted (#593)

#3 Updated by Thomas Schöpping 21 days ago

  • Status changed from New to Resolved
  • Assignee set to Thomas Schöpping
  • % Done changed from 0 to 100
Four new flags have been introduced to aosconf.h:
  • AMIROOS_CFG_BOOTLOADER
    Controls the bootloader to be used alongside with AMiRo-OS.
    Currently allowed values are:
    • AOS_BOOTLOADER_NONE
      No bootloader is available.
    • AOS_BOOTLOADER_AMiRoBLT
      AMiRo-BLT is used as bootloader.
  • AMIROOS_CFG_SSSP_STARTUP
    Controls, whether the SSSP startup sequence (see SSSP 1.4 until startup stage 2.2) shall be executed by AMiRo-OS (set to true) or is handled by some other system, i.e. a bootloader (set to false).
  • AMIROOS_CFG_SSSP_SHUTDOWN
    Controls, whether the SSSP shutdown sequence (see SSSP 1.4 from shutdown stage 1.3) shall be executed by AMiRo-OS (set to true) or is handled by some other system, i.e. a bootloader (set to false).
  • AMIROOS_CFG_SSSP_MSI
    Controls, whether the optional module stack initialization (see SSSP 1.4 startup phase stage 3) shall be performed.

Also available in: Atom PDF