S32DS 牌照消失 S32DS 许可证丢失，需要激活，但旧激活码无效。如何解决这个问题？ Re: S32DS licence disappear 请参考此页面和我的个人资料许可证状态。 Re: S32DS licence disappear DS 3.5 ，我的执照状态。 Re: S32DS licence disappear 你好 能否请您提供试图安装的 S32DS 版本？ 顺祝商祺！ Peter Re: S32DS licence disappear Ds 3.5 Re: S32DS licence disappear 你好、 我检查了您的账户，您的许可证是有效的。您尝试过离线激活吗？ https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Activate-S32-Design-Studio/ta-p/1128340 Re: S32DS licence disappear 是的，我试过. 结果和其他信息，请参考我的其他回复。 我找不到我的驾照 . @jiri_kral Re: S32DS licence disappear 我使用了其他激活有效代码，也显示了该错误。请参考我的其他回复。 @jiri_kral @petervlna Re: S32DS licence disappear 我的个人资料中没有许可证激活码，请查看。 Re: S32DS licence disappear 你好 这个问题是否仍然有效，或者你是否设法让它运行了？ 顺祝商祺！ Peter

iMX8QM 上の Jailhouse（lf-6.6.52_2.2.0 搭載） こんにちは、NXPチームの皆様、 i.MX Linux リリースノート RN00210、Rev. LF6.6.52_2.2.0 — 2025 年 1 月 6 日 には 、jailhouse がすべての i.MX 8M、8ULP、 i.MX 93、 i.MX 95 をサポートしていることが記載されています。iMX8Quad Max はリストに含まれていません。 meta-freescale( https://github.com/Freescale/meta-freescale/tree/scarthgap ) は jailhouse を構築するためのレシピを提供しています。MACHINE_FEATURES が jailhouse と互換性のあるマシンには imx8qm が搭載されていません。搭載されているのは imx95、imx93、imx8mm、imx8mn、imx8mp、imx8ulp のみです。これは上記のi.MX Linux リリースノート RN00210 と一致しています。 しかしながら、jailhouseのソースコード( https://github.com/nxp-imx/imx-jailhouse/tree/lf-6.6.52_2.2.0/configs/arm64 ) にはimx8qm SoC用のコードが含まれています 。jailhouseはimx8qm SoC上で動作可能のようです。一部のドキュメントやコミュニティチケットによると、jailhouseはカーネル5.4と4.9で動作していたようです。 私の質問は、jailhouse が LF6.6.52 でもまだ動作するのか、それとも検証されていないだけなのかということです。 ありがとう。 Re: Jailhouse on iMX8QM with lf-6.6.52_2.2.0 こんにちは@Benjamin_Huさん、 NXP サポートにお問い合わせいただきありがとうございます。 UG10170によれば、現在の BSP では、そのプロセッサに対して jailhouse 機能は正式にサポートされていません。 公式にサポートされているプロセッサは次のとおりです。 i.MX 8Mシリーズ i.MX 8M ミニ LPDDR4 EVKB i.MX 8M ナノ LPDDR4 EVK i.MX 8M Plus LPDDR4 EVK i.MX 9シリーズ i.MX 93 EVK i.MX 943 EVK i.MX 95 15x15 LPDDR4x EVK i.MX 95 19x19 LPDDR5 EVK よろしくお願いいたします。 チャビラ

グリーンVIP 1.3.0GVP_RTU_1_C1_VM2 の生成に失敗しました こんにちは、専門家さん。 GVP_RTU_1_C1_VM2 の元のプロジェクトを開くと、以下のようなエラーが表示されています しかし、.mexからファイルを見ると、それが /RTOS_R52/Os/OsCounter_0 です。しかし、GUI インターフェースでは何も参照できません。ご協力いただけませんか?ありがとう！ BR、 キャサリン グリーン_VIP Re: GreenVIP 1.3.0 GVP_RTU_1_C1_VM2 generation failed こんにちは@Catherine 、 問題を追跡するために Jira チケットを作成しました。GreenVIP チームができるだけ早く返信します。 Re: GreenVIP 1.3.0 GVP_RTU_1_C1_VM2 generation failed こんにちは@Catherine 、 この問題をリクエストしたお客様はいますか? よろしくお願いします、 ラドゥ

Failed to transfer int data to float data Hello: ‘nvm_calib->par_p1’ data is int16 (7002), ‘nvmdata_buff’ is a float. After assignment, it becomes 14229, which should be 7002.0. MCUXpress IDE V24.12; RW612 sdK25.09; frdmrw612 wifi_httpsrc。 May I ask how to set it up! Re: Failed to transfer int data to float data Hi, Could you please tell me how to reproduce this using the example? Is the issue related to the example itself, or is it coming from a custom implementation?   Regards, Daniel.

Problem in setting up PRE -> PRG -> IPU -> HDMI pipeline on i.MX6 We've got Voipac iMX6 Rex UltraPlus dev kit. It comes with linux 4.1. I wanted to get mordern linux so I got linux-imx branch lf-6.6.y and imx_v7_defconfig. I tried porting the device tree and  // SPDX-License-Identifier: GPL-2.0-only /* * Copyright 2014 FEDEVEL, Inc. * * Author: Robert Nelson */ /dts-v1/; #include "imx6q.dtsi" #include "imx6qp.dtsi" #include "imx6qdl-rex.dtsi" / { model = "Rex Pro i.MX6 Quad Board"; compatible = "rex,imx6q-rex-pro", "fsl,imx6q"; memory: memory@10000000 { device_type = "memory"; reg = <0x10000000 0x80000000>; }; }; &ecspi3 { flash: flash@0 { compatible = "sst,sst25vf032b", "jedec,spi-nor"; spi-max-frequency = <20000000>; reg = <0>; }; }; &i2c2 { clock-frequency = <100000>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_i2c2>; status = "okay"; hdmi_ddc: edid@50 { compatible = "fsl,imx6-hdmi-i2c"; reg = <0x50>; }; }; &sata { status = "okay"; }; &mxcfb1 { prefetch; status = "okay"; }; &mxcfb2 { prefetch; status = "okay"; }; &mxcfb3 { prefetch; status = "disabled"; }; &mxcfb4 { prefetch; status = "disabled"; }; &pre1 { status = "okay"; }; &pre2 { status = "okay"; }; &pre3 { status = "okay"; }; &pre4 { status = "okay"; }; &prg1 { memory-region = <&memory>; status = "okay"; }; &prg2 { memory-region = <&memory>; status = "okay"; }; &hdmi_core { ipu_id = <0>; disp_id = <0>; status = "okay"; }; &hdmi_video { fsl,phy_reg_vlev = <0x0294>; fsl,phy_reg_cksymtx = <0x800d>; status = "okay"; }; There seems to be a problem in PRE -> PRG -> IPU -> HDMI pipeline.  Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 6.6.52-g5a0a5e71d2bd-dirty (anurag@anurag-SK5800) (arm-linux-gnueabi-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #29 SMP PREEMPT Tue Jan 13 15:33:15 IST 2026 [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Rex Pro i.MX6 Quad Board [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Reserved memory: created CMA memory pool at 0xea000000, size 320 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] OF: reserved mem: 0xea000000..0xfdffffff (327680 KiB) map reusable linux,cma [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000010000000-0x000000007fffffff] [ 0.000000] HighMem [mem 0x0000000080000000-0x00000000ffffefff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000010000000-0x00000000ffffefff] [ 0.000000] Initmem setup node 0 [mem 0x0000000010000000-0x00000000ffffefff] [ 0.000000] percpu: Embedded 12 pages/cpu s18900 r8192 d22060 u49152 [ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/nfs nfsroot=192.168.1.41:/srv/nfsroot,v3 rw ip=dhcp [ 0.000000] Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes, linear) [ 0.000000] Inode-cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 979007 [ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off [ 0.000000] Memory: 3544512K/3932156K available (14336K kernel code, 1522K rwdata, 4944K rodata, 1024K init, 425K bss, 59964K reserved, 327680K cma-reserved, 1769468K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: DT/platform modifies aux control register: 0x32070000 -> 0x32470000 [ 0.000000] L2C-310 erratum 769419 enabled [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9 [ 0.000000] L2C-310 ID prefetch enabled, offset 16 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 cache controller enabled, 16 ways, 1024 kB [ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76470001 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] Switching to timer-based delay loop, resolution 333ns [ 0.000001] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns [ 0.000026] clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns [ 0.001453] Console: colour dummy device 80x30 [ 0.001498] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000) [ 0.001518] CPU: Testing write buffer coherency: ok [ 0.001562] CPU0: Spectre v2: using BPIALL workaround [ 0.001573] pid_max: default: 32768 minimum: 301 [ 0.001769] Mount-cache hash table entries: 4096 (order: 2, 16384 bytes, linear) [ 0.001804] Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes, linear) [ 0.002831] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.004268] RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1. [ 0.004454] Setting up static identity map for 0x10100000 - 0x10100060 [ 0.004688] rcu: Hierarchical SRCU implementation. [ 0.004694] rcu: Max phase no-delay instances is 1000. [ 0.006556] smp: Bringing up secondary CPUs ... [ 0.007512] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.007532] CPU1: Spectre v2: using BPIALL workaround [ 0.008616] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.008634] CPU2: Spectre v2: using BPIALL workaround [ 0.009701] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.009720] CPU3: Spectre v2: using BPIALL workaround [ 0.009851] smp: Brought up 1 node, 4 CPUs [ 0.009868] SMP: Total of 4 processors activated (24.00 BogoMIPS). [ 0.009878] CPU: All CPU(s) started in SVC mode. [ 0.011183] devtmpfs: initialized [ 0.020354] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.020648] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.020675] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.038260] pinctrl core: initialized pinctrl subsystem [ 0.039950] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.047487] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.048756] thermal_sys: Registered thermal governor 'step_wise' [ 0.048832] cpuidle: using governor menu [ 0.049055] CPU identified as i.MX6QP, silicon rev 1.0 [ 0.057573] platform soc: Fixed dependency cycle(s) with /soc/bus@2000000/gpc@20dc000 [ 0.058532] platform 120000.hdmi: Fixed dependency cycle(s) with /soc/ipu@2800000 [ 0.058565] platform 120000.hdmi: Fixed dependency cycle(s) with /soc/ipu@2400000 [ 0.065172] mxs_phy 20c9000.usbphy: supply phy-3p0 not found, using dummy regulator [ 0.065766] mxs_phy 20ca000.usbphy: supply phy-3p0 not found, using dummy regulator [ 0.067266] platform 20dc000.gpc: Fixed dependency cycle(s) with /soc/bus@2000000/clock-controller@20c4000 [ 0.069057] platform 20e0000.iomuxc-gpr:ipu1_csi0_mux: Fixed dependency cycle(s) with /soc/ipu@2400000 [ 0.069276] platform 20e0000.iomuxc-gpr:ipu2_csi1_mux: Fixed dependency cycle(s) with /soc/ipu@2800000 [ 0.069515] platform 20e0000.pinctrl: Fixed dependency cycle(s) with /soc/bus@2000000/pinctrl@20e0000/imx6qdl-rex/hoggrp [ 0.075192] platform 20e0000.iomuxc-gpr:ipu1_csi0_mux: Fixed dependency cycle(s) with /soc/ipu@2400000 [ 0.075299] platform 120000.hdmi: Fixed dependency cycle(s) with /soc/ipu@2400000 [ 0.075404] platform 2400000.ipu: Fixed dependency cycle(s) with /soc/hdmi@120000 [ 0.075496] platform 2400000.ipu: Fixed dependency cycle(s) with /soc/bus@2000000/iomuxc-gpr@20e0000/ipu1_csi0_mux [ 0.076923] platform 20e0000.iomuxc-gpr:ipu2_csi1_mux: Fixed dependency cycle(s) with /soc/ipu@2800000 [ 0.077039] platform 120000.hdmi: Fixed dependency cycle(s) with /soc/ipu@2800000 [ 0.077125] platform 2800000.ipu: Fixed dependency cycle(s) with /soc/hdmi@120000 [ 0.077210] platform 2800000.ipu: Fixed dependency cycle(s) with /soc/bus@2000000/iomuxc-gpr@20e0000/ipu2_csi1_mux [ 0.080562] No ATAGs? [ 0.080724] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.080738] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.081653] imx6q-pinctrl 20e0000.pinctrl: initialized IMX pinctrl driver [ 0.085204] imx mu driver is registered. [ 0.085646] imx rpmsg driver is registered. [ 0.087876] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible. [ 0.089669] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.091854] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.093802] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.095768] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.097730] gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.099770] gpio gpiochip5: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.101758] gpio gpiochip6: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.107751] SCSI subsystem initialized [ 0.108266] usbcore: registered new interface driver usbfs [ 0.108311] usbcore: registered new interface driver hub [ 0.108358] usbcore: registered new device driver usb [ 0.108509] usb_phy_generic usbphynop1: dummy supplies not allowed for exclusive requests [ 0.108714] usb_phy_generic usbphynop2: dummy supplies not allowed for exclusive requests [ 0.110687] i2c i2c-0: IMX I2C adapter registered [ 0.112084] pca953x 1-0027: using no AI [ 0.139188] pca953x 1-0027: interrupt support not compiled in [ 0.159914] i2c i2c-1: IMX I2C adapter registered [ 0.160673] i2c i2c-2: IMX I2C adapter registered [ 0.161268] mc: Linux media interface: v0.10 [ 0.161343] videodev: Linux video capture interface: v2.00 [ 0.161431] pps_core: LinuxPPS API ver. 1 registered [ 0.161438] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.161463] PTP clock support registered [ 0.162678] imx-ipuv3 2400000.ipu: [ 0.162705] imx-ipuv3 2400000.ipu: revision is IPUv3H [ 0.163023] imx-ipuv3 2400000.ipu: IPU CM Regs = (ptrval) [ 0.163039] imx-ipuv3 2400000.ipu: IPU IC Regs = (ptrval) [ 0.163050] imx-ipuv3 2400000.ipu: IPU IDMAC Regs = (ptrval) [ 0.163057] imx-ipuv3 2400000.ipu: IPU DP Regs = (ptrval) [ 0.163065] imx-ipuv3 2400000.ipu: IPU DC Regs = (ptrval) [ 0.163072] imx-ipuv3 2400000.ipu: IPU DMFC Regs = (ptrval) [ 0.163080] imx-ipuv3 2400000.ipu: IPU DI0 Regs = (ptrval) [ 0.163087] imx-ipuv3 2400000.ipu: IPU DI1 Regs = (ptrval) [ 0.163095] imx-ipuv3 2400000.ipu: IPU SMFC Regs = (ptrval) [ 0.163102] imx-ipuv3 2400000.ipu: IPU CSI0 Regs = (ptrval) [ 0.163109] imx-ipuv3 2400000.ipu: IPU CSI1 Regs = (ptrval) [ 0.163117] imx-ipuv3 2400000.ipu: IPU CPMem = (ptrval) [ 0.163125] imx-ipuv3 2400000.ipu: IPU TPMem = (ptrval) [ 0.163133] imx-ipuv3 2400000.ipu: IPU DC Template Mem = (ptrval) [ 0.163141] imx-ipuv3 2400000.ipu: IPU VDI Regs = (ptrval) [ 0.163349] imx-ipuv3 2800000.ipu: [ 0.163374] imx-ipuv3 2800000.ipu: revision is IPUv3H [ 0.163681] imx-ipuv3 2800000.ipu: IPU CM Regs = (ptrval) [ 0.163694] imx-ipuv3 2800000.ipu: IPU IC Regs = (ptrval) [ 0.163701] imx-ipuv3 2800000.ipu: IPU IDMAC Regs = (ptrval) [ 0.163709] imx-ipuv3 2800000.ipu: IPU DP Regs = (ptrval) [ 0.163716] imx-ipuv3 2800000.ipu: IPU DC Regs = (ptrval) [ 0.163723] imx-ipuv3 2800000.ipu: IPU DMFC Regs = (ptrval) [ 0.163729] imx-ipuv3 2800000.ipu: IPU DI0 Regs = (ptrval) [ 0.163736] imx-ipuv3 2800000.ipu: IPU DI1 Regs = (ptrval) [ 0.163743] imx-ipuv3 2800000.ipu: IPU SMFC Regs = (ptrval) [ 0.163750] imx-ipuv3 2800000.ipu: IPU CSI0 Regs = (ptrval) [ 0.163757] imx-ipuv3 2800000.ipu: IPU CSI1 Regs = (ptrval) [ 0.163763] imx-ipuv3 2800000.ipu: IPU CPMem = (ptrval) [ 0.163770] imx-ipuv3 2800000.ipu: IPU TPMem = (ptrval) [ 0.163778] imx-ipuv3 2800000.ipu: IPU DC Template Mem = (ptrval) [ 0.163785] imx-ipuv3 2800000.ipu: IPU VDI Regs = (ptrval) [ 0.164339] mxc_vdoa 21e4000.vdoa: iram_base:0xf0940000,iram_paddr:0x905000,size:0x12000 [ 0.164358] mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed [ 0.164777] imx-prg 21cc000.prg: driver probed [ 0.164928] imx-prg 21cd000.prg: driver probed [ 0.165408] imx-pre 21c8000.pre: driver probed [ 0.165719] imx-pre 21c9000.pre: driver probed [ 0.166014] imx-pre 21ca000.pre: driver probed [ 0.166306] imx-pre 21cb000.pre: driver probed [ 0.166615] MIPI CSI2 driver module loaded [ 0.166665] Advanced Linux Sound Architecture Driver Initialized. [ 0.168110] Bluetooth: Core ver 2.22 [ 0.168159] NET: Registered PF_BLUETOOTH protocol family [ 0.168167] Bluetooth: HCI device and connection manager initialized [ 0.168181] Bluetooth: HCI socket layer initialized [ 0.168191] Bluetooth: L2CAP socket layer initialized [ 0.168212] Bluetooth: SCO socket layer initialized [ 0.168645] vgaarb: loaded [ 0.169232] clocksource: Switched to clocksource mxc_timer1 [ 0.169539] VFS: Disk quotas dquot_6.6.0 [ 0.169596] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.181120] NET: Registered PF_INET protocol family [ 0.181747] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.184933] tcp_listen_portaddr_hash hash table entries: 1024 (order: 1, 8192 bytes, linear) [ 0.184988] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.185067] TCP established hash table entries: 16384 (order: 4, 65536 bytes, linear) [ 0.185229] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear) [ 0.185739] TCP: Hash tables configured (established 16384 bind 16384) [ 0.185938] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.186015] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.186259] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.186896] RPC: Registered named UNIX socket transport module. [ 0.186907] RPC: Registered udp transport module. [ 0.186913] RPC: Registered tcp transport module. [ 0.186917] RPC: Registered tcp-with-tls transport module. [ 0.186924] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.188518] PCI: CLS 0 bytes, default 64 [ 0.189143] armv7-pmu pmu: hw perfevents: no interrupt-affinity property, guessing. [ 0.189492] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available [ 0.192313] Bus freq driver module loaded [ 0.193564] Initialise system trusted keyrings [ 0.193855] workingset: timestamp_bits=14 max_order=20 bucket_order=6 [ 0.194593] NFS: Registering the id_resolver key type [ 0.194649] Key type id_resolver registered [ 0.194657] Key type id_legacy registered [ 0.194693] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.194703] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 0.194744] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.195069] fuse: init (API version 7.39) [ 0.335183] Key type asymmetric registered [ 0.335195] Asymmetric key parser 'x509' registered [ 0.335305] bounce: pool size: 64 pages [ 0.335338] io scheduler mq-deadline registered [ 0.335348] io scheduler kyber registered [ 0.335381] io scheduler bfq registered [ 0.341513] mxc_hdmi 20e0000.hdmi_video: hdcp disable [ 0.341791] mxc_hdmi 20e0000.hdmi_video: supply HDMI not found, using dummy regulator [ 0.342866] mxc_sdc_fb fb@0: mxcfb_probe enter [ 0.343005] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init [ 0.343023] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init - default mode 1920x1080M@60 bpp=24 [ 0.343076] mxc_hdmi 20e0000.hdmi_video: Enabled HDMI clocks [ 0.343088] mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1 [ 0.343120] fbcvt: 1920x1080@60: CVT Name - 2.073M9 [ 0.343228] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init exit [ 0.343241] mxc_sdc_fb fb@0: di_pixfmt:0x33424752, bpp:0x18, di:0, ipu:0 [ 0.343255] mxc_sdc_fb fb@0: registered mxc display driver hdmi [ 0.343266] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_deinit [ 0.343371] mxc_sdc_fb fb@1: mxcfb_probe enter [ 0.343388] mxc_sdc_fb fb@1: get of property mode_str fail [ 0.343405] mxc_sdc_fb fb@1: NO mxc display driver found! [ 0.347745] imx-sdma 20ec000.dma-controller: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2 [ 0.347765] imx-sdma 20ec000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx6q.bin [ 0.349746] mxs-dma 110000.dma-controller: initialized [ 0.356074] 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 283, base_baud = 5000000) is a IMX [ 0.356137] printk: console [ttymxc0] enabled [ 1.770772] 21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 284, base_baud = 5000000) is a IMX [ 1.780999] imx sema4 driver is registered. [ 1.800787] brd: module loaded [ 1.812434] loop: module loaded [ 1.815837] at24 1-0057: supply vcc not found, using dummy regulator [ 1.823438] at24 1-0057: 256 byte 24c02 EEPROM, writable, 1 bytes/write [ 1.832399] ahci-imx 2200000.sata: fsl,transmit-level-mV not specified, using 00000024 [ 1.840381] ahci-imx 2200000.sata: fsl,transmit-boost-mdB not specified, using 00000480 [ 1.848398] ahci-imx 2200000.sata: fsl,transmit-atten-16ths not specified, using 00002000 [ 1.856610] ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000 [ 1.864374] ahci-imx 2200000.sata: supply ahci not found, using dummy regulator [ 1.871891] ahci-imx 2200000.sata: supply phy not found, using dummy regulator [ 1.879193] ahci-imx 2200000.sata: supply target not found, using dummy regulator [ 1.889925] ahci-imx 2200000.sata: SSS flag set, parallel bus scan disabled [ 1.896922] ahci-imx 2200000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode [ 1.905794] ahci-imx 2200000.sata: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst [ 1.916410] scsi host0: ahci-imx [ 1.919969] ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 285 [ 1.933418] spi-nor spi2.0: found sst26vf064b, expected sst25vf032b [ 1.939920] imx-sdma 20ec000.dma-controller: sdma or sdma firmware not ready! [ 1.948437] spi-nor spi2.0: sst26vf064b (8192 Kbytes) [ 1.958027] tun: Universal TUN/TAP device driver, 1.6 [ 1.963393] CAN device driver interface [ 1.969204] e1000e: Intel(R) PRO/1000 Network Driver [ 1.974220] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.980653] usbcore: registered new device driver r8152-cfgselector [ 1.986967] usbcore: registered new interface driver r8152 [ 1.992522] usbcore: registered new interface driver lan78xx [ 1.998221] usbcore: registered new interface driver asix [ 2.003694] usbcore: registered new interface driver ax88179_178a [ 2.009866] usbcore: registered new interface driver cdc_ether [ 2.015738] usbcore: registered new interface driver smsc95xx [ 2.021547] usbcore: registered new interface driver net1080 [ 2.027245] usbcore: registered new interface driver cdc_subset [ 2.033233] usbcore: registered new interface driver zaurus [ 2.038845] usbcore: registered new interface driver MOSCHIP usb-ethernet driver [ 2.046328] usbcore: registered new interface driver cdc_ncm [ 2.052057] usbcore: registered new interface driver r8153_ecm [ 2.058033] usbcore: registered new interface driver usb-storage [ 2.066104] imx_usb 2184000.usb: No over current polarity defined [ 2.076502] ci_hdrc ci_hdrc.0: EHCI Host Controller [ 2.081461] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 [ 2.109250] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 [ 2.114949] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 2.123265] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.130531] usb usb1: Product: EHCI Host Controller [ 2.135423] usb usb1: Manufacturer: Linux 6.6.52-g5a0a5e71d2bd-dirty ehci_hcd [ 2.142611] usb usb1: SerialNumber: ci_hdrc.0 [ 2.147750] hub 1-0:1.0: USB hub found [ 2.151577] hub 1-0:1.0: 1 port detected [ 2.156563] imx_usb 2184200.usb: No over current polarity defined [ 2.166823] ci_hdrc ci_hdrc.1: EHCI Host Controller [ 2.171762] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2 [ 2.199254] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00 [ 2.204926] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 2.213235] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.220489] usb usb2: Product: EHCI Host Controller [ 2.225376] usb usb2: Manufacturer: Linux 6.6.52-g5a0a5e71d2bd-dirty ehci_hcd [ 2.232535] usb usb2: SerialNumber: ci_hdrc.1 [ 2.237597] hub 2-0:1.0: USB hub found [ 2.241419] hub 2-0:1.0: 1 port detected [ 2.251492] snvs_rtc 20cc000.snvs:snvs-rtc-lp: registered as rtc0 [ 2.257628] snvs_rtc 20cc000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T00:00:00 UTC (0) [ 2.260795] ata1: SATA link down (SStatus 0 SControl 300) [ 2.266835] i2c_dev: i2c /dev entries driver [ 2.272086] ahci-imx 2200000.sata: no device found, disabling link. [ 2.282606] ahci-imx 2200000.sata: pass ahci_imx..hotplug=1 to enable hotplug [ 2.285770] Bluetooth: HCI UART driver ver 2.3 [ 2.294294] Bluetooth: HCI UART protocol H4 registered [ 2.299592] Bluetooth: HCI UART protocol BCSP registered [ 2.305007] Bluetooth: HCI UART protocol LL registered [ 2.310222] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 2.316527] Bluetooth: HCI UART protocol Marvell registered [ 2.322204] usbcore: registered new interface driver btusb [ 2.328901] sdhci: Secure Digital Host Controller Interface driver [ 2.335125] sdhci: Copyright(c) Pierre Ossman [ 2.339502] sdhci-pltfm: SDHCI platform and OF driver helper [ 2.347737] sdhci-esdhc-imx 2194000.mmc: Got CD GPIO [ 2.352866] sdhci-esdhc-imx 2194000.mmc: Got WP GPIO [ 2.353746] sdhci-esdhc-imx 2198000.mmc: Got CD GPIO [ 2.362916] sdhci-esdhc-imx 2198000.mmc: Got WP GPIO [ 2.363755] usbcore: registered new interface driver usbhid [ 2.373525] usbhid: USB HID core driver [ 2.384277] Galcore version 6.4.11.p2.745085 [ 2.408839] mmc1: SDHCI controller on 2194000.mmc [2194000.mmc] using ADMA [ 2.408918] mmc2: SDHCI controller on 2198000.mmc [2198000.mmc] using ADMA [ 2.449354] usb 1-1: new high-speed USB device number 2 using ci_hdrc [ 2.669949] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3 [ 2.678168] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.700727] hub 1-1:1.0: USB hub found [ 2.704708] hub 1-1:1.0: 4 ports detected [ 2.997764] [drm] Initialized vivante 1.0.0 20170808 for 130000.gpu on minor 0 [ 3.007063] mxc_vpu 2040000.vpu_fsl: VPU initialized [ 3.015259] sgtl5000 0-000a: sgtl5000 revision 0x11 [ 3.024398] sgtl5000 0-000a: Using internal LDO instead of VDDD: check ER1 erratum [ 3.064731] fsl-ssi-dai 2028000.ssi: No cache defaults, reading back from HW [ 3.096416] imx-sgtl5000 sound: ASoC: driver name too long 'imx6-rex-sgtl5000' -> 'imx6-rex-sgtl50' [ 3.114109] NET: Registered PF_LLC protocol family [ 3.119542] NET: Registered PF_INET6 protocol family [ 3.125881] Segment Routing with IPv6 [ 3.129662] In-situ OAM (IOAM) with IPv6 [ 3.133683] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 3.140396] NET: Registered PF_PACKET protocol family [ 3.145467] can: controller area network core [ 3.149926] NET: Registered PF_CAN protocol family [ 3.154731] can: raw protocol [ 3.157712] can: broadcast manager protocol [ 3.161929] can: netlink gateway - max_hops=1 [ 3.166510] Bluetooth: RFCOMM TTY layer initialized [ 3.171442] Bluetooth: RFCOMM socket layer initialized [ 3.176611] Bluetooth: RFCOMM ver 1.11 [ 3.180408] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 3.185730] Bluetooth: BNEP filters: protocol multicast [ 3.190985] Bluetooth: BNEP socket layer initialized [ 3.195958] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 3.201910] Bluetooth: HIDP socket layer initialized [ 3.207156] lib80211: common routines for IEEE802.11 drivers [ 3.212940] Key type dns_resolver registered [ 3.219552] Registering SWP/SWPB emulation handler [ 3.241846] Loading compiled-in X.509 certificates [ 3.274136] imx-ipuv3 2400000.ipu: [ 3.278617] imx-ipuv3 2400000.ipu: revision is IPUv3H [ 3.283868] imx-ipuv3 2400000.ipu: IPU CM Regs = (ptrval) [ 3.289293] imx-ipuv3 2400000.ipu: IPU IC Regs = (ptrval) [ 3.294696] imx-ipuv3 2400000.ipu: IPU IDMAC Regs = (ptrval) [ 3.300379] imx-ipuv3 2400000.ipu: IPU DP Regs = (ptrval) [ 3.305782] imx-ipuv3 2400000.ipu: IPU DC Regs = (ptrval) [ 3.311223] imx-ipuv3 2400000.ipu: IPU DMFC Regs = (ptrval) [ 3.316802] imx-ipuv3 2400000.ipu: IPU DI0 Regs = (ptrval) [ 3.322306] imx-ipuv3 2400000.ipu: IPU DI1 Regs = (ptrval) [ 3.327798] imx-ipuv3 2400000.ipu: IPU SMFC Regs = (ptrval) [ 3.333409] imx-ipuv3 2400000.ipu: IPU CSI0 Regs = (ptrval) [ 3.338986] imx-ipuv3 2400000.ipu: IPU CSI1 Regs = (ptrval) [ 3.344577] imx-ipuv3 2400000.ipu: IPU CPMem = (ptrval) [ 3.349817] imx-ipuv3 2400000.ipu: IPU TPMem = (ptrval) [ 3.355047] imx-ipuv3 2400000.ipu: IPU DC Template Mem = (ptrval) [ 3.361182] imx-ipuv3 2400000.ipu: IPU VDI Regs = (ptrval) [ 3.389549] imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) [ 3.397071] imx-ipuv3 2400000.ipu: ipu_clk = 264000000 [ 3.407087] imx-ipuv3 2800000.ipu: [ 3.411838] imx-ipuv3 2800000.ipu: revision is IPUv3H [ 3.417553] imx-ipuv3 2800000.ipu: IPU CM Regs = (ptrval) [ 3.423104] imx-ipuv3 2800000.ipu: IPU IC Regs = (ptrval) [ 3.428510] imx-ipuv3 2800000.ipu: IPU IDMAC Regs = (ptrval) [ 3.434220] imx-ipuv3 2800000.ipu: IPU DP Regs = (ptrval) [ 3.439658] imx-ipuv3 2800000.ipu: IPU DC Regs = (ptrval) [ 3.445062] imx-ipuv3 2800000.ipu: IPU DMFC Regs = (ptrval) [ 3.450647] imx-ipuv3 2800000.ipu: IPU DI0 Regs = (ptrval) [ 3.456135] imx-ipuv3 2800000.ipu: IPU DI1 Regs = (ptrval) [ 3.461656] imx-ipuv3 2800000.ipu: IPU SMFC Regs = (ptrval) [ 3.467233] imx-ipuv3 2800000.ipu: IPU CSI0 Regs = (ptrval) [ 3.472823] imx-ipuv3 2800000.ipu: IPU CSI1 Regs = (ptrval) [ 3.478399] imx-ipuv3 2800000.ipu: IPU CPMem = (ptrval) [ 3.483656] imx-ipuv3 2800000.ipu: IPU TPMem = (ptrval) [ 3.488888] imx-ipuv3 2800000.ipu: IPU DC Template Mem = (ptrval) [ 3.494998] imx-ipuv3 2800000.ipu: IPU VDI Regs = (ptrval) [ 3.529443] imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) [ 3.537075] imx-ipuv3 2800000.ipu: ipu_clk = 264000000 [ 3.544444] mxc_sdc_fb fb@0: mxcfb_probe enter [ 3.548964] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init [ 3.554693] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init - default mode 1920x1080M@60 bpp=24 [ 3.563514] mxc_hdmi 20e0000.hdmi_video: Enabled HDMI clocks [ 3.569261] mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1 [ 3.577170] fbcvt: 1920x1080@60: CVT Name - 2.073M9 [ 3.582303] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_disp_init exit [ 3.588318] mxc_sdc_fb fb@0: di_pixfmt:0x33424752, bpp:0x18, di:0, ipu:0 [ 3.595071] mxc_sdc_fb fb@0: registered mxc display driver hdmi [ 3.601025] mxc_sdc_fb fb@0: Reconfiguring framebuffer [ 3.601038] imx-ipuv3 2400000.ipu: Channel already disabled 9 [ 3.601045] imx-ipuv3 2400000.ipu: Channel already uninitialized 9 [ 3.628416] mxc_sdc_fb fb@0: allocated fb @ paddr=0xF2200000, size=6220800. [ 3.630476] imx-ipuv3 2400000.ipu: init channel = 9 [ 3.630490] imx-ipuv3 2400000.ipu: ipu busfreq high requst. [ 3.630516] mxc_sdc_fb fb@0: pixclock = 148500000l Hz [ 3.630522] imx-ipuv3 2400000.ipu: panel size = 1920 x 1080 [ 3.630530] imx-ipuv3 2400000.ipu: pixel clk = 148500000 [ 3.630561] imx-ipuv3 2400000.ipu: try ipu internal clk [ 3.630571] imx-ipuv3 2400000.ipu: rounded pix clk:176000000 [ 3.630578] imx-ipuv3 2400000.ipu: try ipu ext di clk [ 3.630820] imx-ipuv3 2400000.ipu: di clk:148500000 [ 3.630836] imx-ipuv3 2400000.ipu: round pixel clk:148500000 [ 3.660044] imx-ipuv3 2400000.ipu: div:1 [ 3.660090] mxc_sdc_fb fb@0: Y wrap disabled [ 3.660139] imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) [ 3.660164] imx-prg 21cc000.prg: bind prg0 ch0 with pre0 [ 4.660593] imx-prg 21cc000.prg: wait for buffer ready timeout [ 4.661166] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init [ 4.661185] mxc_sdc_fb fb@0: Y wrap disabled [ 4.689222] imx-pre 21c8000.pre: timeout waiting for PRE to run out of problematic window for shadow update [ 4.689317] mxc_sdc_fb fb@0: Update complete [ 4.689352] mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_MODE_CHANGE [ 4.694476] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000 [ 4.830798] mxc_sdc_fb fb@0: blank = 0 [ 4.830809] mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_BLANK - UNBLANK [ 4.841445] mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_FB_REGISTERED [ 4.847895] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_fb_registered [ 4.853832] mxc_hdmi 20e0000.hdmi_video: Hotplug interrupt received [ 4.860356] mxc_sdc_fb fb@0: Reconfiguring framebuffer [ 4.860366] mxc_sdc_fb fb@0: Reconfiguring framebuffer on the fly [ 4.860373] mxc_sdc_fb fb@0: Y wrap disabled [ 4.879261] mxc_hdmi 20e0000.hdmi_video: phy_int_stat=0x3d, phy_int_pol=0x2 [ 4.879271] mxc_hdmi 20e0000.hdmi_video: EVENT=plugin [ 4.879277] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_cable_connected [ 4.879284] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_read_edid [ 4.915611] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_edid_rebuild_modelist [ 5.929391] mxc_sdc_fb fb@0: MXCFB_WAIT_FOR_VSYNC: timeout 0 [ 6.969344] mxc_sdc_fb fb@0: MXCFB_WAIT_FOR_VSYNC: timeout 0 [ 7.479334] mxc_sdc_fb fb@0: timeout when waiting for on the fly config irq [ 7.479353] fbcon_init: detected unhandled fb_set_par error, error code -110 [ 7.479618] mxc_sdc_fb fb@0: Y wrap disabled [ 7.609225] imx-pre 21c8000.pre: timeout waiting for PRE to run out of problematic window for shadow update [ 7.609440] mxc_sdc_fb fb@0: Update complete [ 7.641447] Console: switching to colour frame buffer device 240x67 [ 7.641466] mxc_sdc_fb fb@0: Y wrap disabled [ 8.149339] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 8.295398] mxc_hdmi 20e0000.hdmi_video: Added mode 0: [ 8.295406] mxc_hdmi 20e0000.hdmi_video: xres = 1920, yres = 1080, freq = 60, vmode = 0, flag = 17 [ 8.295418] mxc_hdmi 20e0000.hdmi_video: Added mode 2: [ 8.295423] mxc_hdmi 20e0000.hdmi_video: xres = 640, yres = 480, freq = 60, vmode = 0, flag = 4 [ 8.295439] mxc_hdmi 20e0000.hdmi_video: Added mode 10: [ 8.295444] mxc_hdmi 20e0000.hdmi_video: xres = 1920, yres = 1080, freq = 60, vmode = 32, flag = 2 [ 8.295453] mxc_hdmi 20e0000.hdmi_video: Added mode 11: [ 8.295458] mxc_hdmi 20e0000.hdmi_video: xres = 1920, yres = 1080, freq = 50, vmode = 32, flag = 2 [ 8.295466] mxc_hdmi 20e0000.hdmi_video: Added mode 12: [ 8.295471] mxc_hdmi 20e0000.hdmi_video: xres = 1920, yres = 1080, freq = 30, vmode = 32, flag = 2 [ 8.295480] mxc_hdmi 20e0000.hdmi_video: Added mode 13: [ 8.295485] mxc_hdmi 20e0000.hdmi_video: xres = 1920, yres = 1080, freq = 24, vmode = 32, flag = 2 [ 8.295494] mxc_hdmi 20e0000.hdmi_video: Added mode 14: [ 8.295501] mxc_hdmi 20e0000.hdmi_video: xres = 1280, yres = 720, freq = 50, vmode = 32, flag = 2 [ 8.295510] mxc_hdmi 20e0000.hdmi_video: Added mode 15: [ 8.295517] mxc_hdmi 20e0000.hdmi_video: xres = 1280, yres = 720, freq = 100, vmode = 32, flag = 2 [ 8.295527] mxc_hdmi 20e0000.hdmi_video: Added mode 16: [ 8.295533] mxc_hdmi 20e0000.hdmi_video: xres = 1280, yres = 720, freq = 120, vmode = 32, flag = 2 [ 8.295541] mxc_hdmi 20e0000.hdmi_video: Added mode 17: [ 8.295546] mxc_hdmi 20e0000.hdmi_video: xres = 720, yres = 480, freq = 59, vmode = 32, flag = 1 [ 8.295554] mxc_hdmi 20e0000.hdmi_video: Added mode 18: [ 8.295559] mxc_hdmi 20e0000.hdmi_video: xres = 720, yres = 576, freq = 50, vmode = 32, flag = 1 [ 8.295602] mxc_sdc_fb fb@0: Y wrap disabled [ 8.799328] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 9.049074] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_set_mode [ 9.049098] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_set_mode: New video mode [ 9.049113] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_set_mode_to_vga_dvi [ 9.049130] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb [ 9.049146] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable [ 9.049334] mxc_sdc_fb fb@0: Reconfiguring framebuffer [ 9.049367] imx-ipuv3 2400000.ipu: Channel already disabled 10 [ 9.049390] imx-ipuv3 2400000.ipu: Channel already uninitialized 10 [ 9.054569] mxc_sdc_fb fb@0: allocated fb @ paddr=0xF2800000, size=691200. [ 9.109150] mxc_sdc_fb fb@0: Reconfiguring framebuffer [ 9.159265] imx-ipuv3 2400000.ipu: DC stop timeout - 5 * 10ms [ 9.159309] imx-ipuv3 2400000.ipu: ipu busfreq high release. [ 9.159326] imx-ipuv3 2400000.ipu: init channel = 9 [ 9.159336] imx-ipuv3 2400000.ipu: ipu busfreq high requst. [ 9.159360] mxc_sdc_fb fb@0: pixclock = 25175000l Hz [ 9.159361] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000 [ 9.159367] imx-ipuv3 2400000.ipu: panel size = 640 x 480 [ 9.159374] imx-ipuv3 2400000.ipu: pixel clk = 25175000 [ 9.159399] imx-ipuv3 2400000.ipu: try ipu internal clk [ 9.159415] imx-ipuv3 2400000.ipu: rounded pix clk:25142857 [ 9.159423] imx-ipuv3 2400000.ipu: round pixel clk:25142857 [ 9.189255] imx-ipuv3 2400000.ipu: div:10 [ 9.189291] mxc_sdc_fb fb@0: Y wrap disabled [ 9.189338] imx-prg 21cc000.prg: bind prg0 ch0 with pre0 [ 10.189709] imx-prg 21cc000.prg: wait for buffer ready timeout [ 10.189724] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init [ 10.189734] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 10.202772] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 10.215809] mxc_sdc_fb fb@0: Y wrap disabled [ 10.291800] imx-pre 21c8000.pre: timeout waiting for PRE to run out of problematic window for shadow update [ 10.291805] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 10.291855] mxc_sdc_fb fb@0: Update complete [ 10.291865] mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_MODE_CHANGE [ 10.291870] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup [ 10.291876] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup - video mode changed [ 10.291885] mxc_hdmi 20e0000.hdmi_video: CEA mode used vic=0 [ 10.291893] mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer [ 10.291900] mxc_hdmi 20e0000.hdmi_video: final pixclk = 24780000 [ 10.291908] mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer exit [ 10.291914] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init [ 10.291923] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 10.304961] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 10.317995] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_enable_video_path [ 10.318001] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup CEA mode [ 10.318011] mxc_hdmi 20e0000.hdmi_video: hdmi_enable_audio_clk [ 10.318016] mxc_hdmi 20e0000.hdmi_video: set up AVI frame [ 10.349256] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup exit [ 10.349256] [ 10.349300] mxc_sdc_fb fb@0: Y wrap disabled [ 10.429013] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 10.859330] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 10.872029] mxc_sdc_fb fb@0: Y wrap disabled [ 10.909652] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 11.379329] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 11.379381] mxc_sdc_fb fb@0: Y wrap disabled [ 11.392469] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 11.889315] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 11.952865] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 11.957594] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb exit [ 12.032604] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 12.035783] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb [ 12.112343] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 12.118257] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable [ 12.194275] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 12.196211] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable - exit [ 12.318475] mxc_sdc_fb fb@0: Reconfiguring framebuffer [ 12.318718] mxc_sdc_fb fb@1: mxcfb_probe enter [ 12.318730] mxc_sdc_fb fb@1: get of property mode_str fail [ 12.318748] mxc_sdc_fb fb@1: NO mxc display driver found! [ 12.322765] pps pps0: new PPS source ptp0 [ 12.329537] fec 2188000.ethernet eth0: registered PHC device 0 [ 12.331284] imx_thermal 20c8000.anatop:tempmon: Extended Commercial CPU temperature grade - max:105C critical:100C passive:95C [ 12.331383] Hot alarm is canceled. GPU3D clock will return to 64/64 [ 12.332023] mxc_sdc_fb fb@1: mxcfb_probe enter [ 12.332036] mxc_sdc_fb fb@1: get of property mode_str fail [ 12.332058] mxc_sdc_fb fb@1: NO mxc display driver found! [ 12.332549] mxc_sdc_fb fb@1: mxcfb_probe enter [ 12.332561] mxc_sdc_fb fb@1: get of property mode_str fail [ 12.332576] mxc_sdc_fb fb@1: NO mxc display driver found! [ 12.339081] Micrel KSZ9021 Gigabit PHY 2188000.ethernet-1:03: attached PHY driver (mii_bus:phy_addr=2188000.ethernet-1:03, irq=POLL) [ 12.369314] imx-ipuv3 2400000.ipu: DC stop timeout - 5 * 10ms [ 12.369392] imx-ipuv3 2400000.ipu: ipu busfreq high release. [ 12.369433] imx-ipuv3 2400000.ipu: init channel = 9 [ 12.369458] imx-ipuv3 2400000.ipu: ipu busfreq high requst. [ 12.369502] mxc_sdc_fb fb@0: pixclock = 148500000l Hz [ 12.369501] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000 [ 12.369522] imx-ipuv3 2400000.ipu: panel size = 1920 x 1080 [ 12.369540] imx-ipuv3 2400000.ipu: pixel clk = 148500000 [ 12.369610] imx-ipuv3 2400000.ipu: try ipu internal clk [ 12.369633] imx-ipuv3 2400000.ipu: rounded pix clk:176000000 [ 12.369651] imx-ipuv3 2400000.ipu: try ipu ext di clk [ 12.369676] imx-ipuv3 2400000.ipu: di clk:148500000 [ 12.369712] imx-ipuv3 2400000.ipu: round pixel clk:148500000 [ 12.399357] imx-ipuv3 2400000.ipu: div:1 [ 12.399419] mxc_sdc_fb fb@0: Y wrap disabled [ 12.399493] imx-ipuv3 2400000.ipu: DMFC high resolution has set, will not change [ 12.399529] imx-prg 21cc000.prg: bind prg0 ch0 with pre0 [ 13.400273] imx-prg 21cc000.prg: wait for buffer ready timeout [ 13.401180] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init [ 13.401207] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 13.413351] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 13.425391] mxc_sdc_fb fb@0: Y wrap disabled [ 13.445292] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 13.467917] imx-pre 21c8000.pre: timeout waiting for PRE to run out of problematic window for shadow update [ 13.467921] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 13.467962] mxc_sdc_fb fb@0: Update complete [ 13.467973] mxc_hdmi 20e0000.hdmi_video: event=FB_EVENT_MODE_CHANGE [ 13.467981] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup [ 13.467986] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup - video mode changed [ 13.467995] mxc_hdmi 20e0000.hdmi_video: CEA mode used vic=16 [ 13.468003] mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer [ 13.468013] mxc_hdmi 20e0000.hdmi_video: final pixclk = 148500000 [ 13.468021] mxc_hdmi 20e0000.hdmi_video: hdmi_av_composer exit [ 13.468027] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_init [ 13.468037] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 13.480072] mxc_hdmi 20e0000.hdmi_video: hdmi_phy_configure [ 13.492109] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_enable_video_path [ 13.492117] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup CEA mode [ 13.492127] mxc_hdmi 20e0000.hdmi_video: hdmi_enable_audio_clk [ 13.492134] mxc_hdmi 20e0000.hdmi_video: set up AVI frame [ 13.515132] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 13.529241] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_setup exit [ 13.529241] [ 13.529515] mxc_sdc_fb fb@0: Y wrap disabled [ 13.559250] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received .......................... [ 14.011217] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 14.039316] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 14.041223] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 14.081533] mxc_sdc_fb fb@0: Y wrap disabled [ 14.101229] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received .......................... [ 14.584323] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 14.589302] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 14.589361] mxc_sdc_fb fb@0: Y wrap disabled [ 14.614327] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received .......................... [ 15.094580] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.099295] mxc_sdc_fb fb@0: timeout when waiting for flip irq [ 15.159937] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_notify_fb exit [ 15.184587] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.186572] mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_cable_connected exit [ 15.215590] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.449726] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 15.451501] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.479325] Sending DHCP requests . [ 15.482506] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.898440] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.919244] , [ 15.928448] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.958451] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.979302] OK [ 15.981125] IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.12 [ 15.988457] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 15.988797] IP-Config: Complete: [ 15.998406] device=eth0, hwaddr=00:0d:15:01:b0:f4, ipaddr=192.168.1.12, mask=255.255.255.0, gw=192.168.1.1 [ 16.008553] host=192.168.1.12, domain=, nis-domain=(none) [ 16.014420] bootserver=0.0.0.0, rootserver=192.168.1.41, rootpath= [ 16.014428] nameserver0=208.67.220.220 [ 16.018459] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 16.021077] , nameserver1=208.67.222.222 [ 16.035658] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 16.045982] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 16.049470] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 16.053202] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' [ 16.065353] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 16.074001] clk: Disabling unused clocks [ 16.078149] ALSA device list: [ 16.079480] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 16.081155] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 16.087502] #0: imx6-rex-sgtl5000 [ 16.109488] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 16.115993] VFS: Mounted root (nfs filesystem) on device 0:16. [ 16.122173] devtmpfs: mounted [ 16.126823] Freeing unused kernel image (initmem) memory: 1024K [ 16.133864] Run /sbin/init as init process [ 16.139491] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 16.169508] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 16.200505] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received INIT: version 3.04 booting[ 16.230512] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received /bin/hostname: invalid option -- [ 16.621278] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 16.651279] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received INIT: [ 16.682294] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received Entering runlevel: 3[ 16.712292] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received Starting udev [ 17.295615] udevd[184]: starting version 3.2.14 [ 22.689252] random: crng init done [ 22.743558] udevd[186]: starting eudev-3.2.14 [ 22.889792] mxc_sdc_fb fb@1: mxcfb_probe enter [ 22.900906] mxc_sdc_fb fb@1: get of property mode_str fail [ 22.906486] mxc_sdc_fb fb@1: NO mxc display driver found! [ 22.917520] platform fb@1: deferred probe pending [ 22.938942] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 23.040064] caam-snvs 20cc000.caam-snvs: ipid matched - 0x3e [ 23.045825] caam-snvs 20cc000.caam-snvs: violation handlers armed - non-secure state [ 23.054427] mxc_sdc_fb fb@1: mxcfb_probe enter [ 23.058922] mxc_sdc_fb fb@1: get of property mode_str fail [ 23.059962] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 23.069185] mxc_sdc_fb fb@1: NO mxc display driver found! [ 23.069883] caam 2100000.crypto: Entropy delay = 3200 [ 23.088553] caam 2100000.crypto: Instantiated RNG4 SH0 [ 23.089973] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 23.097590] caam 2100000.crypto: Instantiated RNG4 SH1 [ 23.105821] caam 2100000.crypto: device ID = 0x0a16010000000000 (Era 4) [ 23.113508] caam 2100000.crypto: job rings = 2, qi = 0 [ 23.119982] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 23.121844] mxc_sdc_fb fb@1: mxcfb_probe enter [ 23.136293] mxc_sdc_fb fb@1: get of property mode_str fail [ 23.144839] mxc_sdc_fb fb@1: NO mxc display driver found! [ 23.150990] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 23.340505] caam algorithms registered in /proc/crypto [ 23.346002] caam 2100000.crypto: rng crypto API alg registered prng-caam [ 23.352778] caam 2100000.crypto: registering rng-caam [ 23.359552] Device caam-keygen registered [ 23.361193] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 23.364105] mxc_sdc_fb fb@1: mxcfb_probe enter [ 23.374530] mxc_sdc_fb fb@1: get of property mode_str fail [ 23.380068] mxc_sdc_fb fb@1: NO mxc display driver found! [ 23.387137] mxc_sdc_fb fb@1: mxcfb_probe enter [ 23.391198] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received [ 23.391689] mxc_sdc_fb fb@1: get of property mode_str fail [ 23.403470] mxc_sdc_fb fb@1: NO mxc display driver found! [ 23.421202] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received sysctl: cannot stat /proc/sys/net/ipv4/tcp_syncookies: No such file or directory [ 23.662273] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received hwclock: settimeofday: Invalid argument [ 23.692282] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received Fri Mar 9 12:34:56 UTC 2018 [ 24.445649] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received Setting kernel log level to 3 [ 24.475672] mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received Configuring network interfaces... ip: RTNETLINK answers: File exists ifup skipped for nfsroot interface eth0 run-parts: /etc/network/if-pre-up.d/nfsroot: exit status 1 ip: SIOCGIFFLAGS: No such device Starting system message bus: dbus. Starting OpenBSD Secure Shell server: sshd done. Starting syslogd/klogd: done Poky (Yocto Project Reference Distro) 5.0.9 imx6-rexultra /dev/console imx6-rexultra login: There were hundereds of repeation of "mxc_hdmi 20e0000.hdmi_video: Overflow interrupt received" which I have cleaned Re: Problem in setting up PRE -> PRG -> IPU -> HDMI pipeline on i.MX6 the link you shared includes different imx6 boards, I don't know which one you used, for standard HDMI or IPU settings in the dts files, I suggest that you can refer to the nxp official bsp https://github.com/nxp-imx/linux-imx/tree/lf-6.6.y/arch/arm/boot/dts/nxp/imx you can find different imx6 board settings, you can refer to that and porting this on your own board by yourself, you also can refer to the porting guide for detailed information https://www.nxp.com/docs/en/user-guide/UG10165.pdf Re: Problem in setting up PRE -> PRG -> IPU -> HDMI pipeline on i.MX6 We have already contacted them, and they confirmed that this is the extent of the support they can provide. Development for the i.MX6 board has been discontinued. At this point, the available options are either to migrate to an i.MX8-based platform or to take ownership of the porting and maintenance effort ourselves. The issue appears to be internal to the SoC, specifically related to the interconnection and configuration of the PRE, PRG, IPU, and HDMI blocks. This strongly suggests a device tree configuration problem rather than an external hardware fault as the HDMI driver is up and runinning. Re: Problem in setting up PRE -> PRG -> IPU -> HDMI pipeline on i.MX6 this is third party company board, I suggest that you can contact them to get further support, because board settings are based on the HW design, they should offer the basic booting up support, if the issue is related to the imx6 SOC, we can offer the support Re: Problem in setting up PRE -> PRG -> IPU -> HDMI pipeline on i.MX6 Modified imx6qdl-rex.dtsi to add following mxcfb1: fb@0 { compatible = "fsl,mxc_sdc_fb"; disp_dev = "hdmi"; interface_pix_fmt = "RGB24"; mode_str ="1920x1080M@60"; default_bpp = <24>; int_clk = <0>; late_init = <0>; status = "disabled"; }; mxcfb2: fb@1 { compatible = "fsl,mxc_sdc_fb"; disp_dev = "ldb"; interface_pix_fmt = "RGB666"; default_bpp = <16>; int_clk = <0>; late_init = <0>; status = "disabled"; }; mxcfb3: fb@2 { compatible = "fsl,mxc_sdc_fb"; disp_dev = "lcd"; interface_pix_fmt = "RGB565"; mode_str ="CLAA-WVGA"; default_bpp = <16>; int_clk = <0>; late_init = <0>; status = "disabled"; }; mxcfb4: fb@3 { compatible = "fsl,mxc_sdc_fb"; disp_dev = "ldb"; interface_pix_fmt = "RGB666"; default_bpp = <16>; int_clk = <0>; late_init = <0>; status = "disabled"; }; Re: Problem in setting up PRE -> PRG -> IPU -> HDMI pipeline on i.MX6 So, If i build linux-fslc with imx_v6_v7_defconfig it uses ETNAVIV and IMX_IPUV3 drivers and enables following and I do get HDMI output CONFIG_DRM_ETNAVIV CONFIG_DRM_IMX CONFIG_IMX_IPUV3_CORE CONFIG_DRM CONFIG_DRM_DW_HDMI Where as linux-imx with imx_v7_defconfig uses VIVANTE and MXC_IPU. This is where I lose my HDMI output. It enables following CONFIG_MXC_GPU_VIV CONFIG_MXC_IPU CONFIG_MXC_IPU_V3_PRE CONFIG_FB_MXC_HDMI My understanding is hdmi with working with DRM_IMX_IPUV3 and not working with MXC_IPU.  Now I want to ask is it possible to use VIVANTE GPU driver with DRM_IMX_IPUV3 instead of MXC_IPU.  I did try it but I ended up in a kernel panic which you can check here https://pastebin.com/S4VRQU9u . Re: Problem in setting up PRE -> PRG -> IPU -> HDMI pipeline on i.MX6 linux-fslc is community bsp, not developed by the NXP, and supported by the [email protected],  linux-imx  is nxp official bsp, it seems your bsp is based on the linux-fslc, for the linux-imx, if you are interested with nxp official bsp, you can refer to the 6.3.2 Image Processing Unit (IPU) of enclosed file

