LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Sponsors
  • Mirrors
  • Logos
  • Contact us
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Overview :: News :: Architecture :: OpenRISC 1200 :: VMware image :: NEW GNU Toolchain Port :: Architectural Simulator :: Linux :: uClinux :: RTEMS :: ATS :: ORP :: ORPmon :: ORPsoc :: Survey :: Forum :: Silicon :: Downloads :: Tracker    

    OpenRISC 1000: ORP

    What is ORP?

    OpenRISC Reference Platform (ORP) is a definition of an OpenRISC based system. It defines how address space (memory map) is organized, how interrupts are allocated by peripheral devices, much like CHRP and PReP define PowerPC systems. Right now only very simple definition is available.
    An OpenRISC based system is either ORP compliant or not. The whole purpose of ORP is:

    • to have common OpenRISC platform that can share software
    • to allow easy creation of new OpenRISC based SoCs with short system verification time (you can reuse system level test cases, see this log file)
    Examples of ORP compliant components:
    • orpmon is an example of software that runs on all ORP compliant systems without the need to modify it. See orpmon page for more information.
    • orp_soc is an example of reference system-on-chip compliant with ORP definition. See orp_soc page for more information.


     

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