Skip to content

linker: Map vector table to RAM for AST1060 boot flow #21

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

stevenlee7189
Copy link
Collaborator

AST1060 does not support XIP; instead, its ROM code copies the entire firmware image from flash to RAM and begins execution there. To support this flow, the vector table must reside in RAM starting at address 0x00000000, rather than being mapped to flash as assumed by the default cortex-m-rt layout.

This change updates the linker script to correctly position the vector table for AST1060's ROM-based boot process.

AST1060 does not support XIP; instead, its ROM code copies the entire firmware
image from flash to RAM and begins execution there. To support this flow,
the vector table must reside in RAM starting at address 0x00000000, rather than
being mapped to flash as assumed by the default cortex-m-rt layout.

This change updates the linker script to correctly position the vector table
for AST1060's ROM-based boot process.

Signed-off-by: Steven Lee <[email protected]>
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