Brad Campbell
Brad Campbell
Ok this should finally be ready!
``` ---| Cortex-M Fault Status |--- No Cortex-M faults detected. ``` That is unexpected. Perhaps this has something to do with the cortex-m0 implementation? If there aren't any faults, what...
First attempt: I ran `make debug RAM_START=0x20004000 FLASH_INIT=0x10020071`. Relevant section of `cortex-m0.userland_debug.lst`: ``` 1002038c : int arg1, int arg2) { 1002038c: b510 push {r4, lr} 1002038e: 0004 movs r4, r0...
This is hard to debug externally. My best thought so far is that since this is a cortex-m0 platform, and we 1) have different implementations for the functions in the...
Unless we happen to figure this out, I propose we be ok with noting this as a known issue for the release.
I added a commit updating the `Soundness.md` documentation. Please take a look that what I added is correct.
Closed in favor of https://github.com/tock/tock/pull/3239
> Removing this would mean that `_sappmem` could be placed not aligned with an MPU region, such that the some portion of "app_memory" would not actually be usable for applications,...
> If `MPU_MIN_ALIGN` never existed, would `_sappmem` instead be named `_ekernelmem`? (since it doesn't actually show the location of the first app, just the last address used by the kernel)....
I'm ok with some sort of `aes_bootup_delay_loops` variable in chip_config, that is set to 0 for fpga and something else for verilator.