[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [pci] about simulation



Hi!

I'm not familiar with CardBus, so I can't really tell you what to do.
But, if I suppose, this is P-T-P and that you are making a CardBus card to
plug it into the host system, I would say the following:
- you have to define a PCI Bridge as GUEST
- hardwire its IDSEL pin to constant 1
- modify a testbench, so only one behavioral device is used (master/target)

So, you should change all references to behavioral device 2 to reference
behavioral device 1 instead. I don't know about other devices, since I don't
know which bus commands are supported on CardBus. I also don't know what
kind of arbiter CardBus requires.

Hope this helps a bit !

Regards,
Miha Dolenc

----- Original Message -----
From: <random_user@163.com>
To: <pci@opencores.org>
Sent: Sunday, July 28, 2002 7:29 AM
Subject: Re: [pci] about simulation


>     Thank you very much for your kind help!
>     But,taking the difference between  P-T-P and sharded bus into
> account, would you give me some advices about how to modify the
> testbench to be used in  a cardbus to wishbone bridge ?
>     Is the configuration cycle initiated by the host or one of the MASTER
> card?
>
> regards,
> wangc
>
>
> ----- Original Message -----
> From: "Miha Dolenc" <mihad@o... >
> To: <pci@o... >
> Date: Fri, 26 Jul 2002 09:20:02 +0200
> Subject: Re: [pci] about simulation
>
> >
> >
> > Point to Point means that every configuration cycle the device
> > detects is
> > meant for it, so it has to be accepted. Therefore I suppose, you do
> > not need
> > an IDSEL pin. You should hardwire IDSEL pin of your "CardBus"
> > target to
> > constant 1.
> >
> > Regards,
> > Miha Dolenc
> >
> > ----- Original Message -----
> > From: <random_user@1... >
> > To: <pci@o... >
> > Sent: Thursday, July 25, 2002 7:59 AM
> > Subject: [pci] about simulation
> >
> >
> > > Hi all,
> > >      I am now working at the testbench and I have met with
> > some
> > > problems.
> > >      1.Why there are two pci_behaviorial_device modules in the
> > > testbench? Isn't one enough?
> > >      2.I am trying to modify the testbench to be used in a
> > CardBus
> > > project.But in the CardBus spec.there is no idsel pin,so when
> > I use this
> > > testbench,an error occured:more than one device drive devsel
> > > simultaneously! When I read the CardBus spec.,I noticed that
> > the
> > > Cardbus is a point to point bus,while PCI is a shared bus.What
> > on earth
> > > does this mean and HOW would this influence the configuration
> > access?
> > >
> > > Thanks!
> > >
> > > regards,
> > > wangc
> > >
> > >
> >
> --
> To unsubscribe from pci mailing list please visit
http://www.opencores.org/mailinglists.shtml
>


--
To unsubscribe from pci mailing list please visit http://www.opencores.org/mailinglists.shtml