Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
不可修改的闪存 我希望保护S32k开发板上包含启动映像和应用程序镜像的内部闪存区域。这些镜像存储在程序闪存(PFlash)中,相关的应用程序数据可能存储在数据闪存(DFlash)中。 在批准的软件编程完成后,是否有办法使选定的区域不可写不可擦?理想情况下,这种保护措施可以防止通过应用程序软件、JTAG/调试访问、编程工具、批量擦除、恢复机制和生命周期转换进行修改。 S32K344 是否提供了一种永久性机制,使选定的 PFlash 或 DFlash 扇区不可写不可擦? 如果无法提供永久保护,NXP 推荐的最强可逆保护配置是什么? 是否存在任何受支持的基于硬件的方法,例如专用引脚或跳线控制信号,可以启用或阻止对内部 PFlash 和 DFlash 进行编程? Re: Not Modifiable Flash 你好, S32K344 不提供用户可访问的 OTP 机制来永久锁定任意 PFlash 或 DFlash 扇区以防止擦除/写入。 S32K344 上没有与 MPC57xx OTP 闪存扇区锁定客户端等效的机制。 启动和应用程序映像的保护旨在通过 HSE 安全架构(安全启动、生命周期管理、调试身份验证和身份验证固件更新)来实现,而不是对 PFlash 扇区进行永久 OTP 锁定。 顺祝商祺! Peter Re: Not Modifiable Flash 是否存在硬件级别的方法来禁用或物理限制 JTAG 或其他编程接口访问、擦除或修改 S32K344 内部的 PFlash 和 DFlash(永久或临时),例如物理隔离 JTAG 信号、移除调试连接或通过外部硬件控制访问?
View full article
Not Modifiable Flash I would like to protect the internal flash regions containing the boot image and application image on the S32k board. The images are stored in Program Flash (PFlash), with related application data potentially stored in Data Flash (DFlash). Is there a way to make the selected regions non-writable and non-erasable after the approved software is programmed. Ideally, this protection would prevent modification through application software, JTAG/debug access, programming tools, mass erase, recovery mechanisms, and lifecycle transitions. Does the S32K344 provide a permanent mechanism for making selected PFlash or DFlash sectors non-writable and non-erasable? If permanent protection is unavailable, what is NXP’s recommended configuration for the strongest reversible protection? Is there any supported hardware-based method, such as a dedicated pin or jumper-controlled signal, that can enable or prevent programming of internal PFlash and DFlash? Re: Not Modifiable Flash Hello, S32K344 does not provide a user-accessible OTP mechanism to permanently lock arbitrary PFlash or DFlash sectors against erase/write. There is not mechanism equivalent to the MPC57xx OTP flash-sector locking clients is available on S32K344. Protection of boot and application images is intended to be implemented using the HSE security architecture (secure boot, lifecycle management, debug authentication, and authenticated firmware update), rather than permanent OTP locking of PFlash sectors. Best regards, Peter Re: Not Modifiable Flash Is there a hardware-level method to disable or physically restrict JTAG or another programming interface from accessing, erasing, or modifying the S32K344 internal PFlash and DFlash (permanently or not) like physically isolating the JTAG signals, removing the debug connection, or controlling access through external hardware for example?
View full article
100kW PMSMインバータにS32K396制御基板を使用することに関するお問い合わせ 親愛なるNXPサポートチームへ、 こんにちは、 現在、100kW級のPMSMインバータ駆動モジュールの開発プロジェクトに取り組んでいます。 目標とする仕様は概ね以下のとおりです。 DCリンク電圧:800V モーター位数電流:250アーム モータータイプ:PMSM 出力レベル:約100kW 研究中、NXPの「S32K396付き3相永久磁石同期モーター制御開発キット」に非常に興味を持つようになりました。 自社で100kWのパワーステージを開発する必要があるため、開発キットのS32K396ベースの制御基板のみを使用し、ゲートドライバーとIGBTパワーステージは自分たちで設計する予定です。 開発キットの回路図を確認した結果、制御基板は外部コネクタを通じてパワーステージとインターフェースしていると理解しています。 三相インバータを制御するためのPWM信号 リゾルバ関連の信号 三相電流検出信号 DCリンク電圧検出 DCリンク電流検出 私たちの理解が正しいか確認していただけますか? もしそうなら、私たちの想定するシステム構成は以下の通りです。 NXP S32K396制御ボードを使用して、当社独自の100kWインバータ電力段用のPWM信号を生成します。 位相電流測定にはホール効果電流センサを使用し、対応するアナログ信号を制御基板に送ります。 リゾルバインターフェース回路は、NXP開発キット/電源基板で使用されているリゾルバ回路を参照して実装します。 制御基板のADC入力に、必要なDCリンク電圧および電流検出信号を供給してください。 つまり、既存のS32K396制御基板とモーター制御ソフトウェアプラットフォームを使用しつつ、元のパワーステージを自社製の800 V / 250アームズインバーターハードウェアに置き換えたいと考えています。 以下の質問について、ご意見をいただければ幸いです。 この構成で、カスタムの高出力インバータ段にS32K396制御基板を使用することは可能でしょうか? 外部ゲートドライバー/電源段を制御基板に接続する際に考慮すべきインターフェース要件、制限、注意点はありますか? S32K396を基に100kWクラスのPMSMインバーターを開発するのに役立つアプリケーションノート、リファレンス・デザイン、回路図、ソフトウェア例、その他の技術文書などはありますか? NXPは約100kW、800VのPMSMインバーター向けのリファレンス設計や評価プラットフォームを提供している、または推奨できるのでしょうか? 追加の情報やご提案があれば、大変ありがたく思います。 再開まで今しばらくお待ちください。 よろしくお願いいたします。 ヒョン・ムンソン Re: Inquiry About Using the S32K396 Control Board for a 100 kW PMSM Inverter こんにちは、 あなたの理解は概ね正しいです。S32K396コントローラは、MCSPTR2AK396キットに付属する低電圧インバータとは独立して使用可能で、必要なフィードバック信号(位相電流、直流バス電圧/電流、ローター位置、故障信号など)が新しいパワーステージインターフェースに適応されていれば可能です。MCSPTR2AK396キットは主に低電圧モーター制御開発プラットフォームおよびソフトウェアイネーブルメントキットとして意図されています。  100kW前後の牽引クラス**アプリケーション**については、NXPのEV牽引インバーター**リファレンス・デザイン**(EV-INVERTERGEN1 / EV-INVERTERGEN2)も検討するとよいでしょう。これらは高電圧・高出力の電気**車載**インバーター**アプリケーション**を想定しており、MCSPTR2AK396評価キットよりも参考になります。S32K39ファミリは、NXPの牽引インバーターエコシステム内でサポートされているモータ制御プラットフォームの一つです。  MCSPTR2AK396ドキュメント(AN14481)は、PMSM FOCソフトウェアアーキテクチャ、ペリフェラル設定、電流センシング、リゾルバ統合、FreeMASTER/MCATサポートの参考文献として依然として有用です。  EVトラクションインバータープラットフォームの詳細はこちらでご覧いただけます: NXP EV パワーインバーターソリューション。 BR、ペトル
View full article
i.MXRT106x HAB がブートに失敗し、HAB ログが AUTHENTICATION_STATUS で停止します。非標準の IVT エントリ ポイントです。 背景:私は痞子衡氏が開発したNXP-MCUBootUtilityを使用して、i.MXRT106xのHABシグネチャに取り組んでいます。このツールにファームウェアのバイナリを読み込むと、次のように表示されます:**ブート可能なファイルヘッダーから有効な割り込みベクターテーブルアドレスが見つからない**。 バイナリを16進エディタで検査した後: - IVTエントリポイントは`0x20209401`、イメージロードベースアドレスは`0x20208000`で、これはファイルオフセット`0x1400`に対応します。 - このコードセグメントは、オフセット `0x2000` までのブート関連のブートデータフローと同一です。 - 通常、IVTエントリはリセットベクタアドレスを指す必要があります(参照例ではオフセット`0x2005`を指しています)。しかし、私のファームウェアでは、IVTエントリはオフセット`0x1400`を指しています。これがツール解析エラーの根本原因だと推測されます。 CSTワークフローに関するさらなる調査: CST署名の高レベルなロジックは理解しています。ファームウェア内の空きブロックを見つけ、IVT CSFポインタをこの場所に設定し、標準のCSFテンプレートを使用し、`[Authenticate Data]`ブロックセクションを変更して、署名検証の開始アドレスとサイズ範囲を設定します。 私のファームウェアは、FCB、IVT、DCD、およびブートデータを含む完全な起動可能なイメージであり、HABクロージャなしでハードウェア上で正常に起動します。 CSFブロックを以下のように設定しました。 Blocks=0x20208000 0x1000 0x126c0 "my_firmware.bin" また、証明書のパスもそれに合わせて更新しました。 CST v3.00.01 コマンドを実行しました。 cst.exe -i .\input_resign.csf -o sig.bin CSTの実行はエラーなく完了し、`sig.bin`が生成されました。 出力と元のバイナリを比較すると、正確には2つの変更点があります。 1. IVT内のオフセット`0x1018`にあるCSFポインタフィールドが更新されます。 2. CSFシグネチャデータはオフセット`0x136c0`に追加されます。 この署名済みイメージをハードウェアに書き込むと: 1.HABが閉じられていない(SEC_CONFIGが閉じられていない)場合、ファームウェアは正常に動作します。 2. SRKヒューズビットを書き込み、HABを閉じた後、ファームウェアが起動に失敗します。 JTAG経由でメモリアドレス`0x2020523c`から長さ256バイトのHABログをダンプしました。ログの内容は以下のとおりです。 ----------------------------------------------------------------------------------------- | Log Entry | Description ----------------------------------------------------------------------------------------- 0x00010002: BOOTMODE_INTERNAL 0x000200cc: SEC_CONFIG_CLOSED 0x00030001: DIR_BT_DIS_VALUE1 0x00040000: BT_FUSE_SEL_VALUE0 0x00050000: PRIM_IMAGE_SELECT 0x00060008: PRIM_BOOTDEVICE_FLEXSPI_NOR 0x00070000: DEVICE_INIT_CALL 0x000700f0: DEVICE_INIT_PASS 0x00090000: AUTHENTICATION_STATUS **私の質問:** 1.実際のHABイベントコードはどこにありますか?参考文献によると、HAB認証の合格/失敗は明示的なイベントコードを生成するはずです。しかし、私のログは『AUTHENTICATION_STATUS』で止まり、その後のイベントエントリーはありません。HAB認証が成功したか失敗したかをどうやって判断すればいいですか? 2. 「blhost」ツールを試しましたが、i.MXRT1061でHABログ読み取りコマンドが動作するのを見つけられません。HABの完全な状態を読み取る他の方法はありますか? 3. 私の署名ワークフローは有効か?私のイメージでは、非標準のIVTエントリポイントを使用しています(リセットベクタオフセット`0x2005`ではなく、オフセット`0x1400`を指しています)。このような画像はCSTで正しくHAB署名できますか? オフセット`0x1000`にある追加のIVTヘッダーバイト: D1 00 20 40 01 94 20 20 00 00 00 00 80 90 20 20 20 90 20 20 00 90 20 20 00 00 00 00 00 00 00 00 00 80 20 20 80 99 01 00 00 00 00 00 00 80 20 20 80 99 01 00 52 44 49 52 00 00 00 00 E4 B8 21 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 00 08 41 CC 00 04 04 CSTツールバージョン:3.00.01 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry こんにちは、 @eleven さん。 最新情報のご提供ありがとうございます。まず、boot.binの最初のバイトがFCBなのかIVTなのかを確認する必要があると思います。FCBの場合、位置合わせの問題がまだ残っている可能性があります。 さらに、HAB障害コードの読み取りと解釈のプロセスにおいて、このガイドが役立つはずです。https: //community.nxp.com/t5/i-MX-Security/HAB-event-in-a-Closed-i-MX-chip/ta-p/1120239 それでも問題の根本原因を特定できない場合は、MCUBootUtilityを使用してHAB署名を直接生成し、バイナリ差分を実行することで、結果を相互検証できる可能性があります。 よろしくお願いします、 ギャビン Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry こんにちは、ギャビンさん。 詳細なご回答をいただき、誠にありがとうございました。最初の投稿で、テスト環境について十分に説明できていなかったと思います。 ご提案いただいたとおり、ブロック設定の調整は既に試してみました。私は両方を試しました。 ブロック = 0x20208000 0x1000 0x126c0 "my_firmware.bin" そして、IVTからファームウェアの最後まで認証を行うために、複数のブロックエントリに分割します。 ブロック = 0x20209000 0x0 0x40 "boot.bin",\ 0x20209080 0x80 0xf80 "boot.bin",\ 0x2020a000 0x1000 0x11c00 "boot.bin" 私の意図は、IVTからアプリケーションコードの最後まで認証することでした。しかし、これらの変更後も起動時の動作は変化しなかった。 私はMCUBootUtility v6.5.1を使用しています。内蔵のブートログ解析と手動のJTAGメモリダンプは、どちらも全く同じログ結果を示す。 また、NORフラッシュメモリの最小ブートオフセットは0x1400であると理解しています。私が明確にしたかったのは、私のIVTエントリポイントは、参照例に見られるようなオフセット0x2005にある一般的なリセットベクタではなく、ブート関連のコードを指しているということです。 ご指導いただき、改めて感謝申し上げます。デバッグ情報をさらに収集するために、sdphostを使用して追加のテストを実行します。そこからもっと手がかりが得られればいいのですが。 よろしくお願いします、 11 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry こんにちは、 @eleven さん。 IVTデータ、CST構成、およびROMログに基づいて、いくつかの潜在的な問題点を特定しました。 1. CST [Authenticate Data] Blocks アドレス/オフセットの不一致(主要な問題) あなたの画像から、 BootData.start = 0x20208000 と IVT.self = 0x20209000 によってマッピングが確立されます。ファイルオフセット 0x1000 メモリアドレス 0x20209000 に対応し、 0x20208000 には対応しません。 CST Blocks の構文は "file" です。現在の回線: Blocks = 0x20208000 0x1000 0x126c0 "my_firmware.bin" ← address/offset misaligned by 0x1000 CSTはファイルオフセット 0x1000 のデータに署名し、デバイス上のHABは 0x20208000 (=ファイルオフセット0)のメモリを検証します。2つは4 0x1000でオフセットされているため、署名が一致することは決してありません。これはまさに「オープンモードでは起動し、クローズモードでは失敗する」という現象を説明しています。オープンモードでは、HAB検証の失敗はログに記録されるだけで(致命的ではない)、クローズモードでは実行がブロックされます。 修理 : (sign from IVT): Blocks = 0x20209000 0x1000 0x126c0 "my_firmware_prepared.bin" また、CST を実行する前に、IVT.csf フィールド (オフセット 0x1018) に最終的な CSF アドレス 0x2021b6c0 (= 0x20208000 + 0x136c0) が事前に設定されていることを確認し、その後署名し、追加します。署名後は署名済みバイトを変更しないでください(IVT/BootData/DCDはすべて署名範囲内です)。そうすると検証も壊れます。 Q1: HABイベントコードはどこにありますか?合否判定の方法は? 0x2020523c から読まれているのはROMブートログであって、詳細なHABイベントログではありません。RT10xxでは、各エントリは (event_id<<16) | parameter として単一の32ビットワードにパックされ、パラメータは下位バイトに格納されます。 詳細な失敗理由については、HAB ROM API: report_status(&config,&state) および report_event(status,index,event,&bytes) を呼び出してください。decode per HAB4 API リファレンス・マニュアル、付録A Q2:blhostがHABログを読み取れません — 他に方法はありますか? blhost ブートROMに直接ではなく、フラッシュローダーと通信します。i.MXRT BootROMのシリアルダウンロード段階はSDPのみをサポートしています( sdphost をご利用ください)。オプション: 推奨: オープン 状態のアプリケーションからHAB APIを呼び出して、ステータスやイベント情報を読み込み印刷してください。 JTAG (ROMログ) を介して 0x2020523c から 256 バイトをダンプするか、MCUBootUtility v6.3 (sdphost がフラッシュローダーをロードし、次に blhost がメモリを読み込む) を使用して自動解析を行います。 重要事項: クローズドで認証が失敗すると、ROMはアプリケーションにジャンプせず、アプリ内 report_event は実行できません。したがって、標準フローはまず開閉状態で HAB_SUCCESS /イベント情報なしを確認し、その後SEC_CONFIG燃焼して閉じる必要があります。 Q3: 非標準IVTエントリー(オフセット0x1400)はHAB署名できますか? はい、これは原因ではありません。NORブートの場合、i.MXRT BootROMの最小オフセットは0x1400です(0x2000は推奨値です)。 よろしくお願いします、 ギャビン Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry またお手数をおかけして申し訳ありませんが、この問題は私にとって非常に重要なのです。 sdphostコマンドを使ってHAB認証エラーを明確に観察できました。次にJTAG経由で初期メモリ領域をダンプしてみたところ、ファームウェアの内容はメモリ上に全く存在しないことがわかった。 さらなるテストの結果、NXP-MCUBootUtilityに同梱されている公式デモプロジェクトでさえ、NON-XIPとして構成した場合、HAB署名に失敗することが判明した。XIPベースのイメージのみが正常に動作します。この結果にはとても驚きました。 私のeFuseレジスタの設定に間違いがあるのではないかと考えています。私のボードにはブートモードのDIPスイッチがないため、boot_cfgを0x1AにしてSRKヒューズを焼き切っただけです(添付のスクリーンショットを参照してください)。 QQ截图20260903101741.pngQQ截图20260903101741.png 私はこの分野の初心者なので、単純なミスをしているかもしれません。訂正やご提案があれば、ぜひお聞かせください。 ご返信をお待ちしております。よろしくお願いいたします。 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry こんにちは、 @eleven さん。 あなたの指摘(公式デモでさえ、非XIPでビルドするとHABが失敗し、XIPでビルドすると動作する)は、以下の記事の根本原因を示しているようです: https://www.cnblogs.com/henjay724/p/18111727 RT1050/1060「Non-XIP + HAB」ブートROM制限 これら2つの初期デバイスでは、BootROMはOCRAMの一部(特に 0x20280000–0x202BFFFF )を予約し、HAB認証には開放しません。他のRTデバイスにはこの制限はありません。イメージはOCRAM( 0x20208000 )に読み込まれるので、HABをオフにして起動しますが、HABオンの状態で検証に失敗し、ファームウェアはメモリにコピーされません。これは脳脊髄液/ブロックとは無関係であるため、以前の変更は効果がなかったのです。 非XIPが必要な場合は、予約済みのOCRAM領域を避け、代わりに外部SDRAMを使用してください。あるいは、上記のリンク先のガイドによると、画像は有害藻類ブルームの認識領域内に厳密に限定されなければならない。 ヒューズについて(スクリーンショット): ブートモードのディップ・スイッチがない場合、スタンドアロン起動には BT_FUSE_SEL = 1が必要です。そうでなければ起動構成は定義されていません。 また、 BOOT_CFG1=0x1A と Conf0=0x40 をRT1060 RMのヒューズマップと比較してビットごとに検証してください。ヒューズはOTP(一度書き込み可能)です。慎重に作業を進めてください。 よろしくお願いします、 ギャビン
View full article
FIT Exception Issue MPC5777c Hi Team,  I am trying produce FIT exception.         asm("li r0, 0x8000");         asm("mtspr TCR, r0");         asm("mtspr TCR, r0");   However, after executing this code, the board resets then enters the FIT exception handler. Could you please let me know if any additional configuration or changes are required to correctly trigger and handle the FIT exception? Thank you for your support. Best regards, Pavan Re: FIT Exception Issue MPC5777c Hi, IVPR points to a valid exception vector table yes. IVOR10 is configured for the FIT handler. No. configured to IVOR11. Interrupts are enabled (MSR[EE] = 1). yes. BSP_MSR_Normal: Unsigned_32 :=16#02009000#; The time base/FIT source is running. yes. You can find the details. which i configured help me out anything else i need to do Regards, Pavan Re: FIT Exception Issue MPC5777c Hi MTSPR(IVOR10, entDECR'Address); -- Decrementer (handled by Ada runtime) -- Now use e200/MPC55xx mapping MTSPR(IVOR11, ent0B'Address); -- Fixed Interval Timer.. This will work by making IVOR10 as FIT. Regards, Pavan Re: FIT Exception Issue MPC5777c Hello, The FIT exception should work once the exception infrastructure is properly configured. Please verify: IVPR points to a valid exception vector table. IVOR10 is configured for the FIT handler. Interrupts are enabled (MSR[EE] = 1). The time base/FIT source is running. Since the board resets before reaching the FIT handler, please also check the RGM reset status registers to identify the reset source. Reference: FIT exception generation is described in AN2865 Section 3. Best regards, Peter Re: FIT Exception Issue MPC5777c Hello,  I’d first check that the FIT enable bit in the TCR is set correctly and that the corresponding exception vector is properly initialized. Also make sure the exception/MSR configuration allows the FIT interrupt to be taken. One thing that stands out is writing the same value to TCR twice: asm("li r0, 0x8000"); asm("mtspr TCR, r0"); asm("mtspr TCR, r0"); If your intention is simply to force the FIT event, you may not need the second write. The exact behavior also depends on the PowerPC core and the TCR bit definitions for that specific device.  Re: FIT Exception Issue MPC5777c Hello, Thank you for the update. Since you are using FIT, IVOR11 is the correct vector. Please additionally verify: TCR[FIE] = 1 (FIT interrupt enabled) FIT period selection (TCR[FP]) TSR[FIS] becomes set when the FIT interval expires The FIT handler clears TSR[FIS] IVOR11 entry in the exception table contains the correct branch to the FIT ISR RGM reset status registers to determine whether another exception or reset occurs before entering the FIT handler The value of TSR is particularly important. If TSR[FIS] is set but the ISR is not entered, the FIT is being generated but the exception dispatch path is not functioning correctly. Best regards, Peter Re: FIT Exception Issue MPC5777c Hello, MTSPR(SPR_HID0, 16#00004000#); -- Enable TB status MTSPR(SPR_TCR, 16#04800000#); -- Enable DEC +FIT MTSPR(SPR_TSR, 16#04000000#); i think is this correct iam enabling properly
View full article
哪里可以获取LPC MCU的ROHS报告? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 亲爱的, 哪里可以获取以下部件号对应的LPC MCU的ROHS报告?谢谢。 LPC2114FBD64 LPC2136FBD64 P89V51RD2FBC lpc2000 Re: Where to get LPC mcu ROHS report? 像 DigiKey、Mouser Electronics 或 Farnell/Newark 这样的大型电子元器件代理商直接在其产品页面上提供合规性文件。如果您查找零件编号(例如 LPC2136FBD64/01 或 P89V51RD2FBC,557),请在库存清单旁边查找标有“RoHS 认证”、“材料声明”或“环境信息”的链接。
View full article
i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry poin Background: I am working on HAB signature for i.MXRT106x, using NXP‑MCUBootUtility developed by 痞子衡. When I load my firmware binary into this tool, it reports: **Cannot find valid interrupt vector table address from bootable file header**. After inspecting the binary with hex editor: - The IVT entry point is `0x20209401`, while the image load base address is `0x20208000`, corresponding to file offset `0x1400`. - This code segment is identical to the boot‑related bootdata flow up to offset `0x2000`. - Normally the IVT entry should point to the reset vector address (reference example points to offset `0x2005`). But in my firmware, IVT entry points to offset `0x1400`. I suspect this is the root cause of the tool parsing failure. Further research on CST workflow: I understand the high‑level logic of CST signing: find a free block within the firmware, set the IVT CSF pointer to this location, use standard CSF template, and modify the `[Authenticate Data]` block section to configure the start address and size range for signature verification. My firmware is a complete bootable image containing FCB, IVT, DCD and BootData, and it boots normally on hardware without HAB closure. I configured my CSF block as: Blocks=0x20208000 0x1000 0x126c0 "my_firmware.bin" Also updated certificate paths accordingly. I ran CST v3.00.01 command: cst.exe -i .\input_resign.csf -o sig.bin The CST execution finished without errors and generated `sig.bin`. Comparing the output against original binary, there are exactly 2 changes: 1. CSF pointer field inside IVT at offset `0x1018` is updated. 2. CSF signature data is appended at offset `0x136c0`. When I flash this signed image to hardware: 1. With HAB not closed (SEC_CONFIG not closed), firmware runs perfectly. 2. After burning SRK fuse bits and closing HAB, the firmware fails to boot. I dumped HAB log from memory address `0x2020523c` with length 256 bytes via JTAG, and the log content is shown below: ----------------------------------------------------------------------------------------- | Log Entry | Description ----------------------------------------------------------------------------------------- 0x00010002: BOOTMODE_INTERNAL 0x000200cc: SEC_CONFIG_CLOSED 0x00030001: DIR_BT_DIS_VALUE1 0x00040000: BT_FUSE_SEL_VALUE0 0x00050000: PRIM_IMAGE_SELECT 0x00060008: PRIM_BOOTDEVICE_FLEXSPI_NOR 0x00070000: DEVICE_INIT_CALL 0x000700f0: DEVICE_INIT_PASS 0x00090000: AUTHENTICATION_STATUS **My questions:** 1. Where is the actual HAB event code? According to references, HAB authentication pass/fail should generate explicit event codes. But my log stops at `AUTHENTICATION_STATUS` with no follow‑up event entry. How can I determine whether HAB authentication succeeded or failed? 2. I tried `blhost` tool, but I cannot find any HAB log read command working on i.MXRT1061. Is there another method to read full HAB status? 3. Is my signing workflow valid? My image uses non‑standard IVT entry point (points to offset `0x1400` instead of reset vector offset `0x2005`). Can such an image be properly HAB‑signed with CST? Additional IVT header bytes at offset `0x1000`: D1 00 20 40 01 94 20 20 00 00 00 00 80 90 20 20 20 90 20 20 00 90 20 20 00 00 00 00 00 00 00 00 00 80 20 20 80 99 01 00 00 00 00 00 00 80 20 20 80 99 01 00 52 44 49 52 00 00 00 00 E4 B8 21 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 00 08 41 CC 00 04 04 CST tool version: 3.00.01 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry Hi @eleven , Thank you for the update. First, I think we should confirm whether the first byte of boot.bin is an FCB or an IVT. If it is an FCB, there may still be an alignment issue. In addition, this guide should be helpful during the process of reading and interpreting HAB fault codes: https://community.nxp.com/t5/i-MX-Security/HAB-event-in-a-Closed-i-MX-chip/ta-p/1120239 If you are still unable to pinpoint the root cause of the problem, using MCUBootUtility to generate an HAB signature directly and then running a binary diff might be another way to cross-verify the results. Best regards, Gavin Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry Hi Gavin, Thank you very much for your detailed reply. I think I did not describe my test setup completely in my original post. I have already tried adjusting the Blocks configuration as you suggested. I tested both: Blocks = 0x20208000 0x1000 0x126c0 "my_firmware.bin" and splitting into multiple block entries to authenticate starting from IVT through to the end of firmware: Blocks = 0x20209000 0x0 0x40 "boot.bin",\ 0x20209080 0x80 0xf80 "boot.bin",\ 0x2020a000 0x1000 0x11c00 "boot.bin" My intention was to authenticate starting from the IVT and cover all the way to the end of application code. However, the boot behaviour remained unchanged after these changes. I am using MCUBootUtility v6.5.1. Both its built‑in boot log analysis and manual JTAG memory dump give exactly the same log result. Also, I understand that the minimum boot offset for NOR is 0x1400. What I wanted to clarify is: my IVT entry points to boot‑related code, not the typical reset vector located at offset 0x2005 as seen in reference examples. Thanks again for your guidance. I will run further tests using sdphost to gather more debug information. Hopefully I can get more clues from that. Best regards, eleven Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry Hi @eleven , Based on your IVT data, CST configuration, and ROM log, I've identified some potential issues. 1. CST [Authenticate Data] Blocks address/offset mismatch (primary issue) From your image, BootData.start = 0x20208000 and IVT.self = 0x20209000 establish the mapping: file offset 0x1000 corresponds to memory address 0x20209000 , not 0x20208000 . The CST Blocks syntax is "file" . Your current line: Blocks = 0x20208000 0x1000 0x126c0 "my_firmware.bin" ← address/offset misaligned by 0x1000 makes CST sign the data at file offset 0x1000 , while HAB on the device verifies memory at 0x20208000 (= file offset 0). The two are offset by 0x1000, so the signature can never match. This exactly explains "boots when Open, fails when Closed": in Open mode a HAB verification failure is only logged (non-fatal), whereas in Closed mode it blocks execution. Fix : (sign from IVT): Blocks = 0x20209000 0x1000 0x126c0 "my_firmware_prepared.bin" Also ensure the IVT.csf field (offset 0x1018) is pre-filled with the final CSF address 0x2021b6c0 (= 0x20208000 + 0x136c0) before running CST, then sign, then append. Do not modify any signed byte after signing (IVT/BootData/DCD are all inside the signed range); doing so will also break verification. Q1: Where is the HAB event code? How to tell pass/fail? What you read from 0x2020523c is the ROM boot log, not the detailed HAB event log. On RT10xx each entry is packed into a single 32-bit word as (event_id<<16) | parameter , with the parameter in the low byte. For the detailed failure reason, call the HAB ROM API: report_status(&config,&state) and report_event(status,index,event,&bytes) . decode per HAB4 API Reference Manual, Appendix A Q2: blhost can't read the HAB log — any other method? blhost talks to the Flashloader, not directly to the BootROM. The i.MXRT BootROM serial-download stage supports only SDP (use sdphost ). Options: Recommended: call the HAB API from your application in the Open state to read/print status and events. Dump 256 bytes from 0x2020523c via JTAG (ROM log); or use MCUBootUtility v6.3 (sdphost loads the flashloader, then blhost read-memory) for automatic parsing. Important: When Closed and verification fails, the ROM never jumps to your application, so an in-app report_event cannot run. The standard flow must therefore be — confirm HAB_SUCCESS /no events in the Open state first, then burn SEC_CONFIG to close. Q3: Can a non-standard IVT entry (offset 0x1400) be HAB-signed? Yes — this is not the cause. For NOR boot the i.MXRT BootROM's minimum offset is 0x1400 (0x2000 is only a recommended value). Best regards, Gavin Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry Sorry for bothering you again, but this issue is critical for me. I could clearly observe HAB authentication errors using the sdphost command. Then I dumped the early memory region via JTAG, and found none of the firmware content was present in memory. Further testing showed that even the official demo projects shipped with NXP‑MCUBootUtility fail HAB signature when configured as NON‑XIP. Only XIP‑based images work successfully. This result surprised me a lot. I suspect there might be a mistake in my eFuse register configuration. My board does not have boot‑mode DIP switches, so I only programmed boot_cfg to 0x1A and burned the SRK fuses (please refer to the attached screenshot). QQ截图20260903101741.pngQQ截图20260903101741.png I am a beginner in this area and may have made some simple mistakes. I would appreciate any corrections or suggestions. Looking forward to your reply, thank you very much. Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry Hi @eleven , Your observation — even the official demo fails HAB when built as Non-XIP, while XIP works — seems to points to this root cause: https://www.cnblogs.com/henjay724/p/18111727 RT1050/1060 "Non-XIP + HAB" BootROM limitation On these two earliest devices, the BootROM reserves part of the OCRAM (notably 0x20280000–0x202BFFFF ) and does not open it to HAB authentication; other RT devices don't have this limit. Your image loads into OCRAM ( 0x20208000 ), so it boots with HAB off but fails verification with HAB on, and the firmware is never copied into memory. This is independent of your CSF/Blocks, which is why earlier changes had no effect. If Non-XIP is required: avoid the reserved OCRAM region and use external SDRAM instead. Alternatively, according to the guide in the link above, the image must be strictly confined to the HAB recognition area. On the fuses (screenshot): With no boot-mode DIP switches, standalone boot requires BT_FUSE_SEL = 1; otherwise the boot configuration is undefined. And please verify your BOOT_CFG1=0x1A and Conf0=0x40 bit-by-bit against the RT1060 RM Fusemap in your use case. Fuses are OTP (write-once) — proceed carefully. Best regards, Gavin
View full article
imx-mkimage iMX8/DXL/QM/QX/ULP KERNEL_DTB* 解除硬编码 我们已提交一个 PR,用于解除 iMX8 AHAB SoC(iMX8/DXL/QM/QX/ULP)的 KERNEL_DTB 和 KERNEL_DTB_ADDR 的硬连线。这一变化是由于 iMX9x 的实施而导致的。我在这里写这篇文章是因为在另一个公开的公关活动中有人评论说公关活动没有得到回应。 例如,当 Linux 镜像较大时,由于硬编码的 DTB 地址位置而留下的默认空间不足,因此需要进行更改。 这个改动微不足道。欢迎您添加此代码,无论是否注明出处,这样我们以后就可以避免使用补丁: 拉取请求 · nxp-imx/imx-mkimage Re: imx-mkimage iMX8/DXL/QM/QX/ULP KERNEL_DTB* unhardwiring 嗨@fa-adv 已为内部团队创建工单。 此致, 志明
View full article
FIT例外問題 MPC5777c チームの皆さん、こんにちは。 FIT例外を発生させようとしています。         asm ( " li r0, 0x8000 " );         asm ( " mtspr TCR, r0 " );         asm ( " mtspr TCR, r0 " );   しかし、このコードを実行すると、ボードがリセットされ、FIT例外ハンドラに入ります。FIT例外を正しくトリガーし処理するために、追加の設定や変更が必要かどうか教えていただけますか? 再開まで今しばらくお待ちください。 よろしくお願いします、 パヴァン Re: FIT Exception Issue MPC5777c こんにちは、 IVPRは有効な例外ベクタテーブルを指します はい。 IVOR10はFITハンドラー用に構成されています。 いいえ。IVOR11に設定されています。 割り込みが有効になっています (MSR[EE] = 1)。 はい。BSP_MSR_Normal: Unsigned_32 :=16#02009000#; タイムベース/FITソースが稼働中です。 はい。 詳細は私が設定したので、他に何か必要なことがあれば教えてください。 よろしくお願いいたします。 パヴァン Re: FIT Exception Issue MPC5777c こんにちは MTSPR(IVOR10, entDECR'Address); -- デクリメンタ(Adaランタイムによって処理されます) -- e200/MPC55xx マッピングを使用する MTSPR(IVOR11, ent0B'Address); -- 固定間隔タイマー。これは、IVOR10をFITにすることで機能します。 よろしくお願いいたします。 パヴァン Re: FIT Exception Issue MPC5777c こんにちは、 例外処理インフラストラクチャが適切に構成されれば、FIT例外は機能するはずです。 ご確認ください: IVPRは有効な例外ベクタテーブルを指します。 IVOR10はFITハンドラー用に構成されています。 割り込みが有効になっています (MSR[EE] = 1)。 タイムベース/FITソースが稼働中です。 ボードはFITハンドラに到達する前にリセットされるため、リセットの原因を特定するためにRGMリセットステータスレジスタも確認してください。 参照:FIT例外の生成については、AN2865のセクション3で説明されています。 よろしくお願いします、 ピーター Re: FIT Exception Issue MPC5777c こんにちは、 まず、TCRのFITイネーブルビットが正しく設定されていること、および対応する例外ベクタが適切に初期化されていることを確認します。また、例外/MSRの設定でFIT割り込みが受け入れられることを確認してください。 特に気になるのは、TCRに同じ値を2回書き込んでいる点です。 asm("li r0, 0x8000"); asm("mtspr TCR, r0"); asm("mtspr TCR, r0"); もし単にFITイベントを強制するだけなら、2回目の書き込みは不要かもしれません。正確な動作は、PowerPCコアの種類と、その特定のデバイスにおけるTCRビット定義によっても異なります。 Re: FIT Exception Issue MPC5777c こんにちは、 最新情報のご提供ありがとうございます。FITを使用しているため、IVOR11が正しいベクトルです。さらに以下の点もご確認ください。 TCR[FIE] = 1 (FIT割り込み有効) FIT期間選択(TCR[FP]) TSR[FIS]はFIT間隔が終了すると設定されます FITハンドラーがTSR[FIS]をクリアします。 例外テーブルのIVOR11エントリには、FIT ISRへの正しい分岐が含まれています。 RGMリセットステータスレジスタを使用して、FITハンドラに入る前に別の例外またはリセットが発生したかどうかを判断します。 TSRの価値は特に重要です。TSR[FIS]が設定されているがISRが入力されていない場合、FITは生成されているものの例外ディスパッチパスが正しく機能していません。 よろしくお願いいたします。 ピーター Re: FIT Exception Issue MPC5777c こんにちは、 MTSPR(SPR_HID0, 16#00004000#); -- TBステータスを有効にする MTSPR(SPR_TCR, 16#04800000#); -- DEC +FIT を有効にする MTSPR(SPR_TSR, 16#04000000#); これは正しいと思います。私は正しく有効化しています。
View full article
imx-mkimage iMX8/DXL/QM/QX/ULP KERNEL_DTB* のハードウェア接続解除 iMX8 AHAB SoC(iMX8/DXL/QM/QX/ULP)向けに、KERNEL_DTBとKERNEL_DTB_ADDRのハードウェア接続を解除するプルリクエストを追加しました。この変更は、iMX9xの導入に伴うものです。別の公開プルリクエストへのコメントで、プルリクエストが処理されていないという指摘があったため、ここに書き込みます。 この変更は、例えばLinuxイメージが有線DTBアドレスのデフォルト領域が大きい場合に必要です。 変更点は些細なものだ。今後パッチの使用を避けるために、帰属の有無にかかわらず追加しても構いません。 プルリクエスト ·nxp-imx/imx-mkimage Re: imx-mkimage iMX8/DXL/QM/QX/ULP KERNEL_DTB* unhardwiring こんにちは@fa-adv 社内チーム向けにチケットを作成しました。 よろしくお願いします、 志明
View full article
FIT 异常问题 MPC5777c 大家好, 我正在尝试生成 FIT 异常。         asm ( " li r0, 0x8000 " );         asm ( " mtspr TCR,r0 " );         asm ( " mtspr TCR,r0 " );   但是,执行此代码后,板复位,然后进入 FIT 异常处理程序。请问是否需要进行任何额外的配置或更改才能正确触发和处理 FIT 异常? 感谢您的支持。 此致, 帕万 Re: FIT Exception Issue MPC5777c 你好, IVPR 指向一个有效的异常向量表 是的。 IVOR10 已配置为 FIT 处理程序。 编号为 IVOR11。 中断已启用(MSR[EE] = 1)。 是的。BSP_MSR_Normal: Unsigned_32 :=16#02009000#; 时基/FIT源正在运行。 是的。 您可以找到详细信息。我已经配置好了,请帮我看看还有什么需要做的。 问候, 帕万 Re: FIT Exception Issue MPC5777c 你好 MTSPR(IVOR10, entDECR'Address); -- 递减器(由 Ada 运行时处理) 现在使用 e200/MPC55xx 映射 MTSPR(IVOR11, ent0B'Address); -- 固定间隔定时器..这将通过将 IVOR10 设置为 FIT 来实现。 问候, 帕万 Re: FIT Exception Issue MPC5777c 你好, 只要异常处理机制配置正确,FIT 异常处理功能应该就能正常工作。 请核实: IVPR 指向一个有效的异常向量表。 IVOR10 已配置为 FIT 处理程序。 中断已启用(MSR[EE] = 1)。 时基/FIT源正在运行。 由于电路板在到达 FIT 处理程序之前复位,请同时检查 RGM 复位状态寄存器以确定复位源。 参考:FIT 异常生成在 AN2865 第 3 节中进行了描述。 此致, 彼得 Re: FIT Exception Issue MPC5777c 你好, 我首先会检查 TCR 中的 FIT 使能位是否已正确设置,以及相应的异常向量是否已正确初始化。还要确保异常/MSR 配置允许发生 FIT 中断。 其中最引人注目的一点是,同一个值被写入了两次 TCR: asm("li r0, 0x8000"); asm("mtspr TCR, r0"); asm("mtspr TCR, r0"); 如果你的目的仅仅是强制执行 FIT 事件,那么可能不需要第二次写入。具体行为还取决于PowerPC内核以及该特定设备的TCR位定义。 Re: FIT Exception Issue MPC5777c 你好, 谢谢你的更新。既然你使用的是 FIT,那么 IVOR11 就是正确的向量。请另行核实: TCR[FIE] = 1(FIT中断已启用) FIT 周期选择 (TCR[FP]) 当 FIT 间隔到期时,TSR[FIS] 将被设置。 FIT 处理程序清除 TSR[FIS] 异常表中的 IVOR11 条目包含指向 FIT ISR 的正确分支。 RGM 重置状态寄存器用于确定在进入 FIT 处理程序之前是否发生其他异常或重置。 总股东回报率(TSR)的价值尤为重要。如果设置了 TSR[FIS] 但未进入 ISR,则会生成 FIT,但异常调度路径无法正常工作。 顺祝商祺! Peter Re: FIT Exception Issue MPC5777c 你好, MTSPR(SPR_HID0, 16#00004000#); -- 启用 TB 状态 MTSPR(SPR_TCR, 16#04800000#); -- 启用 DEC +FIT MTSPR(SPR_TSR, 16#04000000#); 我认为这样正确吗?我已正确启用。
View full article
imx-mkimage iMX8/DXL/QM/QX/ULP KERNEL_DTB* unhardwiring We've added a PR for unhardwiring the KERNEL_DTB and KERNEL_DTB_ADDR for iMX8 AHAB SoCs (iMX8/DXL/QM/QX/ULP).  The change follows the implementation of iMX9x. Writing here because a comment in another open PR commented about the PRs not being attended. The change is necessary for e.g., when a Linux image is bigger the default space left by the hardwired DTB address location. The change is trivial. You're welcome to add it with or without attribution, so we can avoid using patches in the future: Pull requests · nxp-imx/imx-mkimage Re: imx-mkimage iMX8/DXL/QM/QX/ULP KERNEL_DTB* unhardwiring Hi @fa-adv  Have created the ticket for internal team. Best Regards, Zhiming
View full article
i.MXRT106x HAB 启动失败,HAB 日志停留在 AUTHENTICATION_STATUS,非标准 IVT 入口点 背景:我正在使用痞子衡开发的 NXP‑MCUBootUtility 为 i.MXRT106x 开发 HAB 签名。当我将固件二进制文件加载到该工具中时,它报告:**无法从可引导文件头中找到有效的中断向量表地址**。 使用十六进制编辑器检查二进制文件后: - IVT 入口点为 `0x20209401`,而映像加载基地址为 `0x20208000`,对应于文件偏移量 `0x1400`。 - 此代码段与启动相关的启动数据流相同,直到偏移量 `0x2000`。 - 通常情况下,IVT 条目应指向复位向量地址(参考示例指向偏移量 `0x2005`)。但在我的固件中,IVT 入口点指向偏移量 `0x1400`。我怀疑这是工具解析失败的根本原因。 对CST工作流程的进一步研究: 我理解 CST 签名的高级逻辑:在固件中找到一个空闲块,将 IVT CSF 指针设置为该位置,使用标准 CSF 模板,并修改 `[Authenticate Data]` 块部分来配置签名验证的起始地址和大小范围。 我的固件是一个完整的可启动映像,包含 FCB、IVT、DCD 和 BootData,它可以在没有 HAB 关闭的情况下在硬件上正常启动。 我将 CSF 模块配置如下: Blocks=0x20208000 0x1000 0x126c0 "my_firmware.bin" 同时更新了证书路径。 我运行了 CST v3.00.01 命令: cst.exe -i .\input_resign.csf -o sig.bin CST 执行完成,未出现任何错误,并生成了 `sig.bin`。 将输出结果与原始二进制文件进行比较,发现恰好有 2 处变化: 1. 更新 IVT 中偏移量为 `0x1018` 处的 CSF 指针字段。 2. CSF 签名数据附加在偏移量 `0x136c0` 处。 当我将此签名镜像刷入硬件时: 1.在 HAB 未关闭(SEC_CONFIG 未关闭)的情况下,固件运行完美。 2. 烧录 SRK 熔丝位并关闭 HAB 后,固件无法启动。 我通过 JTAG 从内存地址 `0x2020523c` 转储了长度为 256 字节的 HAB 日志,日志内容如下所示: ----------------------------------------------------------------------------------------- | Log Entry | Description ----------------------------------------------------------------------------------------- 0x00010002: BOOTMODE_INTERNAL 0x000200cc: SEC_CONFIG_CLOSED 0x00030001: DIR_BT_DIS_VALUE1 0x00040000: BT_FUSE_SEL_VALUE0 0x00050000: PRIM_IMAGE_SELECT 0x00060008: PRIM_BOOTDEVICE_FLEXSPI_NOR 0x00070000: DEVICE_INIT_CALL 0x000700f0: DEVICE_INIT_PASS 0x00090000: AUTHENTICATION_STATUS 我的问题: 1.实际的HAB事件代码在哪里?根据相关资料,HAB认证通过/失败应生成明确的事件代码。但是我的日志只记录到 `AUTHENTICATION_STATUS` 就停止了,没有后续事件条目。如何判断HAB认证是成功还是失败? 2. 我尝试了 `blhost` 工具,但找不到任何适用于 i.MXRT1061 的 HAB 日志读取命令。还有其他方法可以读取完整的有害藻华状态吗? 3. 我的签名流程是否有效?我的镜像使用了非标准的 IVT 入口点(指向偏移量 `0x1400` 而不是重置向量偏移量 `0x2005`)。这样的图像能否用 CST 正确进行 HAB 签名? 偏移量为 `0x1000` 处的附加 IVT 标头字节: D1 00 20 40 01 94 20 20 00 00 00 00 80 90 20 20 20 90 20 20 00 90 20 20 00 00 00 00 00 00 00 00 00 80 20 20 80 99 01 00 00 00 00 00 00 80 20 20 80 99 01 00 52 44 49 52 00 00 00 00 E4 B8 21 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 00 08 41 CC 00 04 04 CST 工具版本:3.00.01 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry 嗨@eleven , 谢谢你的更新。首先,我认为我们应该确认 boot.bin 的第一个字节是 FCB 还是 IVT。如果是 FCB,可能仍然存在对准问题。 此外,本指南在读取和解释 HAB 故障代码的过程中应该会有所帮助: https://community.nxp.com/t5/i-MX-Security/HAB-event-in-a-Closed-i-MX-chip/ta-p/1120239 如果仍然无法找出问题的根本原因,使用 MCUBootUtility 直接生成 HAB 签名,然后运行二进制差异可能是交叉验证结果的另一种方法。 此致, 加文 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry 嗨,加文, 非常感谢您的详细回复。我觉得我在之前的帖子中没有完整地描述我的测试设置。 我已经按照您的建议调整了模块配置。我两种都测试过了: Blocks = 0x20208000 0x1000 0x126c0 "my_firmware.bin" 并拆分成多个块条目进行身份验证,从 IVT 开始一直到固件结束: Blocks = 0x20209000 0x0 0x40 "启动.bin",\ 0x20209080 0x80 0xf80 "boot.bin",\ 0x2020a000 0x1000 0x11c00 "boot.bin" 我的目的是从 IVT 开始进行身份验证,一直到应用程序代码的末尾。然而,这些更改之后,启动行为仍然没有改变。 我使用的是 MCUBootUtility v6.5.1。其内置的启动日志分析和手动 JTAG 内存转储都给出了完全相同的日志结果。 另外,我了解到 或非 的最小启动偏移量为 0x1400。我想澄清的是:我的 IVT 入口点指向与启动相关的代码,而不是像参考示例中那样指向位于偏移量 0x2005 处的典型复位向量。 再次感谢您的指导。我将使用 sdphost 进行更多测试,以收集更多调试信息。希望我能从中获得更多线索。 此致, 十一 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry 嗨@eleven , 根据您的 IVT 数据、CST 配置和 ROM 日志,我发现了一些潜在问题。 1. CST [Authenticate Data] Blocks 地址/偏移量不匹配(主要问题) 从你的图像中, BootData.start = 0x20208000 和 IVT.self = 0x20209000 建立了映射关系:文件偏移量 0x1000 对应于内存地址 0x20209000 ,而不是 0x20208000 。 CST Blocks 语法为 "file" 。您当前线路: Blocks = 0x20208000 0x1000 0x126c0 "my_firmware.bin" ← address/offset misaligned by 0x1000 使 CST 对文件偏移量 0x1000 处的数据进行签名,同时设备上的 HAB 验证 0x20208000 处的内存(= 文件偏移量 0)。两者偏移了 0x1000,因此签名永远不可能匹配。这就解释了“打开时启动,关闭时失败”:在打开模式下,HAB 验证失败只会记录下来(非致命的),而在关闭模式下,它会阻止执行。 使固定 : (sign from IVT): Blocks = 0x20209000 0x1000 0x126c0 "my_firmware_prepared.bin" 另外,在运行 CST 之前,请确保 IVT.csf 字段(偏移量 0x1018)已预先填充最终的 CSF 地址 0x2021b6c0 (= 0x20208000 + 0x136c0),然后签名,然后追加。签名后不要修改任何已签名的字节(IVT/BootData/DCD 都在已签名范围内);这样做也会破坏验证。 Q1: HAB事件代码在哪里?如何判断通过/不通过? 从 0x2020523c 读取的是 ROM 启动日志,而不是详细的 HAB 事件日志。在 RT10xx 上,每个条目都打包成一个 32 位字 (event_id<<16) | parameter ,参数位于低字节。 要了解详细的失败原因,请调用 HAB ROM API: report_status(&config,&state) 和 report_event(status,index,event,&bytes) 。根据 HAB4 API 参考手册附录 A 进行解码 Q2:blhost 无法读取 HAB 日志——还有其他方法吗? blhost 它与 Flashloader 通信,而不是直接与 BootROM 通信。i.MXRT BootROM 串行下载阶段仅支持 SDP(使用 sdphost )。选项: 建议:在应用程序处于打开状态时调用 HAB API,以读取/打印状态和事件。 通过 JTAG 从 0x2020523c 转储 256 字节(ROM 日志);或者使用 MCUBootUtility v6.3(sdphost 加载 flashloader,然后 blhost 读取内存)进行自动解析。 重要提示:当应用关闭且验证失败时,ROM 永远不会跳转到您的应用程序,因此应用内 report_event 无法运行。因此,标准流程必须是——首先确认 HAB_SUCCESS /Open 状态下没有事件,然后烧录 SEC_CONFIG 以关闭。 Q3:非标准 IVT 条目(偏移量 0x1400)能否进行 HAB 签名? 是的——这不是原因。对于 NOR 启动,i.MXRT BootROM 的最小偏移量为 0x1400(0x2000 只是一个推荐值)。 此致, 加文 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry 很抱歉再次打扰您,但这个问题对我来说至关重要。 使用 sdphost 命令可以清楚地观察到 HAB 身份验证错误。然后我通过 JTAG 转储了早期内存区域,发现内存中没有任何固件内容。 进一步测试表明,即使是 NXP-MCUBootUtility 附带的官方演示项目,在配置为 NON-XIP 时也无法通过 HAB 签名验证。只有基于 XIP 的镜像才能正常工作。这个结果让我非常惊讶。 我怀疑我的 eFuse 寄存器配置可能有误。我的板没有启动模式 DIP 开关,所以我只将 boot_cfg 编程为 0x1A 并烧毁了 SRK 熔丝(请参考附件截图)。 QQ截图20260903101741.pngQQ截图20260903101741.png 我在这个领域还是个新手,可能犯了一些简单的错误。如有任何更正或建议,敬请不吝赐教。 期待您的回复,非常感谢。 Re: i.MXRT106x HAB closed boot fail, HAB log stops at AUTHENTICATION_STATUS, non‑standard IVT entry 嗨@eleven , 您的观察——即使是官方演示程序,在以非 XIP 方式构建时 HAB 也会失败,而以 XIP 方式构建则可以正常工作——似乎指向了以下根本原因: https://www.cnblogs.com/henjay724/p/18111727 RT1050/1060“非XIP + HAB”BootROM限制在这两款最早的设备上,BootROM保留了部分OCRAM(特别是 0x20280000–0x202BFFFF ),并且没有将其开放给HAB认证;其他RT设备没有此限制。您的映像加载到 OCRAM ( 0x20208000 ) 中,因此在 HAB 关闭时可以启动,但在 HAB 打开时验证失败,并且固件永远不会复制到内存中。这与您的脑脊液/阻滞无关,这就是为什么之前的改变没有效果的原因。 如果需要非 XIP 模式:请避开保留的 OCRAM 区域,改用外部同步动态随机存取存储器(SDRAM)。或者,根据上面链接中的指南,图像必须严格限制在 HAB 识别区域内。 关于熔丝(截图): 如果没有启动模式 DIP 开关,独立组网 \\(SA\\) 启动需要BT_FUSE_SEL = 1 ;否则启动配置未定义。 请根据您的使用案例,逐位验证您的 BOOT_CFG1=0x1A 和 Conf0=0x40 与 RT1060 RM 熔丝图。熔丝是一次性写入 (OTP) 的——请谨慎操作。 此致, 加文
View full article
S32G2 电路板支持包 44 Ubuntu 版本失败 您好,我正在尝试按照 S32G2_LinuxBSP_44.0_User_Manual_updated_D250603.pdf 中的规定为 xx 构建 ubuntu 镜像。但是,我遇到了以下错误。检查配置文件后发现,即使我们现在使用的是 `scarthgap` 构建,系统中的某些部分似乎仍然需要 `kirkstone`?预期的 glib 版本似乎不匹配。我已经列出了运行的命令以及尝试运行版本时出现的错误输出。我是不是漏掉了什么配置? 命令: mkdir fsl-auto-yocto-bsp cd fsl-auto-yocto-bsp repo init -u https://github.com/nxp-auto-linux/auto_yocto_bsp/ -b release/bsp44.0 -m default.xml repo sync sudo apt update ./sources/meta-alb/scripts/host-prepare.sh source nxp-setup-alb.sh -m s32g274ardb2ubuntu # Set NXP_FIRMWARE_LOCAL_DIR in local/local.conf bitbake fsl-image-ubuntu-base 输出: ❯ bitbake fsl-image-ubuntu-base Loading cache: 100% |#######################################################################################################################################################################################################| Time: 0:00:00 Loaded 1143 entries from dependency cache. ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:44 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-ros.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:32 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-ros.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-base.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:29 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-base.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-extended/ubuntu/ubuntu-base_22.04.1.bb: nativeaptinstall.bbclass is incompatible to the current layer setETA: 0:00:17 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-extended/ubuntu/ubuntu-base_22.04.1.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! Parsing recipes: 100% |#####################################################################################################################################################################################################| Time: 0:00:55 Parsing of 3692 .bb files complete (766 cached, 2926 parsed). 5803 targets, 617 skipped, 2 masked, 0 errors. NOTE: Resolving any missing task queue dependencies WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-aarch64 not available (for item virtual/aarch64-fsl-linux-binutils) WARNING: versions of binutils-cross-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native-dev) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-crosssdk-x86_64-fslbsp-linux not available (for item virtual/x86_64-fslbsp-linux-binutils) WARNING: versions of binutils-crosssdk-x86_64-fslbsp-linux available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item virtual/libc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-native not available (for item binutils-native) WARNING: versions of binutils-native available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libintl) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libiconv) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-thread-db) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-localedata-i18n) WARNING: versions of glibc-locale available: 2.31 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-utils) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dbg) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dev) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-canadian-aarch64 not available (for item binutils-cross-canadian-aarch64) WARNING: versions of binutils-cross-canadian-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-ldconfig) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-utils) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-dev) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item ldconfig) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-locale) WARNING: versions of glibc-locale available: 2.31 2.39+git ERROR: Nothing PROVIDES 'virtual/x86_64-fslbsp-linux-gcc-crosssdk' (but /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-devtools/binutils2.34/binutils-cross-canadian_2.34.bb DEPENDS on or otherwise requires it). Close matches: virtual/x86_64-fslbsp-linux-g++ virtual/x86_64-fslbsp-linux-gcc virtual/x86_64-fslbsp-linux-go NOTE: Runtime target 'binutils-cross-canadian-aarch64' is unbuildable, removing... Missing or unbuildable dependency chain was: ['binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] NOTE: Runtime target 'packagegroup-cross-canadian-s32g274ardb2' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-cross-canadian-s32g274ardb2', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] ERROR: Required build target 'fsl-image-ubuntu-base' has no buildable providers. Missing or unbuildable dependency chain was: ['fsl-image-ubuntu-base', 'packagegroup-cross-canadian-s32g274ardb2', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] Summary: There were 46 WARNING messages. Summary: There were 10 ERROR messages, returning a non-zero exit code. Re: S32G2 BSP 44 Ubuntu Build Failure 你好, @sid_rotor 感谢你的帖子。 电路板支持包44 版本中没有提供为在 S32G 处理器上运行而构建 Ubuntu 镜像的功能,很遗憾 电路板支持包 用户手册没有正确更新,建议忽略用户手册中的相关章节。 BR 陈银 Re: S32G2 BSP 44 Ubuntu Build Failure 感谢您的快速回复。其他BSP版本也存在这种情况吗?我会尝试将我们的补丁移植到不同的电路板支持包,但我想确保它们支持构建 Ubuntu 镜像。 另外,我可以在哪里找到更新我的 电路板支持包 版本的变更日志/发布说明/移植指南? Re: S32G2 BSP 44 Ubuntu Build Failure 你好, @sid_rotor 感谢您的回复。 据我所知,44 之前的 电路板支持包 版本(43 或更早版本)可以正确支持 ubuntu 版本,您可以尝试使用这些版本进行工作。 BR 陈银
View full article
Where to get LPC mcu ROHS report? Dear, Where to get LPC mcu ROHS report for below Part number? Thanks. LPC2114FBD64 LPC2136FBD64 P89V51RD2FBC lpc2000 Re: Where to get LPC mcu ROHS report? Major electronic component distributors like DigiKey, Mouser Electronics, or Farnell/Newark host compliance documents directly on their product pages. If you look up the part number (e.g., LPC2136FBD64/01 or P89V51RD2FBC,557), look for links labeled "RoHS Cert", "Material Declaration", or "Environmental Information" next to the inventory listing.
View full article
S32G2 BSP 44 Ubuntu Build Failure Hello, I am trying to build an ubuntu image for xx as specified by S32G2_LinuxBSP_44.0_User_Manual_updated_D250603.pdf. However, I am running into the following errors. Inspecting the configuration files, it appears that some of the system still expects `kirkstone` even though we are now building with `scarthgap`? And the glib versions that are expected don't seem to match. I have listed the commands run and the error output when I attempt to run the build. Am I missing some configuration? Commands: mkdir fsl-auto-yocto-bsp cd fsl-auto-yocto-bsp repo init -u https://github.com/nxp-auto-linux/auto_yocto_bsp/ -b release/bsp44.0 -m default.xml repo sync sudo apt update ./sources/meta-alb/scripts/host-prepare.sh source nxp-setup-alb.sh -m s32g274ardb2ubuntu # Set NXP_FIRMWARE_LOCAL_DIR in local/local.conf bitbake fsl-image-ubuntu-base Output: ❯ bitbake fsl-image-ubuntu-base Loading cache: 100% |#######################################################################################################################################################################################################| Time: 0:00:00 Loaded 1143 entries from dependency cache. ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:44 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-ros.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:32 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-ros.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-base.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:29 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-base.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-extended/ubuntu/ubuntu-base_22.04.1.bb: nativeaptinstall.bbclass is incompatible to the current layer setETA: 0:00:17 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-extended/ubuntu/ubuntu-base_22.04.1.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! Parsing recipes: 100% |#####################################################################################################################################################################################################| Time: 0:00:55 Parsing of 3692 .bb files complete (766 cached, 2926 parsed). 5803 targets, 617 skipped, 2 masked, 0 errors. NOTE: Resolving any missing task queue dependencies WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-aarch64 not available (for item virtual/aarch64-fsl-linux-binutils) WARNING: versions of binutils-cross-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native-dev) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-crosssdk-x86_64-fslbsp-linux not available (for item virtual/x86_64-fslbsp-linux-binutils) WARNING: versions of binutils-crosssdk-x86_64-fslbsp-linux available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item virtual/libc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-native not available (for item binutils-native) WARNING: versions of binutils-native available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libintl) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libiconv) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-thread-db) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-localedata-i18n) WARNING: versions of glibc-locale available: 2.31 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-utils) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dbg) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dev) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-canadian-aarch64 not available (for item binutils-cross-canadian-aarch64) WARNING: versions of binutils-cross-canadian-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-ldconfig) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-utils) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-dev) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item ldconfig) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-locale) WARNING: versions of glibc-locale available: 2.31 2.39+git ERROR: Nothing PROVIDES 'virtual/x86_64-fslbsp-linux-gcc-crosssdk' (but /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-devtools/binutils2.34/binutils-cross-canadian_2.34.bb DEPENDS on or otherwise requires it). Close matches: virtual/x86_64-fslbsp-linux-g++ virtual/x86_64-fslbsp-linux-gcc virtual/x86_64-fslbsp-linux-go NOTE: Runtime target 'binutils-cross-canadian-aarch64' is unbuildable, removing... Missing or unbuildable dependency chain was: ['binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] NOTE: Runtime target 'packagegroup-cross-canadian-s32g274ardb2' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-cross-canadian-s32g274ardb2', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] ERROR: Required build target 'fsl-image-ubuntu-base' has no buildable providers. Missing or unbuildable dependency chain was: ['fsl-image-ubuntu-base', 'packagegroup-cross-canadian-s32g274ardb2', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] Summary: There were 46 WARNING messages. Summary: There were 10 ERROR messages, returning a non-zero exit code. Re: S32G2 BSP 44 Ubuntu Build Failure Hello, @sid_rotor  Thanks for your post. Building Ubuntu images for running on S32G processors is not available in BSP44 release, I feel sorry that the BSP UM is not updated correctly, I suggest ignoring the related chapter in the UM. BR Chenyin Re: S32G2 BSP 44 Ubuntu Build Failure Thanks for the quick response. Is this also the case for other BSP versions? I will try to port our patches to a different BSP, but would like to make sure they support building an Ubuntu image. Also, where might I be able to find a changelog/release notes/porting guide to update my BSP version? Re: S32G2 BSP 44 Ubuntu Build Failure Hello, @sid_rotor  Thanks for your reply. As far as I know, the BSP version before 44(43 or earlier) could support the ubuntu build correctly, you may try using these versions for your work. BR Chenyin
View full article
S32G2 BSP 44 Ubuntu ビルド失敗 こんにちは。S32G2_LinuxBSP_44.0_User_Manual_updated_D250603.pdf で指定されているように、xx 用の Ubuntu イメージを構築しようとしています。しかし、以下のエラーが発生しています。設定ファイルを調べたところ、現在`scarthgap`でビルドしているにもかかわらず、システムの一部がまだ`kirkstone`を想定しているようです。そして、期待されるglibのバージョンが一致しないようです。ビルドを実行しようとした際に実行したコマンドと、その際に出力されたエラーを以下に示します。何か設定が抜けているのでしょうか? コマンド: mkdir fsl-auto-yocto-bsp cd fsl-auto-yocto-bsp repo init -u https://github.com/nxp-auto-linux/auto_yocto_bsp/ -b release/bsp44.0 -m default.xml repo sync sudo apt update ./sources/meta-alb/scripts/host-prepare.sh source nxp-setup-alb.sh -m s32g274ardb2ubuntu # Set NXP_FIRMWARE_LOCAL_DIR in local/local.conf bitbake fsl-image-ubuntu-base 出力: ❯ bitbake fsl-image-ubuntu-base Loading cache: 100% |#######################################################################################################################################################################################################| Time: 0:00:00 Loaded 1143 entries from dependency cache. ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:44 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-ros.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:32 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-ros.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-base.bb: nativeaptinstall.bbclass is incompatible to the current layer set | ETA: 0:00:29 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-fsl/images/fsl-image-ubuntu-base.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-extended/ubuntu/ubuntu-base_22.04.1.bb: nativeaptinstall.bbclass is incompatible to the current layer setETA: 0:00:17 ERROR: /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-extended/ubuntu/ubuntu-base_22.04.1.bb: You must check APTGET_YOCTO_TRANSLATION and update the anonymous python() function! Parsing recipes: 100% |#####################################################################################################################################################################################################| Time: 0:00:55 Parsing of 3692 .bb files complete (766 cached, 2926 parsed). 5803 targets, 617 skipped, 2 masked, 0 errors. NOTE: Resolving any missing task queue dependencies WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-aarch64 not available (for item virtual/aarch64-fsl-linux-binutils) WARNING: versions of binutils-cross-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native-dev) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-crosssdk-x86_64-fslbsp-linux not available (for item virtual/x86_64-fslbsp-linux-binutils) WARNING: versions of binutils-crosssdk-x86_64-fslbsp-linux available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item virtual/libc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-native not available (for item binutils-native) WARNING: versions of binutils-native available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libintl) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libiconv) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-thread-db) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-localedata-i18n) WARNING: versions of glibc-locale available: 2.31 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-utils) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dbg) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dev) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-canadian-aarch64 not available (for item binutils-cross-canadian-aarch64) WARNING: versions of binutils-cross-canadian-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-ldconfig) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-utils) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-dev) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item ldconfig) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-locale) WARNING: versions of glibc-locale available: 2.31 2.39+git ERROR: Nothing PROVIDES 'virtual/x86_64-fslbsp-linux-gcc-crosssdk' (but /path/reproduce-for-forum/fsl-auto-yocto-bsp/sources/meta-alb/meta-alb-sdk/recipes-devtools/binutils2.34/binutils-cross-canadian_2.34.bb DEPENDS on or otherwise requires it). Close matches: virtual/x86_64-fslbsp-linux-g++ virtual/x86_64-fslbsp-linux-gcc virtual/x86_64-fslbsp-linux-go NOTE: Runtime target 'binutils-cross-canadian-aarch64' is unbuildable, removing... Missing or unbuildable dependency chain was: ['binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] NOTE: Runtime target 'packagegroup-cross-canadian-s32g274ardb2' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-cross-canadian-s32g274ardb2', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] ERROR: Required build target 'fsl-image-ubuntu-base' has no buildable providers. Missing or unbuildable dependency chain was: ['fsl-image-ubuntu-base', 'packagegroup-cross-canadian-s32g274ardb2', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] Summary: There were 46 WARNING messages. Summary: There were 10 ERROR messages, returning a non-zero exit code. Re: S32G2 BSP 44 Ubuntu Build Failure こんにちは、 @sid_rotor 投稿ありがとうございます。 S32Gプロセッサで動作するUbuntuイメージのビルディングはBSP44リリースには含まれていません。BSPのUMが正しく更新されていないのは残念です。UMの関連章は無視することをお勧めします。 BR チェイン Re: S32G2 BSP 44 Ubuntu Build Failure 迅速なご対応ありがとうございます。他のBSPバージョンでも同じようなことなのでしょうか?パッチを別のBSPに移植しようと思いますが、Ubuntuイメージの構築をサポートしているか確認したいです。 また、BSPのバージョンアップに必要な変更履歴、リリースノート、移植ガイドなどはどこで入手できますか? Re: S32G2 BSP 44 Ubuntu Build Failure こんにちは、 @sid_rotor ご返信ありがとうございます。 私の知る限り、44以前のBSPバージョン(43以前)はUbuntuビルドを正しくサポートできたはずです。これらのバージョンを仕事で試してみるのも良いでしょう。 BR チェイン
View full article
LPC MCU ROHSレポートはどこで入手できますか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 親愛なる、 以下の部品番号のLPC MCU ROHSレポートはどこで入手できますか?ありがとう。 LPC2114FBD64 LPC2136FBD64 P89V51RD2FBC lpc2000 Re: Where to get LPC mcu ROHS report? DigiKey、Mouser Electronics、Farnell/Newarkなどの主要な電子部品ディストリビューターは、製品ページに直接コンプライアンス関連書類を掲載しています。部品番号(例:LPC2136FBD64/01やP89V51RD2FBC,557)を調べると、「RoHS証明書」「材料申告」「環境情報」とラベル付けされたリンクが在庫リストの横にあります。
View full article
MCX N Knowledge Hub MCX N series of highly integrated Arm Cortex-M33 microcontrollers are designed for high performance and low power consumption. MCX N includes intelligent peripherals and on-chip accelerators providing multitasking capabilities and performance efficiency. Select MCX N families include NXP's eIQ® Neutron neural processing unit (NPU) for machine learning applications. The low-power cache enhances system performance, while the dual-bank flash and full ECC RAM support system safety and offer an extra layer of protection and advanced security. These secure MCUs include our EdgeLock® Secure Enclave, Core Profile offering a secure-by-design approach, secure boot with an immutable root-of-trust and hardware-accelerated cryptography. Documents: MCX N Series  MCX N Fact Sheet MCX N Series Hardware Design Guide MCX Nx4x TSI QSG UG10101 MCX Nx4x Power Management User Guide Migration Guide Froom LPC55xx to MCX Nx4x MCX N Series Products: MCX N94/N54/N53/N52/N24:  The MCX N94, N54, N53, N52 and N24 include up to two are based on dual high-performance Arm® Cortex®-M33 cores running up to 150 MHz, with 2 MB of Flash with optional full ECC RAM, a DSP co-processor and an integrated eIQ Neutron NPU. The NPU delivers up to 42x faster machine learning throughput compared to a CPU core alone enabling it to spend less time awake and reducing overall power consumption. The multicore design delivers improved system performance and reduces consumption by enabling smart, efficient distribution of workloads to the analog and digital peripherals.  Documents: Data Sheet MCX N947/946/547/546/536/527/526/247 MCXN_1P02G Errata MCXNx4x_0P02G Errata Reference Manual  Secure Reference Manual  AFCI 8HC Demo QSG Omdia Market Radar: AI Processors for the Edge 2024 MCX N94x MCUs: Bringing more intelligence to the Edge  MCX N23: The MCX N23x is based on a high-performance Arm® Cortex®-M33 running up to 150 MHz, with 1 MB of Flash, 352 kB ECC RAM and SmartDMA. The MCX N23x is optimized for cost, memory and system performance and offers a single core option with efficient distribution of workloads to the analog and digital peripherals. The EdgeLock Secure Enclave on the MCX N23x is a self-contained, on-die hardware security subsystem that has its own dedicated security core, internal ROM, secure RAM and it supports state-of-the-art side-channel attack-resilient symmetric and asymmetric crypto accelerators and hashing functions for security services. Documents: MCX N23x Data Sheet MCXN23x_0P21K Errata Reference Manual Security Reference Manual MCX N23 HLQFP100 Hardware Design Guide Boards: FRDM-MCXN947: FRDM-MCXN947 are compact and scalable development boards for rapid prototyping of MCX N94 and N54 MCUs. They offer industry standard headers for easy access to the MCU’s I/Os, integrated open-standard serial interfaces, external flash memory and an on-board MCU-Link debugger. Documents: FRDM-MCXN947 QSG MCUXpresso SDK Field-Oriented Control of 3-Phase PMSM and BLDC Motors -FRDM-MCXN947 FRDM-MCXN947 Getting Started FRDM-MCXN947 Board User Manual  FRDM-MCXN236FRDM-MCXN236 is a compact and scalable development board for rapid prototyping of MCX N23x MCU. It offers industry-standard headers for easy access to the MCU's I/Os, integrated open-standard serial interfaces, external flash memory and an onboard MCU-Link debugger Documents: FRDM-MCXN236 Development Board QSG Getting Started with FRDM-MCXN236 FRDM-MCXN236 Board User Manual  MCX-N9XX-EVK is a full featured evaluation kit for prototyping of MCX N94 / N54 MCUs. They offer industry standard headers for access to the MCU’s I/Os, integrated open-standard serial interfaces and an on-board MCU-Link debugger with power measurement capability. Documents: Getting Started with MCX-N9XX-EVK MCX-N9XX-EVK Board User Manual MCX N to FRDM Board Mapping: Supported MCU(s) Recommended Board Best fit for  Key Differentiators MCX N94 / N54 / N53 / N52 / N24 FRDM-MCXN947 Rapid prototyping across the MCX N portfolio Arduino-compatible headers, MCU-Link debugger, Ethernet PHY, CAN-FD, camera and LCD expansion support. MCX N94x / N54x MCX-N9XX-EVK Full-featured evaluation, performance benchmarking, advanced prototyping Energy monitoring, external memory support, Ethernet, CAN, PMIC, M.2 expansion, MCU-Link debugger. MCXN236 FRDM-MCXN236 Ultra-low-power IoT devices, battery-powered sensors, edge nodes Arm Cortex-M33 MCU, low-power architecture, integrated analog peripherals, optimized for connected sensing applications.   Applications Notes: Software, hardware and Peripherals AN15071 Implementation of Optical module CMIS protocol over I3C on the MCX N94: This application note introduces how to implement the CMIS protocol demo on an MCX N947 microcontroller using the I3C interface. AN15072 Implementation of an I3C Secondary Bootloader on MCX N947: The I3C interface is widely used in many scenarios, such as data center, PCs, and optical modules. As a result, I3C-based secondary bootloader for firmware updates have become a common requirement. AN14407 DICE Attestation for MCX N Series Devices: This application note explains and provides a demo on how to implement DICE on MCX N series devices. In this implementation, DICE uses the UDS of the device, its hardware state, firmware, and RTF to create a unique identity that gets registered on an offline database system. This offline database system is later used to verify the genuineness of the device. AN14320 Ease ISA/IEC 62443-4-2 Compliance with MCX N Series: This document is addressed to OEMs interested in understanding how the MCX N can be used to facilitate the implementation of ISA/IEC 62443-4-2 requirements. AN14166 MCX N Over-The-Air (OTA) Update by Using SB3 file: This document describes a method to secure OTA via SB3 files. For demonstration purposes, this documentation uses the EVK and onboard Ethernet. AN15087 Implementing Three I2C Target Interfaces Using SmartDMA on the MNC N947: This demo implements three virtual I2C target ports on MCX N947 using SmartDMA-assisted GPIO-style signaling, without dedicating three hardware LPI2C target peripherals AN14900 Using eDMA and Ping-Pong Buffer ti deserialize Multi-Channel ADC Result FIFO:  This application note describes how to use eDMA to tackle the Analog-to-Digital Converter (ADC) result First-In First-Out (FIFO) and deserialize each channel data in FIFO to respective buffer for each channel. It is useful for high-speed and multi-channel ADC result process by reducing CPU loading and improving data processing speed. AN14807 Accelerate FFT Computation with PowerQuad: In high-performance signal processing applications, the Fast Fourier Transform (FFT) plays a critical role. To enhance efficiency, the LPC55 Series and MCX N Series microcontrollers integrate a hardware accelerator called PowerQuad. This application note presents an approach to accelerate FFT computation using PowerQuad while addressing its limitation of a maximum FFT length of 512 points AN14175 Using FlexIO to emulate Quad SPI controller: Quad SPI serves as a common interface for flash memory, Wi-Fi modules, and LCD displays. However, some microcontrollers do not support the Quad SPI interface. In such cases, FlexIO offers a versatile alternative. AN14712 Advanced PowerQuad Operation Guide: This application note provides some information, code snippets, and tips to help users accelerate their calculations with MAU. The MCX N Series microcontrollers feature a powerful and efficient coprocessor called PowerQuad. It operates in parallel with the CPUs to offload intensive mathematical computations and enhance overall performance. AN14650 SmartDMA Cookbook: This application note primarily introduces the internal architecture, main functions, and features of EZH or SmartDMA, and finally lists the usage and meanings of the main instructions AN14520 General MCU PWM DAC Application: This application note introduces how to set the low-cost Digital-to-Analog Converter (DAC) using the PWM output. The main application is household electrical and industry appliances, which need a low cost and accurate DAC without a high-bandwidth requirement.  AN14567 How to implement USB microphone on MCX Series MCUs: This documentation describes how to implement a USB microphone on MCX Series MCUs. The data source could be an external digital microphone or generated data. A USB Audio Class 1.0 (UAC 1.0) and USB Audio Class 2.0 (UAC 2.0) microphone is used in this document. AN14553 Building a GPS Speedometer using GUI Guider and FREM-MCXN947: This application note provides examples to build a GPS-based speedometer with FRDM-MCXN947, LVGL, GUI Guider tool, and a GPS module. The document describes how to deploy LVGL on the MCX Nx4x platform with GUI Guider and SDK. AN14470 How to Use FlexIO State Mode to Generate Center-Aligned PWM: This application note describes how to use the FlexIO state mode to generate a center-aligned PWM waveform on the MCXN series MCUs. AN14259 SDK Example to Write CMPA and CFPA with monotonic Counter dor MCXN947: This document provides an example of changing the Customer Field Programmable Area (CFPA) bit field using the ROM APIs.  AN14532 Migration from Kinetis K Series to MCXNx4x Series: This application note is about migrating Kinetis K series to MCXN94x/N54x series and lists the differences between both the series. AN14543 Connect Barcide Scanner with MCX N Series USB Host port: This application note describes how to build a USB host port connected with a USB barcode scanner using the FRDM-MCXN947 board for demonstration. NXP’s MCX N series devices feature a high-speed (HS) USB port capable of reaching transmission speeds up to 480 Mbit/s and compatible with Full-speed mode. AN14509 How to Use SmartMDA to Implement MDIO Slave Interface on MCX MCU:  This application note describes the use of SmartDMA to implement the MDIO slave interface on MCX series MCUs. AN14479 OTA Recovery Boot Image Stored in 1-bit SPI Flash: This application note describes the step-by-step process to load a recovery image to the external 1-bit SPI flash memory using a secure firmware update. In addition, the steps demonstrate how to trigger a recovery boot from the application using the ROM APIs. AN14300 MCX Nx4x Unleashing the Power of eDMA Controller: his application note provides a working knowledge by covering the following topics: introduction and overview of eDMA controllers, features of the MCX Nx4x eDMA module, interaction between the eDMA and DMA multiplexer (DMAMUX), and configuration advice for applications. AN14423 On-Device Training for Fan Anomaly Detection Using FRDM-MCXN947: This document describes how to prepare the software environment and set up the hardware for fan anomaly detection using FRDM-MCXN947. This demo uses an accelerator sensor on the fan to monitor in real-time whether the fan is operating normally. AN14145 Flash Memory Swap feature on MCX N Series: This application note describes how to use the flash remap feature of MCX series. AN14305 Permanent Magnet Synchronous Motor Field Oriented Control Using MCX Microcontrollers: This application note describes the implementation of Field Oriented Control (FOC) application for a 3-phase Permanent Magnet Synchronous Motor (PMSM) on NXP MCX MCUs, including the N and A series. AN14184 Using SmartDMA for Keyscan on MCX N Series MCU: This application note mainly introduces the Keyscan solution for MCX N series MCU. It includes the introduction of the Keyscan solution, its features and API routines, and a demo. AN14191 How to use SmartDMA to implement Camera Interface in MCXN MCU: This application note describes the parallel interface for the camera solution in MCXN947 and MCXN236. It includes the introduction of camera interface, features, API routines, and demo.  AN14172 Using SmartDMA for Graphic on MCX N Series MCU: This application note introduces the application of SmartDMA on the graphic. AN14196 Flex Pulse Width Modulator (FlexPWM) usage on MCXN MCU: This document introduces several operation modes, including the corresponding implementation, to provide reference for different applications.  AN14253 USB to CAN-FD Adapter based on MCXN Microcontroller: This application note provides two demo examples to build a USB to CAN-FD adapter where the USB retransmits data to the CAN-bus and vice versa. It uses MCX_N9XX_EVK and MCX_N9XX_FDRM boards for the demo.  AN14284 Timing Parameter tuning for FlexIO Emulated Interface: This application note describes how to use additional timers to tune the setup time in SPI master. AN14254 Use QDC/ENC/Quad Timer Peripherals to Calculare the Angle and Speed of the Quadrature Encoder: This application note provides an angle measurement method and an enhanced M/T speed measurement method that can take into account both high and low speeds. AN14167 Internal Reference Clock (IRC) Trim Feature on MCX N Series: This application describe how to use auto-trim feature on MCX N series. AN14241 How to integrate Customer ML Model to NPU on MCX N94x: This document describes how to integrate the customer ML model to NPU on the FRDMMCXN947 board. AN14195 USB Remote Wake-up on MCXN947: MCXN947 contains two USB 2.0 interfaces. USB0 is a full-speed interface. It comprises an On The-Go (OTG) dual-role subsystem with OTG protocol support. AN14185 DCDC Usage on MCXNx4x/Nx3x: This application note is designed to provide a better understanding of the on-chip DCDC module. It offers a comprehensive guide on how to control both basic and advanced parameters, as well as how to configure the DCDC module to work efficiently with other peripherals. AN14178 MCXNx4x Flash Command Example: This document explains how to use the flash command controller to perform flash read and write operations, which can be more efficient than using calls to the ROM API. AN14177 Headset with Touch Function on MCX Nx4x: This application note describes how to use the MCX-N5XX-EVK to implement USB audio with touch control. AN14151 MCX Nx4x MICFIL interface: This application note is based on examples how to leverage the MICFIL coupled with eDMA, interrupts to send the audio stream to the SRAM for postprocessing. AN14146 CANopen Bootloader in MCX N Series: This application note discusses how to implement CANopen bootloader AN14132 Face Detection demo with elQ Neutron NPU Accelerated on MCX N947: This application note shows how to implement the face detection example on the FRDM-MCXN947 board. AN14150 MCX Nx4x Inter-Core Communication Application Note: This application note introduces how dual core devices can communicate using the Mailbox interface. Power Management AN15066 Direct Current arc Fault Circuit Interrupters Solution with Time Series Studio: This application note presents a DC AFCI reference solution based on the MCX N547 MCU. It describes the system architecture, hardware design considerations, and software and algorithm concepts to assist system designers in implementing reliable and standards-compliant arc fault detection solutions AN14180 Estimating Device Lifetime for MCX Nx4x: This document describes the estimated product Power-on Hours (PoH) for the MCX N94x and MCX N54x devices, based on the criteria used in the qualification process. AN14190 OPAMP usage on MCXM947: This application note describes the functions of OPAMP module and how to use OPAMP features on MCXN947. AN14139 Design Considerations for Optimizing Performance with MCX N Series: This application note explains the features of MCX N-series devices that can affect system performance Security AN14148 Secure Boot on MCX N Series: This application note describes the steps for secure boot using the Secure Provisioning Tool (SEC) AN14162 MCX N Debug Authentication: This application note describes the secure debug feature on the MCX N series devices. The document walks through the steps used to configure a device to enable secure debug using the Secure Provisioning Tool. The document also shows the debug authentication steps to unlock the debug port. AN14096 Encryption and Decryption Enablement Using NPX Module on SEC tool:   AN14361 Generating Digital Signature Using ELS ECSIGN command with RTF Enabled: This application note focuses mostly on the ECSIGN command and creates a demo to use it with Run Time Fingerprint (RTF) enabled. The MCX N series SDK contains various ELS command example projects including the ECSIGN usage but not with RTF enabled.  AN14154 Secure Provisioning Guidelines for MCX N Series MCUs: This application note assumes that you are already familiar with the security features available on the MCX N series devices. AN14086 Encryption and Decryption Enablement Using IPED Module on SPSDK Tool: IPED is the abbreviation of Inline Prince Encryption Decryption. The MCX N series devices offer support for real-time encryption and decryption for external flash using the IPED algorithm. Compared to AES, IPED is fast because it can decrypt and encrypt without adding extra latency. IPED operates as data is read or written, without the need to first store data in RAM and then encrypt or decrypt to another space. It operates on a block size of 64 bits with a 128-bit key. This functionality is useful for asset protection, such as securing application code that resides in external NOR flash memory. AN14095 Encryption and Decryption Enablement using IPED Module on SEC Tool: The MCX N series supports seven regions for encryption and decryption. Each crypto region resides at a memory address boundary of the external flash from 0x0800_0000 to 0x0FFF_FFFF. There must be no overlap among these seven ranges. Otherwise, the behavior of IP is undefined. AN14087 Encryption and Decryption Enablement Using NPX Module on SPSDK tool: A trend in embedded processor design is an increasing need for hardware to support cryptographic calculations that are required for system security. There are emerging customer requirements to protect application code and data stored in flash memories in an encrypted form. AN15038 EdgeLock 2GO Provisioning MCUs via Product Type using Secure Provisioning (SEC) tool:  This document offers an outline of the EdgeLock 2GO platform and discusses the "Device provisioning via product type" flow. In this case, the MCUXpresso Secure Provisioning Tool (SEC) is the proxy being used to provision an MCU. AN14670 EdgeLock 2GO Provisioning via SPSDK for MCUs: This document offers an outline of the EdgeLock 2GO platform and discusses the “Device provisioning via proxy” flow. In this case, the SPSDK command line tool is the proxy being used to provision an MCU. AN14687 Ease CRA Compliance with MCX N: This document addresses OEMs who want to understand how the MCX N series can facilitate the implementation of CRA requirements. While the MCX N series provides core security capabilities that can be mapped to the cybersecurity requirements of the CRA, the OEM must fill the remaining compliance gap by performing additional actions.  AN14624 EdgeLock 2Go Provisioning via Secure Provisioning (SEC) tool: This document offers an outline of the EdgeLock 2GO platform and discusses the "Device provisioning via proxy" flow. In this case, the MCUXpresso Secure Provisioning Tool (SEC) is the proxy being used to provision an MCU. AN14460 How to program MCX N series internal flash through ISP: This application note describes how to use USB/UART/SPI/I 2 C ISP to program internal flash of MCX N series MCUs via blhost or MCUXpresso Secure Provisioning Tool AN14544 EdgeLock 2GO Service for MPU and MCU: This application note introduces various methods that the EdgeLock 2GO service can be used with MCU and MPU devices and the features available for each method. AN14248 Recovery Boot from IFR0 for MCX Nx4x: This application note describes the step-by-step process of boot recovery of the signed binary image from Flash Bank 1 IFR 0 of the MCX Nx4x device upon failure of the image execution from the program flash. AN14255 Recovery Boot from 1-bit SPI Flash for MCXNx4x: This application note describes the step-by-step process of boot recovery of the signed binary image from 1-bit SPI flash on the MCXNx4x device upon failure of the image. AN14475 Dual Boot Secure Firmware Update using OTA HTTP Server:  This application note describes the step-by-step process to do a secure firmware update with dual image boot enabled. Covers the example provided in the SDK, which runs from internal flash and what changes are necessary to run from external memory. AN14271 CRC Calculation Features and Performance on MCX: This application note has been divided into two main parts. The first part provides information about the cyclic redundant checker (CRC). The second part introduces the features and performance of the CRC module on an MCX MCU. Training: Introduction: Flexible and Rapid Development with MCUXpresso: Getting Started with Your FRDM Development Boards Fe.... Learn more about NXP's FRDM Development Platform featuring our MCX MCUs portfolio. Discover why specific applications benefit from MCX and features to help differentiate your next product. You will also learn more about the MCUXpresso Developer Experience and how to get started with your FRDM development board. MCX Lab NXP initiative designed to foster collaboration with universities, providing students and educators with cutting-edge hardware, software, and educational resources.  ML/AI: eIQ Time Series Studio Training: Build and Run Time Series ML Models on FRDM-MCXN947 Getting Started with eIQ Time Series Studio Graphics Getting Started with Embedded GUI Development Using GUI Guider and LVGL Useful Links: See some demo videos created based on FRDM-MCXN Application Code Examples Expansion Boards and Accesories: accessories list in Expansion Board Hub compatible with FRDM-MCXN boards. Find displays, rotary, joystick, sensors, and more. Explore the different expansion boards which are supported by software to help you extend and evaluate the features in combination with FRDM-MCXN boards. Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here    MCXN
View full article
S32K358 MBDT Hi NXP expert, I have a question. The S32K358-Q289 model is not listed in the MBDT tool. It's not included in any version packages from 1.5.0 to 1.8.0. How can I resolve this? Chenxu1_0-1788095653895.pngChenxu1_0-1788095653895.pngChenxu1_0-1788095653895.pngChenxu1_0-1788095653895.png Re: S32K358 MBDT Hi, @Chenxu1, Thank you for your interest into Model-Based Design Toolbox for S32K3. The S32K358-Q289 device is not supported in the current S32K3 Toolbox releases. However, support for this device is planned for the upcoming S32K3 Toolbox v1.9.0 release, which is currently scheduled for the end of this year.   In the meantime, if you would like to start developing and evaluating software on the S32K358-Q289, you can use S32 Design Studio, which already provides support for this device.   Best regards, Dragos Re: S32K358 MBDT Hi, @simon98, Thank you for the clarification. What I meant by saying that the S32K358-Q289 is not yet supported is that the device is not currently available as a predefined hardware target in the MBDT Hardware Settings dropdown menu. As a result, there is no default board/project configuration provided by MBDT for this specific hardware variant. In particular, we do not currently provide a preconfigured target with all pin mappings, clock settings, and board-specific documentation already defined. That being said, as you have discovered, it is entirely possible to use the S32K358-Q289 with MBDT by creating a custom configuration and selecting the appropriate device package in S32 Configuration Tools.   The planned support in MBDT v1.9.0 is intended to address this by adding an official hardware target/configuration for the S32K358-Q289, making the setup process more straightforward and providing a validated default project configuration.   Hope this helps, Dragos Re: S32K358 MBDT Hi @dragostoma, Thank you for this clarification. Could you please clarify what exactly is meant by the statement that the S32K358-Q289 is “not supported” by the current S32K3 MBDT releases? I’m asking because I have actually been developing for a quite a lot of time using MBDT for an application that is specifically based on the S32K358-Q289. Throughout this development, I have been using MBDT successfully, including the S32 Configuration Tools (S32CT), where I select/change the appropriate device package. So, from a practical point of view, I have been using MBDT with the S32K358-Q289 for quite some time. Could you please explain which part of the S32K358-Q289 functionality is currently considered unsupported? For example, is the limitation related only to the device not being explicitly listed/selected in the MBDT configuration, or are there specific peripherals, drivers, code generation features, or other limitations that make the Q289 variant officially unsupported? It would be very useful to understand the exact scope of the limitation, especially since we already have a significant amount of development based on this device and MBDT. Best regards, Simon
View full article