Honour instr_storage_offset when generating the HBM image - #9
Merged
Merged
Conversation
generate_hbm accepted instr_storage_offset and never used it, so the instruction section always landed at offset zero while the core fetched at pc plus the offset baked into configuration.svh. The writer now pads zero rows up to the offset and fails closed when the offset is not row-aligned or would land inside written data.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
generate_hbmignoredinstr_storage_offsetgenerate_hbmacceptedinstr_storage_offsetand never used it, so the instruction section always landed at offset zero while the core fetched atpc + INSTRUCTION_STORAGE_OFFSETas baked intoconfiguration.svh.Fix
The writer now pads zero rows up to the offset and fails closed when the offset is not row-aligned or would land inside already-written data.