Skip to content
Snippets Groups Projects
Select Git revision
  • 3b9393fec6b49cd8e389b05e7f45f3922bb66f75
  • master default protected
  • backslash
  • nickname-match-configs
  • genofire/leds_rgb_get_state
  • genofire/rockets-state
  • genofire/ble-follow-py
  • plaetzchen/ios-workaround
  • blinkisync-as-preload
  • genofire/haule-ble-fs-deactive
  • schneider/max30001-pycardium
  • schneider/max30001-epicaridum
  • schneider/max30001
  • schneider/stream-locks
  • ios-workarounds
  • schneider/fundamental-test
  • schneider/ble-buffers
  • schneider/maxim-sdk-update
  • ch3/splashscreen
  • koalo/bhi160-works-but-dirty
  • koalo/wip/i2c-for-python
  • v1.9
  • v1.8
  • v1.7
  • v1.6
  • v1.5
  • v1.4
  • v1.3
  • v1.2
  • v1.1
  • v1.0
  • release-1
  • bootloader-v1
  • v0.0
34 results

main.c

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>