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 > Pci > Message List > Message Post

    Message

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

    From: Klaas Gadeyne<klaas.gadeyne@f...>
    Date: Wed Jun 13 15:10:01 CEST 2007
    Subject: [pci] raggedstone pci core
    Top
    I am trying the opencores pci core from
    <http://www.opencores.org/projects.cgi/web/raggedstone/overview> on a
    raggedstone1 board with a spartan xc3s1500 on board.

    I slightly modified the makefiles [*], but this doesn't seem to do the
    trick. That is, I can load the driver, but the pc freezes immediately
    after loading the driver (i.e.~the device_probe() function returns
    succesfully, but then the system locks up completely).

    In the raggedstone1 faq I found this
    <quote>
    "OPENCORES BASED PCI DESIGN HANGS PC" - First check the issue
    above. If the mod is applied another reason that a PC hangs is the the
    REQ# line is in it's active state permanently. Some Opencores designs
    have not supported this line but it should be parked into a high level
    either with a FPGA pullup or drive to '1'. Failure to do this make a
    lock up of the PCI with the Raggedstone1 being granted the bus and
    never releasing it to other bus masters.
    </quote>

    I tried adding a signal req to the pci2wishbone bridge core and put
    that permanently to one, but that didn't improve things.
    Neither did it help to declare the req signal as PULLUP in the pin
    assignment.

    Now I was wondering (being a complete FPGA/VHDL newbie), is there
    anything besides the Makefiles I should port to get things operational
    on the 1500k spartan?

    Thanks for any advice,

    Klaas Gadeyne

    [*] For the record:
    root at einstein:~/CVS/raggedstone #
    cvs diff Makefile
    Index: Makefile
    ===================================================================
    RCS file: /cvsroot/anonymous/raggedstone/Makefile,v
    retrieving revision 1.1
    diff -r1.1 Makefile
    9a10,12
    > FPGA := xc3s1500-fg456-4
    > # FPGA := xc3s400-fg456-4
    >
    33c36
    < ngdbuild -intstyle ise -dd "$(PWD)/_ngo" -nt timestamp -uc
    $(PROJECT).ucf -p xc3s400-fg456-4 $(PROJECT).ngc $(PROJECT).ngd &>
    tmp/build.ngdbuild.log
    ---
    > ngdbuild -intstyle ise -dd "$(PWD)/_ngo" -nt timestamp -uc
    $(PROJECT).ucf -p $(FPGA) $(PROJECT).ngc $(PROJECT).ngd &>
    tmp/build.ngdbuild.log
    38c41
    < map -intstyle ise -p xc3s400-fg456-4 -cm area -pr b -k 4 -c
    100 -o $(PROJECT)_map.ncd $(PROJECT).ngd $(PROJECT).pcf &>
    tmp/build.map.log
    ---
    > map -intstyle ise -p $(FPGA) -cm area -pr b -k 4 -c 100 -o
    $(PROJECT)_map.ncd $(PROJECT).ngd $(PROJECT).pcf &> tmp/build.map.log
    root at einstein:~/CVS/raggedstone #
    cvs diff pci_7seg.xst
    Index: pci_7seg.xst
    ===================================================================
    RCS file: /cvsroot/anonymous/raggedstone/pci_7seg.xst,v
    retrieving revision 1.1
    diff -r1.1 pci_7seg.xst
    7c7
    < -p xc3s400-4-fg456
    ---
    > -p xc3s1500-4-fg456

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