Where does the clock for the RW612 LCDIC come from and how many HZ can the SPI 8080 run to respectively?

QNXがNXPに登場 こんにちは、サポートチームの皆様 評価ボード S32G-VNP-RDB3 で QNX イメージを起動することに関する質問があります。QNX ソフトウェア センターから参照イメージを入手できます。 QNX BSPビルドプロセスの出力は.uiです。ファイル。 すでに Linux Yocto BSP パッケージが動作しており、これをビルドして SD ブートを使用しました。これは.sdカードです正常に起動しているイメージ。Linux イメージ ファイルの代わりに QNX イメージを使用しようとしましたが、起動しません。 以下の質問があります:- QNX を起動するには、Linux Yocto ビルドから u-boot または ATF に変更を加える必要がありますか? 起動するには QNX イメージ形式に何か変更が必要ですか? PS: QNX ビルドから生成された生のファイルのブートも試みました。起動もしませんでした。 Re: QNX bring up in NXP Silicon Signalsで試してみるといいでしょう Re: QNX bring up in NXP こんにちは@shebin 、 QNX は NXP 製品ではないため、それに関する情報はあまりありません。そうは言っても、役に立つかもしれないアプリケーション ノートがあります: AN14355 は、 S32G3 製品ページでいつでも入手できます。このドキュメントの目的は、QNX で PFE を使用する方法を説明することですが、uboot と ATF を設定してフラッシュする方法、および SD カードを設定する方法を説明するセクションがいくつかあります。セクション4「前提条件」 、 「5「コンポーネント」」 、および5.2.4「準備された SD カードのサンプル パーティション」を確認してください。確実に動作させるために、ドキュメントに記載されているコンポーネント バージョンを使用することを強くお勧めします。 一部の手順は PFE のコンポーネントを構成するためのものであるため、スキップできる可能性があります。 この情報で問題が解決したかどうかお知らせください。

