EDK Bug ?

Dec 23, 2004 1 Replies

When creating custom IP Cores for inclusion in to EDK projects, I stumbled across the following problem:



If a custom core (in VHDL) does not have a generic section as for example:


----------------------------------------------------------- library IEEE; use IEEE.STD_LOGIC_1164.ALL; use IEEE.STD_LOGIC_ARITH.ALL; use IEEE.STD_LOGIC_UNSIGNED.ALL; library UNISIM; use UNISIM.VComponents.all;



entity my_inverter is port ( I : in STD_LOGIC; O : out STD_LOGIC ); end my_inverter;



architecture arch_my_inverter of my_inverter is



begin O I, O => O );



end architecture STRUCTURE;



-----------------------------------------------------------



And than complains when compiling the code it just generated:



Compiling vhdl file /home/rudi/projects/system/synthesis/hdl/rst_inverter_wrapper.vhd in Library work. ERROR:HDLParsers:164 - /home/rudi/projects/system/synthesis/hdl/rst_inverter_wrapper.vhd Line 25. parse error, unexpected CLOSEPAR, expecting IDENTIFIER


Is this a bug or am I doing something wrong ? This occurs with EDK 6.2 and EDK 6.3 (both latest patch levels) on a linux system. Thanks ! rudi ============================================================= Rudolf Usselmann, ASICS World Services, http://www.asics.ws Your Partner for IP Cores, Design, Verification and Synthesis

Dear Mr Usselman,

the IP core you did include in your posting is originally from uClinux MB Vanilla distribution from John Williams. This IP core is defenetly useable in EDK 6.2 at least. EDK 6.3 has changed a little the .MPD parsing rules so for the 6.3 it should be modified a little. However I am 100% positive that John Williams has updated the MBvanilla and related IP cores to 6.3 as I do know that he works tightly with Xilinx EDKI group in order to work out the remainin issues that as until today still prevent the use of xilinx EDK GCC tools to succesfully compiled uClinux.

as of the problem with missing generics, here I can only suggest one generic rule for EDK - you simple have to find a way to make EDK happy, one way would be to add some dummy generics lets say C_FAMILY to the core that causes the problems with empty generic section.

hope it helps, Antti Lukats

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required