i.MXプロセッサ ナレッジベース

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

i.MX Processors Knowledge Base

ディスカッション

ソート順:
1. What this is (and what it is not) This project is an interactive edge-compute demonstrator. It runs a quantum-circuit simulator entirely on an NXP i.MX 95 applications processor and presents the results in a browser-based GUI served by the board itself. CRITICAL POINT. The i.MX 95 is a classical Arm SoC. It does NOT contain quantum hardware and performs NO quantum computation. It simulates quantum circuits using ordinary floating-point math — exactly the way a flight simulator imitates a plane without being one. There is no quantum speedup; the demonstrated value is the SoC’s classical compute and memory capability. In one sentence: “A normal NXP chip imitates a quantum computer by doing the exact math a quantum computer would — so you can watch quantum algorithms behave and see how much heavy numerical work this edge chip can handle locally, with no cloud.”   2. Why simulate quantum on a classical chip? Education / engagement. Quantum computing is a high-interest topic. A live, interactive simulator makes abstract ideas (superposition, entanglement, quantum search) tangible on hardware the team already owns. Capability showcase. Simulating quantum circuits is a genuinely demanding numerical workload. Every additional qubit doubles the memory and compute required. That makes it an excellent, recognizable stress test for demonstrating that an automotive edge SoC can run serious floating-point and memory-bound workloads locally. 3. A 5-minute quantum primer Bit vs. qubit A classical bit is 0 or 1 (a light switch). A qubit can be 0, 1, or a blend of both at once (a spinning coin: “both heads and tails” until it lands). The blend is called superposition. Measurement You cannot read the blend directly. When you measure a qubit it randomly lands on a definite 0 or 1, with probabilities set by the blend. Because the result is probabilistic, we repeat the experiment many times (“shots”) and tally the outcomes into a histogram. Entanglement Two qubits can be entangled — linked so their measurement outcomes are correlated. The Bell state always gives 00 or 11, never 01 or 10. Why it is hard to simulate To simulate n qubits, a classical computer must track the statevector: 2^n complex numbers (amplitudes). Qubits Amplitudes (2^n) Statevector memory (complex128) 10 1,024 16 KB 20 1,048,576 16 MB 24 16,777,216 268 MB 27 134,217,728 2.0 GB 30 1,073,741,824 16 GB (exceeds board RAM)   Each extra qubit doubles everything. This exponential growth is why even a powerful chip hits a hard ceiling. 4. How the demo is built (architecture) The demonstrator is deliberately minimal: only Python 3 + NumPy, both already present in the board’s Yocto image. No external services, no cloud, no accelerator libraries. File Role qsim_server.py Statevector simulator + tiny HTTP/JSON server. Runs the simulation on the A55 cores and serves the UI and a JSON API with real on-board timing/memory. quantum_explorer.html Browser UI. Calls the board’s API; auto-detects LIVE-on-board vs. a JS fallback simulator. run_benchmark.py Command-line sweep producing a CSV of time/memory vs. qubit count (single-core vs. multi-core).     The simulation engine The state is a NumPy complex128 array of length 2^n. Gates are in-place array operations. The key gate for the capability test is the Hadamard (H), which puts a qubit into superposition and touches the entire statevector. A “Hadamard layer” applies H to several qubits; the benchmark uses up to four layers as a standardized unit of work. 5. The four algorithms 6. Walking through the web UI Served at http://<board-ip>:8000/. Three areas: Controls (left) Algorithm — selects the circuit. Capability sweep: qubits — slider (4–27) setting the statevector size to stress-test; the SoC capability knob. Measurement shots — 256/1024/4096; more shots = smoother histogram. Measure single-core & speedup — optionally time a single-core run to report multi-core speedup. Results (right) Circuit — text diagram of the gates. Capability metrics — qubits, amplitudes, state memory, cores used, wall-time, single-core time, speedup, CPU GFLOPS, memory GB/s, peak memory. All measured on the board. Measurement histogram — tallied outcomes. Capability scaling (bottom) A “Run scaling sweep” button walks a range of qubit counts and draws two live charts: wall-time (single vs. 6-core, log) and the speedup curve. STATUS BADGE. A green “LIVE on board” badge confirms the UI is talking to the i.MX 95 (real numbers). Orange “browser sim” means it fell back to a JS simulator. 7. Multi-core: using all six A55 cores Statevector simulation is naturally parallel: a Hadamard on qubit t combines index i only with i XOR (1<<t) — independent pairs. The engine splits the 2^n statevector into contiguous slices processed on separate threads (one per A55 core), aligned so no pair straddles two slices. WHY NOT 6x? Statevector simulation is memory-bandwidth bound, not compute bound. The six cores share one memory bus; once a few cores saturate bandwidth, more cores cannot help. The measured ~2.5–2.8x ceiling is the expected behavior for a memory-bound kernel — a realistic engineering result, not marketing. For small circuits (< ~17 qubits) thread-coordination overhead makes multi-core slower; the engine favors single-core below the crossover and parallelizes above it.   8. Measured results on the i.MX 95 Real measurements from the i.MX 95 EVK (6× A55, 15.35 GiB), applying four Hadamard layers. Qubits Amplitudes State Single-core 6-core Speedup Peak mem 14 16,384 0.3 MB 9.34 ms 10.82 ms 0.86x 1.0 MB 16 65,536 1.0 MB 35.5 ms 90.4 ms 0.39x 3.8 MB 18 262,144 4.2 MB 121 ms 103 ms 1.18x 15.1 MB 20 1,048,576 16.8 MB 323 ms 150 ms 2.16x 65.7 MB 22 4,194,304 67.1 MB 1,248 ms 463 ms 2.69x 257 MB 24 16,777,216 268 MB 4,666 ms 1,860 ms 2.51x 1,051 MB 25 33,554,432 537 MB — 4,112 ms — 2,058 MB 26 67,108,864 1.07 GB — 8,260 ms — 4,295 MB 27 134,217,728 2.0 GB — 16,533 ms — 8,590 MB       Key observations Textbook exponential scaling: 20->27 qubits, time grew ~110x and peak memory ~128x. Real multi-core benefit at scale: ~2.5–2.7x across 20–24 qubits; peak 2.69x at 22 qubits (a single-core-enabled run observed up to 2.76x). Practical ceiling = 27 qubits: 27q uses ~8.6 GB peak of ~15.35 GiB; 28q (~17 GB) does not fit. Peak memory ~4x statevector due to NumPy working copies — the reason the ceiling is 27, not 29. 9. Compute metrics: GFLOPS, GB/s — and why not TOPS CPU compute (GFLOPS): each Hadamard layer performs ~4 x 2^n real FLOPs (complex128). Total FLOPs / wall-time = CPU floating-point rate. Memory bandwidth (GB/s): each layer reads+writes the full statevector (~2 x state_bytes). This is the limiting metric. GFLOPS IS NOT TOPS. TOPS rates the eIQ Neutron NPU (~2–4 TOPS on i.MX 95), an integer/quantized accelerator for neural networks. The quantum simulator runs floating-point math on the CPU, so the correct unit is GFLOPS. The NPU is not used and consumes zero TOPS. Reporting TOPS here would be incorrect. COULD THE NPU HELP? Not with quantum simulation (wrong math type). The only honest bridge is a Quantum Machine Learning (QML) pipeline: CPU computes a quantum feature map and the NPU runs a quantized NN classifier — there real TOPS would be exercised. That is a separate demonstrator needing the eIQ/Neutron (TFLite + Neutron delegate) stack.   10. How to run it yourself Prerequisites (verified on the EVK): Python 3.13.4, NumPy 2.2.3, 6 cores, ~15 GiB. Deploy: copy the three files to /home/<user>/quantum, then:   python3 qsim_serve.py --port 8000 > qsim.log Open http://<board-ip>:8000/quantum_explorer_gflop.html on a PC browser; badge should read LIVE on board. Capability sweep: python3 run_benchmark.py --min 10 --max 27 --out sweep.csv Verify it is really the board computing: run top (press 1) and watch python3 light up the cores.   11. Customer talk-track & honest claims 30-SECOND PITCH. “Quantum is everywhere in the news. Here is a quantum-circuit simulator running entirely on an NXP i.MX 95 at the edge — no cloud, no quantum computer. Pick an algorithm and watch entanglement or Grover’s search happen live. The scale-up slider shows the i.MX 95 simulating a 22-qubit circuit in under half a second and reaching 27 qubits — 134 million amplitudes — using all six A55 cores. This automotive edge SoC runs serious numerical workloads locally.” Classical simulation — no qubits, no quantum speedup. Time/memory grow as 2^n; ~27 qubits is the practical ceiling on 15.35 GiB. Multi-core speedup caps at ~2.7x because the workload is memory-bandwidth bound. GFLOPS/GB/s describe CPU performance; the NPU (TOPS) is not involved.    
記事全体を表示
Background : This article introduces a practical method to test the i.MX95 10GbE interface using two i.MX95 EVKs connected directly by an Ethernet cable. By using iperf3 to measure TCP throughput in both TX and RX directions, customers can verify the 10GbE functionality and evaluate network performance as a reference for their own i.MX95-based designs. Hardware: • 2 × i.MX95 EVK boards • 1 × Ethernet cable for direct connection between the 10GbE ports • Power supplies and serial debug cables for both boards Software: Linux BSP: 6.18.2_1.0.0 Test Procedure: Step 1: Connect the Hardware Connect the 10GbE ports of the two i.MX95 EVK boards directly using an Ethernet cable.(Boot both boards with Linux BSP 6.18.2_1.0.0.) Step 2: Configure the IP Addresses Configure static IP addresses for the 10GbE interfaces on both i.MX95 EVKs to ensure they are in the same subnet and can communicate with each other.   # EVK 1 ifconfig eth0 192.168.0.1   # EVK 2 ifconfig eth0 192.168.0.2 Step3: Run the iperf3 Throughput Test On EVK 1 (Server), start the iperf3 server: iperf3 -s On EVK 2 (Client), run the following command: iperf3 -c 192.168.0.1 -O 2 -P 8 -w 4M -Z -t 60 -R  Command Explanation: -c : 192.168.0.1Runs iperf3 in client mode and connects to the iperf3 server at 192.168.0.1. -O 2  : Omits the first 2 seconds of the test from the final statistics to reduce the impact of the TCP startup phase. -P 8 : Creates 8 parallel TCP streams to increase link utilization. -w 4M : Sets the TCP socket buffer size to 4 MB. -Z : Enables zero-copy mode to reduce CPU overhead caused by data copying. Step4: Test Result Summary Using 8 parallel TCP streams for a 60-second reverse-direction test, the two i.MX95 EVKs achieved an aggregate throughput of 7.90 Gbit/s, transferring 55.2 GBytes of data. The test also reported 4176 TCP retransmissions. The test results are output as follows: [ ID] Interval           Transfer     Bitrate         Retr [  5]  0.00-60.00  sec  7.31 GBytes 1.05 Gbits/sec  414            sender [  5]  0.00-59.97  sec  7.30 GBytes 1.05 Gbits/sec                 receiver [  7]  0.00-60.00  sec  5.07 GBytes  726 Mbits/sec  540            sender [  7]  0.00-59.97  sec  5.07 GBytes  726 Mbits/sec                 receiver [  9]  0.00-60.00  sec  2.87 GBytes  410 Mbits/sec  244            sender [  9]  0.00-59.97  sec  2.87 GBytes  410 Mbits/sec                 receiver [ 11]   0.00-60.00  sec 12.7 GBytes  1.82 Gbits/sec  366           sender [ 11]   0.00-59.97  sec 12.7 GBytes  1.82 Gbits/sec                  receiver [ 13]   0.00-60.00  sec 4.22 GBytes   604 Mbits/sec  553           sender [ 13]   0.00-59.97  sec 4.21 GBytes   604 Mbits/sec                  receiver [ 15]   0.00-60.00  sec 7.24 GBytes  1.04 Gbits/sec  733           sender [ 15]   0.00-59.97  sec 7.23 GBytes  1.04 Gbits/sec                  receiver [ 17]   0.00-60.00  sec 7.01 GBytes  1.00 Gbits/sec  708           sender [ 17]   0.00-59.97  sec 7.01 GBytes  1.00 Gbits/sec                  receiver [ 19]   0.00-60.00  sec 8.76 GBytes  1.25 Gbits/sec  618           sender [ 19]   0.00-59.97  sec 8.76 GBytes  1.25 Gbits/sec                  receiver [SUM]   0.00-60.00 sec  55.2 GBytes  7.90 Gbits/sec  4176             sender [SUM]   0.00-59.97 sec  55.2 GBytes  7.90 Gbits/sec                  receiver iperf Done. Server: [ ID] Interval           Transfer     Bitrate         Retr [  5]  0.00-60.00  sec  7.31 GBytes 1.05 Gbits/sec  414            sender [  8]  0.00-60.00  sec  5.07 GBytes  726 Mbits/sec  540            sender [ 10]   0.00-60.00  sec 2.87 GBytes   410 Mbits/sec  244           sender [ 12]   0.00-60.00  sec 12.7 GBytes  1.82 Gbits/sec  366           sender [ 14]   0.00-60.00  sec 4.22 GBytes   604 Mbits/sec  553           sender [ 16]   0.00-60.00  sec 7.24 GBytes  1.04 Gbits/sec  733           sender [ 18]   0.00-60.00  sec 7.01 GBytes  1.00 Gbits/sec  708           sender [ 20]   0.00-60.00  sec 8.76 GBytes  1.25 Gbits/sec  618           sender [SUM]   0.00-60.00 sec  55.2 GBytes  7.90 Gbits/sec  4176             sender   Summarize : The i.MX95 10GbE interface achieved approximately 7.90 Gbit/s TCP throughput with 8 parallel streams in the Server-to-Client direction. During the 60-second test, 55.2 GBytes of data were transferred, with 4176 TCP retransmissions reported.
記事全体を表示
The purpose of this document is to provide supportive information for selection of suitable LPDDR4, DDR4 and DDR3L devices that are supported by i.MX 8M family of processors to aid project feasibility assessment capabilities of customers that are evaluating the SoCs for usage in their products.  It is strongly recommended to consult with NXP and the memory vendor the final choice of the memory part number to ensure that the device meets all the compatibility, availability, longevity and pricing requirements. Please note that some of the LPDDR4 devices may not support operation at low speeds and in addition, DQ ODT may not be active, which can impact signal integrity at these speeds. If low speed operation is planned in the use case, please consult with the memory vendor the configuration aspects and possible customization of the memory device so correct functionality is ensured. In all cases, it is strongly recommended to follow the DRAM layout guidelines outlined in the NXP Hardware Developer's Guides for the specific SoCs available on NXP.com Memory devices with binary densities (e.g., 1 GB, 2 GB, 4 GB) are preferred because they simplify memory management by aligning with system addressing schemes and reducing software complexity. For any questions related to specific DRAM part numbers please contact the respective DRAM vendor. For any questions regarding the i.MX SoC please contact your support representative or enter a support ticket.  LPDDR4 - maximum supported densities Please note that the SoCs only support memory devices that support either the LPDDR4 mode or support both LPDDR4 and LPDDR4X modes. Memory devices that support only the LPDDR4X mode are not supported. SoC Max data bus width Maximum density Assumed memory organization Notes i.MX 8M Quad 32-bit 32Gb/4GB dual rank, dual-channel  device with 16-row addresses (R0-R15) 1, 2, 4 i.MX 8M Mini  32-bit 64Gb/8GB dual rank, dual-channel  device with 17-row addresses (R0-R16) 1, 2 i.MX 8M Nano  16-bit 32Gb/4GB dual rank, single-channel  device with 17-row addresses (R0-R16) 1, 2, 3, 12 i.MX 8M Plus  32-bit 64Gb/8GB dual rank, dual-channel  device with 17-row addresses (R0-R16)  1, 2   LPDDR4 - list of validated memories Please note that the validation process is an ongoing effort - regular updates of the table are expected. Please contact NXP if a specific vendor or configuration is required. SoC Density Memory Vendor Validated Memory Part#  Notes i.MX 8M Quad  24Gb/3GB    Micron MT53B768M32D4NQ-062 WT:B  15 32Gb/4GB Micron MT53D1024M32D4DT-046 AAT:D  14 4Gb/512MB ISSI IS43LQ16256B-062BLI  5, 14 8Gb/1GB ISSI IS43LQ32256B-062BLI  5, 14 i.MX 8M Mini 16Gb/2GB Micron MT53D512M32D2DS-053 WT:D  15 16Gb/2GB    ESMT M56Z16G32512A-SMBIG 5, 14 32Gb/4GB Micron MT53E1G32D2FW-046 WT:A  5, 14 64Gb/8GB Micron MT53E2G32D4DT-046 AIT:A  5, 14 64Gb/8GB Micron MT53E2G32D4DE-046 AUT:C 5, 14 32Gb/4GB Intelligent Memory IMBG32L4KBB 5,14 32Gb/4GB Kingston B3221PM3BDGUI -U 5 16Gb/2GB Kingston D1621PM4CDGVIW-U related PNs also covered by the test: D1621PM4CDGUI-U D1621PM4CDGUIW-U D1621PM4CDGVI-U 5 i.MX 8M Nano  16Gb / 2GB  Kingston C1612PC2WDGTKR-U  15 16Gb / 2GB  Kingston  D1611PM3BDGUI-U 5,14 32Gb / 4GB Micron MT53E2G32D4DT-046 AIT:A  5, 13, 15 16Gb / 2GB Intelligent Memory  IMAG16L4KBB 5,14 4Gb / 512MB Nanya NT6AN256M16AV-J2 5,14 4Gb / 512MB  Winbond W66CP6RBQAHJ 5,14 8Gb / 1GB ISSI IS43LQ16512A-053BLI 5,14 8Gb / 1GB  Micron MT53D512M32D2DS-053 WT:D 13, 15   i.MX 8M Plus         48Gb/6GB  Micron MT53E1536M32D4DT-046 WT:A  15 64Gb/8GB  Micron MT53E2G32D4DE-046 AUT:C  5, 14 32Gb/4GB Samsung K4FBE3D4HB-KHCL  5, 14 32Gb/4GB Kingston B3221PM3BDGVIW-U 5, 14 64Gb/8GB Kingston Q6422PM3BDGVK-U  5, 14 8Gb/1GB Winbond W66DP2RQQAHJ  5, 14 32Gb/4GB ISSI IS46LQ32K01S2A-046BLA2 5, 14 16Gb/2GB ISSI IS46LQ32512A-046BLA3 5 32Gb/4GB ISSI IS43LQ32K01S2A-046BLI 5, 14 32Gb/4GB IM IMBG32LK4BBG-046I 5, 14 32Gb/4GB Nanya NT6AN1024F32AV-J2 5, 14 32Gb/4GB Nanya NT6AT1024T32AV-J1 5 16Gb/2GB Gigadevice GDB4CBQA-ML 5   LPDDR4 - list of incompatible devices Given the limitations mentioned in this document, the following memory devices were identified as incompatible with the particular SoCs as detailed in the following table:   Memory Vendor Memory Part# Density Incompatible SoCs Incompatibility reason Samsung K4FHE3S4HA-KU(H/F)CL 24Gb/3Gb i.MX 8M Quad  The memory device requires 17th row address bit to function. Samsung K4UHE3S4AA-KU(H/F)CL K4UJE3D4AA-KU(H/F)CL 24Gb/3Gb 48Gb/6GB i.MX 8M Quad i.MX 8M Mini i.MX 8M Nano i.MX 8M Plus The memory device only supports the LPDDR4X mode. Samsung K4FCE3Q4HB-KU(H/F)CL K4UCE3Q4AB-KU(H/F)CL 64Gb/8GB i.MX 8M Quad i.MX 8M Mini i.MX 8M Nano i.MX 8M Plus A byte mode memory device. The memory device only supports the LPDDR4X mode.    DDR4 - maximum supported densities SoC Max data bus width Maximum density Assumed memory organization Notes i.MX 8M Quad  32-bit 32Gb/4GB x16, 16Gb device with 1 bank group address, 17-row addresses and 10 column addresses 1, 6 i.MX 8M Mini  32-bit 64Gb/8GB x16, 16Gb device with 1 bank group address, 17-row addresses and 10 column addresses 1, 7 i.MX 8M Nano  16-bit 64Gb/8GB x8, 16Gb device with 2 bank group addresses, 17-row addresses and 10 column addresses 1, 8 i.MX 8M Plus  32-bit 64Gb/8GB x16, 16Gb device with 1 bank group address, 17-row addresses and 10 column addresses 1, 7   DDR4 - list of validated memories Please note that the validation process is an ongoing effort - regular updates of the table are expected. Please contact NXP if a specific vendor or configuration is required.   SoC Density Memory Vendor Validated Memory Part#  Notes i.MX 8M Quad 32Gb/4GB Micron 4x MT40A512M16JY-083EAAT  15 i.MX 8M Mini  16Gb/2GB Micron 2x MT40A512M16LY-075:E  15 i.MX 8M Nano 16Gb/2GB Micron 1x MT40A1G16RC-062E:B  15 8Gb/1GB Rayson 1x RS512M16Z2DD-62DT 14 8Gb/1GB UniIC SCB12Q8G160BF-06SI 14 i.MX 8M Plus 64Gb/8GB Micron 4x MT40A1G16RC-062E:B  15 16Gb/2GB Nanya NT5AD512M16C4-JRI  14   DDR3L - maximum supported densities SoC Max data bus width Maximum density Assumed memory organization Notes i.MX 8M Quad  32-bit 32Gb/4GB x16, 8Gb device with 16-row addresses and 10 column addresses 1, 9 i.MX 8M Mini  32-bit 64Gb/8GB x8, 8Gb device with 16-row addresses and 11 column addresses 1, 10 i.MX 8M Nano  16-bit 32Gb/4GB x8, 8Gb device with 16-row addresses and 11 column addresses 1, 11 i.MX 8M Plus  i.MX 8M Plus does not support DDR3L   DDR3L - list of validated memories Please note that the validation process is an ongoing effort - regular updates of the table are expected. Please contact NXP if a specific vendor or configuration is required. SoC Density Vendor Validated Memory Part#  Notes i.MX 8M Quad  16Gb/2GB Micron 4x MT41K256M16TW-107 AAT  14 i.MX 8M Mini  16Gb/2GB Micron 4x MT41K256M16TW-107 AAT  14              i.MX 8M Nano 8Gb/1GB Micron MT41K512M16VRN-107  15   Note 1: The numbers are based purely on the IP vendor documentation for the DDR Controller and the DDR PHY, on the settings of the implementation parameters chosen for their integration into the SoC, and on the JEDEC standards JESD209-4/JESD209-4A (LPDDR4), JESD279-4/JESD279-4A (DDR4), and JESD79-3E/JESD79-3F/JESD79-3-1A (DDR3/DDR3L). Therefore, they are not backed by validation, unless said otherwise and there is no guarantee that an SoC with the specific density and/or desired internal organization is offered by the memory vendors. Should the customers choose to use the maximum density and assume it in the intended use case, they do it at their own risk. Note 2: Byte-mode LPDDR4 devices (x16 channel internally split between two dies, x8 each) of any density are not supported therefore, the numbers are applicable only to devices with x16 internal organization (referred to as "standard" in the JEDEC specification). Note 3: The memory vendors often do not offer so many variants of single-channel memory devices. As an alternative, a dual-channel device with only one channel connected may be used. For example: A dual-rank, single-channel device with 16-row address bits has a density of 16Gb. If such a device is not available at the chosen supplier, a dual-rank, dual-channel device with 16-row address bits can be used instead. This device has a density of 32 Gb however since only one channel can be connected to the SoC, only half of the density is available (16 Gb). Usage of more than one discrete memory chips to overcome market constraints is not supported since only point-to-point connections are assumed for LPDDR4. Note 4: Devices with 17-row addresses (R0-R16) are not supported by the DDR Controller Note 5: The memory part number did not undergo full JEDEC verification however, it passed all functional testing items. Note 6: The density can be achieved by connecting 2 single-rank discrete devices with one 16Gb die each. Since the SoC supports x8 devices and also has connectivity for a second rank, usage of more discrete devices is possible. However, this advantage cannot be used to get higher density since this SoC has only 32Gb/4GB of address space dedicated for the DDR. Two x16 16Gb devices giving 32Gb/4GB in total is, therefore, the optimal choice that balances the maximum density aspects, the signal integrity aspects (only two discrete devices used), and bandwidth aspects (full data bus width used). Note 7: The density can be achieved by connecting 4 single rank discrete devices with one 16Gb die each, 2 devices connected to each chip select. Since the SoC supports x8 devices, the usage of more discrete devices is possible. However, this advantage cannot be used to get higher density since this SoC has only 64Gb/8GB of address space dedicated for the DDR. Four x16 16Gb devices giving 64Gb/8GB in total is the optimal choice that balances the maximum density aspects, the signal integrity aspects (only four discrete devices used), and the bandwidth aspects (full data bus width used). Note 8: The density can be achieved by connecting 4 single rank discrete devices with one 16Gb die each, 2 devices connected to each chip select.  Note 9: The density can be achieved by connecting 4 single rank discrete devices with one 8Gb die each, 2 devices connected to each chip select, or by connecting 2 dual rank discrete devices with two 8Gb dies each. Since the SoC supports x8 devices, the usage of more discrete devices is possible. However, this advantage cannot be used to get higher density since this SoC has only 32Gb/4GB of address space dedicated for the DDR. Four x16 8Gb devices giving 32Gb/4GB in total is, therefore, the optimal choice that balances the maximum density aspects, the signal integrity aspects (four discrete devices used), and bandwidth aspects (full data bus width used). Note 10: The density can be achieved by connecting 8 single rank discrete devices with one 8Gb die each, 4 devices connected to each chip select or by connecting 4 dual rank discrete devices with two 8Gb dies each. Note that the first option significantly exceeds the number of devices used on the validation board (4 discrete devices) therefore, it is not guaranteed that the i.MX would be able to drive the signals with margin to the required voltage levels due to increased loading on the traces. A significant effort would be required in terms of PCB layout and signal integrity analysis. Practically, it is not recommended to use more than 4 discrete DDR3L devices. This corresponds to the maximum density of 32Gb/4GB in the case of the single rank devices containing one 8Gb die or 64Gb/8GB in case of the dual-rank devices, each containing two 8Gb dies. Note 11: The density can be achieved by connecting 4 single rank discrete devices with one 8Gb die each, 2 devices connected to each chip select or by connecting 2 dual rank discrete devices with two 8Gb dies each. Note 12: For single-channel (x16) memory devices, the current maximum available density in the market is 16Gb/2GB (Q1 2022). Note 13: Only one channel of the device (and hence, half of its density) was utilized due to the reduced data bus width (x16) of the SoC. Note 14: Part is active. Reviewed Jan 2026 Note 15: Part will either EoL or is not recommended for new designs by the respective vendor.   Additional Links https://community.nxp.com/t5/iMX-and-Vybrid-Support/i-MX-8-8X-8XL-maximum-supported-LPDDR4-and-DDR3L-densities/ta-p/1152715           
記事全体を表示
This document is Q&A about the i.MX Functional Safety Concept Guide, materials based on Safety Academy: Designing for Safety Critical Systems Table of Contents What is functional safety? What is the difference between functional safety and security? How does functional safety prevent unacceptable risks? What are the differences between ISO 26262 and IEC 61508? List the key differences in detail. Using motor control as an example, how does industrial functional safety differ from automotive functional safety? Give examples of SIL/ASIL optimization techniques. What types of failures are there, and how are they defined? How do IEC 61508 and ISO 26262 define fault-handling time differently? What are common misconceptions about functional safety? What does NXP FuSa include? What role does NXP play, and what development processes and platforms does it provide? What are the two functional safety development models? What device types are used in functional safety implementations? What is the i.MX95 EENV architecture? Explain its architectural design in detail. How are the i.MX95 functional safety mechanisms implemented? What FuSa software packages does NXP provide, and what does each do? Analyze the i.MX FuSa software architecture. Analyze the i.MX Auto FuSa software architecture. How does it differ from standard FuSa? Introduce SCST and its software flow. Introduce SAF and its key components. Which parts of SM can customers modify? Do such changes trigger recertification? What are the automotive application scenarios for i.MX? Using DMS as an example, break down the functional safety concept. How does the ISO standard classify faults? What are PFH and PFD, and how are they calculated? What functional safety deliverables does NXP provide to customers? What exactly has NXP had certified by TÜV SÜD? What is the purpose of NXP's Safety Manual, and how does it help customers? How should ISO 26262 be addressed during hardware development? What is the process? What does a hardware fault mean, and how can hardware faults be analyzed quantitatively? What is the V-model for software development in ISO 26262? What software safety analysis methods are available? How are hazardous events classified in HARA? What is a complete HARA example? Explain with an example. What are FSC and TSC? Explain their decomposition process.
記事全体を表示
Background: The OCOTP_CTRL module is a hardware IP block that manages access to the eFuses. It provides read/write access to internal eFuses and it loads the eFuse values into shadow registers for normal software access.   In this article, Will explain how to read security-sensitive fuses that are not accessible via FSB (Fuse Status Block) on i.MX9x devices, by using the ELE "Read Shadow Fuse" command through the S3MU messaging interface.   Take the following “SJC_DISABLE” example as an illustration: As shown in the figure below, SJC_DISABLE corresponds to word57, with a hexadecimal value of 0x39.       1. Each message sent to ELE via S3MU starts with a 32-bit header, consisting of four fields: Tag (must be 0x17), Command (command ID), Size (message length in words, 1–255), and Ver (must be 0x06). The corresponding command for reading registers is 0xF3. 2. ELE's response also starts with a 32-bit header: Tag (must be 0xe1), Command (echoes the original command ID), Size (response length in words, 1–255), and Ver (must be 0x06). 3. Test: Reading the i.MX 93 SJC_DISSBLE Note: This API can be called only in OEM OPEN life cycles.
記事全体を表示
Background: By default, the i.MX 8QM uses UART0 as the AP UART. However, some customers use UART1 as the AP UART when employing the DDR stress test tool. This article uses the i.MX8QM MEK as an example to provide a detailed guide on how to reconfigure the AP UART to UART1.   1. HW re-work: On the i.M8QM MEK board, UART1 is not directly connected to the FTDI chip associated with the "Micro USB Debug Interface" (J18). To use UART1, a hardware modification (HW re-work) is required. A hardware rework connects the MX8QM’s UART1 to the “FTDID_TX” and “FTDID_RX” ports of the FTDI chip. 1.1 : Ensure that no Bluetooth module is installed.                 1.2 : Connect BT_UART1_RX to U62.12; Connect BT_UART1_TX to U10.10; connect FTDID_TX to U62.5; connect FTDID_RX to U62.7              2. SW configure Edit the .ds script to add the UART1 port configuration at the end of the file.  Add the following line at the end of the .ds file: memory set  0x5C01042C 32   0x00000001   # UART1 port selection for AP UART    3. Test For the DDR stress test, please select the fourth COM port option, which corresponds to UART1. UART1 is connected to "FTDID_TX" and "FTDID_RX"—this maps to the fourth COM port.  
記事全体を表示
What actually happens between powering on an i.MX95 system and reaching a Linux login prompt? The answer involves far more than a bootloader and a kernel. This QEMU-based i.MX95 emulation turns that otherwise difficult-to-observe sequence into a reproducible virtual laboratory for students, hobbyists, and engineers who want to study the complete boot chain without relying entirely on physical hardware.
記事全体を表示
Processor and Board Support i.MX 8M Mini EVK i.MX 8M Nano EVK i.MX 8M Plus EVK i.MX 8M Quad EVK i.MX 91 EVK i.MX 93 EVK i.MX 93W EVK i.MX 95 15x15 EVK i.MX 95 19x19 EVK FRDM-IMX8MPLUS FRDM-IMX91 FRDM-IMX91S FRDM-IMX93 FRDM-IMX93W FRDM-IMX95 FRDM-IMX95-PRO OpenWrt and Toolchain OpenWrt from mainline (date: 29 Jun 2026, commit: f0a60eee2fe tag: v25.12.5) Toolchain:  ARMV8: GCC 14.3.0, GNU Binutils 2.44 U-Boot Bootloader i.MX SDK release, tag: lf-6.12.49-2.2.0 v2025.04 Linux Kernel OpenWrt kernel 6.12.94 based on IMX SDK release kernel lf-6.12.49-2.2.0 Firmware firmware-imx-8.30 Features Squashfs rootfs support on SD card. Support CLI and web configuration. U-Boot Boot Loader - U-Boot: lf-6.12.49-2.2.0. - Arm Trusted firmware (TF-A) integration. - Boot from SDHC Linux Kernel Core - Linux kernel 6.12.49 - Cortex-A53 (AARCH64), little endian for imx8m platforms - Cortex-A55 (AARCH64), little endian for imx9 platforms - 64-bit effective kernel addressing Linux Kernel Drivers - SDIO 3.0 / eMMC5.1 - USB 3.0/2.0 Dual-Role with PHY type C - 32-bit LPDDR4/LPDDR5 - 2x Gigabit Ethernet with AVB, IEEE 1588, EEE   and 1x w/ TSN - PCIe Gen 3 + WIFI - CAN FD - Dual-ch. QuadSPI (XIP) or 1x OctalSPI(XIP) - RTC - IW610/IW612 WiFi module - Bluetooth Licensing The majority of the software included in the OpenWrt release is licensed under a form of open source license (e.g. GPL, BSD). Some software is licensed under the NXP EULA license.  How to obtain this release The source code of the OpenWrt release can be got from the following link: https://github.com/nxp-imx/imx_openwrt   branch: imx-openwrt-25.12 tag: imx_v25.12_v6.12.49 The user guide can be found in the below link for build and deployment on IMX targets: https://github.com/nxp-imx/imx_openwrt/blob/imx-openwrt-25.12/target/linux/imx/README
記事全体を表示
Important: If you have any questions or would like to report any issues with the DDR tools or supporting documents please create a support ticket in the  i.MX community. Please note that any private messages or direct emails are not monitored and will not receive a response. NOTE: Please note that DDR support for the i.MX 8M Family and has also been added in the Config Tools for i.MX Applications Processors | NXP Semiconductors Please consider using this tool with more enhanced features. i.MX 8M Family DDR Tools Overview The i.MX 8M Family DDR Tool is a Windows-based software to help users to do LPDDR4/DDR4/DDR3L training, stress test and DDR initial code generation for u-boot SPL. This page contains the latest releases for the i.MX 8M Family DDR Tools and cover the following SoCs : i.MX 8M Quad and its derivatives i.MX 8M Quadlite and i.MX 8M Dual i.MX 8M Mini Quad and its derivatives i.MX 8M Mini Quadlite/Dual/DualLite/Solo/SoloLite  i.MX 8M Nano Quad and its derivatives i.MX 8M Nano Quadlite/Dual/DualLite/Solo/SoloLite  i.MX 8M Plus   NOTE: For the i.MX 8/8X Family of DDR tools please refer to the: i.MX 8/8X Family DDR Tools Release   The purpose of the i.MX 8M Family DDR Tools is to enable users to generate and test a custom DRAM initialization based on their device configuration (density, number of chip selects, etc.) and board layout (data bus bit swizzling, etc.).  This process equips the user to then proceed with the bring-up of a boot loader and an OS.  Once the OS is brought up, it is recommended to run an OS-based memory test (like Linux memtester) to further verify and test the DDR memory interface.     The i.MX 8M Family DDR Tools consist of: DDR Register Programming Aid (RPA) MSCALE DDR Tool   For more details regarding these DDR tools and their usage, refer to the i.MX 8M DDR Tools User Guide.   i.MX 8M Family DDR Tool    The i.MX 8M Family DDR stress test tool is a Windows-based software tool that is used as a mechanism to verify that the DDR initialization is operational for use with u-boot and OS bring-up. To install the DDR Stress Test, save and extract the zip file mscale_ddr_tool_vXXX_setup.exe.zip   (where 'xxx' is the current version number) and follow the on-screen installation instructions.   i.MX 8M Family DDR Tool Requirements   The tool requires access to the Windows registry, hence users must run it in administrator mode. When users design new i.MX 8M Family boards, please make sure to follow the rules outlined in the respective Hardware Developers Guide and the MSCALE_DDR_Tool_User_Guide, which can help users bring up DDR devices on their respective i.MX 8M boards.   i.MX 8M Family DDR Tool User Guide   The i.MX 8M DDR tool includes the document: MSCALE_DDR_Tool_User_Guide NOTE: Please read the MSCALE_DDR_Tool_User_Guide inside the package carefully before you use this tool.   i.MX8M DDR Tool Revision History   Rev Major Changes* (Features) Comments 3.31 Integration of the workaround for 8MQ ERR051273   3.30 Fix DBI enabled issue for all i.MX 8M series Automatically identify ROHM and PCA9450 PMICs on i.MX 8M Nano board Fix 4GB/8GB memory tester issues   3.20 Add support to i.MX 8M Plus   3.10 Fixe UART communication issues for some specific characters between the PC software and the target board. Fine-tune DDRPHY registers in generated C code.   3.00 Add support to i.MX8M-nano Add support to different PMIC or PMIC configuration Add support to stress test for all DDR frequency points RPA tools for Nano include support for DDR3L, DDR4, and LPDDR4.   Note that the DDR3L and LPDDR4 RPAs contain the name preliminary only to denote that these RPAs are based on internal NXP validation boards where the DDR4 RPA is based on the released EVK.   2.10 Change DDR4 capacity computing method   2.00 Add support to i.MX8M-mini   * Further details available in the release notes   Sample configuration in the .ds script for i.MX 8M debug UART2: ################step 0: configure debug uart port. Assumes use of UART IO Pads.   ##### ##### If using non-UART pads (i.e. using other pads to mux out the UART signals), ##### ##### then it is up to the user to overwrite the following IO register settings   ##### memory set 0x3033023C 32 0x00000000 #IOMUXC_SW_MUX_UART2_RXD memory set 0x30330240 32 0x00000000 #IOMUXC_SW_MUX_UART2_TXD memory set 0x303304A4 32 0x0000000E #IOMUXC_SW_PAD_UART2_RXD memory set 0x303304A8 32 0x0000000E #IOMUXC_SW_PAD_UART2_TXD memory set 0x303304FC 32 0x00000000 #IOMUXC_SW_MUX_UART2_SEL_RXD sysparam set debug_uart   1 #UART index from 0 ('0' = UART1, '1' = UART2, '2' = UART3, '3' = UART4)   Sample configuration in the front of the .ds script for i.MX 8M debug UART3  ################step 0: configure debug uart port. Assumes use of UART IO Pads.   ##### ##### If using non-UART pads (i.e. using other pads to mux out the UART signals), ##### ##### then it is up to the user to overwrite the following IO register settings   ##### memory set 0x30330244 32 0x00000000 #IOMUXC_SW_MUX_UART3_RXD memory set 0x30330248 32 0x00000000 #IOMUXC_SW_MUX_UART3_TXD memory set 0x303304AC 32 0x0000000E #IOMUXC_SW_PAD_UART3_RXD memory set 0x303304B0 32 0x0000000E #IOMUXC_SW_PAD_UART3_TXD memory set 0x30330504 32 0x00000002 #IOMUXC_SW_MUX_UART3_SEL_RXD sysparam set debug_uart   2 #UART index from 0 ('0' = UART1, '1' = UART2, '2' = UART3, '3' = UART4)   Sample configuration in the front of the .ds script for i.MX 8M Mini PMIC configuration: ##############step 0.5: configure I2C port IO pads according to your PCB design.   ##### ########### You can modify the following instructions to adapt to your board PMIC ####### memory set 0x30330214 32 0x00000010  #IOMUXC_SW_MUX_I2C1_SCL memory set 0x30330218 32 0x00000010  #IOMUXC_SW_MUX_I2C1_SDA memory set 0x3033047C 32 0x000000C6 #IOMUXC_SW_PAD_I2C1_SCL memory set 0x30330480 32 0x000000C6  #IOMUXC_SW_PAD_I2C1_SDA sysparam set pmic_cfg 0x004B #bit[7:0] = PMIC addr,bit[15:8]=I2C Bus. Bus index from 0 ('0' = I2C1, '1' = I2C2, '2' = I2C3, '3' = I2C4) sysparam set pmic_set 0x2F01 #bit[7:0] = Reg val, bit[15:8]=Reg addr. #REG(0x2F) = 0x01 sysparam set pmic_set 0x0C02   #REG(0x0C) = 0x02 sysparam set pmic_set 0x171E   #REG(0x17) = 0x1E sysparam set pmic_set 0x0C00   #REG(0x0C) = 0x00 sysparam set pmic_set 0x2F11    #REG(0x2F)=0x11     i.MX 8M Family DDR Register Programming Aid (RPA) The i.MX 8M DDR RPA (or simply RPA) is an Excel spreadsheet tool used to develop DDR initialization for a user’s specific DDR configuration (DDR device type, density, etc.). The RPA generates the DDR initialization(in a separate Excel worksheet tab):   DDR Stress Test Script: This format is used specifically with the DDR stress test by first copying the contents in this worksheet tab and then pasting it to a text file, naming the document with the “.ds” file extension. The user will select this file when executing the DDR stress test. The How to Use Excel worksheet tab provides instructions on using the RPA   i.MX 8M Family DDR Register Programming Aid (RPA): Current Versions To obtain the latest RPAs, please refer to the following links (note, existing RPAs have been removed from this main page and moved to the SoC specific links below): i.MX 8M Quad : https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX8M-m850D-DDR-Register-Programming-Aid-RPA/ta-p/1172441 i.MX 8M Mini : https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX8MMini-m845S-DDR-Register-Programming-Aid-RPA/ta-p/1172443 i.MX 8M Nano: https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX8MNano-m815S-DDR-Register-Programming-Aid-RPA/ta-p/1172444 i.MX 8M Plus: https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8MPlus-m865S-DDR-Register-Programming-Aids-RPA/ta-p/1235352   Processor Mask Revisions Memory Supported Latest RPA Version * i.MX 8M Quad & Derivatives All LPDDR4 Rev 36 i.MX 8M Quad & Derivatives All DDR4 Rev 20 i.MX 8M Quad & Derivatives All DDR3L Rev 12 i.MX 8M Mini & Derivatives A0 LPDDR4 Rev 25 i.MX 8M Mini & Derivatives A0 DDR4 Rev 23 i.MX 8M Mini & Derivatives A0 DDR3L Rev 12 i.MX 8M Nano & Derivatives A0 LPDDR4 Rev 12 i.MX 8M Nano & Derivatives A0 DDR4 Rev 14 i.MX 8M Nano & Derivatives A0 DDR3L Rev 8 i.MX 8M Plus & Derivatives A1 LPDDR4 Rev 11 i.MX 8M Plus & Derivatives A1 DDR4 Rev 11 * For the details about the updates, please refer to the Revision History tab of the respective RPA.    To modify the DRAM Frequency for a custom setting refer to iMX 8M Mini Register Programming Aid DRAM PLL setting    Related Resources Links: Config Tools for i.MX Applications Processors | NXP Semiconductors i.MX 8M Mini Register Programming Aid DRAM PLL setting  i.MX 8/8X Series DDR Tool Release  i.MX 6/7 DDR Stress test GUI Tool i.MX 8M Application Processor Related Resources i.MX8M (m850D) DDR Register Programming Aid (RPA)  i.MX8MMini (m845S) DDR Register Programming Aid (RPA)  i.MX8MNano (m815S) DDR Register Programming Aid (RPA) i.MX 8MPlus (m865S) DDR Register Programming Aids (RPA)   i.MX 8ULP DDR tools: i.MX Software and Development Tools | NXP Semiconductors Scroll down to “Other Resources --> Tools --> DDR Tools”  
記事全体を表示
This is a detailed programming aid for the registers associated with i.MX 8MNano (m815S) DDR initialization.  For more details, refer to the main mScale DDR tools page: https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8M-Family-DDR-Tool-Release/ta-p/1104467 Please note that this page is only intended to store the RPA spreadsheets. For questions, please create a new community thread.
記事全体を表示
This is a detailed programming aid for the registers associated with i.MX 8MMini (m845S) DDR initialization.  For more details, refer to the main mScale DDR tools page: https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8M-Family-DDR-Tool-Release/ta-p/1104467 Please note that this page is only intended to store the RPA spreadsheets. For questions, please create a new community thread.
記事全体を表示
This is a detailed programming aid for the registers associated with i.MX 8M (m850D) DDR initialization.  For more details, refer to the main mScale DDR tools page: https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8M-Family-DDR-Tool-Release/ta-p/1104467 Please note that this page is only intended to store the RPA spreadsheets. For questions, please create a new community thread.
記事全体を表示
  This is a detailed programming aid for the registers associated with i.MX 8M Plus DDR initialization. LPDDR4 DDR4  For more details, refer to the main mScale DDR tools page: https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-8M-Family-DDR-Tool-Release/ta-p/1104467 Please note that this page is only intended to store the RPA spreadsheets. For questions, please create a new community thread.  