IMX8MP Kernel Configuration CAAM Reboot System Stuck Hello NXP community technicians! IMX8MP motherboard reboot encountered problems: yocto system for reboot, there will be a kernel stuck print, resulting in the kernel has not been responsive, as if into a dead loop waiting; has been configured with CAAM, not sure if it is caused by this configuration, the probability of recurrence of 1/100,1/200,1/500; to help analyze and see it, I look forward to your reply! Platform: IMX8MP Kernel: 6.6.52 yocto: init boot 5.0 The log is as follows, the full log and CAAM configuration will be attached configure.txt and log.txt [ 2.131014] caam 30900000.crypto. device ID = 0x0a16040100000100 (Era 9) [ 2.137748] caam 30900000.crypto. job rings = 2, qi = 0 [ 2.145206] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA [ 2.146567] caam algorithms registered in /proc/crypto [ 2.157655] caam 30900000.crypto. caam pkc algorithms registered in /proc/crypto [ 2.165088] caam 30900000.crypto. rng crypto API alg registered prng-caam [ 2.171948] caam 30900000.crypto. registering rng-caam [ 2.179519] Executing RNG SELF-TEST with wait [ 2.257632] mmc2: new HS400 Enhanced strobe MMC card at address 0001 [ 2.265061] mmcblk2: mmc2:0001 DV4032 29.1 GiB [ 2.273422] mmcblk2: p1 p2 p3 [ 2.278865] mmcblk2boot0: mmc2:0001 DV4032 4.00 MiB [ 2.285336] mmcblk2boot1: mmc2. 0001 DV4032 4.00 MiB [ 2.291975] mmcblk2rpmb: mmc2:0001 DV4032 16.0 MiB, chardev (234:0) [ 60.417175] imx-sdma 30bd0000.dma-controller. Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 [ 60.427636] imx-sdma 30bd0000.dma-controller. Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin [ 121.829472] imx-sdma 30bd0000.dma-controller. external firmware not found, using ROM firmware [ 122.985105] random: crng init done Re: IMX8MP 内核配置CAAM重启系统卡住 Thanks for the reply, I'll turn off the self-checking verification on my end and see if turning this off will have any effect on the CAAM application. Re: IMX8MP 内核配置CAAM重启系统卡住 Hi @DADAXIN Take a look at this log. Executing RNG SELF-TEST with wait Try setting CONFIG_CRYPTO_DEV_FSL_CAAM_RNG_TEST to n. Best Regards, Zhiming Re: IMX8MP 内核配置CAAM重启系统卡住 Hi @DADAXIN You try the problem first to see if this CAAM test is causing it. Best Regards, Zhiming Re: IMX8MP 内核配置CAAM重启系统卡住 Hi @dadaxin It has no effect, I don't see this in the latest bsp defconfig. Best Regards, Zhiming Re: IMX8MP 内核配置CAAM重启系统卡住 Thanks for the reply, by default BSP does not enable this configuration; but does it have any effect to not enable this CAAM self-test when CAAM function is enabled? Re: IMX8MP 内核配置CAAM重启系统卡住 Hi, Zhiming After turning off CONFIG_CRYPTO_DEV_FSL_CAAM_RNG_TEST, 1000 times of hot reboot on multiple motherboards are normal, so it can be confirmed that CAAM self-test has an effect on hot reboot, and the actual application can turn off this configuration?

