Skip to content

Note on how to rebuild if memory.x is changed #253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bors merged 2 commits into from
Jun 20, 2020
Merged

Note on how to rebuild if memory.x is changed #253

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d4b9b2f
Note on how to rebuild if memory.x is changed
hyperslv Jun 20, 2020
e57e1c8
Change to 'may not' as the reviewer suggested
hyperslv Jun 20, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/start/hardware.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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` 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.
Expand Down