From d4b9b2ffdcdb9bac66788ab7296e93a87e0d1306 Mon Sep 17 00:00:00 2001 From: hyperslv Date: Sat, 20 Jun 2020 13:23:30 +0300 Subject: [PATCH 1/2] Note on how to rebuild if memory.x is changed --- src/start/hardware.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/start/hardware.md b/src/start/hardware.md index d8b23076..c1cce81a 100644 --- a/src/start/hardware.md +++ b/src/start/hardware.md @@ -78,6 +78,9 @@ MEMORY RAM : ORIGIN = 0x20000000, LENGTH = 40K } ``` +> **NOTE**: If you for some reason changed the `memory.x` file after you had made +> the first build of a specific build target, then do `cargo clean` before +> `cargo build`, because `cargo build` does not track updates of `memory.x`. Make sure the `debug::exit()` call is commented out or removed, it is used only for running in QEMU. From e57e1c83e217b187b61560eb4547ecef7fad8df5 Mon Sep 17 00:00:00 2001 From: hyperslv Date: Sun, 21 Jun 2020 01:16:13 +0300 Subject: [PATCH 2/2] Change to 'may not' as the reviewer suggested --- src/start/hardware.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/start/hardware.md b/src/start/hardware.md index c1cce81a..6b212df0 100644 --- a/src/start/hardware.md +++ b/src/start/hardware.md @@ -80,7 +80,7 @@ MEMORY ``` > **NOTE**: If you for some reason changed the `memory.x` file after you had made > the first build of a specific build target, then do `cargo clean` before -> `cargo build`, because `cargo build` does not track updates of `memory.x`. +> `cargo build`, because `cargo build` may not track updates of `memory.x`. Make sure the `debug::exit()` call is commented out or removed, it is used only for running in QEMU.