rust-embedded / rust-embedded/cortex-m
region 'FLASH' already defined
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 202
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 2
Description
I seem to have stumbled accross this issue region 'FLASH' already defined but the thread is closed by now.
The proposed fix (using the GNU linker) does work for me.
I wonder if I'm doing something wrong or if there's a bug here.
I set up a reproduction here:
https://github.com/dimpolo/linkerbug
The goal would be to have a bootloader sit at the first 32K of FLASH and the main application at the 32K after.
Steps to reproduce:
git clone https://github.com/dimpolo/linkerbug.git
cd linkerbug/bootloader
cargo build
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Clone the linked dimpolo/linkerbug reproduction, enter linkerbug/bootloader, and run cargo build to reproduce the duplicate FLASH region error. Compare the failing linker setup with the proposed GNU linker workaround and verify a fix that keeps the bootloader in the first 32K of FLASH and the application after it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100