Multi Source Translation Content

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Multi Source Translation Content

讨论

排序依据:
MPC8308VMAGDA こんにちは、チーム LTB後も製品は継続されますか? 製造番号: MPC8308VMAGDA DC: 2505 MCX C Re: MPC8308VMAGDA 最終配達日: 2024 年 6 月 30 日。2025年のチップは不可能だ。 あるいは、 www.aceicc.comにアクセスしてアドバイスを求めることもできます。私は前回、彼らから良い回答を受け取りました。
查看全文
How to add the PFE driver to the BSP of S32G274A Dear experts,   I am compiling the Linux BSP according to section 3.1.2 of the manual S32G2_LinuxBSP_44.0_User_Manual. Currently, the compilation environment has been properly configured and the compilation has been completed successfully. However, after burning the compiled image file to the SD card and booting it up, there is no PFE firmware file in the FAT32 partition of the SD card. In addition, the pfe network interface is not displayed when running the ifconfig command after the image is booted.   Could you please advise on how to compile the PFE driver into the Linux BSP? Also, could you provide any relevant manuals? Re: How to add the PFE driver to the BSP of S32G274A hi,waitewang Please try to refer to the 7.3.4 Build by Auto Linux BSP of S32G2_LinuxBSP_44.0_User_Manual.pdf as the following picture. BR Joey Re: How to add the PFE driver to the BSP of S32G274A Dear experts, With your assistance, I can now compile the PFE driver into the BSP image file and have verified its functionality on the development board. I would like to consult you further on one question: how can I locate the corresponding PFE driver code? I have found some PFE-related code snippets via global search, but I cannot confirm their validity. My ultimate goal is to port the PFE driver code to other operating systems, so my first step is to identify the configuration process of the PFE module clock. If it is success, I will port the function code step by step. thanks very much! Re: How to add the PFE driver to the BSP of S32G274A Hi, Waitewang. Try visiting the link below: S32G2 Secure and Reliable Automotive Network Processor | NXP Semiconductors BR Joey. Re: How to add the PFE driver to the BSP of S32G274A Hi Joey         I tried to modify the code under this directory—such as altering existing print statements or adding new ones—but after recompiling with bitbake, there were no changes at all; the print output remained the same. Could it be that I’m looking in the wrong directory?
查看全文
i.MX6x ENETは、一時停止フレームを受信するとENETx_RCR[FCE]がクリアされ、予期せず転送を中断します。 こんにちは。イーサネットのポーズ フレーム機能に関する問題が発生しています。ポーズ フレームを受信したときに ENET がデータを送信し続けるようにしたいので、「22.6.4.7 ポーズ フレームの終了」と i.MX6x UM の FCE ビット定義に従って、ENETx_RCR[FCE] ビットをクリアしてフロー制御機能を無効にしましたが、FCE がクリアされているかどうかに違いはないようです。有効なポーズ フレームを受信すると、ENET MAC は送信を一時停止します。 また、同じ PHY、同じ設定、同じテスト ツールと操作手順で他の SOC (xilinx Zynq など) をテストしたところ、動作しました。 SO テストの前に実行する必要がある追加の構成手順はありますか? Re: i.MX6x ENET suspends transfer unexpectedly with ENETx_RCR[FCE] cleared when pause frame receive こんにちは、ジョセフさん。ご返信ありがとうございます。 「ethtool -A eth0 autoneg off rx off tx off」が /etc/network/インターフェース に追加され、eth0 が起動するたびに自動的に呼び出されるようになりました。 ethtool クエリの結果は次のようになります。 # # # ethtool -a eth0 eth0 の一時停止パラメータ: 自動ネゴシエーション: オフ RX: オフ TX: オフ 件 ENET_RCR: # # # デバイスメモリ 0x020B4084 32 0x45F20104 # ethtool eth0 eth0の設定: サポートされているポート: [ TP MII ] サポートされているリンクモード: 10baseT/Half 10baseT/Full 100baseT/ハーフ 100baseT/フル サポートされている一時停止フレームの使用: いいえ 自動ネゴシエーションをサポート: はい サポートされているFECモード: 報告なし アドバタイズされたリンクモード: 10baseT/Half 10baseT/Full 100baseT/ハーフ 10baseT/フル 宣伝されている一時停止フレームの使用: いいえ 宣伝されている自動ネゴシエーション: いいえ 宣伝されているFECモード: 報告なし リンクパートナーがアドバタイズするリンクモード: 10baseT/Half 10baseT/Full 100baseT/ハーフ 10baseT/フル リンクパートナーが通知する一時停止フレームの使用: 対称受信のみ リンクパートナーがアドバタイズした自動ネゴシエーション: はい リンクパートナーがアドバタイズしたFECモード: 報告なし 速度: 100Mb/s デュプレックス:フル ポート: MII PHYAD: 5 トランシーバ: 外部 自動ネゴシエーション: オン ウェイクオンをサポート: g ウェイクオン: d リンクが検出されました: はい # Re: i.MX6x ENET suspends transfer unexpectedly with ENETx_RCR[FCE] cleared when pause frame receive こんにちは、 NXP Semiconductors製品にご興味をお持ちいただきありがとうございます。 次のコマンドを試してください: ethtool -A eth0 受信オフ 送信オフ また、一時停止オプションを印刷してから、もう一度試してください。 よろしくお願いします。
查看全文
LPC5536 HSCMP dont work Hello everyone, We are using the HSCMP peripheral of the LPC5536 primarily to monitor a slow voltage. We configured HSCMP2 for "Nano Power Comparison," along with the DAC sub-module. However, we are experiencing instability with the output of HSCMP2, which oscillates. The duty cycle of the oscillation appears to depend on the voltage of the negative input, leading me to suspect that the positive input—the DAC signal—is not stable. When changing the power mode to "Low Speed Comparison," the oscillation issue is resolved. Additionally, my colleague has encountered similar problems with HSCMP0 and HSCMP1. He requires switching to "High Speed" mode for stable operation, but another PCB does not function properly with this setting. Has anyone else faced similar issues? Is there a reliability concern with the internal HSCMP? What steps can we take to achieve stability? Thank you for your input! Re: LPC5536 HSCMP dont work Hi,   it happens with 3 out of 3 devices on Rev. 1B Chip.  I compare a DC voltage with 8bit DAC (11/256 VCC (3.5V)) ~150mV. It triggered just an error flag in Application. I also checked it with Lab supply as input voltage. It always oscillate in Nano power mode changing the mode to a higher level will fix it.  Re: LPC5536 HSCMP dont work Hello @nobodyKnows, In order to support you better, could you provide me more details about when the oscillation occurs? For example: -Which signals are you comparing? -Does it happen in 100% of the cases? -Do you perform any specific actions in your code when it occurs? Additionally, I highly recommend reviewing these two application notes (AN13540 and AN13714), which provide detailed explanations of the HSCMP and may be helpful. BR Habib Re: LPC5536 HSCMP dont work Hello @nobodyKnows, I am investigating into this further, in the meantime. Could you provide me the error flag that you mentioned? BR Habib Re: LPC5536 HSCMP dont work it is really nothing special. I just test for COUT in CSR Register and set a Errorflag in my application.  if(HSCMP2->CSR & HSCMP_CSR_COUT_MASK){ errorFlg = 1; } Re: LPC5536 HSCMP dont work Hello @nobodyKnows, It is expected that, in low‑power modes, the overall performance and responsiveness of the peripheral will be reduced.  For example, for the HSCMP, in low‑power comparator mode the propagation delay can increase by up to a factor of 60 compared to the high‑speed mode, as shown in Table 49 of the datasheet. For this reason, you observe reduced performance across the different power modes. BR Habib Re: LPC5536 HSCMP dont work Hello, I currently have another device where the HSCMP2 peripheral is not functioning. I have two identical devices on my table with the same firmware, one of which works and the other does not. To facilitate testing, I connected my laboratory power supply to the positive input of the CMP, allowing me to easily adjust the voltage. I am comparing the output at 163 mV generated with the DAC sub-module, which creates the reference voltage at the negative input from the 3.5 V supply. The output of the CMP is inverted. The working device sets the HSCMP_CSR_COUT bit when the voltage is below 160 mV; otherwise, the bit is 0. The non-functioning device sets the HSCMP_CSR_COUT bit below 210 mV and above 780 mV; in between, it remains 0. I directly readout the status with debugger. What I would also like to mention is that in the datasheet, the bit fields INPSEL (bits 29-28) and INPSEL (bits 25-24) in the CCR2 register cannot be written to and are always read back as 0. I think that the fields do not exist and that only MSEL and PSEL are used for the input mux. Is anyone else experiencing a similar problem? Is there a workaround? I'm starting to have a very, very bad feeling about using this mcu in mass-produced devices. Best regards, nobodyKnows Re: LPC5536 HSCMP dont work Hello, next device with defect on HSCMP2. Now it faulty triggers ~10sec after init and a false trigger above 2,9V.  Can I assume that I will receive help here, or do I need to open a ticket regarding this matter? Re: LPC5536 HSCMP dont work Hi @nobodyKnows, I apologize for the delayed response. Since the issue is different to the original question, could you please open a ticket of this matter? This also help to bring a better personal support. Inside this new ticket, could you please provide the next information? -The detailed steps you followed when the issue occurred. -If you are able to reproduce this issue on any of our EVKs. -To verify whether the issue follows the MCU, could you swap the MCU that is presenting the problem onto a board that is not showing the issue, and share the results? You can open a support ticket on this page. BR Habib
查看全文
我需要测试时间敏感网络 我需要在 s32g3 上测试时间敏感网络,IEEE 802.1AS、802.1Qbv 和 802.1Qbu。我应该订购参考设计板 (RDB3) 还是评估板 (EVB3)。 Re: I need to test Time sensitive networking @chenyin_h 可供下载的 BSP 附带了 EVB3 的设备树,我如何获得 RDB3 设备树的 BSP。 Re: I need to test Time sensitive networking 你好,@disrupt-user01 不客气。 如果有任何与 S32G 相关的其他问题,欢迎在这个 S32G 板上发布新话题,我们很乐意提供支持。 BR 切宁 Re: I need to test Time sensitive networking 感谢您的反馈, Re: I need to test Time sensitive networking 你好,@disrupt-user01 谢谢您的帖子。 也许您可以试试 RDB3,因为 sja1110 集成了更多功能。 BR 切宁 BR 切宁 Re: I need to test Time sensitive networking 你好,@disrupt-user01 感谢您的回复。 你是如何下载的电路板支持包镜像的?应包含支持 RDB3 和 EVB3 的所有图像 我建议通过以下链接下载: https://www.nxp.com/app-autopackagemgr/automotive-software-package-manager:AUTO-SW-PACKAGE-MANAGER BR 切宁
查看全文
LVDSバッファ/スプリッタ こんにちは、 私はプロセッサインターフェースを持っており、そこからLCDを接続するための直接LVDSインターフェースを取得しています。これはLCDで問題なく動作します。 LVDS_CLK_P LVDS_CLK_N LVDS_D0_P LVDS_D0_N LVDS_D1_P LVDS_D1_N LVDS_D2_P LVDS_D2_N LVDS_D3_P LVDS_D3_N 今、同じインターフェースで並列ディスプレイを作成したいのですが、要件を満たすドライバー IC はありますか? そのCASE、どのように接続すればよいのでしょうか? 1024 * 768 XGA モード、または 1280 * 800 または 1366 x 768 (HD) 解像度をサポートしますか? Re: LVDS buffer/splitter こんにちは、 そのソリューション用のブリッジやリファレンス デザインはありません。 マーケットには目的にかなう製品がいくつかあるはずですが、私たちは特定の製品を他よりもお勧めするわけではありません。 すでにご興味をお持ちいただける製品をいくつかご用意しております。 LVDS 側には、jdi,tx26d202vm0bwa を使用する jdi wuxga lvds パネルがあります。 よろしくお願いいたします。 Re: LVDS buffer/splitter クロスポイントスイッチ/ブリッジソリューションはありませんか? オープンソース/サードパーティのソリューションを提案していただければ、非常に助かります。
查看全文
用于闪存阵列完整性检查的离线 MISR 签名计算 我正在 S32K311 控制器上实施闪存阵列完整性检查。我的目标是为生成的 .bin 文件离线计算 MISR 签名值。文件,并将其存储在 NVM 中进行比较。   我尝试从 .bin 文件中计算 MISR 值。使用参考手册中描述的方法进行归档;但是,结果与 UM0-UM9 寄存器中观察到的值不匹配。请提供一个简单的 C 代码公式,以便从 .bin 文件中读取数据。文件并生成特定内存段的 MISR 值?   此外,我希望澄清 MISR[288] 位的作用,因为它的功能目前还不清楚。     顺祝商祺!   桑迪普-辛格 Re: offline MISR signature calculation for Flash Array Integrity Check 你好,我是@sandeepSingh18606、 让我看看我们是否有解决办法。 MISR 为 288 位宽,以 UM0-UM9 方式实现,MISR[288] 仅为 MSB。 此致, 丹尼尔 Re: offline MISR signature calculation for Flash Array Integrity Check 你好@sandeepSingh18606、 感谢您的耐心等待。我想告诉您,目前还没有针对该功能的离线解决方案。 不过,我们已向我们的软件工具团队提出申请,要求他们审查开发这种选项的可能性。评估工作仍在进行中,我们尚未得出结论,也没有可能的解决方案的时间表。 此致, 丹尼尔
查看全文
[ls1046ardb] Exchange DDR4 DIMM to other DIMM(2GB), then boot failed. I exchanged DDR4 DIMM with other DIMM. (This DIMM can be used general Ubuntu-PC, and it can pass memtest86) Then boot sequence failed with following error message. ERROR:   Board parameters no match. ERROR:   Failed matching board timing.   In cal_board_params() function, I found pdimm->rc value was 0x01, then modified following parameter. static const struct rc_timing rce[] = { {U(1600), U(8), U(7)}, {U(1867), U(8), U(7)}, {U(2134), U(8), U(9)}, {} }; static const struct board_timing udimm[] = { {U(0x01), rce, U(0x01020304), U(0x06070805)}, // add this line {U(0x04), rce, U(0x01020304), U(0x06070805)}, {U(0x1f), rce, U(0x01020304), U(0x06070805)}, };     However boot sequence failed. It seems that BL31 cannot be booted, and failed. NOTICE:  BL2: Booting BL31 INFO:    Entry point address = 0xfbe00000 INFO:    SPSR = 0x3cd // no more logs..   I think that rce and udimm parameters should be configured using QCVS(CodeWarrior), but I got following error. Create new "QorIQ Configuration Project" Select "DDR Memory Controller Configuration" Select "From memory file", choose SPD binary file as "Input file" "Import" button Error message "Please check the value of DDR data rate in import file!" is shown.   Is my approach correct? How to create correct parameters by QCVS? Re: [ls1046ardb] Exchange DDR4 DIMM to other DIMM(2GB), then boot failed. You need to use QCVS DDRv tool to connect to the custom board to do validation and optimization to get optimized DDR initialization parameters and used them in ATF software. Please refer to DDRv user manual https://www.nxp.com/docs/en/user-guide/QCVS_DDR_User_Guide.pdf The customer needs to create a DDR QCVS project according to the custom board. If DIMM is used on the customer’s board, there is SPD on the target, please select “Read SPD” in DDR configuration panel when create QCVS DDR project. Then use QCVS DDRv tool to connect to the target board to do further optimization and validation. After successful validation, please click Project->Generate Processor Expert Code to get the optimized DDR controller configuration parameters in file ddr_init1.c, and use it to modify ATF source code plat/nxp/soc-ls1046a/ls1046ardb/ddr_init.c. Re: [ls1046ardb] Exchange DDR4 DIMM to other DIMM(2GB), then boot failed. Thank you for comment. I might have misunderstood.. Can't QCVS read 512-byte SPD binary file? Not from SPD in DDR DIMM. I don't have JTAG hardware now. Best Regards, Narita Re: [ls1046ardb] Exchange DDR4 DIMM to other DIMM(2GB), then boot failed. JTAG hardware is necessary, you need to connect QCVS DDRv tool to the target board to do optimization and validation through JTAG to get the optimization parameters. Re: [ls1046ardb] Exchange DDR4 DIMM to other DIMM(2GB), then boot failed. Thank you. I'll get CodeWarrior TAP and try as your comment. Best Regards, Narita
查看全文
S32DSライセンスが消える S32DS ライセンスが失われ、アクティベーションが必要ですが、古いアクティベーション コードは無効です。これをどう解決すればいいでしょうか? Re: S32DS licence disappear このページと私のプロフィールのライセンスステータスを参照してください。 Re: S32DS licence disappear 、ds 3.5、私のライセンスステータス。 Re: S32DS licence disappear こんにちは、 インストールしようとしている S32DS のバージョンを共有していただけますか? よろしくお願いいたします。 ピーター Re: S32DS licence disappear Ds 3.5 Re: S32DS licence disappear プロフィールにライセンスアクティベーションコードがありません。確認してください。 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 こんにちは、 この問題はまだ有効ですか、それとも実行できましたか? よろしくお願いいたします。 ピーター
查看全文
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
查看全文
S32DS licence disappear The S32DS licence is lost and needs activation, but the old activation code is invalid. How can this be resolved? Re: S32DS licence disappear please ref this page and my profile licenses status. Re: S32DS licence disappear ,ds 3.5  , my license status.  Re: S32DS licence disappear Hello, Could you please share version of S32DS you are trying to install? Best regards, Peter Re: S32DS licence disappear Ds 3.5 Re: S32DS licence disappear I have no license activate code in my profile, please check. Re: S32DS licence disappear i've used other activate valid code ,also display that errorr . please ref my other response. @jiri_kral @petervlna  Re: S32DS licence disappear yes, i'v tried .  result and other info , please ref my other reponse .  i can't find my license .  @jiri_kral  Re: S32DS licence disappear Hi,  I checked your account and your license is valid. Did you tried offline activation? https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Activate-S32-Design-Studio/ta-p/1128340 Re: S32DS licence disappear Hello, Is this issue still valid, or did you manage to get it run? Best regards, Peter
查看全文
iMX8QM 上的 Jailhouse,使用 lf-6.6.52_2.2.0 您好,NXP团队: 在 i.MX Linux 版本说明 RN00210,修订版 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 一致 。 不过,在监狱源代码中有 imx8qm SoC 的代码(https://github.com/nxp-imx/imx-jailhouse/tree/lf-6.6.52_2.2.0/configs/arm64).看来 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、 感谢您联系恩智浦支持中心! 根据 UG10170,我们当前的 BSP 中该处理器未正式支持监狱功能。 官方支持的处理器有 i.MX 8M 系列 i.MX 8M Mini LPDDR4 EVKB i.MX 8M Nano 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 顺祝商祺! 查维拉
查看全文
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 よろしくお願いいたします。 チャビラ
查看全文
CodeWarrior の LS1046ARDB ベアメタルフラッシュ LS1046ARDB をベースにしたカスタム ボードの最初のフラッシュを実行する方法を模倣しようとしています。当社のカスタム ボードでは、ボードの初回電源投入時に eMMC と QSPI のみが使用されます。まず eMMC をフラッシュしたいと思います。AN5184.pdfの指示と「LS1046A-1.pdfを起動する」に従ってemmc_clone.binファイルを作成しました。CodeWarrior からフラッシュする方法について説明します。CodeWarrior Tap が動作しており、サーバーに接続できることを確認しました。ただし、Flash Programmer を使用すると、常に eMMC との通信に関するエラーが返されます。LS1046A_RDB*.tccにはさらに変更が必要なようです(ターゲット初期化ファイル) を使用して eMMC を有効にしますか?リセット セクションの下に、QSPI を有効にする行があります。 TA.rcw.set_data({13:0x20124000}) eMMC を有効にするには別の行が必要だと思いますか?しかし、それは何でしょうか?他に何かする必要があるでしょうか? Re: LS1046ARDB Bare Metal Flash from CodeWarrior 「ターゲット初期化ファイル」の内容をls1046ardb.py_2100&1600_pass.txtに置き換えます。 LS1046ARDB 上の eMMC をプログラムすることができ、LS1046ARDB を eMMC から起動することができました。 LS1046ARDB には1 つの MUX 制御信号SD_eMMC_SELがありますが、これは SD カードが挿入されているかどうかによって決まります。 eMMC を使用する場合は、SD カードを挿入しないでください。 Re: LS1046ARDB Bare Metal Flash from CodeWarrior さらに詳しい情報を次に示します... SD カードの読み取り/消去/フラッシュは問題なく行えますが、eMMC が応答しないようです。SD カードが取り外され、ジャンパーがまだ SD/eMMC から起動するように設定されているため、eMMC にアクセスできません。CPLD が SD から eMMC に切り替わっていないようです。eMMC は空 (プログラムされていない) なので、電源を入れても SD カードが挿入されていない場合は、コンソールのプリントなどは表示されません。ここで CodeWarrior を起動し、Tap に接続して eMMC のプログラムを試みます。しかし、試してみるとエラーばかりです。CPLD が問題であるのではないかと考え始めています。 Re: LS1046ARDB Bare Metal Flash from CodeWarrior ファイルを試しましたが、USE_SAFE_RCE = True にしないとエラーが発生します。消去とプログラムではエラーは返されませんが、それでも起動できません。 Re: LS1046ARDB Bare Metal Flash from CodeWarrior USE_SAFE_RC W = Trueの場合、それが私があなたに送信した元のものです。 txt の初期化はハードコード RCW ( USE_SAFE_RC W = True ) ごとに調整されるためです。 独自のRCWを使用する場合は、初期化を変更してください。 Re: LS1046ARDB Bare Metal Flash from CodeWarrior これは次のことに関連しているので閉じておきます: https://community.nxp.com/t5/CodeWarrior-Development-Tools/eMMC-on-LS1046ARDB/mp/2298628/highlight/false#M9358
查看全文
LS1046ARDB Bare Metal Flash from CodeWarrior I'm trying to mimic how we will be performing the first flash of our custom board based on the LS1046ARDB.  On our custom board we only have eMMC and QSPI when first powering on the board.  We would like to flash the eMMC first.  I have built an emmc_clone.bin file based on the AN5184.pdf instructions and also following the "Bring up the LS1046A-1.pdf" on how to flash from CodeWarrior.  I have verified that the CodeWarrior Tap is working and I can connect to the server.  However, when I use the Flash Programmer it always returns an error about communication with eMMC.  It seems there are more modifications needed to the LS1046A_RDB*.tcc (Target Initialization File) to enable the eMMC?  I see a line under the Reset section to enable the QSPI: TA.rcw.set_data({13: 0x20124000}) I assume another line is needed to enable the eMMC?  But what would that be?  Is there anything else I need to do? Re: LS1046ARDB Bare Metal Flash from CodeWarrior Replace the "Target Initialization File" content with the ls1046ardb.py_2100&1600_pass.txt. I could program the eMMC on the LS1046ARDB and the LS1046ARDB could bring up from the eMMC. There is one mux control signal SD_eMMC_SEL on the LS1046ARDB, but it's decided by whether inserting SD card or not. When you use the eMMC, please kindly don't insert SD card.  Re: LS1046ARDB Bare Metal Flash from CodeWarrior Here is some more information... I'm able to read/erase/flash the SD card without issue but the eMMC doesn't seem to respond.  With the SD card removed and the jumpers still set to boot from SD/eMMC I don't have access to the eMMC.  It appears that the CPLD is not switching from the SD to eMMC.  The eMMC is blank (never been programmed) so when powering it on and no SD card is in there are no console prints or anything.  This is where I start CodeWarrior and connect to the Tap to try and program the eMMC.  But nothing but errors when trying.  I'm starting to think that the CPLD is the problem.  Re: LS1046ARDB Bare Metal Flash from CodeWarrior Tried the file however I get errors unless I USE_SAFE_RCE = True.  Erase and Program returns no errors however still can't boot.  Re: LS1046ARDB Bare Metal Flash from CodeWarrior When the USE_SAFE_RCW = True, that is the original one I sent it to you. Because the initialization of the txt is adjusted per the hard-code RCW(USE_SAFE_RCW = True). If you use your own RCW, please kindly change the initialization. Re: LS1046ARDB Bare Metal Flash from CodeWarrior I'm going to close this one since it is related to: https://community.nxp.com/t5/CodeWarrior-Development-Tools/eMMC-on-LS1046ARDB/m-p/2298628/highlight/false#M9358
查看全文
モーター制御 エントリーレベルのモーター制御プロジェクトを探しています。モーターは マイクロコントローラのコマンドによる、1 アンペア未満の 12V DC モーター。 ランディ Re: motor control こんにちは@randyseedle 、 ご投稿ありがとうございます。 シンプルな 12V ブラシ付き DC モーター (<1A) の場合、Kinetis K02/K20 または KE02/KE04 が最適です。 これらは、PWM (FTM 経由)、GPIO 制御、電流検知用の ADC を提供し、低コストで初心者にも使いやすいです。 こちらからダウンロードした SDK デモを参照できます。 ボードを選択 | MCUXpresso SDKs ビルダー 後で BLDC または FOC 制御を試したい場合は、Kinetis KV シリーズにアップグレードできますが、現在の 12V DC モーターの場合は、K/KE ファミリで十分です。 BR セレステ ------------------------------------------------------------------------------------------------------------------------------- 注: この投稿が質問の答えである場合は、「解決策として承認」ボタンをクリックしてください。ありがとう! ------------------------------------------------------------------------------------------------------------------------------- Re: motor control MCUXpresso SDK Builder はfrdmke02z40m を認識していないようです。もう一度これを見ていただけますか? Re: motor control 問題のボードは見つかりましたが、選択されたミドルウェア オプションで問題が発生しているようです。私は FRDM-k64f を持っており、モーター制御に関連するものを見つけることができましたが、それがあなたが私に指示しようとしていたことと何ら関係があるとは思えません。 ランディ・シードル Re: motor control こんにちは@randyseedle 、 存在することを確認しました。SDK ビルダーは検索時にハイフン (「-」) を含めます。正しい名前はFRDM-KE02Z40Mです。KE02Z40を直接入力して検索することもできます。 お役に立てて、良い一日をお過ごしください。 BR セレステ --------------------------------------------------------------------------------------------------------------------- 注: この投稿が質問の答えである場合は、「解決策として承認」ボタンをクリックしてください。ありがとう! --------------------------------------------------------------------------------------------------------------------- Re: motor control はい、今のところは大丈夫です。ダウンロードできました。SO、ここでのタスクは、ダウンロードした SDK を調査することになります。 何かご提案はございますか? Re: motor control FRDM-KE02Z40M が検出され、選択したミドルウェアがリストされます。SDK をビルドするように指示しましたが、何もビルドされません。 Re: motor control デバイス ドライバがリストされた SDK ビルダーのキャプチャ画像があります。FRDM-KE02Z40M の認識が失われるため、そのポイントに到達することはありません。とにかくそう思います。ADC および GPIO ドライバにアクセスできます。その他はリストに載っていません。ファンキーな行動。 ランディ Re: motor control ビルドとダウンロードは正常にできました。添付の記録ビデオをご覧ください。 Re: motor control 録画した画面は添付ファイルをご参照ください。あなたの意味とは違う意味ですか? Re: motor control 添付の新しいビデオをご覧ください。 それでもこれらのデモが見つからない場合は、MCUXpresso で SDK をアンインストールしてから再インストールしてみてください。 SDK を再インポートした後、MCUXpresso IDE を再起動する必要がある場合があることに注意してください。 ZIP パッケージを MCUXpresso に直接ドラッグ アンド ドロップして SDK をインポートすることもできます。 さらに、SDK パッケージが完全であることを確認するために、SDK Builder から SDK を再度ダウンロードしてみることもできます。 BR セレステ Re: motor control デバイス ドライバ リストにはまだ ftm または tpm がありません。手順を1つずつ書きます。ビデオの再生速度が速すぎます。まだ何か見逃しているかも知れません。
查看全文
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
查看全文
SDK 为 RT685-AUD-EVK 启用 8 通道 DMIC 板 我本来想找一个恩智浦提供的软件开发工具包,用 RT685-AUD-EVK 来设置我的 8 通道 DMIC 板。我想恩智浦应该有一些准备就绪,因为他们出售这两款设备。如果有人能为我指点迷津,将不胜感激。谢谢! Re: SDK to enable 8ch DMIC Board for RT685-AUD-EVK 你好, 我正在尝试使用 8-DMIC 阵列板在 EVK-MIMXRT685 上运行 dmic_multi_channel CM33 演示。 根据演示文档,在 J31 上启用 8-DMIC 板需要移动多个电阻器(例如R379、R380、R384、R389、R390、R391、R392 至 2-3)。完成此操作后,FlexSPI 八进制闪存 (U19) 变得无法访问: -LinkServer 闪存失败 -ROM ISP (blhost) 已连接,但是 FLEX-SPI-或非 显示扇区大小 = 0 /页面大小 = 0 -无法擦除/写入闪存 我的问题: 这个演示是否有望在没有八进制闪存(仅限 RAM 的工作流程)的情况下运行? 更换电阻器后是否有官方的闪存/启动程序? 是否所有电阻器都需要更改,还是某些电阻器可以保持默认状态以保证 FlexSPI 闪存工作? 现在看来所需的DMIC硬件设置会阻止正常的闪存编程/启动。 感谢您的指导。 Re: SDK to enable 8ch DMIC Board for RT685-AUD-EVK 您好, 我认为将多个 DMIC 中的 PCM 采样放到 USB 负载中是可以的,因为 DMIC 和 USB 都是流,要注意同步问题。 BR 荣向军 Re: SDK to enable 8ch DMIC Board for RT685-AUD-EVK @xiangjun_rong 谢谢你我成功地用这个 SDK 听了 8ch DMIC 板。我的下一个目标是通过 USB 将 8 个通道连接到电脑上。我认为将 DMIC_Multi_Ch 和 USB_Device_Composite_Audio_Multi_Ch 结合起来会很有效,您对如何结合这两个软件包有什么指导意见吗?或者,是否已经有一款软件可以做到这一点,而我却忽略了? Re: SDK to enable 8ch DMIC Board for RT685-AUD-EVK 谢谢你,我可以用 DMIC 驱动程序示例来监听麦克风了。我的下一个目标是将 dmic 的 8 个通道接入电脑,我认为将 dmic_multi_channel 与 usb_device_composite_audio_multi_ch 结合起来会很有效。您对如何合并这两个 sdk 有什么指导意见吗? @xiangjun_rong Re: SDK to enable 8ch DMIC Board for RT685-AUD-EVK 您好, 遗憾的是,没有基于 AUD-EVK 的示例,所有示例都基于 MIMXRT685-EVK。由于引脚具有多重功能,因此电阻用于切换功能。因此,不要关心电阻器,只检查引脚是否连接到 DMIC 设备即可。 希望对您有所帮助 BR 荣向军 Re: SDK to enable 8ch DMIC Board for RT685-AUD-EVK 谢谢。read_me 中的说明是针对 MIMXRT685-EVK 的,包括移动电阻器和重新焊接。有人使用过 AUD-EVK 的 SDK 吗?我不想听错板的指令然后发现我不应该移动它们... Re: SDK to enable 8ch DMIC Board for RT685-AUD-EVK 您好, 有 DMIC 驱动程序示例作为 i.mxrt600 系列的屏幕截图,请尝试使用它。 希望对您有所帮助 BR 荣向军
查看全文
Fedora 41 上的 GUI Guider 身份验证窗口焦点问题 - 窗口保持模态并导致崩溃 说明: 我在 Fedora 41 上的 GUI Guider 遇到了一个关键问题,即身份验证成功后,身份验证窗口拒绝关闭,导致应用程序崩溃。 环境: 操作系统:Fedora 41 工作站 桌面环境:GNOME (Wayland/X11) GUI Guider 版本:1.10.0 和 1.10.1 以前的工作配置:同样的设置完美运行了几个星期,直到今天早上 症状 GUI Guider 正常启动并显示身份验证窗口 在输入有效凭据并成功进行身份验证后,身份验证窗口将保持打开 状态。身份验证窗口捕获并保持输入焦点,防止与 GUI Guider 主窗口(如果它打开)交互 尝试关闭身份验证窗口(单击 X 按钮)会关闭整个应用程序,而不仅仅是模态对话框 。GUI Guider 主窗口可能在后台可见,但由于模态身份验证窗口被阻塞而无法访问焦点 可重复性:自今天上午以来的每次上市均可实现 100% 的可重复性。这个问题是在我没有进行任何系统更新或配置更改的情况下突然出现的。 由于这完全阻碍了我的开发工作流程,如果能提供任何帮助或指导,将不胜感激。 Re: GUI Guider authentication window focus issue on Fedora 41 - window remains modal and causes cras 你好,@PBouchand、 正如 GUI Guider 产品页面的系统要求中所述,支持的操作系统是 Windows 11(64 位)、Ubuntu 24.04 或 macOS 11.6。我们不对不同的发行版进行测试,这就是为什么我们无法保证 Fedora 上的 Ubuntu 版本的 GUI Guider 能够完全正常运行的原因。话虽如此,由于你的计算机上安装的 GUI Guider 没有任何变化,我会尝试看看底层软件是否有变化,比如操作系统本身。 BR, Edwin. Re: GUI Guider authentication window focus issue on Fedora 41 - window remains modal and causes cras 你好 我用 Ubuntu 22.04 试过,也遇到了同样的问题。 我还没有尝试过 Ubuntu 24。 请注意,删除 .config/gui-guider、重新启动、不接受或拒绝 cookies 的身份验证是一种变通方法。 祝您愉快 帕特里斯
查看全文
Periodic ADC sampling + DMA with MIMXRT533 I am using the MIMXRT533 in an application where I need to sample a signal periodically with the ADC and move that data into a buffer. I need this all to be done deterministically and without CPU intervention. Once the buffer is full I intend to trigger an interrupt to stop the ADC sampling, process the data, and prepare for the next acquisition. My current approach is as follows: SCTimer generates a 50 kHz signal on SCT0_OUT4. SCT0_OUT4 triggers the ADC to complete a conversion  The ADC FIFO0 watermark is set to 1 and the DMA request is enabled, so once a conversion is complete the DMA is triggered I need 3400 samples, so the DMA is configured with 4 linked descriptors to cover this full amount since we have a max XFERCOUNT of 1024 per descriptor The DMA is configured to accept hardware triggering and peripheral requests are turned off since the ADC does not support peripheral DMA request as per the datasheet. A DMA callback is defined which should stop the SCTimer and reset everything once the DMA reaches the end of the final linked descriptor. Unfortunately, this does not work as expected. I get two ADC samples at each linked descriptor boundary, and zeros everywhere else. Is this because the ADC does not have a traditional DMA request line to pace the transfer? Is there any way to achieve what I am trying to do with the MIMXRT533? I assume there has to be a way to perform periodic sampling without CPU intervention, but I'm a bit stumped as to how to proceed. Any direction would be appreciated. I couldn't find anything similar to what I'm trying to do in the SDK examples. All the ADC examples there were single software triggered samples, no periodic hardware triggering. Re: Periodic ADC sampling + DMA with MIMXRT533 Take a look at this post: https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT685-CTimer0-callBack-delayed/m-p/2259801#M35834 I've do it on a rt685. Regards. Re: Periodic ADC sampling + DMA with MIMXRT533 Hi @katte82, It makes sense that the same issue happens with a similar setup on the RT685, since these two devices use the same modules than the RT533. @npmarshall, could you try adjusting the priorities as mentioned by the linked post? Does this also provide a workaround for your issue? BR, Edwin. Re: Periodic ADC sampling + DMA with MIMXRT533 I actually found a different solution for my application. Since I'm already generating a 50 kHz PWM to trigger the ADC with SCTimer SCT0_OUT4, I added an event to the SCTimer which creates a DMA request at the same time that SCT0_OUT4 goes low. By setting the INPUTMUX to send the SCT DMA request to the DMA trigger input instead of the ADC DMA request, I was able to get the buffer to fill properly with pacing set by the SCTimer instead of the ADC. The other relevant DMA settings are setting HWTRIGEN=1, TRIGTYPE=1 (Level triggering), TRIGPOL=1 (Active high). This way the SCTimer handles both triggering the ADC and telling the DMA to move data out of the FIFO after the ADC has had enough time to complete a sample conversion.
查看全文