Qsys generation may get stuck when executing a pearl script associated with an On-Chip Memory component. In the "Generate" window, you may see the process stopped at a message such as following.
Info: onchip_memory_16bit: Generation command is [exec C:/altera/13.0sp1/quartus/bin/perl/bin/perl.exe -I C:/altera/13.0sp1/quartus/common/ip/altera/common/perl/5.8.3 -I C:/altera/13.0sp1/quartus/sopc_builder/bin/europa -I C:/altera/13.0sp1/quartus/sopc_builder/bin/perl_lib -I C:/altera/13.0sp1/quartus/sopc_builder/bin -I C:/altera/13.0sp1/quartus/../ip/altera/sopc_builder_ip/common -I C:/altera/13.0sp1/quartus/../ip/altera/sopc_builder_ip/altera_avalon_onchip_memory2 -- C:/altera/13.0sp1/quartus/../ip/altera/sopc_builder_ip/altera_avalon_onchip_memory2/generate_rtl.pl --name=my_system_onchip_memory_16bit --dir=C:/Users/xyz/AppData/Local/Temp/alt5967_7790742084512251913.dir/0002_onchip_memory_16bit_gen/ --quartus_dir=C:/altera/13.0sp1/quartus --verilog --config=C:/Users/xyz/AppData/Local/Temp/alt5967_7790742084512251913.dir/0002_onchip_memory_16bit_gen/
/my_system_onchip_memory_16bit_component_configuration.pl --do_build_sim=0 ]
This issue was observed on Windows systems using Quartus® II 13.0/sp1. To get out of the stuck condition, you'll need to open the task manager and kill the process "perl.exe *32". Killing the process will result in an error message, such as following, in the "Generate Completed" window.
Error: onchip_memory_16bit: Failed to generate module <memory component name>
The root cause of this issue is the following:
In the On-Chip Memory (RAM or ROM) component, if you enable the option "Enable In-System Memory Content Editor feature", the Instance ID has to be 4 characters long, and must not contain any numbers.
To workaround this issue, use a 4-character Instance ID name, without any numbers.
This issue will be fixed in a future software version.
