Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

Microblaze migration to new device

Status
Not open for further replies.
Y

ya_montazar

Member level 2
Joined
Feb 24, 2014
Messages
47
Helped
0
Reputation
0
Reaction score
0
Trophy points
6
Activity points
342
Hello all,
I have had an about complex project using Microblaze and so, Implemented in a v6-130t and ٍnow the employer asked me to displace it to v6-240t.
what I have done to do this migration is regenerateing all the componnets such as IPs for new device.
the problem is that in new project I can not program the fpga and debug the MBLAZE code via SDK as I could. and the elf file is now disapeared! how ever I build the code again and it does not generate new error.
should I design and build new Microblaze core?:bang:

thanks
 

Porting a design between parts in the sme family (Virtex 6) only requires that you change rhe part number and the ucf/xdc constraints to match the new pins and locations. If the parts selected have compatible pinouts and you didn't use a pin that was not part of the common pins, then you probably wouldn't even have to modify the ucf/xdc file.

Regenerating all the IP was unnecessary.
 
ads-ee said:
Porting a design between parts in the sme family (Virtex 6) only requires that you change rhe part number and the ucf/xdc constraints to match the new pins and locations. If the parts selected have compatible pinouts and you didn't use a pin that was not part of the common pins, then you probably wouldn't even have to modify the ucf/xdc file.

Regenerating all the IP was unnecessary.
Click to expand...

the target device and previous one are compatible. but especially the MBLAZE does not work,yet. however it seems the rtl codes work with no problem.
(regenerating IPs as I said means they just upgraded by software without any changes from me.)
 

In order to use SDK (assuming that you are using Vivado), one needs to first export the hardware. Could you do that successfully?
 

dpaul said:
In order to use SDK (assuming that you are using Vivado), one needs to first export the hardware. Could you do that successfully?
Click to expand...

if you had read my question you would see that I have told about virtex 6 device so it couldn't be in vivado ;) .

- - - Updated - - -

The Problem has been solved, and that was missing the elf file. so I add it manually and then synthesize it again....
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top