記事全体を表示
Here's the imx-power-estimation SKILL for any AI agents: name: imx-power-estimation description: Estimate the Power Consumption for i.MX95/952/943 SoC. Use this skill when user ask for the i.MX SoC power consumption with their application scenarios. Input: Describe your use case in natural language. e.g: "estimate the power consumption of i.MX95 for Automotive IVI use cases.". You can also specify the temperature/corner/mode, as well as the IP modules usage/bandwidth, like 2xA55 core running 50% loading, DDR bandwidth 30%, 1xETH 500Mbps. Output: Detailed power breakdown by voltage rail with total consumption
記事全体を表示
The purpose of this document is to provide extended guidance for selection of compatible LPDDR5 and LPDDR4x memory devices that are supported by the i.MX 95 and i.MX 952/937 processors. In all cases, it is strongly recommended to follow the DRAM layout guidelines outlined in the NXP Hardware Developer's Guides for the specific SoCs. Please note that some of the LPDDR4x devices may not support operation at low speeds and in addition, DQ ODT may not be active, which can impact signal integrity at these speeds. If low speed operation is planned in the use case, please consult with the memory vendor the configuration aspects and possible customization of the memory device so correct functionality is ensured. LPDDR5 - maximum supported densities SoC Max Data bus width Maximum density Assumed memory organization Notes i.MX 95 32-bit 128Gb/16GB dual rank, dual channel device with 17-row addresses and x8 (byte mode) organization 1, 3, 7 i.MX 952 32-bit 128Gb/16GB dual rank, dual channel device with 17-row addresses and x8 (byte mode) organization 1, 3, 7, 9 i.MX 937 32-bit 128Gb/16GB dual rank, dual channel device with 17-row addresses and x8 (byte mode) organization 1, 3, 7, 9   LPDDR5 - list of validated memories Note: The memory vendors often list their devices as LPDDR5x in their high-level product information while in fact, they are in most cases backward compatible with the LPDDR5 mode. This may lead to the false impression that there are not so many LPDDR5 devices on the market. In such cases, it is strongly recommended to check the full datasheet to confirm if the device is in fact LPDDR5/LPDDR5x or LPDDR5x only. The SoC cannot be used with devices that only support the LPDDR5X mode. The validation process is an ongoing effort - regular updates of the table are expected. SoC Density Memory Vendor  Validated Memory Part#  Notes i.MX 95 128Gb/16GB Micron MT62F4G32D8DV-023 FAAT:C - 64Gb/8GB  Samsung K3KL9L90QM-MHCT - 32Gb/4GB  Samsung K3KL8L80QM-MHCT 2 32Gb/4GB  Samsung K3KL8L80EM-MUCV 2        64Gb/8GB  SK HYNIX H58G66DK9VX067N 2 64Gb/8GB Micron MT62F2G32D4DS-023 FAAT:C 2, 6 32Gb/4GB Micron MT62F1G32D2DS-020 WT:D 2 16Gb/2GB Micron MT62F1G16D1DS-023 IT:B 2 64Gb / 8GB Rayson RS2G32LO5D24DB-31BT 2 32Gb/4GB Rayson ATL5X4G32M7E-31IT 2 64Gb / 8GB CXMT CXDB6CCBM-MA-A 2 i.MX 952 128Gb/16GB Micron MT62F4G32D8DV-023 FAAT:C 9 32Gb/4GB Micron MT62F1G32D2DS-020 WT:D 2 i.MX 937 128Gb/16GB Micron MT62F4G32D8DV-023 FAAT:C 9   LPDDR5 - list of incompatible devices The SoC cannot be used with memory devices that only support the LPDDR5x mode. LPDDR4x - maximum supported densities SoC Max Data bus width Maximum density Assumed memory organization Notes i.MX 95 32-bit 128Gb/16GB dual rank, dual channel device with 17-row addresses 1 i.MX 952 32-bit 128Gb/16GB dual rank, dual channel device with 17-row addresses 1, 9 i.MX 937 32-bit 128Gb/16GB dual rank, dual channel device with 17-row addresses and x8 (byte mode) organization 1, 3, 7, 9   LPDDR4x - list of validated memories   The validation process is an ongoing effort - regular updates of the table are expected. SoC Density Memory Vendor Validated Memory Part# Notes i.MX 95 64Gb/8GB Micron   MT53E2G32D4DE-046 AUT:C  5 8Gb/1GB Micron MT53E256M32D1KS-046 IT:L 2 128Gb/16GB Micron MT53E4G32D8GS-046 2 64Gb/8GB SK Hynix H54G66BYYVPX104 2 32Gb/4GB Intelligent Memory IMBG32L4KBB_V10 2 48Gb/6GB Micron MT53E1536M32D4DT-046 WT:A 3, 8 24Gb/3GB Micron MT53E768M32D4DT-053 AIT:E 3, 8 8Gb/1GB Samsung K4U8E3S4ADGHCL  2 32Gb/4GB Intelligent Memory IMBG32LK4BBG-046I 2 32Gb/4GB Alliance Memory AS4C1G32MD4V-046BIN 2 64Gb/8GB Rayson ATL4X8G32M2D-46IT 2 64Gb/8GB Rayson ATL4X8G32M2D-46AIT 2 64Gb/8GB DW DWCTB36HLC0 2 8Gb/1GB Alliance Memory AS4C256M32MD4V-062BAN 2 32Gb/4GB ISSI IS46LQ32K01S2A-046BLA2 2 32Gb/4GB Nanya NT6AT1024T32AV-J1 2 64Gb/8GB Nanya NT6AT2048F32AV-J1 2 64Gb/8GB Rayson RS2G32LR4D4BNR-46BT 2 i.MX 952 64Gb/8GB Micron   MT53E2G32D4DE-046 AUT:C  9 i.MX 937 64Gb/8GB Micron MT53E2G32D4DE-046 AUT:C  9   LPDDR4/4X - list of incompatible devices Note: This SoC supports LPDDR4x memory devices. This SoC is not compatible with memories that only support LPDDR4. Combo Devices that support both LPDDR4x and LPDDR4 are compatible with the SoC. Note 1: The numbers are based purely on the IP documentation for the DDR Controller and the DDR PHY, on the settings of the implementation parameters chosen for their integration into the SoC, SoC reference manual and on the JEDEC standards JESD209-5 (LPDDR5) and JESD209-4C/JESD209-4-1 (LPDDR4/4X). Therefore, they are not backed by validation, unless said otherwise and there is no guarantee that an SoC with the specific density and/or desired internal organization is offered by the memory vendors. Should the customers choose to use the maximum density and assume it in the intended use case, they do it at their own risk. Note 2: The memory part number did not undergo full JEDEC verification however, it passed all functional testing items. Note 3: Memory devices with binary densities (e.g., 1 GB, 2 GB, 4 GB) are preferred because they simplify memory management by aligning with system addressing schemes and reducing software complexity. Note 4: All memory parts are available at vendors unless stated otherwise. Checked Q3 2026 Note 5: Memory device supports both LPDDR4x and LPDDR4, however can only be used in LPDDR4x mode Note 6: Not validated by NXP but confirmed working on a non NXP Board Note 7: The maximum density supported may change in the future when DRAM vendors make higher density options available Note 8: This DRAM part number is not recommended for new designs Note 9: This SoC is in Pre-Production
記事全体を表示
SPI NAND boot on i.MX8ULP This article is about the SPI NAND boot on the i.MX8ULP, some customers using the i.MX8ULP want to use the SPI NAND on it. We just have verified the NOR NAND on the i.MX8ULP EVK board, for the SPI NAND use customers do not clear and do not know how to realized, here will give details steps and modifications for customers to refer to. 1\The boot mode support on the i.MX8ULP For the i.MX8ULP support many kinds of external memory devices SD, eMMC, SPI NOR and Flash SPI NAND Flash.   Compared to traditional parallel NAND (which requires GPMI/NFC controllers), SPI NAND can be accessed through a serial FlexSPI interface. For the i.MX8ULP for the SPI NAND use need to connect to the FlexSPI2 interface. 2\ Hardware SPI NAND boot configuration On the i.MX8ULP the SPI NAND is mounted on the FlexSPI2 interface, the configuration need to follow the section in the RM.     Boot configuration needs to follow the Table 84. Boot configuration.   In our reference design use the NOR SPI flash, for the SPI NAND connection can refer to it. 3\Software realized for the SPI NAND boot on the i.MX8ULP Make sure the hardware connections are proper. Next step is to boot up. On our 8ULP EVK board I have confirmed that do not have the SPI NAND on it. The default u-boot and the imx-mkimage flash_singleboot_m33_flexspi is for the SPI NOR, not for the SPI NAND, for the SPI NAND is using the different mechanism with SPI NOR, so if customer use ROM code read it fail, in our default released BSP do not include the build images for the 8ULP SPI NAND https://github.com/nxp-imx/imx-mkimage/blob/lf-6.18.20_2.0.0/iMX8ULP/soc.mak. So it need the special build images, and realized by customer themselves. For the i.MX8ULP ROM code already confirm that support the SPI NAND boot, so in customer’s side they need to porting in their side to support it. The SPI NAND boot mechanism for the i.MX8ULP is the same as that of the i.MX91, so we can refer to the i.MX91 design. For support the SPI NAND boot, the actual project needs to supplement U-Boot, imx mkimage, FCDBBT, download, and Linux support for related NAND part numbers. The core of SPI NAND boot is not a single binary image, but a set of data structures for ROM to identify media, bad blocks, and boot image locations. The key structures as FCB, DBBT, and Image Container. 3.1 U-boot modify Add the NAND related information and parameters in the driver: Take the Winbond NAND as an example, https://github.com/nxp-imx/uboot-imx/blob/lf-6.18.20-2.0.0/drivers/mtd/nand/spi/winbond.c   Add customized header support for SPI NAND boot in the cmd_fspinand.c (Added customized FlexSPI NAND header support: allowing different configurations to be generated for different NAND models.) https://github.com/nxp-imx/uboot-imx/blob/lf_v2026.04/arch/arm/mach-imx/cmd_fspinand.c   3.2 Add the SPI NAND support in the imx-mkimage imx-mkimage is a boot image generation tool provided by NXP, used to package multiple boot components such as U-Boot, ATF, OP-TEE, DDR firmware, ELE,SECO firmware into the final boot image (flash.bin). imx-mkimage generates the Container Images that meet Boot ROM requirements. The default code: https://github.com/nxp-imx/imx-mkimage/tree/lf-6.18.20_2.0.0/iMX8ULP Need to add the related information for the SPI NAND support refer to the i.MX91:https://github.com/nxp-imx/imx-mkimage/tree/lf-6.18.20_2.0.0/iMX91 Generate the flash_fw.bin and flash.bin . flash_fw.bin is a temporary boot image used by the UUU tool during SPI NAND programming. flash.bin is the Boot image programmed into the SPI NAND flash. The write the boot images to UUU command is: uuu -b spinand flash_fw.bin flash.bin 3.3 Kernel modify For the kernel need to add the driver and spi-nand node in the board device tree. Add the NAND related information and parameters in the driver like u-boot.   Configure FLEXSPI2 and add the SPI NAND Flash node in the board Device Tree (DTS):   Build the source code, test on the customer’s board. 4\ Trouble shooting a.Need to check the hardware design is proper, check the connection and pins mux. b.Confirm the i.MX8ULP if validation the 4KB SPI NAND Page size. For the page_data_size and page_total_size 2K      config->pageDataSize = 2048;     config->pageTotalSize = 4096; 4K     config->pageDataSize = 4096; config->pageTotalSize = 8192; Confirm if configuration the FCB to 4KB page size or still 2K. At firstly in the 91 RM we can see that there is BOOT_CFG0[7] FlexSPI_NAND_4K_Page_Selection, no describe for the i.MX8ULP. We thought need special configuration for the i.MX8ULP. But for the i.MX8ULP do not use this BOOT_CFG0[7] FlexSPI_NAND_4K_Page_Selection. And in the default ROM Code support 2K and 4K, details can see in the ROM document .       c. The FCB, DBBT, flash.bin, and all contained boot images are 4 KB aligned to match the SPI NAND page size requirement.  Make sure already confirm the FCB configure to 4KB page size. If not 4KB aligned will all met fail boot. d. uboot/arch/arm/mach-imx/cmd_fspinand.c The original code use the fspinand_prep_micron_mem_config() configure NAND's in-die ECC using a semi-hardcoded approach, then write to the SR2 register, this method will cover other key configuration bits in the Winbond W25N04L series SR2. Firstly ask customer to commit out the function of the “fspinand_prep_micron_mem_config()” to see if can pass the fail. (Commenting out the fspinand_prep_micron_mem_config() function in uboot: arch/arm/mach-imx/cmd_fspinand.c will be quick way(not a solution) to verify if this causes the boot failure.) After annotation, the spi nand can start normally, but this is only a verification method and not the final solution. Then customer try to modify the value configuration for the SR2 from 0x10 to 0x19: - config->mem_config.configCmdArgs[1] = 0x10; + config->mem_config.configCmdArgs[1] = 0x19; This works well in customer’s side. But fixed the SR2 value not suit for all customer’s situation using other vendors’ chip. NXP do not use the hard code, because this may affect other NAND customers and instead increase the customized flexspi_nand_config header support. Using the attached U-Boot and mkimage tool patches to generate the required custom header for the target SPI NAND device. Note: Please use our official patches (Already merged in NXP 2026 Q3 release) to address this issue. We have introduced support for customized flexspi_nand_config headers. Please use the attached U-Boot and mkimage tool patches to generate the required custom header for the target SPI NAND device. Please note that the changes in our mkimage patch are based on the SPI NAND implementation for the NXP release of the i.MX91 platform. Please make the corresponding modifications according to the platform you are using. If you are using the Linux 6.18.37_2.1.0 our newest released BSP, we already apply this patch.  Just make porting SPI Nand boot according the i.MX91 section code to finish. If you are using the before released version, the following two patches are needed. 0001-iMX91-soc.mak-add-flash_singleboot_spinand_customhdr.patch.txt 0001-LFU-1037-cmd_fspinand-add-customized-header-support-.patch.txt  
記事全体を表示
The purpose of this document is to provide extended guidance for the selection of compatible LPDDR4 memory devices that are supported by the i.MX 91 series of processors. In all cases, it is strongly recommended to follow the DRAM layout guidelines outlined in the NXP Hardware Developer's Guides for the specific SoCs. Memory devices with binary densities (e.g., 1 GB, 2 GB, 4 GB) are preferred because they simplify memory management by aligning with system addressing schemes and reducing software complexity.   LPDDR4 - Maximum Supported Densities SoC Max Data bus width Maximum density Assumed memory organization Notes i.MX 91 (i.MX 91xx) 16-bit 16 Gb / (2 GB) single rank, single channel device with 17-row addresses (R0 - R16) 1, 2, 3   LPDDR4 - List of Validated Memories The validation process is an ongoing effort - regular updates of the table are expected. SoC Density Memory Vendor Validated Memory Part# Notes i.MX 91 16 Gb / (2 GB) Micron MT53E1G16D1FW-046 AAT:A MT53E1G16D1ZW-046 AAT:C 5    2 Gb / (256 MB)  Winbond  W66BP6NBHAHJ 4 8 Gb / (1 GB) Nanya NT6AN512M16AV-J1I   4 Gb / (512 MB) Nanya NT6AN256M16AV-J1I 4 8 Gb / (1 GB) ISSI IS43LQ16512B-046BLI 4 12 Gb / (1.5 GB) Micron MT53E768M16D1ZW-046 4 16 Gb / (2 GB) Intelligent Memory IMAG16L4KBBG 4 2 Gb / (256 MB) Nanya NT6AN128M16AV-J1 4 4 Gb / (512 MB) UniIC SCB11N4G160BF-04ZI 4 4 Gb / (512 MB) ISSI IS43LQ16256B-053BLI 4 4 Gb / (512 MB) Winbond W66CP6RBHAHJ 4 4 Gb / (512 MB) Winbond W66CP6RBQAHJ 4     Note: This device supports operation with LPDDR4 memories only. LPDDR4x operation is not supported. Dual‑mode memories that support both LPDDR4 and LPDDR4x are allowed as long as the device can operate in LPDDR4 mode, including using LPDDR4 I/O voltage levels and initialization sequences. NOTE: LPDDR4 devices from certain memory vendors may not support operation at low speeds and in addition, DQ ODT may not be active, which can impact signal integrity at these speeds. If low-speed operation is planned in the use case, please consult with the memory vendor about the configuration aspects and possible customization of the memory device so correct functionality is ensured. Note 1: The numbers are based purely on the IP documentation for the DDR Controller and the DDR PHY, on the settings of the implementation parameters chosen for their integration into the SoC, SoC reference manual and on the JEDEC standards JESD209-4B (LPDDR4). Therefore, they are not backed by validation, unless said otherwise and there is no guarantee that an SoC with the specific density and/or desired internal organization is offered by the memory vendors. Should the customers choose to use the maximum density and assume it in the intended use case, they do it at their own risk. Note 2: Byte-mode LPDDR4 devices (x16 channel internally split between two dies, x8 each) of any density are not supported therefore, the numbers are applicable only to devices with x16 internal organization (referred to as "standard" in the JEDEC specification). Note 3: The SoC also supports dual rank single channel devices therefore, 16Gb/2GB density can be also achieved by using a dual rank single channel device with 16-row addresses (R0 - R15). Note 4: The memory part number did not undergo full JEDEC verification however, it passed all functional testing items. Note 5: The memory part number is not recommended for new designs and superseded by a new part number
記事全体を表示
We are pleased to announce that Config Tools for i.MX 26.09 are now available. Downloads & links To download the installer for all platforms, please login to our download site via:  https://www.nxp.com/design/designs/config-tools-for-i-mx-applications-processors:CONFIG-TOOLS-IMX Please refer to  Documentation  for installation and quick start guides. For further information about DDR config and validation, please go to this  blog post. Release Notes Full details on the release (features, known issues...) Version 26.09 Framework Added support for downloading all boards associated with a processor when downloading the processor. DDR tool Added support for i.MX 937 Added DDR3 support for i.MX 8MP FRDM board Added support for i.MX93W FRDM and EVK boards at 3600 MT/s Enabled PMIC PF9453 support for i.MX 91 Minor improvements, enhancements, and bug fixes SerDes tool Added support for i.MX 952 System Manager Multiple validation ID issues are resolved. DDR tool – NXP-validated memory configurations for multiple vendors is available System Manager – extended CLI support for a headless setting      
記事全体を表示
Enabling a 2-Channel CAN HAT (MCP2515) on the NXP i.MX93 FRDM Board   This article documents the process of adding hardware support for a 2-Channel CAN HAT from WaveShare using dual Microchip MCP2515 controllers over SPI on the NXP i.MX93 FRDM evaluation board. By default, the board exposes native FlexCAN interfaces, but utilizing a popular Raspberry Pi-compatible CAN HAT requires customizing the Linux device tree and kernel configuration.   Prerequisites   Hardware: NXP i.MX93 FRDM board, 2-Channel CAN HAT. Software: NXP Linux BSP (Tested in 6.18.y). Toolchain: Toolchain obtained from Yocto (Refer to the 4.5.12 How to build U-Boot and Kernel in standalone environment from i.MX Linux User's Guide).   Step 1: Modify the Device Tree   We need to edit the main board device tree file  arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts  to configure the SPI master, add the dual MCP2515 nodes, assign interrupt pins, and disable conflicting native interfaces. The key changes:   Power Regulators: Ensured the expansion connectors ( VEXP_3V3 and VEXP_5V ) correctly pull up and preserve state using pinctrl-assert-gpios . Fixed Clock: Defined an external 16MHz clock element required by the MCP2515 crystal oscillators. FlexCAN Deactivation: Disabled conflicting native flexcan2 nodes sharing pins. LPSPI3 Configuration: Replaced the default spidev dummy node with two microchip,mcp2515 nodes, adding two distinct Chip Select (CS) pins ( GPIO2_IO08 and GPIO2_IO07 ) and mapping the respective hardware interrupts ( GPIO2_IO23 and GPIO2_IO25 ). Device Tree Git Diff: diff --git a/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts b/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts index 18afe964e020..7b3af73f144f 100644 --- a/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts +++ b/arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts @@ -134,6 +134,7 @@ reg_vexp_3v3: regulator-vexp-3v3 { compatible = "regulator-fixed"; regulator-name = "VEXP_3V3"; gpio = <&pcal6524 2 GPIO_ACTIVE_HIGH>; + pinctrl-assert-gpios = <&pcal6524 2 GPIO_ACTIVE_HIGH>; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; enable-active-high; @@ -144,6 +145,7 @@ reg_vexp_5v: regulator-vexp-5v { compatible = "regulator-fixed"; regulator-name = "VEXP_5V"; gpio = <&pcal6524 8 GPIO_ACTIVE_HIGH>; + pinctrl-assert-gpios = <&pcal6524 8 GPIO_ACTIVE_HIGH>; regulator-min-microvolt = <5000000>; regulator-max-microvolt = <5000000>; enable-active-high; @@ -269,6 +271,15 @@ K3: user_btn2 { interrupts = <6 IRQ_TYPE_EDGE_FALLING>; }; }; + + clocks { + clk16m: clk16m { + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <16000000>; + clock-output-names = "clk16m"; + }; + }; }; &adc1 { @@ -292,7 +303,7 @@ &flexcan2 { pinctrl-0 = <&pinctrl_flexcan2>; pinctrl-1 = <&pinctrl_flexcan2_sleep>; xceiver-supply = <&reg_can2_stby>; - status = "okay"; + status = "disabled"; }; &mu1 { @@ -620,15 +631,29 @@ typec1_dr_sw: endpoint { &lpspi3 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_lpspi3>; - cs-gpios = <&gpio2 8 GPIO_ACTIVE_LOW>; - pinctrl-assert-gpios = <&pcal6408 0 GPIO_ACTIVE_HIGH>; + cs-gpios = <&gpio2 8 GPIO_ACTIVE_LOW>, <&gpio2 7 GPIO_ACTIVE_LOW>; + pinctrl-assert-gpios = <&pcal6408 0 GPIO_ACTIVE_LOW>; status = "okay"; - spidev0: spi@0 { + can0: can@0 { + compatible = "microchip,mcp2515"; reg = <0>; - compatible = "lwn,bk4"; - spi-max-frequency = <1000000>; + clocks = <&clk16m>; + interrupt-parent = <&gpio2>; + interrupts = <23 IRQ_TYPE_LEVEL_LOW>; + spi-max-frequency = <10000000>; }; + + can1: can@1 { + compatible = "microchip,mcp2515"; + reg = <1>; + clocks = <&clk16m>; + interrupt-parent = <&gpio2>; + interrupts = <25 IRQ_TYPE_LEVEL_LOW>; + spi-max-frequency = <10000000>; + }; + + }; &lpuart1 { /* console */ @@ -894,9 +919,12 @@ MX93_PAD_GPIO_IO29__LPI2C3_SCL 0x40000b9e pinctrl_lpspi3: lpspi3grp { fsl,pins = < MX93_PAD_GPIO_IO08__GPIO2_IO08 0x39e + MX93_PAD_GPIO_IO07__GPIO2_IO07 0x39e MX93_PAD_GPIO_IO09__LPSPI3_SIN 0x39e MX93_PAD_GPIO_IO10__LPSPI3_SOUT 0x39e MX93_PAD_GPIO_IO11__LPSPI3_SCK 0x39e + MX93_PAD_GPIO_IO23__GPIO2_IO23 0x39e + MX93_PAD_GPIO_IO25__GPIO2_IO25 0x39e >; };   After modifying the file, compile your device tree blobs (.dtb) and deploy them to your target boot partition. You can refer to the below post to know the process: How to compile Linux Kernel Image and device tree using Yocto SDK.   Step 2: Enable Kernel Driver Support   The MCP251x driver must be enabled within the Linux kernel configuration framework. Run the configuration tool: user@host:~/linux-imx$ make menuconfig   Navigate through the menu to enable the driver either statically ( [*] ) or as a module ( [M] 😞 [*] Networking support <*> CAN bus subsystem support <*> Raw CAN Protocol (raw access with CAN-ID filtering)   <*> Broadcast Manager CAN Protocol (with content filtering) <*> CAN Gateway/Router (with netlink configuration) And: Device Drivers [*] Network device support <*> CAN Device Drivers CAN SPI interfaces <*> Microchip MCP251x and MCP25625 SPI CAN controllers <*> Microchip MCP251xFD SPI CAN controllers   Save your configuration and compile your kernel/modules.   Step 3: Initialize and Test Interfaces   Once the board boots with the new device tree and kernel, you should see two new network interfaces listed under ip link show ( can0 and can1 ).   Now, you can setup the CAN interfaces: $ sudo ip link set can0 up type can bitrate 1000000 $ sudo ip link set can1 up type can bitrate 1000000 $ sudo ifconfig can0 txqueuelen 65536 $ sudo ifconfig can1 txqueuelen 65536   Connect the HAT in loopback:     From Interface can0: candump can0   From interface can1: cansend can1 000#11.22.33.44         Hope this can be helpful.   Best regards, Salas.        
記事全体を表示
The purpose of this document is to provide extended guidance for the selection of compatible LPDDR4/4X memory devices that are supported by the i.MX 93 series of processors. In all cases, it is strongly recommended to follow the DRAM layout guidelines outlined in the NXP Hardware Developer's Guides for the specific SoCs. The i.MX 93 series of processors supports different packages, and each have their own maximum supported LPDDR4/4x data rates. Please refer to the respective datasheets. Memory devices with binary densities (e.g., 1 GB, 2 GB, 4 GB) are preferred because they simplify memory management by aligning with system addressing schemes and reducing software complexity. NOTE: Some of the LPDDR4/4X devices may not support operation at low speeds and in addition, DQ ODT may not be active, which can impact signal integrity at these speeds. If low-speed operation is planned in the use case, please consult with the memory vendor about the configuration aspects and possible customization of the memory device so correct functionality is ensured. LPDDR4/4X - Maximum Supported Densities SoC Max Data bus width Maximum density Assumed memory organization Notes i.MX 93 (i.MX 93xx) 16-bit 16 Gb / (2 GB) single rank, single channel device with 17-row addresses (R0 - R16) 1, 2, 3   LPDDR4/4X - List of Validated Memories The validation process is an ongoing effort - regular updates of the table are expected. SoC Density Memory Vendor Validated Memory Part# Notes i.MX 93 16 Gb/ (2 GB) Micron LPDDR4/4x: MT53E1G16D1FW-046 AAT:A  (Z32N) MT53E1G16D1ZW-046 AAT:C (Z42N) 7   4, 8 8 Gb/ (1 GB) Micron LPDDR4/4x: MT53D512M16D1DS-046 AAT (Z11M) 4, 10 16 Gb/ (2 GB) Micron LPDDR4/4x: MT53E1G32D2FW-046 AUT:B (Z42M) 4, 5, 10 8 Gb/ (1 GB) Nanya LPDDR4: NT6AN512M16AV-J1I LPDDR4x: NT6AP512M16BV-J1I 4, 8 4 Gb/ (512 MB) Nanya LPDDR4x: NT6AP256M16AV  4, 8 16 Gb/ (2 GB) Kingston LPDDR4: D1611PM3BDGUI-U 4, 8 16 Gb/ (2 GB) Kingston LPDDR4: C1612PC2WDGTKR-U  7, 9 4 Gb/ (512 MB) ISSI LPDDR4: IS43LQ16256B-062BLI 4, 8 2 Gb / (256 MB) ISSI LPDDR4: IS43LQ16128A-062BSLI 4, 6, 8   8 Gb/ (1 GB) CXMT LPDDR4/4x: CXDB4CBAM-EA-M 4, 9 16 Gb/ (2 GB) JSC LPDDR4x: JSL4BAG167ZAMF  4, 8 8 Gb/ (1 GB) JSC LPDDR4x: JSL4B8G168ZAMF-05x  4, 8 4 Gb/ (512 MB) JSC LPDDR4x: JSL4A4G168ZAMF-05 4, 8 2 Gb / (256 MB) Winbond  LPDDR4x: W66BQ6NBHAGJ 4, 6, 8 8 Gb / (1 GB) IM (Intelligent Memory) LPDDR4x: IM8G16L4JCB-046I 4, 11 16 Gb / (2 GB) IM (Intelligent Memory) LPDDR4/4x: IMAG16L4KBBG 4, 8 4 Gb / (512 MB) Samsung LPDDR4: K4F4E164HD-THCL 4, 8 8Gb / (1 GB) AM (Alliance Memory) LPDDR4X: AS4C512M16MD4V-053BIN 4, 8 4 Gb / (512 MB) ISSI LPDDR4/4X: IS43LQ16256B-053BLI 4, 8 8 Gb / (1 GB) ISSI LPDDR4/4X: IS46LQ16512B-046BLA2 4, 8 32Gb / (4GB) 16 Gb / (2Gb) usable by i.MX 93 ISSI LPDDR4/4X: IS46LQ32K01B-046BLI 4, 8   Note 1: The numbers are based purely on the IP documentation for the DDR Controller and the DDR PHY, on the settings of the implementation parameters chosen for their integration into the SoC, SoC reference manual and on the JEDEC standards JESD209-4B/JESD209-4-1 (LPDDR4/4X). Therefore, they are not backed by validation, unless said otherwise and there is no guarantee that an SoC with the specific density and/or desired internal organization is offered by the memory vendors. Should the customers choose to use the maximum density and assume it in the intended use case, they do it at their own risk. Note 2: Byte-mode LPDDR4/4X devices (x16 channel internally split between two dies, x8 each) of any density are not supported therefore, the numbers are applicable only to devices with x16 internal organization (referred to as "standard" in the JEDEC specification). Note 3: The SoC also supports dual rank single channel devices therefore, 16Gb/2GB density can be also achieved by using a dual rank single channel device with 16-row addresses (R0 - R15). Note 4: The memory part number did not undergo full JEDEC verification however, it passed all functional testing items. Note 5: This is a dual channel x32 device. Since i.MX93 only supports 16-bit LPDDR4/X data bus, it can only interface with one of the channels and therefore, utilize only half of the device's density. As indicated in the table - the device has 32Gb/4GB density however, only 16Gb/2GB can be used. There is no functional problem with using only one channel of a dual channel device as the channels are independent in LPDDR4/4X.  Note 6: This is a new JEDEC 100 ball package, half the size of the standard 200 ball package. This 100 ball package has the same performance and functionality as the 200 ball package, and has the added advantage of being smaller and cheaper than the standard package. Note 7: This device has been EoLed by the manufacturer and has been updated by a new memory part number  Note 8: Part is active. Reviewed Q3 2026 Note 9: Part is obsolete. Note 10: This device will be EoLed in Q2 24 by the manufacturer and will not be updated by a new memory part number Note 11: DQ eye marginalities were identified during TSA analysis. vTSA and stability testing did not identify any issues.
記事全体を表示