Jump to content


importing FSL IP for microblaze into EDK


  • You cannot reply to this topic
2 replies to this topic

#1 zje

    Member

  • Members
  • PipPip
  • 11 posts

Posted 12 May 2009 - 04:55 PM

How would I got about importing a pcore compiled by impulseC to EDK on a different machine?
I tried using the import peripheral wizard and everything works fine up until the bus interface port mapping.

The reset and clock ports map fine, but everything else only has one option: "FSL1_M_Full"
The IP core import wizard refuses to work when multiple bus connections are assigned to the same port.

If I select only slave, the results are the same.

Here is what the output looks like:


Any insight would be great!
Is there a directory I can just copy my "hw" folder into for it to be imported into EDK or is that not how this sort of thing works?

Thanks!

#2 zje

    Member

  • Members
  • PipPip
  • 11 posts

Posted 13 May 2009 - 09:17 AM

It seems that copying the files straight into the "pcores" directory in the project works. I'm at a loss for how to use the "create and import peripheral wizard."
Now I just need to debug my software...

#3 RalphBodenner

    Advanced Member

  • Admin
  • PipPipPip
  • 348 posts

Posted 18 May 2009 - 03:22 PM

You can "Export Generated Hardware" from CoDeveloper to copy the files that make up a pcore into a subdirectory you specify of the Impulse C project. Either create an EDK project in that export directory, or copy the contents of the export directory into your project. It should then appear on a list of cores in EDK--see the Help file for MicroBlaze PSPs for more details on where the core will show up (Help > Platform Support Package Help menu, then select "PSP_Xilinx_Microblaze.chm").

Regards,
Ralph
Ralph Bodenner
Impulse Accelerated Technologies, Inc.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users