Hacker News Reader

> Our HardFault handler can now ... quickly interpret the faulting instruction, emulate the write, flush the cache line, and resume.

This sounds similar to the approach taken by yocto-8

https://github.com/yocto-8/yocto-8/blob/main/doc/extmem.md

View on HN

except they use a memory region that does not exist, forcing them to emulate reads, so their memory is shit slow AND not executable, while this project's memory reads and executes at full speed, only shit-slow for writes.

Reply on news.ycombinator.com