Agilex3 dcio parsing issue with RSU - Agilex3 dcio parsing issue with RSU Dear support, I am facing with the following issue: Environment: Quartus prime pro 26.1.0 build 110 (03/26/2026) on windows 11 Target board: Agilex3C evaluation kit (non-hps) Cosigned SDM + Authentication enabled Quartus pfg config file attached (manual.pfg.txt) I can successfully program the flash (the rbf helper signed) via Quartus programmer so the generated jic image is there. When I power-cycle the board and check in configuration debugger the RSU status, I get the following picture: attached rsu_dcio_issue.png I tried to generate the boot.rbf: from sof with -o rsu_boot=ON without injecting sdm without signing the rbf from sof with -o rsu_boot=ON with injecting a signed sdm, with signing the rbf (and basically all the combination with/without signing) In all cases I get back this same issue. QSF file also attached. I validated if I can load from configuration debugger the 1) Factory image (entered base address) --> OK 2) P1 image --> OK 3) P2 image --> OK so it looks like the error is either in the tables or in the decision firmware image itself. The decision firmware.rbf image I signed with permission 0x6, the agilex3.zip with permission 0x1 Today I basically iterated through all the possible way and it still fails. If anyone has any idea where to debug it further (online help again not helping too much), please let me know. Since the issue happening at commands those were in the normal and security guideline and where there are not so much parameters I believe it is either: 1) qsf issue, i am missing some assignment or have false setting --> but which one?? 2) quartus sw issue One last thing: Permission for signing SDM was 0x1 Permission for signing BOOT_INFO / FACTORY_IMAGE / User partitions were 0x6 quartus_sign did not allow me to sign BOOT_INFO with 0x1 permission Signing chains: root0 -> 2x QKY: firmware signing key (0x1) + design signing key (0x6) Update: Is this related to the following entry?! Error(22650): File <filename>.jic is corrupted. DCIO/Main section data information is not found | Altera Community - 351710 Update2: After disabling in the .pfg file the factory fallback: <partition reserved="1" fixed_s_addr="1" s_addr="0x00000000" factory_fallback="0" e_addr="0x0020FFFF" fixed_e_addr="1" id="BOOT_INFO" size="0"/> the issue did not happen anymore --> confirming the issue in 351710 still exists with Quartus 26.1 Thank you for your help in advance! Kind regards, Peter Replies: Re: Agilex3 dcio parsing issue with RSU Hi, It is schedule to be available in July time frame. Replies: Re: Agilex3 dcio parsing issue with RSU Hi, thank you! About when it will be available? or is there any individual patch file just to fix this problem? Replies: Re: Agilex3 dcio parsing issue with RSU Hi, The issue is fixed in Quartus 26.1.1. Replies: Re: Agilex3 dcio parsing issue with RSU Update2:After disabling in the .pfg file the factory fallback: <partition reserved="1" fixed_s_addr="1" s_addr="0x00000000" factory_fallback="0" e_addr="0x0020FFFF" fixed_e_addr="1" id="BOOT_INFO" size="0"/> the issue did not happen anymore --> confirming the issue in 351710 still exists with Quartus 26.1 Replies: Re: Agilex3 dcio parsing issue with RSU The failing address is within the BOOT section: BLOCK START ADDRESS END ADDRESS BOOT_INFO 0x00000000 0x0020FFFF FACTORY_IMAGE 0x00210000 0x0035FFFF (0x0031FFFF) SPT0 0x00360000 0x00367FFF SPT1 0x00368000 0x0036FFFF CPB0 0x00370000 0x00377FFF CPB1 0x00378000 0x0037FFFF P1 0x00380000 0x0048FFFF P2 0x00490000 0x0059FFFF Configuration device: A3CY135BM16A Configuration mode: Active Serial x4 Notes: - Data checksum for this conversion is 0xDA1340C2 - All the addresses in this file are byte addresses