Skip to content
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.

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

help understanding relationship between memory.x and base offset #6

Closed
TheButlah opened this issue Dec 18, 2021 · 2 comments
Closed

Comments

@TheButlah
Copy link

Hi, I was told that for my particular bootloader, I should set -b to 0x26000, which accounts for the adafruit bootloader + the proprietary Bluetooth stack that the nrf52840 uses.

Should I set memory.x to 0x26000? What exactly is the relationship between memory.x and the base offset?

@jacobrosenthal
Copy link
Contributor

Yeah the base is what flash address the tool writes your image to. The flash origin of the memory.x is the base offset. So if your chips flash memory starts at 0x0 like nordics do, its 0x0.

Complications occur when you have a softdevice or a bootloader or something which is placed at 0x0 and you cant overwrite, so you have to avoid it. which is a bit out of scope of this tool.

You can google something like "nordic softdevice app ram base address" and see tutorials and images of different softdevices (plus the mbr) and how much space they require.

But assuming you have a working rust app, whatever address you or whoever calculated your memory.x flash origin to, thats what you use.

@jacobrosenthal
Copy link
Contributor

Btw we all hang out in https://matrix.to/#/#rust-embedded:matrix.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants