i.MX8QM上のAAOS 15における複数ディスプレイのタッチ入力設定 チームの皆さん、こんにちは。 私はi.MX8QMボードで10.1インチのHDMI LCD(E)タッチスクリーンディスプレイを使用しています。これらのディスプレイを基板に適切に接続し、各ディスプレイのタッチ入力を設定する方法について、ご指導をお願いします。具体的には、タッチ入力(USB)を接続するために基板上のどのポートやインターフェースを使うべきかを理解したいです。さらに、Android Automotiveシステム内の各タッチ入力を対応するディスプレイに正しくマッピングする方法も助けが必要です。 ありがとうございます。 Re: Touch Input Configuration for Multiple Displays in AAOS 15 on i.MX8QM こんにちは、 i.MX 8QuadMaxは最大4台のディスプレイに対応しています: 以下の4つのディスプレイ（HDMI_TX、LVDS0_CH0、LVDS1_CH0、MIPI_DSI1）から、2～4個のディスプレイを任意の組み合わせで使用できます。 以下の4つのディスプレイ（LVDS0_CH0、LVDS1_CH0、MIPI_DSI0、MIPI_DSI1）から2～4個のディスプレイを任意の組み合わせで使用できます。 入力設定については、Android Automotive User's Guideの8.3.3.1セクション「ディスプレイポートと入力ポートのバインド」を参照してください。 よろしくお願いいたします。 Re: Touch Input Configuration for Multiple Displays in AAOS 15 on i.MX8QM よろしくお願いします。

MCXA265VPNレイアウト案 NXPチーム、 MCXA265VPNのファンアウトの例はありますか？パッドと穴のサイズに関する推奨事項が必要です。ビアはパッド内ですか、それともピン間ですか? BGAでしっかりしたGND機が必要ですか? 助けてください。 ダン・ロジャースさん、ありがとう。 ボード設計 Re: MCXA265VPN Layout Suggestion チーム、 配線例が記載されたデモボードはありますか？知りたいこと： BGAピン間の配線に使われるトレース幅やサイズはどのくらいですか? 使用されているタイプとパッドサイズ、穴のサイズによって決まりますか？ スルーホール、BBVIA、スタック？ 配線後のピン間の間隔は？ 説明 = MCXA265VPN、NXP Semiconductors MXCA_169_BGA169（パッド幅10ミル、ピン間隔19.7ミル） どうもありがとうございます。皆さんのサポートに感謝します。 ダン・ロジャース

Support Required: Secure Partition Access-File Corruption Issue on i.MX8QXP C0 MEK – Yocto Scarthgap Hi NXP Team, We need your support regarding a secure partition/file system issue observed on i.MX8QXP C0 MEK. We are using the below software baseline: Item Details Platform i.MX8QXP C0 MEK BSP Yocto Linux Yocto Release Scarthgap Kernel Version 6.6.5 Issue Description: We are able to generate the secure partition key successfully. However, when we try to use/access the secure partition from the Linux file system, the access fails. In some cases, the file also gets corrupted after access/write operations. Observation: Area Status Secure partition key generation Successful File system access using the generated key Failing File read/write operation Not stable File integrity File corruption observed Could you please help us understand the recommended and correct way to handle secure partition access in Yocto Linux for i.MX8QXP? We need your guidance on the below points: What is the recommended method to create, format, mount, and access a secure partition in Yocto Linux on i.MX8QXP? Is there any specific file system type recommended for secure partition usage? Are any kernel configuration, device tree, OP-TEE, or Yocto layer changes required? Is there any NXP reference implementation or document available for secure partition handling? What is the correct flow to use the generated secure key without causing file system access failures or file corruption? Request you to please review and suggest the correct implementation approach. Re: Support Required: Secure Partition Access-File Corruption Issue on i.MX8QXP C0 MEK – Yocto Scart Hello, You may refer to our BSP documentation, I cannot find this specific Linux release in our releases, so I may recommend to refer to the closest one available. i.e kernel 6.6.23 i.MX Linux User's Guide chapter 10.5 Disk encryption acceleration For the file system we use ext4 for our testing so I would recommend using this one, please have a look to the documentation for the kernel configuration needed and the actual steps to follow. Best regards/Saludos, Aldo.

FRDM i.MX93におけるAP1302 MIPI CSIストリーミングの問題 こんにちは、 私はFRDM i.MX93ボードとX-RPI-CAM-MIPI A1カメラモジュールを使用しています。 私が直面している問題は、この設定からMIPI CSIストリームをキャプチャできないことです。 ファームウェアバイナリap1302_60fps_ar0144_27M_2Lane_awb_tuning.binを次の場所に配置しました: "/lib/firmware" 起動時にAP1302が正常に検出されていることは確認できますが、ビデオストリーミングを開始しようとすると、 VIDIOC_STREAMONが 「パイプが壊れています」という エラー で失敗します 。 以下に、関連するログを示します。 カーネルログ: root@imx93evk:~# dmesg | grep ap1302 [ 0.340980] /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c: Fixed dependency cycle(s) with /soc@0/bus@42800000/csi@4ae00000 [ 0.371014] /soc@0/bus@42800000/csi@4ae00000: Fixed dependency cycle(s) with /soc@0/bus@42000000/i2c@42530000/ap1302_mipi@3c ... [ 10.088832] ap1302 2-003c: AP1302 revision 0.2.6 detected ストリーミングテスト: root@imx93evk:~# v4l2-ctl -d /dev/video0 \ --verbose \ --stream-mmap=3 \ --stream-count=10 VIDIOC_QUERYCAP: ok VIDIOC_REQBUFS returned 0 (Success) VIDIOC_CREATE_BUFS returned 0 (Success) VIDIOC_QUERYBUF returned 0 (Success) VIDIOC_QUERYBUF returned 0 (Success) VIDIOC_QUERYBUF returned 0 (Success) VIDIOC_G_FMT returned 0 (Success) VIDIOC_QBUF returned 0 (Success) VIDIOC_QBUF returned 0 (Success) VIDIOC_QBUF returned 0 (Success) VIDIOC_STREAMON returned -1 (Broken pipe) なぜ VIDIOC_STREAMON が「 Broken pipe(パイプ破損) 」エラー で故障しているのか 、教えていただけません か? ストリーミングを正常に開始する前に、AP1302のファームウェア、デバイスツリー、メディアパイプライン、またはセンサの初期化に追加の設定が必要ですか? さらに、現時点では「LF_v6.18.2-1.0.0_images_IMX93EVK」というプリビルドイメージを使用しています。 追加のログや情報が必要な場合はお知らせください。 再開まで今しばらくお待ちください。 Re: AP1302 MIPI CSI Streaming Issue on FRDM i.MX93 AEチームと話し合っています。 Re: AP1302 MIPI CSI Streaming Issue on FRDM i.MX93 こんにちは@yipingwang ご返信ありがとうございます。 参考までに、私の回答を以下に記載します。 1. ファームウェアの場所 推奨されているファームウェアのインストール場所と、それぞれの場所を個別に試してみました。カメラプローブは、 ap1302_ar0144_single_fw.binを使用した場合にのみ成功します。 root@imx93evk:~# ls -la /lib/firmware/ap1302_ar0144_single_fw.bin -rw-r--r-- 1 root root 80528 Aug 5 15:36 /lib/firmware/ap1302_ar0144_single_fw.bin root@imx93evk:~# ls -la /lib/firmware/imx/camera/ap1302.fw -rw-r--r-- 1 root root 80528 Aug 5 15:38 /lib/firmware/imx/camera/ap1302.fw AP1302は起動時に正常に検出されました。 root@imx93evk:~# dmesg | grep -i ap1302 ... [ 9.962705] ap1302 2-003c: AP1302 revision 0.2.6 detected しかし、カーネルログにはAP1302に関連するファームウェアの読み込みメッセージは一切見当たりません。 2. ソフトウェア環境 私はFRDM i.MX93ボード用に提供されているプリビルドイメージを使用しています。 root@imx93evk:~# cat /proc/device-tree/model NXP FRDM-IMX93 root@imx93evk:~# cat /proc/cmdline console=ttyLP0,115200 earlycon root=/dev/mmcblk0p2 rootwait rw AP1302は正常に検出され、CSI/ISIデバイスも存在しています。参考までに、ログ全体を添付しました。 3. メディアパイプライン メディアパイプラインは正しく作成されているようです。 root@imx93evk:~# ls /dev/media0 /dev/media0 root@imx93evk:~# ls /dev/video* /dev/video0 /dev/video1 media-ctlの出力はAP1302、CSI、ISIエンティティが有効であることを示しています。参照のために、完全なmedia-ctl出力を添付します。 4. 追加情報 ご依頼いただいた情報については、添付ファイルfourth_point.txtをご参照ください。 5. ストリーミングの失敗 ストリーミングコマンドが失敗した際に、カーネルから追加のメッセージは表示されません。 root@imx93evk:~# dmesg -c root@imx93evk:~# v4l2-ctl -d /dev/video0 --stream-mmap=3 --stream-count=10 VIDIOC_STREAMON returned -1 (Broken pipe) root@imx93evk:~# dmesg 障害後もdmesg出力は空のままなので、根本原因を特定するための追加のカーネルログはありません。 AP1302が正常に検出され、メディアグラフも正しく作成され、VIDIOC_STREAMON中にカーネルエラーも報告されていないので、「 Broken pipe」 エラーでストリーミングが失敗する原因を特定するために、どのような追加のチェックやデバッグステップを教えていただけますか? 再開まで今しばらくお待ちください。 root@imx93evk:~# v4l2-ctl --list-devices mxc-isi-cap (platform:4ae40000.isi): /dev/video0 /dev/video1 /dev/media0 root@imx93evk:~# v4l2-ctl -d /dev/video0 --all Driver Info: Driver name : mxc-isi Card type : mxc-isi-cap Bus info : platform:4ae40000.isi Driver version : 6.18.2 Capabilities : 0xa4201000 Video Capture Multiplanar I/O MC Streaming Extended Pix Format Device Capabilities Device Caps : 0x24201000 Video Capture Multiplanar I/O MC Streaming Extended Pix Format Media Driver Info: Driver name : mxc-isi Model : FSL Capture Media Device Serial : Bus info : platform:4ae40000.isi Media version : 6.18.2 Hardware revision: 0x00000000 (0) Driver version : 6.18.2 Interface Info: ID : 0x0300000a Type : V4L Video Entity Info: ID : 0x00000008 (8) Name : mxc_isi.0.capture Function : V4L2 I/O Pad 0x01000009 : 0: Sink Link 0x0200000c: from remote pad 0x1000007 of entity 'mxc_isi.0' (Video Pixel Formatter): Data, Enabled, Immutable Priority: 2 Video input : 0 (mxc_isi.0.capture: ok) Format Video Capture Multiplanar: Width/Height : 1920/1080 Pixel Format : 'YUYV' (YUYV 4:2:2) Field : None Number of planes : 1 Flags : Colorspace : sRGB Transfer Function : sRGB YCbCr/HSV Encoding: ITU-R 601 Quantization : Limited Range Plane 0 : Bytes per Line : 3840 Size Image : 4147200 User Controls horizontal_flip 0x00980914 (bool) : default=0 value=0 flags=0x00001000 vertical_flip 0x00980915 (bool) : default=0 value=0 flags=0x00001000 alpha_component 0x00980929 (int) : min=0 max=255 step=1 default=0 value=0 flags=0x00001000 root@imx93evk:~# media-ctl -p Media controller API version 6.18.2 Media device information ------------------------ driver mxc-isi model FSL Capture Media Device serial bus info platform:4ae40000.isi hw revision 0x0 driver version 6.18.2 Device topology - entity 1: crossbar (3 pads, 3 links, 1 route) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 routes: 0/0 -> 2/0 [ACTIVE] pad0: SINK,MUST_CONNECT [stream:0 fmt:UYVY8_1X16/1920x1080 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range] <- "csidev-4ae00000.csi":1 [ENABLED,IMMUTABLE] pad1: SINK,MUST_CONNECT <- "mxc_isi.output":0 [ENABLED,IMMUTABLE] pad2: SOURCE [stream:0 fmt:UYVY8_1X16/1920x1080 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range] -> "mxc_isi.0":0 [ENABLED,IMMUTABLE] - entity 5: mxc_isi.0 (2 pads, 2 links, 0 routes) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: SINK [stream:0 fmt:UYVY8_1X16/1920x1080 field:none colorspace:jpeg xfer:srgb ycbcr:601 quantization:full-range compose.bounds:(0,0)/1920x1080 compose:(0,0)/1920x1080] <- "crossbar":2 [ENABLED,IMMUTABLE] pad1: SOURCE [stream:0 fmt:YUV8_1X24/1920x1080 field:none colorspace:jpeg xfer:srgb ycbcr:601 quantization:full-range crop.bounds:(0,0)/1920x1080 crop:(0,0)/1920x1080] -> "mxc_isi.0.capture":0 [ENABLED,IMMUTABLE] - entity 8: mxc_isi.0.capture (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: SINK <- "mxc_isi.0":1 [ENABLED,IMMUTABLE] - entity 16: mxc_isi.output (1 pad, 1 link) type Node subtype V4L flags 0 pad0: SOURCE -> "crossbar":1 [ENABLED,IMMUTABLE] - entity 23: csidev-4ae00000.csi (2 pads, 2 links, 1 route) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 routes: 0/0 -> 1/0 [ACTIVE] pad0: SINK [stream:0 fmt:UYVY8_1X16/1920x1080 field:none colorspace:smpte170m xfer:709 ycbcr:601 quantization:lim-range] <- "ap1302 2-003c":2 [ENABLED] pad1: SOURCE [stream:0 fmt:UYVY8_1X16/1920x1080 field:none colorspace:smpte170m xfer:709 ycbcr:601 quantization:lim-range] -> "crossbar":0 [ENABLED,IMMUTABLE] - entity 28: ap1302 2-003c (3 pads, 2 links, 0 routes) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev4 pad0: SINK [stream:0 fmt:SGRBG12_1X12/1280x800 field:none colorspace:srgb crop.bounds:(0,0)/1280x800 crop:(0,0)/1280x800] <- "ar0144 0":0 [ENABLED,IMMUTABLE] pad1: SINK [stream:0 fmt:SGRBG12_1X12/1280x800 field:none colorspace:srgb crop.bounds:(0,0)/1280x800 crop:(0,0)/1280x800] pad2: SOURCE [stream:0 fmt:UYYVYY8_0_5X24/4224x4092 field:none colorspace:srgb crop.bounds:(0,0)/1280x800 crop:(0,0)/1280x800] -> "csidev-4ae00000.csi":0 [ENABLED] - entity 32: ar0144 0 (1 pad, 1 link, 0 routes) type V4L2 subdev subtype Sensor flags 0 device node name /dev/v4l-subdev3 pad0: SOURCE [stream:0 fmt:SGRBG12_1X12/1280x800 field:none colorspace:srgb] -> "ap1302 2-003c":0 [ENABLED,IMMUTABLE] よろしくお願いします、 ミラフ Re: AP1302 MIPI CSI Streaming Issue on FRDM i.MX93 AP1302プローブが成功したとしても、カメラパイプライン全体が構成され、ストリーミングが開始されることを保証するものではありません。i.MX93では、VIDIOC_STREAMONが-1(破損パイプ)を返すと、通常、メディアパイプラインのコンポーネント(AP1302→MIPI、CSI-2レシーバ、→ISIキャプチャパス)が有効なストリームを開始または交渉できなかったことを意味します。ログには、AP1302 I²Cデバイスが検出されたという情報しか記録されていません。 ap1302 2-003c: AP1302 リビジョン 0.2.6 が検出されました しかし、それは以下のことを確認するものではありません。 ファームウェアのロードに成功しました。 正しいDTBが使用されました。 メディアグラフが作成されました。 CSIレシーバは受信するMIPIデータにロックされています。 AP1302は、対応する出力フォーマットで設定されています。 まず最初に確認すべきことは、ファームウェアの場所と名前です。 FRDM-i.MX93 AP1302のサポートについては、NXPのドキュメントには以下が記載されています: ap1302_60fps_ar0144_27M_2Lane_awb_tuning.bin をダウンロードしてください。 名前をap1302.fwに変更してください。 配置場所： /lib/firmware/imx/camera/ap1302.fw 単に /lib/firmware ではない。 ご確認ください： ls -l /lib/ファームウェア/imx/カメラ/ap1302.fw そしてブートログを確認してください。 dmesg | grep -i firmware dmesg | grep -i ap1302 次のようなメッセージを探してください。 ファームウェアを要求する ファームウェアがロードされました ファームウェアの読み込みに失敗しました 2つ目の確認事項：正しいDTBを使用していますか？ リリースノートによると、AP1302のサポートはi.MX93 EVKデバイスツリーのサポートと関連しています。 確認： cat /proc/device-tree/model cat /proc/cmdline そして、実際にロードされるDTBを特定します。 こちらもご確認ください： dmesg | grep -i ap1302 dmesg | grep -i csi dmesg | grep -i isi 三つ目のチェック:メディアトポロジーの検証 v4l2-ctlを試す前に、メディアグラフが存在するか確認してください: シェル media-ctl -p もっと行を表示 以下のようなエンティティが表示されるはずです。 ap1302 CSI イシ ビデオX /dev/media0が存在しない場合、カメラパイプラインが正しく作成されていません。非常に似たFRDM-i.MX93 AP1302 CASEは以下の通りでした: media-ctl -p /dev/media0 の列挙に失敗しました これはメディアパイプラインがインスタンス化されていないことを示していました。 チェックしてください： ls -l /dev/media* 4つ目の確認事項：交渉済みのフォーマットを検査する 次を実行します。 v4l2-ctl --list-devices そして、 v4l2-ctl -d /dev/video0 --all また： media-ctl -p AP1302のファームウェアは通常、RAWベイヤーではなく、処理済みのYUVフォーマットを出力します。もう一つよくある失敗例は次のとおりです。 AP1302はフォーマットAを出力する ISIはフォーマットB用に構成されています ストリームの起動失敗を引き起こしています。フォーマットの不一致は、STREAMONの失敗やCSIパイプラインのエラーとして現れることが多い。 5回目のチェック：STREAMON実行中のCSIエラーを検査する 別のターミナルを開いて監視します。 dmesg -w そして、以下を実行します。 v4l2-ctl -d /dev/video0 \ --stream-mmap=3 \ --stream-count=10 次のようなメッセージを探してください。 CSIタイムアウト フレーム開始タイムアウト データを受信しませんでした FIFOオーバーフロー MIPIエラー リンクが有効になっていません これらのメッセージは通常、配管破損の本当の原因を明らかにします。 Re: AP1302 MIPI CSI Streaming Issue on FRDM i.MX93 キャプチャを開始する前に、以下のコマンドを使用してパイプラインを設定する必要があります。 $ media-ctl -l "'ap1302 2-003c':2 -> 'csidev-4ae00000.csi':0 [1]" $ media-ctl -V "'ap1302 2-003c':0 [fmt: UYVY8_1X16/1280x800 field:none]" $ media-ctl -V "'ap1302 2-003c':2 [fmt: UYVY8_1X16/1280x800 field:none]" $ media-ctl -V "'ar0144 0':0 [fmt: UYVY8_1X16/1280x800 field:none]" $ media-ctl -V "'csidev-4ae00000.csi':1 [fmt: UYVY8_1X16/1280x800 field:none]" $ media-ctl -V "'crossbar':2 [fmt: UYVY8_1X16/1280x800 field:none]"

MRF13750H Schematic How to convert the MRF13750H-915MHz board to a schematic? The MRF13750H datasheet includes the reference board layout for 915 MHz, but not the schematic.

FRDM-IMX95: SDカードから起動するとシリアル出力がない (プリインストールされたeMMCブートは正常に動作します) こんにちは、NXPコミュニティの皆さん、 私は機械工学と電気工学のバックグラウンドを持っていますが、複雑なシステムオンチップ（SoC）や組み込みオペレーティングシステムに深く取り組むのは今回が初めてです。 私のプロジェクトではFRDM-IMX95の開発ボードを使用しています。私の最終目標は、IPC（プロセス間通信）フレームワークを使用して、2つのオペレーティングシステムを並行して実行することです。 ボードは内部eMMCにプリインストールされたLinuxイメージを同梱していました。これは箱から出してすぐに完璧に動作し、ターミナルモニタープログラムでシリアル出力ログを完全に取得できます。 現在、公式の Starting Guide に従って、Windowsホストマシン上でUUU(Universal Update Utility)を使って標準のLinux BSPイメージをmicroSDカードにフラッシュしようとしています。 Windowsのコマンドプロンプトによると、UUUのフラッシュ処理は「SUCCESS」ステータスで完了します。私は以下の標準コマンドレイアウトを使用しました: ".\uuu.exe -b sd_all imx-boot-imx95-15x15-lpddr4x-frdm-sd.bin-flash_all imx-image-full-imx95evk.wic" 問題点:フラッシュに成功した後、ボードを電源を切り、物理的なブートスイッチをSDブートモードに設定し、SW1 [1:2]を11(オン/オン)に設定します。ボードの電源を入れ直しても、シリアルモニターは完全に空白のままです。テキスト出力やハードウェアの初期化は一切表示されません。 1. ブートチェーンの仕組みについて、私は根本的な誤解をしているのでしょうか？i.MX Linux ユーザーガイドによると、.wicはこのイメージには、ブートローダーイメージ（U-Boot）を含む、4つの必須要素すべてが含まれています。基本的なハードウェア構成ブロックはカードから読み込まれるはずなので、少なくとも最初のU-Boot SPLシーケンスがシリアルモニターに表示されるべきではないでしょうか？ この特定のFRDMバリアントで初心者がよく注意する落とし穴、あるいは隠れたスイッチの要件について、何かアドバイスがあればぜひ教えてください! よろしくお願いいたします。 FRDMトレーニング Re: FRDM-IMX95: No Serial Output when Booting from SD Card (Pre-installed eMMC Boot Works Perfectly こんにちは、 現在、こちらでテストを行い、正確な手順をお伝えします。近日中に更新いたします。 Re: FRDM-IMX95: No Serial Output when Booting from SD Card (Pre-installed eMMC Boot Works Perfectly 調査していただき、またそちらでテストしていただき、ありがとうございます！ご協力ありがとうございます。今後のご報告をお待ちしております。

NFCリーダー・ライブラリ こんにちは、みんな。 DESFire EV3カードに対応したサンプルおよびライブラリのPN7642 NDA版の見つけ方とダウンロード方法。 私はすでに有効なNDAを持っています。 再開まで今しばらくお待ちください。 NFCリーダー・ライブラリ Re: NFC reader library こんにちは、 @dbogovicさん。 あなたの調子が良いといいのですが。 すでに有効なNDAをお持ちの場合、MIFARE DESFireをサポートするPN7642 SDKは、このページの指示に従ってSecure Access Rightsを通じて申請する必要があります: Secure Access Rights | NXP Semiconductors。また、 Secure Access Rights FAQs(セキュリティアクセス権FAQs)も確認することをお勧めします。NXP Semiconductors。 利用可能なセキュアリソースは PN7642製品ページのソフトウェアセクション(セキュア)で確認できます。 よろしくお願いいたします。 エドゥアルド。

S32G399A-RDB3 QNX PFE Driver Problems Greetings, we try to get PFE running on a S32G399A-RDB3 board with QNX. As far as I can tell, this is a valid combination: BSP 37.0 PFE-FW_S32G_1.7.0 PFE-DRV-S32G_A53_QNX_1.4.0 It ends with a no carrier error on all network interfaces. Plugging the cable into different ethernet ports changes nothing.  It used to work with gmac0. Any ideas? io pkt call: io-pkt-v6-hc -p tcpip -d pfe-2 pfe0_mac=000a0b0c0d66,pfe1_mac=001a1b1c1d66,pfe2_mac=002a2b2c2d66,class_fw=/proc/boot/s32g_pfe_class.fw,no_reset,mode0=sgmii,phy0=0,mode1=sgmii,phy1=1 Uboot parameters: Uboot is the same as from the Linux sdcard image with modified parmeters for qnx boot.  setenv hwconfig "pcie0:mode=rc,clock=ext;pcie1:mode=sgmii,clock=ext,fmhz=125,xpcs_mode=2G5" setenv pfeng_mode 'enable,sgmii,sgmii,rgmii' setenv s32cc_gmac_mode disable setenv pfeng enable; s32ccgmac disable; s32ccgmac enable; setenv boot_qnx_atf 'mmc dev 0; fatload mmc 0:1 0x83e00000 s32g399a-rdb3.dtb; pfeng enable; s32ccgmac disable; s32ccgmac enable; fatload mmc 0:1 0x80080000 ifs-s32g399a-rdb.ui; bootm 0x80080000 - 0x83E00000' setenv bootcmd 'run boot_qnx_atf' saveenv Log: U-Boot 2020.04+g156b168010 (Jun 09 2023 - 10:14:25 +0000)   CPU:   NXP S32G399A rev. 1.1 Model: NXP S32G399A-RDB3 DRAM:  3.5 GiB MMC:   FSL_SDHC: 0 Loading Environment from MMC... OK Configuring PCIe0 as RootComplex PCIe0: Failed to get link up PCI: Failed autoconfig bar 1c In:    serial@401c8000 Out:   serial@401c8000 Err:   serial@401c8000 Board revision: RDB3 Revision F Net:   EQOS phy: rgmii @ 1   Warning: eth_eqos (eth0) using random MAC address - 26:e4:e6:43:15:ad eth0: eth_eqosFailed to get speed of XPCS for emac1_xpcs PFE: emac0: sgmii emac1: sgmii emac2: rgmii , eth1: eth_pfeng Hit any key to stop autoboot:  3  2  1  0  switch to partitions #0, OK mmc0 is current device 50640 bytes read in 17 ms (2.8 MiB/s) 11948752 bytes read in 540 ms (21.1 MiB/s) ## Booting kernel from Legacy Image at 80080000 ...    Image Name:       Image Type:   AArch64 Linux Kernel Image (uncompressed)    Data Size:    11948688 Bytes = 11.4 MiB    Load Address: 80080000    Entry Point:  80080000    Verifying Checksum ... OK ## Flattened Device Tree blob at 83e00000    Booting using the fdt blob at 0x83e00000    Loading Kernel Image    Using Device Tree in place at 0000000083e00000, end 0000000083e0f5cf    fixup: pfe0 set to 00:01:be:be:ef:11    fixup: pfe1 set to 00:01:be:be:ef:22    fixup: pfe1: update phy addr to 0x8    fixup: pfe2 set to 00:01:be:be:ef:33   Starting kernel ...   Reserving RAM region for PFE driver on EVB/RDB Done. ClockCycles samples:  0 43600679  1 43600679  2 43600678  3 43600679  4 43600678  5 43600678  6 43600678  7 43600679 All ClockCycles offsets within tolerance Welcome to QNX Neutrino 7.1.0 on the NXP S32G399A RDB Board!! Starting watchdog... Starting serial driver ... Starting Networking driver (/dev/socket)...   Process 4107 (ifconfig) exited status=0.   Process 10 (sh) exited status=0.   Process 9 (dhclient) exited status=0. cp: Can't open source file.  (/proc/boot/libfci_cli)   Process 20489 (cp) exited status=1. Starting SPI driver (/dev/spi0,1,2,3,4,5)... Starting I2C 0/1/2/3/4 driver (/dev/i2c0,1,2,3,4)... Starting USDHC0 memory card driver... [00]     SIM="SDMMC" HBA="imx" [00,0,0] type=00 ver=05 resp=00                       SDMMC:   Process 24596 (chkqnx6fs) exited status=0.   Process 28692 (mount) exited status=0. Starting QSPI Flash driver... Starting USB host driver (/dev/usb/*) Detected QSPI Flash: Macronix MX25UW512, JEDEC 0xC2 - 0x813A, Size: 0x4000000 Launching devb-umass for /dev/usb/* ... #  Process 36891 (sleep) exited status=0. sh: /var/cetitec2/startup.sh: No such file or directory   Process 45081 (sh) terminated signo=0 code=0 by process 0 value=0. slog2info   Jan 01 00:00:00.023                       random.4                  low*     0  qcrypto: loading configuration file '/etc/qcrypto.conf' [qcrypto_common.c(190)] Jan 01 00:00:00.024                    random.4..0                 slog*   700  Random is using the Fortuna PRNG Jan 01 00:00:00.031                       random.4                  low      0  qcrypto: 'openssl' plugin loaded [qcrypto_plugins.c(354)] Jan 01 00:00:00.031                    random.4..0                 slog    700  Selecting timer as an entropy source Jan 01 00:00:00.032                    random.4..0                 slog    700  Registered path names Jan 01 00:00:00.032                    random.4..0                 slog    700  random: starting resmgr Jan 01 00:00:00.032                    random.4..0                 slog    700  random: Daemonizing the process Jan 01 00:00:00.042             devc_serlinflexd.7                 slog*     0  serlinflexd_interrupt_attach: Attaching to interrupt 114 Jan 01 00:00:00.047                        iopkt.8          main_buffer*     0  tcpip starting Jan 01 00:00:00.047                        iopkt.8          main_buffer      0  smmu support is disabled Jan 01 00:00:00.049                        iopkt.8          main_buffer      0  initializing IPsec... Jan 01 00:00:00.049                        iopkt.8          main_buffer      0   done   Jan 01 00:00:00.049                        iopkt.8          main_buffer      0  IPsec: Initialized Security Association Processing.   Jan 01 00:00:00.051                        iopkt.8          main_buffer      0  devnp-pfe-2.so pfe0_mac=000a0b0c0d66,pfe1_mac=001a1b1c1d66,pfe2_mac=002a2b2c2d66,class_fw=/proc/boot/s32g_pfe_class.fw,pfe0_mode=sgmii,pfe0_phy=0,pfe1_mode=sgmii,pfe1_phy=1 Jan 01 00:00:00.052                 io_pkt_v6_hc.8                 slog*     0  INF[src/pfe_drv.c:1377]: VERSION INFO Driver version: 1.4.0 Driver commit hash: 2f3265a49ac18f94ba5e48254c8f870fe7bfc511 PFE_CFG_MULTI_INSTANCE_SUPPORT: 0 PFE_CFG_LOCAL_IF: 6 PFE_CFG_MASTER_IF: 6 PFE_CFG_SC_HIF: 1 PFE_CFG_HIF_RING_LENGTH: 256 PFE_CFG_PFE0_PROMISC: 1 PFE_CFG_PFE1_PROMISC: 1 PFE_CFG_PFE2_PROMISC: 1     Jan 01 00:00:00.052                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1384]: --- Safe IRQ enabled. No InterrupAttach() or InterruptAttach_r() allowed.   Jan 01 00:00:00.052                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_fw.c:83]: 42792 bytes read   Jan 01 00:00:00.053                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_fw.c:89]: Loaded firmware file: /proc/boot/s32g_pfe_class.fw   Jan 01 00:00:00.053                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1477]: MII mode configuration for pfe0/EMAC0 not found. Using SGMII.   Jan 01 00:00:00.053                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1477]: MII mode configuration for pfe1/EMAC1 not found. Using SGMII.   Jan 01 00:00:00.053                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1477]: MII mode configuration for pfe2/EMAC2 not found. Using RGMII.   Jan 01 00:00:00.053                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1495]: Issuing PFE peripheral reset...   Jan 01 00:00:00.274                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1496]: PFE reset OK.   Jan 01 00:00:00.274                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:3519]: PFE CBUS p0x46000000 mapped @ v0x38f2e23000   Jan 01 00:00:00.274                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:3524]: HW version 0x101   Jan 01 00:00:00.274                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hw_feature.c:95]: Silicon S32G3   Jan 01 00:00:00.274                 io_pkt_v6_hc.8                 slog      0  WRN[hw/s32g/pfe_platform_master.c:3536]: Fail-Stop mode disabled   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2687]: PFE_ERRORS:Parity instance created   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2702]: PFE_ERRORS:Watchdog instance created   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2718]: PFE_ERRORS:Bus Error instance created   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2731]: PFE_ERRORS:FW Fail Stop instance created   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2744]: PFE_ERRORS:Host Fail Stop instance created   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2757]: PFE_ERRORS:Fail Stop instance created   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2770]: PFE_ERRORS:ECC Err instance created   Jan 01 00:00:00.275                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:1766]: BMU1 buffer base: p0xc0000000   Jan 01 00:00:00.277                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:1810]: BMU2 buffer base: p0x83000000 (0x200000 bytes)   Jan 01 00:00:00.279                 io_pkt_v6_hc.8                 slog      0  INF[src/oal_irq_qnx.c:117]: PFE BMU IRQ Worker started (IRQ ID: 226)   Jan 01 00:00:00.279                 io_pkt_v6_hc.8                 slog      0  WRN[hw/s32g/pfe_platform_master.c:2194]: The option 'g2_ordered_class_writes' is disabled.   Jan 01 00:00:00.279                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_bmu_csr.c:96]: BMU_EMPTY_INT (BMU @ p0x88000). Pool ready.   Jan 01 00:00:00.279                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_bmu_csr.c:96]: BMU_EMPTY_INT (BMU @ p0x8c000). Pool ready.   Jan 01 00:00:00.281                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2239]: Firmware .elf detected   Jan 01 00:00:00.281                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2248]: Uploading CLASS firmware   Jan 01 00:00:00.281                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_pe.c:609]: Selected FW loading OPs to load 8 PEs in parallel   Jan 01 00:00:00.285                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_pe.c:1945]: pfe_ct.h file version"92367c0e25f21f49217a9b08168ad2c8"   Jan 01 00:00:00.288                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_pe.c:2422]: [FW VERSION] 1.7.0, Build: Jun  2 2023, 13:48:57 (nogitaaa), ID: 0x31454650   Jan 01 00:00:00.406                 io_pkt_v6_hc.8                 slog      0  WRN[hw/s32g/pfe_platform_master.c:2312]: VLAN ID incorrect or not set. Using default VLAN ID = 0x01.   Jan 01 00:00:00.406                 io_pkt_v6_hc.8                 slog      0  WRN[hw/s32g/pfe_platform_master.c:2318]: VLAN stats size incorrect or not set. Using default VLAN stats size = 20.   Jan 01 00:00:00.406                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_l2br.c:1181]: Software vlan hash table @ p0x20001228     Jan 01 00:00:00.406                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_l2br.c:1286]: Fall-back bridge domain @ 0x20000a7c (class)   Jan 01 00:00:00.406                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_l2br.c:1287]: Default bridge domain @ 0x20000a74 (class)   Jan 01 00:00:00.406                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:2412]: Routing table created, Hash Table @ p0x80014000, Pool @ p0x8001c000 (65536 bytes)   Jan 01 00:00:00.407                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64   Jan 01 00:00:00.408                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64   Jan 01 00:00:00.409                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64   Jan 01 00:00:00.508                 io_pkt_v6_hc.8                 slog      0  INF[hw/s32g/pfe_platform_master.c:3705]: Feature err051211_workaround: DISABLED   Jan 01 00:00:00.509                        iopkt.8          main_buffer      0  pfe0   Jan 01 00:00:00.509                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2152]: pfe0: Using PHY mode: MDIO=0, ADDR=0, CLAUSE=0, RESET=0   Jan 01 00:00:00.509                 io_pkt_v6_hc.8                 slog      0  INF[src/oal_irq_qnx.c:117]: PFE HIF0 IRQ Worker started (IRQ ID: 222)   Jan 01 00:00:00.509                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1795]: Adding 00:0a:0b:0c:0d:66 to pfe0   Jan 01 00:00:00.511                        iopkt.8          main_buffer      0  pfe1   Jan 01 00:00:00.511                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe0 not found. Using 1 Gbps/full-duplex.   Jan 01 00:00:00.511                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 0   Jan 01 00:00:00.511                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started   Jan 01 00:00:00.511                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2363]: New PFE device: 0, ID: 0   Jan 01 00:00:00.511                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2152]: pfe1: Using PHY mode: MDIO=1, ADDR=0, CLAUSE=0, RESET=0   Jan 01 00:00:00.511                 io_pkt_v6_hc.8                 slog      0  INF[src/oal_irq_qnx.c:117]: PFE HIF1 IRQ Worker started (IRQ ID: 223)   Jan 01 00:00:00.511                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1795]: Adding 00:1a:1b:1c:1d:66 to pfe1   Jan 01 00:00:00.513                        iopkt.8          main_buffer      0  pfe2   Jan 01 00:00:00.513                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe1 not found. Using 1 Gbps/full-duplex.   Jan 01 00:00:00.513                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 1   Jan 01 00:00:00.513                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started   Jan 01 00:00:00.513                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2363]: New PFE device: 1, ID: 2   Jan 01 00:00:00.513                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2145]: pfe2: Using static PHY mode, RESET=0   Jan 01 00:00:00.513                 io_pkt_v6_hc.8                 slog      0  INF[src/oal_irq_qnx.c:117]: PFE HIF2 IRQ Worker started (IRQ ID: 224)   Jan 01 00:00:00.513                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:1795]: Adding 00:2a:2b:2c:2d:66 to pfe2   Jan 01 00:00:00.515                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe2 not found. Using 1 Gbps/full-duplex.   Jan 01 00:00:00.515                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 2   Jan 01 00:00:00.515                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started   Jan 01 00:00:00.515                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2363]: New PFE device: 2, ID: 4   Jan 01 00:00:00.530                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2702]: Adding 00:0a:0b:0c:0d:66 to pfe0   Jan 01 00:00:00.530                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2707]: Unable to assign MAC address 00:0a:0b:0c:0d:66 to the pfe0   Jan 01 00:00:00.530                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode   Jan 01 00:00:00.538                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_mdio.c:427]: pfe0: PHY @ bus 0 addr 0 not found. Switching to static mode.   Jan 01 00:00:00.538                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2829]: EMAC speed change for SGMII is currently not supported.   Jan 01 00:00:00.538                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0   Jan 01 00:00:00.540                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode   Jan 01 00:00:00.540                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2450]: unable to add 33:33:00:00:00:01 into emac0: 17   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2829]: EMAC speed change for SGMII is currently not supported.   Jan 01 00:00:00.542                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 01:00:5e:00:00:01 to emac0   Jan 01 00:00:00.544                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0   Jan 01 00:00:00.544                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2450]: unable to add 33:33:00:00:00:01 into emac0: 17   Jan 01 00:00:00.544                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0   Jan 01 00:00:00.544                 io_pkt_v6_hc.8                 slog      0  WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17   Jan 01 00:00:00.544                 io_pkt_v6_hc.8                 slog      0  INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode   Jan 01 00:00:00.554               spi_master.24585               normal*     0  Starting spi-master resource manager Jan 01 00:00:00.558               spi_master.24587               normal*     0  Starting spi-master resource manager Jan 01 00:00:00.561               spi_master.24588               normal*     0  Starting spi-master resource manager Jan 01 00:00:00.565               spi_master.24589               normal*     0  Starting spi-master resource manager Jan 01 00:00:00.582          devb_sdmmc_mx8x.24595                 slog*  1800  devb-sdmmc-mx8x 1.00A (Jun 23 2026 09:45:48) Jan 01 00:00:00.583          devb_sdmmc_mx8x.24595                 slog      0  libcam.so (Jun 22 2020 21:33:15) bver 7010003 Jan 01 00:00:00.594          devb_sdmmc_mx8x.24595                 slog   1800  sdio_cd:  insertion path 0, cd state 0x1 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800  SD CID: Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    MID 0x27, OID 0x5048, PNM SD32G Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    PRV 0x62, PSN 0x6c62d132, MDT 4-2023 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800  SD CSD: Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    CSD_STRUCTURE 1, SPEC_VERS 0, CCC 0x5b5 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    TAAC 14, NSAC 0, TRAN_SPEED 50 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    C_SIZE 59023, C_SIZE_MULT 0 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    READ_BL_LEN 9, WRITE_BL_LEN 9 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    ERASE GRP_SIZE 0, GRP_MULT 0, SIZE 127 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    blksz 512, sectors 60440576, dtr 25000000 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800  SD SW CAPS: Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    bus mode 0x3, cmd sys 0x1 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    drv type 0x1, curr limit 0x1 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800    dtr 50000000 Jan 01 00:00:00.644          devb_sdmmc_mx8x.24595                 slog   1800  CFG:  Timing HS, DTR 50000000, Bus Width 4 bit   Jan 01 00:00:00.645          devb_sdmmc_mx8x.24595                 slog    100  cam-disk.so (Jun 22 2020 21:33:17) Jan 01 00:00:00.647          devb_sdmmc_mx8x.24595                 slog      0  scsi_interpret_sense (sdmmc ptl-0:0:0):  cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=1a, error=70, sense=5, asc=24, ascq=0 Jan 01 00:00:00.647          devb_sdmmc_mx8x.24595                 slog      0  scsi_interpret_sense (sdmmc ptl-0:0:0):  cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=5a, error=70, sense=5, asc=24, ascq=0 Jan 01 00:00:00.647          devb_sdmmc_mx8x.24595                 slog      0  scsi_interpret_sense (sdmmc ptl-0:0:0):  cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=5a, error=70, sense=5, asc=24, ascq=0 Jan 01 00:00:01.827          devb_sdmmc_mx8x.24595                 slog   1000  fs-qnx6: Allocation strategy 0 Jan 01 00:00:01.827          devb_sdmmc_mx8x.24595                 slog   1000  fs-qnx6: Use btree directory 0 Jan 01 00:00:01.828          devb_sdmmc_mx8x.24595                 slog   1000  fs-qnx6: fs-qnx6: trim (0,1048576,2) was not requested, and is NOT supported Jan 01 00:00:01.833               io_usb_otg.36885                 slog*     0  main(453)[tid:1]: io-usb-otg (Jun 13 2020 20:10:17) args: -d hcd-ehci-mx28 ioport=0x44064100,irq=243,ulpi,no_stream,verbose=5  Jan 01 00:00:01.835           devf_qspi_s32g.36884                 slog*     0  (devf  t1::f3s_qspi_ident:73) Page size: 256 Jan 01 00:00:01.835           devf_qspi_s32g.36884                 slog      0  (devf  t1::f3s_qspi_ident:74) Total chip size: 0x4000000, Unit size: 0x10000 Jan 01 00:00:01.839               io_usb_otg.36885                 slog      0  ehci_init: Initialiaing with sever version: 2  Jan 01 00:00:01.839               io_usb_otg.36885                 slog      0  ehci_controller_init(4303): devu-hcd-ehci-mx28.so (Apr 19 2024 13:44:54):  args ulpi,no_stream,verbose=5 Jan 01 00:00:01.840               io_usb_otg.36885                 slog      8  usb_enum_port(94)[tid:1]: busno 0, parent -1, port 0, High speed Jan 01 00:00:01.840               io_usb_otg.36885                 slog     11  usb_client_descriptor_get(198)[tid:1]: (type 1, index 0, length 😎 Jan 01 00:00:01.840               io_usb_otg.36885                 slog     12  usb_device_set_address(245)[tid:1]: b:0 devno 0 Jan 01 00:00:01.840               io_usb_otg.36885                 slog     11  usb_client_descriptor_get(198)[tid:1]: (type 1, index 0, length 18) Jan 01 00:00:01.841               io_usb_otg.36885                 slog     11  usb_client_descriptor_get(198)[tid:1]: (type 2, index 0, length 9) Jan 01 00:00:01.841               io_usb_otg.36885                 slog     11  usb_client_descriptor_get(198)[tid:1]: (type 2, index 0, length 25) Jan 01 00:00:01.841               io_usb_otg.36885                 slog      8  usb_enum_port(141)[tid:1]: vid 0x0000, did 0x0000 enumerated(busno 0, devno 0:0) Jan 01 00:00:01.841               io_usb_otg.36885                 slog     11  hub_state_inserted(569)[tid:1]: bdentry 0, dentry 0 0 Jan 01 00:00:01.841               io_usb_otg.36885                 slog     13  hub_configuration_enable(263)[tid:1]: 1 Jan 01 00:00:01.943               io_usb_otg.36885                 slog      0  usbh_timeout_init(203)[tid:1]: Complete Jan 01 00:00:01.954               io_usb_otg.36885                 slog      0  read_vid_pid: ULPI VID 0x0424 PID 0x0009 Jan 01 00:00:01.954               io_usb_otg.36885                 slog      0  s32g_phy_set_vbus: set_vbus off Jan 01 00:00:01.968               io_usb_otg.36885                 slog      0  s32g_phy_set_vbus: set_vbus on Jan 01 00:00:01.979               io_usb_otg.36885                 slog      0  ehci_get_port_status(3568 0x44064100): port=0, tpstatus 10100 e_pstatus 8c001000 Jan 01 00:00:01.979               io_usb_otg.36885                 slog      8  usb_enum_port_extract(172)[tid:7]: (busno 0, pdevno 0, portno 1) Jan 01 00:00:01.979               io_usb_otg.36885                 slog      8  usb_enum_port_extract(192)[tid:7]: status (2) Jan 01 00:00:01.983               devb_umass.36886                 slog*   900  devb-umass 1.00A (Jun 22 2020 21:33:41) Jan 01 00:00:01.984               devb_umass.36886                 slog      0  libcam.so (Jun 22 2020 21:33:15) bver 7010003 Jan 01 00:00:01.985               io_usb_otg.36885                 slog      0  usbdi_client_connect(58)[tid:5]: pid 36886 proc=proc/boot/devb-umass usbdi_client 32eebb9a80 Jan 01 00:00:01.986               io_usb_otg.36885                 slog      0  usbdi_resmgr_connect(310)[tid:5]: usbdi_resmgr_connect: pid 36886 usbdi_client 32eebb9a80  Jan 01 00:00:01.986               devb_umass.36886                 slog      0  usbdi debug path /pps/usb/debug/ doesn't exist   Process 49177 (slog2info) exited status=0. # ifconfig   lo0: flags=8049 mtu 33136 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 pfe0: flags=8843 mtu 1500 capabilities=1f enabled=0 address: 00:0a:0b:0c:0d:66 media: Ethernet none (1000baseT full-duplex) status: active inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 inet6 fe80::20a:bff:fe0c:d66%pfe0 prefixlen 64 scopeid 0x11 pfe1: flags=8802 mtu 1500 capabilities=1f enabled=0 address: 00:1a:1b:1c:1d:66 media: Ethernet none (1000baseT full-duplex) status: no carrier pfe2: flags=8802 mtu 1500 capabilities=1f enabled=0 address: 00:2a:2b:2c:2d:66 media: Ethernet none (1000baseT full-duplex) status: no carrier   Process 57369 (ifconfig) exited status=0. #  Re: S32G399A-RDB3 QNX PFE Driver Problems Ok, so I replaced s32g_pfe_class.fw and s32g_pfe_util.fw with the files from PFE-FW_S32G_1.6.0.zip here: https://nxp.flexnetoperations.com/control/frse/download?agree=Accept&element=14074877 Uboot parameters: setenv boot_qnx_atf 'mmc dev 0; fatload mmc 0:1 0x83e00000 s32g399a-rdb3.dtb; run atf_fdt_0to3; run atf_fdt_4to7; fatload mmc 0:1 0x80080000 ifs-s32g399a-rdb.ui; pfeng enable; s32ccgmac disable; s32ccgmac enable; bootm 0x80080000 - 0x83E00000' setenv atf_fdt_0to3 'fdt addr 0x83e00000; fdt resize; fdt set /cpus/cpu@1 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@100 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@101 cpu-release-addr <0x0 0xa0000010>;' setenv atf_fdt_4to7 'fdt set /cpus/cpu@2 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@3 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@102 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@103 cpu-release-addr <0x0 0xa0000010>;' setenv release_cpus 'run cpu_trap; mp 1 release 0xa0000000; mp 2 release 0xa0000000; mp 3 release 0xa0000000; mp 4 release 0xa0000000; mp 5 release 0xa0000000; mp 6 release 0xa0000000; mp 7 release 0xa0000000;' setenv cpu_trap 'dcache off; mw.l 0xa0000000 0xd503205f; mw.l 0xa0000004 0x58000060; mw.l 0xa0000008 0xb4ffffc0; mw.l 0xa000000C 0xd61f0000; mw.q 0xa0000010 0x00000000; dcache on;' setenv bootcmd 'run boot_qnx_atf' setenv hwconfig "pcie0:mode=rc,clock=ext;pcie1:mode=sgmii,clock=ext,fmhz=125,xpcs_mode=2G5" setenv pfeng_mode 'enable,sgmii,sgmii,rgmii' setenv s32cc_gmac_mode disable saveenv Note: I removed the release_cpus command from boot_qnx_atf because then I would havef a cpu 1 error. Doesn't look much better to me: NOTICE:  BL2: v2.5(release):bsp37.0_rc6-2.5 NOTICE:  BL2: Built : 09:12:21, Jun 13 2023 NOTICE:  BL2: Booting BL31     U-Boot 2020.04+g156b168010 (Jun 09 2023 - 10:14:25 +0000)   CPU:   NXP S32G399A rev. 1.1 Model: NXP S32G399A-RDB3 DRAM:  3.5 GiB MMC:   FSL_SDHC: 0 Loading Environment from MMC... OK Configuring PCIe0 as RootComplex PCIe0: Failed to get link up PCI: Failed autoconfig bar 1c In:    serial@401c8000 Out:   serial@401c8000 Err:   serial@401c8000 Board revision: RDB3 Revision F Net:   EQOS phy: rgmii @ 1   Warning: eth_eqos (eth0) using random MAC address - 16:ec:a0:4e:1d:7c eth0: eth_eqosFailed to get speed of XPCS for emac1_xpcs PFE: emac0: sgmii emac1: sgmii emac2: rgmii , eth1: eth_pfeng Hit any key to stop autoboot:  3  2  1  0  switch to partitions #0, OK mmc0 is current device 50640 bytes read in 17 ms (2.8 MiB/s) 11950600 bytes read in 534 ms (21.3 MiB/s) ## Booting kernel from Legacy Image at 80080000 ...    Image Name:       Image Type:   AArch64 Linux Kernel Image (uncompressed)    Data Size:    11950536 Bytes = 11.4 MiB    Load Address: 80080000    Entry Point:  80080000    Verifying Checksum ... OK ## Flattened Device Tree blob at 83e00000    Booting using the fdt blob at 0x83e00000    Loading Kernel Image    Using Device Tree in place at 0000000083e00000, end 0000000083e0ffff    fixup: pfe0 set to 00:01:be:be:ef:11    fixup: pfe1 set to 00:01:be:be:ef:22    fixup: pfe1: update phy addr to 0x8    fixup: pfe2 set to 00:01:be:be:ef:33   Starting kernel ...   Reserving RAM region for PFE driver on EVB/RDB Done. ClockCycles samples:  0 43642864  1 43642864  2 43642864  3 43642864  4 43642864  5 43642864  6 43642864  7 43642864 All ClockCycles offsets within tolerance Welcome to QNX Neutrino 7.1.0 on the NXP S32G399A RDB Board!! Starting watchdog... Starting serial driver ... Starting Networking driver (/dev/socket)...   Process 4107 (ifconfig) exited status=0.   Process 10 (sh) exited status=0.   Process 9 (dhclient) exited status=0. cp: Can't open source file.  (/proc/boot/libfci_cli)   Process 20489 (cp) exited status=1. Starting SPI driver (/dev/spi0,1,2,3,4,5)... Starting I2C 0/1/2/3/4 driver (/dev/i2c0,1,2,3,4)... Starting USDHC0 memory card driver... [00]     SIM="SDMMC" HBA="imx" [00,0,0] type=00 ver=05 resp=00                       SDMMC:   Process 24596 (chkqnx6fs) exited status=0.   Process 28692 (mount) exited status=0. Starting QSPI Flash driver... Starting USB host driver (/dev/usb/*) Detected QSPI Flash: Macronix MX25UW512, JEDEC 0xC2 - 0x813A, Size: 0x4000000 Launching devb-umass for /dev/usb/* ... # ifconfig   lo0: flags=8049 mtu 33136 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 pfe0: flags=8843 mtu 1500 capabilities=1f enabled=0 address: 00:0a:0b:0c:0d:66 media: Ethernet none (1000baseT full-duplex) status: active inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 inet6 fe80::20a:bff:fe0c:d66%pfe0 prefixlen 64 scopeid 0x11 pfe1: flags=8802 mtu 1500 capabilities=1f enabled=0 address: 00:1a:1b:1c:1d:66 media: Ethernet none (1000baseT full-duplex) status: no carrier pfe2: flags=8802 mtu 1500 capabilities=1f enabled=0 address: 00:2a:2b:2c:2d:66 media: Ethernet none (1000baseT full-duplex) status: no carrier   Process 40985 (ifconfig) exited status=0. #  Process 36891 (sleep) exited status=0. sh: /var/cetitec2/startup.sh: No such file or directory   Process 53273 (sh) terminated signo=0 code=0 by process 0 value=0.   # ifconfig    lo0: flags=8049 mtu 33136 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 pfe0: flags=8843 mtu 1500 capabilities=1f enabled=0 address: 00:0a:0b:0c:0d:66 media: Ethernet none (1000baseT full-duplex) status: active inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 inet6 fe80::20a:bff:fe0c:d66%pfe0 prefixlen 64 scopeid 0x11 pfe1: flags=8802 mtu 1500 capabilities=1f enabled=0 address: 00:1a:1b:1c:1d:66 media: Ethernet none (1000baseT full-duplex) status: no carrier pfe2: flags=8802 mtu 1500 capabilities=1f enabled=0 address: 00:2a:2b:2c:2d:66 media: Ethernet none (1000baseT full-duplex) status: no carrier   # slog2info | grep pfe Jan 01 00:00:00.051 iopkt.8 main_buffer 0 devnp-pfe-2.so pfe0_mac=000a0b0c0d66,pfe1_mac=001a1b1c1d66,pfe2_mac=002a2b2c2d66,class_fw=/proc/boot/s32g_pfe_class.fw Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog* 0 INF[src/pfe_drv.c:1377]: VERSION INFO Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1384]: --- Safe IRQ enabled. No InterrupAttach() or InterruptAttach_r() allowed. Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog 0 INF[src/pfe_fw.c:83]: 49480 bytes read Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog 0 INF[src/pfe_fw.c:89]: Loaded firmware file: /proc/boot/s32g_pfe_class.fw Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1477]: MII mode configuration for pfe0/EMAC0 not found. Using SGMII. Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1477]: MII mode configuration for pfe1/EMAC1 not found. Using SGMII. Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1477]: MII mode configuration for pfe2/EMAC2 not found. Using RGMII. Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1495]: Issuing PFE peripheral reset... Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1496]: PFE reset OK. Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:3519]: PFE CBUS p0x46000000 mapped @ v0x1abef95000 Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:3524]: HW version 0x101 Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hw_feature.c:95]: Silicon S32G3 Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:3536]: Fail-Stop mode disabled Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2687]: PFE_ERRORS:Parity instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2702]: PFE_ERRORS:Watchdog instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2718]: PFE_ERRORS:Bus Error instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2731]: PFE_ERRORS:FW Fail Stop instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2744]: PFE_ERRORS:Host Fail Stop instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2757]: PFE_ERRORS:Fail Stop instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2770]: PFE_ERRORS:ECC Err instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:1766]: BMU1 buffer base: p0xc0000000 Jan 01 00:00:00.277 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:1810]: BMU2 buffer base: p0x83000000 (0x200000 bytes) Jan 01 00:00:00.279 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:2194]: The option 'g2_ordered_class_writes' is disabled. Jan 01 00:00:00.279 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_bmu_csr.c:96]: BMU_EMPTY_INT (BMU @ p0x88000). Pool ready. Jan 01 00:00:00.279 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_bmu_csr.c:96]: BMU_EMPTY_INT (BMU @ p0x8c000). Pool ready. Jan 01 00:00:00.281 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2239]: Firmware .elf detected Jan 01 00:00:00.281 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2248]: Uploading CLASS firmware Jan 01 00:00:00.281 io_pkt_v6_hc.8 slog 0 INF[src/pfe_pe.c:609]: Selected FW loading OPs to load 8 PEs in parallel Jan 01 00:00:00.285 io_pkt_v6_hc.8 slog 0 INF[src/pfe_pe.c:1945]: pfe_ct.h file version"92367c0e25f21f49217a9b08168ad2c8" Jan 01 00:00:00.288 io_pkt_v6_hc.8 slog 0 INF[src/pfe_pe.c:2422]: [FW VERSION] 1.6.0, Build: Mar 15 2023, 12:37:54 (), ID: 0x31454650 Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:2312]: VLAN ID incorrect or not set. Using default VLAN ID = 0x01. Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:2318]: VLAN stats size incorrect or not set. Using default VLAN stats size = 20. Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[src/pfe_l2br.c:1181]: Software vlan hash table @ p0x20001208 Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[src/pfe_l2br.c:1286]: Fall-back bridge domain @ 0x20000a44 (class) Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[src/pfe_l2br.c:1287]: Default bridge domain @ 0x20000a3c (class) Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2412]: Routing table created, Hash Table @ p0x80014000, Pool @ p0x8001c000 (65536 bytes) Jan 01 00:00:00.407 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64 Jan 01 00:00:00.408 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64 Jan 01 00:00:00.409 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64 Jan 01 00:00:00.508 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:3705]: Feature err051211_workaround: DISABLED Jan 01 00:00:00.509 iopkt.8 main_buffer 0 pfe0 Jan 01 00:00:00.509 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2145]: pfe0: Using static PHY mode, RESET=0 Jan 01 00:00:00.510 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1795]: Adding 00:0a:0b:0c:0d:66 to pfe0 Jan 01 00:00:00.512 iopkt.8 main_buffer 0 pfe1 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe0 not found. Using 1 Gbps/full-duplex. Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 0 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2363]: New PFE device: 0, ID: 0 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2145]: pfe1: Using static PHY mode, RESET=0 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1795]: Adding 00:1a:1b:1c:1d:66 to pfe1 Jan 01 00:00:00.514 iopkt.8 main_buffer 0 pfe2 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe1 not found. Using 1 Gbps/full-duplex. Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 1 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2363]: New PFE device: 1, ID: 2 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2145]: pfe2: Using static PHY mode, RESET=0 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1795]: Adding 00:2a:2b:2c:2d:66 to pfe2 Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe2 not found. Using 1 Gbps/full-duplex. Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 2 Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2363]: New PFE device: 2, ID: 4 Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2702]: Adding 00:0a:0b:0c:0d:66 to pfe0 Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2707]: Unable to assign MAC address 00:0a:0b:0c:0d:66 to the pfe0 Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2829]: EMAC speed change for SGMII is currently not supported. Jan 01 00:00:00.532 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.534 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.534 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:00:00:00:01 into emac0: 17 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2829]: EMAC speed change for SGMII is currently not supported. Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 01:00:5e:00:00:01 to emac0 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:00:00:00:01 into emac0: 17 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode # slog2info  | grep io_pkt_v6_hc Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog* 0 INF[src/pfe_drv.c:1377]: VERSION INFO Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1384]: --- Safe IRQ enabled. No InterrupAttach() or InterruptAttach_r() allowed. Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog 0 INF[src/pfe_fw.c:83]: 49480 bytes read Jan 01 00:00:00.052 io_pkt_v6_hc.8 slog 0 INF[src/pfe_fw.c:89]: Loaded firmware file: /proc/boot/s32g_pfe_class.fw Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1477]: MII mode configuration for pfe0/EMAC0 not found. Using SGMII. Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1477]: MII mode configuration for pfe1/EMAC1 not found. Using SGMII. Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1477]: MII mode configuration for pfe2/EMAC2 not found. Using RGMII. Jan 01 00:00:00.053 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1495]: Issuing PFE peripheral reset... Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1496]: PFE reset OK. Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:3519]: PFE CBUS p0x46000000 mapped @ v0x1abef95000 Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:3524]: HW version 0x101 Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hw_feature.c:95]: Silicon S32G3 Jan 01 00:00:00.274 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:3536]: Fail-Stop mode disabled Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2687]: PFE_ERRORS:Parity instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2702]: PFE_ERRORS:Watchdog instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2718]: PFE_ERRORS:Bus Error instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2731]: PFE_ERRORS:FW Fail Stop instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2744]: PFE_ERRORS:Host Fail Stop instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2757]: PFE_ERRORS:Fail Stop instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2770]: PFE_ERRORS:ECC Err instance created Jan 01 00:00:00.275 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:1766]: BMU1 buffer base: p0xc0000000 Jan 01 00:00:00.277 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:1810]: BMU2 buffer base: p0x83000000 (0x200000 bytes) Jan 01 00:00:00.279 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:2194]: The option 'g2_ordered_class_writes' is disabled. Jan 01 00:00:00.279 io_pkt_v6_hc.8 slog 0 INF[src/oal_irq_qnx.c:117]: PFE BMU IRQ Worker started (IRQ ID: 226) Jan 01 00:00:00.279 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_bmu_csr.c:96]: BMU_EMPTY_INT (BMU @ p0x88000). Pool ready. Jan 01 00:00:00.279 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_bmu_csr.c:96]: BMU_EMPTY_INT (BMU @ p0x8c000). Pool ready. Jan 01 00:00:00.281 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2239]: Firmware .elf detected Jan 01 00:00:00.281 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2248]: Uploading CLASS firmware Jan 01 00:00:00.281 io_pkt_v6_hc.8 slog 0 INF[src/pfe_pe.c:609]: Selected FW loading OPs to load 8 PEs in parallel Jan 01 00:00:00.285 io_pkt_v6_hc.8 slog 0 INF[src/pfe_pe.c:1945]: pfe_ct.h file version"92367c0e25f21f49217a9b08168ad2c8" Jan 01 00:00:00.288 io_pkt_v6_hc.8 slog 0 INF[src/pfe_pe.c:2422]: [FW VERSION] 1.6.0, Build: Mar 15 2023, 12:37:54 (), ID: 0x31454650 Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:2312]: VLAN ID incorrect or not set. Using default VLAN ID = 0x01. Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 WRN[hw/s32g/pfe_platform_master.c:2318]: VLAN stats size incorrect or not set. Using default VLAN stats size = 20. Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[src/pfe_l2br.c:1181]: Software vlan hash table @ p0x20001208 Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[src/pfe_l2br.c:1286]: Fall-back bridge domain @ 0x20000a44 (class) Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[src/pfe_l2br.c:1287]: Default bridge domain @ 0x20000a3c (class) Jan 01 00:00:00.406 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:2412]: Routing table created, Hash Table @ p0x80014000, Pool @ p0x8001c000 (65536 bytes) Jan 01 00:00:00.407 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64 Jan 01 00:00:00.408 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64 Jan 01 00:00:00.409 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_chnl.c:1997]: Initializing RX buffer pool. Depth: 256; Buffer Size: 2048; Cache Line Size: 64 Jan 01 00:00:00.508 io_pkt_v6_hc.8 slog 0 INF[hw/s32g/pfe_platform_master.c:3705]: Feature err051211_workaround: DISABLED Jan 01 00:00:00.509 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2145]: pfe0: Using static PHY mode, RESET=0 Jan 01 00:00:00.509 io_pkt_v6_hc.8 slog 0 INF[src/oal_irq_qnx.c:117]: PFE HIF0 IRQ Worker started (IRQ ID: 222) Jan 01 00:00:00.510 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1795]: Adding 00:0a:0b:0c:0d:66 to pfe0 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe0 not found. Using 1 Gbps/full-duplex. Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 0 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2363]: New PFE device: 0, ID: 0 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2145]: pfe1: Using static PHY mode, RESET=0 Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/oal_irq_qnx.c:117]: PFE HIF1 IRQ Worker started (IRQ ID: 223) Jan 01 00:00:00.512 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1795]: Adding 00:1a:1b:1c:1d:66 to pfe1 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe1 not found. Using 1 Gbps/full-duplex. Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 1 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2363]: New PFE device: 1, ID: 2 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2145]: pfe2: Using static PHY mode, RESET=0 Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/oal_irq_qnx.c:117]: PFE HIF2 IRQ Worker started (IRQ ID: 224) Jan 01 00:00:00.514 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:1795]: Adding 00:2a:2b:2c:2d:66 to pfe2 Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2298]: Speed/duplex configuration for pfe2 not found. Using 1 Gbps/full-duplex. Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:336]: Attempt to register HIF client: 2 Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_hif_drv_sc.c:1189]: HIF driver started Jan 01 00:00:00.516 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2363]: New PFE device: 2, ID: 4 Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2702]: Adding 00:0a:0b:0c:0d:66 to pfe0 Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2707]: Unable to assign MAC address 00:0a:0b:0c:0d:66 to the pfe0 Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.531 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2829]: EMAC speed change for SGMII is currently not supported. Jan 01 00:00:00.532 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.534 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.534 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:00:00:00:01 into emac0: 17 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17 Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2829]: EMAC speed change for SGMII is currently not supported. Jan 01 00:00:00.536 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 01:00:5e:00:00:01 to emac0 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:00:00:00:01 into emac0: 17 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17 Jan 01 00:00:00.538 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Process 172057 (slog2info) exited status=0. Jan 01 00:01:01.630 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:00:00:00:01 to emac0 Jan 01 00:01:01.630 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:00:00:00:01 into emac0: 17 Jan 01 00:01:01.630 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2443]: Adding 33:33:ff:0c:0d:66 to emac0 Jan 01 00:01:01.630 io_pkt_v6_hc.8 slog 0 WRN[src/pfe_drv.c:2450]: unable to add 33:33:ff:0c:0d:66 into emac0: 17 Jan 01 00:01:01.630 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2495]: Removing 01:00:5e:00:00:01 from emac0 Jan 01 00:01:01.632 io_pkt_v6_hc.8 slog 0 INF[src/pfe_phy_if.c:2716]: Address 01:00:5e:00:00:01 removed from emac0 Jan 01 00:01:01.632 io_pkt_v6_hc.8 slog 0 INF[src/pfe_drv.c:2663]: pfe0: Disabling promiscuous mode Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your post. By default, the S32G PFE QNX Driver Version 1.4.0 is compatible with S32G PFE Firmware Standard Version 1.6.0, would you mind testing it again with this PFE FW version instead? BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Ok, so I downloaded the  BSP_nxp-s32g-evb_br-710_be-710_SVN984052_JBN51 package you mentioned, modified the .build file and add the  kprintf("Reserving RAM region for PFE driver on EVB/RDB\n"); as_add_containing(0x80000000,0x80000000 + 0x4000000 - 1,AS_ATTR_RAM, "pfe_ddr","ram"); to src/hardware/startup/boards/s32g/s32g399a-rdb/s32g_init_raminfo.c and replace my ifs file with the resulting ifs-s32g399a-rdb.ui. Unfortunately, it doesn't seem to execute the pfe_ddr allocation from above.  Is there anything I need to modify for the uboot parameters or else for this new image to work? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. I suggest referencing the integration manual strictly, refer to the part you mentioned, the following need to be modified before building the QNX BSP. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings, do you know if NXP provides SDCard images that already have the uboot modifications necessary for PFE as in board_cleanup_before_linux? I don't know what packages like binaries_auto_linux_bsp37.0_s32g3_pfe do. Regards Re: S32G399A-RDB3 QNX PFE Driver Problems And what was the PFE firmware version used? JBN51 needs NXP BSP39 which comes with PFE Firmware 1.8.0. But section 2.1.3 of the Pfe Driver 1.7.0 release notes states that only PFW FW 1.10.0 was tested with this release. Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. The tested BSP version is BSP39 combine with QNX driver version 1.7.0 and QNX SDP 7.1 BSP JBN51 BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings, I intend to try the following combination: BSP 33 PFE Driver 1.2.0 PFE FW 1.3.0 Is this officially supported? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings, I intend to try the following combination: BSP 33 PFE Driver 1.2.0 PFE FW 1.3.0 Is this officially supported? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Hello. @Seneca  Thanks for your reply. 1. For the combination, I suggest referencing the documents included in the QNX PFE drivers directly, which included the recommended/tested combination. Other combination may or may not work, you may test it accordingly if indeed needed. 2. From the available information, for QNX PFE drive 1.2, the supported PFE FW is 1.2 with BSP30 used for test BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Hello Chenyin, can you tell me which NXP BSP Version was used by the person who tested the PFE Driver 1.7.0 with the QNXJBN51? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Sorry that there are not such images for publicly downloaded. For "binaries_auto_linux_bsp37.0_s32g3_pfe", seems it is the name of the tgz file from: If so, it includes the pre-built binaries of Linux BSP provisioned by NXP, there are not any QNX related images included.  BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. Would you mind providing the full booting log including all u-boot env information for further checking? BR Chenyin  Re: S32G399A-RDB3 QNX PFE Driver Problems Note: io pkt is not started at the moment. Starting it will not remove the no carrier problem though. U-Boot 2022.04 (Jul 01 2026 - 16:53:39 +0200) SoC: NXP S32G399A rev. 1.1 CPU: ARM Cortex-A53 r0p4 @ max 1300 MHz Model: NXP S32G399A-RDB3 DRAM: 3.5 GiB Core: 306 devices, 25 uclasses, devicetree: board MMC: FSL_SDHC: 0 Loading Environment from MMC... OK In: serial@401c8000 Out: serial@401c8000 Err: serial@401c8000 Board revision: RDB3 Revision F PCIe: BusDevFun VendorId DeviceId Device Class Sub-Class __________________________________________________________________________ pcie@40400000 RootComplex | `-- 01:00.00 0x1957 0x4300 Bridge device 0x04 Net: eth0: ethernet@4033c000 Found PFE version 0x0101 (S32G3) , eth1: pfe0, eth2: pfe1, eth3: pfe2 Hit any key to stop autoboot: 2  1  0 => printenv atf_fdt_0to3=fdt addr 0x83e00000; fdt resize; fdt set /cpus/cpu@1 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@100 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@101 cpu-release-addr <0x0 0xa0000010>; atf_fdt_4to7=fdt set /cpus/cpu@2 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@3 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@102 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@103 cpu-release-addr <0x0 0xa0000010>; baudrate=115200 board_rev=F boot_mtd=booti boot_qnx_atf=mmc dev 0; fatload mmc 0:1 0x83e00000 s32g399a-rdb3.dtb; run atf_fdt_0to3; run atf_fdt_4to7; fatload mmc 0:1 0x80080000 ifs-s32g399a-rdb.ui; bootm 0x80080000 - 0x83E00000 bootargs=root=/dev/ram rw earlycon loglevel=7 bootcmd=run boot_qnx_atf bootdelay=2 console=ttyLF0 cpu_trap=dcache off; mw.l 0xa0000000 0xd503205f; mw.l 0xa0000004 0x58000060; mw.l 0xa0000008 0xb4ffffc0; mw.l 0xa000000C 0xd61f0000; mw.q 0xa0000010 0x00000000; dcache on; eth1addr=00:04:9f:be:ef:00 eth2addr=00:04:9f:be:ef:01 eth3addr=00:04:9f:be:ef:02 ethaddr=0e:46:58:92:0b:68 fdt_addr=0x83000000 fdt_enable_hs400es=fdt addr ${fdt_addr}; fdt rm /soc/mmc no-1-8-v; fdt resize; fdt_file=s32g399a-rdb3.dtb fdt_high=0xffffffffffffffff fdt_override=; fdtcontroladdr=ffa96000 flashboot=echo Booting from flash...; run flashbootargs;mtd read Kernel ${loadaddr};mtd read DTB ${fdt_addr};mtd read Rootfs ${ramdisk_addr};${boot_mtd} ${loadaddr} ${ramdisk_addr} ${fdt_addr}; flashbootargs=setenv bootargs console=${console},${baudrate} root=/dev/ram rw earlycon ;setenv flashsize 0x04000000; hwconfig=serdes0:mode=pcie,clock=ext;pcie0:mode=rc;serdes1:mode=xpcs0&xpcs1,clock=ext,fmhz=125;xpcs1_0:speed=2G5;xpcs1_1:speed=1G image=Image initrd_high=0xffffffffffffffff ipaddr=10.0.0.100 loadaddr=0x80000000 loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}; run fdt_override; loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image} loadtftpfdt=tftp ${fdt_addr} ${fdt_file}; loadtftpimage=tftp ${loadaddr} ${image}; mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot} earlycon mmcboot=echo Booting from mmc ...; run mmcargs; if run loadfdt; then run fdt_fixups; ${boot_mtd} ${loadaddr} - ${fdt_addr}; else echo WARN: Cannot load the DT; fi; mmcdev=0 mmcpart=1 mmcroot=/dev/mmcblk0p2 rootwait rw netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp earlycon netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${image}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then ${boot_mtd} ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then ${boot_mtd}; else echo WARN: Cannot load the DT; fi; fi; else ${boot_mtd}; fi; netmask=255.255.255.0 nfsboot=echo Booting from net using tftp and nfs...; run nfsbootargs;run loadtftpimage; run loadtftpfdt;${boot_mtd} ${loadaddr} - ${fdt_addr}; nfsbootargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs rw ip=${ipaddr}:${serverip}::${netmask}::eth0:off nfsroot=${serverip}:/tftpboot/rfs,nolock,v3,tcp earlycon pfe1_phy_addr=8 pfeng_mode=enable,sgmii,sgmii,rgmii ramdisk_addr=0x90000000 release_cpus=run cpu_trap; mp 1 release 0xa0000000; mp 2 release 0xa0000000; mp 3 release 0xa0000000; mp 4 release 0xa0000000; mp 5 release 0xa0000000; mp 6 release 0xa0000000; mp 7 release 0xa0000000; script=boot.scr serverip=10.0.0.1 skip_scmi_reset_agent=1 stderr=serial@401c8000 stdin=serial@401c8000 stdout=serial@401c8000 Environment size: 3581/8188 bytes => boot switch to partitions #0, OK mmc0 is current device 59970 bytes read in 7 ms (8.2 MiB/s) 9362112 bytes read in 394 ms (22.7 MiB/s) ## Booting kernel from Legacy Image at 80080000 ... Image Name: Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size: 9362048 Bytes = 8.9 MiB Load Address: 80080000 Entry Point: 80080000 Verifying Checksum ... OK ## Flattened Device Tree blob at 83e00000 Booting using the fdt blob at 0x83e00000 Loading Kernel Image Using Device Tree in place at 0000000083e00000, end 0000000083e11fff fixup: pfe1: update phy addr to 0x8 Starting kernel ... board_cleanup_before_linux: QNX PFE code. ethernet@4033c000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! phy_startup() failed: -110FAILED: -110 Found PFE version 0x0101 (S32G3) Found PFE version 0x0101 (S32G3) pfe2 Waiting for PHY auto negotiation to complete......... TIMEOUT ! pfeng_netif pfe1: Failed to establish XPCS link on PFE1 ## Setting pfe_ts clock ... ## Setting ftm0_sys clock ... ## Setting ftm0_ext clock ... ## Setting ftm1_sys clock ... ## Setting ftm1_ext clock ... Reserving RAM region for PFE driver on EVB/RDB ClockCycles samples: 0 166386615 1 166386614 2 166386615 3 166386615 4 166386615 5 166386615 6 166386616 7 166386615 All ClockCycles offsets within tolerance Welcome to QNX Neutrino 7.1.0 on the NXP S32G399A RDB Board!! Starting watchdog... Starting serial driver ... Starting Networking driver (/dev/socket)... Utarting SPI driver (/dev/spi0,1,2,3,4,5)... Starting I2C 0/1/2/3/4 driver (/dev/i2c0,1,2,3,4)... Starting USDHC0 memory card driver... [00] Starting QSPI Flash driver... SIM="SDMMC" HBA="imx" [00,0,0] type=00 ver=05 resp=00 SDMMC: Starting USB host driver (/dev/usb/*) Detected QSPI Flash: Macronix MX25UW512, JEDEC 0xC2 - 0x813A, Size: 0x4000000 Launching devb-umass for /dev/usb/* ... U# slogi 2info Jan 01 00:00:00.022 random.4 low* 0 qcrypto: loading configuration file '/etc/qcrypto.conf' [qcrypto_common.c(190)] Jan 01 00:00:00.023 random.4..0 slog* 700 Random is using the Fortuna PRNG Jan 01 00:00:00.031 random.4 low 0 qcrypto: 'openssl' plugin loaded [qcrypto_plugins.c(354)] Jan 01 00:00:00.031 random.4..0 slog 700 Selecting timer as an entropy source Jan 01 00:00:00.031 random.4..0 slog 700 Registered path names Jan 01 00:00:00.031 random.4..0 slog 700 random: starting resmgr Jan 01 00:00:00.031 random.4..0 slog 700 random: Daemonizing the process Jan 01 00:00:00.041 devc_serlinflexd.7 slog* 0 serlinflexd_interrupt_attach: Attaching to interrupt 114 Jan 01 00:00:10.146 spi_master.8 normal* 0 Starting spi-master resource manager Jan 01 00:00:10.149 spi_master.9 normal* 0 Starting spi-master resource manager Jan 01 00:00:10.152 spi_master.10 normal* 0 Starting spi-master resource manager Jan 01 00:00:10.155 spi_master.11 normal* 0 Starting spi-master resource manager Jan 01 00:00:10.158 spi_master.12 normal* 0 Starting spi-master resource manager Jan 01 00:00:10.161 spi_master.13 normal* 0 Starting spi-master resource manager Jan 01 00:00:10.177 devb_sdmmc_mx8x.19 slog* 1800 devb-sdmmc-mx8x 1.00A (Jul 1 2026 14:10:37) Jan 01 00:00:10.178 devb_sdmmc_mx8x.19 slog 0 libcam.so (Jun 22 2020 21:33:15) bver 7010003 Jan 01 00:00:10.189 devb_sdmmc_mx8x.19 slog 1800 sdio_cd: insertion path 0, cd state 0x1 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 SD CID: Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 MID 0x27, OID 0x5048, PNM SD32G Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 PRV 0x62, PSN 0x6c62d196, MDT 4-2023 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 SD CSD: Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 CSD_STRUCTURE 1, SPEC_VERS 0, CCC 0x5b5 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 TAAC 14, NSAC 0, TRAN_SPEED 50 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 C_SIZE 59023, C_SIZE_MULT 0 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 READ_BL_LEN 9, WRITE_BL_LEN 9 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 ERASE GRP_SIZE 0, GRP_MULT 0, SIZE 127 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 blksz 512, sectors 60440576, dtr 25000000 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 SD SW CAPS: Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 bus mode 0x3, cmd sys 0x1 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 drv type 0x1, curr limit 0x1 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 dtr 50000000 Jan 01 00:00:10.239 devb_sdmmc_mx8x.19 slog 1800 CFG: Timing HS, DTR 50000000, Bus Width 4 bit Jan 01 00:00:10.240 devb_sdmmc_mx8x.19 slog 100 cam-disk.so (Jun 22 2020 21:33:17) Jan 01 00:00:10.242 devb_sdmmc_mx8x.19 slog 0 scsi_interpret_sense (sdmmc ptl-0:0:0): cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=1a, error=70, sense=5, asc=24, ascq=0 Jan 01 00:00:10.242 devb_sdmmc_mx8x.19 slog 0 scsi_interpret_sense (sdmmc ptl-0:0:0): cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=5a, error=70, sense=5, asc=24, ascq=0 Jan 01 00:00:10.242 devb_sdmmc_mx8x.19 slog 0 scsi_interpret_sense (sdmmc ptl-0:0:0): cam_status=c4, scsi_status=2, flag=00000040, vuflag=0008, cmd=5a, error=70, sense=5, asc=24, ascq=0 Jan 01 00:00:10.248 io_usb_otg.21 slog* 0 main(453)[tid:1]: io-usb-otg (Jun 13 2020 20:10:17) args: -d hcd-ehci-mx28 ioport=0x44064100,irq=243,ulpi,no_stream,verbose=5 Jan 01 00:00:10.250 devf_qspi_s32g.20 slog* 0 (devf t1::f3s_qspi_ident:73) Page size: 256 Jan 01 00:00:10.250 devf_qspi_s32g.20 slog 0 (devf t1::f3s_qspi_ident:74) Total chip size: 0x4000000, Unit size: 0x10000 Jan 01 00:00:10.254 io_usb_otg.21 slog 0 ehci_init: Initialiaing with sever version: 2 Jan 01 00:00:10.254 io_usb_otg.21 slog 0 ehci_controller_init(4292): devu-hcd-ehci-mx28.so (Aug 15 2023 16:44:48): args ulpi,no_stream,verbose=5 Jan 01 00:00:10.254 io_usb_otg.21 slog 8 usb_enum_port(94)[tid:1]: busno 0, parent -1, port 0, High speed Jan 01 00:00:10.255 io_usb_otg.21 slog 11 usb_client_descriptor_get(198)[tid:1]: (type 1, index 0, length 😎 Jan 01 00:00:10.255 io_usb_otg.21 slog 12 usb_device_set_address(245)[tid:1]: b:0 devno 0 Jan 01 00:00:10.255 io_usb_otg.21 slog 11 usb_client_descriptor_get(198)[tid:1]: (type 1, index 0, length 18) Jan 01 00:00:10.255 io_usb_otg.21 slog 11 usb_client_descriptor_get(198)[tid:1]: (type 2, index 0, length 9) Jan 01 00:00:10.255 io_usb_otg.21 slog 11 usb_client_descriptor_get(198)[tid:1]: (type 2, index 0, length 25) Jan 01 00:00:10.256 io_usb_otg.21 slog 8 usb_enum_port(141)[tid:1]: vid 0x0000, did 0x0000 enumerated(busno 0, devno 0:0) Jan 01 00:00:10.256 io_usb_otg.21 slog 11 hub_state_inserted(569)[tid:1]: bdentry 0, dentry 0 0 Jan 01 00:00:10.256 io_usb_otg.21 slog 13 hub_configuration_enable(263)[tid:1]: 1 Jan 01 00:00:10.358 io_usb_otg.21 slog 0 usbh_timeout_init(203)[tid:1]: Complete Jan 01 00:00:10.369 io_usb_otg.21 slog 0 read_vid_pid: ULPI VID 0x0424 PID 0x0009 Jan 01 00:00:10.369 io_usb_otg.21 slog 0 s32g_phy_set_vbus: set_vbus off Jan 01 00:00:10.383 io_usb_otg.21 slog 0 s32g_phy_set_vbus: set_vbus on Jan 01 00:00:10.394 io_usb_otg.21 slog 0 ehci_get_port_status(3557 0x44064100): port=0, tpstatus 10100 e_pstatus 8c001000 Jan 01 00:00:10.394 io_usb_otg.21 slog 8 usb_enum_port_extract(172)[tid:7]: (busno 0, pdevno 0, portno 1) Jan 01 00:00:10.394 io_usb_otg.21 slog 8 usb_enum_port_extract(192)[tid:7]: status (2) Jan 01 00:00:10.398 devb_umass.22 slog* 900 devb-umass 1.00A (Jun 22 2020 21:33:41) Jan 01 00:00:10.399 devb_umass.22 slog 0 libcam.so (Jun 22 2020 21:33:15) bver 7010003 Jan 01 00:00:10.400 io_usb_otg.21 slog 0 usbdi_client_connect(58)[tid:5]: pid 22 proc=proc/boot/devb-umass usbdi_client 51ba29fa80 Jan 01 00:00:10.400 io_usb_otg.21 slog 0 usbdi_resmgr_connect(310)[tid:5]: usbdi_resmgr_connect: pid 22 usbdi_client 51ba29fa80 Jan 01 00:00:10.400 devb_umass.22 slog 0 usbdi debug path /pps/usb/debug/ doesn't exist Jan 01 00:00:14.507 qconn.24 slog* 0 Couldn't initialize listen service: tcp (Address family not supported by protocol family) Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for sharing the log. There seems serdes issues existed during the booting phase, may I know if you had done the following modification? (to comment out the init_serdes() function) BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Note: I not both pfe0 and pfe2 work at the same time. And when I ping them from an external machine it assigns pfe0 a funny mac address: arp -a | grep 192 ? (192.168.0.200) at 22:33:44:55:66:77 [ether] on enx00e04c680383 ? (192.168.0.202) at on enx00e04c680383 This is from qnx slog2info: Jan 01 00:00:58.251 iopkt.4121 main_buffer 0 duplicate IP address 192.168.0.200 sent from link address 22:33:44:55:66:77 Re: S32G399A-RDB3 QNX PFE Driver Problems Ok some more news: When I start the network client manually io-pkt-v6-hc -p tcpip pkt_typed_mem=pfe_ddr -d /proc/boot/devnp-pfe-2.so pfe0_mac=000a0b0c0d66,pfe1_mac=001a1b1c1d66,pfe2_mac=002a2b2c2d66,class_fw=/proc/boot/s32g_pfe_class.fw,util_fw=/proc/boot/s32g_pfe_util.fw and set a static ip for pfe0 ifconfig pfe0 192.168.0.200 netmask 255.255.255.0 ifconfig pfe0 down ifconfig pfe0 up I actually get a ping to an external address. Nevertheless, in ifconfig pfe0 still shows ethernet none. It seems to me there are problems negotiating interface speed # slog2info | grep pfe0 Jan 01 00:00:25.515 iopkt.4121 main_buffer 0 /proc/boot/devnp-pfe-2.so pfe0_mac=000a0b0c0d66,pfe1_mac=001a1b1c1d66,pfe2_mac=002a2b2c2d66,class_fw=/proc/boot/s32g_pfe_class.fw,util_fw=/proc/boot/s32g_pfe_util.fw Jan 01 00:00:25.517 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:1460]: MII mode configuration for pfe0/EMAC0 not found. Using SGMII. Jan 01 00:00:25.647 iopkt.4121 main_buffer 0 pfe0 Process 98332 (slog2info) exited status=0. Jan 01 00:00:25.647 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:2124]: pfe0: Using static PHY mode, RESET=0 Jan 01 00:00:25.647 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:2286]: Speed/duplex configuration for pfe0 not found. Using 1 Gbps/full-duplex. Jan 01 00:00:58.251 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:2606]: pfe0: Disabling promiscuous mode Jan 01 00:00:58.251 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:2606]: pfe0: Disabling promiscuous mode Jan 01 00:00:58.251 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:2606]: pfe0: Disabling promiscuous mode Jan 01 00:00:58.251 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:2606]: pfe0: Disabling promiscuous mode Jan 01 00:01:05.966 io_pkt_v6_hc.4121 slog 0 INF[src/pfe_drv.c:2606]: pfe0: Disabling promiscuous mode For Pfe2 it might already fail in uboot in the board_cleanup_before_linux pfe2 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Edit: I can also obtain a ping from pfe2 but it also seems to have problems negotiating the correct speed. I wonder if the above timeout is correct. Re: S32G399A-RDB3 QNX PFE Driver Problems Ok then hopefully these questions will bring me close to the finish line: - How should I set the MAC addresses of pfe0 and pfe2? I understand an attempt is made to set it via io pkt io-pkt-v6-hc -p tcpip pkt_typed_mem=pfe_ddr -d /proc/boot/devnp-pfe-2.so pfe0_mac=000a0b0c0d66,pfe1_mac=001a1b1c1d66,pfe2_mac=002a2b2c2d66,class_fw=/proc/boot/s32g_pfe_class.fw,util_fw=/proc/boot/s32g_pfe_util.fw But when I ping pfe0 from an external machine that machines arp table presents a bogus address ? (192.168.0.200) at 22:33:44:55:66:77 [ether] on enx00e04c680383 On the external machine, tcpdump reveals there doesn't seem to be an arp response from pfe0 which has 192.168.0.200: 08:53:11.208021 IP6 user-Precision-7510 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48 08:53:11.394038 IP6 user-Precision-7510 > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48 08:53:25.750284 ARP, Request who-has 192.168.0.200 tell 192.168.0.200, length 46 08:53:26.641915 IP6 :: > ff02::1:ff0c:d66: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ff0c:d66, length 24 08:53:26.692011 IP6 :: > ff02::1:ff0c:d66: ICMP6, neighbor solicitation, who has fe80::20a:bff:fe0c:d66, length 24 08:53:32.742005 IP6 fe80::20a:bff:fe0c:d66 > ff02::1:ff0c:d66: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ff0c:d66, length 24 When I cast another ping from the external machine I finally get a response: 08:59:22.118282 ARP, Request who-has 192.168.0.200 tell user-Precision-7510, length 28 08:59:22.118553 ARP, Reply 192.168.0.200 is-at 22:33:44:55:66:77 (oui Unknown), length 46 08:59:22.118569 IP user-Precision-7510 > 192.168.0.200: ICMP echo request, id 1, seq 1, length 64 08:59:22.118554 ARP, Reply 192.168.0.200 is-at 00:0a:0b:0c:0d:66 (oui Unknown), length 46 00:0a:0b:0c:0d:66 is what should be the correct mac address. Nevertheless the arp table of the external machine still shows the bogus address arp -a ? (192.168.0.200) at 22:33:44:55:66:77 [ether] on enx00e04c680383 My first guess would be to set them manually in uboot but I see no section in the integration manual that recommends that. - What are the commands to use "fixed link"? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems I see. The ethaddr, eth1addr, eth2addr, eth3addr are set in my uboot but they are not enough to prevent the funny MAC for pfe0. Are there other parameters? Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your updates. Glad that the PFE would ping correctly with the external machine. There are limitation for the PFE driver in QNX: So that it is suggested using the fixed link, while speed changes triggered by AN are not supported. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Ok, just for understanding this right: There is another component that just happens to use 192.168.0.200? And if I use 192.168.1.200 for pfe0 I will be fine? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for the reply. 1. Yes, it is usually by default used by the switch connected. 2. I think the new IP addr you mentioned is fine for the test. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. 1. For setting the MAC address, you may try using the  "io-pkt-v6-hc -p tcpip -d \ pfe1_mac=000a0b0c0d0e,pfe2_mac=001a1b1c1d1e" for example. 2. Since you are using RDB3, while with default settings you tried, the PFE0 connected to the sja1110 switch, usually the 192.168.0.200 is set internally within the SJA1110 SDK, so I suggest not using this IP for testing with PFE0, you may try setting other IP address like 192.168.1.X for PFE0 3. In u-boot, you may try setting the mac address with the "setenv ethaddr/eth1addr/eth2addr xxxx" for each MAC. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings chenyin, I intend to create a bridge interface using the ethernet ports gmac0, pfe0, pfe2. https://www.qnx.com/developers/docs/7.0.0/index.html#com.qnx.doc.neutrino.utilities/topic/b/brconfig.html The connected clients are intended to be in the subnet 192.168.0.X netmask 255.255.255.0  Will this conflict with 192.168.0.200 or anything else? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. If you do want to use the 192.168,.0.x subnet, when not assigning 192.168.0.200 to both PFE0 and the external devices that are connected to the switch, It would be correct for the network connection when you try pinging from outside to PFE0 or vice versa. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. From my understanding, there would not be confliction while not using 192.168.0.200. However, if possible, you may use other subnet instead to avoid possible issues. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings, can you tell me if 192.168.0.200 listens to broadcast calls or something like that? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Would you mind making sure internally? Is there anything 192.168.0.200 does that requires it to have sole control of the subnet? Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. This IP could receive the broadcast packets from linked devices. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings chenyin, a new problem has arisen: The arp handshake fails when I connect a TC387 / FreeRTOS target to pfe_mac2. It works with a regular Linux machine. Any ideas? Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. Since the same setup works with a Linux machine, the problem is more likely to be on the TC387 side (Ethernet driver, TCP/IP stack configuration, or related implementation) rather than on the MAC side. Further packet-level analysis would be needed to confirm the exact cause BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. Since the PFE2 could work correctly with a Linux machine, there may not much issue existed on the S32G side, in order for solving your issue, you may try checking the link status, every frames sent between the two sides and then analyze on them, sorry that I do not know much about the software stack on your Infineon board. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings, when I connect the TC387 to my Linux desktop there are lots of arp/icmp messages produced immediately. The same when I connect my S32G pfe2 port to the Linux desktop. But when I connect the TC387 to the S32G pfe2 port I get not arp or icmp messages at all. For which error messages should I look? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings chenyin, could you please tell me again which ports on the target was exactly pfe0 and pfe2 on s32g399Ardb3? I assumed pfe0 is the left one of the three stacked ports and pfe2 top-center, is this correct? Are there any known problems mixing pfe and gmac? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. I suggest referencing the following picture. PFE0 is connected with the SJA1110, cables connected to P1/2/3 could be linked with PFE0 GMAC could be used with PFE together. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Another thing. Will this uboot line recommended in the integration manual: hwconfig "serdes0:mode=pcie,clock=ext;pcie0:mode=rc;serdes1:mode=xpcs0&xpcs1,clock=ext,fmhz=125;xpcs1_0:speed=2G5;xpcs1_1:speed=1G" Really enable gmac0, pfe0 and pfe2 as individual interfaces or only two of them? Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your reply. 1. For the hwconfig you mentioned, when using them on RDB3, the 3 MACs could all be used. 2. For the error log you shared, sorry that we do not commonly support QNX commands directly, form my personal experience, it may caused by the command used itself, I suggest  re-checking syntax of commands based on the QNX document. 3. Under QNX, there are some limitation for the PFE driver, auto-negotiation is not supported, so you may make sure that the two sides are running with the same speed. BR Chenyin Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings, I tried setting the correct speed on QNX with something like ifconfig pfe2 media 100baseTX mediaopt full-duplex but it wasn't enough. Do I have to do something else, maybe even in uboot parameters? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Greetings, after more research it seem that pfe_mac2 in particular has problems with our 100T1 ethernet adapters. Connecting a Linux Laptop with USB ethernet works fine though. Do you know if pfe_mac2 can connect to this adapter type correctly and if I have to do something special to make it work? Regards Re: S32G399A-RDB3 QNX PFE Driver Problems Ok, so I should be able to use, from the three stacked ports, left port as pfe0 and top center as pfe2 I presume. Bottom center for gmac0. Now, I try to start the interfaces in bridge mode using the following io pkt syntax (note the bridge parameter behind tcp ip): io-pkt-v6-hc -p tcpip bridge pkt_typed_mem=pfe_ddr -d dwceqos-s32g mac=`genmac-random -m`,ptp_off,verbose=5 -d /proc/boot/devnp-pfe-2.so pfe0_mac=000a0b0c0d66,pfe1_mac=001a1b1c1d66,pfe2_mac=002a2b2c2d66,class_fw=/proc/boot/s32g_pfe_class.fw,util_fw=/proc/boot/s32g_pfe_util.fw ifconfig dwc0 192.168.10.100 up ifconfig pfe0 0.0.0.0 up ifconfig pfe2 0.0.0.0 up ifconfig bridge0 create ifconfig bridge0 add dwc0 add pfe0 add pfe2 up This will result in lots of memory errors in slog2info Jan 01 00:04:37.485 io_pkt_v6_hc.159753 slog 0 ERR[src/pfe_drv.c:2996]: (DRIVER) event 1 - Driver runtime error: Mbuf addr out of 32bit. Start @ p0x8df239b58 end @ p0x8df239b82 Jan 01 00:04:38.485 io_pkt_v6_hc.159753 slog 0 ERR[src/pfe_drv.c:2996]: (DRIVER) event 1 - Driver runtime error: Mbuf addr out of 32bit. Start @ p0x8df239558 end @ p0x8df239582 Jan 01 00:04:38.485 io_pkt_v6_hc.159753 slog 0 ERR[src/pfe_drv.c:2996]: (DRIVER) event 1 - Driver runtime error: Mbuf addr out of 32bit. Start @ p0x8df239558 end @ p0x8df239582 Jan 01 00:04:39.451 io_pkt_v6_hc.159753 slog 0 ERR[src/pfe_drv.c:2996]: (DRIVER) event 1 - Driver runtime error: Mbuf addr out of 32bit. Start @ p0x8df239b58 end @ p0x8df239b82 Jan 01 00:04:39.451 io_pkt_v6_hc.159753 slog 0 ERR[src/pfe_drv.c:2996]: (DRIVER) event 1 - Driver runtime error: Mbuf addr out of 32bit. Start @ p0x8df239b58 end @ p0x8df239b82 Is bridge parameter correct in io-pkt-v6-hc call?  Also, I use this allocation from the driver integration manual for both gmac0 and pfe as can be seen in the io-pkt-v6-hc call. Is that a problem? kprintf("Reserving RAM region for PFE driver on EVB/RDB\n"); as_add_containing(0x80000000,0x80000000 + 0x4000000 - 1,AS_ATTR_RAM, "pfe_ddr","ram"); Re: S32G399A-RDB3 QNX PFE Driver Problems Hello, @Seneca  Thanks for your post. 1. I can confirm that the PFE2 port on RDB3 could work correctly with connection to 100T1 network via a 100base-TX<->100base-T1 converter under Linux BSP provisioned by NXP. 2. You may try the following command for a test: io-pkt-v6-hc -p tcpip -d pfe2_link=100-1-2  But I am not very sure for these settings on QNX since it is beyond our S32G community supporting scope,  sorry for your inconvenience. BR Chenyin

reliability data request dear NXP As part of our component evaluation process, we would appreciate receiving the reliability report for the MMX9352XVVXMAC this information is crucial for our design considerations. thank you for your support Re: reliability data request Hi Mike, Thank you for your inquiry. Since you are contacting us using a Gmail address rather than a company email address, could you please provide the following information? Your company name Project details End customer name If you prefer not to share these details here, please feel free to reply directly to the email I sent you. I will need this information when requesting the reliability report from our internal quality team. Thank you in advance for your cooperation. I look forward to your reply. Thank you and have a nice day. Re: reliability data request Dear bar mike,   Thanks for reaching out.   Based on the confirmation: the correct part# should MiMX9352XVVXMAC, not MMX9352XVVXMAC you mentioned.   For the reliability report of MiMX9352XVVXMAC, it is not public, I need to check with our internal quality engineer, will provide it to you once I got it.   Thanks in advance for your patience.  Re: reliability data request Dear mike,    I got our engineers reply, pls advise me if you have signed the NDA (Non disclosure agreement) with NXP?   And we need below information as well.   Your company name Project details End customer name   Look forward to your reply.   Thank you and have a nice day. Re: reliability data request Dear Mike, Could you pls advise us if your company has signed the NDA (Non disclosure agreement) with NXP? If yes, pls provide the NDA # and let me check in our database. If you do not have an NDA , for the assistance please create a Support Request in our ticket system. You need to use your company e-mail. https://www.nxp.com/support/support:SUPPORTHOME?tid=sbmenu Our NDA team will assist you with the NDA process. Look forward to your reply. Otherwise this ticket will automatically close in 7days. ​​​​​​​​​​​​​​Have a wonderful day!  BR Lina 

必要なサポート:Wayland-EGLプラグインおよびIVI-Shellのビデオ再生パフォーマンスの問題 こんにちは、NXP チームの皆様、 Yocto Linuxのセットアップで確認されたWayland/Westonシェル関連の問題について、皆様のサポートをお願いしています。 現在、 kiosk-shellとivi-shellを使用した動画再生の検証を行っています。kiosk-shellを使用すると、wayland-egl プラグインが検出されてアクセス可能になり、フレーム落ちやシステムハングアップもなく、ビデオ再生がスムーズに動作します。しかし、 ivi-shellを使うとwayland-eglプラグインに正しくアクセス・取得できず、動画再生時にフレームロスや断続的なハングが発生します。 問題の概要は以下のとおりです。 項目観察 プラットフォーム i.MX8QXP C0 MEK OS Yocto Linux [ Scarthgap L6.6.5] ウェストンシェル1 キオスクシェル ウェストンシェル2 イヴィシェル グラフィックスインターフェース ウェイランド / ウェイランド-EGL ビデオ再生 GStreamerベースの再生 観察 テストケース結果 キオスクシェル + ウェイランドEGL プラグインは利用可能でアクセス可能です キオスク端末＋ビデオ再生 動画はフレーム落ちやフリーズなくスムーズに再生されます。 ivi-shell + wayland-egl Wayland-eglプラグインが正しく検出・アクセスされません ivi-shell + ビデオ再生 フレーム落ちや断続的なフリーズが観測された サポートが必要です 以下のポイントについてご助言いただけますか? wayland-eglはi.MX8QXP Yocto Linux 6.6.5バージョンの ivi-shell で完全にサポートされているのでしょうか wayland-eglをivi-shellで有効にするために、Weston、IVI-shell、またはコンポジタの設定で何か特別な変更が必要ですか？ i.MX8QXP上でivi-shellを使用する場合、推奨されるweston.iniの設定はありますか？ ivi-shellの動画再生やGPUによるレンダリングに既知の制限はありますか? ivi-shell + wayland-egl + video playbackの参考文献、パッチ、または例のアプリケーションはありますか? フレームの損失やハングは、コンポジターの設定、バッファの処理、GPU/VPUの統合、またはGStreamerのスリンク選択に関連しているのでしょうか? 要求 この問題を解決するためのガイダンス、推奨構成、および利用可能な参考資料やパッチをご提供ください。 Re: Support Required: Wayland-EGL Plugin and Video Playback Performance Issue with IVI-Shell こんにちは、 以下のドキュメントを参照してください。 https://wayland.pages.freedesktop.org/weston/toc/ivi-shell.html https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/AGL-architecture-and-How-to-port-in-i-MX8qm/ta-p/1383200 よろしくお願いいたします。 アルド。

FRDM-IMX95: No Serial Output when Booting from SD Card (Pre-installed eMMC Boot Works Perfectly Hello NXP Community, I am mechanical and electrical engineering background, and this is my first time diving deep into complex System-on-Chips (SoCs) and embedded Operating Systems. For my project, I am using the FRDM-IMX95 development board. My ultimate goal is to run two operating systems in parallel using an IPC (Inter-Process Communication) framework. The board arrived with a pre-installed Linux image on the internal eMMC. This works flawlessly out of the box, and I get full serial output logs in my terminal monitor program. Now, I am trying to follow the official Getting Started Guide to flash the standard Linux BSP image onto a microSD card using UUU (Universal Update Utility) on a Windows host machine. According to the Windows command prompt, the UUU flashing process completes with a "SUCCESS" status. I used the following standard command layout: ".\uuu.exe -b sd_all imx-boot-imx95-15x15-lpddr4x-frdm-sd.bin-flash_all imx-image-full-imx95evk.wic" The Problem: After successful flashing, I turn off the board and configure the physical boot switches for SD Boot Mode by setting SW1 [1:2] to 11 (ON / ON). When I power the board back on, the serial monitor remains completely blank. There is absolutely no text output or hardware initialization visible. 1. Do I have a fundamental misunderstanding of how the boot chain works here? According to the i.MX Linux User's Guide, the .wic image contains all four essential pieces, including the bootloader image (U-Boot). Shouldn't I at least see the initial U-Boot SPL sequence appearing on my serial monitor, since the basic hardware configuration blocks should be read from the card? Any insights, common pitfalls for beginners on this specific FRDM variant, or hidden switch requirements would be highly appreciated! Best regards FRDM-Training Re: FRDM-IMX95: No Serial Output when Booting from SD Card (Pre-installed eMMC Boot Works Perfectly Hello,  I'm testing on my side to share the exact steps for you, I will update soon.  Re: FRDM-IMX95: No Serial Output when Booting from SD Card (Pre-installed eMMC Boot Works Perfectly Thank you for looking into this and testing it on your end! I appreciate the help and look forward to your update.

サポート要件:i.MX8QXP C0 MEK – Yocto Scarthgapにおけるセキュアパーティションアクセスファイル破損問題 こんにちは、NXP チームの皆様、 i.MX8QXP C0 MEKで検出されたセキュアパーティション/ファイルシステムの問題について、皆様のサポートをお願いします。 以下のソフトウェアベースラインを使用しています。 商品詳細 プラットフォーム i.MX8QXP C0 MEK BSP Yocto Linux ヨクトリリース スカースギャップ カーネルバージョン 6.6.5 問題の説明: セキュアパーティションキーを正常に生成できました。しかし、Linuxファイルシステムからセキュアパーティションを使ったりアクセスしようとすると、アクセスが失敗します。場合によっては、アクセス/書き込み操作後にファイルが破損することもあります。 観察： エリアステータス 安全なパーティションキー生成 成功 生成されたキーを用いたファイルシステムアクセス 失敗する ファイル読み書き操作 不安定 ファイル整合性 ファイル破損が確認されました i.MX8QXPのYocto Linuxにおける安全なパーティションアクセスの推奨かつ正しい方法について教えていただけますか? 以下の点について、皆様のご意見をお聞かせください。 i.MX8QXP上でYocto Linuxでセキュアパーティションを作成、フォーマット、マウント、アクセスする推奨方法は何ですか? セキュアパーティションの使用に推奨される特定のファイルシステムの種類はありますか？ カーネル設定、デバイスツリー、OP-TEE、またはYoctoレイヤーの変更は必要ですか? NXP社製のセキュアパーティション処理に関するリファレンス実装やドキュメントはありますか？ 生成されたセキュアキーを使うために、ファイルシステムアクセスの失敗やファイル破損を避けて正しいフローは何でしょうか? 適切な実施方法について、ご検討の上、ご提案いただけますでしょうか。 Re: Support Required: Secure Partition Access-File Corruption Issue on i.MX8QXP C0 MEK – Yocto Scart こんにちは、 BSPのドキュメントを参照してください。この特定のLinuxリリースは当社のリリースに見つからないので、最も近いものを参照することをお勧めします。 つまり、カーネル 6.6.23i.MX Linuxユーザーガイド 第10.5章 ディスク暗号化加速 ファイルシステムではテストにext4を使用しているので、この方法を使うことをおすすめします。必要なカーネル設定や実際の手順についてはドキュメントをご覧ください。 よろしくお願いいたします。 アルド。

Touch Input Configuration for Multiple Displays in AAOS 15 on i.MX8QM Hi Team, I am using 10.1-inch HDMI LCD(E) touchscreen displays with the i.MX8QM board. I need guidance on how to properly connect these displays to the board and configure the touch input for each display. Specifically, I would like to understand which ports/interfaces on the board should be used to connect the touch input (USB). Additionally, I need help in correctly mapping each touch input to its corresponding display in the Android Automotive system. Thanks & Regards Re: Touch Input Configuration for Multiple Displays in AAOS 15 on i.MX8QM Hello, i.MX 8QuadMax, support up to 4 displays: Any combination of 2-4 displays of the following 4 displays: HDMI_TX, LVDS0_CH0, LVDS1_CH0, MIPI_DSI1. Any combination of 2-4 displays of the following 4 displays: LVDS0_CH0, LVDS1_CH0, MIPI_DSI0, MIPI_DSI1. Regarding the input configuration, I suggest you take a look in section 8.3.3.1 Binding the display port with the input port of Android Automotive User's Guide. Best regards. Re: Touch Input Configuration for Multiple Displays in AAOS 15 on i.MX8QM Thank you.

NFC reader library Hello everyone. How to find and download the PN7642 NDA version of the examples and libraries with support for DESFire EV3 cards. I already have an active NDA. Thank you for your support. NFC Reader Library Re: NFC reader library Hello @dbogovic Hope you are doing well. If you already have an active NDA, PN7642 SDK supporting MIFARE DESFire must be requested through the Secure Access Rights by following the instructions from this page: Secure Access Rights | NXP Semiconductors. Also, I would recommend checking the Secure Access Rights FAQs | NXP Semiconductors. Available Secure Resources can be found in PN7642 product page, Software section (Secure). Regards, Eduardo.

MCXA265VPN Layout Suggestion NXP Team, Do you have a MCXA265VPN fanout example?  Need recommended via pad and hole size.  Are the vias in pads or between pins?  Need to have a solid GND plane under BGA? Please help. Thanks Dan Rogers Board Design Re: MCXA265VPN Layout Suggestion Team, Do you have a demo board with suggested routing? I need to know: Trace widths sizes used to route between BGA pins? Via types used and pad sizes with hole size? thru hole, bbvia, stacked? Spacings used between pins after routing? DESCRIPTION = MCXA265VPN, NXP SEMICONDUCTORS MXCA_169_BGA169 (10 mil pads with 19.7 mil pitch between pins) Thank you very much. for your support. Dan Rogers

需要支持：Wayland-EGL 插件和 IVI-Shell 的视频播放性能问题 您好，NXP团队： 我们需要您的帮助，解决我们在 Yocto Linux 系统中遇到的 Wayland/Weston shell 相关问题。 我们目前正在使用kiosk-shell和ivi-shell验证视频播放功能。使用kiosk-shell ，可以检测到 wayland-egl 插件并进行访问，视频播放流畅，不会出现丢帧或系统卡顿的情况。但是，使用ivi-shell时，我们无法正确访问/获取 wayland-egl 插件，视频播放出现丢帧和间歇性卡顿。 以下是问题概要： 项目观察 平台 i.MX8QXP C0 MEK OS Yocto Linux [ Scarthgap L6.6.5] 韦斯顿壳牌1号 信息亭外壳 韦斯顿壳牌2号 ivi-shell 图形界面 韦兰/韦兰-EGL 视频播放 基于 GStreamer 的播放 观察 测试用例结果 kiosk-shell + wayland-egl 插件可用且可访问 信息亭外壳 + 视频播放 视频播放流畅，无丢帧或卡顿现象。 ivi-shell + wayland-egl wayland-egl 插件无法被正确检测/访问。 ivi-shell + 视频播放 观察到掉帧和间歇性卡顿 需要支持 请您协助我们解决以下几个问题？ 在 i.MX8QXP Yocto Linux 6.6.5 版本上， ivi-shell是否完全支持 wayland-egl？ 要使用 IVI-shell 启用 wayland-egl，是否需要对 Weston、IVI-shell 或合成器进行任何特定的配置更改？ i.MX8QXP 上的 ivi-shell 有什么推荐的 weston.ini 配置吗？ ivi-shell 在视频播放或 GPU 加速渲染方面是否存在任何已知限制？ 是否有适用于 ivi-shell + wayland-egl + 视频播放的参考文档、补丁或示例应用程序？ 丢帧/卡顿是否与合成器配置、缓冲区处理、GPU/VPU 集成或 GStreamer 接收器选择有关？ 申请它 请提供指导、推荐配置以及任何可用的参考文档或补丁程序来解决此问题。 Re: Support Required: Wayland-EGL Plugin and Video Playback Performance Issue with IVI-Shell 你好， 您可以参考以下文档： https://wayland.pages.freedesktop.org/weston/toc/ivi-shell.html https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/AGL-architecture-and-How-to-port-in-i-MX8qm/ta-p/1383200 此致敬礼/Saludos， 阿尔多。

FRDM-IMX95：从 SD 卡启动时无串口输出（预装 eMMC 启动完全正常） NXP社区的各位朋友，大家好！ 我拥有机械和电气工程背景，这是我第一次深入研究复杂的片上系统 (SoC) 和嵌入式操作系统。 我的项目使用的是 FRDM-IMX95 开发板。我的最终目标是使用 IPC（进程间通信）框架并行运行两个操作系统。 主板到货时，其内部 eMMC 上预装了 Linux 镜像。它开箱即用，完美运行，我的终端监测程序中可以获取完整的串行输出日志。 现在，我正在尝试按照官方入门指南，使用 Windows 主机上的 UUU（通用更新实用程序）将标准 Linux 电路板支持包映像刷写到 microSD 卡上。 根据 Windows 命令提示符显示，UUU 刷新过程以“成功”状态完成。我使用了以下标准命令布局： “.\uuu.exe -b sd_all imx-boot-imx95-15x15-lpddr4x-frdm-sd.bin-flash_all imx-image-full-imx95evk.wic” 问题：成功刷写固件后，我关闭电路板，并将物理启动开关配置为 SD 启动模式，方法是将 SW1 [1:2] 设置为 11（ON / ON）。当我重新启动电路板时，串口监视器完全空白。完全没有任何文本输出或硬件初始化信息可见。 1. 我是否对这里的启动链的工作原理存在根本性的误解？根据i.MX Linux 用户指南，.wic镜像包含所有四个基本部分，包括引导加载程序镜像（U-Boot）。既然基本的硬件配置块应该从卡上读取，那么我的串口监视器上至少应该能看到初始的 U-Boot SPL 序列吧？ 任何关于此特定 FRDM 变体的见解、初学者常犯的错误或隐藏的开关要求都将不胜感激！ 顺祝商祺！ FRDM 培训 Re: FRDM-IMX95: No Serial Output when Booting from SD Card (Pre-installed eMMC Boot Works Perfectly 你好， 我这边正在进行测试，稍后会把具体步骤分享给你，稍后会更新。 Re: FRDM-IMX95: No Serial Output when Booting from SD Card (Pre-installed eMMC Boot Works Perfectly 感谢您调查并进行了测试！感谢您的帮助，期待您的最新消息。

LLCEの例とU-boot こんにちは、 Goldbox上でLLCEのサンプルを動作させようとしています。 CAN2CANのサンプルコードを少し修正したところ、S32DSからデバッグすると正常に動作しました。 しかし、U-bootから実行しようとすると、実行はされるものの、U-boot自体がハングアップしてしまう。 私が実行しているコマンドは以下のとおりです。 dcache オフ; mw.q 0x34000000 0x0 0x100000; dcache オン fatload mmc 0:2 ${loadaddr} /llce.elf bootm7 ${loadaddr} VTABLE バス上でCANトラフィックは確認できているので例は実行中ですが、U-bootがフリーズしてコマンドを受け付けられなくなりました。 デバッグの結果、問題の原因はPlatformInit()呼び出し、特にクロックを設定するコードにあることが分かりました。 しかし、そのコードを削除すると、サンプルコードは動作しなくなります。 何かご提案はありますか？ Re: LLCE example and U-boot こんにちは、 @GioMusto ご返信ありがとうございます。 はい、S32G2向けであってG3ではありませんが、導入された方法は似ています。 初期バージョンのソフトウェアパッケージに基づいているため、最近のバージョンのソフトウェアの組み合わせを使った際のステップバイステップガイドとは見なせません。 BR チェイン Re: LLCE example and U-boot こんにちは、 @chenyin_h さん、ご返信ありがとうございます。 あなたが投稿したガイドはS32G2用だと分かりました。S32G3でも同じですか？それとも何か違いがありますか？ 注意すべき点について何かご提案はありますか？よくある問題などです。 Re: LLCE example and U-boot こんにちは、 @GioMusto 投稿ありがとうございます。 ご指摘の問題は、M側とA側の間のクロックまたはその他のリソースの競合が原因である可能性があります。 1. S32G製品では、デフォルト設定でA53側で動作するBSPがシステムへの排他的アクセス権を持つことを前提と設計されており、他のソフトウェアコンポーネントによる潜在的な競合を考慮しません。一方、Mコアアプリケーションではクロックやメモリなどの重要なリソースにも触れる可能性があります。重要なリソースに関して、起こりうる競合や再構成を避けるために、コードのあらゆる部分に注意を払う必要があります。 2. M7アプリケーションとLinux BSPを同時に動作させる場合、推奨される方法は、まずM7ブートローダーを起動してリソースを管理することです。これはAN13750で紹介されました BR チェイン

i.MX8QM 上 AAOS 15 中多显示器触摸输入配置 大家好， 我使用的是 10.1 英寸 HDMI LCD(E) 触摸屏显示器，搭配 i.MX8QM 主板。我需要指导，如何正确地将这些显示屏连接到板，并配置每个显示屏的触摸输入。具体来说，我想了解应该使用板上的哪些端口/接口来连接触摸输入（USB）。此外，我还需要帮助，将每个触摸输入正确映射到 Android Automotive 系统中对应的显示屏。 谢谢！此致敬礼！ Re: Touch Input Configuration for Multiple Displays in AAOS 15 on i.MX8QM 你好， i.MX 8QuadMax，最多支持 4 个显示器： 以下 4 个显示器中的 2-4 个显示器的任意组合：HDMI_TX、LVDS0_CH0、LVDS1_CH0、MIPI_DSI1。 以下 4 个显示器中的 2-4 个显示器的任意组合：LVDS0_CH0、LVDS1_CH0、MIPI_DSI0、MIPI_DSI1。 关于输入配置，我建议您查看Android Automotive 用户指南的 8.3.3.1 节“将显示端口与输入端口绑定”。 顺祝商祺！ Re: Touch Input Configuration for Multiple Displays in AAOS 15 on i.MX8QM 谢谢！

Support Required: Wayland-EGL Plugin and Video Playback Performance Issue with IVI-Shell Hi NXP Team, We need your support regarding a Wayland/Weston shell-related issue observed in our Yocto Linux setup. We are currently validating video playback with kiosk-shell and ivi-shell. With kiosk-shell, the wayland-egl plugin is detected and accessible, and video playback is working smoothly without frame drops or system hang. However, with ivi-shell, we are not able to access/get the wayland-egl plugin properly, and video playback is showing frame loss and intermittent hang. Please find the issue summary below: Item Observation Platform i.MX8QXP C0 MEK OS Yocto Linux [ Scarthgap L6.6.5] Weston Shell 1 kiosk-shell Weston Shell 2 ivi-shell Graphics Interface Wayland / Wayland-EGL Video Playback GStreamer-based playback Observation Test Case Result kiosk-shell + wayland-egl Plugin is available and accessible kiosk-shell + video playback Video plays smoothly without frame loss or hang ivi-shell + wayland-egl wayland-egl plugin is not getting detected/accessed properly ivi-shell + video playback Frame drops and intermittent hang observed Support Required Could you please help us with the below points? Is wayland-egl fully supported with ivi-shell on i.MX8QXP Yocto Linux 6.6.5 version Are there any specific Weston, IVI-shell, or compositor configuration changes required to enable wayland-egl with ivi-shell? Is there any recommended weston.ini configuration for ivi-shell on i.MX8QXP? Are there any known limitations with ivi-shell for video playback or GPU-accelerated rendering? Is there any reference document, patch, or example application available for ivi-shell + wayland-egl + video playback? Could the frame loss/hang be related to compositor configuration, buffer handling, GPU/VPU integration, or GStreamer sink selection? Request Please provide your guidance, recommended configuration, and any available reference documents or patches to resolve this issue. Re: Support Required: Wayland-EGL Plugin and Video Playback Performance Issue with IVI-Shell Hello, You may refer to the following documentation: https://wayland.pages.freedesktop.org/weston/toc/ivi-shell.html https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/AGL-architecture-and-How-to-port-in-i-MX8qm/ta-p/1383200 Best regards/Saludos, Aldo.