- Sep 19, 2021
- Sep 17, 2021
-
- Sep 16, 2021
-
-
schneider authored
-
schneider authored
-
schneider authored
-
schneider authored
The loop condition in the epic_sleep based sleep could underflow if an interrupt introduced too much delay at the end.
-
schneider authored
The clock source of epicardium is not very stable and can drift multiple percent. This has an effect on epic_sleep() and can lead to sleeps which are longer than anticipated. With this change we slowly move towards our sleep goal using multiple calls. This is less efficient but leads to precise results.
-
schneider authored
-
schneider authored
-
schneider authored
-
schneider authored
-
schneider authored
-
schneider authored
This can be used by the second core to signal that the system can go to a light sleep to recuce power consumption.
-
- Sep 15, 2021
- Sep 14, 2021
-
-
schneider authored
This reduces the power consumption of the system by around .1 mA when the personal state is not active.
-
- Aug 17, 2021
-
- Aug 15, 2021
- Jul 25, 2021
-
- Jul 16, 2021
-
-
rahix authored
-
- Jul 04, 2021
-
-
rahix authored
Disable all maskable interrupts on core 1 during API calls. This brings two main advantages: 1. It means API calls are now always ISR-safe and can be used everywhere in core 1 code. This is mostly interesting to l0dables as Pycardium should not need to do this. 2. It allows Epicardium to halt the clock for core 1 without fear as we have observed problems with doing this when core 1 is currently executing instructions that touch memory. Now a synchronous call from core 1 will guarantee that it is currently waiting in a WFE and no other ISRs could be potentially running.
-
rahix authored
When interrupts are disabled during API calls on core 1, we can only trigger a core 1 reset when there is no API call ongoing. This means that the lifecycle machinery needs to allow any running API calls to complete before it has a chance to see its reset interrupt delivered. This is complicated because we cannot synchronize on core 1 triggering an API call - the best we can do is stop the dispatcher, check whether our reset interrupt was delivered, and if not, give it another chance to process an API call. Additionally, "give it another chance to process an API call" means that the IDLE task must run, because this is currently a prerequisite to scheduling the dispatcher (see [1]). The only way to facilitate this is with a sleep that is long enough that it will eventually let core 0 go idle. It seems that an 8 tick delay does the job quite fine. Thus, implement a busy loop which provides the above requirements and with that makes Epicardium prepared for payloads which perform API calls with interrupts disabled. [1]: https://firmware.card10.badge.events.ccc.de/epicardium/overview.html#internals
-
rahix authored
This function is useful on its own for more complex lifecycle management in Epicardium. Split it out of core1_wait_ready() so it can be used.
-
- Apr 11, 2021
-
- Apr 09, 2021
- Apr 08, 2021