Krus83
New ContributorJoined 4 years ago
User Profile
New Contributor
User Widgets
Contributions
Re: aocl-clang.exe - Entry Point Not Found
Hi, 1)possible to try to compile any example design that comes with hls installation. Same error 2)any chances do you have more recent hls version other than 18.1 lite to test on? Same error. 3) you mention you have a similar working system, is it hls 18.1 lite/quartus 18.1/ VS 2010 Ultimate? and are you able to compile the same design there? Yes. I have now several colleagues with the same problem and it seems to have come after windows update KB5008212. Uninstalling the update does not solve the problem. Thanks.Re: aocl-clang.exe - Entry Point Not Found
Hi, thank you for the fast response. All paths have been checked and compared with a working system and I can't see anything wrong there. No other versions of Quartus have been installed recently. Correct, 18.1 Lite is the one in use and was previously working. Thanks in advance.Re: aocl-clang.exe - Entry Point Not Found
Hi, The error is generated when using any i++ command regardless of which source file or -march=** is used. Windows 10 Quartus 18.1 (re-installed, no improvement) HLS 18.1 (re-installed, no improvement) Visual Studio 2010 Ultimate (re-installed, no improvement) Additionally, genereationlib.dll was replaced (no improvement) Thanks in advance.Standard interface start signal
Hi, I am trying to run a simple component with standard interfaces but whatever I set the start signal to, the component will automatically run. Does it have to do with the amount/kind of logic in the component? component unsigned char counter(unsigned char a){ return a; } I want to connect the start signal from the CALL conduit to a switch to activate the component but it always runs automatically whatever the control signals are set to. HLS version: 18.1 Quartus version: 18.1Re: HLS area report unreadable
Hi, I tried a few different browsers with the same result. HLS Version: 18.1 Status of other reports: Summary: no issues Loop analysis: no issues Area analysis of system: Any details regarding RAM are unreadable Area analysis of source: Any details regarding RAM are unreadable Component viewer: All details unreadable Memory viewer: All details unreadable Verification statistics: no issuesHLS actual vs estimated resource usage
When I do --quartus-compile for MAX10 the actual resource utilization in the summary report is correct (based on MAX10 M9K block ram). But the estimated resource usage shows approximately half and seems to be based on M20K memory. The same goes for area analysis of system/source. Are there parameters that can be modified for the compiler to base the estimated resource usage on M9K memory? thanks.
