Why are bad blocks in NAND memory being used after programming with quartus_hps? - Why are bad blocks in NAND memory being used after programming with quartus_hps? Description The quartus_hps tool erases both the factory NAND bad block markers and the software maintained bad block tables. This can lead to unreliable NAND operation. Symptoms include intermittent or permanent failure to boot from NAND, failure to configure the FPGA from the HPS using NAND and also NAND cyclic redundancy check (CRC) errors. Resolution To work around this problem, use U-Boot or Linux to program the NAND memory. Note: U-boot can be loaded via the Arm* Development Studio for Intel® SoC FPGA debugger, or from FPGA on-chip-ram, and the HPS ethernet or the debugger can be used to transfer the NAND Image to SDRAM for use by u-boot for programming. This problem is scheduled to be fixed in a future release of the Intel® Quartus® Prime Software. Custom Fields values: ['novalue'] Troubleshooting FB: 238484 366060; False ['novalue'] ['FPGA Dev Tools Quartus II Software'] 17.0 14.0 ['Cyclone® V SE FPGA', 'Cyclone® V ST FPGA', 'Cyclone® V SX FPGA', 'Arria® 10 SX FPGA'] ['Embedded Dev Tools SoC Suite'] ['novalue'] ['novalue']