Thanks,
/Mikhail
/Mikhail
you can sometimes enable "early access" support, by changing some
things in the EDK,
or just be adding the new family to the MPD files
Antti
> you can sometimes enable "early access" support, by changing some things
> in the EDK,
> or just be adding the new family to the MPD files
Antti,
Have you actually tried this approach of "porting" MB to V6? I wonder how
much time I will have to spend and whether I will be able to estimate
performance this way...
Thanks,
/Mikhail
not with V6, with some previous version yes
Antti
I suggest to generate the XPS project for older FPGA like V5 or S3A
first. You can change the FPGA in project settings then.
Jan
MicroBlaze works fine in V6 and has so for some time now.
EDK will only make cores officially supported for an architecture if
we have proven the core in real hardware with production status of the
speed files.
By setting "Early access" for IP catalog in the XPS preferences, you
will see MicroBlaze in the IP catalog when you have selected V6 or S6,
provided that you have a ISE installation that supports V6/S6.
However BSB will not generate V6 or S6 systems yet since the cores
needs official approval first for BSB.
But just generate a system for V5 board in BSB and then change the
architecture to S6 or V6.
Remember that packages and pinout will most likely differ so you might
need to modify the system.ucf file if you want to create a bitfile.
Don't do this for MPMC based system since plenty of placement
constraints are architecture and board specific.
MicroBlaze in V6 runs at least one speed grade faster than in V5.
Göran Bilski