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
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cores > Message List > Message Post

    Message

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

    From: Armando Astarloa<jtpascua@b...>
    Date: Wed Sep 21 15:22:29 CEST 2005
    Subject: [oc] OPB2WB wrapper + SPI lite
    Top

    Hello,

    I am wrapping the Ethernet 10/1000 opencores IP with
    OPB2WB fot the slave WB if and WB2OPB for the master WB.

    Although the resulting design is synthesizable, the memory range for
    the OPB2WB (00h-FFh) is not big enough for that core (it needs
    from 0x000h to 0x7ff).

    Is possible the extension?

    Thanks,

    Armando


    At 01:11 03/06/2005 +0700, you wrote:
    >On Thu, 2005-06-02 at 15:42 +0200, secamiei@b... wrote:
    > > I checked with Chipscope, and the transfer is acknowledged only when
    > > the address is in range 0x80000000 ->0x800000ff. If you change the
    > > address in
    > > EDK, and you write to that address, the transfer is not acknowledged.
    > > Now I am trying to build a system with 2 SPI cores (attached to the
    > > OPB with 2 OPB2WB wrappers). I assigned in EDK 0x80000000->0x800000ff
    > > to the first OPB2WB wrapper (connected to the first SPI core) and
    > > 0x80000100->0x800001ff. I hope the wrappers will accept those address
    > > ranges.
    >
    >
    >The problem is that when I ship a netlist version of this wrapper,
    >the parameters C_BASEADDR and C_HIGHADDR get compiled in to the
    >netlist. I honestly do not know how to work around this problem.
    >One way would be provide a non OPB input "SELECT" which would
    >force the address decoding outside the core, but would require
    >another level of abstraction.
    >
    >If somebody could figure out how to solve this problem, I would
    >be happy to create a new release of the OPB/WB wrapper ...
    >
    >Regards,
    >rudi
    >=============================================================
    >Rudolf Usselmann, ASICS World Services, http://www.asics.ws
    >Your Partner for IP Cores, Design, Verification and Synthesis
    >
    >_______________________________________________
    >http://www.opencores.org/mailman/listinfo/cores

    ----------------------------------------------------------------------------------------------------------------------

    Armando Astarloa Cuéllar - Universidad del Pais Vasco UPV/EHU
    Tecnología Electrónica
    Departamento de Electrónica y Telecomunicaciones
    Escuela Superior de Ingenieros - Email: jtpascua@b...
    Ald. de Urquijo s/n Tel.: 34 - 94 - 601 73 04
    48013 BILBAO (SPAIN) Fax.: 34 - 94 - 601 42 59
    URL : http://det.bi.ehu.es/~apert
    ----------------------------------------------------------------------------------------------------------------------


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