I have been working with Labs 2 the last few weeks. I believe it catches much more errors than Labs 1, but I still frequently get the following error from Vivado:
ERROR: [Common 17-70] Application Exception: Failed to launch run ‘impl_1’ due to failures in the following run(s):synth_1These failed run(s) need to be reset prior to launching ‘impl_1’ again.
I get this error, even though Labs2 says my project is error free. Vivado just stops at this point, providing no further information.
I have two problems:
1. I have no idea how to reset synth_1 or whatever they are asking me to do. I know that throwing out the whole build directory doesn’t work.
2. I have no idea what is wrong with my project when this happens. Neither Labs 2 nor Vivado give me the slightest clue what went wrong.
Hi, I don’t know the cause of this issue, but you can reset a run in Vivado by doing this :
In the “Design Runs” tab (usually at the bottom of the main window), click on the run you want to reset :
Does anyone know anything about what causes the behavior in Vivado?
I am usually pretty good at trouble-shooting, but I have had no luck in trying to isolate the source. It has occurred several times in several different projects. I can only fix by a drastic work-around or abandoning the project. As I said, Labs 2 doesn’t see any errors.
If you can provide an example on how to reproduce it that would be incredibly helpful.
Vivado’s error doesn’t make a whole lot of sense because the entire Vivado project is recreated at build time so it’s already fresh. What would you be resetting?
Problem Resolved (Sort Of) I decided to work harder at figuring out the problem. (I didn’t want to start asking Justin to debug my code, in spite of the nice offer.)
I found the source of the error. I moved an existing ROM module of my own making from Labs1 over to Labs2. It stores characters, so its input is address and its output is char. “char” must be a keyword somewhere. From Labs1, this same version of Vivado thought this was fine. But when the exact same module is run from Labs2, the use of char causes Vivado to produce this error. Perhaps there is some subtle thing between Labs1 and Labs 2 that makes Vivado process “char” differently.
And as Justin pointed out, since Vivado starts out from scratch each time, changing char to char1, or anything else, causes Vivado to run fine without resetting anything, in spite of the error message.
Was the ROM written in Lucid or Verilog? If it was Verilog, know that the IDE does almost no error checking other than syntax at this point.
I ran into a similar issue a week or so ago with a different keyword. I believe it stems from V1 converting to Verilog but V2 converting to SystemVerilog. The list of keywords needs to be expanded it seems.
If your module was Verilog it’s likely caused by renaming the files to .sv instead of .v. I could add an exception for Verilog during the build process.
It was written in Lucid. I still don’t know why “char” is a restricted work. It worked fine on the same version of Vivado, when I was using it with Labs 1.
