Migration Error: Unable to Open data_pattern_generator Service in Quartus Prime Standard Edition

[DeadEnd]

Hi

I have a project written in Quartus II subscription version and I want to run it in Quartus 22.1 standard version.

So I ran Quartus with .QDF file, and in the top left corner of the screen, it said that I need to do an IP upgrade, and I went ahead and do it, and it said that it's done.

I programmed the Stratix V well with the SOF file, but when I ran it through the .tcl file, I got an error that the data_pattern_generator service could not be opened.

The .tcl file is trying to do something to check data integrity using the BER function, and I know it should use the data_pattern_generator in Qsys.

In conclusion, I think that this error is caused by a poor or problematic migration of Qsys.

The question is below, and the error log is below the question

1. Is there any other way to migrate from the II subscription version to prime standard version than what I did above?
2. If you can look at the error below and figure out what the problem is, could let me know?
3. As shown in the attached screen shot, when I opened the Qsys file in platform Designer, there were 6 warning entries in the message field, is this a problem? 
4. Or do you have any additional information you need to troubleshoot the problem? (if you need a .tcl file or somthing, I will attach it)

I would be very greatful if you could help me solve the problem.

====================================================================

-. Error Log

error: data_pattern_generator_is_generating: /devices/5SGXEA7H(1|2|2ES|3|3ES)|..@1#USB-0/(link)/JTAG/sld_hub.node_0/phy_0/master_0.master/data_pattern_generator_0.csr_slave/driver is not an open data_pattern_generator service

    while executing

"data_pattern_generator_is_generating $generator_path"
    (procedure "data_pattern_generator_config_set" line 2)
    invoked from within

"data_pattern_generator_config_set $generator_path $generator_data_pattern($tx_logical_channel) $enable_preamble $generator_preamble_word($tx_logical_c..."
    ("foreach" body line 24)
    invoked from within

"foreach logical_link_pair $logical_link_pairs {
           set tx_logical_channel [lindex $logical_link_pair 0]
           set rx_logical_channel [lindex $logical_link_p..."
    (file "eyeQ8.tcl" line 148)
    invoked from within

"source eyeQ8.tcl"

[SyafieqS · Accepted solution]

Normally IP migration or device migration, from diff version or edition, sometime there will be an issue.

If the gap of the prior tool is big, better things to do is to instantiate directly the IP from catalog and compile.

Also, need to check as well the IP version, big gap might have issue (of course due to IP will keep updating for improvement and might be not fit with your design).

[DeadEnd]

Sorry for late response,

Thank you for your advise, so I'll try to migrate the IP version again.

[SyafieqS]

Let me know if there is any update

[SyafieqS]

 I now transition this thread to community support. If you have a new question, Please login to https://supporttickets.intel.com/, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.

p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution, give Kudos and rate 5/5 survey