agilex® 7 fpgas and socs
1552 TopicsWhy does generating an HDMI IP Design Example fail when selecting "No Daughter Card" in the Quartus® Prime Pro?
Description Due to a problem in the Quartus® Prime Pro Edition software version 26.1.1, generating an F-Tile HDMI FPGA IP design example encounters an error under the following configurations: Daughter Card parameter set to "No Daughter Card" with No Development Kit selected. Daughter Card parameter set to "No Daughter Card" with a Development Kit selected. Symptoms & Affected Components: Failure: Design Example generation fails or produces an error in Platform Designer Affected IP: F-Tile HDMI FPGA IP (ip.Video Connectivity.HDMI) Target Device / Architecture: Agilex® 7 / F-Tile devices Cause: The F-Tile HDMI IP design example generation script relies on a selected daughter card definition to automatically generate required board topology, clocking, and transceiver constraints. Selecting "No Daughter Card" causes error in the generation script in the Quartus Prime Pro Edition software version 26.1.1. Resolution To work around this problem, follow the steps below. Open the F-Tile HDMI FPGA IP parameter editor. Under the Design Example tab, select a supported HDMI Daughter Card option instead of "No Daughter Card". Generate the design example. If targeting a custom board, manually update the generated top-level pin locations and clock/transceiver settings in your project to match your custom board requirements. Patches are available to fix this problem for the Quartus Prime Pro Edition Software version 26.1.1 versions. Download and install patch below. Quartus Prime Pro Edition Software v26.1.1 Patch 1.25 This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.10Views0likes0CommentsWhy does the Linux* EDAC driver report "Previous Boot UE detected[0x40000]" on Agilex® 7 FPGA F and I-Series SoC FPGA devices?
Description The Linux* EDAC driver (drivers/edac/altera_edac.c) in the SoCFPGA Linux 6.12.11-lts (and earlier versions) may print a false Uncorrectable Error (UE) message during driver probe on Agilex® 7 F/I series SoC FPGA platform, as shown below. EDAC Altera: Previous Boot UE detected[0x40000] @ 0x0 The EDAC driver maps BOOT_SCRATCH_COLD8 (offset address0x220in System Manager, absolute address 0xFFD12220) to S10_SYSMGR_UE_VAL_OFST and treats any non-zero value as evidence of a previous boot UE event. At probe time, the driver checks: if (dberror) { ... } instead of properly masking with: if (dberror & AGX7F_I_DBE_IRQ_MASK) { ... } The valid UE sticky mask AGX7F_I_DBE_IRQ_MASK(0x30002) covers bits 1/16/17 only. When the value of BOOT_SCRATCH_COLD8 is 0x40000 in which bit 18 represents the SDM ACF DDR data rate per the Agilex 7 F/I SoC FPGA register definition, but it’s reported as a DDR UE/DBE by Linux EDAC driver by mistake. The driver does not account for the differences among the various Agilex 7 device series or for future device families. BOOT_SCRATCH_COLD8 bit definitions: Bit field Agilex 7 F/I-Series Agilex 7 M-Series Values / description Usage or source [31] Available as scratch memory DBE Triggered Flag M-Series:0: DDR DBE not triggered; 1: DDR DBE triggered U-Boot ddr_ecc_dbe_status(): evaluates DDR ECC DBE status [30] Available as scratch memory DDR Init in progress M-Series:0: DDR initialization not performed or completed successfully; 1: DDR initialization in progress U-Boot is_ddr_init_hang() checks the bit; ddr_init_inprogress() sets or clears it [29] Available as scratch memory OCRAM_DBE Error Flag M-Series:0: error did not occur; 1: error occurred U-Boot hps_ocram_dbe_status() returns OCRAM DBE status; ddr_init_inprogress() sets or clears it [28:27] Available as scratch memory Number of IO96B instances assigned to HPS M-Series:Written during DDR handoff data population U-Boot update_io96b_assigned_to_hps() [19] Flag indicating that a CPU power domain is about to be turned on; value 1 Flag indicating that a CPU power domain is about to be turned on; value 1 F/I/M-Series:A value of 1 indicates that the CPU power domain is about to be turned on ATF socfpga_pwr_domain_on() [18] ACF DDR data rate set by SDM Available as scratch memory F/I-Series: 0 = half-rate; 1 = quarter-rate U-Boot sdram_mmr_init_full() uses the value to configure DDRIOCTRL [17] ECC_DBE_DDR1 Error Flag ECC_DBE_DDR1 Error Flag F/I/M-Series:0: error did not occur; 1: error occurred ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler [16] ECC_DBE_DDR0 Error Flag ECC_DBE_DDR0 Error Flag F/I/M-Series:0: error did not occur; 1: error occurred ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler [1] ECC_DBE_OCRAM Error Flag ECC_DBE_OCRAM Error Flag F/I/M-Series:0: error did not occur; 1: error occurred ATF cold_reset_for_ecc_dbe() checks the flag; Linux sets it through the ATF SMC handler Impact: No actual DDR UE event is indicated by 0x40000. The false-positive log does not trigger kernel panic, reboot, or EDAC fault handling. However, the driver executes a full register write of zero to both BOOT_SCRATCH_COLD8 and BOOT_SCRATCH_COLD9 after printing the message, which may clear other valid scratch data (ATF, SDM, DDR progress bits) used by boot software on subsequent resets. Real DDR ECC uncorrectable errors continue to be reported correctly through the runtime ECC interrupt path (ECC_INTSTATUS_DERR @ sysmgr +0xA0). Resolution A patch has been applied to remove the incorrect previous DBE check using the BOOT_SCRATCH_COLD8 register during EDAC driver probe. ES-14508: EDAC/altera: Remove previous DBE check using boot scratch c… · altera-fpga/linux-socfpga@d06daa2 Related Articles A.7. BOOT_SCRATCH_COLD8 - 2025-12-16 linux-socfpga/drivers/edac/altera_edac.c at socfpga-6.12.11-lts · altera-fpga/linux-socfpga9Views0likes0CommentsWhy do I unexpectedly observe intermittent DDM Errors?
Description Beginning January 10, 2026, executing commands in the terminal or GUI of Quartus® Prime Pro Edition software, Quartus Embedded Edition software or select standalone tools may cause the software or tool to crash with an error similar to the crash signature shown below. This error affects: Quartus Prime Pro Software versions v22.1 through v25.3.1 Standalone Quartus Prime Pro Programmer v22.1 through v25.3.1 Standalone Quartus Prime Pro Embedded Edition v25.3 and v25.3.1 Standalone Quartus Prime Pro Power Thermal Analyzer v25.3 through v25.3.1 This issue is not observed in Quartus Prime Pro Edition versions 22.1 or prior or Quartus Prime Standard Edition. Crash Signature: Error (22912): Unhandled exception: Fatal Error: Assertion failed tools/cpp/ddm/ddm_assessor.cpp:53: DDM_T::verify_token(token) : Cannot identify the client from function assertion_error in tools/cpp/ddm_report/ddm_report_msg.cpp@465 *** Fatal Error: Program termination requested *** *** Below is the stack trace at the time the error occurred. *** The lines beginning "Err Handler" represent frames relating *** to generating this report. *** The point at which the error occurred is somewhere after these lines. *** There may be a few frames representing standard/library code *** before the Quartus frames begin. *** The search for the error should begin with the Quartus frames. *** Unwinder: libunwind *** Stack depth: 15 Quartus 0x24e67: err_terminator() + 0x1bc (ccl_err) Quartus 0xb036a: __cxxabiv1::__terminate(void (*)()) + 0xa (stdc++) Quartus 0xb03d5: (stdc++) Quartus 0xb0628: (stdc++) Quartus 0x1680d: void ddm_throw<DDM_RUNTIME_ERROR>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x26d (ddm_report) Quartus 0x13fae: DDM_REPORT::DDM_ASSERTION_HANDLER::assertion_error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) const + 0xde (ddm_report) Quartus 0x12a52: DDM_REPORT::ASSERTION_HANDLER::error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x72 (ddm_report) Quartus 0x13e64: DDM_REPORT::detail::assert_at_line(char const*, char const*, int, char const*, ...) + 0x1b4 (ddm_report) Quartus 0x205fb0: ddm_set_lassessor(DDM_T_ASSESSOR*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x60 (ddm) Quartus 0xf4445: DMS_MANAGER::DMS_MANAGER() + 0x5c5 (dni_dms) Quartus 0xf45b2: DMS_MANAGER::get() + 0x7a (dni_dms) Quartus 0xf6db4: _GLOBAL__sub_I_dms_manager.cpp + 0x58 (dni_dms) Quartus 0x647e: (ld-linux-x86-64) Quartus 0x6568: (ld-linux-x86-64) Quartus 0x202ca: (ld-linux-x86-64) Resolution To work around this problem: For Windows machines Download and unzip the Quartus Prime Pro version zip file that matches your Quartus Prime Pro version from this KDB. Double click on the executable ending in “windows.exe”. When the GUI pops up, press Next. Note that the GUI may look slightly different depending on the version of Quartus you are using. Accept the license agreement Specify the directory where the patch needs to be applied which may be a different location than Quartus install if you have standalone tools in a different directory from your Quartus Prime Pro software installation. Keep “Allow Patch to be uninstalled” selected. Select the software in which to install the patch: The patch will install in the directory of the software or tool you have selected. You will see an uninstall directory for the patch in your software or tool folder where patch is installed; it will contain an executable to uninstall the patch if required for any reason. To confirm patch is installed, you can run quartus_sh -v or corresponding version command for your tool via command line. Alternatively, you can Open Quartus in the GUI and select Help → About Quartus Prime in the main menu. If you are opening up a standalone tool you will navigate to Help-> About <tool_name>. For the Command Line Implementation of the patch in Windows, use the following command: <patch_filename.exe> --mode unattended --installdir <your_install_directory> --accept_eula 1 --patch_to [quartus|qprogrammer|qemb|pta] # An example to patch Quartus Prime Pro Edition Software v25.3: quartus-25.3-0.27-windows.exe --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 # An example to patch the Standalone Programmer for Quartus Prime Pro Software v25.3: quartus-25.3-0.27-windows.exe --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 --patch_to qprogrammer For Linux machines: Download and unzip the Quartus Prime Pro version zip file that matches your Quartus Prime Pro version from this KDB. Ensure you run chmod +x on the file ending with linux.run. Run in the command line: ./<installation_patch_run_file>. When GUI pops up, press Next. Note that the GUI may look slightly different depending on the version of Quartus you are using. Accept the license agreement Specify the directory where the patch needs to be applied which may be a different location than Quartus install if you have standalone tools in a different directory from your Quartus Prime Pro software installation. Keep “Allow Patch to be uninstalled” selected. Select the software in which to install the patch: The patch will install in the directory of the software or tool you have selected. You will see an uninstall directory for the patch in your software or tool folder where patch installed; it will contain an executable to uninstall the patch if required for any reason. To confirm patch is installed, you can run ./quartus_sh -v or corresponding version command for your tool via command line. Alternatively, you can Open Quartus in the GUI and select Help → About Quartus Prime in the main menu. If you are opening up a standalone tool you will navigate to Help-> About <tool_name>. For the Command Line Implementation of the patch in Linux, use the following command: ./<patch_filename.run> --mode unattended --installdir <your_install_directory> --accept_eula 1 --patch_to [quartus|qprogrammer|qemb|pta] # An example to patch Quartus Prime Pro Edition v25.3: ./quartus-25.3-0.27-linux.run --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 # An example to patch the Standalone Programmer for Quartus Prime Pro Software v25.3: ./quartus-25.3-0.27-linux.run --mode unattended --installdir /tmp/altera_pro/25.3 --accept_eula 1 --patch_to qprogrammer This problem has been fixed in Quartus® Prime Pro Edition Software version 26.1. The below table lists the patches that are available and the associated patch number. The patch zip files are attached to the KDB below: Quartus Prime Pro Edition Version Patch Number 22.1 0.51 22.2 0.63 22.3 0.56 22.4 0.51 23.1 0.63 23.2 0.63 23.3 0.52 23.4 0.70 23.4.1 1.01 24.1 0.52 24.2 0.64 24.3 0.35 24.3.1 1.29 25.1 0.36 25.1.1 1.31 25.3 0.27 25.3.1 1.0214KViews5likes0CommentsWhy does the Nios® V/g processor become unstable when both CLIC and shadow registers are enabled?
Description Due to a problem in the Quartus® Pro/Standard Edition software version 26.1/25.1, Nios® V/g interrupt handling might be unstable when both CLIC mode and Shadow Register are enabled. This is because the Shadow Register CSR (msrfstatus) is not saved/restored during interrupt context saving under CLIC mode. Resolution To work around this problem in the Quartus® Prime Pro/Standard Edition Software version 26.1/25.1, follow these steps: Download the machine_trap.zip Extract to get the new machine_trap.S Search for the old machine_trap.S in your BSP project Replace with the new machine_trap.S file Rebuild your software Additional Information This problem is currently scheduled to be resolved in a future release of the Quartus® Prime Pro and Standard Edition Software.30Views0likes0CommentsError: CPU "intel_niosv_g_0" has no memories connected to its Avalon host(s)
Description Due to a problem in the Quartus® Pro Edition software version 26.1.1, you might see an error when generating a Nios® V BSP, when the AXI Address Span Extender IP is inserted between the Nios V processor and the memory device connected to the instruction and data buses of the Nios V. This is because the AXI Address Span Extender IP does not recognize the connected device as a memory device for the Nios V processor. Resolution To work around this problem in the Quartus® Prime Pro Edition Software version 26.1.1, follow these steps: 1. Open <QUARTUS_INSTALL_DIR>/ip/altera/merlin/axi_address_span_extender/axi_address_span_extender_hw.tcl 2. Go to around line 448, then delete the lines marked in red and add the lines marked in green as shown below. # this assignment allows this component to appear as a memory target in the Nios II linker script configuration GUI # it makes the memory map of our slave look like a valid linker target memory region # <<to be revisited in 13.0>> - #set_interface_assignment windowed_slave embeddedsw.configuration.isMemoryDevice 1 + set_interface_assignment $slave embeddedsw.configuration.isMemoryDevice 1 # # this assignment allows the macros of components attached to our master to appear in the Nios II system.h header # <<to be revisited in 13.0>> - #set_interface_assignment windowed_slave embeddedsw.configuration.affectsTransactionsOnMasters "expanded_master" + set_interface_assignment $slave embeddedsw.configuration.affectsTransactionsOnMasters $master Please do not include the leading "+" and "-" characters. 3. Regenerate your design in Platform Designer. Additional Information This problem is currently scheduled to be resolved in a future release of the Quartus® Prime Pro Edition Software. However, the updated statements are commented out by default. To apply the changes, remove the comment markers.14Views0likes0CommentsWhy Does a 528-bit PCS66 Phase Shift Occur with 400GZR/ZR+ Coherent Optical Modules on F-Tile Ethernet Hard IP?
Description In the Quartus® Prime Pro Edition software version 26.3 and earlier, raw receive PCS66 parallel data might appear phase-shifted by 528 bits when a 400G-8 F-Tile Ethernet Hard IP design without the Media Access Control (MAC) block is connected to a 400GZR or ZR+ coherent optical module. The shift equals eight 66-bit Physical Coding Sublayer (PCS) blocks, or half of the 1056-bit parallel word. The 66-bit symbols can remain intact, and rx_block_lock andrx_am_lock can remain asserted. This behavior can occur when the receive path selects the alternate 1:2 demultiplexer phase. The PCS does not provide parallel-data phase alignment relative to the original transmit AM and data relationship. The behavior was observed in the raw Media Independent Interface (MII) PCS66 path. MAC and MAC Segment modes successfully transferred packets. Electrical loopback, digital-to-analog converter loopback, internal serial loopback, and 400GE-8 short-reach optical paths did not show the same behavior. Resolution No Quartus Prime Pro Edition software fix is identified for this behavior at this time. To work around this problem, use a packet-oriented higher layer where possible. For designs that consume raw PCS66 data, follow these steps: Capture rx_pcs66_d and any available AM location or indication, rx_block_lock , and rx_am_lockas signals. Transmit a deterministic PCS66 block sequence that includes a unique known block pattern around the transmit AM location. Compare the received block sequence with the expected sequence to determine whether the received data is at offset 0 or offset 8 PCS66 blocks, which is a 528-bit offset. Implement protocol-specific realignment in the higher-level logic based on the detected offset. Do not use rx_am_lockas the sole phase detector. It indicates AM lock, but it does not identify which 1:2 demultiplexer phase is selected. A generalized phase-correction method or dedicated status bit/register has not been identified. The required realignment depends on the protocol consuming the raw PCS66 stream. Additional Information The current explanation is based on available data. It is generalized to all ZR/ZR+ module (subject to data availability). Customer-specific protocol details are required to define a complete phase-correction implementation or to suggest workarounds.30Views0likes0CommentsWhy don’t the new Nios® V/c processor features appear after upgrading the Nios® V/c Processor IP to Quartus® Prime Pro version 26.3?
Description In Quartus® Prime Pro Edition 26.3, the Nios® V/c processor IP is renamed from intel_niosv_c to niosv_c across all FPGA device families. Performing IP Upgrade from earlier Quartus® Prime project will retain the legacy intel_niosv_c in your project. For your information, This legacy intel_niosv_c IP remains at last updated back in Quartus® Prime Pro Edition 26.1.1. While new Nios® V/c processor IP feature are introduced into niosv_c IP starting from Quartus® Prime Pro Edition 26.3. In another words, auto-upgrade of intel_niosv_c to niosv_c in not supported by IP Upgrade. Thus, you may find those new Nios® V/c processor features (in niosv_c) is missing in intel_niosv_c. Resolution If new Nios® V/c processor features (such as Debug option) is required, re-instantiate the Nios® V/c processor in Quartus® Prime Pro version 26.3.31Views0likes0CommentsWhy 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 Decoder50Views0likes0CommentsWhy is there a port width mismatch on d2h_usr_desc_cdt_avail_cnt in the generated top-level wrapper of the AXI Multichannel DMA IP for PCI Express*?
Description Due to a problem in the Quartus® Prime Pro Edition software version 26.1.1, the generated top-level wrapper (*_inst.v) for the AXI Multichannel DMA IP for PCI Express* exports an incorrect port width for d2h_usr_desc_cdt_avail_cnt when the D2H Descriptor Engine Credit Interface is enabled. For example, when Maximum D2H Descriptor Fetch (d2h_max_num_desc_fetch_hwtcl) is set to 64, the generated wrapper defines d2h_usr_desc_cdt_avail_cnt as a 6-bit output ([5:0]) instead of a 7-bit output ([6:0]). Resolution To work around this problem in the Quartus Prime Pro Edition software version 26.1.1, manually update the d2h_usr_desc_cdt_avail_cnt port width in the generated top-level wrapper (*_inst.v). The expected port width of d2h_usr_desc_cdt_avail_cnt for each Maximum D2H Descriptor Fetch setting is: d2h_max_num_desc_fetch_hwtcl = 64 --> [6:0] (7 bits) d2h_max_num_desc_fetch_hwtcl = 32 --> [5:0] (6 bits) d2h_max_num_desc_fetch_hwtcl = 16 --> [4:0] (5 bits) This problem is scheduled to be fixed in a future release of the Quartus Prime Pro Edition software.50Views0likes0CommentsWhy is the HPS I2C SCL clock frequency above 400 kHz in fast mode when using U-Boot?
Description When the HPS I2C controller is configured for fast mode (clock-frequency = <400000>) in U-Boot, the measured SCL frequency might exceed the 400 kHz maximum in the I2C specification (for example, 431 kHz) on SoC FPGA designs. This happens because the U-Boot DesignWare I2C driver (drivers/i2c/designware_i2c.c) calculates the SCL high and low counts from assumed SCL rise and fall times. When the device tree does not specify them, the driver assumes default 300 ns for both in fast mode. The driver subtracts the assumed rise time from the SCL period. If the board's actual SCL rise time is shorter than 300 ns, the unused part of that allowance shortens the period, and SCL runs faster than 400 kHz. The Linux DesignWare I2C driver uses a different calculation and different device tree properties, so the same device tree node can give different SCL frequencies in U-Boot and Linux. Resolution To set the SCL timing to match your board, follow these steps: Measure the SCL and SDA rise times (30%–70%) and fall times (70%–30%) on your board with an oscilloscope, in fast mode. In the U-Boot device tree, add the measured values to the HPS I2C node: &i2c0 { clock-frequency = <400000>; i2c-scl-rising-time-ns = <[measured tr]>; i2c-scl-falling-time-ns = <[measured tf]>; i2c-sda-hold-time-ns = <[required hold, default 300]>; }; For Linux, add the SDA fall time to the same node. The Linux driver uses i2c-sda-falling-time-ns for the SCL high count and i2c-scl-falling-time-ns for the SCL low count, and ignores i2c-scl-rising-time-ns: i2c-sda-falling-time-ns = <[measured tf]>; Rebuild U-Boot and the Linux device tree blob, then re-measure SCL in both U-Boot and Linux to confirm the frequency is at or below 400 kHz and that tLOW ≥ 1.3 µs and tHIGH ≥ 0.6 µs. Note these points when tuning: In U-Boot, enter the actual measured rise time. A larger i2c-scl-rising-time-ns value makes SCL faster, not slower. In U-Boot, i2c-scl-falling-time-ns changes only the high/low duty cycle, not the frequency. In Linux, larger fall-time values make SCL slower. Do not lower clock-frequency below 400000 in U-Boot to slow the bus. Any value below 400000 selects standard mode (100 kHz timing). snps,bus-capacitance-pf has no effect in fast mode. U-Boot ignores it, and Linux uses it only for high-speed mode (3.4 MHz). Additional Information Property U-Boot Linux clock-frequency Sets the target SCL period (default 100 kHz) Selects the speed mode only (default 400 kHz) i2c-scl-rising-time-ns Sets the SCL frequency (default 300 ns in fast mode, 1000 ns in standard mode) Ignored by the DesignWare driver i2c-scl-falling-time-ns Changes the duty cycle only (default 300 ns) Sets the SCL low count (default 300 ns) i2c-sda-falling-time-ns Ignored Sets the SCL high count (default 300 ns) i2c-sda-hold-time-ns Sets the SDA hold time (default 300 ns) Sets the SDA hold time (default: keeps the existing hardware value) snps,bus-capacitance-pf Ignored Used in high-speed mode (3.4 MHz) only31Views0likes0Comments