Multi Source Translation Content

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

Multi Source Translation Content

ディスカッション

ソート順:
S32K344 Whiteboard Example Project @S32kUser  The S32K344 Whiteboard (S32K344-WB) is a reference design board for providing quick prototype verification, such as Body Domain Control, Gateway, Passive Entry Passive Start (PEPS), Motor Control, and so on. It Based on the 32-bit Arm® Cortex®-M7 S32K3 MCU in a 257 MPABGA package. To help customers get familiar with the hardware quickly, a set of example projects are provided based on the Real-Time Drivers(RTD) provided by NXP. With these example projects, you can have an out-of-box experience with the S32K344-WB reference design. You can get this example package from the attachment on this page. Re: S32K344 Whiteboard Example Project Is there an LLD Driver API? I have searched the website, and the S32DS help content. I cannot find one. There is one for the mcuxpresso drivers, but these are different than what gets generated from RTD libraries with the Eclipse IDE. Re: S32K344 Whiteboard Example Project Hi Stephen, Can you provide an example using half Duplex Lpspi and for Qspi_lp? I would like to see how they are configured and used for the S32K344-WB board.  Preferably for a bare metal application. Thanks!  Re: S32K344 Whiteboard Example Project I mean what are the steps to configure the ethernet example for the S32K344 WB to be client (use the Socket example as Client ).  Thanks in advance . Re: S32K344 Whiteboard Example Project hi, Yomna Due to this is a third-party software (Not sure the license limitation), please download by yourself. I can only to tell you the name which we are using: Wireshark. Re: S32K344 Whiteboard Example Project Hello,  Could you send me an example for client program, such as SocketTest, for the S32K344 WHITEBOARD? Thanks in advance,  Re: S32K344 Whiteboard Example Project I tried to reconfigure the LWIP example to be CLient but i faced this lwip_connect function returns error out of memory and i don't know why this happen so if you have a client example working properly could you you sent it to me Thanks in advance  Re: S32K344 Whiteboard Example Project hi, Mossab The TCP/IP (LWIP) only has the LLD version, it is included in the S32K344_Whiteboard_Example(LLD)_RTM_1.0.0.zip attached in this page, please download and install it (Above this message). Re: S32K344 Whiteboard Example Project Hi,  would you please send me TCP/IP example that compatible with the mentioned board Re: S32K344 Whiteboard Example Project I already checked it and i found the lwip example thank you for your support  I also have another question is this example client or server and what's the configured ip address Re: S32K344 Whiteboard Example Project hi, Yomna The LWIP only has the LLD version, it is included in the S32K344_Whiteboard_Example(LLD)_RTM_1.0.0.zip attached in this page, please download and install it (Above this message). Re: S32K344 Whiteboard Example Project I want LWIP example Re: S32K344 Whiteboard Example Project I checked that again, it seems the issue for the EB. I re-installed it and it's ok now. Projects can be built pass. Re: S32K344 Whiteboard Example Project Thanks for the info! I have build errors when import the examples, shows at: Also, I import the EB project, shows error: Anything else I miss? The S32DS  version: S32 Design Studio for S32 Platform Version: 3.5 Build id: 231128 (Update 😎 Is it ok to compile the examples? Thanks in advance! Gavin Re: S32K344 Whiteboard Example Project We have provided a richer sample project. Please take it if you needed. Re: S32K344 Whiteboard Example Project hi, In the attachment, there is include one IAR example project which located in the IAR folder. You can create your own project based on this example project. Re: S32K344 Whiteboard Example Project I use s32k344 now, and i want to get some IAR project. how to get it? thank you very much! Re: S32K344 Whiteboard Example Project We don't have such complex example project. But I think you can import the modules which you want one by one based on any example project. If you have question during this process, please let me known. Re: S32K344 Whiteboard Example Project Yes, but I need a full mcal eb project which has much more modules inside if You already had one. Re: S32K344 Whiteboard Example Project hi, savantwxj In fact, it is there. Please refer to the "Tresos_Project" folder in each example project. Re: S32K344 Whiteboard Example Project Hi  Would you help provide the mcal eb project of this S32K344 Whiteboard? I will use it as a starting point of my own mcal eb project based on our own HW board. Thanks! Re: S32K344 Whiteboard Example Project To get more Multi-Core example projects, please switch to the page: S32K324 Multi-Core Example Project based on Whiteboard Re: S32K344 Whiteboard Example Project To get more example projects for S32K344-WB, please contact me.
記事全体を表示
T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work Hi,  In our board, T1024 connect to one port of Marvell switch chip by mac to mac. I change uboot code to adapt this, and ping works well in uboot.  I changed the DTS and sdk_dpaa code in kernel. but it dose not work. Now I don't know how to do next step. Could you give me some advices?  the DTS changes:  The bold lines are my changes ethernet@e2000 { /*phy-handle = <0x0>;*/ phy-connection-type = "sgmii";    #status = "enable"; phy_mode = "internal"; fixed-link = <0x0 0x1 1000 0 0>; rcpm-wakeup = <0x9 0x40000000>; cell-index = <0x1>; compatible = "fsl,fman-memac"; reg = <0xe2000 0x1000>; fsl,port-handles = <0xe 0xf>; ptimer-handle = <0xd>; linux,phandle = <0x21>; phandle = <0x21>; }; Re: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work Hi, We ran into the same problem and solved it by modifying the FMAN driver (memac) in the kernel. Even with a fixed-link set in the DTS, you still need to clear the autonegotiation bit when initializing the SerDes lanes, and avoid restarting them afterward. Take a look at SetupSgmiiInternalPhy(). This issue shows up in a MAC-to-MAC setup with no external PHY. In that case, both ends (CPU and L2 switch) must be configured as direct links with no negotiation. Just force the link parameters. https://community.nxp.com/t5/QorIQ/Mac-to-Mac-communication-over-SGMII/m-p/993299 Regards, Bogdan 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work please refer to: https://blog.csdn.net/weixin_41289976/article/details/136476979?spm=1011.2124.3001.6209 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work Can you post the solution for your issue? What changes were needed in your DTS file? 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work please ignore this issue. it has been fixed.
記事全体を表示
T1024,修改设备树以支持 MAC (SGMII) 到 MAC (SGMII),但不起作用 你好、 在我们的板中,T1024 通过 mac 到 mac 连接到 Marvell 交换机芯片的一个端口。我修改了 uboot 代码以适应这一点,ping 在 uboot 中运行良好。 我修改了内核中的 DTS 和 sdk_dpaa 代码。但它不起作用。现在我不知道下一步该怎么做了。您能给我一些建议吗? DTS 更改: 粗体字是我的改动 ethernet@e2000 { /*phy-handle<0x0> =;*/ phy-connection-type =" sgmii "; #status ="enable"; phy_mode ="internal"; fixed-link<0x0 0x1 1000 0 0> =< 0x0 0x1 1000 0 0>; rcpm-wakeup =<0x9 0x40000000> ; cell-index<0x1> =; compatible ="fsl,fman-memac"; reg =;<0xe2000 0x1000> fsl,port-handles<0xe 0xf> <0xd> <0x21> <0x21> =; ptimer-handle =; linux,phandle =; phandle =;}; Re: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work 你好, 我们遇到了同样的问题,通过修改内核中的 FMAN 驱动程序 (memac) 解决了这个问题。即使在 DTS 中设置了固定链路,在初始化 SerDes 通道时仍需清除自动协商位,并避免之后重新启动它们。 请查看 SetupSgmiiInternalPhy().这个问题出现在没有外部 PHY 的 MAC 对 MAC 设置中。在这种情况下,必须将两端(CPU 和 L2 交换机)都配置为无需协商的直接链接。只需强制链接参数。 https://community.nxp.com/t5/QorIQ/Mac-to-Mac-communication-over-SGMII/m-p/993299 谢谢、 博格丹 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work please refer to:https://blog.csdn.net/weixin_41289976/article/details/136476979?spm=1011.2124.3001.6209 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work 您能提供问题的解决方案吗?您的 DTS 文件需要做哪些更改? 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work 请忽略这个问题。已修复。
記事全体を表示
T1024、デバイスツリーを変更してMAC(SGMII)からMAC(SGMII)をサポートするが、動作しない こんにちは、 私たちのボードでは、T1024 は Mac から Mac 経由で Marvell スイッチ チップの 1 つのポートに接続します。これを適応させるために uboot コードを変更すると、 ping は uboot で正常に動作します。カーネル内の DTS および sdk_dpaa コードを変更しました。しかしそれは機能しません。今、次のステップをどうすればよいかわかりません。何かアドバイスをいただけますか? DTSの変更点:太字は私の変更点です イーサネット@e2000 { /*物理ハンドル<0x0> =;*/ phy-connection-type = "sgmii"; #status = "有効"; phy_mode = "内部"; 固定リンク<0x0 0x1 1000 0 0> =; rcpm-wakeup =;<0x9 0x40000000> セルインデックス<0x1> =; 互換性 = "fsl、fman-memac"; <0xe2000 0x1000><0xe 0xf> <0xd> <0x21> レジスタ<0x21> =; fsl、ポートハンドル =; ptimer-handle =; linux、phandle = !; ファンドル = !; }; Re: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work こんにちは、 私たちも同じ問題に遭遇しましたが、カーネル内の FMAN ドライバ (memac) を変更することで解決しました。DTS に固定リンクが設定されている場合でも、SerDes レーンを初期化するときに自動ネゴシエーション ビットをクリアし、その後の再起動を回避する必要があります。 SetupSgmiiInternalPhy() を見てください。この問題は、外部 PHY のない MAC 間セットアップで発生します。そのCASE、両端 (CPU と L2 スイッチ) をネゴシエーションなしの直接リンクとして設定する必要があります。リンクパラメータを強制するだけです。 https://community.nxp.com/t5/QorIQ/Mac-to-Mac-communication-over-SGMII/mp/993299 よろしくお願いいたします。 ボグダン 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work 詳細は以下を参照してください: https://blog.csdn.net/weixin_41289976/article/details/136476979? spm=1011.2124.3001.6209 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work CAN問題の解決策を投稿していただけますか?DTS ファイルにはどのような変更が必要でしたか? 回复: T1024, modify the device tree to support MAC(SGMII) to MAC(SGMII), but not work この問題は無視してください。修正されました。
記事全体を表示
S32K344 ホワイトボードサンプルプロジェクト @S32kユーザー S32K344 ホワイトボード(S32K344-WB) は、ボディ ドメイン コントロール、ゲートウェイ、パッシブ エントリ パッシブ スタート (PEPS)、モータ制御などのプロトタイプの迅速な検証を可能にするリファレンス・デザイン ボードです。これは、257 MPABGA パッケージの 32 ビット Arm ® Cortex ® -M7 S32K3 MCU に基づいています。 お客様がハードウェアにすぐに慣れることができるように、NXP が提供するリアルタイム・ドライバ (RTD)に基づいた一連のサンプル プロジェクトが提供されています。これらのサンプル プロジェクトを使用すると、S32K344-WB リファレンス・デザインをすぐに使える。このサンプル パッケージはこのページの添付ファイルから入手できます。 Re: S32K344 Whiteboard Example Project LLD ドライバ API はありますか?ウェブサイトと S32DS のヘルプ コンテンツを検索しました。見つかりません。 mcuxpresso ドライバ用のものも存在しますが、これは Eclipse IDEs の RTD ライブラリから生成されるものとは異なります。 Re: S32K344 Whiteboard Example Project こんにちは、スティーブン。 半二重 Lpspi と Qspi_lp を使用する例を挙げていただけますか?S32K344-WB ボードでこれらがどのように構成され、使用されるかを確認したいと思います。 ベアメタルアプリケーションに適しています。 ありがとうございます! Re: S32K344 Whiteboard Example Project つまり、S32K344 WB のイーサネット例をクライアントとして構成する手順は何ですか (ソケット例をクライアントとして使用します)。 前もって感謝します 。 Re: S32K344 Whiteboard Example Project こんにちは、ヨムナ サードパーティ製のソフトウェア(ライセンス制限は不明)のため、ご自身でダウンロードしてください。私たちが使用している名前は Wireshark だけです。 Re: S32K344 Whiteboard Example Project こんにちは、 S32K344 ホワイトボード用の SocketTest などのクライアント プログラムの例を送っていただけますか? 前もって感謝します、 Re: S32K344 Whiteboard Example Project LWIPの例をクライアント用に再構成しようとしましたが、lwip_connect関数がメモリ不足のエラーを返しました。なぜこれが起こるのかわかりません。正常に動作するクライアントの例があれば、私に送っていただけますか。 前もって感謝します Re: S32K344 Whiteboard Example Project こんにちは、モサブ TCP/IP (LWIP) には LLD バージョンのみがあり、このページに添付されている S32K344_Whiteboard_Example(LLD)_RTM_1.0.0.zip に含まれていますので、ダウンロードしてインストールしてください (このメッセージの上)。 Re: S32K344 Whiteboard Example Project こんにちは、 上記のボードと互換性のあるTCP/IPの例を送っていただけますか? Re: S32K344 Whiteboard Example Project すでに確認しましたが、lwipの例を見つけました。サポートありがとうございます。 もう一つ質問があります。この例はクライアントですか、それともサーバーですか?また、設定されているIPアドレスは何ですか? Re: S32K344 Whiteboard Example Project こんにちは、ヨムナ LWIP には LLD バージョンのみがあり、このページに添付されている S32K344_Whiteboard_Example(LLD)_RTM_1.0.0.zip に含まれていますので、ダウンロードしてインストールしてください (このメッセージの上)。 Re: S32K344 Whiteboard Example Project LWIPの例が欲しい Re: S32K344 Whiteboard Example Project もう一度確認しましたが、EB の問題のようです。 再インストールしたら大丈夫になりました。プロジェクトはパスしてCAN構築できます。 Re: S32K344 Whiteboard Example Project 情報ありがとうございます! 例をインポートするときにビルド エラーが発生し、次のように表示されます。 また、EB プロジェクトをインポートすると、エラーが表示されます。 他に何か見逃しているものはありますか? S32DS バージョン: S32 プラットフォーム用 S32 デザインスタジオ バージョン: 3.5 ビルドID: 231128 (更新 😎 例をコンパイルしても大丈夫でしょうか? よろしくお願いいたします! Gavin Re: S32K344 Whiteboard Example Project より豊富なサンプル プロジェクトを提供しました。必要であればお持ちください。 Re: S32K344 Whiteboard Example Project こんにちは、 添付ファイルには、IAR フォルダにある 1 つの IAR サンプル プロジェクトが含まれています。このサンプル プロジェクトに基づいて独自のプロジェクトをCAN作成します。 Re: S32K344 Whiteboard Example Project 私は現在 s32k344 を使用しており、いくつかの IAR プロジェクトを入手したいと考えています。 どうやって入手するのですか?どうもありがとうございます! Re: S32K344 Whiteboard Example Project これほど複雑なサンプルプロジェクトはありません。ただし、任意のサンプル プロジェクトに基づいて、必要なモジュールを1つずつインポートCANと思います。このプロセス中に質問がある場合は、お知らせください。 Re: S32K344 Whiteboard Example Project はい、ただし、すでに存在する場合は、内部にさらに多くのモジュールが含まれる完全な mcal eb プロジェクトが必要です。 Re: S32K344 Whiteboard Example Project こんにちは、savantwxjさん。実際、そこにあります。各サンプル プロジェクトの「Tresos_Project」フォルダを参照してください。 Re: S32K344 Whiteboard Example Project こんにちは この S32K344 ホワイトボードの mcal eb プロジェクトの提供に協力していただけませんか?これを、独自の HW ボードに基づいた独自の mcal eb プロジェクトの開始点として使用します。ありがとう! Re: S32K344 Whiteboard Example Project マルチコアのサンプルプロジェクトをもっと入手するには、次のページにスイッチしてください:ホワイトボードに基づく S32K324 マルチコアサンプルプロジェクト Re: S32K344 Whiteboard Example Project S32K344-WB のその他のサンプル プロジェクトを入手するには、私にお問い合わせください。
記事全体を表示
sja1110 の gPTP マスター ポート この疑問は長い間私を悩ませてきました。回答が得られることを期待しています。 大変感謝致します。 S32G-VNP-RDB3とLinuxBSP 43.0を使用しています。 sja1110 をグランド マスターまたはブリッジとして設定すると、マスター ポート (ポート 4) は常に、フォローアップ メッセージなしで同期メッセージのみを送信します。すると、同期メッセージのフラグ フィールドに 2 つのステップが表示されます。なぜフォローアップメッセージが送信されなかったのか分かりません。 スレーブ ポートとしての s32g pfe0 ポートは pdelay req メッセージを送信しますが、マスター ポートとしての sja1110 port4 は pdealy req メッセージに応答せず、qdelay resp メッセージを送信します。 スレーブ ポートとしての s32g pfe0 のコマンドは次のとおりです。 sudo ./ptp4l-i pfe0 -f configs/オートモーティブ-slave.cfg --step_threshold=1 -m ただし、sja1110 をブリッジとして構成すると、sja1110 のスレーブ ポートは正常に時刻を同期CAN。スレーブ ポートとしての Sja1110 port4 は、マスター ポートとしての s32g pfe0 と正常に時間を同期できます。 s32g pfe0 をマスター ポートとして使用するコマンドは次のとおりです。 bluebox@ubuntu-s32g399ardb3:~/linuxptp$ sudo ./ptp4l-i pfe0 -f configs/オートモーティブ-master.cfg --step_threshold=1 -m プロジェクトとキャプチャ ファイルをアップロードしました。 Re: gPTP master port of sja1110 こんにちは@xiaoshumiao 、 あなたに代わって新しいサポートCASEが作成されました。あなたはすでにそれについて返信しており、私も返信しています。まだ進行中です。新しいサポートCASEについては、引き続きお知らせします。 よろしくお願いいたします。 パベル Re: gPTP master port of sja1110 こんにちは@PavelL このメールに返信しました。ご覧になれますか? [email protected] Re: gPTP master port of sja1110 こんにちは@xiaoshumiao 、 はい、その通りです。その間に、私はいくつか調査を行い、解決策を見つけました。今週中にプライベートメールで共有します。 よろしくお願いいたします。 パベル Re: gPTP master port of sja1110 こんにちは@PavelL 、 通常、tcpip コンポーネントは gPTP コンポーネントの通常の動作に影響を与えません。nxp は後で修正しますか? Re: gPTP master port of sja1110 こんにちは@PavelL 、 本当にありがとうございます。あなたの提案に従います。 Re: gPTP master port of sja1110 こんにちは@xiaoshumiao 、 タイマー設定の問題にも気づきました。 これにかなりの時間を費やし、Lauterbachデバッガを使用して詳細な調査を行った結果、根本的な原因を特定することができました。tcpipコンポーネントとlwip_demo.cを追加したことです。gptp_sja1110x プロジェクトにファイルを追加すると、同じ不具合のある動作が発生します。 この時点で、唯一利用可能な回避策は、プロジェクトから lwip コンポーネントと tcpip コンポーネントの両方を削除することです。lwIP を使用せずにスイッチと gPTP を初期化する方法の例については、gptp_sja1110x/main.c を参照してください。また、ENET 設定にも注意してください。これは、switch_config_s32g_vnp_rdb の例とは少し異なります。 ご不便をおかけしましたことをお詫び申し上げます。 よろしくお願いいたします。 パベル Re: gPTP master port of sja1110 こんにちは@PavelL この問題に引き続きご注目いただきありがとうございます。 私の不注意により、設定に間違いがあることがわかりました。 LPIT チャネル 3 のトリガー ソースを内部トリガーに変更する必要があります。 私が行った他の変更は次のとおりです。 このCASE、フォローアップメッセージが時々送信されますが、理由はわかりません。 添付ファイルはキャプチャされたパッケージです。 Re: gPTP master port of sja1110 こんにちは@xiaoshumiao 、 仕事の都合で返信が遅れたことをお詫び申し上げます。 問題を再現できました。gptp_sja1110x の例は SJA1110-EVM で正常に動作しているので、まだよく分かりません。 今週中に返信できるよう最善を尽くします。 ご辛抱いただきありがとうございます。 よろしくお願いいたします。 パベル Re: gPTP master port of sja1110 こんにちは@xiaoshumiao 、 祝日のため返信が遅れましたことをお詫び申し上げます。 そのような行動の理由がCANません。さらに調査してみます。進捗があれば随時お知らせします。 よろしくお願いいたします。 パベル Re: gPTP master port of sja1110 こんにちは@PavelL 、 1.ブリッジの場合、スレーブはポート 4、マスターはポート 2 になります。 スレーブ ポートを nvidia orin にコネクテッドし、nvidia orin でパケットをキャプチャしました。 sudo tcpdump -i 任意 -vnn -w tsn0707.pcap 2. sja1110 がグランドマスターの場合、グランドマスターはポート 4 になり、s32g pfe0 はスレーブになります。 このCASE、s32g上のパケットをキャプチャします: sudo tcpdump -i any -vnn -w tsn0707.pcap このCASE、キャプチャされたパケットには同期のみがあり、フォローアップはありません。 Re: gPTP master port of sja1110 こんにちは@xiaoshumiao 、 仕事の都合で返信が遅くなり申し訳ございません。 プロジェクトを確認したところ、ソース コードや gPTP 設定など、確認した内容はすべて正しいようです。ただし、gPTP に定義されているポートは 1 つだけであることに気づきました。そのポートに対して「Pdelay Initiator」オプションを有効にしてみるとよいでしょう。 PC で Wireshark を接続するために使用しているポートを確認してください。 一般的な提案: SJA1110-EVM ボード用に用意されたリファレンス例 gptp_sja1110x とプロジェクトを比較してください。 また、SJA1110 製品ページの「ドキュメント」セクション (「セキュア ファイル」内) にある gPTP アプリケーション ノートも参照してください。 よろしくお願いいたします。 パベル Re: gPTP master port of sja1110 こんにちは@PavelL 、 ありがとうございます。何度も解決を試みましたが、うまくいきませんでした。 Re: gPTP master port of sja1110 こんにちは@xiaoshumiao 、 返信が遅くなり申し訳ございません。 今は答えが分からないので、もっと時間が必要です。 ご辛抱いただきありがとうございます。 よろしくお願いいたします。 パベル
記事全体を表示
How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing and My dear NXP, I would like to inquire about the process of updating the custom-modified U-Boot onto the board for i.mx9352. Could you please provide guidance on how to erase and flash the board with my own version of U-Boot? On i.MX 93, multiple elements are needed: • imx-boot (built by imx-mkimage), which includes SPL, U-Boot, Arm Trusted Firmware, OP-TEE, Sentinel Firmware, DDR PHY Firmware I currently do not want to modify SPL, Arm Trusted Firmware, OP-TEE, Sentinel Firmware, DDR PHY Firmware, but only make changes to u-boot. Which file generated by compiling u-boot needs to be updated in the partition of the board? Are there any instructions I can refer to? For i.mx6u, the reference instruction is ‘dd if=u-boot-imx6ull-14x14-ddr512-emmc.imx of=/dev/mmcblk1boot0 bs=1024 seek=1 conv=fsync’. So, what is the u-boot update instruction for i.mx93? I look forward to your reply. Thank you and have a pleasant life. Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing Hi, @orange-bear . Did you get solution to this issue? I'm facing same problem with imx93. No FBK ID after booting initramfs, so cannot execute any FBK command from uuu. Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing I have encountered an issue with Image and imx93-11x11-evk.dtb. I attempted to flash my own Image and imx93-11x11-evk. dtb onto the EVK board using evk_example_kernel_emmc.uuu. However, it is stuck at the ‘Start handle command’ stage. When I tested these two files using TFTP, they ran successfully. I also tried replacing them in /run/media/boot-mmcblk0p1, and they worked fine. So, if I want to flash my own Image and imx93-11x11-evk. dtb onto my own board using evk_example_kernel_emmc. uuu, which configurations in the kernel and device tree do I need to modify? Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing I employ the NXP iMX93 EVK development board along with the official image package. The utilization of the example_kernel_emmc.uuu yields favorable outcomes, as evidenced by the following printed information.  ...... uuu fastboot cli[ 3.160728] read strings ent 1.0.0 [built [ 3.164686] read strings Aug 17 2022 19:49:14] Start init usb uuu fastboot client 1.0.0 [built Aug 17 2022 19:49:14] Start init usb write string write string Start handle command Start handle command run shell cmd: while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "wait for /dev/mmcblk*boot* appear"; done; run shell cmd: dev=`ls /dev/mmcblk*boot*`; dev=($dev); dev=${dev[0]}; dev=${dev#/dev/mmcblk}; dev=${dev%boot*}; echo $dev > /tmp/mmcdev; run shell cmd: mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=512 count=1 1+0 records in 1+0 records out 512 bytes copied, 0.00157254 s, 326 kB/s run shell cmd: mmc=`cat /tmp/mmcdev`; PARTSTR=$'10M,500M,0c\n600M,,83\n'; echo "$PARTSTR" | sfdisk --force /dev/mmcblk${mmc} Partition #1 contains a vfat signature. Partition #2 contains a ext3 signature. I am unsure why my mirror is not executing the following shell command: while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "Waiting for the appearance of /dev/mmcblk*boot*"; done; Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing I'm sorry, but I seem to have misunderstood your intention. Please allow me to clarify my previous statement. I would like to update the imx-image-multimedia-imx93evk.tar.zst separately using commands or scripts, instead of updating the imx-image-multimedia-imx93evk.wic file. The "fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot" image package that I obtained is from the official website of NXP. It is based on the usage of "example_kernel_emmc.uuu". Currently, the execution stops at "FB: acmd ${kboot} ${loadaddr} ${initrd_addr} ${fdt_addr}". Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing From these logs, It seems uuu downloading not finished. Not sure how you handle the kernel Image. The way you use the example, you can also try command below, which is same as you taken. but at least can help troubleshooting for the current issue of loading and booting. uuu.exe -v -b emmc_all imx-boot-imx93evk-sd.bin-flash_singleboot imx-image-multimedia-imx93evk.wic Best regards Harvey Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing Thank you for your response. I have found that in the L6.1.1_1.0.0_MX93-BETA2/samples directory, there is a script called example_kernel_emmc.uuu that can fulfill my requirements. I am attempting to modify example_kernel_emmc.uuu to make it compatible with IMX93. The revised example_kernel_emmc.uuu file is as follows. uuu_version 1.2.39 # Please Replace below items with actually file names # @_flash.bin | boot loader, here is imx-boot-imx93evk-sd.bin-flash_singleboot # @_Image | kernel image, arm64 is Image, arm32 it is zImage, here is Image # @_board.dtb | board dtb file, here is imx93-11x11-evk.dtb # @_initramfs.cpio.gz.uboot | mfgtool init ramfs, here is fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot # @_rootfs.tar.zst | rootfs, here is imx-image-multimedia-imx93evk.tar.zst # @_uTee.tar | optee image, put dummy _uTee.tar file here if platform is not MX6/MX7* # This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ SDP: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot # This command will be run when ROM support stream mode # i.MX8QXP, i.MX8QM SDPS: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot # SDPU will be deprecated. please use SDPV instead of SDPU # { SDPU: delay 1000 SDPU: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -offset 0x57c00 SDPU: jump # } # These commands will be run when use SPL and will be skipped if no spl # if (SPL support SDPV) # { SDPV: delay 1000 SDPV: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -skipspl SDPV: jump # } # use uboot burn bootloader to eMMC # becaue difference chip, offset is difference # you can use kernel to do that for specific boards FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: flash bootloader imx-boot-imx93evk-sd.bin-flash_singleboot FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi; FB: ucmd setenv emmc_cmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0 FB: ucmd if test "${emmc_skip_fb}" != "yes"; then run emmc_cmd; fi FB: ucmd setenv emmc_cmd mmc bootbus ${emmc_dev} 2 0 1; FB: ucmd if test "${emmc_skip_fb}" != "yes"; then run emmc_cmd; fi FB: ucmd setenv fastboot_buffer ${loadaddr} FB: download -f Image FB: ucmd setenv fastboot_buffer ${fdt_addr} FB: download -f imx93-11x11-evk.dtb FB: ucmd setenv fastboot_buffer ${initrd_addr} FB: download -f fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot #FB: ucmd setenv bootargs console=${console},${baudrate} earlycon=${earlycon},${baudrate} FB: acmd ${kboot} ${loadaddr} ${initrd_addr} ${fdt_addr} # get mmc dev number from kernel command line # Wait for emmc FBK: ucmd while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "wait for /dev/mmcblk*boot* appear"; done; # serach emmc device number, if your platform have more than two emmc chip, please echo dev number >/tmp/mmcdev FBK: ucmd dev=`ls /dev/mmcblk*boot*`; dev=($dev); dev=${dev[0]}; dev=${dev#/dev/mmcblk}; dev=${dev%boot*}; echo $dev > /tmp/mmcdev; # dd to clear the possible MBR FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=512 count=1 # create partition FBK: ucmd mmc=`cat /tmp/mmcdev`; PARTSTR=$'10M,500M,0c\n600M,,83\n'; echo "$PARTSTR" | sfdisk --force /dev/mmcblk${mmc} FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=1k seek=4096 count=1 FBK: ucmd sync # you can enable below command to write boot partition. but offset is difference at difference platform #FBK: ucmd mmc=`cat /tmp/mmcdev`; echo 0 > /sys/block/mmcblk${mmc}boot0/force_ro #FBK: ucp imx-boot-imx93evk-sd.bin-flash_singleboot t:/tmp #FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/tmp/imx-boot-imx93evk-sd.bin-flash_singleboot of=/dev/mmc${mmc}boot0 bs=1K seek=32 #FBK: ucmd mmc=`cat /tmp/mmcdev`; echo 1 > /sys/block/mmcblk${mmc}boot0/force_ro FBK: ucmd mmc=`cat /tmp/mmcdev`; while [ ! -e /dev/mmcblk${mmc}p1 ]; do sleep 1; done FBK: ucmd mmc=`cat /tmp/mmcdev`; mkfs.vfat /dev/mmcblk${mmc}p1 FBK: ucmd mmc=`cat /tmp/mmcdev`; mkdir -p /mnt/fat FBK: ucmd mmc=`cat /tmp/mmcdev`; mount -t vfat /dev/mmcblk${mmc}p1 /mnt/fat FBK: ucp Image t:/mnt/fat FBK: ucp imx93-11x11-evk.dtb t:/mnt/fat #FBK: ucp _uTee.tar t:/tmp/op.tar FBK: ucmd tar --no-same-owner -xf /tmp/op.tar -C /mnt/fat FBK: ucmd umount /mnt/fat FBK: ucmd mmc=`cat /tmp/mmcdev`; mkfs.ext3 -F -E nodiscard /dev/mmcblk${mmc}p2 FBK: ucmd mkdir -p /mnt/ext3 FBK: ucmd mmc=`cat /tmp/mmcdev`; mount /dev/mmcblk${mmc}p2 /mnt/ext3 FBK: acmd export EXTRACT_UNSAFE_SYMLINKS=1; tar --zstd --warning=no-timestamp -x -C /mnt/ext3 FBK: ucp imx-image-multimedia-imx93evk.tar.zst t:- FBK: Sync FBK: ucmd umount /mnt/ext3 FBK: DONE The structure of the file is represented as follows. example_kernel_emmc.uuu Image imx-boot-imx93evk-sd.bin-flash_singleboot fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot imx93-11x11-evk.dtb imx-image-multimedia-imx93evk.rootfs.tar.zst The log information of the burning process is as follows: U-Boot SPL 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000) SOC: 0xa0009300 LC: 0x40010 M33 prepare ok Normal Boot Trying to boot from BOOTROM Boot Stage: USB boot Find img info 0x&88000000, size 416 Download 1610752, Total size 1611776 NOTICE: BL31: v2.6(release):lf-6.1.1-1.0.0-0-g616a4588f NOTICE: BL31: Built : 10:31:38, Mar 1 2023 U-Boot 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000) CPU: i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz) CPU: Consumer temperature grade (0C to 95C) at 46C Reset cause: POR (0x1) Model: NXP i.MX93 11X11 EVK board DRAM: 2 GiB tcpc_init: Can't find device id=0x52 setup_typec: tcpc portpd init failed, err=-19 tcpc_init: Can't find device id=0x51 setup_typec: tcpc port2 init failed, err=-19 tcpc_init: Can't find device id=0x50 setup_typec: tcpc port1 init failed, err=-19 pca953x gpio@22: Error reading output register Core: 204 devices, 28 uclasses, devicetree: separate MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from nowhere... OK [*]-Video Link 0adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 [0] lcd-controller@4ae30000, video [1] dsi@4ae10000, video_bridge [2] hdmi@3d, panel adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 In: serial Out: serial Err: serial BuildInfo: - ELE firmware version 0.0.9-9df0f503 MMC: no card present UID: 0x1d46516e 0xa9410d98 0x93a276bd 0xe691bc10 Detect USB boot. Will enter fastboot mode! Net: pca953x gpio@22: Error reading output register pca953x gpio@22: Error reading output register Warning: ethernet@42890000 (eth0) using random MAC address - d6:1f:33:20:03:1c pca953x gpio@22: Error reading output register pca953x gpio@22: Error reading output register Warning: ethernet@428a0000 (eth1) using random MAC address - 22:92:db:80:d8:ea eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME] Fastboot: Normal Boot from USB for mfgtools *** Warning - Use default environment for mfgtools , using default environment Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot auto; fi; Hit any key to stop autoboot: 0 ## Checking Image at 83800000 ... Legacy image found Image Name: fsl-image-mfgtool-initramfs-imx8 Created: 2011-04-05 23:00:00 UTC Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 11910836 Bytes = 11.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Run fastboot ... auto usb 0 UID: 0x1d46516e 0xa9410d98 0x93a276bd 0xe691bc10 Detect USB boot. Will enter fastboot mode! flash target is MMC:1 MMC: no card present MMC card init failed! MMC: no card present ** Block device MMC 1 not supported Detect USB boot. Will enter fastboot mode! flash target is MMC:0 Starting download of 1876992 bytes .............. downloading of 1876992 bytes finished writing to partition 'bootloader' Initializing 'bootloader' switch to partitions #1, OK mmc0(part 1) is current device Writing 'bootloader' MMC write: dev # 0, block # 0, count 3666 ... 3666 blocks written: OK Writing 'bootloader' DONE! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Set to BOOT_BUS_WIDTH = 0x2, RESET = 0x0, BOOT_MODE = 0x1 Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Starting download of 32117248 bytes .......................................................................... .......................................................................... .......................................................................... ....................... downloading of 32117248 bytes finished Detect USB boot. Will enter fastboot mode! Starting download of 43801 bytes downloading of 43801 bytes finished Detect USB boot. Will enter fastboot mode! Starting download of 11910900 bytes .......................................................................... ................ downloading of 11910900 bytes finished ## Loading init Ramdisk from Legacy Image at 83800000 ... Image Name: fsl-image-mfgtool-initramfs-imx8 Created: 2011-04-05 23:00:00 UTC Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 11910836 Bytes = 11.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000 Using Device Tree in place at 0000000083000000, end 000000008300db18 adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] [ 0.000000] Linux version 6.1.1+g29549c7073bf (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0.20220819) #1 SMP PREEMPT Thu Mar 2 14:54:17 UTC 2023 [ 0.000000] Machine model: NXP i.MX93 11X11 EVK board [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000b0000000, size 256 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4020000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdevbuffer@a4020000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4120000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node ele-reserved@a4120000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 256 MiB [ 0.000000] OF: reserved mem: initialized node ethosu_region@C0000000, compatible id shared-dma-pool [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] NUMA: NODE_DATA [mem 0xffbd3700-0xffbd5fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000080000000-0x0000000095ffffff] [ 0.000000] node 0: [mem 0x0000000098000000-0x00000000a3ffffff] [ 0.000000] node 0: [mem 0x00000000a4000000-0x00000000a421ffff] [ 0.000000] node 0: [mem 0x00000000a4220000-0x00000000ffffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] On node 0, zone DMA: 8192 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 20 pages/cpu s44520 r8192 d29208 u81920 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Virtualization Host Extensions [ 0.000000] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009 [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] alternatives: applying boot alternatives [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 507904 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: console=ttyLP0,115200 earlycon,115200 rdinit=/linuxrc clk_ignore_unused [ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off [ 0.000000] Memory: 1453904K/2064384K available (19584K kernel code, 1604K rwdata, 6712K rodata, 3328K init, 644K bss, 86192K reserved, 524288K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 960 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: GICv3 features: 16 PPIs [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000048040000 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.000309] Console: colour dummy device 80x25 [ 0.000364] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.000373] pid_max: default: 32768 minimum: 301 [ 0.000413] LSM: Security Framework initializing [ 0.000484] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.000493] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.001211] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 0.001615] cblist_init_generic: Setting adjustable number of callback queues. [ 0.001624] cblist_init_generic: Setting shift to 1 and lim to 1. [ 0.001670] cblist_init_generic: Setting shift to 1 and lim to 1. [ 0.001788] rcu: Hierarchical SRCU implementation. [ 0.001791] rcu: Max phase no-delay instances is 1000. [ 0.002539] EFI services will not be available. [ 0.002685] smp: Bringing up secondary CPUs ... [ 0.003029] Detected VIPT I-cache on CPU1 [ 0.003095] cacheinfo: Unable to detect cache hierarchy for CPU 1 [ 0.003105] GICv3: CPU1: found redistributor 100 region 0:0x0000000048060000 [ 0.003142] CPU1: Booted secondary processor 0x0000000100 [0x412fd050] [ 0.003229] smp: Brought up 1 node, 2 CPUs [ 0.003234] SMP: Total of 2 processors activated. [ 0.003238] CPU features: detected: 32-bit EL0 Support [ 0.003240] CPU features: detected: 32-bit EL1 Support [ 0.003244] CPU features: detected: Data cache clean to the PoU not required for I/D coherence [ 0.003247] CPU features: detected: Common not Private translations [ 0.003249] CPU features: detected: CRC32 instructions [ 0.003253] CPU features: detected: RCpc load-acquire (LDAPR) [ 0.003255] CPU features: detected: LSE atomic instructions [ 0.003257] CPU features: detected: Privileged Access Never [ 0.003259] CPU features: detected: RAS Extension Support [ 0.003265] CPU features: detected: Speculative Store Bypassing Safe (SSBS) [ 0.003313] CPU: All CPU(s) started at EL2 [ 0.003315] alternatives: applying system-wide alternatives [ 0.007599] devtmpfs: initialized [ 0.012159] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.012179] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.020304] pinctrl core: initialized pinctrl subsystem [ 0.021503] DMI not present or invalid. [ 0.021949] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.022749] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations [ 0.022890] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.022983] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.023035] audit: initializing netlink subsys (disabled) [ 0.023191] audit: type=2000 audit(0.020:1): state=initialized audit_enabled=0 res=1 [ 0.023541] thermal_sys: Registered thermal governor 'step_wise' [ 0.023546] thermal_sys: Registered thermal governor 'power_allocator' [ 0.023575] cpuidle: using governor menu [ 0.023744] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.023789] ASID allocator initialised with 65536 entries [ 0.024382] Serial: AMBA PL011 UART driver [ 0.024424] imx mu driver is registered. [ 0.024435] imx rpmsg driver is registered. [ 0.029818] imx93-pinctrl 443c0000.pinctrl: initialized IMX pinctrl driver [ 0.036057] platform 4ae30000.lcd-controller: Fixing up cyclic dependency with 4ae10000.dsi [ 0.039167] KASLR disabled due to lack of seed [ 0.050510] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages [ 0.050519] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page [ 0.050522] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages [ 0.050524] HugeTLB: 508 KiB vmemmap can be freed for a 32.0 MiB page [ 0.050527] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages [ 0.050529] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page [ 0.050532] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages [ 0.050534] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page [ 0.052231] ACPI: Interpreter disabled. [ 0.053090] iommu: Default domain type: Translated [ 0.053100] iommu: DMA domain TLB invalidation policy: strict mode [ 0.053318] SCSI subsystem initialized [ 0.053622] usbcore: registered new interface driver usbfs [ 0.053650] usbcore: registered new interface driver hub [ 0.053669] usbcore: registered new device driver usb [ 0.054429] mc: Linux media interface: v0.10 [ 0.054461] videodev: Linux video capture interface: v2.00 [ 0.054497] pps_core: LinuxPPS API ver. 1 registered [ 0.054500] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.054508] PTP clock support registered [ 0.054601] EDAC MC: Ver: 3.0.0 [ 0.055719] FPGA manager framework [ 0.055781] Advanced Linux Sound Architecture Driver Initialized. [ 0.056190] Bluetooth: Core ver 2.22 [ 0.056218] NET: Registered PF_BLUETOOTH protocol family [ 0.056220] Bluetooth: HCI device and connection manager initialized [ 0.056226] Bluetooth: HCI socket layer initialized [ 0.056230] Bluetooth: L2CAP socket layer initialized [ 0.056244] Bluetooth: SCO socket layer initialized [ 0.056579] vgaarb: loaded [ 0.057072] clocksource: Switched to clocksource arch_sys_counter [ 0.057247] VFS: Disk quotas dquot_6.6.0 [ 0.057275] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.057384] pnp: PnP ACPI: disabled [ 0.062200] NET: Registered PF_INET protocol family [ 0.062459] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.063693] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 0.063721] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.063730] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.063799] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear) [ 0.064220] TCP: Hash tables configured (established 16384 bind 16384) [ 0.064337] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.064375] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.064523] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.064896] RPC: Registered named UNIX socket transport module. [ 0.064902] RPC: Registered udp transport module. [ 0.064904] RPC: Registered tcp transport module. [ 0.064906] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.065481] PCI: CLS 0 bytes, default 64 [ 0.065671] Unpacking initramfs... [ 0.077164] hw perfevents: enabled with armv8_cortex_a55 PMU driver, 7 counters available [ 0.077791] kvm [1]: IPA Size Limit: 40 bits [ 0.077823] kvm [1]: GICv3: no GICV resource entry [ 0.077826] kvm [1]: disabling GICv2 emulation [ 0.077840] kvm [1]: GIC system register CPU interface enabled [ 0.077945] kvm [1]: vgic interrupt IRQ9 [ 0.077995] kvm [1]: VHE mode initialized successfully [ 0.079075] Initialise system trusted keyrings [ 0.079368] workingset: timestamp_bits=42 max_order=19 bucket_order=0 [ 0.083800] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.084377] NFS: Registering the id_resolver key type [ 0.084427] Key type id_resolver registered [ 0.084430] Key type id_legacy registered [ 0.084478] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.084483] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 0.084498] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.084799] 9p: Installing v9fs 9p2000 file system support [ 0.110306] Key type asymmetric registered [ 0.110323] Asymmetric key parser 'x509' registered [ 0.110421] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 0.110426] io scheduler mq-deadline registered [ 0.110430] io scheduler kyber registered [ 0.115631] EINJ: ACPI disabled. [ 0.121059] Bus freq driver module loaded [ 0.127423] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.130859] 44380000.serial: ttyLP0 at MMIO 0x44380010 (irq = 18, base_baud = 1500000) is a FSL_LPUART [ 0.579725] Freeing initrd memory: 11624K [ 0.587591] printk: console [ttyLP0] enabled [ 1.297743] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 1.307341] loop: module loaded [ 1.311565] of_reserved_mem_lookup() returned NULL [ 1.316484] megasas: 07.719.03.00-rc1 [ 1.321853] imx ahci driver is registered. [ 1.329636] tun: Universal TUN/TAP device driver, 1.6 [ 1.335399] thunder_xcv, ver 1.0 [ 1.338673] thunder_bgx, ver 1.0 [ 1.341914] nicpf, ver 1.0 [ 1.345372] pps pps0: new PPS source ptp0 [ 1.354869] fec 42890000.ethernet eth0: registered PHC device 0 [ 1.362443] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.369679] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.375062] hclge is initializing [ 1.378397] e1000: Intel(R) PRO/1000 Network Driver [ 1.383269] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.389040] e1000e: Intel(R) PRO/1000 Network Driver [ 1.394000] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.399932] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.405330] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.410916] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 1.417174] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.423285] sky2: driver version 1.30 [ 1.427579] imx-dwmac 428a0000.ethernet: IRQ eth_lpi not found [ 1.433752] imx-dwmac 428a0000.ethernet: User ID: 0x10, Synopsys ID: 0x52 [ 1.440551] imx-dwmac 428a0000.ethernet: DWMAC4/5 [ 1.445333] imx-dwmac 428a0000.ethernet: DMA HW capability register supported [ 1.452455] imx-dwmac 428a0000.ethernet: RX Checksum Offload Engine supported [ 1.459578] imx-dwmac 428a0000.ethernet: TX Checksum insertion supported [ 1.466268] imx-dwmac 428a0000.ethernet: Wake-Up On Lan supported [ 1.472401] imx-dwmac 428a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 1.480057] imx-dwmac 428a0000.ethernet: device MAC address 86:81:0f:94:98:19 [ 1.487205] imx-dwmac 428a0000.ethernet: Enabled L3L4 Flow TC (entries=8) [ 1.493987] imx-dwmac 428a0000.ethernet: Enabled RFS Flow TC (entries=10) [ 1.500766] imx-dwmac 428a0000.ethernet: Enabling HW TC (entries=256, max_off=256) [ 1.508321] imx-dwmac 428a0000.ethernet: Using 32 bits DMA width [ 1.518225] usbcore: registered new interface driver r8152 [ 1.524089] VFIO - User Level meta-driver version: 0.3 [ 1.531938] usbcore: registered new interface driver uas [ 1.537317] usbcore: registered new interface driver usb-storage [ 1.543397] usbcore: registered new interface driver usbserial_generic [ 1.549930] usbserial: USB Serial support registered for generic [ 1.555949] usbcore: registered new interface driver ftdi_sio [ 1.561690] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.569004] usbcore: registered new interface driver usb_serial_simple [ 1.575530] usbserial: USB Serial support registered for carelink [ 1.581622] usbserial: USB Serial support registered for zio [ 1.587281] usbserial: USB Serial support registered for funsoft [ 1.593287] usbserial: USB Serial support registered for flashloader [ 1.599640] usbserial: USB Serial support registered for google [ 1.605559] usbserial: USB Serial support registered for libtransistor [ 1.612090] usbserial: USB Serial support registered for vivopay [ 1.618095] usbserial: USB Serial support registered for moto_modem [ 1.624358] usbserial: USB Serial support registered for motorola_tetra [ 1.630970] usbserial: USB Serial support registered for nokia [ 1.636807] usbserial: USB Serial support registered for novatel_gps [ 1.643163] usbserial: USB Serial support registered for hp4x [ 1.648922] usbserial: USB Serial support registered for suunto [ 1.654845] usbserial: USB Serial support registered for siemens_mpi [ 1.661206] usbcore: registered new interface driver usb_ehset_test [ 1.669805] bbnsm_pwrkey 44440000.bbnsm:pwrkey: KEY_POWER without setting in dts [ 1.678054] input: 44440000.bbnsm:pwrkey as /devices/platform/soc@0/44000000.bus/44440000.bbnsm/44440000.bbnsm:pwrkey/input/input0 [ 1.693496] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0 [ 1.700063] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:40:35 UTC (2435) [ 1.709596] i2c_dev: i2c /dev entries driver [ 1.716720] imx7ulp-wdt 42490000.wdog: imx93 wdt probe [ 1.750651] Bluetooth: HCI UART driver ver 2.3 [ 1.755119] Bluetooth: HCI UART protocol H4 registered [ 1.760253] Bluetooth: HCI UART protocol BCSP registered [ 1.765575] Bluetooth: HCI UART protocol LL registered [ 1.770704] Bluetooth: HCI UART protocol ATH3K registered [ 1.776103] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.782493] Bluetooth: HCI UART protocol Broadcom registered [ 1.788157] Bluetooth: HCI UART protocol QCA registered [ 1.794787] sdhci: Secure Digital Host Controller Interface driver [ 1.800994] sdhci: Copyright(c) Pierre Ossman [ 1.805883] Synopsys Designware Multimedia Card Interface Driver [ 1.812371] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.819532] ledtrig-cpu: registered to indicate activity on CPUs [ 1.826499] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 1.833373] usbcore: registered new interface driver usbhid [ 1.838953] usbhid: USB HID core driver [ 1.844379] ethosu ethosu: assigned reserved memory node ethosu_region@C0000000 [ 1.850056] mmc0: SDHCI controller on 42850000.mmc [42850000.mmc] using ADMA [ 1.891274] cs_system_cfg: CoreSight Configuration manager initialised [ 1.898992] optee: probing for conduit method. [ 1.903467] optee: revision 3.19 (ad4e8389) [ 1.903903] optee: dynamic shared memory is enabled [ 1.913286] optee: initialized driver [ 1.920587] NET: Registered PF_LLC protocol family [ 1.926018] NET: Registered PF_INET6 protocol family [ 1.931886] Segment Routing with IPv6 [ 1.935621] In-situ OAM (IOAM) with IPv6 [ 1.939623] NET: Registered PF_PACKET protocol family [ 1.944709] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 1.957852] Bluetooth: RFCOMM TTY layer initialized [ 1.962736] Bluetooth: RFCOMM socket layer initialized [ 1.967882] Bluetooth: RFCOMM ver 1.11 [ 1.971628] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 1.975581] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 1.976925] Bluetooth: BNEP filters: protocol multicast [ 1.983735] mmcblk0: mmc0:0001 58A398 7.28 GiB [ 1.988480] Bluetooth: BNEP socket layer initialized [ 1.994157] mmcblk0: p1 p2 [ 1.997954] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.001220] mmcblk0boot0: mmc0:0001 58A398 4.00 MiB [ 2.006645] Bluetooth: HIDP socket layer initialized [ 2.012467] mmcblk0boot1: mmc0:0001 58A398 4.00 MiB [ 2.016733] 8021q: 802.1Q VLAN Support v1.8 [ 2.022269] mmcblk0rpmb: mmc0:0001 58A398 4.00 MiB, chardev (234:0) [ 2.025790] lib80211: common routines for IEEE802.11 drivers [ 2.037706] 9pnet: Installing 9P2000 support [ 2.042071] Key type dns_resolver registered [ 2.046761] registered taskstats version 1 [ 2.050882] Loading compiled-in X.509 certificates [ 2.069935] usb_phy_generic soc@0:usbphynop1: supply vcc not found, using dummy regulator [ 2.078259] usb_phy_generic soc@0:usbphynop1: dummy supplies not allowed for exclusive requests [ 2.087063] usb_phy_generic soc@0:usbphynop2: supply vcc not found, using dummy regulator [ 2.095411] usb_phy_generic soc@0:usbphynop2: dummy supplies not allowed for exclusive requests [ 2.113448] gpio gpiochip0: (43810080.gpio): not an immutable chip, please consider fixing it! [ 2.122542] gpio gpiochip1: (43820080.gpio): not an immutable chip, please consider fixing it! [ 2.131592] gpio gpiochip2: (43830080.gpio): not an immutable chip, please consider fixing it! [ 2.140641] gpio gpiochip3: (47400080.gpio): not an immutable chip, please consider fixing it! [ 2.154906] remoteproc remoteproc0: imx-rproc is available [ 2.162795] i2c 0-003d: Fixing up cyclic dependency with 4ae10000.dsi [ 2.169394] adv7511 0-003d: supply avdd not found, using dummy regulator [ 2.176171] adv7511 0-003d: supply dvdd not found, using dummy regulator [ 2.182901] adv7511 0-003d: supply pvdd not found, using dummy regulator [ 2.189618] adv7511 0-003d: supply a2vdd not found, using dummy regulator [ 2.196414] adv7511 0-003d: supply v3p3 not found, using dummy regulator [ 2.203140] adv7511 0-003d: supply v1p2 not found, using dummy regulator [ 2.210309] adv7511 0-003d: Probe failed. Remote port 'dsi@4ae10000' disabled [ 2.217833] st_lsm6dsx_i2c 0-006a: supply vdd not found, using dummy regulator [ 2.225158] st_lsm6dsx_i2c 0-006a: supply vddio not found, using dummy regulator [ 2.289539] st_lsm6dsx_i2c 0-006a: failed to read whoami register [ 2.295812] st_lsm6dsx_i2c: probe of 0-006a failed with error -5 [ 2.301895] i2c i2c-0: LPI2C adapter registered [ 2.307942] pca953x 1-0022: supply vcc not found, using dummy regulator [ 2.314705] pca953x 1-0022: using AI [ 2.318364] pca953x 1-0022: failed writing register [ 2.323346] pca953x: probe of 1-0022 failed with error -5 [ 2.329016] adp5585 1-0034: Failed to read reg 0x00, ret is -5 [ 2.334871] adp5585: probe of 1-0034 failed with error -5 [ 2.340359] i2c i2c-1: LPI2C adapter registered [ 2.345948] i2c 2-0050: Fixing up cyclic dependency with 4c100000.usb [ 3.357110] tcpci: probe of 2-0050 failed with error -110 [ 3.362704] i2c 2-0051: Fixing up cyclic dependency with 4c200000.usb [ 4.377113] tcpci: probe of 2-0051 failed with error -110 [ 5.389069] adp5585 2-0034: Failed to read reg 0x00, ret is -110 [ 5.395082] adp5585: probe of 2-0034 failed with error -110 [ 5.400885] i2c 2-003c: Fixing up cyclic dependency with 4ae00000.csi [ 5.407546] i2c i2c-2: LPI2C adapter registered [ 5.414180] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 5.422156] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/dsi@4ae10000 to encoder DSI-34: -19 [ 5.432166] dw-mipi-dsi-imx 4ae10000.dsi: [drm:dw_mipi_dsi_imx_bind] *ERROR* failed to attach bridge: -19 [ 5.441725] imx-drm display-subsystem: failed to bind 4ae10000.dsi (ops dw_mipi_dsi_imx_ops): -19 [ 5.450869] imx-drm display-subsystem: adev bind failed: -19 [ 5.456538] dw-mipi-dsi-imx 4ae10000.dsi: [drm:dw_mipi_dsi_imx_probe] *ERROR* failed to register component: -19 [ 5.478535] sdhci-esdhc-imx 42860000.mmc: Got CD GPIO [ 5.479882] dwc-mipi-csi2-host 4ae00000.csi: lanes: 2, name: mxc-mipi-csi2.0 [ 5.498291] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 5.511405] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 5.518188] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 5.521123] clk: Not disabling unused clocks [ 5.526882] mmc1: SDHCI controller on 42860000.mmc [42860000.mmc] using ADMA [ 5.531085] ALSA device list: [ 5.538113] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 5.541074] No soundcards found. [ 5.554051] Freeing unused kernel memory: 3328K [ 5.573123] Run /linuxrc as init process Found New UDC: ci_hdrc.0 ci_hdrc.0 0 Found New UDC: ci_hdrc.1 ci_hdrc.1 1 ffs.utp0 [ 5.621381] file system registered ffs.utp1 run utp at /dev/usb-utp0/ep0 . run utp at /dev/usb-utp1/ep0 [ 5.642106] read descriptors uuu fastboot cli[ 5.646482] read descriptors ent 1.0.0 [built [ 5.650846] read strings Aug 17 2022 19:49[ 5.650846] read strings :14] Start init usb uuu fastboot client 1.0.0 [built Aug 17 2022 19:49:14] Start init usb write string write string Start handle command Start handle command Currently, it remains stuck at "Start handle command" and I am unsure of how to rectify this situation. I kindly request your guidance or potentially providing a readily usable example_kernel_emmc.uuu for i.mx93. I eagerly await your response and wish you a delightful day ahead. Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing Hi @orange-bear  You can refer to the i.MX_Porting_Guide (Embedded Linux for i.MX Applications Processors | NXP Semiconductors) Best regards Harvey
記事全体を表示
Segger j-link V9デバッガを使用してS32k311 MCUをデバッグできない 私は、S32k311 MCU をベースにした 18s BMS ソリューションのために、Elekronika India の評価ボードを使用しています。フラッシュとデバッグには、Segger j-link V9-G JTAG デバッガーが使用されています。 しかし、サンプル コードをデバッグすると、フラッシュ後に PC はメイン関数ではなくランダムな RAM の位置に移動します。参考までに画像を同封します。main以外にブレークポイントはありません。しかし、PC はメインで停止せず、ランダムな RAM の場所に移動してそこで停止します。S32k311 の別のサンプル コードを試してみましたが、同じ出力が得られました。   解決策を提案してください。   Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger 問題は、Segger コネクタから JTAG アダプタ ボードへの接続にありました。デバッグ セッションの前にコントローラをリセットできませんでした。今は解決しました。 Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger こんにちは、 しかし、サンプルコードをデバッグすると、フラッシュ後にPCはメイン関数ではなくランダムなRAMの場所に移動します。 わかりました。奇妙に思えます。コアはその中にロードされた命令を実行します。ランダムなものではありません。 SW 内でその RAM 位置への何らかの分岐 (ジャンプ) を実行する必要があります。また、分岐を実行するには、コア レジスタで RAM の場所を定義する必要があります。 ステップごとにデバッグを行うと、RAM への分岐がどこで発生しているか、またその前提条件も正確に確認できます。 しかし、PC はメインで停止せず、ランダムな RAM の場所に移動してそこで停止します。S32k311 の別のサンプル コードを試してみましたが、同じ出力が得られました。 はい、メインに到達しない場合は、メインブレークポイントで停止しません。 別の例でも同じ結果が得られるため、EVB を使用する場合はボード上のジャンパー設定に問題がある可能性があります。 必要なすべての HW 設定が記載されているスタートガイドが EVB に付属しています。 しかし、起動時のデバッグを行うと、問題がどこにあるかが簡単にわかります。 よろしくお願いいたします。 ピーター Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger 参考までにgdbサーバログをご覧ください。
記事全体を表示
如何将我的自定义 U-Boot 更新到 i.mx9352 板?删除和 亲爱的恩智浦,我想询问一下将自定义修改的U-Boot更新到i.mx9352板的过程。你能否就如何使用我自己的 U-启动 版本擦除和刷新主板提供指导? 在 i.MX 93 上,需要多个元素: • imx-启动(由 imx-mkimage 版本),包括 SPL、U-启动、Arm 可信固件、OP-TEE、Sentinel 固件、DDR PHY 固件 我目前不想修改 SPL、Arm Trusted 固件、OP-TEE、Sentinel 固件、DDR PHY 固件,而只想修改 u-boot。编译 u-boot 生成的哪个文件需要在板分区中更新?有什么说明可以参考吗?对于 i.mx6u 来说,参考指令是 'dd if=u-boot-imx6ull-14x14-ddr512-emmc.imx of=/dev/mmcblk1boot0 bs=1024 seek=1 conv=fsync'。那么,i.mx93 的 u-启动 更新指令是什么?期待您的回复。谢谢您,祝您生活愉快。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 嗨,@橘子熊。 您解决这个问题了吗? 我在使用 imx93 时也遇到了同样的问题。启动 initramfs 后没有 FBK ID,因此无法从 uuu 执行任何 FBK 命令。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 我在使用 Image 和 imx93-11x11-evk.dtb 时遇到了问题。我试着刷自己的镜像和 imx93-11x11-evk。使用 evk_example_kernel_emmc.uuu 将 dtb 放到 EVK 板上。但是,它停留在 “启动句柄命令” 阶段。当我使用 TFTP 测试这两个文件时,它们成功运行。我还尝试在 /run/media/boot-mmcblk0p1 中替换它们,它们运行良好。所以,如果我想刷自己的镜像和 imx93-11x11-evk。使用 evk_example_kernel_emmc 将 dtb 放到我自己的板上。uuu,我需要修改内核和设备树中的哪些配置? Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 我使用了恩智浦iMX93 EVK开发板以及官方镜像软件包。使用example_kernel_emmc.uuu可以产量良好的结果,以下印刷信息就证明了这一点。 ...... uuu fastboot cli[ 3.160728] read strings ent 1.0.0 [built [ 3.164686] read strings Aug 17 2022 19:49:14] Start init usb uuu fastboot client 1.0.0 [built Aug 17 2022 19:49:14] Start init usb write string write string Start handle command Start handle command run shell cmd: while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "wait for /dev/mmcblk*boot* appear"; done; run shell cmd: dev=`ls /dev/mmcblk*boot*`; dev=($dev); dev=${dev[0]}; dev=${dev#/dev/mmcblk}; dev=${dev%boot*}; echo $dev > /tmp/mmcdev; run shell cmd: mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=512 count=1 1+0 records in 1+0 records out 512 bytes copied, 0.00157254 s, 326 kB/s run shell cmd: mmc=`cat /tmp/mmcdev`; PARTSTR=$'10M,500M,0c\n600M,,83\n'; echo "$PARTSTR" | sfdisk --force /dev/mmcblk${mmc} Partition #1 contains a vfat signature. Partition #2 contains a ext3 signature. 我不确定为什么我的镜像没有执行以下 shell 命令:while [!-e /dev/mmcblk *boot0];睡觉 1;echo " 等待 /dev/mmcblk 的出现 *boot* "; 完成; Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 对不起,我似乎误解了你的意图。请允许我澄清一下我之前的发言。 我想使用命令或脚本单独更新 imx-image-multimedia-imx93evk.tar.zst,而不是更新 imx-image-multimedia-imx93evk.wic 文件。 " fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-启动 "我获得的镜像软件包来自恩智浦的官方网站。它基于"example_kernel_emmc.uuu" 的用法。目前,执行停止在"FB: acmd${kboot} ${loadaddr} ${initrd_addr} ${fdt_addr} " 。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 从这些日志来看,uuu 下载似乎尚未完成。不知道你是如何处理内核映像的。 您使用的示例也可以试试下面的命令,与您使用的相同。但至少可以帮助解决当前的加载和启动问题。 uuu.exe-v-b emmc_all imx-启动-imx93evk-sd.bin-flash_singleboot imx-image-multimedia-imx-multimedia-imx93evk.wic 顺祝商祺! 哈维 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 感谢您的反馈, 我发现在 L6.1.1_1.0.0_MX93-BETA2/samples 目录中,有一个名为 example_kernel_emmc.uuu 的脚本可以满足我的要求。我正在尝试修改 example_kernel_emmc.uuu,使其与 IMX93 兼容。 修改后的 example_kernel_emmc.uuu 文件如下。 uuu_version 1.2.39 # Please Replace below items with actually file names # @_flash.bin | boot loader, here is imx-boot-imx93evk-sd.bin-flash_singleboot # @_Image | kernel image, arm64 is Image, arm32 it is zImage, here is Image # @_board.dtb | board dtb file, here is imx93-11x11-evk.dtb # @_initramfs.cpio.gz.uboot | mfgtool init ramfs, here is fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot # @_rootfs.tar.zst | rootfs, here is imx-image-multimedia-imx93evk.tar.zst # @_uTee.tar | optee image, put dummy _uTee.tar file here if platform is not MX6/MX7* # This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ SDP: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot # This command will be run when ROM support stream mode # i.MX8QXP, i.MX8QM SDPS: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot # SDPU will be deprecated. please use SDPV instead of SDPU # { SDPU: delay 1000 SDPU: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -offset 0x57c00 SDPU: jump # } # These commands will be run when use SPL and will be skipped if no spl # if (SPL support SDPV) # { SDPV: delay 1000 SDPV: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -skipspl SDPV: jump # } # use uboot burn bootloader to eMMC # becaue difference chip, offset is difference # you can use kernel to do that for specific boards FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: flash bootloader imx-boot-imx93evk-sd.bin-flash_singleboot FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi; FB: ucmd setenv emmc_cmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0 FB: ucmd if test "${emmc_skip_fb}" != "yes"; then run emmc_cmd; fi FB: ucmd setenv emmc_cmd mmc bootbus ${emmc_dev} 2 0 1; FB: ucmd if test "${emmc_skip_fb}" != "yes"; then run emmc_cmd; fi FB: ucmd setenv fastboot_buffer ${loadaddr} FB: download -f Image FB: ucmd setenv fastboot_buffer ${fdt_addr} FB: download -f imx93-11x11-evk.dtb FB: ucmd setenv fastboot_buffer ${initrd_addr} FB: download -f fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot #FB: ucmd setenv bootargs console=${console},${baudrate} earlycon=${earlycon},${baudrate} FB: acmd ${kboot} ${loadaddr} ${initrd_addr} ${fdt_addr} # get mmc dev number from kernel command line # Wait for emmc FBK: ucmd while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "wait for /dev/mmcblk*boot* appear"; done; # serach emmc device number, if your platform have more than two emmc chip, please echo dev number >/tmp/mmcdev FBK: ucmd dev=`ls /dev/mmcblk*boot*`; dev=($dev); dev=${dev[0]}; dev=${dev#/dev/mmcblk}; dev=${dev%boot*}; echo $dev > /tmp/mmcdev; # dd to clear the possible MBR FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=512 count=1 # create partition FBK: ucmd mmc=`cat /tmp/mmcdev`; PARTSTR=$'10M,500M,0c\n600M,,83\n'; echo "$PARTSTR" | sfdisk --force /dev/mmcblk${mmc} FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=1k seek=4096 count=1 FBK: ucmd sync # you can enable below command to write boot partition. but offset is difference at difference platform #FBK: ucmd mmc=`cat /tmp/mmcdev`; echo 0 > /sys/block/mmcblk${mmc}boot0/force_ro #FBK: ucp imx-boot-imx93evk-sd.bin-flash_singleboot t:/tmp #FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/tmp/imx-boot-imx93evk-sd.bin-flash_singleboot of=/dev/mmc${mmc}boot0 bs=1K seek=32 #FBK: ucmd mmc=`cat /tmp/mmcdev`; echo 1 > /sys/block/mmcblk${mmc}boot0/force_ro FBK: ucmd mmc=`cat /tmp/mmcdev`; while [ ! -e /dev/mmcblk${mmc}p1 ]; do sleep 1; done FBK: ucmd mmc=`cat /tmp/mmcdev`; mkfs.vfat /dev/mmcblk${mmc}p1 FBK: ucmd mmc=`cat /tmp/mmcdev`; mkdir -p /mnt/fat FBK: ucmd mmc=`cat /tmp/mmcdev`; mount -t vfat /dev/mmcblk${mmc}p1 /mnt/fat FBK: ucp Image t:/mnt/fat FBK: ucp imx93-11x11-evk.dtb t:/mnt/fat #FBK: ucp _uTee.tar t:/tmp/op.tar FBK: ucmd tar --no-same-owner -xf /tmp/op.tar -C /mnt/fat FBK: ucmd umount /mnt/fat FBK: ucmd mmc=`cat /tmp/mmcdev`; mkfs.ext3 -F -E nodiscard /dev/mmcblk${mmc}p2 FBK: ucmd mkdir -p /mnt/ext3 FBK: ucmd mmc=`cat /tmp/mmcdev`; mount /dev/mmcblk${mmc}p2 /mnt/ext3 FBK: acmd export EXTRACT_UNSAFE_SYMLINKS=1; tar --zstd --warning=no-timestamp -x -C /mnt/ext3 FBK: ucp imx-image-multimedia-imx93evk.tar.zst t:- FBK: Sync FBK: ucmd umount /mnt/ext3 FBK: DONE 文件结构如下。 example_kernel_emmc.uuu Image imx-boot-imx93evk-sd.bin-flash_singleboot fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot imx93-11x11-evk.dtb imx-image-multimedia-imx93evk.rootfs.tar.zst 焚烧过程的日志信息如下: U-Boot SPL 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000) SOC: 0xa0009300 LC: 0x40010 M33 prepare ok Normal Boot Trying to boot from BOOTROM Boot Stage: USB boot Find img info 0x&88000000, size 416 Download 1610752, Total size 1611776 NOTICE: BL31: v2.6(release):lf-6.1.1-1.0.0-0-g616a4588f NOTICE: BL31: Built : 10:31:38, Mar 1 2023 U-Boot 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000) CPU: i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz) CPU: Consumer temperature grade (0C to 95C) at 46C Reset cause: POR (0x1) Model: NXP i.MX93 11X11 EVK board DRAM: 2 GiB tcpc_init: Can't find device id=0x52 setup_typec: tcpc portpd init failed, err=-19 tcpc_init: Can't find device id=0x51 setup_typec: tcpc port2 init failed, err=-19 tcpc_init: Can't find device id=0x50 setup_typec: tcpc port1 init failed, err=-19 pca953x gpio@22: Error reading output register Core: 204 devices, 28 uclasses, devicetree: separate MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from nowhere... OK [*]-Video Link 0adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 [0] lcd-controller@4ae30000, video [1] dsi@4ae10000, video_bridge [2] hdmi@3d, panel adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 In: serial Out: serial Err: serial BuildInfo: - ELE firmware version 0.0.9-9df0f503 MMC: no card present UID: 0x1d46516e 0xa9410d98 0x93a276bd 0xe691bc10 Detect USB boot. Will enter fastboot mode! Net: pca953x gpio@22: Error reading output register pca953x gpio@22: Error reading output register Warning: ethernet@42890000 (eth0) using random MAC address - d6:1f:33:20:03:1c pca953x gpio@22: Error reading output register pca953x gpio@22: Error reading output register Warning: ethernet@428a0000 (eth1) using random MAC address - 22:92:db:80:d8:ea eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME] Fastboot: Normal Boot from USB for mfgtools *** Warning - Use default environment for mfgtools , using default environment Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot auto; fi; Hit any key to stop autoboot: 0 ## Checking Image at 83800000 ... Legacy image found Image Name: fsl-image-mfgtool-initramfs-imx8 Created: 2011-04-05 23:00:00 UTC Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 11910836 Bytes = 11.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Run fastboot ... auto usb 0 UID: 0x1d46516e 0xa9410d98 0x93a276bd 0xe691bc10 Detect USB boot. Will enter fastboot mode! flash target is MMC:1 MMC: no card present MMC card init failed! MMC: no card present ** Block device MMC 1 not supported Detect USB boot. Will enter fastboot mode! flash target is MMC:0 Starting download of 1876992 bytes .............. downloading of 1876992 bytes finished writing to partition 'bootloader' Initializing 'bootloader' switch to partitions #1, OK mmc0(part 1) is current device Writing 'bootloader' MMC write: dev # 0, block # 0, count 3666 ... 3666 blocks written: OK Writing 'bootloader' DONE! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Set to BOOT_BUS_WIDTH = 0x2, RESET = 0x0, BOOT_MODE = 0x1 Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Starting download of 32117248 bytes .......................................................................... .......................................................................... .......................................................................... ....................... downloading of 32117248 bytes finished Detect USB boot. Will enter fastboot mode! Starting download of 43801 bytes downloading of 43801 bytes finished Detect USB boot. Will enter fastboot mode! Starting download of 11910900 bytes .......................................................................... ................ downloading of 11910900 bytes finished ## Loading init Ramdisk from Legacy Image at 83800000 ... Image Name: fsl-image-mfgtool-initramfs-imx8 Created: 2011-04-05 23:00:00 UTC Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 11910836 Bytes = 11.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000 Using Device Tree in place at 0000000083000000, end 000000008300db18 adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] [ 0.000000] Linux version 6.1.1+g29549c7073bf (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0.20220819) #1 SMP PREEMPT Thu Mar 2 14:54:17 UTC 2023 [ 0.000000] Machine model: NXP i.MX93 11X11 EVK board [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000b0000000, size 256 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4020000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdevbuffer@a4020000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4120000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node ele-reserved@a4120000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 256 MiB [ 0.000000] OF: reserved mem: initialized node ethosu_region@C0000000, compatible id shared-dma-pool [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] NUMA: NODE_DATA [mem 0xffbd3700-0xffbd5fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000080000000-0x0000000095ffffff] [ 0.000000] node 0: [mem 0x0000000098000000-0x00000000a3ffffff] [ 0.000000] node 0: [mem 0x00000000a4000000-0x00000000a421ffff] [ 0.000000] node 0: [mem 0x00000000a4220000-0x00000000ffffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] On node 0, zone DMA: 8192 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 20 pages/cpu s44520 r8192 d29208 u81920 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Virtualization Host Extensions [ 0.000000] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009 [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] alternatives: applying boot alternatives [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 507904 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: console=ttyLP0,115200 earlycon,115200 rdinit=/linuxrc clk_ignore_unused [ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off [ 0.000000] Memory: 1453904K/2064384K available (19584K kernel code, 1604K rwdata, 6712K rodata, 3328K init, 644K bss, 86192K reserved, 524288K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 960 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: GICv3 features: 16 PPIs [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000048040000 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.000309] Console: colour dummy device 80x25 [ 0.000364] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.000373] pid_max: default: 32768 minimum: 301 [ 0.000413] LSM: Security Framework initializing [ 0.000484] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.000493] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.001211] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 0.001615] cblist_init_generic: Setting adjustable number of callback queues. [ 0.001624] cblist_init_generic: Setting shift to 1 and lim to 1. [ 0.001670] cblist_init_generic: Setting shift to 1 and lim to 1. [ 0.001788] rcu: Hierarchical SRCU implementation. [ 0.001791] rcu: Max phase no-delay instances is 1000. [ 0.002539] EFI services will not be available. [ 0.002685] smp: Bringing up secondary CPUs ... [ 0.003029] Detected VIPT I-cache on CPU1 [ 0.003095] cacheinfo: Unable to detect cache hierarchy for CPU 1 [ 0.003105] GICv3: CPU1: found redistributor 100 region 0:0x0000000048060000 [ 0.003142] CPU1: Booted secondary processor 0x0000000100 [0x412fd050] [ 0.003229] smp: Brought up 1 node, 2 CPUs [ 0.003234] SMP: Total of 2 processors activated. [ 0.003238] CPU features: detected: 32-bit EL0 Support [ 0.003240] CPU features: detected: 32-bit EL1 Support [ 0.003244] CPU features: detected: Data cache clean to the PoU not required for I/D coherence [ 0.003247] CPU features: detected: Common not Private translations [ 0.003249] CPU features: detected: CRC32 instructions [ 0.003253] CPU features: detected: RCpc load-acquire (LDAPR) [ 0.003255] CPU features: detected: LSE atomic instructions [ 0.003257] CPU features: detected: Privileged Access Never [ 0.003259] CPU features: detected: RAS Extension Support [ 0.003265] CPU features: detected: Speculative Store Bypassing Safe (SSBS) [ 0.003313] CPU: All CPU(s) started at EL2 [ 0.003315] alternatives: applying system-wide alternatives [ 0.007599] devtmpfs: initialized [ 0.012159] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.012179] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.020304] pinctrl core: initialized pinctrl subsystem [ 0.021503] DMI not present or invalid. [ 0.021949] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.022749] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations [ 0.022890] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.022983] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.023035] audit: initializing netlink subsys (disabled) [ 0.023191] audit: type=2000 audit(0.020:1): state=initialized audit_enabled=0 res=1 [ 0.023541] thermal_sys: Registered thermal governor 'step_wise' [ 0.023546] thermal_sys: Registered thermal governor 'power_allocator' [ 0.023575] cpuidle: using governor menu [ 0.023744] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.023789] ASID allocator initialised with 65536 entries [ 0.024382] Serial: AMBA PL011 UART driver [ 0.024424] imx mu driver is registered. [ 0.024435] imx rpmsg driver is registered. [ 0.029818] imx93-pinctrl 443c0000.pinctrl: initialized IMX pinctrl driver [ 0.036057] platform 4ae30000.lcd-controller: Fixing up cyclic dependency with 4ae10000.dsi [ 0.039167] KASLR disabled due to lack of seed [ 0.050510] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages [ 0.050519] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page [ 0.050522] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages [ 0.050524] HugeTLB: 508 KiB vmemmap can be freed for a 32.0 MiB page [ 0.050527] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages [ 0.050529] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page [ 0.050532] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages [ 0.050534] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page [ 0.052231] ACPI: Interpreter disabled. [ 0.053090] iommu: Default domain type: Translated [ 0.053100] iommu: DMA domain TLB invalidation policy: strict mode [ 0.053318] SCSI subsystem initialized [ 0.053622] usbcore: registered new interface driver usbfs [ 0.053650] usbcore: registered new interface driver hub [ 0.053669] usbcore: registered new device driver usb [ 0.054429] mc: Linux media interface: v0.10 [ 0.054461] videodev: Linux video capture interface: v2.00 [ 0.054497] pps_core: LinuxPPS API ver. 1 registered [ 0.054500] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.054508] PTP clock support registered [ 0.054601] EDAC MC: Ver: 3.0.0 [ 0.055719] FPGA manager framework [ 0.055781] Advanced Linux Sound Architecture Driver Initialized. [ 0.056190] Bluetooth: Core ver 2.22 [ 0.056218] NET: Registered PF_BLUETOOTH protocol family [ 0.056220] Bluetooth: HCI device and connection manager initialized [ 0.056226] Bluetooth: HCI socket layer initialized [ 0.056230] Bluetooth: L2CAP socket layer initialized [ 0.056244] Bluetooth: SCO socket layer initialized [ 0.056579] vgaarb: loaded [ 0.057072] clocksource: Switched to clocksource arch_sys_counter [ 0.057247] VFS: Disk quotas dquot_6.6.0 [ 0.057275] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.057384] pnp: PnP ACPI: disabled [ 0.062200] NET: Registered PF_INET protocol family [ 0.062459] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.063693] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 0.063721] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.063730] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.063799] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear) [ 0.064220] TCP: Hash tables configured (established 16384 bind 16384) [ 0.064337] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.064375] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.064523] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.064896] RPC: Registered named UNIX socket transport module. [ 0.064902] RPC: Registered udp transport module. [ 0.064904] RPC: Registered tcp transport module. [ 0.064906] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.065481] PCI: CLS 0 bytes, default 64 [ 0.065671] Unpacking initramfs... [ 0.077164] hw perfevents: enabled with armv8_cortex_a55 PMU driver, 7 counters available [ 0.077791] kvm [1]: IPA Size Limit: 40 bits [ 0.077823] kvm [1]: GICv3: no GICV resource entry [ 0.077826] kvm [1]: disabling GICv2 emulation [ 0.077840] kvm [1]: GIC system register CPU interface enabled [ 0.077945] kvm [1]: vgic interrupt IRQ9 [ 0.077995] kvm [1]: VHE mode initialized successfully [ 0.079075] Initialise system trusted keyrings [ 0.079368] workingset: timestamp_bits=42 max_order=19 bucket_order=0 [ 0.083800] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.084377] NFS: Registering the id_resolver key type [ 0.084427] Key type id_resolver registered [ 0.084430] Key type id_legacy registered [ 0.084478] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.084483] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 0.084498] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.084799] 9p: Installing v9fs 9p2000 file system support [ 0.110306] Key type asymmetric registered [ 0.110323] Asymmetric key parser 'x509' registered [ 0.110421] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 0.110426] io scheduler mq-deadline registered [ 0.110430] io scheduler kyber registered [ 0.115631] EINJ: ACPI disabled. [ 0.121059] Bus freq driver module loaded [ 0.127423] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.130859] 44380000.serial: ttyLP0 at MMIO 0x44380010 (irq = 18, base_baud = 1500000) is a FSL_LPUART [ 0.579725] Freeing initrd memory: 11624K [ 0.587591] printk: console [ttyLP0] enabled [ 1.297743] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 1.307341] loop: module loaded [ 1.311565] of_reserved_mem_lookup() returned NULL [ 1.316484] megasas: 07.719.03.00-rc1 [ 1.321853] imx ahci driver is registered. [ 1.329636] tun: Universal TUN/TAP device driver, 1.6 [ 1.335399] thunder_xcv, ver 1.0 [ 1.338673] thunder_bgx, ver 1.0 [ 1.341914] nicpf, ver 1.0 [ 1.345372] pps pps0: new PPS source ptp0 [ 1.354869] fec 42890000.ethernet eth0: registered PHC device 0 [ 1.362443] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.369679] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.375062] hclge is initializing [ 1.378397] e1000: Intel(R) PRO/1000 Network Driver [ 1.383269] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.389040] e1000e: Intel(R) PRO/1000 Network Driver [ 1.394000] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.399932] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.405330] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.410916] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 1.417174] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.423285] sky2: driver version 1.30 [ 1.427579] imx-dwmac 428a0000.ethernet: IRQ eth_lpi not found [ 1.433752] imx-dwmac 428a0000.ethernet: User ID: 0x10, Synopsys ID: 0x52 [ 1.440551] imx-dwmac 428a0000.ethernet: DWMAC4/5 [ 1.445333] imx-dwmac 428a0000.ethernet: DMA HW capability register supported [ 1.452455] imx-dwmac 428a0000.ethernet: RX Checksum Offload Engine supported [ 1.459578] imx-dwmac 428a0000.ethernet: TX Checksum insertion supported [ 1.466268] imx-dwmac 428a0000.ethernet: Wake-Up On Lan supported [ 1.472401] imx-dwmac 428a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 1.480057] imx-dwmac 428a0000.ethernet: device MAC address 86:81:0f:94:98:19 [ 1.487205] imx-dwmac 428a0000.ethernet: Enabled L3L4 Flow TC (entries=8) [ 1.493987] imx-dwmac 428a0000.ethernet: Enabled RFS Flow TC (entries=10) [ 1.500766] imx-dwmac 428a0000.ethernet: Enabling HW TC (entries=256, max_off=256) [ 1.508321] imx-dwmac 428a0000.ethernet: Using 32 bits DMA width [ 1.518225] usbcore: registered new interface driver r8152 [ 1.524089] VFIO - User Level meta-driver version: 0.3 [ 1.531938] usbcore: registered new interface driver uas [ 1.537317] usbcore: registered new interface driver usb-storage [ 1.543397] usbcore: registered new interface driver usbserial_generic [ 1.549930] usbserial: USB Serial support registered for generic [ 1.555949] usbcore: registered new interface driver ftdi_sio [ 1.561690] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.569004] usbcore: registered new interface driver usb_serial_simple [ 1.575530] usbserial: USB Serial support registered for carelink [ 1.581622] usbserial: USB Serial support registered for zio [ 1.587281] usbserial: USB Serial support registered for funsoft [ 1.593287] usbserial: USB Serial support registered for flashloader [ 1.599640] usbserial: USB Serial support registered for google [ 1.605559] usbserial: USB Serial support registered for libtransistor [ 1.612090] usbserial: USB Serial support registered for vivopay [ 1.618095] usbserial: USB Serial support registered for moto_modem [ 1.624358] usbserial: USB Serial support registered for motorola_tetra [ 1.630970] usbserial: USB Serial support registered for nokia [ 1.636807] usbserial: USB Serial support registered for novatel_gps [ 1.643163] usbserial: USB Serial support registered for hp4x [ 1.648922] usbserial: USB Serial support registered for suunto [ 1.654845] usbserial: USB Serial support registered for siemens_mpi [ 1.661206] usbcore: registered new interface driver usb_ehset_test [ 1.669805] bbnsm_pwrkey 44440000.bbnsm:pwrkey: KEY_POWER without setting in dts [ 1.678054] input: 44440000.bbnsm:pwrkey as /devices/platform/soc@0/44000000.bus/44440000.bbnsm/44440000.bbnsm:pwrkey/input/input0 [ 1.693496] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0 [ 1.700063] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:40:35 UTC (2435) [ 1.709596] i2c_dev: i2c /dev entries driver [ 1.716720] imx7ulp-wdt 42490000.wdog: imx93 wdt probe [ 1.750651] Bluetooth: HCI UART driver ver 2.3 [ 1.755119] Bluetooth: HCI UART protocol H4 registered [ 1.760253] Bluetooth: HCI UART protocol BCSP registered [ 1.765575] Bluetooth: HCI UART protocol LL registered [ 1.770704] Bluetooth: HCI UART protocol ATH3K registered [ 1.776103] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.782493] Bluetooth: HCI UART protocol Broadcom registered [ 1.788157] Bluetooth: HCI UART protocol QCA registered [ 1.794787] sdhci: Secure Digital Host Controller Interface driver [ 1.800994] sdhci: Copyright(c) Pierre Ossman [ 1.805883] Synopsys Designware Multimedia Card Interface Driver [ 1.812371] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.819532] ledtrig-cpu: registered to indicate activity on CPUs [ 1.826499] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 1.833373] usbcore: registered new interface driver usbhid [ 1.838953] usbhid: USB HID core driver [ 1.844379] ethosu ethosu: assigned reserved memory node ethosu_region@C0000000 [ 1.850056] mmc0: SDHCI controller on 42850000.mmc [42850000.mmc] using ADMA [ 1.891274] cs_system_cfg: CoreSight Configuration manager initialised [ 1.898992] optee: probing for conduit method. [ 1.903467] optee: revision 3.19 (ad4e8389) [ 1.903903] optee: dynamic shared memory is enabled [ 1.913286] optee: initialized driver [ 1.920587] NET: Registered PF_LLC protocol family [ 1.926018] NET: Registered PF_INET6 protocol family [ 1.931886] Segment Routing with IPv6 [ 1.935621] In-situ OAM (IOAM) with IPv6 [ 1.939623] NET: Registered PF_PACKET protocol family [ 1.944709] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 1.957852] Bluetooth: RFCOMM TTY layer initialized [ 1.962736] Bluetooth: RFCOMM socket layer initialized [ 1.967882] Bluetooth: RFCOMM ver 1.11 [ 1.971628] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 1.975581] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 1.976925] Bluetooth: BNEP filters: protocol multicast [ 1.983735] mmcblk0: mmc0:0001 58A398 7.28 GiB [ 1.988480] Bluetooth: BNEP socket layer initialized [ 1.994157] mmcblk0: p1 p2 [ 1.997954] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.001220] mmcblk0boot0: mmc0:0001 58A398 4.00 MiB [ 2.006645] Bluetooth: HIDP socket layer initialized [ 2.012467] mmcblk0boot1: mmc0:0001 58A398 4.00 MiB [ 2.016733] 8021q: 802.1Q VLAN Support v1.8 [ 2.022269] mmcblk0rpmb: mmc0:0001 58A398 4.00 MiB, chardev (234:0) [ 2.025790] lib80211: common routines for IEEE802.11 drivers [ 2.037706] 9pnet: Installing 9P2000 support [ 2.042071] Key type dns_resolver registered [ 2.046761] registered taskstats version 1 [ 2.050882] Loading compiled-in X.509 certificates [ 2.069935] usb_phy_generic soc@0:usbphynop1: supply vcc not found, using dummy regulator [ 2.078259] usb_phy_generic soc@0:usbphynop1: dummy supplies not allowed for exclusive requests [ 2.087063] usb_phy_generic soc@0:usbphynop2: supply vcc not found, using dummy regulator [ 2.095411] usb_phy_generic soc@0:usbphynop2: dummy supplies not allowed for exclusive requests [ 2.113448] gpio gpiochip0: (43810080.gpio): not an immutable chip, please consider fixing it! [ 2.122542] gpio gpiochip1: (43820080.gpio): not an immutable chip, please consider fixing it! [ 2.131592] gpio gpiochip2: (43830080.gpio): not an immutable chip, please consider fixing it! [ 2.140641] gpio gpiochip3: (47400080.gpio): not an immutable chip, please consider fixing it! [ 2.154906] remoteproc remoteproc0: imx-rproc is available [ 2.162795] i2c 0-003d: Fixing up cyclic dependency with 4ae10000.dsi [ 2.169394] adv7511 0-003d: supply avdd not found, using dummy regulator [ 2.176171] adv7511 0-003d: supply dvdd not found, using dummy regulator [ 2.182901] adv7511 0-003d: supply pvdd not found, using dummy regulator [ 2.189618] adv7511 0-003d: supply a2vdd not found, using dummy regulator [ 2.196414] adv7511 0-003d: supply v3p3 not found, using dummy regulator [ 2.203140] adv7511 0-003d: supply v1p2 not found, using dummy regulator [ 2.210309] adv7511 0-003d: Probe failed. Remote port 'dsi@4ae10000' disabled [ 2.217833] st_lsm6dsx_i2c 0-006a: supply vdd not found, using dummy regulator [ 2.225158] st_lsm6dsx_i2c 0-006a: supply vddio not found, using dummy regulator [ 2.289539] st_lsm6dsx_i2c 0-006a: failed to read whoami register [ 2.295812] st_lsm6dsx_i2c: probe of 0-006a failed with error -5 [ 2.301895] i2c i2c-0: LPI2C adapter registered [ 2.307942] pca953x 1-0022: supply vcc not found, using dummy regulator [ 2.314705] pca953x 1-0022: using AI [ 2.318364] pca953x 1-0022: failed writing register [ 2.323346] pca953x: probe of 1-0022 failed with error -5 [ 2.329016] adp5585 1-0034: Failed to read reg 0x00, ret is -5 [ 2.334871] adp5585: probe of 1-0034 failed with error -5 [ 2.340359] i2c i2c-1: LPI2C adapter registered [ 2.345948] i2c 2-0050: Fixing up cyclic dependency with 4c100000.usb [ 3.357110] tcpci: probe of 2-0050 failed with error -110 [ 3.362704] i2c 2-0051: Fixing up cyclic dependency with 4c200000.usb [ 4.377113] tcpci: probe of 2-0051 failed with error -110 [ 5.389069] adp5585 2-0034: Failed to read reg 0x00, ret is -110 [ 5.395082] adp5585: probe of 2-0034 failed with error -110 [ 5.400885] i2c 2-003c: Fixing up cyclic dependency with 4ae00000.csi [ 5.407546] i2c i2c-2: LPI2C adapter registered [ 5.414180] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 5.422156] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/dsi@4ae10000 to encoder DSI-34: -19 [ 5.432166] dw-mipi-dsi-imx 4ae10000.dsi: [drm:dw_mipi_dsi_imx_bind] *ERROR* failed to attach bridge: -19 [ 5.441725] imx-drm display-subsystem: failed to bind 4ae10000.dsi (ops dw_mipi_dsi_imx_ops): -19 [ 5.450869] imx-drm display-subsystem: adev bind failed: -19 [ 5.456538] dw-mipi-dsi-imx 4ae10000.dsi: [drm:dw_mipi_dsi_imx_probe] *ERROR* failed to register component: -19 [ 5.478535] sdhci-esdhc-imx 42860000.mmc: Got CD GPIO [ 5.479882] dwc-mipi-csi2-host 4ae00000.csi: lanes: 2, name: mxc-mipi-csi2.0 [ 5.498291] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 5.511405] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 5.518188] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 5.521123] clk: Not disabling unused clocks [ 5.526882] mmc1: SDHCI controller on 42860000.mmc [42860000.mmc] using ADMA [ 5.531085] ALSA device list: [ 5.538113] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 5.541074] No soundcards found. [ 5.554051] Freeing unused kernel memory: 3328K [ 5.573123] Run /linuxrc as init process Found New UDC: ci_hdrc.0 ci_hdrc.0 0 Found New UDC: ci_hdrc.1 ci_hdrc.1 1 ffs.utp0 [ 5.621381] file system registered ffs.utp1 run utp at /dev/usb-utp0/ep0 . run utp at /dev/usb-utp1/ep0 [ 5.642106] read descriptors uuu fastboot cli[ 5.646482] read descriptors ent 1.0.0 [built [ 5.650846] read strings Aug 17 2022 19:49[ 5.650846] read strings :14] Start init usb uuu fastboot client 1.0.0 [built Aug 17 2022 19:49:14] Start init usb write string write string Start handle command Start handle command 目前,它仍然停留在"开始处理命令" ,我不知道如何纠正这种情况。我恳请您给予指导,或提供一个 i.mx93 可用的 example_kernel_emmc.uuu。我热切地等待着您的回复,并祝您有愉快的一天。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 嗨,@橘子熊 您可以参考 i.MX_Porting_Guide(适用于 i.MX 应用处理器的嵌入式 Linux | 恩智浦半导体) 顺祝商祺! 哈维
記事全体を表示
无法使用 Segger j-link V9 调试器调试 S32k311 微控制器 我一直在使用 Elekronika India 的评估板开发基于 s32k311 MCU 的 18s 电池管理系统 解决方案。Segger j-link V9-G JTAG 调试器用于闪存和调试。 但当我们调试示例代码时,闪存闪烁后,PC 进入随机 RAM 位置,而不是主函数。附上图片供您参考。除主断点外,没有其他断点。但电脑没有停在主内存,而是转到随机内存位置并停在那里。我用 S32k311 的另一个示例代码进行了尝试,得到了相同的输出结果。   请提出解决方案。   Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger 问题出在 JTAG 适配器板上的 Segger 连接器上。它无法在调试会话之前 RESET 控制器。现在已经解决了。 Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger 你好 但是,当我们调试示例代码时,闪存闪烁后,PC 会进入随机 RAM 位置,而不是进入主函数 好吧,我觉得很奇怪。内核将执行加载的指令。而不是一些随意的人。 在您的软件系统中必须执行一些分支(跳转)到该 RAM 位置。要执行分支,必须在核心寄存器中定义 RAM 位置。 如果按步骤进行调试,就会看到指向 RAM 的分支发生的确切位置及其先决条件。 但电脑没有停在主内存,而是转到随机内存位置并停在那里。我用 S32k311 的另一个示例代码进行了尝试,得到了相同的输出结果。 是的,如果没有达到主断点,就不会在主断点停止。 由于另一个示例给出了相同的结果,因此如果您使用我们的 EVB,可能是电路板上的一些跳线设置。 我们为 EVB 提供了入门指南,其中介绍了所有必要的硬件设置。 但启动调试只会告诉你问题出在哪里。 顺祝商祺! Peter Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger 请查找 gdb 服务器日志以供参考
記事全体を表示
カスタマイズした U-Boot を i.mx9352 ボードに更新するにはどうすればよいですか?消去と NXP 様、i.mx9352 のボード上でカスタム変更された U-Boot を更新するプロセスについて問い合わせたいと思います。ボードを消去して、独自の U-Boot バージョンでフラッシュする方法を教えてください。 i.MX 93 では、複数の要素が必要です。 • imx-boot(imx-mkimageによって構築)には、SPL、U-Boot、Arm Trusted Firmware、OP-TEE、Sentinelが含まれています。 ファームウェア、DDR PHYファームウェア 現時点では、SPL、Arm Trusted Firmware、OP-TEE、Sentinel Firmware、DDR PHY Firmware を変更するつもりはなく、u-boot のみに変更を加えたいと思っています。u-boot をコンパイルすることによって生成されるどのファイルをボードのパーティションで更新する必要がありますか?参照できる手順はありますか?i.mx6u の場合、参照命令は「dd if=u-boot-imx6ull-14x14-ddr512-emmc.imx of=/dev/mmcblk1boot0 bs=1024 seek=1 conv=fsync」です。SO、i.mx93 の u-boot アップデート手順は何でしょうか?ご返信をお待ちしております。ありがとう、そして楽しい人生を。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing こんにちは、 @orange-bear 。 この問題の解決策は見つかりましたか? imx93 でも同じ問題が発生しています。initramfs を起動した後に FBK ID がないので、uuu から FBK コマンドを実行できません。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing イメージファイルとimx93-11x11-evk.dtbで問題が発生しました。evk_example_kernel_emmc.uuu を使用して 、独自のイメージファイルとimx93-11x11-evk.dtb をEVKボードに書き込も うとしました が、「Start handle command」の段階で停止してしまいます。TFTP を使用してこれらの2つのファイルをテストしたところ、正常に動作しました。 また、/run/media/boot-mmcblk0p1に置き換えて試したところ、問題なく動作しました。SO、evk_example_kernel_emmc.uuu を使用して独自のイメージファイルとimx93-11x11-evk.dtbをEVKボードに 書き込む場合 、カーネルとデバイスツリーのどの設定を変更する必要がありますか? Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing NXP iMX93 EVK 開発ボードと公式イメージ パッケージを使用します。example_kernel_emmc.uuu を使用すると、次の印刷された情報からもわかるように、好ましい結果が得られます。 ...... uuu fastboot cli[ 3.160728] read strings ent 1.0.0 [built [ 3.164686] read strings Aug 17 2022 19:49:14] Start init usb uuu fastboot client 1.0.0 [built Aug 17 2022 19:49:14] Start init usb write string write string Start handle command Start handle command run shell cmd: while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "wait for /dev/mmcblk*boot* appear"; done; run shell cmd: dev=`ls /dev/mmcblk*boot*`; dev=($dev); dev=${dev[0]}; dev=${dev#/dev/mmcblk}; dev=${dev%boot*}; echo $dev > /tmp/mmcdev; run shell cmd: mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=512 count=1 1+0 records in 1+0 records out 512 bytes copied, 0.00157254 s, 326 kB/s run shell cmd: mmc=`cat /tmp/mmcdev`; PARTSTR=$'10M,500M,0c\n600M,,83\n'; echo "$PARTSTR" | sfdisk --force /dev/mmcblk${mmc} Partition #1 contains a vfat signature. Partition #2 contains a ext3 signature. ミラーが次のシェル コマンドを実行しない理由がわかりません: while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "Waiting for the appearance of /dev/mmcblk*boot*"; done; Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing 申し訳ありませんが、あなたの意図を誤解していたようです。前回の発言を明確にさせてください。 imx-image-multimedia-imx93evk.wic ファイルを更新するのではなく、コマンドまたはスクリプトを使用して imx-image-multimedia-imx93evk.tar.zst を個別に更新したいと思います。 「fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot」入手したイメージ パッケージは、NXP の公式 Web サイトからのものです。これは、「example_kernel_emmc.uuu」の使用法に基づいています。現在、実行は「FB: acmd ${kboot} ${loadaddr} ${initrd_addr} ${fdt_addr} 」で停止します。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing これらのログから、uuu のダウンロードはまだ完了していないようです。カーネル イメージをどのように処理するかはわかりません。 例の使用方法と同様に、実行したのと同じ以下のコマンドを試すこともCAN。ただし、少なくとも、読み込みと起動に関する現在の問題のトラブルシューティングにはCAN役立ちます。 uuu.exe -v -b emmc_all imx-boot-imx93evk-sd.bin-flash_singleboot imx-image-multimedia-imx93evk.wic よろしくお願いいたします。 Harvey Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing ご返信ありがとうございます。 L6.1.1_1.0.0_MX93-BETA2/samples ディレクトリに、私の要件を満たす example_kernel_emmc.uuu というスクリプトがあることが分かりました。IMX93 と互換性を持たせるために example_kernel_emmc.uuu を変更しようとしています。 修正された example_kernel_emmc.uuu ファイルは次のとおりです。 uuu_version 1.2.39 # Please Replace below items with actually file names # @_flash.bin | boot loader, here is imx-boot-imx93evk-sd.bin-flash_singleboot # @_Image | kernel image, arm64 is Image, arm32 it is zImage, here is Image # @_board.dtb | board dtb file, here is imx93-11x11-evk.dtb # @_initramfs.cpio.gz.uboot | mfgtool init ramfs, here is fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot # @_rootfs.tar.zst | rootfs, here is imx-image-multimedia-imx93evk.tar.zst # @_uTee.tar | optee image, put dummy _uTee.tar file here if platform is not MX6/MX7* # This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ SDP: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot # This command will be run when ROM support stream mode # i.MX8QXP, i.MX8QM SDPS: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot # SDPU will be deprecated. please use SDPV instead of SDPU # { SDPU: delay 1000 SDPU: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -offset 0x57c00 SDPU: jump # } # These commands will be run when use SPL and will be skipped if no spl # if (SPL support SDPV) # { SDPV: delay 1000 SDPV: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -skipspl SDPV: jump # } # use uboot burn bootloader to eMMC # becaue difference chip, offset is difference # you can use kernel to do that for specific boards FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: flash bootloader imx-boot-imx93evk-sd.bin-flash_singleboot FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi; FB: ucmd setenv emmc_cmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0 FB: ucmd if test "${emmc_skip_fb}" != "yes"; then run emmc_cmd; fi FB: ucmd setenv emmc_cmd mmc bootbus ${emmc_dev} 2 0 1; FB: ucmd if test "${emmc_skip_fb}" != "yes"; then run emmc_cmd; fi FB: ucmd setenv fastboot_buffer ${loadaddr} FB: download -f Image FB: ucmd setenv fastboot_buffer ${fdt_addr} FB: download -f imx93-11x11-evk.dtb FB: ucmd setenv fastboot_buffer ${initrd_addr} FB: download -f fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot #FB: ucmd setenv bootargs console=${console},${baudrate} earlycon=${earlycon},${baudrate} FB: acmd ${kboot} ${loadaddr} ${initrd_addr} ${fdt_addr} # get mmc dev number from kernel command line # Wait for emmc FBK: ucmd while [ ! -e /dev/mmcblk*boot0 ]; do sleep 1; echo "wait for /dev/mmcblk*boot* appear"; done; # serach emmc device number, if your platform have more than two emmc chip, please echo dev number >/tmp/mmcdev FBK: ucmd dev=`ls /dev/mmcblk*boot*`; dev=($dev); dev=${dev[0]}; dev=${dev#/dev/mmcblk}; dev=${dev%boot*}; echo $dev > /tmp/mmcdev; # dd to clear the possible MBR FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=512 count=1 # create partition FBK: ucmd mmc=`cat /tmp/mmcdev`; PARTSTR=$'10M,500M,0c\n600M,,83\n'; echo "$PARTSTR" | sfdisk --force /dev/mmcblk${mmc} FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/dev/zero of=/dev/mmcblk${mmc} bs=1k seek=4096 count=1 FBK: ucmd sync # you can enable below command to write boot partition. but offset is difference at difference platform #FBK: ucmd mmc=`cat /tmp/mmcdev`; echo 0 > /sys/block/mmcblk${mmc}boot0/force_ro #FBK: ucp imx-boot-imx93evk-sd.bin-flash_singleboot t:/tmp #FBK: ucmd mmc=`cat /tmp/mmcdev`; dd if=/tmp/imx-boot-imx93evk-sd.bin-flash_singleboot of=/dev/mmc${mmc}boot0 bs=1K seek=32 #FBK: ucmd mmc=`cat /tmp/mmcdev`; echo 1 > /sys/block/mmcblk${mmc}boot0/force_ro FBK: ucmd mmc=`cat /tmp/mmcdev`; while [ ! -e /dev/mmcblk${mmc}p1 ]; do sleep 1; done FBK: ucmd mmc=`cat /tmp/mmcdev`; mkfs.vfat /dev/mmcblk${mmc}p1 FBK: ucmd mmc=`cat /tmp/mmcdev`; mkdir -p /mnt/fat FBK: ucmd mmc=`cat /tmp/mmcdev`; mount -t vfat /dev/mmcblk${mmc}p1 /mnt/fat FBK: ucp Image t:/mnt/fat FBK: ucp imx93-11x11-evk.dtb t:/mnt/fat #FBK: ucp _uTee.tar t:/tmp/op.tar FBK: ucmd tar --no-same-owner -xf /tmp/op.tar -C /mnt/fat FBK: ucmd umount /mnt/fat FBK: ucmd mmc=`cat /tmp/mmcdev`; mkfs.ext3 -F -E nodiscard /dev/mmcblk${mmc}p2 FBK: ucmd mkdir -p /mnt/ext3 FBK: ucmd mmc=`cat /tmp/mmcdev`; mount /dev/mmcblk${mmc}p2 /mnt/ext3 FBK: acmd export EXTRACT_UNSAFE_SYMLINKS=1; tar --zstd --warning=no-timestamp -x -C /mnt/ext3 FBK: ucp imx-image-multimedia-imx93evk.tar.zst t:- FBK: Sync FBK: ucmd umount /mnt/ext3 FBK: DONE ファイルの構造は次のように表されます。 example_kernel_emmc.uuu Image imx-boot-imx93evk-sd.bin-flash_singleboot fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.zst.u-boot imx93-11x11-evk.dtb imx-image-multimedia-imx93evk.rootfs.tar.zst 書き込みプロセスのログ情報は次のとおりです。 U-Boot SPL 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000) SOC: 0xa0009300 LC: 0x40010 M33 prepare ok Normal Boot Trying to boot from BOOTROM Boot Stage: USB boot Find img info 0x&88000000, size 416 Download 1610752, Total size 1611776 NOTICE: BL31: v2.6(release):lf-6.1.1-1.0.0-0-g616a4588f NOTICE: BL31: Built : 10:31:38, Mar 1 2023 U-Boot 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000) CPU: i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz) CPU: Consumer temperature grade (0C to 95C) at 46C Reset cause: POR (0x1) Model: NXP i.MX93 11X11 EVK board DRAM: 2 GiB tcpc_init: Can't find device id=0x52 setup_typec: tcpc portpd init failed, err=-19 tcpc_init: Can't find device id=0x51 setup_typec: tcpc port2 init failed, err=-19 tcpc_init: Can't find device id=0x50 setup_typec: tcpc port1 init failed, err=-19 pca953x gpio@22: Error reading output register Core: 204 devices, 28 uclasses, devicetree: separate MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from nowhere... OK [*]-Video Link 0adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 [0] lcd-controller@4ae30000, video [1] dsi@4ae10000, video_bridge [2] hdmi@3d, panel adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 In: serial Out: serial Err: serial BuildInfo: - ELE firmware version 0.0.9-9df0f503 MMC: no card present UID: 0x1d46516e 0xa9410d98 0x93a276bd 0xe691bc10 Detect USB boot. Will enter fastboot mode! Net: pca953x gpio@22: Error reading output register pca953x gpio@22: Error reading output register Warning: ethernet@42890000 (eth0) using random MAC address - d6:1f:33:20:03:1c pca953x gpio@22: Error reading output register pca953x gpio@22: Error reading output register Warning: ethernet@428a0000 (eth1) using random MAC address - 22:92:db:80:d8:ea eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME] Fastboot: Normal Boot from USB for mfgtools *** Warning - Use default environment for mfgtools , using default environment Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot auto; fi; Hit any key to stop autoboot: 0 ## Checking Image at 83800000 ... Legacy image found Image Name: fsl-image-mfgtool-initramfs-imx8 Created: 2011-04-05 23:00:00 UTC Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 11910836 Bytes = 11.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Run fastboot ... auto usb 0 UID: 0x1d46516e 0xa9410d98 0x93a276bd 0xe691bc10 Detect USB boot. Will enter fastboot mode! flash target is MMC:1 MMC: no card present MMC card init failed! MMC: no card present ** Block device MMC 1 not supported Detect USB boot. Will enter fastboot mode! flash target is MMC:0 Starting download of 1876992 bytes .............. downloading of 1876992 bytes finished writing to partition 'bootloader' Initializing 'bootloader' switch to partitions #1, OK mmc0(part 1) is current device Writing 'bootloader' MMC write: dev # 0, block # 0, count 3666 ... 3666 blocks written: OK Writing 'bootloader' DONE! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Set to BOOT_BUS_WIDTH = 0x2, RESET = 0x0, BOOT_MODE = 0x1 Detect USB boot. Will enter fastboot mode! Detect USB boot. Will enter fastboot mode! Starting download of 32117248 bytes .......................................................................... .......................................................................... .......................................................................... ....................... downloading of 32117248 bytes finished Detect USB boot. Will enter fastboot mode! Starting download of 43801 bytes downloading of 43801 bytes finished Detect USB boot. Will enter fastboot mode! Starting download of 11910900 bytes .......................................................................... ................ downloading of 11910900 bytes finished ## Loading init Ramdisk from Legacy Image at 83800000 ... Image Name: fsl-image-mfgtool-initramfs-imx8 Created: 2011-04-05 23:00:00 UTC Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 11910836 Bytes = 11.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000 Using Device Tree in place at 0000000083000000, end 000000008300db18 adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c fail to probe panel device hdmi@3d fail to get display timings probe video device failed, ret -19 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] [ 0.000000] Linux version 6.1.1+g29549c7073bf (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0.20220819) #1 SMP PREEMPT Thu Mar 2 14:54:17 UTC 2023 [ 0.000000] Machine model: NXP i.MX93 11X11 EVK board [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000b0000000, size 256 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4020000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdevbuffer@a4020000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a4120000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node ele-reserved@a4120000, compatible id shared-dma-pool [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 256 MiB [ 0.000000] OF: reserved mem: initialized node ethosu_region@C0000000, compatible id shared-dma-pool [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] NUMA: NODE_DATA [mem 0xffbd3700-0xffbd5fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000080000000-0x0000000095ffffff] [ 0.000000] node 0: [mem 0x0000000098000000-0x00000000a3ffffff] [ 0.000000] node 0: [mem 0x00000000a4000000-0x00000000a421ffff] [ 0.000000] node 0: [mem 0x00000000a4220000-0x00000000ffffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff] [ 0.000000] On node 0, zone DMA: 8192 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 20 pages/cpu s44520 r8192 d29208 u81920 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Virtualization Host Extensions [ 0.000000] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009 [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] alternatives: applying boot alternatives [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 507904 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: console=ttyLP0,115200 earlycon,115200 rdinit=/linuxrc clk_ignore_unused [ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off [ 0.000000] Memory: 1453904K/2064384K available (19584K kernel code, 1604K rwdata, 6712K rodata, 3328K init, 644K bss, 86192K reserved, 524288K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 960 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: GICv3 features: 16 PPIs [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000048040000 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.000309] Console: colour dummy device 80x25 [ 0.000364] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.000373] pid_max: default: 32768 minimum: 301 [ 0.000413] LSM: Security Framework initializing [ 0.000484] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.000493] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.001211] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 0.001615] cblist_init_generic: Setting adjustable number of callback queues. [ 0.001624] cblist_init_generic: Setting shift to 1 and lim to 1. [ 0.001670] cblist_init_generic: Setting shift to 1 and lim to 1. [ 0.001788] rcu: Hierarchical SRCU implementation. [ 0.001791] rcu: Max phase no-delay instances is 1000. [ 0.002539] EFI services will not be available. [ 0.002685] smp: Bringing up secondary CPUs ... [ 0.003029] Detected VIPT I-cache on CPU1 [ 0.003095] cacheinfo: Unable to detect cache hierarchy for CPU 1 [ 0.003105] GICv3: CPU1: found redistributor 100 region 0:0x0000000048060000 [ 0.003142] CPU1: Booted secondary processor 0x0000000100 [0x412fd050] [ 0.003229] smp: Brought up 1 node, 2 CPUs [ 0.003234] SMP: Total of 2 processors activated. [ 0.003238] CPU features: detected: 32-bit EL0 Support [ 0.003240] CPU features: detected: 32-bit EL1 Support [ 0.003244] CPU features: detected: Data cache clean to the PoU not required for I/D coherence [ 0.003247] CPU features: detected: Common not Private translations [ 0.003249] CPU features: detected: CRC32 instructions [ 0.003253] CPU features: detected: RCpc load-acquire (LDAPR) [ 0.003255] CPU features: detected: LSE atomic instructions [ 0.003257] CPU features: detected: Privileged Access Never [ 0.003259] CPU features: detected: RAS Extension Support [ 0.003265] CPU features: detected: Speculative Store Bypassing Safe (SSBS) [ 0.003313] CPU: All CPU(s) started at EL2 [ 0.003315] alternatives: applying system-wide alternatives [ 0.007599] devtmpfs: initialized [ 0.012159] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.012179] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.020304] pinctrl core: initialized pinctrl subsystem [ 0.021503] DMI not present or invalid. [ 0.021949] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.022749] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations [ 0.022890] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.022983] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.023035] audit: initializing netlink subsys (disabled) [ 0.023191] audit: type=2000 audit(0.020:1): state=initialized audit_enabled=0 res=1 [ 0.023541] thermal_sys: Registered thermal governor 'step_wise' [ 0.023546] thermal_sys: Registered thermal governor 'power_allocator' [ 0.023575] cpuidle: using governor menu [ 0.023744] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.023789] ASID allocator initialised with 65536 entries [ 0.024382] Serial: AMBA PL011 UART driver [ 0.024424] imx mu driver is registered. [ 0.024435] imx rpmsg driver is registered. [ 0.029818] imx93-pinctrl 443c0000.pinctrl: initialized IMX pinctrl driver [ 0.036057] platform 4ae30000.lcd-controller: Fixing up cyclic dependency with 4ae10000.dsi [ 0.039167] KASLR disabled due to lack of seed [ 0.050510] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages [ 0.050519] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page [ 0.050522] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages [ 0.050524] HugeTLB: 508 KiB vmemmap can be freed for a 32.0 MiB page [ 0.050527] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages [ 0.050529] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page [ 0.050532] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages [ 0.050534] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page [ 0.052231] ACPI: Interpreter disabled. [ 0.053090] iommu: Default domain type: Translated [ 0.053100] iommu: DMA domain TLB invalidation policy: strict mode [ 0.053318] SCSI subsystem initialized [ 0.053622] usbcore: registered new interface driver usbfs [ 0.053650] usbcore: registered new interface driver hub [ 0.053669] usbcore: registered new device driver usb [ 0.054429] mc: Linux media interface: v0.10 [ 0.054461] videodev: Linux video capture interface: v2.00 [ 0.054497] pps_core: LinuxPPS API ver. 1 registered [ 0.054500] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.054508] PTP clock support registered [ 0.054601] EDAC MC: Ver: 3.0.0 [ 0.055719] FPGA manager framework [ 0.055781] Advanced Linux Sound Architecture Driver Initialized. [ 0.056190] Bluetooth: Core ver 2.22 [ 0.056218] NET: Registered PF_BLUETOOTH protocol family [ 0.056220] Bluetooth: HCI device and connection manager initialized [ 0.056226] Bluetooth: HCI socket layer initialized [ 0.056230] Bluetooth: L2CAP socket layer initialized [ 0.056244] Bluetooth: SCO socket layer initialized [ 0.056579] vgaarb: loaded [ 0.057072] clocksource: Switched to clocksource arch_sys_counter [ 0.057247] VFS: Disk quotas dquot_6.6.0 [ 0.057275] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.057384] pnp: PnP ACPI: disabled [ 0.062200] NET: Registered PF_INET protocol family [ 0.062459] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.063693] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 0.063721] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.063730] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.063799] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear) [ 0.064220] TCP: Hash tables configured (established 16384 bind 16384) [ 0.064337] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.064375] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.064523] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.064896] RPC: Registered named UNIX socket transport module. [ 0.064902] RPC: Registered udp transport module. [ 0.064904] RPC: Registered tcp transport module. [ 0.064906] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.065481] PCI: CLS 0 bytes, default 64 [ 0.065671] Unpacking initramfs... [ 0.077164] hw perfevents: enabled with armv8_cortex_a55 PMU driver, 7 counters available [ 0.077791] kvm [1]: IPA Size Limit: 40 bits [ 0.077823] kvm [1]: GICv3: no GICV resource entry [ 0.077826] kvm [1]: disabling GICv2 emulation [ 0.077840] kvm [1]: GIC system register CPU interface enabled [ 0.077945] kvm [1]: vgic interrupt IRQ9 [ 0.077995] kvm [1]: VHE mode initialized successfully [ 0.079075] Initialise system trusted keyrings [ 0.079368] workingset: timestamp_bits=42 max_order=19 bucket_order=0 [ 0.083800] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.084377] NFS: Registering the id_resolver key type [ 0.084427] Key type id_resolver registered [ 0.084430] Key type id_legacy registered [ 0.084478] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.084483] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 0.084498] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.084799] 9p: Installing v9fs 9p2000 file system support [ 0.110306] Key type asymmetric registered [ 0.110323] Asymmetric key parser 'x509' registered [ 0.110421] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 0.110426] io scheduler mq-deadline registered [ 0.110430] io scheduler kyber registered [ 0.115631] EINJ: ACPI disabled. [ 0.121059] Bus freq driver module loaded [ 0.127423] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.130859] 44380000.serial: ttyLP0 at MMIO 0x44380010 (irq = 18, base_baud = 1500000) is a FSL_LPUART [ 0.579725] Freeing initrd memory: 11624K [ 0.587591] printk: console [ttyLP0] enabled [ 1.297743] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 1.307341] loop: module loaded [ 1.311565] of_reserved_mem_lookup() returned NULL [ 1.316484] megasas: 07.719.03.00-rc1 [ 1.321853] imx ahci driver is registered. [ 1.329636] tun: Universal TUN/TAP device driver, 1.6 [ 1.335399] thunder_xcv, ver 1.0 [ 1.338673] thunder_bgx, ver 1.0 [ 1.341914] nicpf, ver 1.0 [ 1.345372] pps pps0: new PPS source ptp0 [ 1.354869] fec 42890000.ethernet eth0: registered PHC device 0 [ 1.362443] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.369679] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.375062] hclge is initializing [ 1.378397] e1000: Intel(R) PRO/1000 Network Driver [ 1.383269] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.389040] e1000e: Intel(R) PRO/1000 Network Driver [ 1.394000] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.399932] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.405330] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.410916] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 1.417174] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.423285] sky2: driver version 1.30 [ 1.427579] imx-dwmac 428a0000.ethernet: IRQ eth_lpi not found [ 1.433752] imx-dwmac 428a0000.ethernet: User ID: 0x10, Synopsys ID: 0x52 [ 1.440551] imx-dwmac 428a0000.ethernet: DWMAC4/5 [ 1.445333] imx-dwmac 428a0000.ethernet: DMA HW capability register supported [ 1.452455] imx-dwmac 428a0000.ethernet: RX Checksum Offload Engine supported [ 1.459578] imx-dwmac 428a0000.ethernet: TX Checksum insertion supported [ 1.466268] imx-dwmac 428a0000.ethernet: Wake-Up On Lan supported [ 1.472401] imx-dwmac 428a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 1.480057] imx-dwmac 428a0000.ethernet: device MAC address 86:81:0f:94:98:19 [ 1.487205] imx-dwmac 428a0000.ethernet: Enabled L3L4 Flow TC (entries=8) [ 1.493987] imx-dwmac 428a0000.ethernet: Enabled RFS Flow TC (entries=10) [ 1.500766] imx-dwmac 428a0000.ethernet: Enabling HW TC (entries=256, max_off=256) [ 1.508321] imx-dwmac 428a0000.ethernet: Using 32 bits DMA width [ 1.518225] usbcore: registered new interface driver r8152 [ 1.524089] VFIO - User Level meta-driver version: 0.3 [ 1.531938] usbcore: registered new interface driver uas [ 1.537317] usbcore: registered new interface driver usb-storage [ 1.543397] usbcore: registered new interface driver usbserial_generic [ 1.549930] usbserial: USB Serial support registered for generic [ 1.555949] usbcore: registered new interface driver ftdi_sio [ 1.561690] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.569004] usbcore: registered new interface driver usb_serial_simple [ 1.575530] usbserial: USB Serial support registered for carelink [ 1.581622] usbserial: USB Serial support registered for zio [ 1.587281] usbserial: USB Serial support registered for funsoft [ 1.593287] usbserial: USB Serial support registered for flashloader [ 1.599640] usbserial: USB Serial support registered for google [ 1.605559] usbserial: USB Serial support registered for libtransistor [ 1.612090] usbserial: USB Serial support registered for vivopay [ 1.618095] usbserial: USB Serial support registered for moto_modem [ 1.624358] usbserial: USB Serial support registered for motorola_tetra [ 1.630970] usbserial: USB Serial support registered for nokia [ 1.636807] usbserial: USB Serial support registered for novatel_gps [ 1.643163] usbserial: USB Serial support registered for hp4x [ 1.648922] usbserial: USB Serial support registered for suunto [ 1.654845] usbserial: USB Serial support registered for siemens_mpi [ 1.661206] usbcore: registered new interface driver usb_ehset_test [ 1.669805] bbnsm_pwrkey 44440000.bbnsm:pwrkey: KEY_POWER without setting in dts [ 1.678054] input: 44440000.bbnsm:pwrkey as /devices/platform/soc@0/44000000.bus/44440000.bbnsm/44440000.bbnsm:pwrkey/input/input0 [ 1.693496] bbnsm_rtc 44440000.bbnsm:rtc: registered as rtc0 [ 1.700063] bbnsm_rtc 44440000.bbnsm:rtc: setting system clock to 1970-01-01T00:40:35 UTC (2435) [ 1.709596] i2c_dev: i2c /dev entries driver [ 1.716720] imx7ulp-wdt 42490000.wdog: imx93 wdt probe [ 1.750651] Bluetooth: HCI UART driver ver 2.3 [ 1.755119] Bluetooth: HCI UART protocol H4 registered [ 1.760253] Bluetooth: HCI UART protocol BCSP registered [ 1.765575] Bluetooth: HCI UART protocol LL registered [ 1.770704] Bluetooth: HCI UART protocol ATH3K registered [ 1.776103] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.782493] Bluetooth: HCI UART protocol Broadcom registered [ 1.788157] Bluetooth: HCI UART protocol QCA registered [ 1.794787] sdhci: Secure Digital Host Controller Interface driver [ 1.800994] sdhci: Copyright(c) Pierre Ossman [ 1.805883] Synopsys Designware Multimedia Card Interface Driver [ 1.812371] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.819532] ledtrig-cpu: registered to indicate activity on CPUs [ 1.826499] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 1.833373] usbcore: registered new interface driver usbhid [ 1.838953] usbhid: USB HID core driver [ 1.844379] ethosu ethosu: assigned reserved memory node ethosu_region@C0000000 [ 1.850056] mmc0: SDHCI controller on 42850000.mmc [42850000.mmc] using ADMA [ 1.891274] cs_system_cfg: CoreSight Configuration manager initialised [ 1.898992] optee: probing for conduit method. [ 1.903467] optee: revision 3.19 (ad4e8389) [ 1.903903] optee: dynamic shared memory is enabled [ 1.913286] optee: initialized driver [ 1.920587] NET: Registered PF_LLC protocol family [ 1.926018] NET: Registered PF_INET6 protocol family [ 1.931886] Segment Routing with IPv6 [ 1.935621] In-situ OAM (IOAM) with IPv6 [ 1.939623] NET: Registered PF_PACKET protocol family [ 1.944709] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 1.957852] Bluetooth: RFCOMM TTY layer initialized [ 1.962736] Bluetooth: RFCOMM socket layer initialized [ 1.967882] Bluetooth: RFCOMM ver 1.11 [ 1.971628] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 1.975581] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 1.976925] Bluetooth: BNEP filters: protocol multicast [ 1.983735] mmcblk0: mmc0:0001 58A398 7.28 GiB [ 1.988480] Bluetooth: BNEP socket layer initialized [ 1.994157] mmcblk0: p1 p2 [ 1.997954] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.001220] mmcblk0boot0: mmc0:0001 58A398 4.00 MiB [ 2.006645] Bluetooth: HIDP socket layer initialized [ 2.012467] mmcblk0boot1: mmc0:0001 58A398 4.00 MiB [ 2.016733] 8021q: 802.1Q VLAN Support v1.8 [ 2.022269] mmcblk0rpmb: mmc0:0001 58A398 4.00 MiB, chardev (234:0) [ 2.025790] lib80211: common routines for IEEE802.11 drivers [ 2.037706] 9pnet: Installing 9P2000 support [ 2.042071] Key type dns_resolver registered [ 2.046761] registered taskstats version 1 [ 2.050882] Loading compiled-in X.509 certificates [ 2.069935] usb_phy_generic soc@0:usbphynop1: supply vcc not found, using dummy regulator [ 2.078259] usb_phy_generic soc@0:usbphynop1: dummy supplies not allowed for exclusive requests [ 2.087063] usb_phy_generic soc@0:usbphynop2: supply vcc not found, using dummy regulator [ 2.095411] usb_phy_generic soc@0:usbphynop2: dummy supplies not allowed for exclusive requests [ 2.113448] gpio gpiochip0: (43810080.gpio): not an immutable chip, please consider fixing it! [ 2.122542] gpio gpiochip1: (43820080.gpio): not an immutable chip, please consider fixing it! [ 2.131592] gpio gpiochip2: (43830080.gpio): not an immutable chip, please consider fixing it! [ 2.140641] gpio gpiochip3: (47400080.gpio): not an immutable chip, please consider fixing it! [ 2.154906] remoteproc remoteproc0: imx-rproc is available [ 2.162795] i2c 0-003d: Fixing up cyclic dependency with 4ae10000.dsi [ 2.169394] adv7511 0-003d: supply avdd not found, using dummy regulator [ 2.176171] adv7511 0-003d: supply dvdd not found, using dummy regulator [ 2.182901] adv7511 0-003d: supply pvdd not found, using dummy regulator [ 2.189618] adv7511 0-003d: supply a2vdd not found, using dummy regulator [ 2.196414] adv7511 0-003d: supply v3p3 not found, using dummy regulator [ 2.203140] adv7511 0-003d: supply v1p2 not found, using dummy regulator [ 2.210309] adv7511 0-003d: Probe failed. Remote port 'dsi@4ae10000' disabled [ 2.217833] st_lsm6dsx_i2c 0-006a: supply vdd not found, using dummy regulator [ 2.225158] st_lsm6dsx_i2c 0-006a: supply vddio not found, using dummy regulator [ 2.289539] st_lsm6dsx_i2c 0-006a: failed to read whoami register [ 2.295812] st_lsm6dsx_i2c: probe of 0-006a failed with error -5 [ 2.301895] i2c i2c-0: LPI2C adapter registered [ 2.307942] pca953x 1-0022: supply vcc not found, using dummy regulator [ 2.314705] pca953x 1-0022: using AI [ 2.318364] pca953x 1-0022: failed writing register [ 2.323346] pca953x: probe of 1-0022 failed with error -5 [ 2.329016] adp5585 1-0034: Failed to read reg 0x00, ret is -5 [ 2.334871] adp5585: probe of 1-0034 failed with error -5 [ 2.340359] i2c i2c-1: LPI2C adapter registered [ 2.345948] i2c 2-0050: Fixing up cyclic dependency with 4c100000.usb [ 3.357110] tcpci: probe of 2-0050 failed with error -110 [ 3.362704] i2c 2-0051: Fixing up cyclic dependency with 4c200000.usb [ 4.377113] tcpci: probe of 2-0051 failed with error -110 [ 5.389069] adp5585 2-0034: Failed to read reg 0x00, ret is -110 [ 5.395082] adp5585: probe of 2-0034 failed with error -110 [ 5.400885] i2c 2-003c: Fixing up cyclic dependency with 4ae00000.csi [ 5.407546] i2c i2c-2: LPI2C adapter registered [ 5.414180] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 5.422156] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/dsi@4ae10000 to encoder DSI-34: -19 [ 5.432166] dw-mipi-dsi-imx 4ae10000.dsi: [drm:dw_mipi_dsi_imx_bind] *ERROR* failed to attach bridge: -19 [ 5.441725] imx-drm display-subsystem: failed to bind 4ae10000.dsi (ops dw_mipi_dsi_imx_ops): -19 [ 5.450869] imx-drm display-subsystem: adev bind failed: -19 [ 5.456538] dw-mipi-dsi-imx 4ae10000.dsi: [drm:dw_mipi_dsi_imx_probe] *ERROR* failed to register component: -19 [ 5.478535] sdhci-esdhc-imx 42860000.mmc: Got CD GPIO [ 5.479882] dwc-mipi-csi2-host 4ae00000.csi: lanes: 2, name: mxc-mipi-csi2.0 [ 5.498291] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 5.511405] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 5.518188] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 5.521123] clk: Not disabling unused clocks [ 5.526882] mmc1: SDHCI controller on 42860000.mmc [42860000.mmc] using ADMA [ 5.531085] ALSA device list: [ 5.538113] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 5.541074] No soundcards found. [ 5.554051] Freeing unused kernel memory: 3328K [ 5.573123] Run /linuxrc as init process Found New UDC: ci_hdrc.0 ci_hdrc.0 0 Found New UDC: ci_hdrc.1 ci_hdrc.1 1 ffs.utp0 [ 5.621381] file system registered ffs.utp1 run utp at /dev/usb-utp0/ep0 . run utp at /dev/usb-utp1/ep0 [ 5.642106] read descriptors uuu fastboot cli[ 5.646482] read descriptors ent 1.0.0 [built [ 5.650846] read strings Aug 17 2022 19:49[ 5.650846] read strings :14] Start init usb uuu fastboot client 1.0.0 [built Aug 17 2022 19:49:14] Start init usb write string write string Start handle command Start handle command 現時点では、「Start handle command」のままになっており、この状況を修正する方法がわかりません。ご指導をお願いするか、i.mx93 にすぐに使用できる example_kernel_emmc.uuu を提供していただければ幸いです。あなたのご返答を心待ちにしており、楽しい一日をお過ごしいただけることを祈っております。 Re: How can I update my customized U-Boot to the i.mx9352 board? What are the procedures for erasing こんにちは@orange-bear i.MX_Porting_Guide ( i.MXアプリケーション・プロセッサ向け組み込みLinux | NXP Semiconductors ) を参照してください。 よろしくお願いいたします。 Harvey
記事全体を表示
Unable to debug S32k311 mcu using Segger j-link V9 debugger I have been working with an eval board by Elekronika India for 18s BMS solution based on S32k311 MCU. The Segger j-link V9-G JTAG debugger is being used for flashing and debugging. But when we debug the sample code, after flashing, the PC goes to random RAM locations and not to the main function. Enclosed image for your reference. There are no breakpoints except main. But PC does not halt at the main and goes to random RAM locations and halts there. I tried with another example code for S32k311 and it gave the same output.    Kindly suggest a solution.   Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger Issue was with the Segger connector to JTAG adapter board. It wasn't able to reset the controller before debug session. It is resolved now. Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger Hello, But when we debug the sample code, after flashing, the PC goes to random RAM locations and not to the main function Ok, seems to me weird. The core will execute the instruction loaded in it. Not some random ones. There must be executed in your SW some branch (jump) to that RAM location. And the RAM location must be defined in your core registers, to perform branch. If you do step by step debug, you will see exactly where the branch to RAM is happening, and also its preconditions. But PC does not halt at the main and goes to random RAM locations and halts there. I tried with another example code for S32k311 and it gave the same output. Yes, if the main is not reached, it wont halt at main breakpoint. Since the another example gives you the same result, it could be some jumper settings on the board if you use our EVB. We supply the EVBs with getting started guide, where all necessary HW settings are described. But debugging of startup will simply tell you where the issue lie. Best regards, Peter Re: Unable to debug S32k311 mcu using Segger j-link V9 debugger Please find gdb server log for your reference
記事全体を表示
gPTP master port of sja1110 This question has troubled me for a long time. I hope to get an answer.  I will be very grateful。 I am using S32G-VNP-RDB3 and LinuxBSP 43.0. Configuring sja1110 as grand master or bridge, the master port (port 4)always sends only sync messages without follow up messages. Then the flag field of the sync message shows two step. I don't know why no follow up message was sent. The s32g pfe0 port as the slave port sends  pdelay req message, but the sja1110 port4 as the master port does not respond to the pdealy req message and sends a qdelay resp message. The command for s32g pfe0 as slave port is: sudo ./ptp4l -i pfe0 -f configs/automotive-slave.cfg --step_threshold=1 -m However, when sja1110 is configured as a bridge, the slave port of sja1110 can synchronize time normally. Sja1110 port4 as a slave port can synchronize time normally with s32g pfe0 as a master port. The command for s32g pfe0 as master port is: bluebox@ubuntu-s32g399ardb3:~/linuxptp$ sudo ./ptp4l -i pfe0 -f configs/automotive-master.cfg --step_threshold=1 -m I uploaded my project and the capture file. Re: gPTP master port of sja1110 Hello @xiaoshumiao , a new support case has been created on your behalf. You have already replied on that, as well I have. It is still on progress. I will keep you informed in that new support case. Best regards, Pavel Re: gPTP master port of sja1110 Hello @PavelL  I have replied to this email, can you see it?[email protected] Re: gPTP master port of sja1110 Hello @xiaoshumiao , yes, you are right. In the meantime, I did some research and I have a solution. I will share it via private email within this week. Best regards, Pavel Re: gPTP master port of sja1110 Hello @PavelL , Normally, the tcpip component should not affect the normal operation of the gPTP component. Will nxp fix it later? Re: gPTP master port of sja1110 hello @PavelL , Thank you so much, I will follow your suggestion. Re: gPTP master port of sja1110 Hello @xiaoshumiao , I also noticed the timer configuration issue. After spending a significant amount of time on this and performing a deep investigation using the Lauterbach debugger, I was able to identify the root cause: adding the tcpip component and the lwip_demo.c file to the gptp_sja1110x project introduces the same faulty behavior. At this point, the only available workaround is to remove both the lwip and tcpip components from the project. Please refer to gptp_sja1110x/main.c for an example of how the switch and gPTP are initialized without lwIP. Also, take note of the ENET settings, which differ slightly from those in the switch_config_s32g_vnp_rdb example. I apologize for any inconvenience this may have caused. Best regards, Pavel Re: gPTP master port of sja1110 Hello @PavelL  Thank you for your continued attention to this issue. I found a mistake in the configuration, which was caused by my carelessness. The trigger source of LPIT channel 3 should be changed to internal trigger. Other changes I made are: In this case, follow up messages are occasionally sent, but I don't know the reason. The attachment is the captured package. Re: gPTP master port of sja1110 Hello @xiaoshumiao , I apologize for the late response caused my workload. I was able to replicate your issue. It's still not clear to me, because gptp_sja1110x example working well on SJA1110-EVM. I'll do my best to reply within this week. Thank you for your patience. Best regards, Pavel Re: gPTP master port of sja1110 Hello @xiaoshumiao , I apologize for the delayed response due to public holidays. I can't see the reason for such a behavior. I will further investigated. I will keep you updated on any progress. Best regards, Pavel Re: gPTP master port of sja1110 Hello @PavelL , 1. When as bridge, the slave is port 4 and the master is port 2. Connected the slave port to nvidia orin, and then captured the packets on nvidia orin. sudo  tcpdump -i any -vnn -w tsn0707.pcap 2. when sja1110 as grandmaster, the grandmaster is port 4, and the s32g pfe0 is slave. in this case,  capture the packets on s32g: sudo  tcpdump -i any -vnn -w tsn0707.pcap In this case, the captured packet only has sync but no follow up. Re: gPTP master port of sja1110 Hello @xiaoshumiao , I apologize for the late response caused by workload. After reviewing your project, everything I checked looks correct — including the source code and gPTP settings. However, I noticed that only one port is defined for gPTP. You might want to try enabling the "Pdelay Initiator" option for that port. Could you please confirm which port you are using to connect Wireshark on your PC? General suggestions: Please compare your project with the reference example gptp_sja1110x, which was prepared for the SJA1110-EVM board. Also, refer to the gPTP application note, available on the SJA1110 product page under the Documents section (in Secure Files). Best regards, Pavel Re: gPTP master port of sja1110 Hello @PavelL , Thank you very much, I have tried to solve it many times but to no avail. Re: gPTP master port of sja1110 Hello @xiaoshumiao , I apologize for the delayed reply. I need more time, since I don't know the answer right now. Thank you for your patience. Best regards, Pavel
記事全体を表示
EB RTD license sorry, I encountered some issues while using eb. When I click on the mcal module, it shows that I don't have a license for this module, as shown in the picture below. Besides activating the eblicense and installing the corresponding rtd exe package, are there any other operations I need to perform? Re: EB RTD license Hi,  RTD itself doesn't need any license. You are probably missing license for EB tresos. You can find current EB Tresos activation key on your NXP account. 
記事全体を表示
sja1110 的 gPTP 主端口 这个问题困扰了我很长时间。希望能得到答复。 我将不胜感激。 我使用的是 S32G-VNP-RDB3 和 LinuxBSP 43.0。 将 sja1110 配置为主端口或网桥,主端口(端口 4)总是只发送同步信息,而不发送后续信息。然后,同步信息的标志字段显示两个步骤。 我不知道为什么没有发送后续信息。 作为从端口的 s32g pfe0 端口发送了 pdelay req 信息,但作为主端口的 sja1110 port4 没有响应 pdealy req 信息,而是发送了 qdelay resp 信息。 将 s32g pfe0 作为从端口的命令是 sudo ./ptp4l-i pfe0 -f configs/automotive-slave.cfg --step_threshold=1 -m 但是,当 sja1110 配置为网桥时,sja1110 的从端口可以正常同步时间。作为从端口的 Sja1110 port4 可以与作为主端口的 s32g pfe0 正常同步时间。 将 s32g pfe0 作为主端口的命令是 bluebox@ubuntu-s32g399ardb3:~/linuxptp$ sudo ./ptp4l-i pfe0 -f configs/automotive-master.cfg --step_threshold=1 -m 我上传了我的项目和捕获文件。 Re: gPTP master port of sja1110 你好@xiaoshumiao、 已为您创建了一个新的支持案例。你已经回答过了,我也回答过了。目前仍在进行中。我会随时向您通报新的支持案例。 顺祝商祺! 帕维尔 Re: gPTP master port of sja1110 你好@PavelL 我已经回复了这封邮件,您能看到吗?[email protected] Re: gPTP master port of sja1110 你好@xiaoshumiao、 是的,你说得对。与此同时,我做了一些研究,我有一个解决方案。我将在本周内通过私人电子邮件与大家分享。 顺祝商祺! 帕维尔 Re: gPTP master port of sja1110 你好@PavelL、 通常,tcpip 元器件不应影响 gpTP 元器件的正常运行。以后 nxp 会修复吗? Re: gPTP master port of sja1110 你好@PavelL、 非常感谢,我会按照你的建议去做。 Re: gPTP master port of sja1110 你好@xiaoshumiao、 我还注意到计时器配置问题。 在花了大量时间研究这个问题并使用劳特巴赫调试器进行了深入调查之后,我得以确定根本原因:添加了 tcpip 元器件和 lwip_demo.c文件会引入同样的错误行为。 此时,唯一可用的解决方法是从项目中删除 lwip 和 tcpip 元器件。请参阅 gptp_sja1110x/main.c,了解在没有 lwIP 的情况下如何初始化交换机和 gPTP。此外,请注意 ENET 设置,它与 switch_config_s32g_vnp_rdb 示例中的设置略有不同。 对于由此造成的不便,我深表歉意。 顺祝商祺! 帕维尔 Re: gPTP master port of sja1110 你好@PavelL 感谢您对这一问题的持续关注。 我发现配置中有一个错误,这是我粗心大意造成的。 LPIT 频道 3 的触发信号应更改为内部触发器。 我还做了其他改动: 在这种情况下,偶尔会发送后续信息,但我不知道原因何在。 附件是捕获的包裹。 Re: gPTP master port of sja1110 你好@xiaoshumiao、 很抱歉,由于工作繁忙,我的回复晚了。 我能够复制你的问题。我仍然不清楚,因为 gptp_sja1110x 示例在 SJA1110-EVM 上运行良好。 我会尽力在本周内回复。 感谢您的耐心等待。 顺祝商祺! 帕维尔 Re: gPTP master port of sja1110 你好@xiaoshumiao、 很抱歉由于公共假期而延迟回复。 我不明白为什么会有这种行为。我会进一步调查。如果有任何进展,我会及时通知你们。 顺祝商祺! 帕维尔 Re: gPTP master port of sja1110 你好@PavelL、 1.桥接时,从端口为 4,主端口为 2。 将从属端口连接到 nvidia orin,然后在 nvidia orin 上捕获数据包。 sudo tcpdump -i any -vnn -w tsn0707.pcap 2. 当 sja1110 作为主站时,主站是端口 4,而 s32g pfe0 是从站。 在这种情况下,在 s32g 上捕获数据包:sudo tcpdump-i any-vnn-w tsn0707.pcap 在这种情况下,捕获的数据包只能同步,但没有后续跟进。 Re: gPTP master port of sja1110 你好@xiaoshumiao、 由于工作繁忙,我很抱歉没有及时回复。 在查看了您的项目后,我所检查的一切看起来都是正确的,包括源代码和 gPTP 设置。不过,我注意到 gPTP 只定义了一个端口。你可能需要尝试为该端口启用 " Pdelay 启动器 " 选项。 能否请您确认连接 Wireshark 的端口? 一般建议 请将您的项目与为 SJA1110-EVM 主板准备的参考示例 gptp_sja1110x 进行比较。 另请参阅 gPTP 应用笔记,该说明可在 SJA1110 产品页面的 “文档” 部分(在 “安全文件” 中)下找到。 顺祝商祺! 帕维尔 Re: gPTP master port of sja1110 你好@PavelL、 非常感谢,我曾多次尝试解决这个问题,但都无济于事。 Re: gPTP master port of sja1110 你好@xiaoshumiao、 对于延迟回复,我深表歉意。 我需要更多时间,因为我现在还不知道答案。 感谢您的耐心等待。 顺祝商祺! 帕维尔
記事全体を表示
S32K3 SPD DMA こんにちは、 RTD400とSPD105を使用し、開発ボードはS32K312 144P開発ボードです。 設定を行わずに、テスト対象の UART + DMA プログラムに FCCU モジュールを追加しました。ヘッダーファイルが参照されておらず、コード内でFCCU部分が初期化されていない場合でも、プログラムはClock_Ip_SetWaitStatesで停止します。 テスト対象の SPD モジュール プログラムに uart モジュールを通常どおり追加し (RAM およびフラッシュ インジェクション エラーを含む)、その後、設定を行わずに DMA モジュールを追加しました。ヘッダー ファイルと初期化 Fdma 部分がコード内で参照されていない場合でも、プログラムは Clock_Ip_SetWaitStates() 関数内にあります。その後、ハードウェア エラー割り込みが発生します。 FCCU モジュールを追加せずに UART + DMA のコードをアップロードしましたが、正常に動作しました。ただし、追加後はクロック初期化プログラムにハードウェア エラーが発生します。この原因は何でしょうか? また、この問題はどのように解決できるでしょうか? Re: S32K3 SPD DMA 同様の問題に遭遇しました。S32K312 のUART 割り込みモードを使用すると動作しますが、Dma_Ip_Init() および Rm_Init() の後にLpuart_Uart_Ip_AsyncSend () またはLpuart_Uart_Ip_AsyncReceive () を実行すると、 HardFault_Handler () に入ります。 サポートをお願いできますか。 Re: S32K3 SPD DMA こんにちは@ Neo1096 申し訳ございませんが、IAR をサポートすることはできません。変更するには、提供されているリンク ファイルを参照してください。 Re: S32K3 SPD DMA icf ファイルを提供してもらえますか?IARで使用する必要があります Re: S32K3 SPD DMA こんにちは@ Neo1096 問題の原因を見つけました。 これは、S32 DS が提供するリンク ファイルの構成の問題が原因です。 SPD パッケージ内のリンク ファイルを S32 DS 内のリンク ファイルに置き換えると、この問題は解決できます。 SO、さらにテストを行うには、添付ファイルのリンク ファイルを参照してください。 Re: S32K3 SPD DMA こんにちは@ Neo1096 社内チームが問題を再現し、現在考えられる原因を排除しています。 更新日時: 2025年7月23日。 Re: S32K3 SPD DMA こんにちは@Neo1096 社内フォーラムからの返信はまだ受け取っていませんので、お待ちください。 更新日:2025年7月15日。 Re: S32K3 SPD DMA こんにちは@Neo1096 社内フォーラムからの返信はまだ受け取っていませんので、お待ちください。 更新データ:2025年7月7日。 Re: S32K3 SPD DMA こんにちは@ Neo1096 今朝再度プッシュしましたが、社内フォーラムからはまだ何の返答もありません。 Re: S32K3 SPD DMA 何か進展はありましたか? Re: S32K3 SPD DMA こんにちは@Ne01096 これはバグかもしれません。何か見落としているかどうか、デザインチームに確認する必要があります。 現状では、DMA モジュールを追加すると、クロックの初期化時にハードファルト状態になります。 さまざまなバージョンでテストしましたが、結果は同じでした。 Re: S32K3 SPD DMA exceptions.cにコードを追加しましたStartup_Code フォルダーの下に、主にエラー注入によって発生したハードウェア エラーを処理するためにあります。その他の部分は変更ありません。 Re: S32K3 SPD DMA こんにちは@Neo1096 ご提供いただいたプロジェクト「S32K312_SPD104_DMA_UART」をテストしているときに、問題が発生しました。 原因はまだ見つかっていませんが、理論上は「S32K312_SPD104」と同じ設定であれば、このような問題は発生しないはずです。 明日、「S32K312_SPD104」のコードを修正してみます。 しばらく時間がかかります。また、起動ファイルが変更されている可能性があります。 Re: S32K3 SPD DMA 以前アップロードしたコードは実行CAN。FCCU モジュールを個別に追加すると、操作が失敗します。 コードのコピーを2つ再アップロードしました。 正しく実行CANファイルは、SPD104 バージョンに基づいて RAM および FLASH インジェクション エラーをテストします。(S32K312_SPD104) もう 1 つは正しく実行できません。これは、前のコードにDMA+UART部分を追加し、Clock_Ip_SetWaitStates(); ハードウェア割り込みを入力します(S32K312_SPD104_DMA_UART) ぜひご覧ください。ありがとう。 Re: S32K3 SPD DMA こんにちは@ Neo1096 まず、提供されたプロジェクトをテストしましたが、おっしゃった問題は発生しませんでした。CANさらに詳しい情報と、変更が必要かどうかを教えてください。 第二に、SPDバージョン4.0.0に対応するP24は1.0.4のはずです。バージョン1.0.4をインストールしてもう一度お試しください
記事全体を表示
S32G3:RTD MemMap 截面违规(用于 LLCE) 您好, 根据"[S32G3/Valeo] RTD MemMap Sections Violations - NXP Community" 的建议,我创建了此票据,用于为 LLCE 进行 xxx_MemMap 审核,具体如下(完整文档附后)。 请检查使用 GHS 编译后,下列参数/函数是否遗漏包含在适当的内存区域。 ================================================================= (Can_43_LLCE_TS_T40D11M10I8R0) (Llce_Af_TS_T40D11M10I8R0) Can_43_LLCE_AFcfg.c: Llce_Eth2Can_EnabledFormats => CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE(即 bss 部分)中的数据 pLlce_Can_AfBuffer => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED(即 rodata 部分)中的数据 (Can_43_LLCE_TS_T40D11M10I8R0) (Llce_Af_TS_T40D11M10I8R0) Can_43_LLCE_MAIN_SOC_PBcfg.c:// VariantPostBuild 已启用 (MAIN_SOC) Llce_Rx_Filters_List_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据为 rodata 部分 Llce_RxAf_Filters_List_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据为 rodata 部分 Llce_Rx_Filters_Ctrl0_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据为啮合数据。 Llce_Rx_Filters_Ctrl2_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,它是啮合数据 Llce_Rx_Filters_Ctrl4_PB_MAIN_SOC=> CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据是啮合数据段 Llce_Rx_Filters_Ctrl9_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据是啮合数据段 Llce_Rx_Filters_Ctrl15_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据是啮合数据段。 Llce_RxAf_Filters_Ctrl0_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据。这是rodata部分 Llce_RxAf_Filters_Ctrl5_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,这是 Llce_RxAf_Filters_Ctrl9_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据为 rodata 部分 Llce_RxAf_Filters_Ctrl15_PB_MAIN_SOC => CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED 中的数据,该数据为 rodata 部分 (Can_43_LLCE_TS_T40D11M10I8R0) (Llce_Af_TS_T40D11M10I8R0) Can_Llce: llce_minihif => 未包含在 Can_43_LLCE_MemMap.h 中的静态全局变量 u8Length => 未包含在 Can_43_LLCE_MemMap.h 中的静态局部变量 stringBuf => 未包含在 Can_43_LLCE_MemMap.h 中的静态局部变量 ***************************************************************************************************************************************************************** 答:请通过标签"LLCE" 在恩智浦社区 ***************************************************************************************************************************************************************** 向 LLCE 团队提出此问题。 LLCE Re: S32G3: RTD MemMap Sections Violations (For LLCE) 您好, 你知道修复工作是否有时间表吗?如果有,何时? Re: S32G3: RTD MemMap Sections Violations (For LLCE) 您好, 法雷奥很晚才对您的问题做出反馈: 1.当你说:"Llce_Eth2Can_EnabledFormats => data in CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE which is bss section", 你是说 Llce_Eth2Can_EnabledFormats 应该放在例如 .mcal_bss_no_cacheable 中,但实际上却放在 .bss 部分? 该变量的初始化值为 4,但变量位于 .bss 部分,而不是 .data 部分。部分,因此变量应放在 .mcal_data_x 中。 2. 将全局静态变量llce_minihif加入相应的 MemMap 部分。u8Length/ stringBuf 是函数静态变量,它们不受 MemMap 控制,因为根据 SWS_MemMap_00023,MemMap 不能添加到函数体内部。如果需要通过 MemMap 部分对其进行控制,我们可以遵循 AUTOSAR 建议:"要强制对函数的静态变量进行特殊内存映射,必须将该变量移至文件静态作用域"。 看起来这个变量在 Can_43_LLCE_TS_T40D11M10I10R0 中已被修复。 3.对于 Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ ,您确定将其放在正确的部分吗? 从下图中可以看到,有(static、static const),但它们都被放在同一个部分,即 .mcal_cont_cfg 部分。它是 rodata,而这个文件是生成的,所以我不能把它放在任何部分。 在之前/旧的交易所中,你预计下一个版本中不会有任何软件更新,因为不会有新的软件版本。现在还是这样吗? Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi Cong、 我已将我方的答复汇总给客户,但至今没有进一步的反馈。 我刚刚向我们的联系人发送了一封电子邮件,就您提出的 LLCE 问题征求进一步的反馈意见。 如果客户有任何回复,我们将在此更新。 此致, 理查德-钟 Re: S32G3: RTD MemMap Sections Violations (For LLCE) HiRichard, 感谢您的更新! 我们将在 2025 年 3 月在 S32G 上发行一张光盘,计划于 2025 年 5 月发行。此后没有发布下一个版本的计划。因此,我想收集有关该主题的信息,然后我们可以将这些实现纳入即将发布的2025年5月版本中。 请就我最初答复中的问题提供反馈意见: 1.我是否正确理解了他们所说的话?当他们说"Llce_Eth2Can_EnabledFormats => data in CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE which is bss section", 他们是否说 Llce_Eth2Can_EnabledFormats 应放在 .mcal_bss_no_cacheable 等位置,但实际上却放在 .bss 部分? 2. 将全局静态变量llce_minihif加入相应的 MemMap 部分。u8Length/ stringBuf 是函数静态变量,它们不受 MemMap 控制,因为根据 SWS_MemMap_00023,MemMap 不能添加到函数体内部。如果需要通过 MemMap 部分来控制它们,我们可以遵循 AUTOSAR 的建议:"要强制对函数的静态变量进行特殊内存映射,必须将该变量移至文件静态作用域"。 您能否确认这是一个强烈要求? 3. 对于 Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ , 您是否检查过为什么客户认为它被放在了错误的部分? Re: S32G3: RTD MemMap Sections Violations (For LLCE) 您好, 根据原始票据上关于修复期望的更新,客户将在 6 月冻结代码。 尽管涉及许多元器件并且需要补丁,但要在6月之前组装起来会很困难。 因此,除非客户进一步强调,否则请根据现有假设/资源进行规划。 此致, 理查德-钟 Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi Cong、 很抱歉迟迟没有更新,但正如您在原始票据上看到的,客户完全没有反馈。 我将再次推动这项工作,但看起来您可以根据您对当前形势的评估来制定计划。 此致, 理查德-钟 Re: S32G3: RTD MemMap Sections Violations (For LLCE) 嗨,理查德、 你有关于这个话题的最新消息吗? 我们需要尽快在 S32G 上的三月光盘中实施。 此致, Cong Re: S32G3: RTD MemMap Sections Violations (For LLCE) 对于 2.是的,我们创建了AF-4950票来记录这些详细信息。正在等待上述问题的确认,以便最终确定机票细节。 Re: S32G3: RTD MemMap Sections Violations (For LLCE) 您好, 感谢您的更新。 1.对于Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ ,我将进一步检查为什么客户认为它被放在了错误的部分。 2.至于其他部分,既然您提到我们将进行修订,以确保包含适当的部分,那么我们是否已经制定了解决这些问题的方案/计划,以便与客户分享? 3.如原始票据"[S32G3/Valeo] RTD MemMap Sections Violations - NXP Community" 所述,FAE 正在与客户核实他们对此问题修正的期望,如有进一步信息,将在此更新。 此致, 理查德-钟 Re: S32G3: RTD MemMap Sections Violations (For LLCE) 你好, 首先,我需要了解报告的内容。当他们说"Llce_Eth2Can_EnabledFormats => CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE 中的数据,这是 bss 部分 "时, ,他们是否说 Llce_Eth2Can_EnabledFormats 应位于例如.mcal_bss_no_cacheable、但实际上它被放入 .bss部分? 根据上述假定的理解,反馈意见是: NXP 将: - 将全局静态变量 llce_minihif 纳入相应的 MemMap 部分。u8Length/ stringBuf 是函数静态变量,它们不受 MemMap 控制,因为根据 SWS_MemMap_00023,MemMap 不能添加到函数体内部。如果需要通过 MemMap 部分对其进行控制,我们可以遵循 AUTOSAR 建议:"要强制对函数的静态变量进行特殊内存映射,必须将该变量移至文件静态作用域"。您能确认这是一个强烈要求吗? - 将全局静态变量 llce_minihif 定义纳入相应的 MemMap 部分 - 将 Llce_Eth2Can_EnabledFormats 的声明纳入相应的 MemMap 部分。这很可能就是放错位置的原因。 - 将 pLlce_Can_AfBuffer 的声明纳入相应的 MemMap 部分,并仔细检查当前 MemMap 部分是否合适。 - Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ 已被放入相应的 MemMap 部分,因此需要进行额外分析以确定变量错放的原因。 Re: S32G3: RTD MemMap Sections Violations (For LLCE) 您好, 是否有任何更新? 此致, 理查德-钟
記事全体を表示
S32G3: RTD MemMap Sections Violations (For LLCE) Hi, As suggested by  "[S32G3/Valeo] RTD MemMap Sections Violations - NXP Community", I am creating this ticket for xxx_MemMap review for LLCE as below (full document attached.) Please check if below parameter/functions missed to be included in proper memory region after compiled with GHS. ================================================================= (Can_43_LLCE_TS_T40D11M10I8R0) (Llce_Af_TS_T40D11M10I8R0) Can_43_LLCE_AFcfg.c: Llce_Eth2Can_EnabledFormats => data in CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE which is bss section pLlce_Can_AfBuffer => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section (Can_43_LLCE_TS_T40D11M10I8R0) (Llce_Af_TS_T40D11M10I8R0) Can_43_LLCE_MAIN_SOC_PBcfg.c: // VariantPostBuild is enabled (MAIN_SOC) Llce_Rx_Filters_List_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_RxAf_Filters_List_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_Rx_Filters_Ctrl0_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_Rx_Filters_Ctrl2_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_Rx_Filters_Ctrl4_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_Rx_Filters_Ctrl9_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_Rx_Filters_Ctrl15_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_RxAf_Filters_Ctrl0_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_RxAf_Filters_Ctrl5_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_RxAf_Filters_Ctrl9_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section Llce_RxAf_Filters_Ctrl15_PB_MAIN_SOC => data in CAN_43_LLCE_START_SEC_CONFIG_DATA_UNSPECIFIED which is rodata section (Can_43_LLCE_TS_T40D11M10I8R0) (Llce_Af_TS_T40D11M10I8R0) Can_Llce: llce_minihif => Static global variable not inculded in the Can_43_LLCE_MemMap.h u8Length => Static local variable not inculded in the Can_43_LLCE_MemMap.h stringBuf => Static local variable not inculded in the Can_43_LLCE_MemMap.h ***************************************************************************************************************************************************************** Answer: please raise this questions to LLCE team via tag "LLCE" on NXP community ***************************************************************************************************************************************************************** LLCE Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi, Do you know if fixes are schedule then? if so, when? Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi, Extremely late feedback from Valeo regarding your question: 1. When you said: “Llce_Eth2Can_EnabledFormats => data in CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE which is bss section”, do you say that Llce_Eth2Can_EnabledFormats should be in e.g. .mcal_bss_no_cacheable, but it is actually placed into .bss section? This variable is initialized by a value of 4 but the variable is within A .bss section not .data section so yes the variable should be in e.g .mcal_data_x. 2. Include global static variable llce_minihif into the appropriate MemMap section. u8Length/ stringBuf are function-static variables and they are not under MemMap control because the MemMap cannot be added inside the body of the function according to SWS_MemMap_00023. If it is required to control them by MemMap section, we can follow the AUTOSAR recommendation : “To force a special memory mapping of a function’s static variable, this variable must be moved to file static scope”.  looks like this variable has been fixed in Can_43_LLCE_TS_T40D11M10I10R0. 3. For the Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ , are you sure you placed it in the right section? as you can see in the below image there are (static, static const) but all of them are placed in the same section which is .mcal_cont_cfg which is rodata, and this file is generated so it's not up to me to place it in any section. In the previous/old exchanges you expected no sw updates in next release as there will be no new sw version. Is it still the case?  Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi Cong, I had summarized the response from our side to customer but no further feedback so far. I just sent an individual email to our contact to ask for further feedback on LLCE questions you raised. Will update here if any reply from customer. Regards, Richard Chung. Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi Richard, Thanks for your updates! We will have a CD on S32G in Mar-2025, and it is planed in May-2025. There is no plan for the next release after that. So I want to collect the information on the topic, then we can include these implementations in this upcoming release of May-2025. Please help me with feedback on the questions on my initial response: 1. Do I understand correctly what they say? e.g: When they say: “Llce_Eth2Can_EnabledFormats => data in CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE which is bss section”, do they say that Llce_Eth2Can_EnabledFormats should be in e.g. .mcal_bss_no_cacheable, but it is actually placed into .bss section? 2. Include global static variable llce_minihif into the appropriate MemMap section. u8Length/ stringBuf are function-static variables and they are not under MemMap control because the MemMap cannot be added inside the body of the function according to SWS_MemMap_00023. If it is required to control them by MemMap section, we can follow the AUTOSAR recommendation : “To force a special memory mapping of a function’s static variable, this variable must be moved to file static scope”. Can you confirm this is a strong request? 3. For the Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ , Did you check why customer consider this being placed in wrong section? Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi, As updated on originating ticket about fix expectation, customer will have the code freeze by June. While there being many components getting involved and need patch, it would be difficult to put them together before June. So please plan according to your current assumption/resources unless further highlighted by customer. Regards, Richard Chung. Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi Cong, Sorry for the late update but as you can see on the origin ticket, there is totally no feedback from customer. I will push for this again but it looks like you can plan according to your evaluation as of current situation. Regards, Richard Chung. Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi Richard, Do you have any update on the topic? We need to implement it asap for the March CD on S32G. Regards, Cong Re: S32G3: RTD MemMap Sections Violations (For LLCE) For 2. Yes, we created the ticket AF-4950 to log these details. Waiting for the confirmations for the above questions to finalize the ticket details. Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi, Thanks for your update. 1. For the Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ , I will further check why customer consider this being placed in wrong section. 2. For the rest, since you mentioned we will revise to ensure the proper section inclusion, do we have a ticket/plan in place to fix them so that we can share with customer? 3. As described on the originating ticket "[S32G3/Valeo] RTD MemMap Sections Violations - NXP Community" FAE is checking with customer on their expectation of this issue correction, will update if any further information here. Regards, Richard Chung. Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi, First of all, I need to understand the report. When they say: “Llce_Eth2Can_EnabledFormats => data in CAN_43_LLCE_START_SEC_VAR_CLEARED_16_NO_CACHEABLE which is bss section”, do they say that Llce_Eth2Can_EnabledFormats should be in e.g. .mcal_bss_no_cacheable, but it is actually placed into .bss section? Following the presumed understanding above, the feedback is: NXP will: • Include global static variable llce_minihif into the appropriate MemMap section. u8Length/ stringBuf are function-static variables and they are not under MemMap control because the MemMap cannot be added inside the body of the function according to SWS_MemMap_00023. If it is required to control them by MemMap section, we can follow the AUTOSAR recommendation : “To force a special memory mapping of a function’s static variable, this variable must be moved to file static scope”. Can you confirm this is a strong request? • Include global static variable definition llce_minihif into the appropriate MemMap section • Include the declaration of Llce_Eth2Can_EnabledFormats into the corresponding MemMap section. This is most probably the reason for misplacement. • Include the declaration of pLlce_Can_AfBuffer into the corresponding MemMap section and double check whether the current MemMap section is appropriate . • Llce_Rx_Filters_List_ / Llce_RxAf_Filters_List_ is already placed into the corresponding MemMap section, extra analysis is required to determine the source of variable misplacing. Re: S32G3: RTD MemMap Sections Violations (For LLCE) Hi, Is there any update? Regards, Richard Chung.
記事全体を表示
S32K3 SPD DMA 您好。 我使用 RTD400 和 SPD105,开发板是 S32K312 144P 开发板 我在测试的 UART+DMA 程序中添加了 FCCU 模块,但没有进行任何设置。即使未参考头文件,也没有在代码中初始化 FCCU 部分,该程序也会在 clock_ip_setWaitStates 时死亡 我在已测试的 SPD 模块程序中正常添加了 uart 模块(包括 RAM 和闪存注入错误),然后添加了 DMA 模块,但未作任何设置。即使代码中没有参考头文件和初始化 Fdma 部分,该程序仍将处于函数 Clock_Ip_SetWaitStates() 中;然后它会进入硬件错误中断。 我上传了 UART+DMA 的代码,没有添加 FCCU 模块,可以正常运行。但是,添加后,时钟初始化程序会出现硬件错误。出现这种情况的原因是什么,如何解决这个问题? Re: S32K3 SPD DMA 我也遇到了类似的问题。在 Dma_Ip_Init() 和 Rm_Init() 之后运行Lpuart_Uart_Ip_AsyncSend() 或Lpuart_Uart_Ip_AsyncReceive() 时,使用 S32K312 的UART 中断模式 可以正常工作,但会进入HardFault_Handler()。 有人能帮我一下吗? Re: S32K3 SPD DMA 你好@Neo1096 很抱歉,我们不支持 IAR,您可以参考我们提供的链接文件进行修改。 Re: S32K3 SPD DMA 能否提供 icf 文件?我需要在 IAR 中使用它 Re: S32K3 SPD DMA 你好@Neo1096 我们找到了问题的原因。 这是因为 S32 DS 提供的链接文件存在配置问题。 我们用 S32 DS 中的链接文件替换了 SPD 代码包,这个问题就可以解决了。 因此,请参考附件中的链接文件进行进一步测试。 Re: S32K3 SPD DMA 你好@Neo1096 内部团队已重现该问题,目前正在排除可能的原因。 更新时间 : 7/23/2025. Re: S32K3 SPD DMA 你好@Neo1096 我还没有收到内部论坛的回复,感谢您的耐心等待。 更新数据:2025 年 7 月 15 日。 Re: S32K3 SPD DMA 你好@Neo1096 我还没有收到内部论坛的回复,感谢您的耐心等待。 更新数据:7/7/2025。 Re: S32K3 SPD DMA 你好@Neo1096 我今天早上又催了一次,但还没有收到内部论坛的任何回复。 Re: S32K3 SPD DMA 有什么进展吗? Re: S32K3 SPD DMA 你好@Ne01096 这可能是一个错误,我需要与设计团队确认我是否忽略了什么。 目前的情况是,只要我添加了 DMA 模块,它就会在初始化时钟时进入硬停机状态。 我在不同版本中进行了测试,结果都是一样的。 Re: S32K3 SPD DMA 我在 exceptions.c 中添加了一些代码主要用于处理由错误注入引起的硬件错误。其他部分保持不变。 Re: S32K3 SPD DMA 你好@Neo1096 我在测试您提供的项目"S32K312_SPD104_DMA_UART" 时遇到了您的问题。 我还没有找到原因,但从理论上讲,如果您的设置与"S32K312_SPD104" 相同,应该不会出现这样的问题。 明天我将尝试在"S32K312_SPD104" 中修改您的代码。 这需要一些时间,而且您可能已经修改了启动文件。 Re: S32K3 SPD DMA 我之前上传的代码可以运行。单独添加 FCCU 模块将导致操作失败。 我重新上传了两份代码。 根据 SPD104 版本,可以正确运行测试 RAM 和 FLASH 注入错误的文件。(S32K312_SPD104) 另一个无法正常运行。在前面的代码中额外添加 DMA+UART 部分,该部分将位于 Clock_Ip_SetWaitStates();输入硬件中断 (S32K312_SPD104_DMA_UART) 请看一看。谢谢。 Re: S32K3 SPD DMA 你好@Neo1096 首先,我测试了你提供的项目,没有遇到你提到的问题。您能否提供更多信息,以及是否需要做一些改动? 第二,对应于 4.0.0 的 SPD 版本P24 应为 1.0.4。您可以尝试安装 1.0.4 版,然后再试一次
記事全体を表示
OM27160 ラズベリー i2c NfcService 初期化失敗 OM27160A1HNをラズベリーパイにコネクテッドしています。 https://www.nxp.com/docs/en/application-note/AN12991.pdfの i2c の手順に従いました。 「nfcDemoApp poll」を実行すると、「NfcService Init Failed」というメッセージが表示されます。 これまで試したこと: ボードを二重にチェックしましたが、SPI ではなく I2C でした。 「i2cdetect -y 1」でi2cをスキャンしても何も表示されません。 他の i2c デバイスで動作することがわかっている 2 種類のラズベリー ナッツ クッキーで試しました。 デバッグを有効にしました。ログが添付されています。 今何をチェックすべきかアイデアがありますか? Re: OM27160 raspberry i2c NfcService Init Failed セットアップの詳細: Debian を実行している Raspberry Pi 5 (カーネル 6.12.25+rpt-rpi-2712、aarch64) NXP NFCチップ用のlinux_libnfc-nciライブラリの使用 /dev/i2c-1、/dev/i2c-13、/dev/i2c-14 のバスで I2C が有効 現在の問題: sudo i2cdetect -y 1 はデバイスを表示しません(すべて "--") nfcDemoApp はコンパイルされますが、「NfcService Init Failed」で失敗します また、strings.cpp で C++ std::out_of_range 例外が発生します。 I2C スキャンでは、バス 1 に NFC ハードウェアが検出されないことが示されています。モジュールが正しくコネクテッドされていないか、NFC チップの I2C が正しく構成されていません。 ソースコードの分岐したブランチを使うと進歩しましたが、 @danielchenの返信を見た別の会話によると、皆さんはどこかにプライベートに保存された動作するソースコードのバージョンを持っているようです。 Re: OM27160 raspberry i2c NfcService Init Failed こんにちは@mikytron98さん、 CANセットアップの詳細を教えていただけますか?どの Raspberry Pi と Linux バージョンを使用していますか? BR トーマス Re: OM27160 raspberry i2c NfcService Init Failed 文脈的には、同じことが言えます: NfcService の初期化に失敗しました Elechouse クイック スタート ガイドに従っています。 私はM2チップを搭載したMacからSSH経由でPiにアクセスしています。ここで何が起こっているのかを正確に特定するのに役立つ追加のコンテキスト。 Re: OM27160 raspberry i2c NfcService Init Failed こんにちは@Tomas_Parizek 私も上記と同様の立場です。パッチ ファイルを見つけましたが、nfcDemoApp のポーリングを実行すると、依然として問題が発生します。sudo i2cdetect -y 1 を実行すると、ピンが検出されないことが示されます。他のセットアップで使用していて動作したため、Raspberry Pi が故障していないと判断しました。では、Pi が NFC コントローラを検出するようにするには、他にどのようなパッチを適用すればよいでしょうか? Re: OM27160 raspberry i2c NfcService Init Failed こんにちは、 KennyGさんとStephan_Bさん、 解決策はすでに用意されています。私の同僚が NXP NFC Knowledge base 経由でそれを共有します。 ここのリンクもすぐに更新します。 BR トーマス Re: OM27160 raspberry i2c NfcService Init Failed この問題は最新の Pi リリースで動作するように解決されましたか? よろしくお願いします! --ケン Re: OM27160 raspberry i2c NfcService Init Failed ***アップデート*** --> 修正を見る https://community.nxp.com/t5/NFC-Knowledge-Base/Porting-PN7160-NCI2-stack-to-Raspberry-Pi-5-OS-Bookworm/ta-p/1977521 最新の Raspian Linux バージョン 12 (Bookworm) では、PN7160 が「NfcService Init Failed」を返すことがわかります。 Linux バージョン 11 (bullseye) の場合、この問題は発生しないはずです。 NXP はできるだけ早く修正するために取り組んでいます。 Re: OM27160 raspberry i2c NfcService Init Failed こんにちは@Tomas_Parizek 今日、セットアップがうまくいきました。古い Rasbian バージョン (bullseye) をインストールする必要がありましたが、その後はエラーなしでコンパイルされ、動作します。 どの OS / HW バージョンでテストされているかについては、「スタートガイド」にいくつかのヒントがあればよかったと思います。 よろしくお願いします。 ステファン Re: OM27160 raspberry i2c NfcService Init Failed こんにちは@Tomas_Parizek 私は Raspberry Pi 5 と Raspberry Pi 3 B+ で試してみました。32 ビット版と 64 ビット版の両方をテストしました。ただし、64 ビット バージョン用にコンパイルするときに、後で 64 ビット パッチ ファイルで見つかったコードの一部を修正する必要がありました。 次に、オシロスコープで I2C 信号が送信されているのをCAN確認できたので、これはハードウェアの問題であると想定しました。SO、別の EvalBoard を購入しましたが、まだ動作しません。 「NfcService の初期化に失敗しました」 「出発します…」 それが私が得たすべてです。OSに関してはRasbianを使っています。私は開発キットに付属していたRaspberry Shieldを使用し、ターミナル(SSH/Putty)経由ですべてをセットアップ/インストールしました。 ステファンより Re: OM27160 raspberry i2c NfcService Init Failed こんにちはStephan_Bさん、 セットアップの詳細を教えていただけますか?使用している Raspberry と OS は何ですか? 最新の Raspberry には PN7160 の問題があるようですが、当社の SW チームがすでにそれを確認しています。 BR トーマス Re: OM27160 raspberry i2c NfcService Init Failed こんにちは@Tomas_Parizek 私も同じ問題を抱えています。I2C をチェックし、プラグを抜いて何度も再起動しましたが、常に「NfcService Init Failed」というメッセージが表示されます。セットアップを実行するために試すことができる他の提案はありますか? OM27160 が接続されているかどうかに関係なく、エラー メッセージは同じです。PN7160 が応答しているかどうかを確認する簡単な方法はありますか?ハードウェアに何らかの欠陥があるのでしょうか? よろしくお願いします。 ステファン Re: OM27160 raspberry i2c NfcService Init Failed 皆さん、完全なインストールを実行して、何かを変更できると信じているドライバを使用する時間がありませんでした。 同時に、解決策としてマークされているものは何も解決しません。私の説明を読めば、I2C を使用してさまざまなデバイスと通信することに問題がないことがわかります。SO、マークされたソリューションは、I2C を無効にすることによってそれ自体が作成した問題のみを解決します。 Re: OM27160 raspberry i2c NfcService Init Failed こんにちは、パウェルさん。 私は自分のRaspberry Piでテストしました 私はアプリに記載されている指示に正確に従いました。あなたが言及したことに注意してください。 結果は次のとおりです。 初めてですが、私もあなたと同じように「 NfcService Init Failed 」というエラー メッセージを受け取りました。 SO、PN7160 をソケットから取り外して元に戻し、I2C が有効になっているかどうかを確認しました。 すると、写真の通り、NFC アプリケーションが動作し始めました。 私が使用している HW に関する情報は次のとおりです。 また、最初にやったことがもうひとつあります。設定で I2C を有効にしました。 BR トーマス Re: OM27160 raspberry i2c NfcService Init Failed こんにちは、パウェルさん。 わかりました。Raspberry Pi を 1 台取り出して、私の側で PN7160 をチェックしてみます。 ところで、Raspberry Piの「シールド」を使用していますか、それともケーブル接続を使用していますか? BR トーマス Re: OM27160 raspberry i2c NfcService Init Failed 7160 にファームウェアが欠落しているか、間違ったファームウェアがインストールされている可能性はありますか? SPI を試してみると役立ちますか? Re: OM27160 raspberry i2c NfcService Init Failed 以下は設定から抜粋した関連部分です。ビルディング前に構成が変更されました。 NXP_TRANSPORT=0x02 ############################################################################### # NFCデバイスノード名 NXP_NFC_DEV_NODE="/dev/i2c-1" strace ファイルには、正しいファイルが開かれていることが示されます。興味深いThreadからログのみを抜粋しました。 コマンドは「strace -ff -o strace.log nfcDemoApp poll」でした。 Re: OM27160 raspberry i2c NfcService Init Failed 設定は正しいです。/dev/i2c-1 を開いていることを示す strace ログを添付します。 Re: OM27160 raspberry i2c NfcService Init Failed こんにちは、パウェルさん。 libnfc-nxp.confを確認してください。お願いします? ここでも I2C 代替ドライバを設定する必要があります。 I2Cの場合 -> NXP_TRANSPORT= 0x02 BR トーマス Re: OM27160 raspberry i2c NfcService Init Failed こんにちは@paweljasinski 、 あなたの調子が良いといいのですが。 PN7160 Linux 移植ガイドを参照してください。このドキュメントでは、汎用 GNU/Linux システムに PN7160 コントローラのサポートを追加する方法について詳しく説明します。 よろしく。 エドゥアルド。
記事全体を表示