Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
imx-firmwareからW8997ファームウェアを削除することに関する質問 NXPチームの皆様、こんにちは。 imx-firmwareリポジトリにおける以下のコミットに関してご連絡差し上げております。 「26Q1以降、BSPからSD/PCIE W8997サポートを解除」 W8997のファームウェアは標準のimx-firmwareパッケージからのみ削除されたのか、それともこれらのデバイスのサポートが完全に終了したのか、教えていただけますか? Git履歴から最後のW8997ファームウェアファイルは取得できるので、主な質問は最新のimxファームウェアを使い続けながらW8997のサポートを維持する推奨方法についてです。 最新のimx-firmwareパッケージをインストールして、それらを含む最後のリリースのW8997ファームウェアファイルを追加することはサポートされていますか? もしそうなら、これをきれいに処理し、将来のimxファームウェアアップデートとの競合を避けるための推奨される手順やパッケージング方法はありますか? 私たちの目標は、88W8997をベースにした古い展開ハードウェアのサポートを維持しつつ、システムを最新の i.MX ファームウェアパッケージに維持することです。 よろしくお願いいたします。 アントワーヌ・ジェナール Re: Question regarding removal of W8997 firmware from imx-firmware こんにちは、 @agennart さん。お元気でお過ごしでしょうか。 社内チームに確認中です。返信があり次第、ご連絡いたします。 Re: Question regarding removal of W8997 firmware from imx-firmware こんにちは、 @agennart さん。 プロジェクトの詳細を教えていただけますか?あなたが使っているW8997モジュールや、実装したインターフェース(PCIeまたはSDIO)も含めて。 Re: Question regarding removal of W8997 firmware from imx-firmware 私はW8997を使用するプロジェクトを持っていません。Buildrootプロジェクトで`imx-firmware`のバージョンを上げようとしています。Buildrootは、旧型のハードウェアとの互換性を維持しつつ、新型ハードウェアもサポートすることを目指しており、今回のアップデートはそのためのものです。 問題は、このアップデートが古いハードウェアとの互換性を壊してしまうため、その互換性を維持する方法が必要なことです。 私は二つの可能なシナリオを考えています。 1. NXPは単純に古いハードウェアのサポートを廃止しました。その場合、Buildrootプロジェクトは古いハードウェアとの互換性を維持するために適切なバージョンの「imx-firmware」を選択する方法が必要です。 2. NXPは旧ハードウェアのサポートを別のパッケージ/プロジェクトに移しました。その場合、Buildrootプロジェクトは互換性を維持するためにそのパッケージやプロジェクトを更新または統合する必要があります。 Re: Question regarding removal of W8997 firmware from imx-firmware こんにちは、 @agennart さん。 88W8997のサポートは、Github上の専用ホットフィックスブランチを通じて、W8997ドライバーとLF 6.12.49_2.2.0リリースベースラインに基づくファームウェアの両方で提供されます。これらのブランチには、今後のW8997を対象としたオフサイクルリリースがすべて含まれます。したがって、以下のホットフィックスブランチを参照するように環境を更新してください。 ドライバーブランチ - GitHub - https://github.com/nxp-imx/mwifiex/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 ファームウェアブランチ - GitHub - https://github.com/nxp-imx/imx-firmware/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 W8997との互換性を確保するために、メインブランチはこのデバイスへのさらなるサポートを受けないため、共有ホットフィックスブランチを指すのが推奨されています。 この情報がご要望に合致するかどうかお知らせください。
View full article
AFM907N PAについて もしあれば、915MHz帯のチューニングレイアウトを共有してもらえますか? Re: Regarding AFM907N PA こんにちは、lavanyaemsecさん 良い一日! 残念ながら、915 MHz 用のリファレンスレイアウトはご用意しておりません。最も近いものとしては、... AFM907N 760-870 MHz リファレンス回路設計ファイル 公式 AFM907N ページのデザインリソースセクションでご覧いただけます。 ご迷惑をおかけして申し訳ありません。 良い一日をお過ごしください。幸運を祈ります。
View full article
S32DS v3.5のライセンスが期限切れです。権利は有効ですが、延長ボタンが表示されず、返品もできません。 Hello NXP support, My NXP account holds valid entitlement for S32DS v3.5, but the generated license expired. Fulfillment ID: 113445398 IDE: S32 Design Studio for S32 Platform v3.5 License Expiry: Aug 8, 2026 Entitlement Expiry: Sep 16, 2030 Machine ID: A5883F5CCBF60C6BECC55C5A0CC9D1C68DA192AD Current situation: 1. The license management page has no EXTEND button. 2. Return license is disabled, cannot release this fulfillment. 3. The entitlement is still valid until Sep 16, 2030. Could you help refresh this fulfillment license to entitlement expiry date Sep 16,2030? I have attached the screenshot of license list for your reference. Thanks. LicenseNotAllow.png Re: S32DS v3.5 license expired, entitlement valid, no EXTEND button and Return not allowed ご協力いただき、誠にありがとうございました。S32DSの再アクティベーションに成功しました。 Re: S32DS v3.5 license expired, entitlement valid, no EXTEND button and Return not allowed こんにちは、 古いライセンスを返却しましたので、以前のコードでS32DSを再度アクティベートできるはずです。
View full article
TEA1716 сalculation file Hello, I am looking for an Excel calculation file for the TEA1716 IC, similar to those provided in the development tools for other chips in the TEA series. I am using the TEA1716DB1255 development board and following the relevant documentation, but I would also like to access the calculation file if one exists. Thank you for your reply, and have a great day! Power solution Re: TEA1716 сalculation file Hello, An Excel-based calculation sheet for the TEA1716 exists ("Calculation sheet TEA1716 draft V1_4") and serves as the replacement for the original online design tool, which is no longer operational. Please find it attached. For reference alongside the calculation sheet, the key documents for your TEA1716DB1255 work are: AN11179 — detailed design guidance including worked calculation examples UM10557 — TEA1716DB1255 demo board documentation BRs, Tomas
View full article
On-chip secure NVM (S32K314) The Secure NVM mapping(FULL_MEM) described in HSE FW install for S32K3xx.pdf is as follows: HSE data flash is 160KB,APP data flash is 88KB,total : 160KB+88KB=248KB luojing_0-1789619650388.png luojing_1-1789619740147.png However, the dflash allocation described in S32K3XXRM.pdf is as follows: The total size of dflash is 128KB luojing_2-1789619854070.png Why are the Dflash sizes mentioned in the two documents different? Note: I am using the HSE firmware version HSE_FW_S32K344_0_2_55_0_S2502.exe luojing_3-1789620886731.png Re: sRe: On-chip secure NVM (S32K314) All these information you will find in HSE-B Firmware Reference Manual. It is a secure file, so following procedure is needed to follow unless you have already done it before: https://www.nxp.com/docs/en/user-guide/nxp-secure-access-rights-registration.pdf For better understanding you may also see following link: https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS Re: sRe: On-chip secure NVM (S32K314) The HSE FW install for S32K3xx.pdf only specifies the range of HSE Pflash and dflash, without specifying the RAM range. What is the RAM range used by HSE? What are the starting address and size? Is there a specific document describing it? Re: sRe: On-chip secure NVM (S32K314) Secure data flash starts at 0x10016000 (for FULL_MEM) having 168KB. It is the same on all derivatives. The appnote is not up to date. Re: sRe: On-chip secure NVM (S32K314) luojing_0-1789654909700.png Is it incorrect for HSE (FULL UMEM) Dflash size to be 160KB? Should it be 128KB-88KB=40KB? sRe: On-chip secure NVM (S32K314) It is described here: davidtosenovjan_0-1789654479428.png
View full article
片上安全型非易失性存储器(S32K314) HSE FW install for S32K3xx.pdf 中描述的 Secure NVM 映射(FULL_MEM)如下: HSE 数据闪存为 160KB,APP 数据闪存为 88KB,总计:160KB+88KB=248KB 罗静_0-1789619650388.png 罗静_1-1789619740147.png 然而,S32K3XXRM.pdf 中描述的 dflash 分配如下: dflash的总大小为128KB 罗晶_2-1789619854070.png 为什么两份文件中提到的Dflash容量大小不同? 注意:我使用的是 HSE 固件版本 HSE_FW_S32K344_0_2_55_0_S2502.exe 罗静_3-1789620886731.png Re: sRe: On-chip secure NVM (S32K314) 所有这些信息都可以在 HSE-B 固件参考手册中找到。 这是一个安全文件,因此除非您之前已经操作过,否则需要按照以下步骤操作: https://www.nxp.com/docs/en/user-guide/nxp-secure-access-rights-registration.pdf 为了更好地理解,您还可以参考以下链接: https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS Re: sRe: On-chip secure NVM (S32K314) S32K3xx 的 HSE FW 安装说明.pdf 仅指定了 HSE Pflash 和 dflash 的范围,而没有指定 RAM 的范围。HSE使用的内存范围是多少? 起始地址和大小是多少? 是否有相关文件进行描述? Re: sRe: On-chip secure NVM (S32K314) 安全数据闪存从 0x10016000 开始(对于 FULL_MEM),大小为 168KB。所有衍生品都一样。 该应用说明已过时。 Re: sRe: On-chip secure NVM (S32K314) 罗晶_0-1789654909700.png HSE(完整 UMEM)Dflash 大小为 160KB 是否不正确?应该是 128KB-88KB=40KB 吗? sRe: On-chip secure NVM (S32K314) 具体描述如下: davidtosenovjan_0-1789654479428.png
View full article
Regarding AFM907N PA Can you share tuned layout for 915MHz frequency range if available Re: Regarding AFM907N PA Hello lavanyaemsec Good day! We regret to inform you that we do not have a reference layout for 915 MHz; the closest one would be the... AFM907N 760-870 MHz Reference Circuit Design Files Which can be found on the official AFM907N page in the design resources section. We apologize for any inconvenience this may cause. Have a great day and best of luck.
View full article
TEA1716計算ファイル こんにちは、TEA1716 IC用のExcel計算ファイルを探しています。これはTEAシリーズの他のチップの開発ツールに付属しているものに似ています。 TEA1716DB1255の開発ボードを使い、関連するドキュメントに従っていますが、もし存在すれば計算ファイルにもアクセスしたいです。 ご返信ありがとうございます。良い一日をお過ごしください! 電源ソリューション Re: TEA1716 сalculation file こんにちは、 TEA1716用のExcelベースの計算シート(「計算シートTEA1716ドラフトV1_4」)が存在し、元のオンライン設計ツールの代替として機能しています。元のオンライン設計ツールは現在は運用されていません。添付ファイルをご確認ください。 計算シートと並べて参照するために、TEA1716DB1255作業の主要な文書は以下の通りです: AN11179 — 計算例を含む詳細な設計ガイダンス UM10557 — TEA1716DB1255デモボードのドキュメント BRs、トーマス
View full article
MCXW23x — BLE connection drops repeatedly when using FRO32K MCXW235B BLE connection drops repeatedly, `disconnect reason=0x08` (LL supervision timeout), consistently a few seconds after connect  Hardware constraint (fixed, not changeable on this design):** the custom board does **not** populate a 32.768kHz crystal on `XI32K`/`XO32K` — both pins are left open. The board only has a 32MHz crystal on `XI32M`/`XO32M` Board Design Re: MCXW23x — BLE connection drops repeatedly when using FRO32K Hello, hope you are doing well. How are you selecting the clock source in your application?  FRO32K is supported as an option for the BLE sleep clock, as part of the two low-frequency sources available for MCXW23xB: external crystal oscillator XO_32K, and 32.768 kHz freely running oscillator FRO_32K. The command "HCI_CMD_OCF_LE_SELECT_SLEEP_CLOCK_SOURCE" is used to select the sleep clock source that is used for the sleep timer, where FRO32K is a sleep clock source (slp_clk_src=0x01).  In a case where the 32.768 kHz crystal (XO_32K) is absent, the free running oscillator (FRO_32K) can also act as a backup of the 32.768 kHz clocking. In MCXW23, the frequency of an on-chip or off-chip clock signal can be measured accurately with a selectable reference clock. For example, the frequency measurement function can be used to determine the frequency of the 32.768 kHz free running oscillator (FRO32K) accurately, using the frequency measure function control register (FREQ_ME_CTRL). To start a frequency measurement cycle and read the result, see MCXW23 Reference Manual Section 11.4.1. The FRO32K trim registers are available in RM section 45.4.11.2.13 FRO32K control (FRO32K) Best regards, Sofia. Re: MCXW23x — BLE connection drops repeatedly when using FRO32K Dear  sofiaurueta,  Thanks for your reply.  We also tested ll_intf_curb_sleep_state(1) to disable sleep, which returned 0. After reviewing the code, we couldn't find any explicit sleep commands. Furthermore, ll_intf_le_select_slp_clk_src(RTC_SLPTMR) was configured with value 0x02, corresponding to the RTC clock source. Additionally, we integrated FSCI into the Wireless UART sample and tested Peripheral mode, where we observed the following RX data when connecting via phone. Best Regards,
View full article
MCXW23x — FRO32K使用時にBLE接続が繰り返し切断される MCXW235B BLE接続が繰り返し切断される。`切断理由=0x08`(LL監視タイムアウト)、接続後数秒で必ず切断される。 ハードウェア制約(この設計では固定、変更不可):** カスタムボードは**XI32K/'XO32K'の32.768kHzクリスタルを**埋めていません** — 両方のピンが開いたままです。このボードには、`XI32M`/`XO32M`にのみ32MHzの水晶発振子が搭載されています。 ボード設計 Re: MCXW23x — BLE connection drops repeatedly when using FRO32K こんにちは、お元気でお過ごしでしょうか。 アプリケーションでクロックソースをどのように選んでいますか? FRO32Kは、BLEスリープクロックのオプションとしてサポートされており、MCXW23xBで使用可能な2つの低周波ソース(外部水晶発振器XO_32Kと、32.768kHzの自由発振器FRO_32K)の1つです。 コマンド「HCI_CMD_OCF_LE_SELECT_SLEEP_CLOCK_SOURCE」は、スリープタイマーに使用するスリープクロックソースを選択するために使用されます。ここで、FRO32Kはスリープクロックソースです(slp_clk_src=0x01)。32.768 kHzのクリスタル(XO_32K)がない場合、自由走行する発振器(FRO_32K)は32.768 kHzのクロックのバックアップとしても機能します。 MCXW23では、オンチップまたはオフチップのクロック信号の周波数を選択可能な参照クロックで正確に測定できます。例えば、周波数測定関数は周波数測定関数制御レジスタ(FREQ_ME_CTRL)を用いて、32.768 kHzの自由走行発振器(FRO32K)の周波数を正確に測定するために使えます。周波数測定サイクルを開始し結果を読みたい場合は、MCXW23リファレンス・マニュアルセクション11.4.1を参照してください。FRO32Kトリムレジスタは、RMセクション45.4.11.2.13 FRO32K制御(FRO32K)に記載されています。 よろしくお願いします、 ソフィア。 Re: MCXW23x — BLE connection drops repeatedly when using FRO32K 親愛なる ソフィアウレタ、 ご返信ありがとうございます。 また、スリープを無効にするために ll_intf_curb_sleep_state(1) をテストしたところ、 0が返されました。コードを調べたところ、明示的なスリープコマンドは見つかりませんでした。さらに、ll_intf_le_select_slp_clk_src(RTC_SLPTMR) は、RTC クロックソースに対応する値 0x02 に設定されました。 さらに、FSCIをワイヤレスUARTサンプルに統合し、ペリフェラルモードで電話接続時に以下のRXデータを観察しました。 よろしくお願いいたします。
View full article
MCXW23x — 使用 FRO32K 时 BLE 连接反复断开 MCXW235B BLE 连接反复断开,断开原因为 `0x08`(LL 监控超时),每次连接后几秒钟都会断开。 硬件限制(此设计中固定且不可更改):** 定制板** 未** 在 `XI32K`/`XO32K` 上安装 32.768kHz 晶振 — 两个引脚均未连接。该电路板仅在 `XI32M`/`XO32M` 上配备了 32MHz 晶振。 电路板设计 Re: MCXW23x — BLE connection drops repeatedly when using FRO32K 你好,希望你一切都好。 你的应用程序中是如何选择时钟源的? FRO32K 可作为 BLE 睡眠时钟的一个选项,是 MCXW23xB 可用的两个低频源之一:外部晶体振荡器 XO_32K 和 32.768 kHz 自由运行振荡器 FRO_32K。 命令“HCI_CMD_OCF_LE_SELECT_SLEEP_CLOCK_SOURCE”用于选择睡眠定时器使用的睡眠时钟源,其中FRO32K是一个睡眠时钟源(slp_clk_src=0x01)。如果缺少 32.768 kHz 晶体 (XO_32K),则自由运行振荡器 (FRO_32K) 也可以作为 32.768 kHz 时钟的备用。 在 MCXW23 中,可以使用可选的参考时钟精确测量片上或片外时钟信号的频率。例如,可以使用频率测量功能控制寄存器(FREQ_ME_CTRL)精确地确定 32.768 kHz 自由运转振荡器(FRO32K)的频率。要启动频率测量周期并读取结果,请参阅 MCXW23 参考手册第 11.4.1 节。FRO32K 微调寄存器可在 RM 45.4.11.2.13 节 FRO32K 控制 (FRO32K) 中找到。 此致, 索菲亚。 Re: MCXW23x — BLE connection drops repeatedly when using FRO32K 亲爱的 sofiaurueta , 谢谢你的回复。 我们还测试了 ll_intf_curb_sleep_state(1) 来禁用睡眠,结果返回0。检查代码后,我们没有找到任何显式的睡眠命令。此外,ll_intf_le_select_slp_clk_src(RTC_SLPTMR) 配置值为 0x02,对应于 RTC 时钟源。 此外,我们将 FSCI 集成到无线 UART 示例中,并测试了外围模式,在通过手机连接时观察到以下 RX 数据。 顺祝商祺!
View full article
TEA1716 计算文件 您好,我正在寻找TEA1716 IC的Excel计算文件,类似于TEA系列其他芯片开发工具中提供的计算文件。我使用的是TEA1716DB1255开发板,并按照相关文档进行操作,但我也想获取该计算文件(如果存在的话)。谢谢您的回复,祝您一切顺利! 电源解决方案 Re: TEA1716 сalculation file 你好, TEA1716 有一个基于 Excel 的计算表(“TEA1716 计算表草案 V1_4”),它取代了不再运行的原始在线设计工具。请查收附件。 除计算表外,您完成 TEA1716DB1255 工作所需的关键文件如下: AN11179 — 详细设计指南,包括计算示例 UM10557 — TEA1716DB1255 演示板文档 BRs,托马斯
View full article
オンチップセキュアNVM(S32K314) HSE FW install for S32K3xx.pdfに記載されているセキュアNVMマッピング(FULL_MEM)は以下のとおりです。 HSEデータフラッシュは160KB、APPデータフラッシュは88KB、合計:160KB+88KB=248KB 羅京_0-1789619650388.png luojing_1-1789619740147.png ただし、S32K3XXRM.pdfに記載されているdflashの割り当ては以下のとおりです。 dflashの合計サイズは128KBです。 luojing_2-1789619854070.png なぜ2つの文書に記載されているDflashのサイズが異なるのですか? 注:私はHSEファームウェアバージョンHSE_FW_S32K344_0_2_55_0_S2502.exeを使用しています。 luojing_3-1789620886731.png Re: sRe: On-chip secure NVM (S32K314) これらの情報はすべてHSE-Bファームウェアリファレンスマニュアルに記載されています。 これは安全なファイルなので、すでに行ったことがない限り、以下の手順に従う必要があります。 https://www.nxp.com/docs/en/user-guide/nxp-secure-access-rights-registration.pdf より理解を深めるために、以下のリンクもご参照ください。 https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS Re: sRe: On-chip secure NVM (S32K314) S32K3xx 用の HSE FW インストールに関する PDF ファイルでは、HSE Pflash と dflash の範囲のみが指定されており、RAM の範囲は指定されていません。HSEが使用するRAMの範囲は? 開始地点の住所とサイズを教えてください。 それについて説明した特定の文書はありますか? Re: sRe: On-chip secure NVM (S32K314) セキュアデータフラッシュは、0x10016000 (FULL_MEMの場合) から始まり、168KB の容量を持ちます。これは全てのデリバティブ商品に共通する。 アプリケーションノートは最新ではありません。 Re: sRe: On-chip secure NVM (S32K314) 羅京_0-1789654909700.png HSE(FULL UMEM)のDflashサイズが160KBというのは間違いでしょうか?128KB-88KB=40KBになるべきでしょうか? sRe: On-chip secure NVM (S32K314) 以下に説明します。 davidtosenovjan_0-1789654479428.png
View full article
S32DS v3.5 license expired, entitlement valid, no EXTEND button and Return not allowed Hello NXP support, My NXP account holds valid entitlement for S32DS v3.5, but the generated license expired. Fulfillment ID: 113445398 IDE: S32 Design Studio for S32 Platform v3.5 License Expiry: Aug 8, 2026 Entitlement Expiry: Sep 16, 2030 Machine ID: A5883F5CCBF60C6BECC55C5A0CC9D1C68DA192AD Current situation: 1. The license management page has no EXTEND button. 2. Return license is disabled, cannot release this fulfillment. 3. The entitlement is still valid until Sep 16, 2030. Could you help refresh this fulfillment license to entitlement expiry date Sep 16,2030? I have attached the screenshot of license list for your reference. Thanks. LicenseNotAllow.png Re: S32DS v3.5 license expired, entitlement valid, no EXTEND button and Return not allowed Thank you very much for your help. I have reactivated S32DS successfully. Re: S32DS v3.5 license expired, entitlement valid, no EXTEND button and Return not allowed Hi,  I returned old licenses, you should be able activate S32DS again with your old code. 
View full article
关于 AFM907N PA 如果有的话,能否分享一下针对 915MHz 频率范围的调谐布局? Re: Regarding AFM907N PA 你好 lavanyaemsec 再会! 很遗憾地通知您,我们没有 915 MHz 的参考布局图;最接近的应该是…… AFM907N 760-870 MHz 参考电路设计文件 可以在AFM907N官方页面的设计资源部分找到。 对于可能由此导致的不便,我们深感抱歉。 祝你今天过得愉快,一切顺利。
View full article
S32DS v3.5 许可证已过期,授权仍然有效,没有“延长”按钮,且不允许退货。 Hello NXP support, My NXP account holds valid entitlement for S32DS v3.5, but the generated license expired. Fulfillment ID: 113445398 IDE: S32 Design Studio for S32 Platform v3.5 License Expiry: Aug 8, 2026 Entitlement Expiry: Sep 16, 2030 Machine ID: A5883F5CCBF60C6BECC55C5A0CC9D1C68DA192AD Current situation: 1. The license management page has no EXTEND button. 2. Return license is disabled, cannot release this fulfillment. 3. The entitlement is still valid until Sep 16, 2030. Could you help refresh this fulfillment license to entitlement expiry date Sep 16,2030? I have attached the screenshot of license list for your reference. Thanks. LicenseNotAllow.png Re: S32DS v3.5 license expired, entitlement valid, no EXTEND button and Return not allowed 非常感谢您的帮助。我已经成功重新激活了S32DS。 Re: S32DS v3.5 license expired, entitlement valid, no EXTEND button and Return not allowed 你好, 我已经退回了旧的许可证,您应该可以使用之前的激活码再次激活S32DS。
View full article
Question regarding removal of W8997 firmware from imx-firmware Hello NXP team, I’m contacting you regarding the following commit in the imx-firmware repository: “Remove SD/PCIE W8997 support from BSP from 26Q1 onwards” Could you please clarify whether the W8997 firmware was only removed from the standard  imx-firmware package or wheter support for these devices has been discontinued entierly ?  We can retrieve the last W8997 firmware files from the Git history, so our main question is about the recommended way to maintain W8997 support while continuing to use the latest imx-firmware releases. Is it supported to install the latest imx-firmware package and add the W8997 firmware files from the last release that contained them? If so, is there any recommended procedure or packaging approach to do this cleanly and avoid conflicts with future imx-firmware updates? Our goal is to keep systems on the latest i.MX firmware package while preserving support for older deployed hardware based on the 88W8997. Best regards, Antoine Gennart Re: Question regarding removal of W8997 firmware from imx-firmware Hello @agennart, hope you are doing well. I'm checking this with the internal team. I will get back to you once I get a response. Re: Question regarding removal of W8997 firmware from imx-firmware Hi @agennart, Could you please provide more details on your project? As well as the W8997 module that you are using and the interface you have implemented (PCIe or SDIO). Re: Question regarding removal of W8997 firmware from imx-firmware I don't have a project using W8997. I am trying to bump the `imx-firmware` version in the Buildroot project. Buildroot aims to maintain compatibility with older hardware, while also supporting newer hardware, hence the update. The problem is that this update would break compatibility with older hardware, so I need a way to preserve that compatibility. I see two possible scenarios: 1. NXP has simply removed support for the older hardware. In that case, the Buildroot project needs a way to select the appropriate version of `imx-firmware` in order to maintain compatibility with older hardware. 2. NXP has moved support for the older hardware to another package/project. In that case, the Buildroot project needs to update or integrate that package/project to maintain compatibility. Re: Question regarding removal of W8997 firmware from imx-firmware Hi @agennart, Support for 88W8997 will be provided through dedicated hotfix branches on Github for both W8997 drivers and firmware based on the LF 6.12.49_2.2.0 release baseline. These branches will contain all future off-cycle releases targeting W8997. Hence, you may update your environemnt to reference the below hotfix branches: Driver branch - GitHub - https://github.com/nxp-imx/mwifiex/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 Firmware branch - GitHub -https://github.com/nxp-imx/imx-firmware/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 For compatibility with W8997, the suggested path is to point to the shared hotfix branches as the main branch will not receive further support for this device. Please let me know if this information fits your requirements.
View full article
关于从 imx-firmware 中移除 W8997 固件的问题 您好,NXP团队, 我联系您是关于imx-firmware仓库中的以下提交: “从 26 年第一季度开始,从电路板支持包中移除 SD/PCIE W8997 支持” 请问W8997固件只是从标准imx固件包中移除,还是已经完全停止对这些设备的支持? 我们可以从 Git 历史记录中检索到最新的 W8997 固件文件,因此我们的主要问题是,在继续使用最新的 imx-firmware 版本的同时,保持对 W8997 支持的推荐方法是什么。 是否支持安装最新的 imx-firmware 软件包,并添加包含这些文件的上一版本中的 W8997 固件文件? 如果是这样,是否有推荐的步骤或打包方法可以干净利落地完成此操作,并避免与未来的 imx 固件更新发生冲突? 我们的目标是在保持对基于 88W8997 的旧已部署硬件的支持的同时,使系统保持最新的 i.MX 固件包。 顺祝商祺! 安托万·热纳尔 Re: Question regarding removal of W8997 firmware from imx-firmware 你好@agennart ,希望你一切都好。 我正在和内部团队核实此事。我收到回复后会尽快回复你。 Re: Question regarding removal of W8997 firmware from imx-firmware 嗨@agennart , 您能否提供更多关于您项目的信息?除了您正在使用的 W8997 模块和您实现的接口(PCIe 或 SDIO)之外。 Re: Question regarding removal of W8997 firmware from imx-firmware 我没有使用 W8997 的项目。我正在尝试提升 Buildroot 项目中的 `imx-firmware` 版本。Buildroot 的目标是在保持与旧硬件兼容性的同时,也支持新硬件,因此进行了此次更新。 问题在于这次更新会破坏与旧硬件的兼容性,所以我需要一种方法来保持这种兼容性。 我认为有两种可能的情况: 1. NXP 已停止对旧硬件的支持。在这种情况下,Buildroot 项目需要一种方法来选择合适的 `imx-firmware` 版本,以保持与旧硬件的兼容性。 2. NXP 已将对旧硬件的支持转移到另一个代码包,软件包/项目中。在这种情况下,Buildroot 项目需要更新或集成该软件包/项目以保持兼容性。 Re: Question regarding removal of W8997 firmware from imx-firmware 嗨@agennart , 我们将通过 Github 上的专用热修复分支为 88W8997 提供支持,包括基于LF 6.12.49_2.2.0 版本基线的 W8997 驱动程序和固件。这些分支将包含所有面向 W8997 的未来非周期性版本。因此,您可以更新您的环境以引用以下热修复分支: 驱动程序分支 - GitHub - https://github.com/nxp-imx/mwifiex/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 固件分支 - GitHub - https://github.com/nxp-imx/imx-firmware/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 为了与 W8997 兼容,建议指向共享的热修复分支,因为主分支将不再获得对该设备的进一步支持。 请告诉我这些信息是否符合您的要求。
View full article
Seeking guidance: se05x_Minimal fails in OP-TEE environment Hello NXP Community, I am attempting to run se05x_Minimal on our target board running Linux with OP-TEE. Following the solution recommended in this community post (How to integrate Plug and Trust MW into OP-TEE), we built the environment accordingly. In particular, for Step 2, we configured the setup without enabling "keep CAAM enabled". As a result of this configuration, the I2C bus connected to SE05x is managed by OP-TEE (Secure World), and the standard Linux I2C device node /dev/i2c-1 is not visible/available in the Normal World (Linux). When executing `./se05x_Minimal` directly from the Linux user-space console, we encounter the following error: App :INFO :Running ./se05x_Minimal App :INFO :If you want to over-ride the selection, use ENV=EX_SSS_BOOT_SSS_PORT or pass in command line arguments. App :INFO :PlugAndTrust_v04.07.01_20250519 App :INFO :Using default PlatfSCP03 keys. You can use keys from file using ENV=EX_SSS_BOOT_SCP03_PATH smCom :ERROR:opening failed... Failed to open the i2c bus: No such file or directory smCom :INFO :Pass i2c device address in the format : . smCom :INFO :Example ./example /dev/i2c-1:0x48 OR ./example /dev/i2c-1 smCom :ERROR:phPalEse_i2c_open_and_configure Failed retry smCom :ERROR:I2C init Failed: retval d smCom :ERROR:phPalEse_Init Failed smCom :ERROR: Failed to create physical connection with ESE sss :ERROR:SM_I2CConnect Failed. Status 7012 App :ERROR:sss_session_open failed App :ERROR:ex_sss_session_open Failed App :ERROR:!ERROR! ret != 0. Environment & Hardware Setup: Evaluation Board: MCIMX8M-WEVK (i.MX 8M Dual/Quad) Secure Element Board: OM-SE051ARD Secure Element: SE05x (Plug & Trust MW v04.07.01) OS: Linux (Normal World) + OP-TEE (Secure World) Middleware Options (CMake): -DPTMW_Host=iMXLinux, -DPTMW_SMCOM=T1oI2C Note: se05x_Minimal works fine if Linux kernel-space direct I2C (/dev/i2c-1) is enabled. It appears smCom is still attempting to open the physical Linux I2C device (/dev/i2c-X), which no longer exists in our Normal World environment. Could you please provide instructions on what we need to do or modify so that se05x_Minimal can run successfully in this setup? SE050 Re: Seeking guidance: se05x_Minimal fails in OP-TEE environment @Kan_Li  Thank you very much for your detailed explanation and the C code samples. Following your guidance, we implemented a C application using the standard PKCS#11 API (libckteec.so.0) under Option 1 (OP-TEE exclusive I2C setup). All operations -- including key generation, AES encrypt/decrypt, RSA sign/verify, and RSA encrypt/decrypt -- are now working completely as expected. We appreciate your support in resolving this issue. Re: Seeking guidance: se05x_Minimal fails in OP-TEE environment Hi @Uc_S , This is an excellent and important question. The short answer is: In Option 1 (OP-TEE exclusive I2C), the Plug & Trust MW SSS APIs cannot be used from Linux userspace directly. You must use the standard PKCS#11 C API via libckteec.so . Below is a detailed explanation and complete C code samples for all the operations you need. Why SSS APIs Cannot Be Used in This Setup The Plug & Trust MW SSS APIs ( sss_session_open , sss_key_store_set_key , sss_asymmetric_sign_digest , etc.) rely on a transport layer to communicate with the SE051. All supported transports ( T1oI2C , JRCP_V1_AM , etc.) ultimately require either Linux I2C access or a proxy server — neither of which is available when OP-TEE exclusively owns the I2C bus. The correct path in the OP-TEE exclusive setup is: Your C App → PKCS#11 C API (cryptoki.h) → libckteec.so → OP-TEE PKCS#11 TA → SE051 libckteec is provided by optee-client and implements the Cryptoki interface with the OP-TEE PKCS#11 TA as its backend. The TA in turn routes crypto operations to SE051 via OP-TEE's native I2C driver. Required Headers and Linking #include /* Standard Cryptoki header — from optee-client or OpenSC */ Compile and link: gcc -o my_app my_app.c -ldl # Or link directly: gcc -o my_app my_app.c /usr/lib/libckteec.so.0 At runtime, set the module path if using dynamic loading: #define PKCS11_MODULE "/usr/lib/libckteec.so.0" Initialization and Token Setup (call once at startup) #include #include #include #define CHECK_RV(rv, msg) \ if ((rv) != CKR_OK) { fprintf(stderr, "%s failed: 0x%lX\n", (msg), (rv)); goto cleanup; } /* User PIN — must match what was set with pkcs11-tool --init-pin */ static CK_UTF8CHAR user_pin[] = "1234"; static CK_ULONG user_pin_len = 4; CK_FUNCTION_LIST *p11 = NULL; /* Global function list pointer */ CK_SESSION_HANDLE session = CK_INVALID_HANDLE; int pkcs11_init(void) { CK_RV rv; CK_ULONG slot_count = 0; CK_SLOT_ID slot_id; CK_SLOT_ID slot_list[8]; /* Load function list — if using dynamic linking, use C_GetFunctionList() */ rv = C_Initialize(NULL_PTR); CHECK_RV(rv, "C_Initialize"); /* Get available slots */ rv = C_GetSlotList(CK_TRUE, NULL_PTR, &slot_count); CHECK_RV(rv, "C_GetSlotList (count)"); rv = C_GetSlotList(CK_TRUE, slot_list, &slot_count); CHECK_RV(rv, "C_GetSlotList"); slot_id = slot_list[0]; /* Use first slot — OP-TEE PKCS#11 TA */ /* Open a read-write session */ rv = C_OpenSession(slot_id, CKF_SERIAL_SESSION | CKF_RW_SESSION, NULL_PTR, NULL_PTR, &session); CHECK_RV(rv, "C_OpenSession"); /* Login as normal user */ rv = C_Login(session, CKU_USER, user_pin, user_pin_len); CHECK_RV(rv, "C_Login"); return 0; cleanup: return -1; } void pkcs11_cleanup(void) { C_Logout(session); C_CloseSession(session); C_Finalize(NULL_PTR); } Operation 1: Generate an RSA Key Pair and Store in SE051 int generate_rsa_keypair(CK_OBJECT_HANDLE *pub_key, CK_OBJECT_HANDLE *priv_key) { CK_RV rv; CK_MECHANISM mech = { CKM_RSA_PKCS_KEY_PAIR_GEN, NULL_PTR, 0 }; CK_ULONG key_bits = 2048; CK_BYTE pub_exponent[] = { 0x01, 0x00, 0x01 }; /* 65537 */ CK_BBOOL ck_true = CK_TRUE; CK_BBOOL ck_false = CK_FALSE; /* Key ID stored in SE051 NVM — choose a unique 4-byte ID */ CK_BYTE key_id[] = { 0x10, 0x10, 0x10, 0x10 }; CK_ATTRIBUTE pub_tmpl[] = { { CKA_MODULUS_BITS, &key_bits, sizeof(key_bits) }, { CKA_PUBLIC_EXPONENT, pub_exponent, sizeof(pub_exponent) }, { CKA_VERIFY, &ck_true, sizeof(ck_true) }, { CKA_ENCRYPT, &ck_true, sizeof(ck_true) }, { CKA_TOKEN, &ck_true, sizeof(ck_true) }, { CKA_ID, key_id, sizeof(key_id) }, }; CK_ATTRIBUTE priv_tmpl[] = { { CKA_SIGN, &ck_true, sizeof(ck_true) }, { CKA_DECRYPT, &ck_true, sizeof(ck_true) }, { CKA_TOKEN, &ck_true, sizeof(ck_true) }, { CKA_SENSITIVE, &ck_true, sizeof(ck_true) }, { CKA_EXTRACTABLE, &ck_false, sizeof(ck_false) }, { CKA_ID, key_id, sizeof(key_id) }, }; rv = C_GenerateKeyPair(session, &mech, pub_tmpl, sizeof(pub_tmpl) / sizeof(pub_tmpl[0]), priv_tmpl, sizeof(priv_tmpl) / sizeof(priv_tmpl[0]), pub_key, priv_key); CHECK_RV(rv, "C_GenerateKeyPair"); printf("RSA-2048 key pair generated. Private key stays in SE051 NVM.\n"); return 0; cleanup: return -1; } Operation 2: Generate an AES Key and Store in SE051 int generate_aes_key(CK_OBJECT_HANDLE *aes_key) { CK_RV rv; CK_MECHANISM mech = { CKM_AES_KEY_GEN, NULL_PTR, 0 }; CK_ULONG key_len = 32; /* 256-bit AES */ CK_BBOOL ck_true = CK_TRUE; CK_BBOOL ck_false = CK_FALSE; CK_BYTE key_id[] = { 0x20, 0x00, 0x00, 0x01 }; CK_ATTRIBUTE aes_tmpl[] = { { CKA_VALUE_LEN, &key_len, sizeof(key_len) }, { CKA_ENCRYPT, &ck_true, sizeof(ck_true) }, { CKA_DECRYPT, &ck_true, sizeof(ck_true) }, { CKA_TOKEN, &ck_true, sizeof(ck_true) }, { CKA_SENSITIVE, &ck_true, sizeof(ck_true) }, { CKA_EXTRACTABLE, &ck_false, sizeof(ck_false) }, { CKA_ID, key_id, sizeof(key_id) }, }; rv = C_GenerateKey(session, &mech, aes_tmpl, sizeof(aes_tmpl) / sizeof(aes_tmpl[0]), aes_key); CHECK_RV(rv, "C_GenerateKey (AES)"); printf("AES-256 key generated and stored in SE051.\n"); return 0; cleanup: return -1; } Operations 3 & 4: AES-CBC Encrypt / Decrypt int aes_encrypt(CK_OBJECT_HANDLE aes_key, const CK_BYTE *plaintext, CK_ULONG plaintext_len, CK_BYTE *ciphertext, CK_ULONG *ciphertext_len) { CK_RV rv; CK_BYTE iv[16] = { 0 }; /* All-zero IV for example; use a random IV in production */ CK_MECHANISM mech = { CKM_AES_CBC_PAD, iv, sizeof(iv) }; rv = C_EncryptInit(session, &mech, aes_key); CHECK_RV(rv, "C_EncryptInit"); rv = C_Encrypt(session, (CK_BYTE *)plaintext, plaintext_len, ciphertext, ciphertext_len); CHECK_RV(rv, "C_Encrypt"); return 0; cleanup: return -1; } int aes_decrypt(CK_OBJECT_HANDLE aes_key, const CK_BYTE *ciphertext, CK_ULONG ciphertext_len, CK_BYTE *plaintext, CK_ULONG *plaintext_len) { CK_RV rv; CK_BYTE iv[16] = { 0 }; /* Must match the IV used for encryption */ CK_MECHANISM mech = { CKM_AES_CBC_PAD, iv, sizeof(iv) }; rv = C_DecryptInit(session, &mech, aes_key); CHECK_RV(rv, "C_DecryptInit"); rv = C_Decrypt(session, (CK_BYTE *)ciphertext, ciphertext_len, plaintext, plaintext_len); CHECK_RV(rv, "C_Decrypt"); return 0; cleanup: return -1; } Operations 5 & 6: RSA Sign (private key stays in SE051) and Verify int rsa_sign(CK_OBJECT_HANDLE priv_key, const CK_BYTE *data, CK_ULONG data_len, CK_BYTE *signature, CK_ULONG *sig_len) { CK_RV rv; /* SHA256-PKCS1v1.5 — SE051 computes SHA-256 digest internally then signs */ CK_MECHANISM mech = { CKM_SHA256_RSA_PKCS, NULL_PTR, 0 }; rv = C_SignInit(session, &mech, priv_key); CHECK_RV(rv, "C_SignInit"); rv = C_Sign(session, (CK_BYTE *)data, data_len, signature, sig_len); CHECK_RV(rv, "C_Sign"); printf("RSA signature generated (%lu bytes). Private key never left SE051.\n", *sig_len); return 0; cleanup: return -1; } int rsa_verify(CK_OBJECT_HANDLE pub_key, const CK_BYTE *data, CK_ULONG data_len, const CK_BYTE *signature, CK_ULONG sig_len) { CK_RV rv; CK_MECHANISM mech = { CKM_SHA256_RSA_PKCS, NULL_PTR, 0 }; rv = C_VerifyInit(session, &mech, pub_key); CHECK_RV(rv, "C_VerifyInit"); rv = C_Verify(session, (CK_BYTE *)data, data_len, (CK_BYTE *)signature, sig_len); if (rv == CKR_OK) { printf("Signature verification: SUCCESS\n"); return 0; } else if (rv == CKR_SIGNATURE_INVALID) { printf("Signature verification: INVALID\n"); return 1; } CHECK_RV(rv, "C_Verify"); cleanup: return -1; } Operations 7 & 8: RSA Encrypt / Decrypt int rsa_encrypt(CK_OBJECT_HANDLE pub_key, const CK_BYTE *plaintext, CK_ULONG plaintext_len, CK_BYTE *ciphertext, CK_ULONG *ciphertext_len) { CK_RV rv; /* RSA-OAEP with SHA-256 — recommended over PKCS1 v1.5 for new designs */ CK_RSA_PKCS_OAEP_PARAMS oaep_params = { .hashAlg = CKM_SHA256, .mgf = CKG_MGF1_SHA256, .source = CKZ_DATA_SPECIFIED, .pSourceData = NULL, .ulSourceDataLen = 0 }; CK_MECHANISM mech = { CKM_RSA_PKCS_OAEP, &oaep_params, sizeof(oaep_params) }; rv = C_EncryptInit(session, &mech, pub_key); CHECK_RV(rv, "C_EncryptInit (RSA-OAEP)"); rv = C_Encrypt(session, (CK_BYTE *)plaintext, plaintext_len, ciphertext, ciphertext_len); CHECK_RV(rv, "C_Encrypt (RSA-OAEP)"); return 0; cleanup: return -1; } int rsa_decrypt(CK_OBJECT_HANDLE priv_key, const CK_BYTE *ciphertext, CK_ULONG ciphertext_len, CK_BYTE *plaintext, CK_ULONG *plaintext_len) { CK_RV rv; CK_RSA_PKCS_OAEP_PARAMS oaep_params = { .hashAlg = CKM_SHA256, .mgf = CKG_MGF1_SHA256, .source = CKZ_DATA_SPECIFIED, .pSourceData = NULL, .ulSourceDataLen = 0 }; CK_MECHANISM mech = { CKM_RSA_PKCS_OAEP, &oaep_params, sizeof(oaep_params) }; rv = C_DecryptInit(session, &mech, priv_key); CHECK_RV(rv, "C_DecryptInit (RSA-OAEP)"); rv = C_Decrypt(session, (CK_BYTE *)ciphertext, ciphertext_len, plaintext, plaintext_len); CHECK_RV(rv, "C_Decrypt (RSA-OAEP)"); printf("RSA decryption completed. Private key never left SE051.\n"); return 0; cleanup: return -1; } Accessing Existing Keys (without regenerating) If a key was previously generated and stored in SE051, retrieve it by CKA_ID without calling C_GenerateKey again: int find_key_by_id(CK_BYTE *key_id, CK_ULONG key_id_len, CK_OBJECT_CLASS obj_class, CK_OBJECT_HANDLE *handle) { CK_RV rv; CK_ULONG obj_count = 0; CK_ATTRIBUTE search_tmpl[] = { { CKA_CLASS, &obj_class, sizeof(obj_class) }, { CKA_ID, key_id, key_id_len }, }; rv = C_FindObjectsInit(session, search_tmpl, sizeof(search_tmpl) / sizeof(search_tmpl[0])); CHECK_RV(rv, "C_FindObjectsInit"); rv = C_FindObjects(session, handle, 1, &obj_count); CHECK_RV(rv, "C_FindObjects"); C_FindObjectsFinal(session); if (obj_count == 0) { fprintf(stderr, "Key not found in SE051\n"); return -1; } return 0; cleanup: C_FindObjectsFinal(session); return -1; } Usage example: CK_OBJECT_HANDLE priv_key; CK_BYTE key_id[] = { 0x10, 0x10, 0x10, 0x10 }; CK_OBJECT_CLASS priv_class = CKO_PRIVATE_KEY; find_key_by_id(key_id, sizeof(key_id), priv_class, &priv_key); Supported Mechanisms (verified on OP-TEE PKCS#11 TA + SE051) Operation Mechanism Constant Notes RSA key generation CKM_RSA_PKCS_KEY_PAIR_GEN 256–4096 bits AES key generation CKM_AES_KEY_GEN 16 or 32 bytes RSA sign/verify CKM_SHA256_RSA_PKCS PKCS#1 v1.5 RSA sign/verify (PSS) CKM_SHA256_RSA_PKCS_PSS PSS padding RSA encrypt/decrypt CKM_RSA_PKCS_OAEP OAEP recommended RSA encrypt/decrypt CKM_RSA_PKCS PKCS#1 v1.5 AES encrypt/decrypt CKM_AES_CBC_PAD CBC with PKCS#7 AES encrypt/decrypt CKM_AES_CBC CBC without padding AES encrypt/decrypt CKM_AES_CTR CTR mode ECC sign/verify CKM_ECDSA_SHA256 160–521 bits ECDH key agreement CKM_ECDH1_DERIVE   Can the SSS APIs Still Be Used at All? Yes — but only in the co-existence setup (Option 2) where Linux still has access to the I2C bus (i.e., the lf-6.12.y-i2c-disabled-se050 DTS patch has NOT been applied). In that case, you can use the SSS APIs as described in AN13030 Section 3.3 directly from Linux. If you choose Option 1 (OP-TEE exclusive), the Cryptoki/PKCS#11 C API shown above is the correct and only supported path from Linux userspace. Reference AN13030 Rev. 2.4, Section 3.3 — Full SSS API reference (for co-existence / non-OP-TEE builds) OP-TEE PKCS#11 TA test suite (pkcs11_1000.c): optee-test/host/xtest/pkcs11_1000.c — comprehensive C examples for all Cryptoki operations NXP GitHub: se05x-pkcs11 — NXP's PKCS#11 standalone library (alternative to libckteec.so for non-OP-TEE builds)   Hope that helps,   Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. ------------------------------------------------------------------------------- Re: Seeking guidance: se05x_Minimal fails in OP-TEE environment @Kan_Li  Thank you very much for the clear and detailed explanation. We are currently considering using Option 1 or Option 2 depending on the stage of our future development (e.g., using Option 2 for initial testing/evaluation and Option 1 for production). Regarding Option 1 (OP-TEE PKCS#11 TA), we have a question about application development in C. If we would like to implement cryptographic operations such as key storage, signing / signature generation, signature verification, and encryption/decryption in a C program under Option 1, which approach should we take? Should we write a C program that directly calls standard PKCS#11 APIs (e.g., C_Initialize, C_CreateObject, C_SignInit, C_Sign, C_VerifyInit, C_Verify, etc.) via the OP-TEE PKCS#11 library (libckteec.so)? Or is it still possible/recommended to use the Plug & Trust MW SSS APIs (such as sss_key_store_set_key, sss_asymmetric_sign_digest, sss_asymmetric_verify_digest, sss_cipher_update, etc.) in this setup? If PKCS#11 APIs are required, could you please provide a simple sample code or reference guide for calling libckteec.so in C? Re: Seeking guidance: se05x_Minimal fails in OP-TEE environment Hi @Uc_S , Thank you for the detailed report. The root cause is clear, and I can explain exactly why this happens and what your options are. Root Cause se05x_Minimal was built with -DPTMW_SMCOM=T1oI2C . This tells the smCom layer to open a physical Linux I2C device node ( /dev/i2c-X ) at session open time. Since you applied the lf-6.12.y-i2c-disabled-se050 DTS patch (Step 1 of the integration guide), that I2C controller is disabled in Linux Normal World — the device node simply does not exist. OP-TEE exclusively owns the I2C bus via CFG_IMX_I2C=y , and Linux cannot see or open it. This is by design — the DTS patch is what gives OP-TEE exclusive, uncontended access to SE051. The se05x_Minimal binary built with T1oI2C is fundamentally incompatible with this configuration. Your Two Options ✅ Option 1 — Use OP-TEE PKCS#11 TA (Recommended for Production) This is the intended Linux userspace path in the OP-TEE exclusive setup. Instead of running se05x_Minimal , use pkcs11-tool or OpenSSL with libckteec.so (the OP-TEE PKCS#11 TA library). The TA internally uses SE051 as its crypto backend via OP-TEE's native I2C driver. Quick verification that SE051 is reachable via PKCS#11: # List available PKCS#11 slots — SE051 should appear pkcs11-tool --module /usr/lib/libckteec.so.0 --list-slots # Get a random number from SE051 via OP-TEE pkcs11-tool --module /usr/lib/libckteec.so.0 --generate-random 16 | xxd If you see a slot and random bytes, SE051 is fully accessible through OP-TEE. There is no need to run se05x_Minimal — it duplicates what the PKCS#11 TA already provides. ✅ Option 2 — Co-existence Setup (Recommended for Development/Testing) If you specifically need to run se05x_Minimal and other Plug & Trust MW demos from Linux userspace, use the co-existence setup where Linux DTS still has I2C enabled (i.e., do not apply the I2C-disabled DTS patch). Steps: Step 1 — Revert the Linux DTS to keep I2C enabled in Normal World Build your imx8mq-evk.dtb (or equivalent) from the unmodified Linux DTS (without the lf-6.12.y-i2c-disabled-se050 patch). The I2C controller node for SE051 must remain enabled in Linux. Step 2 — Keep your existing cmake flags unchanged Your current cmake configuration is correct for co-existence: cmake -S . -B ./build/ -DPTMW_Applet=SE05X_C -DPTMW_SE05X_Ver=07_02 -DPTMW_Host=iMXLinux -DPTMW_SMCOM=T1oI2C -DPTMW_HostCrypto=OPENSSL -DPTMW_RTOS=Default -DPTMW_mbedTLS_ALT=None -DPTMW_SCP=SCP03_SSS -DPTMW_SE05X_Auth=PlatfSCP03 -DPTMW_Log=Silent -DCMAKE_BUILD_TYPE=Release -DPTMW_OpenSSL=3_0 -DPTMW_SE_RESET_LOGIC=1 Step 3 — Set the I2C port before running export EX_SSS_BOOT_SSS_PORT=/dev/i2c-1 ./se05x_Minimal Trade-off: In this mode, both OP-TEE and Linux share the I2C bus to SE051. OP-TEE uses it for RSA/ECC offload; Linux uses it for MW demos. Concurrent access is not arbitrated, which can cause APDU collisions under load. Acceptable for development, but not recommended for production. Summary Option I2C DTS se05x_Minimal OP-TEE exclusive Recommended For PKCS#11 TA ( libckteec.so ) Disabled ❌ Not needed ✅ Yes Production Co-existence (T1oI2C) Enabled ✅ Works ⚠️ Shared I2C Development/Testing Clarification on the Integration Guide The community post you referenced (Step 2 — without CAAM) configures OP-TEE to exclusively own I2C. The Linux-side MW compilation shown in that guide (with T1oI2C ) was intended for the initial verification step before switching to OP-TEE mode — not for use alongside the OP-TEE exclusive I2C setup. Once OP-TEE owns I2C exclusively, the correct Linux userspace interface is the OP-TEE PKCS#11 TA, not the Plug & Trust MW SSS API demos directly. Please let us know which option fits your use case and we can provide further guidance. Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------
View full article
I2C read and write using s32k144 MBD toolbox Hello, I am using s32k144 to read and write data from an external EEPROM. I will attach the model below. I am able to write the data but the read returns 255+NACK as output. Am i missing something here Sriram_0-1737789999186.png Sriram_1-1737790013461.png Is there a way to specify the register address of the EEPROM in the I2Cmaster block Sriram_2-1737790096449.png Can you guys help me out with this issue. Thanks Re: I2C read and write using s32k144 MBD toolbox Hi, I am also facing the same issue with I2C communication using the S32K144 as the master and the ST M24C04 EEPROM as the slave. Since you are using the same microcontroller and EEPROM, I wanted to check whether you were able to find a solution. If you have resolved this issue, could you please share the solution or let me know what fixed it? Thank you in advance for your help. Re: I2C read and write using s32k144 MBD toolbox I m using M24C02-DRE EEPROM
View full article