Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
B bootrom
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kestrel Collaboration
  • Kestrel Firmware
  • bootrom
  • Merge requests
  • !16

Closed
Created Mar 11, 2021 by Jonathan Currier@dormitoMaintainer
  • Report abuse
Report abuse

Address space remapping means rom will no longer be at 0x0

  • Overview 2
  • Commits 1
  • Changes 1

Because the remapping means rom no longer starts at 0x0, this assert will break.

I thought about checking that _start == 0x40000000 but ultimately that did not seem like a good idea to me either. If you have any alternatives to suggest besides dropping the assert I'd be interested.

See also:

https://gitlab.raptorengineering.com/kestrel-collaboration/kestrel-litex/litex-boards/-/merge_requests/5 (and related)

Edited Mar 11, 2021 by Jonathan Currier
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: dormito/address-space-remap

Powered by Integricloud