secure boot on imx8m plus on Android14 BSP I want to enable the secure boot on imx8m plus board with Android 14 BSP, such that the board will always boot on our signed keys only. i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Re: secure boot on imx8m plus on Android14 BSP pls refer to this document firstly https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/Steps-for-single-secure-boot-for-Android-BSP/ta-p/2157256 Re: secure boot on imx8m plus on Android14 BSP I have followed the steps given in the PDF and generated the keys like:  SRK1_sha256_1024_65537_v3_ca_key.der SRK1_sha256_1024_65537_v3_ca_key.pem SRK1_sha256_1024_65537_v3_usr_key.der SRK1_sha256_1024_65537_v3_usr_key.pem SRK1_sha256_2048_65537_v3_ca_key.der SRK1_sha256_2048_65537_v3_ca_key.pem SRK2_sha256_1024_65537_v3_ca_key.der SRK2_sha256_1024_65537_v3_ca_key.pem SRK2_sha256_2048_65537_v3_ca_key.der SRK2_sha256_2048_65537_v3_ca_key.pem SRK3_sha256_2048_65537_v3_ca_key.der SRK3_sha256_2048_65537_v3_ca_key.pem SRK4_sha256_2048_65537_v3_ca_key.der SRK4_sha256_2048_65537_v3_ca_key.pem and also the CSF, IMG and CA. the private keys are openssl x509 -in crts/SRK1_sha256_2048_65537_v3_ca_crt.pem -text -noout | grep Subject Subject: CN = SRK1_sha256_2048_65537_v3_ca Subject Public Key Info: X509v3 Subject Key Identifier:  openssl x509 -in crts/CSF1_1_sha256_2048_65537_v3_usr_crt.pem -text -noout | grep Issuer Issuer: CN = SRK1_sha256_2048_65537_v3_ca openssl rsa -in keys/SRK1_sha256_2048_65537_v3_ca_key.pem -check Enter pass phrase for keys/SRK1_sha256_2048_65537_v3_ca_key.pem: RSA key ok Are all these keys ready to flash on imx8m plus smarc som? Re: secure boot on imx8m plus on Android14 BSP did you generate SRK table already? Re: secure boot on imx8m plus on Android14 BSP yes, SRK Hash TableSRK Hash TableSRK Hash TableSRK Hash TableSRK Hash Table the SRK Hash table is generated successfully from the keys Re: secure boot on imx8m plus on Android14 BSP ok, then you can refer to the chapter 3.1.2.2 Signing bootloader images and 3.1.2.3 Signing the MCU firmware of enclosed file Re: secure boot on imx8m plus on Android14 BSP I have burned the fuses on my imx8m plus board, but unable to get the signed image or flashing,  how to recover and find the correct igned image for flashig? Re: secure boot on imx8m plus on Android14 BSP I am unable to sign the correct image on my imx8m plus board after fusing the keys permanently on the board! 

