10. Advanced Troubleshooting
- Your component behaves differently in simulation and emulation.
- Your component has unexpectedly poor performance, resource utilization, or both.
(Windows only) Long Path Issues
Components kept in directories that result in a long path name might not compile properly or fail in simulation. Check your compilation log or simulation log (debug.log) to determine if the path length is a cause of the failures. Errors that indicate that a file could not be found can indicate that your paths might be too long.
The Intel® HLS Compiler uses the component name in many of the directories that it creates. Long component names can introduce long path issues even if your component is in a relatively shallow location in your directory structure.
- Move your component up the directory hierarchy.
- Use a shorter name for your component.
Did you find the information on this page useful?