[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
R: [microblaze-uclinux] opb2Wb Wrapper
Of course....
The blinker works wery well, the same
I can't say for the wrapper.
Egidio
-----Messaggio originale-----
Da: owner-microblaze-uclinux@itee.uq.edu.au
[mailto:owner-microblaze-uclinux@itee.uq.edu.au]Per conto di Kevin
Somervill
Inviato: giovedi 16 dicembre 2004 18.35
A: microblaze-uclinux@itee.uq.edu.au
Oggetto: RE: [microblaze-uclinux] opb2Wb Wrapper
Hello Rich,
I believe that Edigio is referring to the blinker, not the opb2wb. Have
you contacted the opb2wb author?
/ks
|-----Original Message-----
|From: owner-microblaze-uclinux@itee.uq.edu.au
|[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of
|Richard Klosinski
|Sent: Thursday, December 16, 2004 12:24 AM
|To: microblaze-uclinux@itee.uq.edu.au
|Subject: RE: [microblaze-uclinux] opb2Wb Wrapper
|
|
|Did you get the example to work, or the opb2wb wrapper? As far
|as I can tell, the opb2wb is still missing the obp2wblib file,
|and there seems to be a misspelled signal name (rst).
|
|If someone was able to synthesis this, I sure would like to know how.
|
|rich
|
|-----Original Message-----
|From: owner-microblaze-uclinux@itee.uq.edu.au
|[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of
|Egidio Caricati
|Sent: Wednesday, December 15, 2004 8:20 AM
|To: microblaze-uclinux@itee.uq.edu.au
|Subject: R: [microblaze-uclinux] opb2Wb Wrapper
|
|I have tried your example and it's work fine....:-)) Thanks, Egidio
|
|-----Messaggio originale-----
|Da: owner-microblaze-uclinux@itee.uq.edu.au
|[mailto:owner-microblaze-uclinux@itee.uq.edu.au]Per conto di
|Kevin Somervill
|Inviato: mercoledi 15 dicembre 2004 15.41
|A: microblaze-uclinux@itee.uq.edu.au
|Oggetto: RE: [microblaze-uclinux] opb2Wb Wrapper
|
|
|Hello Edigio,
|I've had to do this type of thing to make use of a GCLK input
|as a general I/O in EDK (otherwise you have to leave EDK and
|stuff in a bufg). For examples, you can look in the
|$EDK_INSTALL_DIR\hw\XilinxProcessorIPLib\pcores\util_bus_split_v1_00_a
|for a Xilinx provided example and I am attaching a simple
|blinker example that doesn't even connect to any of the
|microblaze stuff. Both of these show how to instantiate
|general logic in EDK that may or may not be related to the
|microblaze system. For the blinker, put it into your global
|user cores directory or your project pcores and you can then
|add it in the add edit cores dialog.
|
|Any other discussion about how to do this should be moved to a
|Xilinx forum as it has wandered off topic for this list.
|
|/ks
|
||-----Original Message-----
||From: owner-microblaze-uclinux@itee.uq.edu.au
||[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of Egidio
||Caricati
||Sent: Wednesday, December 15, 2004 6:43 AM
||To: microblaze-uclinux@itee.uq.edu.au
||Subject: R: [microblaze-uclinux] opb2Wb Wrapper
||
||
||I'm sorry but I can't understand,
||there is someone who cam provide un examples?
||thanks in advance
||Egidio
||
||-----Messaggio originale-----
||Da: owner-microblaze-uclinux@itee.uq.edu.au
||[mailto:owner-microblaze-uclinux@itee.uq.edu.au]Per conto di Kevin
||Somervill
||Inviato: lunedi 13 dicembre 2004 14.18
||A: microblaze-uclinux@itee.uq.edu.au
||Oggetto: Re: [microblaze-uclinux] opb2Wb Wrapper
||
||
||Hello Rich and John,
||
||>> I should have been more clearer. I'm using ISE to implement other
||>> parts of my design. Besides that, I'm not sure how to add wishbone
||>> peripherals using only EDK once I've added the opb2wb
|component w/o
||>> using IDE.
||
||You can look in one of John's older mbvanilla releases for the
||"my_inverter" which shows how to instantiate generic logic. So long as
||you describe the block correctly with the mpd/pao files as John
||mentioned, you can instantiated any generic logic. Even if it's not
||related to an embedded processor.
||
||> platgen is fully data driven, it should be possible to describe the
||> wishbone bus with a typical mpd/pao file, then have it create
||> connectivity for wishbone cores etc. I haven't actually
||tried it, but
||> i'm pretty sure custom buses can be supported like this.
||
||I've put lot's of stuff into designs that had nothing to do with the
||microblaze and this is a convenient way to go. The constructs used in
||making EDK compatible
|| components also serve to encourage fairly generic, parameterizable
||blocks. And it's a lot better than jumping back and forth between xps
||and ise.
||
||/ks
||
||___________________________
||microblaze-uclinux mailing list microblaze-uclinux@itee.uq.edu.au
||Project Home Page :
|http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
|Mailing List Archive :
|http://www.itee.uq.edu.au/~listarch/microblaze-|uclinux/
|
|
|___________________________
|microblaze-uclinux mailing list
|microblaze-uclinux@itee.uq.edu.au Project Home Page :
http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/