S32DS 3.5 をインストールしても起動しない 親愛なるみんな; S32DS 3.5はインストール後に起動できませんが、S32DS 3.6.3は正常でした。システム変数から JAVA_HONE 変数を削除したり、S3D2S 3.5 を再インストールしたりするなど、さまざまな解決方法を試しましたが、機能しません。 解決方法がわかりませんので、解決するための提案があれば、大変ありがたく思います。 PC環境: Windows10 64ビット、32GB RAM 添付ファイルはログのファイルですので、ご覧ください。 ths Re: S32DS 3.5 does not start up after installed この欠陥を解決するには、Windows 10 を再インストールすると効果的かもしれません。

[RTD] S32K358/GMACGmac_apxState 为 NULL 客户报告说 Gmac_apxState[Instance] 是 NULL （见下面的截图）。 您能解释一下 Gmac_apxState[Instance] 在什么情况下会变成 NULL 吗？ 此外，请说明出现这种状态的典型情况或故障路径，以及建议的检查或缓解措施。 在我的评论中，可能的原因之一似乎是以太网参考时钟故障。 RTD Re: [RTD] S32K358/GMACGmac_apxState is NULL 你好@alexyang、 Gmac_apxState[Instance] = NULL_PTR 只是在两种情况下： 1.在调用其他函数（如 Gmac_Ip_ProvideRxBuff()、..：Gmac_Ip_ProvideRxBuff(),...在每个函数的头部添加了检查 GMAC_DEV_ASSERT(Gmac_apxState[Instance]!=NULL_PTR);，以确保驱动程序已通过 Gmac_Ip_Init()初始化。 2.调用了函数 Gmac_Ip_Deinit()。 因此，您可以检查客户调用 api 函数的顺序。 在 Gmac_Ip_Init() 之后，Gmac_apxState[Instance] 必须与 NULL_PTR 不同。 顺祝商祺！ Nhi

