UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Adventurer
Adventurer
891 Views
Registered: ‎05-18-2017

FSM extraction for 2017.1 and 2018.1

Hi, there

 

Previously, I use VIVADO-2017.1 to synthesize the ARM cortex-R5 and DAPLITE. Everything is fine. For some reason, I have to move on to VIVADO-2018.1. So, i use exactly same code base with constrains ant TCL, but the bitfile from 2018.1 is not working. After debugging the SCH, VIVADO-2018.1 remove lots of lots module as the following figure. 

无标题.png

 

 

Then, we study the rumme.log and then find the difference for the FSM extraction between 2018.1 and 2017.1

 

2017.1 synthesize rumme.log

2017_1.png

 

2018.1 synthesize rumme.log

2018_1.png

 

So, the problem is the 2018.1 and 2017.1 have different strategy for the FSM extraction. Moreover, I also try different option for the 2018.1 FSM extraction, but always get same result. In a words, 2017.1 is OK, but 2018.1 is not. 

 

 

I attached the both synth runme.log. pls check. thanks

 

Ping Chen

 

2018.7.23

 

 

 

0 Kudos
5 Replies
Adventurer
Adventurer
862 Views
Registered: ‎05-18-2017

Re: FSM extraction for 2017.1 and 2018.1

just try 2018.2. same result. 

 

Regards

 

Ping Chen

 

2018.7.23

0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
825 Views
Registered: ‎02-16-2014

Re: FSM extraction for 2017.1 and 2018.1

Hi @chenpingx

 

Is it possible for you to share testcase to debug this issue?

0 Kudos
Moderator
Moderator
801 Views
Registered: ‎07-21-2014

Re: FSM extraction for 2017.1 and 2018.1

@chenpingx

 

Can you try manually extracting the FSM by using FSM_ENCODING attribute in RTL and let us know if that helps to proceed further?

Also, as mentioned by Manusha please share a test case for us to reproduce the issue at our end.

 

Thanks

Anusheel 

0 Kudos
Adventurer
Adventurer
782 Views
Registered: ‎05-18-2017

Re: FSM extraction for 2017.1 and 2018.1

Sorry. I could not send the file to xilinx. Just paste the state-machine here. Please check it. thanks

 

Ping Chen

 

2018.7.24

 

捕获.PNG

 

0 Kudos
Adventurer
Adventurer
653 Views
Registered: ‎05-18-2017

Re: FSM extraction for 2017.1 and 2018.1

i try (* fsm_encoding = "gray" *), but still fail on 2018. And, we also meet new problem with VIVADO-2017.1. One FSM is not inferred correctly by VIVADO. Any idea? thanks

 

BTW: I also attached the DAPApbMuxArbiter.v as reference. 

 

Ping Chen

 

2018.8.28

0 Kudos