security
47 TopicsWhy do I see Error (20354) and Error (20353) when signing CCERTs in Quartus® Prime Pro Edition version 26.3 with root keys generated in earlier versions?
Description You may encounter a signing failure in Quartus® Prime Pro Edition Software version 26.3 when an Agilex® 7 FPGA device root key generated by quartus_sign in an earlier release, such as Quartus® Prime Pro Edition Software version 21.2, is used to create and sign compact certificates (CCERTs). The operation fails with the following errors: Error (20354): Fail to execute file <path>26.3/111/linux64/devices/programmer/python/agilex_sign.py Error (20353): Module: bitstream.py, Function: verify_block0, Line: 798 Error (20353): Root key select is undetermined Error: Quartus Prime Signing_Tool was unsuccessful. 3 errors, 1 warning For example: In Quartus® Prime Pro Edition Software version 21.2, the following files were generated: root0_212.qky root0_public_212.pem root0_private_212.pem root0_aes_212.qek After switching to Quartus® Prime Pro Edition Software version 26.3 to generate the AES CCERT, the following commands were executed (using the AES CCERT test case as an example): quartus_pfg --ccert -o ccert_type=EFUSE_WRAPPED_AES_KEY -o qek_file=root0_aes_212.qek unsigned_aesccert0-263.ccert quartus_sign --family=agilex --operation=sign --pem=root0_private_212.pem --qky=root0_212.qky unsigned_aesccert0-263.ccert signed_aesccert0-263.ccert Impacted Agilex 7 OPN AGF 012 AGF 014 AGF 022 AGF 027 AGI 022 AGI 027 Resolution Recommendation: To sign a CCERT, use one of the following options: Use the same Quartus sofware version that was used to generate the existing root key. Use Quartus Prime Pro Edition Software version 26.1.1 or earlier. Use Quartus Prime Pro Edition Software version 26.3 or later to generate a new root key. Note: This behavior applies starting with Quartus Prime Pro Edition Software version 26.3 and is not expected to change in future releases. Related Articles Agilex 7 Part number Decoder50Views0likes0CommentsRequest for Technical Meeting – FPGA Selection, ADRV9029 Integration, and Procurement Support
Dear Intel FPGA Team, Greetings from PARAS Defence and Space Technologies. We are currently evaluating FPGA solutions for our C-band SATCOM terminal project. Our key application requirements are as follows: RF frequency range: 4.4–4.95 GHz • Instantaneous RX bandwidth: 16 MHz • RF channels: 4 RX and 4 TX • Interface: JESD204B/C between the RF transceiver and FPGA • Application: Ground-based SATCOM terminal for tracking a moving aircraft We are considering the Intel Arria 10 FPGA family as a potential platform and have reviewed the available reference design for the ADRV9029 Sub-6 GHz evaluation board with Arria 10 FPGA. To clarify the technical feasibility and plan our development and procurement activities, we would like to arrange a meeting with your FPGA technical and sales teams to discuss the following topics. FPGA Selection and Compatibility Recommendation of a suitable Arria 10 or other Intel FPGA family and specific part number for our application, considering JESD interface requirements, FPGA resources, transceiver capabilities, and future scalability. ADRV9029 JESD204 Integration Confirmation of the supported JESD204B/C configurations, available transceiver lanes, achievable lane rates, and relevant FPGA IP requirements for interfacing with the ADRV9029. Reference Design and Porting Support Guidance on the available ADRV9029–Arria 10 reference design, required hardware platform, design files, software dependencies, and the feasibility of adapting the reference design to our intended FPGA platform. Development Tools and Technical Support Information on the required Intel Quartus Prime software edition, JESD204 IP licensing, simulation resources, design examples, and technical support available during FPGA development. Evaluation Hardware Recommendations for a suitable FPGA development kit or evaluation platform for initial ADRV9029 integration, including availability, compatibility, and procurement options. Product Presentation A technical presentation covering relevant FPGA families, high-speed transceiver capabilities, JESD204 interface solutions, design resources, and application examples suitable for RF and SATCOM systems. Procurement and Commercial Discussion Indicative pricing, product availability, lead times, development kit costs, and long-term supply considerations for prototype development and production. We would appreciate the opportunity to discuss these requirements with your technical specialists and sales representatives at a mutually convenient date and time. Please let us know your availability and whether any additional technical information is required from our side before the meeting. Thank you for your support. We look forward to your recommendations and to working with your team to identify a suitable FPGA solution for our project.83Views0likes2CommentsCan Agilex 3 A3CY100BM16AE7S (AXC3000) use SDM cryptographic services?
Hello, I would like to confirm whether the SDM cryptographic services (user-mode access through the Mailbox Client IP) are supported on this device: Device: A3CY100BM16AE7S (Agilex 3 C-Series 100, M16A), Arrow AXC3000 board Tools: Quartus Prime Pro 26.1 build 110 Mailbox Client IP: Enable C-r-y-p-t-o Service = 1, C-r-y-p-t-o Memory Timeout = 10000, AXI manager connected to an on-chip RAM (confirmed in the compile log: intel_memory_initiator_endpoint with has_offload=1) Access: from fabric over Avalon-MM, no HPS What I observe (3 runs each, identical results, response FIFO empty after each command): - NOOP -> response header 0x00000000 (OK) - GET_IDCODE (0x10) -> header 0x00001000, data 0x4361B0DD (OK) - GET_CHIPID (0x12), GET_USERCODE (0x13), GET_TEMPERATURE (0x19), CONFIG_STATUS (0x04) -> all return the documented response lengths - open_crypto_service_session (0xA0) -> header 0x00001085 (error code 0x085, LENGTH=1), data word 0x000000FF - close_crypto_service_session, random_number_request, aes_crypt_request, get_digest_request, ecdsa sign/verify, ecdh_request -> header error code 0x085 (LENGTH=0) What the documentation says: - Agilex 3 C-Series Product Table (2026.02.11): specification code Y has C-r-y-p-t-o = No ("user mode access to the SDM hardened cryptographic IP"); codes U and W have C-r-y-p-t-o = Yes. - Security TRM: the error table of open_crypto_service_session lists both 0x0F (function not supported on the device) and 0x85 (command not allowed under the current security settings). - Security Overview for SDM-based devices, section 2.6, says the SDM C-r-y-p-t-o engines are made available to the FPGA design through the mailbox in user mode, without mentioning per-device restrictions. Questions: 1. Does A3CY100BM16AE7S (spec code Y) support SDM cryptographic services through the Mailbox Client IP? 2. If not, is 0x085 the expected response, or should it be 0x0F? 3. If the device is supposed to support them, what could make the SDM reject the command with 0x085 (security settings, provisioning, initialization)? 4. Is there any supported way to enable these services on this device? Thank you.138Views0likes4CommentsIntroducing the Altera Community AI Responder — Beta
Altera is introducing the AI Responder, an assistant built into the Altera Community to help provide faster, context-aware guidance for Altera product questions. It uses relevant public Altera documentation and Knowledge Database content, with coverage continuing to expand. The AI Responder may provide source references and can hand off complex or out-of-scope questions to an Altera subject-matter expert. As a beta feature, responses may contain errors or omissions, so please review the sources and verify technical guidance against official Altera documentation before implementation. If the response does not fully address your question, add more context and tag ai_responder to continue the discussion. We welcome your feedback as we improve the Community experience.70Views0likes0CommentsRegarding the SDM Random Number Generator in Agilex 5 E-Series
Hi, Altera support team, <Overview> I have some questions about SDM Random Number Generator. But I cannot find any detailed information on that. I think it isn't public information. Could you answer below my questions? <Questions> 1. What is the entropy source? 2. How many bits of entropy are configurated? 3. Is the Random Number Generator configured as a combination of TRNG and DRBG? 4. Is it possible to provide documentation containing detailed information? <Note> We received these questions from a specific customer. So if possible, could you open a private session? BR, Wacky.99Views0likes2CommentsWhy am I unable to run BKP operations with Quartus® Prime Pro Edition 26.1.1 on Windows*?
Description Due to a problem in the Quartus® Prime Pro Edition Software version 26.1.1, Black Key Provisioning (BKP) operations might fail on Windows* with the following error: Error: BKP PLUGIN: [3000] Http error: Could not use specified SSL cipher because Quartus has enabled the Windows SSP interface Schannel (Secure Channel) to work with the OpenSSL library. When using libcurl with the Schannel (Windows) backend, the option CURLOPT_SSL_CIPHER_LIST does not accept individual, specific cipher suites (for example TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384). Resolution To work around this problem in the Quartus® Prime Pro Edition Software version 26.1.1, build a patched bkpprog.dll and select it through the project configuration, as follows: 1. Clone the source repository: GitHub - altera-fpga/device-security-software-services: Device Security Software and Services source code for FPGA Device Onboarding, Attestation, Secure Session, Black Key Provisioning. 2. Prepare the Windows build environment. Follow the Windows Build instructions in the repository README. Install the listed prerequisites and prepare the repository dependencies exactly as documented there. 3. Modify network_wrapper.cpp. Open the following file in the cloned repository: bkpprogrammer/src/core/cpp/network/network_wrapper.cpp In CurlWrapper::CurlWrapper, locate the TLS version and cipher-list configuration: setCurlOptionWithErrorHandling( curlHandle, CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1_2); setCurlOptionWithErrorHandling( curlHandle, CURLOPT_SSL_CIPHER_LIST, acceptedCiphers.c_str()); Replace it with: setCurlOptionWithErrorHandling( curlHandle, CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1_2); 4. Build the patched plug-in. Return to the repository root and build by following the repository Windows Build instructions. Confirm that bkpprog.dll is regenerated after network_wrapper.cpp was modified. 5. Place the custom plug-in. Create the following directory under the BKPS project and copy the rebuilt bkpprog.dll into it. Do not replace the DLL inside the Quartus installation. <project>\cm_provisioning\bkp_plugin\bkpprog.dll 6. Create quartus.ini. Create a quartus.ini file directly under the project cm_provisioning directory with the following line: PGM_ALLOW_CUSTOM_BKP_PLUGIN=7S6Nh0s3@on 7. Update bkp_options.txt. Use the normal project-specific BKP values and add bkp_plugin with the path to the rebuilt DLL: bkp_cfg_id = <ID> bkp_ip = <IP> bkp_port = <PORT> bkp_tls_ca_cert = "<Path_To_bkps_ssl_cert.crt>" bkp_tls_prog_cert = "<Path_To_pro_cert>" bkp_device_opn = <OPN> bkp_plugin = "<Path_To_bkpprog.dll>" 8. Run Quartus Programmer where quartus.ini is located. Set the current working directory to the cm_provisioning directory that contains quartus.ini and bkp_options.txt. Quartus reads quartus.ini from its current working directory, so run the commands from here: quartus_pgm.exe -c 1 -m jtag --bkp_options=bkp_options.txt --bkp_prefetch Use the same working directory for Set Authority and Provision operations, so Quartus continues to load the custom plug-in setting from quartus.ini. This problem is scheduled to be resolved in a future release of the Quartus® Prime Pro Edition Software.63Views0likes0CommentsGeneral Question to your "Vulnerability Handling Process"
How can i subscribe to "Security Advisories"? Your link Manage Your Communication Preferences which i found on your Altera PSIRT Vulnerability Handling Process site does not work. Im not able write my email into the textbox.Solved333Views0likes1Comment