リセットで止まる 私は S32M24x EVB を使っていますが、コントローラーがリセット状態のままになっています。搭載デバッガーを使用しています。 リセット LED が常にハイになっているのがわかり、コントローラーで何もフラッシュできません。 私はDesign Studioを使用しており、「実行中のターゲットにアタッチ」を有効にして試してみましたが、搭載デバッガーは攻撃できますが、停止またはリセットできず、しばらくするとアタッチメントも壊れているようです。 「arm-none-eabi-gdb.exe」を直接使用して試してみましたが、デバイスは保護されており、ソフト リセットに失敗したと表示されます。 ハードウェアもチェックしましたが、コンポーネントは損傷していませんでした。 実行中のプログラムのフラッシュ構成ワードは次のとおりです。 .section .flash_config, "a" .long 0xFFFFFFFF ; 8 bytes backdoor comparison key .long 0xFFFFFFFF ; .long 0xFFFFFFFF ; 4 bytes program flash protection bytes .long 0xFFFF7FFE ; FDPROT:FEPROT:FOPT:FSEC(0xFE = unsecured) そしてフラッシュセクションは - MEMORY { int_flash_config : ORIGIN = 0x00000400, LENGTH = 0x00000010 } SECTIONS { .flash_config ALIGN(4) : > int_flash_config } この状況の原因は何でしょうか? また、コントローラを再び正常に動作させる方法は何でしょうか? 前もって感謝します！！！ Re: Stuck in Reset この問題は、起動時にフラッシュ構成ワードがクリアされたために発生しました。 Re: Stuck in Reset こんにちは@Satyajit_Patil オシロスコープを使用してリセット信号を確認していただけますか?リセットピンを直接測定し、観察した波形の画像を共有します。リセット ラインが図のように切り替わる、添付の信号と同様の信号が表示されることが予想されます。 さらに、私や同様の現象を経験している他のお客様に効果があったプロセスを試していただけますか?MCU を再フラッシュするには、点滅例を使用してフラッシュを試行しながらリセット ボタンを押し続けます。失敗する可能性があり、再試行するかどうかを尋ねられます。その場合は、リセット ボタンを放し、そのプロンプトの下で再度プログラムのロードを試みてください。これを実行すると、プログラムは正常にロードされ、ボードが回復するはずです。 上記の手順を試しても問題が解決しない場合は、お知らせください。 BR、ヴェインB

