Skip to content
Snippets Groups Projects
Select Git revision
  • color-definitions
  • battery-symbol
  • framebuffer-overlay
  • master default protected
  • batt-capacity
  • menu-disp
  • clock-fix
  • personal-state-colors
  • power
  • charge_voltage
  • pybattery
  • koalo/bhi160
  • ch3/splashscreen
  • genofire/ble-rewrite
  • rahix/simple_menu
  • koalo/bhi160-works-but-dirty
  • ios-workarounds
  • koalo/wip/i2c-for-python
  • renze/safe_mode
  • renze/hatchery_apps
  • v1.2
  • v1.1
  • v1.0
  • release-1
  • bootloader-v1
  • v0.0
26 results

main.c

Blame
  • Forked from card10 / firmware
    Source project has a limited visibility.
    • rahix's avatar
      3b9393fe
      feat(epicardium): Implement basic core 1 lifecycle · 3b9393fe
      rahix authored
      
      This commit introduces a way to control core 1.  This is archieved by a
      predefined API-Interrupt:  The reset interrupt.  When triggered, it will
      bring the core back into its default state and wait for a new vector
      address from Epicardium.  Once this vector address is transferred, it
      will start the new payload.
      
      This method only works as long as core 1 is responsive to the API
      interrupts.  Cases where this might not be the case:
      
        - During times where core 1 has interrupts disabled
        - When in a higher priority exception handler
        - When core 1 has corrupted its IVT
      
      Signed-off-by: default avatarRahix <rahix@rahix.de>
      Verified
      3b9393fe
      History
      feat(epicardium): Implement basic core 1 lifecycle
      rahix authored
      
      This commit introduces a way to control core 1.  This is archieved by a
      predefined API-Interrupt:  The reset interrupt.  When triggered, it will
      bring the core back into its default state and wait for a new vector
      address from Epicardium.  Once this vector address is transferred, it
      will start the new payload.
      
      This method only works as long as core 1 is responsive to the API
      interrupts.  Cases where this might not be the case:
      
        - During times where core 1 has interrupts disabled
        - When in a higher priority exception handler
        - When core 1 has corrupted its IVT
      
      Signed-off-by: default avatarRahix <rahix@rahix.de>