Xilinx Home
PicoBlaze
Register  ·  Sign In  ·  Help
Jump to Page:   1
  Reply   Reply  

Stuck with orignal code of KCPSM3
Options    Options  
frozen_relationships
Newbie
Posts: 3
Registered: 11-06-2009


frozen_relationships

Message 1 of 6

Viewed 171 times


hi there,

 

i have downloaded kcpsm3 for my xc3s700a fpga. But wothout changing anything, i made a project and added files in it, all files of verilog have been added, i am using ISE 11.1. As i add files that are compressed in KCPSM3 rar itself am getting about 450 warnings. 

 

 

Some of them are...

 

 WARNING:Xst:616 - Invalid property "XC_PROPS INIT": Did not attach to receive/kcuart/delay15_srl_0.


WARNING:Xst:616 - Invalid property "XC_PROPS INIT": Did not attach to processor/reg_loop_register_bit_3.

 

WARNING:Xst:2591 - "../../../../Verilog/kcuart_rx.v" line 472: attribute on instance <INIT> overrides generic/parameter on entity. It is possible that simulator will not take this attribute into account.


WARNING:Xst:2591 - "../../../../Verilog/kcuart_rx.v" line 485: attribute on instance <INIT> overrides generic/parameter on entity. It is possible that simulator will not take this attribute into account.


WARNING:Xst:2591 - "../../../../Verilog/kcuart_rx.v" line 498: attribute on instance <INIT> overrides generic/parameter on entity. It is possible that simulator will not take this attribute into account.

 

WARNING:Xst:2591 - "kcpsm3.v" line 794: attribute on instance <INIT> overrides generic/parameter on entity. It is possible

 

WARNING:Xst:2591 - "../../../../Verilog/kcuart_tx.v" line 227: attribute on instance <INIT> overrides generic/parameter on entity. It is possible that simulator will not take this attribute into account.

 

 

this is what i have already tried..

>i have changed the frequency matter... that is author has desgned it for 55MHz and i have 50 MHz on board.

>i have read the read me file. It tells to filter the warnings i have filtered them but it cannot be implemented on FPGA

>and the last thing i have found is in the read me  it has been written that

 

"you should globally replace the directives in the 'kcpsm3' and
'ROM_form' files to match the requirements of your synthesis tool"

 

i dont know how to do this.

 

All have i done by myself is the editing of UCF file which i copied from UART real time clock pdf. and changes the LOC according to my FPGA and synthesize the whole project for both 18ns and 20ns timing constraints.

 

I have tried everything i could.

 

Plz help me. I havent slept a long ago just bcoz of kcpsm3 is giving countless warnings and my impatience is increasing. Plz give a clear cut walkthrough of how to implement fresh copy of UART real time clock project in xilinx ISE widout countless warnings??? 

Kudos!
Solved!
Go to the Solution
Go to Solution
11-06-2009 05:35 PM
  Reply   Reply  

Re: Stuck with orignal code of KCPSM3
Options    Options  
greglondon
Visitor
Posts: 20
Registered: 11-05-2009


greglondon

Message 2 of 6

Viewed 168 times


From the readme somewhere in one of the packages: 

 

How to filter this message.

In Project navigator -> Edit -> Message Filters...

Check the box next to 'Filter enabled' and then save using File -> Save

Now return to your project and run XST again and when you return to the message filters

window you will find that all the warning messages have appeared in the lower half of the

screen.

Move any one of the XST 2185 messages into the top window (Click once on message to select

it and then click and drag it to the top window).

In the top window, select the box under 'Filter Text' and right click to choose the 'Delete'

option. This will change the text to read "blank" line "blank": Possible... etc. Now this one

filter will remove all of the 2185 warnings in one go.

Save the changes with File -> Save.

Now when running XST all of the 2185 messages will have been removed.

 

 

Kudos!
11-06-2009 05:38 PM
  Reply   Reply  

Re: Stuck with orignal code of KCPSM3
Options    Options  
frozen_relationships
Newbie
Posts: 3
Registered: 11-06-2009


frozen_relationships

Message 3 of 6

Viewed 166 times


Sir i have already done it, can u send me the working project file with all sources for UART real tile clock? So that i can figure out the errors i make
Kudos!
11-06-2009 05:41 PM
  Reply   Reply  

Re: Stuck with orignal code of KCPSM3
Options    Options  
greglondon
Visitor
Posts: 20
Registered: 11-05-2009


greglondon

Message 4 of 6

Viewed 153 times


edit -> message filters

 

I have two filters:

 

1

(green check mark)

program: xst

filter text ! Xst: 2591 .* * <*> overrides *. It is possible that simulator will not take this attribute into account.

 

2

(green check mark)

program: fuse

filter text ! Xst: 2591 .* * <*> overrides *. It is possible that simulator will not take this attribute into account.

 

Select each one, and make sure they say have the radio button selected that says:

 

"Filter All Instances -- Match message number"

 

When I added an error message, it kept adding it as "this instance only".

 

Kudos!
11-06-2009 06:21 PM
  Reply   Reply  

Re: Stuck with orignal code of KCPSM3
Options    Options  
greglondon
Visitor
Posts: 20
Registered: 11-05-2009


greglondon

Message 5 of 6

Viewed 152 times


>"you should globally replace the directives in the 'kcpsm3' and 'ROM_form'

>files to match the requirements of your synthesis tool"

>i dont know how to do this.

 

When you run the assembler, it reads ROM_form.v and ROM_form.vhd to generate the actual <your_rom>.v and <your_rom>.vhd files.

 

If you open the ROM_form files, you'll see they look like verilog and vhdl, but with templates here and there. If you need to change any parameters for synthesis, change the ROM_form file, rerun the assembler,and it will use the changes to ROM_form to generate new .v and .vhd files.

 

 

Kudos!
11-06-2009 06:30 PM
  Reply   Reply  

Re: Stuck with orignal code of KCPSM3
Options    Options  
frozen_relationships
Newbie
Posts: 3
Registered: 11-06-2009


frozen_relationships

Message 6 of 6

Viewed 127 times


Thank God at last its done,

 

the reason was i had to use JTAG_ROM_FORM.v and its vhd file to assemble my code which i did and got the result, THX all who helped me and SPECIAL THX TO KEN CHAPMAN FOR MAKING A TOY FOR ME TO PLAY AND INNOVATE WITH.

Kudos!
Accepted Solution
Accepted Solution
11-07-2009 08:49 AM
Jump to Page:   1