CAAM ドライバからのユーザーコールバックの使用方法 がある： /*! @brief CAAMハンドル * jobRing とオプションでユーザー コールバック関数を指定します。 * ユーザー コールバック関数は、ジョブリング割り込みがユーザーによって有効にされている場合にのみ呼び出されます。 * デフォルトでは、jobRing 割り込みは無効になっています (デフォルトのジョブ完了テストは CAAM 出力リングをポーリングします)。 */ typedef 構造体 _caam_handle_t { caam_job_ring_t ジョブリング; /* コールバック関数 */ caam_job_callback_t コールバック; /*!< コールバック関数 */ void *userData; /*!< CAAMジョブ完了コールバックのパラメータ */ } caam_handle_t; SOコールバックを書いてcaam_handle_t*ハンドルにマッピングしました 静的void xpnd_CAAM_job_ring_1_complete_clb(void* args) { BaseType_t pxHigherPriorityTaskWoken = pdFALSE; xSemaphoreGiveFromISR(sem[ITF_1], &pxHigherPriorityTaskWoken); IRQ を無効にします(CAAM_IRQ1_IRQn); } 最後に試したのは: IRQ を有効にします (CAAM_IRQ1_IRQn); drv_res = CAAM_RNG_GetRandomDataNonBlocking( ベース、ハンドル、kCAAM_RngStateHandle0、説明、データ、データサイズ、 kCAAM_RngDataAny、NULL); if (drv_res == kStatus_Success) { pdTRUE != xSemaphoreTake(sem[ITF_1], MS_TIMEOUT) の場合 { PRINTF("CAAM 操作に失敗しました\r\n"); ST_FAILURE を返します。 } } それ以外 { PRINTF("ドライバ操作のセットアップに失敗しました、res %d\r\n", drv_res); ST_FAILURE を返します。 } セマフォからエラーを報告しなかったため、プログラムはすぐにクラッシュしたと思います。 他に何かする必要がありますか? アセンブリ startup_mimxrt1176 には CAAM_IRQ0_IRQHandler のプロトタイプがありますが、定義されていない可能性があります。このような状況になるでしょうか? また、ドライバ コードでは、カスタム コールバックが呼び出される場所がわかりません。 Re: How to use user callback from CAAM driver こんにちは@jslota13245さん、 弊社の製品にご興味をお持ちいただき、またコミュニティをご利用いただき誠にありがとうございます。 あなたのコードは FreeRTOS に基づいているようです。 まず NXP SDK デモ「evkbmimxrt1170_caam_cm4」でテストすることをお勧めします。このデモプロジェクトは、KSDKソフトウェアを使用してプレーンテキストを暗号化し、AESアルゴリズムを使用して復号化するデモプログラムです。CBCモードとGCMモードのデモが行われます。対称鍵は、CAAMの乱数ジェネレータを使用してランダムに生成されます。   このデモを実行して、問題が API の使用によるものか、FreeRTOS の統合によるものかを確認してください。   よろしくお願いいたします。 メイリュー Re: How to use user callback from CAAM driver 親愛なる@mayliu1様、 デモでは、ユーザー コールバックの使用方法、または実際の割り込みの使用方法は示されません。 完了時に CAAM ハードウェアからの割り込みが必要です。それについて手伝ってもらえますか？

Power consumption regression after suspend/freeze in BSP 6.6.36 (i.MX8MP) Hello, We are observing a power consumption regression on i.MX8M Plus when using the NXP RealTime Edge v3.1 BSP based on Linux 6.6.36. After suspend/resume, the system consumes ~20% more power than before entering suspend. This happens with a very minimal hardware setup: only NAND and eMMC are connected (no USB, PCIe, Wi-Fi, ETH, etc.). Comparison across BSPs: linux-imx BSP based on Linux 6.6.23 (non-RT): no issue, power consumption is correctly restored after suspend/freeze Realtime Edge 3.1 BSP Linux 6.6.36 (non-RT and RT): issue present Realtime Edge 3.3 BSP (Linux 6.12): no issue observed, power consumption is restored correctly Please let us know if this is a known issue or if there are recommended patches or configuration changes. If needed, we can provide device tree sources, kernel configuration, and any additional files required to help reproduce and analyze the issue. Best regards, Aitor i.MX 8M | i.MX 8M Mini | i.MX 8M Nano i.MXRT Linux Suspected Software Defect Yocto Project Re: Power consumption regression after suspend/freeze in BSP 6.6.36 (i.MX8MP) Hello, Sorry for that, but yes we have update the BSP, please download the real time edge 3.3. Regards Re: Power consumption regression after suspend/freeze in BSP 6.6.36 (i.MX8MP) Hello, Thank you for the reply. We have already tested Realtime Edge 3.3 (kernel 6.12) and can confirm that the issue is not present there. However, upgrading to 3.3 is not an option for us at the moment, as we are currently based on Realtime Edge 3.1 and need to stay close to our existing kernel and BSP for compatibility reasons. Since the problem is fixed in Realtime Edge 3.3, could you please point us to: The specific patch(es) or commit(s) where this issue was addressed, or Any recommended backport to BSP 3.1 / kernel 6.6.x This would allow us to apply the fix without requiring a full BSP upgrade Best regards, Aitor Re: Power consumption regression after suspend/freeze in BSP 6.6.36 (i.MX8MP) Hi, In this case you will have to ask to our professional services since some package that are needed in the 3.1 are update. Regards

MCXE246 MCUXpresso not working for custom board The generated code for a basic project for a custom board with a MCXE246 doesn't work correctly. To make it compile i needed to add  __attribute__ ((used,section(".FlashConfig"))) const struct { unsigned int word1; unsigned int word2; unsigned int word3; unsigned int word4; } Flash_Config = {0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFF, 0xFFFFFFFE}; but when debugging the code doesn't run, it keeps starting in the WDOG code executing every line from the top of the file to the bottom even if the functions are not called. I never reach the main() Is it possible to provide me with a mcuexpresso project for a custom board with a mcxe246? Thank you Kind regards Niels Boot ROM|Booting | Flash Core and Memory Re: MCXE246 MCUXpresso not working for custom board Hi @nd_psi  Thanks for your project. Your project is missing the start. c file. This is a bug in our old version SDK. But we fix it. Please download the latest version of SDK v25.12. BR Harry Re: MCXE246 MCUXpresso not working for custom board Hi @Harry_Zhang, Thank you for your reply, unfortunately it still doesn't work. When I follow the same steps, I get a compile error saying that no flashconfig is provided. I can get rid of this error by disabling the following option (which is enabled by default): When I debug, the MCU crashes immediately and I get the error No source available for "_pvHeapStart() at 0x1fff0080" . I have attached my project. MCUXpresso IDE v25.6 [Build 136] [2025-06-27] SDK_2.x_MCXE246 version 25.09.0.201911251446 (epluginsite815 2025-09-22) 3.15.0 Kind regards Niels Re: MCXE246 MCUXpresso not working for custom board Hi @nd_psi  I tested it on my end. 1. Create a new mcxe246 project. 2. You don't need to add Flash_Config , it can compile successfully 3. And i can debug it. BR Harry Re:Re: MCXE246 MCUXpresso not working for custom board Hi @Harry_Zhang, Thank you for your reply, I updated the SDK and i can now compile it without changing a setting. But when i debug i still get an error and never reach main(). I have attached my project. Kind regards Niels Re: Re:Re: MCXE246 MCUXpresso not working for custom board Hi @nd_psi  I just tested your project. I can debug it. So I think you can try to connect the chip with the jlink. If you can not connect the chip : prioritize  check the hardware connection BR Harry Re: Re:Re: MCXE246 MCUXpresso not working for custom board Hi @nd_psi  “ I connected the J-link to the FRDM-MCXE247 board and observed the same behavior.” In my last reply, my test board was FRDM-MCXE247 and my debuger was J-link. So I think you can try changing a J-link. BR Harry Re: Re:Re: MCXE246 MCUXpresso not working for custom board Hi @Harry_Zhang, Thank you for your reply, unfortunately it still doesn't work. The problem is that I can connect via J-link, but when I start debugging, the program counter jumps to a random location in memory, so you can never execute your code (you also don't end up in the main). You can connect via J-link. I have checked the connections, and this does not offer a solution either. I connected the J-link to the FRDM-MCXE247 board and observed the same behavior. In addition, I connected my custom board to an MCU link, and it works there, so you can run your code without any problems. Are there any known issues with debugging using J-link? Kind regards Niels

FLEXIO I2C による RPMSG の問題 私は i.MX93 M33 コア開発の初心者です。サンプル コード mcimx93evk_rpmsg_lite_str_echo_rtos_remote_cm33 と mcimx93evk_flexio_i2c_read_accel_value_transfer_cm33 をテストしましたが、どちらも正常に動作しました。 しかし、FlexIO I²C 関数を mcimx93evk_rpmsg_lite_str_echo_rtos_remote_cm33 にマージしようとすると、プログラムは FLEXIO_I2C_MasterInit() によって呼び出される FLEXIO_SetShifterConfig() で停止してしまいます。 これら 2 つの機能 (初期化順序、クロック/IRQ 設定、注意すべきリソース競合など) をきれいに統合するためのアドバイスやベスト プラクティスを共有していただける方はいらっしゃいますか?どなたかご指導いただければ幸いです。よろしくお願いします。 Re: Issue of RPMSG with FLEXIO I2C dtbを添付しました。ありがとうございます! Re: Issue of RPMSG with FLEXIO I2C こんにちは@nyc 使用している dts を共有していただけますか? よろしくお願いします、 志明 Re: Issue of RPMSG with FLEXIO I2C @スタッフお手伝いできるスタッフはいますか? Re: Issue of RPMSG with FLEXIO I2C こんにちは@nyc dtsをチェックしましたが、異常はありません。コードをもう一度確認し、クロックが生成されていることを確認してください。FLEXIO I2C ファイルを再度確認してください。 よろしくお願いします、 志明

RW612 - WiFi チャネル状態情報 (CSI) 現在、FRDM-RW612 から CSI データを抽出しようとしています。パラメータを誤って構成すると、ファームウェアが不正なチャネル構成などのエラーを通知することになるため、CSI コールバックが機能しない原因となっている重要なコンポーネントが不足しているものと思われます。残念ながら、まだ CSI のコールバックを取得できません。 どなたか助けていただければ幸いです! Re: RW612 - WiFi Channel State Information (CSI) 親愛なる@rb_ots様、 お客様向けにチャネル状態情報 (CSI) のアプリケーション ノートを提供しています。（AN14281） このアプリケーションは、FRDM-RW612 で CSI テストを段階的に実行する方法を説明します。 リンクから AN にアクセスできます。これはオンライン ドキュメントです。 https://docs.nxp.com/bundle/AN14281/page/topics/about_this_document.html ぜひお試しください！ よろしくお願いいたします。 魏東 Re: RW612 - WiFi Channel State Information (CSI) はい！まさに私が探していたものであり、大変助かりました。

