LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Find Resources
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Openrisc > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: =?unknown-8bit?Q?Gy=F6rgy?= 'nog' Jeney<nog@s...>
    Date: Wed Jun 29 16:55:18 CEST 2005
    Subject: [openrisc] [or1ksim #115] Fix gdb load command
    Top
    Hi,

    People actually want this broken behaviour, so here is a patch to break
    perfectly correct behaviour. If your FLASH is not writeable by the cpu core
    then it's not writeable by the debug core either. I don't see why this has to
    be special cased. I don't use gdb much so I don't really care...

    ChangeLog:
    * Make non-writeable memory writeable by the debug core.

    nog.
    -------------- next part --------------
    diff -upr --unidirectional-new-file ./debug/debug_unit.c /home/nog/or1ksim-ac/debug/debug_unit.c
    --- ./debug/debug_unit.c 2005-06-28 15:41:34.000000000 +0200
    +++ /home/nog/or1ksim-ac/debug/debug_unit.c 2005-06-18 18:56:01.000000000 +0200
    @@ -381,7 +396,7 @@ int debug_set_mem (unsigned int address,
    else {
    // circumvent the read-only check usually done for mem accesses
    // data is in host order, because that's what set_direct32 needs
    - set_direct32(address, data, 0, 0);
    + set_program32(address, data);
    }
    return err;
    }

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.