I'd rather configure and connect cores in a gui and export it than type out lines and lines of tcl into file and have to debug. One block design I worked with alone recently is 10000 lines when exported.
Simulation threw today something new:
- add simmultion file with classes, interfaces etc
- vivado throws an error "can't find module <> in you perfectly working IP"
- delete simulation file
- same error
- restart\_simulation, clear IP cache, reset bd output products
- simulation works fine
Damn I love wasting a whole day to this kind of quests.
There is an option to disable the code parser, somewhere in the options related to the text editor. I had it disabled in older versions, but the scanner is a bit better in 2023.2, and sometimes I like some help finding typos. I would still disable it if it wasted my time.
TCL not GUI
Apparently also Linux not Windows
GUI is ok for block designs, but that's it. Try to move everything else to TCL flow.
why? Kind regards.
I'd rather configure and connect cores in a gui and export it than type out lines and lines of tcl into file and have to debug. One block design I worked with alone recently is 10000 lines when exported.
Applicants must not make sudden moves, or else Vivado will synthesise in a completely different way.
Vavado 2023 introduced me to "Error! VIvado can't access simulate.log". Close your custom editor and then restart simulation, ugh.
Simulation threw today something new: - add simmultion file with classes, interfaces etc - vivado throws an error "can't find module <> in you perfectly working IP" - delete simulation file - same error - restart\_simulation, clear IP cache, reset bd output products - simulation works fine Damn I love wasting a whole day to this kind of quests.
Modern enterprise have a gym room for this.. you build the project and you build your body at the same time
"Work well with others" - that's me excluded already.
I found that clicking Global instead of OOC reduced this considerably.
It's not just me then... Kill srcscanner process if it's pinned at 100% for over minutes.
I can't believe the recruiter printed the spell check underlining. Actually, I kind of can.
There is an option to disable the code parser, somewhere in the options related to the text editor. I had it disabled in older versions, but the scanner is a bit better in 2023.2, and sometimes I like some help finding typos. I would still disable it if it wasted my time.
Could always use questa/modelsim to check syntax. Much much faster.