i.MX8MP 平台开启 CAAM + trusted keys 后 warm reboot 稳定性问题咨询 NXP社区技术人员，大家好        在 i.MX8MP 平台上做系统稳定性测试时，遇到一个与 CAAM 相关的 warm reboot 小概率卡住问题，想请教是否有相关经验或建议的配置方式。 测试环境说明 SoC：i.MX8MP 系统：Yocto Linux（init 启动方式） 内核版本：6.6.52 存储：eMMC 测试方式：系统启动后，通过脚本进行连续 reboot 压力测试 现象描述 关闭 CAAM 相关功能时 连续 reboot 测试超过 500 次 系统均可正常启动 未出现卡死或启动异常 开启 CAAM 及 trusted/encrypted keys 相关功能后 reboot 测试中 约 1/100 ～ 1/200 的概率 系统在启动阶段卡住 串口停留在早期初始化日志 异常时可观察到类似日志     3、异常时可观察到类似日志          <1>内核卡住log [ 2.159151] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto [ 2.166628] caam 30900000.crypto: rng crypto API alg registered prng-caam [ 2.173441] caam 30900000.crypto: registering rng-caam [ 2.180670] Executing RNG SELF-TEST with wait [ 2.259240] mmc2: new HS400 Enhanced strobe MMC card at address 0001 [ 2.266720] mmcblk2: mmc2:0001 DV4032 29.1 GiB [ 2.274171] mmcblk2: p1 p2 p3 [ 2.279584] mmcblk2boot0: mmc2:0001 DV4032 4.00 MiB [ 2.286069] mmcblk2boot1: mmc2:0001 DV4032 4.00 MiB [ 2.293040] mmcblk2rpmb: mmc2:0001 DV4032 16.0 MiB, chardev (234:0) [ 60.410412] imx-sdma 30bd0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 [ 60.420874] imx-sdma 30bd0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin [ 121.822422] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware [ 123.010384] random: crng init done      <2> 在 reboot 过程中，也偶尔能看到： caam_jr ... Device is busy      <3> 相关内核配置 CONFIG_CRYPTO=y CONFIG_CRYPTO_DEV_FSL_CAAM=y CONFIG_CRYPTO_DEV_FSL_CAAM_JR=y CONFIG_CRYPTO_DEV_FSL_CAAM_RNG_API=y CONFIG_TRUSTED_KEYS=y CONFIG_TRUSTED_KEYS_CAAM=y CONFIG_ENCRYPTED_KEYS=y CONFIG_DM_CRYPT=y 关闭 CAAM（或 trusted/encrypted keys），warm reboot 稳定性恢复正常 Re: i.MX8MP 平台开启 CAAM + trusted keys 后 warm reboot 稳定性问题咨询 你好 在 i.MX8MP 平台上，考虑到您提供的内核 6.6.52 和 CAAM RNG 自检卡住问题，这通常与残余 RNG 初始化状态、作业环权限锁定或 SDMA 固件加载超时引起的连锁反应有关。以下是针对该问题的分析建议和配置解决方案： 1。核心原因分析 CAAM 状态机未 RESET：热重启不会 RESET 所有 SoC 寄存器。如果 CAAM 在重启之前很忙（例如，caam_jr...设备在日志中处于繁忙状态），重启后 RNG 的硬件状态机可能处于不确定的中间状态。任务环权限问题：如果使用高度保证启动 (HAB) 或 OP-TEE，BootROM 或 ATF 可能会锁定某些任务环 (JR)。在热重启期间，如果未正确释放 JR 寄存器，Linux 内核将在执行 RNG 自测并等待阶段无限期等待，因为它无法获得硬件响应。 2.建议的优化和解决方案 答：内核配置和驱动程序调整禁用同步自检：尝试在 CONFIG_CRYPTO_DEV_FSL_CAAM_RNG_API 中禁用强制等待机制，或者在 U-启动 中预初始化 RNG。 集成 SDMA 固件：将 SDMA 固件编译到内核（CONFIG_EXTRA_FIRMWARE= " imx/sdma/sdma-imx7d.bin "）中，以避免在启动的早期阶段由于文件系统未安装而导致 60 秒的等待时间。这可以大大降低启动过程中的时间风险。 B. 修改 U-启动/ATF RESET 行为（解决方法）热RESET 在 i.MX8M 系列上经常会出现这种残留问题。 C 。DTS 设备树检查 caam_jr 节点的属性。在某些版本中，必须确保任务环分配与安全模式一致： &crypto { status = "okay"; }; &sec_jr0 { status = "okay"; }; 此致 Re: i.MX8MP 平台开启 CAAM + trusted keys 后 warm reboot 稳定性问题咨询 感谢回复！我将对这两个部分进行改动验证，后续反馈情况；

VR5510 BUCKx electrical specification and LDO2 instability Hello I'm looking for information about VR5510 BUCK performances: I would like to use them in analog application where an LDO is the right choose: however VR5510 LDOs can be at limit current in some situation. I'm not able to find any information about voltage ripple specification of the BUCKs (referred to suggested output filter, I'm using). Is it possible to have? I found on this forum that other VRs have this kind of information but VR5510 doesn't. I have an issue using VR5510 in companion with SJA1110. Short story long: if the SJA1110 is keep in HARD RESET and I power up the VR5510 from external source, the LDO2 connected to VDDIO 1.8V MII power supply rail startup in instability generating 2.2V instead of 1.8V (i think that voltage can rise up to Vin 3.3V if not limited by some SJA1110 internal clamp) Attached the portion of the schematic from NXP  SJA1110-EVM board that is exactly what I used on my custom board. I'm monitoring the 1.8V voltage with VR5510 internal voltage monitors, in that case VR5510 PGOOD never change state because of OVERVOLTAGE detected. Very strange thing is that if I disconnect PGOOD pin from SJA1110 HARD RESET pin, i have no issues and PMIC start successfully together with SJA1110. Is there the possibility that LDO2 goes in instability due to high output load current and never recovers? OTP program is to autoretry every 4s but VR5510 never retry. Thank you enrov Power solution Re: VR5510 BUCKx electrical specification and LDO2 instability Hello Enrico, Thank you for your question regarding the VR5510.   The BUCKx output ripple specification for VR5510 is peak-to-peak 1%.   Could you please confirm which VR5510 part numbers you are using? If VMONx is not used for LDO2 voltage monitoring, PGOOD cannot be asserted in case of LDO2 overvoltage (OV). Please note that VR5510 does not have internal voltage monitors for LDO rails.    Does this issue occur on all modules or only on a specific one? If it can be reproduced across all modules, I recommend following up on this with the SJA1110 engineer to check if the issue can also be reproduced on the SJA1110 EVB. If LDO2 is operating in an overloaded state, the expected fault would be UV (undervoltage), not OV (overvoltage). As a troubleshooting step, please disconnect the LDO2 load and check if the device powers up normally. Additionally, I suggest measuring the impedance of the LDO2 and VPRE network to ensure they are within normal range.   BRs, Tomas Re: VR5510 BUCKx electrical specification and LDO2 instability Hello Tomas thank you for your reply. Going deeper in analysis seems that LDO2 is driven by outside uncontrolled voltage that rise from 1.8 to 2.2. Due to the fact that I am monitoring LDO2 with VREF, PGOOD is not asserted ever. The problem seems to be at SJA side, my only curiosity is to understand if LDO2 can be unstable and if, it can forward the input voltage to output. I agree about the point where you say that an overload is related to an UV, but I do not see UVs. Just for sharing: VR5510 ( I'm using AMMA0 and AMBA0 versions) seems not to be the source of the problem. But any advise on stability of LDOs and instability behavior is well accepted. Regards Re: VR5510 BUCKx electrical specification and LDO2 instability Hello Enrico, If the external components for the LDO regulator are within the specified range, there should be no risk of instability. We generally believe that the input of an LDO cannot be directly forwarded to the output, unless the LDO is specifically configured in load switch mode. BRs, Tomas Re: VR5510 BUCKx electrical specification and LDO2 instability Hello Tomas, ok thank you.  Just to close the topic of LDOs, for VR5510 is there any possibility to parallel LDO2 and LDO3 (that are the same hw seems) with external ballast resistor just to let them share a current that can be slightly over the maximum of 400mA (transitory), to keep the voltage within range? Or, can you tell me if the three BUCKs converter can be used as alternative to LDOs for analog application where noise is important? (this is because i asked the expected output voltage ripple). I'm starting a new application where I would like to use VR5510 to supply some high-speed ADCs and opamps (tens of MHz range of application). Thank you Enrico Re: VR5510 BUCKx electrical specification and LDO2 instability Hello Enrico, LDO2 and LDO3 on VR5510 cannot be used in parallel. In general, BUCKx outputs are not recommended as a direct ADC reference. We recommend adding an external LDO after BUCKx for this purpose. BRs, Tomas

NETC 驱动程序代码审查：同步障碍 1.在 NETC 驱动程序中，"MCAL_INSTRUCTION_SYNC_BARRIER() "不应该是必须的。它会降低性能，可以将其删除。根据我的理解，如果不动态更改指令序列，就不需要刷新指令 FIFO (isync)。如果我说错了，请帮忙仔细检查。 例如，在 Netc_Eth_Ip_SendFrame() 中，关于下面的代码，对于存储指令，投机不会执行，为什么我们需要这个障碍？ /* 启用开发错误时，我们需要先添加一个障碍，以避免在前一个 else if 条件完成之前发生投机性检测。 在前一个 else if 条件完成之前，我们需要先添加一个障碍。*/ mcal_instruction_sync_barrier()； mcal_data_sync_barrier()； 2. 需要对 "MCAL_DATA_SYNC_BARRIER() "中的某些内容进行审查。其中部分似乎不一定（如上），部分需要调整。例如，在 Netc_Eth_Ip_SendFrame()中，关于下面的代码，"MCAL_DATA_SYNC_BARRIER() "应移到缓存操作之后，TBPIR 寄存器之前。 /* BD 在内存中的写入已被优化，因此在开始传输前需要进行同步处理。 以确保在内存中正确写入传输 BD。*/ mcal_data_sync_barrier()；   RTD Re: NETC driver code review: sync barrier 关于"变量 LockTxBufferDes 已更改" ，正如我在问题中所述，任何投机执行都不会导致内存存储动作损坏，因为内存存储动作不会被撤销。请仔细检查投机概念。 Re: NETC driver code review: sync barrier 您好， 我知道在更改全局变量之前会添加障碍命令，以避免对其他变量造成影响。例如：在函数 SendFrame 中使用以下代码： 如果没有屏障命令，在"之前，如果" 条件完全解决，就会执行推测执行。如果出现 NextProducerIndex = LastTxdata 的情况，说明队列已空或已满，但 CPU 预测错误，因此设置变量 LockTxBufferDes = TRUE。在"if" 条件结束后，CPU 发现错误并返回，但变量 LockTxBufferDes 发生了变化。该变量的序列为：发送前，LockTxBufferDes = LOCKED；在 ReportTransmission 中处理后，LockTxBufferDes = UNLOCKED。这导致一个缓冲区被忽略使用。 对于此命令： 这与 RM 中的说明有关： 添加障碍是为了确保 TxBD 在以下命令开始之前同步到内存： 顺祝商祺！ Nhi Re: NETC driver code review: sync barrier 您好， 我的回答如下： 我对此没有更多了解，因此我创建了票据 ARTDCC1-640，您可以通过该票据从 SW 团队获得解释。 顺祝商祺！ Nhi Re: NETC driver code review: sync barrier 这张截图来自哪里？截图中没有显示的来源和背景是什么？ Re: NETC driver code review: sync barrier 是的，我通过人工智能工具找到了这个。是科迪。 Re: NETC driver code review: sync barrier 该截图没有 URL 可以查询，是人工智能生成的文本，这种说法对吗？如果是，是哪个人工智能；如果不是，这是从哪里来的？ Re: NETC driver code review: sync barrier 您好， 我刚刚找到它，虽然不是官方文档，但我认为这可能是 SW 添加该命令的原因。我不知道，也许我的想法是错的，他们有其他原因。SW 团队将在上述票据中给予答复。 顺祝商祺！ Nhi Re: NETC driver code review: sync barrier 好吧，这又是一个人工智能工具以非常漂亮的措辞提供根本不正确信息的案例。