ContributionsMost RecentMost LikesSolutionsRe: Quartus Prime Pro 23.4 internal error during fit when module marked as a partition Is there a flow by which we can provide a testcase privately and under NDA? I have been unable to simplify the test case in a way which reproduces the error and does not have proprietary code. Otherwise, yes, we will use 23.2 as a workaround. Thanks so much, Derek Re: Quartus Prime Pro 23.4 internal error during fit when module marked as a partition I am unable to provide the code in its current state due to IP concerns but am working to put together a reduced form which still exhibits the issue. Thx, Derek Re: Quartus Prime Pro 23.4 internal error during fit when module marked as a partition Just to follow up ... My scripts at this point are quite bare bones so as to run Quartus in its most mainstream (ie. bug free?) configuration. There is nothing in them to steer either toward or away from DNI ... Thx, Derek Re: Quartus Prime Pro 23.4 internal error during fit when module marked as a partition Indeed, Quartus Pro 23.2 is able to complete implementation of my design even when marked as a partition (and placed in a logic lock region). HOWEVER, I am not sure that 23.2 is actually "DNI"-free. I see the message below during my from-RTL synthesis and fit. Info: Running Quartus Prime Synthesis Info: Version 23.2.0 Build 94 06/14/2023 SC Pro Edition Info: Processing started: Fri Mar 1 11:28:22 2024 Info: System process ID: 978588 Info: Command: quartus_syn --dni --read_settings_files=on --write_settings_files=off apipe_top -c apipe_top Info: The application is running in 'DNI' mode. Thx for the suggestion. Quartus Prime Pro 23.4 internal error during fit when module marked as a partition I am working to package my portion of a Stratix 10 design so that it can be used as a "finalized" partition within a larger FPGA implementation. However, when I mark my top level module as a partition, Quartus crashes with an internal error 13% of the way through the fitter place stage. Without the partition, implementation is successful. With a logic lock region for my top level module but no partition, implementation is also successful. Any suggestions how I can avoid the internal error? Details: Quartus Pro v23.4 (also crashes on v23.3 but I upgraded to the latest to check if resolved) Install-default Quartus settings Stratix 10, my portion of the design uses ~15% of device resources Ubuntu 20.04.3 LTS AMD Ryzen thread-ripper 3970x 32-core 256 GB Crash log attached Solved