mirror of
https://github.com/saymrwulf/xous-core.git
synced 2026-11-14 08:03:34 +00:00
glitches can trigger interrupts from several sources: - ECC errors on multiple blocks - consistency check errors on hardened logic - light sensor - voltage sensor - glue cells These primitives respond to these glitches in an interrupt context. At the moment, by default a fairly lax approach is taken to responding to the glitches: partially, we want to make sure that the sensors aren't too sensitive and trigger by accident. The final thresholds can be adjusted fairly readily. In addition, the mesh can trigger an interrupt, and typically, that interrupt is a false reading (because the mesh takes a long time to settle, and we boot the system while the mesh settles). Thus, we take an approach of polling the mesh effectively, and when interrupts happen due to the mesh we just clear it and ignore it and allow the polling routine to manage the mesh. The mesh is theorized to be a static attack, anyways. |
||
|---|---|---|
| .. | ||
| bao1x-api | ||
| bao1x-hal | ||
| blitstr2 | ||
| chat | ||
| cos_table | ||
| flatipc | ||
| flatipc-derive | ||
| keystore-api | ||
| mass-storage | ||
| perflib | ||
| precursor-hal | ||
| tls | ||
| userprefs | ||
| ux-api | ||
| xous-bio | ||
| xous-bio-bdma | ||
| xous-pio | ||
| xous-pl230 | ||