Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Assert rom_backup_data_address stays within RAM at link time#129

Open
dogruis wants to merge 1 commit into
dciabrin:masterdciabrin/ngdevkit:masterfrom
dogruis:assert-rom-backup-data-addressdogruis/ngdevkit:assert-rom-backup-data-addressCopy head branch name to clipboard
Open

Assert rom_backup_data_address stays within RAM at link time#129
dogruis wants to merge 1 commit into
dciabrin:masterdciabrin/ngdevkit:masterfrom
dogruis:assert-rom-backup-data-addressdogruis/ngdevkit:assert-rom-backup-data-addressCopy head branch name to clipboard

Conversation

@dogruis

@dogruis dogruis commented May 22, 2026

Copy link
Copy Markdown
Contributor

Setting rom_backup_data_address to an invalid value (below ORIGIN(RAM) or past ORIGIN(RAM) + LENGTH(RAM)) currently produces a working ELF whose runtime accesses to .bss.bram silently corrupt memory. Two ASSERT statements in runtime/ngdevkit.ld catch the misconfiguration at link time without changing behavior for any valid placement.

Setting rom_backup_data_address to an invalid value (below ORIGIN(RAM)
or past ORIGIN(RAM) + LENGTH(RAM)) currently produces a working ELF
whose runtime accesses to .bss.bram silently corrupt memory. Two
ASSERTs catch the misconfiguration at link time without changing
behavior for valid placements.
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

Successfully merging this pull request may close these issues.

1 participant

Morty Proxy This is a proxified and sanitized view of the page, visit original site.