NGDBuild Error 604

I have been playing around with a script provided by Synplicity to synthesize EDK projects using synplify. It basically replaces the directive in the makefile to point all synthesis actions to synplify. Actually, everything is synthesized in XST first, but the synplicity script deletes the ouput of that synthesis and uses synplify. So Synplify synthesizes the cores (all except the encrypted microblaze) and you end up with a bunch of ngc files for the cores and a system.edn file. All this works fine.

Once xflow is invoked, there are errors before it completes. I believe the first thing that xflow invokes is NGDBuild.exe. This should read in all the ngc files and the system.edn and then build a master netlist, right? Well it reports 4 errors. The following is one of them:

ERROR:NgdBuild:604 - logical block 'tx_data_control/tx_data_control/USER_LOGIC_I' with type 'user_logic_work_tx_data_control_wrapper_structure_0' could not be resolved. A pin name misspelling can cause this, a missing edif or ngc file, or the misspelling of a type name. Symbol 'user_logic_work_tx_data_control_wrapper_structure_0' is not supported in target 'spartan3'.

I have searched Xilinx' website and this forum, and there are reports of this problem, but none of the fixes seem to work...or even seem appropriate for what I am seeing. I DO NOT know if ngdbuild is outputting the first 4 errors it gets and then quits or if there are actually only 4 cores that are having the problem. They are all custom IP cores that are attached to the OPB bus. I have other cores that are attached to the bus too, but I don't get errors with them. So unless ngdbuild is only showing the 1st 4 errors, there is a problem with these 4 cores, but I can't figure it out.

The only thing I can think of is that there may be a limit to the number of characters allowed in the "type" field, but that doesn't seem right.

Any help would be appreciated!

Reply to
motty
Loading thread data ...

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.