Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openocd
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • card10card10
  • openocd
  • Repository
Switch branch/tag
  • openocd
  • src
  • target
  • target.c
Find file BlameHistoryPermalink
  • Øyvind Harboe's avatar
    target: require working area for physical/virtual addresses to be specified · b5ce7fe8
    Øyvind Harboe authored Nov 02, 2009
    Fixed bug: if virtual address for working memory was not specified
    and MMU was enabled, then address 0 would be used.
    
    Require working address to be specified for both MMU enabled
    and disabled case.
    
    For some completely inexplicable reason this fixes the regression
    in svn 2646 for flash write in arm926ejs target. The logs showed
    that MMU was disabled in the case below:
    
    https://lists.berlios.de/pipermail/openocd-development/2009-November/011882.html
    
    
    
    Signed-off-by: default avatarØyvind Harboe <oyvind.harboe@zylin.com>
    b5ce7fe8