Multi Source Translation Content

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

Multi Source Translation Content

ディスカッション

ソート順:
采用 MC33FS6523CAE (FS6500 SBC) 的 S32K358 电源设计 Hello 我正在使用 S32K358 进行设计,并计划使用 MC33FS6523CAE SBC。这种搭配是否受支持?考虑到S32K3内部采用开关电源,您推荐将VDD_HV_A/B、VREFH和V15分别连接到哪些SBC输出(VCORE、VCCA)? 谢谢! https://www.nxp.com/products/FS6500?page=9&nrnd=false Re: S32K358 power supply design with MC33FS6523CAE (FS6500 SBC) 你好,萨克希, MC33FS6523CAE 是与 S32K358 兼容的 SBC。不过,我想强调的是,我们推荐与 S32K358 搭配使用的 SBC 是 FS26,原因如下所述。 FS26 是专为 S32K3 系列(包括 S32K358)设计的功能安全 SBC 连接解决方案。它为S32K358设计提供了一些特别相关的优势: - 专用的参考文档:AN13850(FS26 实现和行为)包含一个专门介绍 FS26 与 S32K358 连接的章节。 -ASIL D 功能安全覆盖范围:FS26 系列专用的 ASIL D 应用而开发和验证,采用 S32K3,并配备专用的 RTD 软件驱动程序和安全应用笔记组合,可随时用于生产。 - 更高电流的 低压差线性稳压器\(LDO\) 输出:FS26 低压差线性稳压器\(LDO\)1 和 LDO2 直接向 S32K358 提供 VDD_HV_A 和 VDD_HV_B。我们的 FRDM-A-S32K358 评估板使用 FS26 作为配套 SBC,其中 LDO1 提供 VDD_HV_A (+3.3 V),LDO2 提供 VDD_HV_B (+3.3 V)。 - 现成的软件:适用于 S32K3 + FS26 的生产就绪 RTD 软件包已可用,大大减少了软件开发工作量。 如果您需要在单个 SBC 封装中集成 CAN FD + LIN 收发器,MC33FS6523CAE 仍然是 S32K358 的一个受支持且功能齐全的 SBC 选择。 BRs,托马斯
記事全体を表示
i.MX95 LPDDR4x 读取模拟通过/失败标准 大家好 对于 i.MX95 处理器,能否提供 LPDDR4x读取时序裕量和仿真通过/失败标准? 汽车电子 工业控制
記事全体を表示
MIMXRT700-EVK 刷写错误 你好, 我无法使用 NXP LinkServer 将我的应用程序刷写到MIMXRT700-EVK上。 硬件/软件: 电路板:MIMXRT700-EVK MCU:MIMXRT798S 调试器:板载 MCU-Link MCU-Link固件版本:V3.172 链接服务器:26.6.137 操作系统:Ubuntu Linux 电源通过 J54 提供 刷写过程中,LinkServer 报告: Error: Wire Ack Fault - target connected? Error: Wire not connected Failed on connect: Ee(42). Could not connect to core. No connection to chip's debug port Flash operation exited with code 1 PC 可以正确检测到 MCU-Link,LinkServer 可以检测到探针。 重要的硬件观察结果是D4红色LED指示灯不亮。根据MIMXRT700-EVK文档,D4指示MCU/RESET状态,其中ON表示处理器正常活动,OFF表示处理器处于RESET状态。 我还执行了RT700预连接脚本,但SWD连接仍然失败,并显示以下错误: Error: Wire Ack Fault - target connected? Error: Wire not connected 支持请求 请问您能否提供以下建议: 为什么 当电路板通过 J54 供电时, D4 LED 灯不亮 ? 如何使RT700处理器退出RESET状态? 是否需要检查任何RESET、启动或硬件配置? 我应该使用哪种恢复程序来恢复LinkServer 的连接,以便我可以刷写应用程序? 评估板 Re: MIMXRT700-EVK Flashing Error 嗨@Aparna1 , 电源很可能没有正确分配给 MCU/电路板的其他部分,而是只分配给了板载调试器。 绿色的D10 LED指示灯也熄灭了吗? 请确保 J2 的跳线位置将引脚 7 和 8 短接。 BR, 埃德温。 Re: MIMXRT700-EVK Flashing Error 您好, 是的,我已经核实了以下内容: 绿色D10 LED指示灯亮起。 J2 将引脚 7 和 8 短接。 如果还需要我进行任何额外的检查,请告知。 问候, 阿帕娜 Re: MIMXRT700-EVK Flashing Error 这是连接 USB 后的状态 Re: MIMXRT700-EVK Flashing Error 您好, 请问我的工单有什么最新进展吗?我仍在等待回复。   谢谢!     Re: MIMXRT700-EVK Flashing Error 您好, 请问我的工单有什么最新进展吗?我仍在等待回复。   谢谢!   Re: MIMXRT700-EVK Flashing Error 您好, 请问我的工单有什么最新进展吗?我仍在等待回复。   谢谢!
記事全体を表示
iMX95 - EMMC 部件确认 大家好, 我们为 128GB EMMC 部件提供了两种替代方案。请问以下部件是否可以与IMX95一起使用? BIWIN零件 - BWEFMA128GN9KC SANDISK 零件 - SDINBDA6-128G-ZA 此致, 因德拉吉特·S Re: iMX95 - EMMC Part confirmation 你好@indrajith_shanmugam , 对于 eMMC i.MX95,支持 eMMC 5.1,没有特殊需求。 在这里,您可以根据 i.MX95 usdhc1 的接口需求来修改 emmc 数据表,这样就可以了。 希望这对您有所帮助。 如有任何疑问,请随时与我联系。 祝你今天过得愉快 顺祝商祺! Rita
記事全体を表示
MIMXRT700-EVK フラッシュエラー こんにちは、 NXP LinkServerを使って MIMXRT700-EVK にアプリケーションをフラッシュできません。 ハードウェア/ソフトウェア: ボード: MIMXRT700-EVK MCU:MIMXRT798S デバッガ:搭載MCU-Link MCU-Linkファームウェア:V3.172 リンクサーバー: 26.6.137 OS:Ubuntu Linux 電源はJ54から供給されます。 フラッシュ処理中、LinkServerは以下を報告します。 Error: Wire Ack Fault - target connected? Error: Wire not connected Failed on connect: Ee(42). Could not connect to core. No connection to chip's debug port Flash operation exited with code 1 MCU-LinkはPCによって正しく検出され、LinkServerはプローブを検出できます。 重要なハードウェアの観察点は、D4の赤いLEDが点灯していないことです。MIMXRT700-EVKのドキュメントによると、D4はMCU/リセットの状態を示し、ONは通常のプロセッサ活動、OFFはプロセッサがリセット中であることを示します。 RT700のプリコネクトスクリプトも実行しましたが、SWD接続は依然として以下のエラーで失敗します。 Error: Wire Ack Fault - target connected? Error: Wire not connected サポートリクエスト 何かアドバイスをいただけますか: 基板がJ54から電源供給されているのに、 D4 LEDが消灯しているのはなぜですか? RT700プロセッサをリセット状態からどうやって解除 できますか? リセット、起動、またはハードウェア構成の確認が必要な項目はありますか? アプリケーションをフラッシュするためにLinkServerのコネクティビティを復元するには、どのような復旧手順を使えばよいでしょうか? 評価ボード Re: MIMXRT700-EVK Flashing Error こんにちは、@Aparna1 さん。 おそらく、電力がMCUや基板全体に適切に分配されておらず、搭載デバッガにだけ送られている可能性が高いです。 緑色のD10 LEDも消灯していますか? J2のジャンパー位置がピン7と8をショートさせていることを確認してください。 BR、 エドウィン。 Re: MIMXRT700-EVK Flashing Error これはUSB接続後の状態です Re: MIMXRT700-EVK Flashing Error こんにちは、 はい、以下の点を確認しました。 緑色のD10 LEDが点灯しています。 J2はピン7と8を短絡させている。 私の方で追加の確認が必要な場合はお知らせください。 よろしくお願いいたします。 アパルナ Re: MIMXRT700-EVK Flashing Error こんにちは、 チケットの状況を教えていただけますか?まだ返答を待っています。   よろしくお願いします。     Re: MIMXRT700-EVK Flashing Error こんにちは、 チケットの状況を教えていただけますか?まだ返答を待っています。   よろしくお願いします。   Re: MIMXRT700-EVK Flashing Error こんにちは、 チケットの状況を教えていただけますか?まだ返答を待っています。   よろしくお願いします。
記事全体を表示
iMX95 - EMMC Part confirmation Hi team, We have two alternate part suggestion for 128GB EMMC part. Can you please confirm we can use below parts with IMX95? BIWIN part - BWEFMA128GN9KC SANDISK part - SDINBDA6-128G-ZA Regards, Indrajith S Re: iMX95 - EMMC Part confirmation Hi @indrajith_shanmugam , For the emmc i.MX95 support the emmc 5.1, and do not have special need. Here you make the emmc datasheet fit for the need for the interface of the i.MX95 usdhc1  will be OK. Hope this can do help for you Any questions please contact me freely Wish you have a nice day Best Regards Rita
記事全体を表示
i.MX95 LPDDR4x READシミュレーションの合否判定基準 こんにちは、チームの皆さん。 プロセッサi.MX95の場合、LPDDR4x の読み取り タイミングマージンとシミュレーションの合格/失敗基準を設定できますか? オートモーティブ インダストリアル
記事全体を表示
Debug interface recommendations for Kinetis and LPC? I do most of my development on the Kinetis series, and potentially some LPC parts in the near future. I've got a drawer full of debug interfaces from P&E Micro, including a Cyclone ACP that I use most. I sometimes find myself switching from the $600 Cyclone to the $20 LPC-Link2 because the Cyclone has so many weird problems with MCUXpresso. Honestly the LPC-Link2 does most of what I need, it's just a bit slow. Should I be looking at Segger interfaces? Can someone recommend a reliable, reasonably fast interface that's well-supported in MCUXpresso (and hopefully CodeWarrior 11 as well) that doesn't cause crashes all of the time, or fail to halt a running target? Trace support would be nice. Thanks! Re: Debug interface recommendations for Kinetis and LPC? Hello @swetie42 , Thanks for your interest in NXP products.  For your use case, I would suggest taking a look at MCU-Link Pro Debug Probe. It works well with MCUXpresso IDE using the standard CMSIS-DAP firmware, and unlike the base MCU-Link, MCU-Link Pro also provides a J-Link LITE firmware option. Since CodeWarrior supports J-Link, this can be useful if you need to work with both MCUXpresso IDE and CodeWarrior on Kinetis devices. MCU-Link Pro also supports SWO profiling and provides additional features such as energy measurement and analog signal monitoring.   Of course, a SEGGER J-Link is also a good option if you prefer the SEGGER ecosystem or need more advanced debug/trace capabilities. The exact trace capability will depend on the probe model and the target device. For more details, I suggest you directly contact Segger support: Ticket | SEGGER - The Embedded Experts   So, in a word, I think MCU-Link Pro would be worth considering first.   Hope it helps.   BR Celeste
記事全体を表示
MIMXRT700-EVK Flashing Error Hi, I am unable to flash my application to the MIMXRT700-EVK using NXP LinkServer. Hardware/Software: Board: MIMXRT700-EVK MCU: MIMXRT798S Debugger: On-board MCU-Link MCU-Link firmware: V3.172 LinkServer: 26.6.137 OS: Ubuntu Linux Power is supplied through J54 During flashing, LinkServer reports: Error: Wire Ack Fault - target connected? Error: Wire not connected Failed on connect: Ee(42). Could not connect to core. No connection to chip's debug port Flash operation exited with code 1 The MCU-Link is detected correctly by the PC, and LinkServer can detect the probe. The important hardware observation is that the D4 red LED is not glowing. According to the MIMXRT700-EVK documentation, D4 indicates the MCU/reset status, where ON indicates normal processor activity and OFF indicates that the processor is in reset. I also executed the RT700 preconnect script, but the SWD connection still fails with: Error: Wire Ack Fault - target connected? Error: Wire not connected Support Request Could you please advise: Why is the D4 LED OFF when the board is powered through J54? How can I bring the RT700 processor out of the reset state? Is there any required reset, boot, or hardware configuration that needs to be checked? What recovery procedure should I use to restore LinkServer connectivity so that I can flash the application? Evaluation Board Re: MIMXRT700-EVK Flashing Error Hi @Aparna1, It's likely that the power is not being properly distributed to the MCU/rest of the board, but rather just to the on-board debugger. Is the green D10 LED also OFF? Please make sure that the jumper position of J2 is shorting pins 7 and 8. BR, Edwin. Re: MIMXRT700-EVK Flashing Error Hi, Yes, I have verified the following: The green D10 LED is ON. J2 is shorting pins 7 and 8 . Please let me know if any additional checks are required from my side. Regards, Aparna Re: MIMXRT700-EVK Flashing Error    This is the Status after connecting USB  Re: MIMXRT700-EVK Flashing Error Hi, could you please provide an update on my ticket? I am still waiting for a response.   Thank you.     Re: MIMXRT700-EVK Flashing Error Hi, could you please provide an update on my ticket? I am still waiting for a response.   Thank you.   Re: MIMXRT700-EVK Flashing Error Hi, could you please provide an update on my ticket? I am still waiting for a response.   Thank you.
記事全体を表示
S32K358 power supply design with MC33FS6523CAE (FS6500 SBC) Hello I’m designing with the S32K358 and plan to use the MC33FS6523CAE SBC. Is this a supported pairing, and which SBC outputs (VCORE, VCCA) do you recommend for VDD_HV_A/B, VREFH and V15, given the S32K3 internal SMPS?  Thanks https://www.nxp.com/products/FS6500?page=9&nrnd=false Re: S32K358 power supply design with MC33FS6523CAE (FS6500 SBC) Hello Sakshi, The MC33FS6523CAE is a compatible SBC for the S32K358. However, I would like to highlight that our recommended companion SBC for the S32K358 is the FS26, for the reasons outlined below. The FS26 is the purpose-designed safety SBC attach solution for the S32K3 series, including the S32K358. It offers a number of advantages specifically relevant to S32K358 designs: - Dedicated reference documentation: AN13850 (FS26 Implementation and Behaviors) includes an explicit section on FS26 connection to the S32K358.  -ASIL D functional safety coverage: The FS26 family is specifically developed and validated for ASIL D applications with S32K3, with a dedicated RTD software driver and safety application note combination ready for production use. - Higher current LDO outputs: FS26 LDO1 and LDO2 directly supply VDD_HV_A and VDD_HV_B to the S32K358. Our FRDM-A-S32K358 evaluation board uses the FS26 as the companion SBC, with LDO1 supplying VDD_HV_A (+3.3 V) and LDO2 supplying VDD_HV_B (+3.3 V). - Ready-made software: A production-ready RTD package for S32K3 + FS26 is available, significantly reducing software development effort. The MC33FS6523CAE is still a supported and functional SBC choice for S32K358 if you require integrated CAN FD + LIN transceivers in a single SBC package. BRs, Tomas
記事全体を表示
iMX95 - EMMC部品確認 チームの皆さん、こんにちは。 128GBのeMMC部品については、代替部品を2つご提案できます。以下の部品をIMX95で使えるか確認していただけますか? BIWIN部品番号 - BWEFMA128GN9KC サンディスク部品 - SDINBDA6-128G-ZA よろしくお願いいたします。 インドラジットS Re: iMX95 - EMMC Part confirmation こんにちは、 @indrajith_shanmugam さん。 emmc i.MX95はemmc 5.1をサポートしており、特別な必要性はありません。 ここでは、iのインターフェースのニーズに合ったemmcのデータシートを作ってください。MX95のusdhc1は問題ありません。 これがあなたの役に立てば幸いです ご質問があれば、どうぞお気軽にお問い合わせください 素敵な一日をお過ごしください よろしくお願いいたします。 リタ
記事全体を表示
Query Regarding OTP Programming of FS2643D Blank OTP Variant Hi, I am planning to use the FS2643D variant, specifically the MFS2643HMDA0AD blank OTP variant, for my 24 V application. I understand that the KITFS26SKTEVM socket board can be used for OTP configuration and programming. However, using the socket board may complicate the workflow, as the IC needs to be placed in the socket for programming and then soldered onto the target PCB. Is there an alternative method to configure and program the OTP directly on the target PCB using an external programmer or target board, without requiring the KITFS26SKTEVM socket board? Could you please advise whether this approach is supported and recommend a suitable solution? https://www.nxp.com/part/MFS2643HMDA0AD Thanks. Re: Query Regarding OTP Programming of FS2643D Blank OTP Variant Hi Sakshi, for prototyping, using the socket board, our other hardware and the NXP Ringo GUI is recommended for benchmarking. For designing your prototype board, please follow the FS26 datasheet and our other documents. Especially the AN12995.  To be able to download these confidential documents, you need to have a valid NDA with NXP. If you have not an NDA yet and you would like to sign one, please create a new ticket here and an NXP representative for NDA matters will help you with the process.  Without the FS26 datasheet and other confidential documents would not be possible to work with the FS26. Once you will have your prototype schematic, we can check it for you. Please note, we do not check layouts. Alternatively you can contact our authorized distributors, they have engineers who can also check the schematic for you. With Best Regards, Jozef Re: Query Regarding OTP Programming of FS2643D Blank OTP Variant Hi Jozef, Thank you for the feedback. Since we are currently in the prototyping phase, our initial volume count is low, and we are focused strictly on bench evaluation and system validation. Given that this is a low-volume prototype phase, could you let us know how you recommend we proceed for our initial boards? Do you recommend we work with an authorized distributor (such as Arrow or Avnet) to get a small batch programmed, or is there an alternative path you suggest for early benchmarking? We want to ensure we align with NXP’s safety and validation guidelines while we bring up our custom target prototype. Best regards, Re: Query Regarding OTP Programming of FS2643D Blank OTP Variant Hi Sakshi, please note, that our evaluation boards and socket boards are designed and recommended to be used for evaluation of our components only. OTP programming of our components are allowed only by NXP or by our authorized distributors. Depending on annual volume of the specific component. Please let me know your annual volume for your project using the FS2643D Blank OTP Variant. We do not allow to program the OTP of our components by our customers. If customers will program themselves, then we do not guarantee safe and correct function of such components.  With Best Regards, Jozef
記事全体を表示
Kinetis 和 LPC 的调试接口有什么建议? 我目前主要从事 Kinetis 系列芯片的开发工作,未来可能还会开发一些 LPC 芯片。我抽屉里装满了 P&E Micro 的调试接口,其中最常用的是 Cyclone ACP。 我有时会发现自己从 600 美元的 Cyclone 换成了 20 美元的 LPC-Link2,因为 Cyclone 与 MCUXpresso 存在很多奇怪的问题。说实话,LPC-Link2 基本能满足我的需求,只是速度有点慢。 我应该考虑使用Segger接口吗?请问有人可以推荐一款可靠、速度适中、在 MCUXpresso(最好也能在 CodeWarrior 11)中支持良好的接口吗?这款接口不会经常导致程序崩溃,也不会无法停止正在运行的目标。如果能支持追踪功能就更好了。 谢谢您! Re: Debug interface recommendations for Kinetis and LPC? 你好@swetie42 , 感谢您对恩智浦产品的关注。 针对您的使用场景,我建议您了解一下MCU-Link Pro Debug Probe。 它与使用标准 CMSIS-DAP 固件的 MCUXpresso IDE 配合良好,而且与基础版 MCU-Link 不同的是,MCU-Link Pro 还提供J-Link LITE 固件选项。由于 CodeWarrior 支持 J-Link,因此如果您需要在 Kinetis 设备上同时使用 MCUXpresso IDE 和 CodeWarrior,这将非常有用。 MCU-Link Pro 还支持 SWO 我的,并提供能量测量和模拟信号监控等附加功能。   当然,如果您更喜欢 SEGGER 生态系统或需要更高级的调试/跟踪功能,SEGGER J-Link 也是一个不错的选择。具体的追踪能力取决于探头型号和目标设备。如需了解更多详情,建议您直接联系 Segger 支持:提交工单 | SEGGER - 嵌入式专家   总之,我认为MCU-Link Pro值得优先考虑。   希望对您有所帮助。   BR 塞莱斯特
記事全体を表示
FS2643DブランクOTPバリアントのOTPプログラミングに関する問い合わせ こんにちは、 私は24V用途にFS2643Dバリアント、特にMFS2643HMDA0ADブランクOTPバリアントを使う予定です。 KITFS26SKTEVMソケットボードはOTPの設定やプログラミングに使えると理解しています。しかし、ソケットボードを使用すると、ICをプログラミングのためにソケットに挿入し、その後ターゲットのPCBにはんだ付けする必要があるため、ワークフローが複雑になる可能性があります。 外部プログラマーやターゲットボードを使って、KITFS26SKTEVMソケットボードを必要とせずに、OTPを直接ターゲットPCB上で設定・プログラムする代替方法はありますか? この方法が支持されているか、また適切な解決策を提案していただけますか? https://www.nxp.com/part/MFS2643HMDA0AD ありがとうございます。 Re: Query Regarding OTP Programming of FS2643D Blank OTP Variant こんにちは、サクシさん。 プロトタイプ作成には、ソケットボード、その他のハードウェア、およびNXP Ringo GUIを使用したベンチマークテストをお勧めします。試作基板の設計にあたっては、FS26のデータシートおよびその他の関連資料をご参照ください。特にAN12995。 これらの機密文書をダウンロードするには、NXPとの有効な秘密保持契約(NDA)が必要です。まだNDAを持っていなければ、署名を希望される場合は 、こちらから 新しいチケットを作成してください。NDAマターに関するNXP担当者が手続きをサポートします。 FS26のデータシートやその他の機密文書がなければ、FS26を扱うことは不可能です。 試作設計図が手に入ったら、私たちが確認します。レイアウトの確認は行っておりませんので、ご了承ください。あるいは、当社の正規代理店にご連絡いただければ、エンジニアが回路図のチェックも可能です。 敬具、 ヨゼフ Re: Query Regarding OTP Programming of FS2643D Blank OTP Variant こんにちは、ヨゼフさん。 ご意見ありがとうございます。現在プロトタイプ開発段階にあるため、初期の生産量は少なく、ベンチテストとシステム検証に重点的に取り組んでいます。 これは低生産量のプロトタイプ段階であることを踏まえ、初期のボード制作をどのように進めるべきか教えていただけますか?ArrowやAvnetなどの正規販売代理店と協力して小規模なバッチをプログラムすることを勧めますか?それとも早期ベンチマークの代替ルートを提案しますか? カスタムターゲットプロトタイプを提出する際には、NXPのセーフティおよび検証ガイドラインに準拠していることを確認したいと考えています。 よろしくお願いします、 Re: Query Regarding OTP Programming of FS2643D Blank OTP Variant こんにちは、サクシさん。 当社の評価ボードおよびソケットボードは、当社の部品評価のみを目的として設計・推奨されていますのでご注意ください。当社のコンポーネントのOTPプログラミングは、NXPまたは 当社の認可代理店のみが許可しています。特定の部品の年間生産量によって異なります。FS2643DブランクOTPバリアントを使用したプロジェクトの年間生産量をお知らせください。 当社はお客様がコンポーネントのOTPをプログラムすることを許可していません。お客様が自分でプログラムする場合、そのような部品の安全かつ正しい動作を保証するものではありません。 敬具、 ヨゼフ
記事全体を表示
SPI NAND boot on i.MX8ULP SPI NAND boot on i.MX8ULP This article is about the SPI NAND boot on the i.MX8ULP, some customers using the i.MX8ULP want to use the SPI NAND on it. We just have verified the NOR NAND on the i.MX8ULP EVK board, for the SPI NAND use customers do not clear and do not know how to realized, here will give details steps and modifications for customers to refer to. 1\The boot mode support on the i.MX8ULP For the i.MX8ULP support many kinds of external memory devices SD, eMMC, SPI NOR and Flash SPI NAND Flash. Compared to traditional parallel NAND (which requires GPMI/NFC controllers), SPI NAND can be accessed through a serial FlexSPI interface. For the i.MX8ULP for the SPI NAND use need to connect to the FlexSPI2 interface. 2\ Hardware SPI NAND boot configuration On the i.MX8ULP the SPI NAND is mounted on the FlexSPI2 interface, the configuration need to follow the section in the RM. Boot configuration needs to follow the Table 84. Boot configuration. In our reference design use the NOR SPI flash, for the SPI NAND connection can refer to it. 3\Software realized for the SPI NAND boot on the i.MX8ULP Make sure the hardware connections are proper. Next step is to boot up. On our 8ULP EVK board I have confirmed that do not have the SPI NAND on it. The default u-boot and the imx-mkimage flash_singleboot_m33_flexspi is for the SPI NOR, not for the SPI NAND, for the SPI NAND is using the different mechanism with SPI NOR, so if customer use ROM code read it fail, in our default released BSP do not include the build images for the 8ULP SPI NAND https://github.com/nxp-imx/imx-mkimage/blob/lf-6.18.20_2.0.0/iMX8ULP/soc.mak. So it need the special build images, and realized by customer themselves. For the i.MX8ULP ROM code already confirm that support the SPI NAND boot, so in customer’s side they need to porting in their side to support it. The SPI NAND boot mechanism for the i.MX8ULP is the same as that of the i.MX91, so we can refer to the i.MX91 design. For support the SPI NAND boot, the actual project needs to supplement U-Boot, imx mkimage, FCDBBT, download, and Linux support for related NAND part numbers. The core of SPI NAND boot is not a single binary image, but a set of data structures for ROM to identify media, bad blocks, and boot image locations. The key structures as FCB, DBBT, and Image Container. 3.1 U-boot modify Add the NAND related information and parameters in the driver: Take the Winbond NAND as an example, https://github.com/nxp-imx/uboot-imx/blob/lf-6.18.20-2.0.0/drivers/mtd/nand/spi/winbond.c Add customized header support for SPI NAND boot in the cmd_fspinand.c (Added customized FlexSPI NAND header support: allowing different configurations to be generated for different NAND models.) https://github.com/nxp-imx/uboot-imx/blob/lf_v2026.04/arch/arm/mach-imx/cmd_fspinand.c 3.2 Add the SPI NAND support in the imx-mkimage imx-mkimage is a boot image generation tool provided by NXP, used to package multiple boot components such as U-Boot, ATF, OP-TEE, DDR firmware, ELE,SECO firmware into the final boot image (flash.bin). imx-mkimage generates the Container Images that meet Boot ROM requirements. The default code: https://github.com/nxp-imx/imx-mkimage/tree/lf-6.18.20_2.0.0/iMX8ULP Need to add the related information for the SPI NAND support refer to the i.MX91:https://github.com/nxp-imx/imx-mkimage/tree/lf-6.18.20_2.0.0/iMX91 Generate the flash_fw.bin and flash.bin . flash_fw.bin is a temporary boot image used by the UUU tool during SPI NAND programming. flash.bin is the Boot image programmed into the SPI NAND flash. The write the boot images to UUU command is: uuu -b spinand flash_fw.bin flash.bin 3.3 Kernel modify For the kernel need to add the driver and spi-nand node in the board device tree. Add the NAND related information and parameters in the driver like u-boot. Configure FLEXSPI2 and add the SPI NAND Flash node in the board Device Tree (DTS): Build the source code, test on the customer’s board. 4\ Trouble shooting a.Need to check the hardware design is proper, check the connection and pins mux. b.Confirm the i.MX8ULP if validation the 4KB SPI NAND Page size. For the page_data_size and page_total_size 2K      config->pageDataSize = 2048;     config->pageTotalSize = 4096; 4K     config->pageDataSize = 4096; config->pageTotalSize = 8192; Confirm if configuration the FCB to 4KB page size or still 2K. At firstly in the 91 RM we can see that there is BOOT_CFG0[7] FlexSPI_NAND_4K_Page_Selection, no describe for the i.MX8ULP. We thought need special configuration for the i.MX8ULP. But for the i.MX8ULP do not use this BOOT_CFG0[7] FlexSPI_NAND_4K_Page_Selection. And in the default ROM Code support 2K and 4K, details can see in the ROM document . c. The FCB, DBBT, flash.bin, and all contained boot images are 4 KB aligned to match the SPI NAND page size requirement.  Make sure already confirm the FCB configure to 4KB page size. If not 4KB aligned will all met fail boot. d. uboot/arch/arm/mach-imx/cmd_fspinand.c The original code use the fspinand_prep_micron_mem_config() configure NAND's in-die ECC using a semi-hardcoded approach, then write to the SR2 register, this method will cover other key configuration bits in the Winbond W25N04L series SR2. Firstly ask customer to commit out the function of the “fspinand_prep_micron_mem_config()” to see if can pass the fail. (Commenting out the fspinand_prep_micron_mem_config() function in uboot: arch/arm/mach-imx/cmd_fspinand.c will be quick way(not a solution) to verify if this causes the boot failure.) After annotation, the spi nand can start normally, but this is only a verification method and not the final solution. Then customer try to modify the value configuration for the SR2 from 0x10 to 0x19: - config->mem_config.configCmdArgs[1] = 0x10; + config->mem_config.configCmdArgs[1] = 0x19; This works well in customer’s side. But fixed the SR2 value not suit for all customer’s situation using other vendors’ chip. NXP do not use the hard code, because this may affect other NAND customers and instead increase the customized flexspi_nand_config header support. Using the attached U-Boot and mkimage tool patches to generate the required custom header for the target SPI NAND device. Note: Please use our official patches (Already merged in NXP 2026 Q3 release) to address this issue. We have introduced support for customized flexspi_nand_config headers. Please use the attached U-Boot and mkimage tool patches to generate the required custom header for the target SPI NAND device. Please note that the changes in our mkimage patch are based on the SPI NAND implementation for the NXP release of the i.MX91 platform. Please make the corresponding modifications according to the platform you are using. If you are using the Linux 6.18.37_2.1.0 our newest released BSP, we already apply this patch.  Just make porting SPI Nand boot according the i.MX91 section code to finish. If you are using the before released version, the following two patches are needed. 0001-iMX91-soc.mak-add-flash_singleboot_spinand_customhdr.patch.txt 0001-LFU-1037-cmd_fspinand-add-customized-header-support-.patch.txt
記事全体を表示
Using the HiFi DSP for Inferencing ML Models on i.MX RT Devices This article will describe how to use the HiFi modules found on certain NXP microcontrollers as an optional method for inferencing a model.  There are several ways of running a TFLite neural network model on NXP microcontrollers: Inference a model only using the main core of the device (CM33 or M7) MCX N i.MX RT1050 i.MX RT1060 i.MX RT1170 i.MX RT1180 i.MX RT595 i.MX RT685 i.MX RT700 Inference a model directly on the HiFi4 or HiFi1 core (on supported platforms) i.MX RT595 i.MX RT685 i.MX RT700 Use the Neutron NPU to accelerate inference of a model - with the CM33 controlling the NPU and acting as a fallback for any non-NPU supported layers i.MX RT700 MCX N Use the Neutron NPU to accelerate inference of a model - with the HiFi4 controlling the NPU and acting as a fallback for any non-NPU supported layers i.MX RT700   This article will cover options #2 and #4 which make use of the HiFi DSP module. Running a model on the HiFi4 (option #2) will be much faster than running a model just on the CM33/M7 (option #1). However using the NPU (options #3 and #4) will be significantly faster than only using the DSP due to the hardware optimizations that an NPU provides for neural network calculations. The exact performance gains will be model specific, and also depend on the layer(s) that may not have been converted to use the NPU as NeutronGraph nodes. The accuracy should remain the very similar regardless of method being used. Any type of TFLite neural network model can be ran on the HiFi1/HiFi4 as those DSP modules are just being used accelerate the neural network math that the model uses. Below are the inference times of a CIFAR10 model on i.MX RT700 with different hardware modules used to inference the model (using default MCUXpresso SDK projects).  CM33: 103.653ms HiFi1*: 19.007ms HiFi4: 12.312ms NPU w/ CM33 Fallback: 0.883ms NPU w/ HiFi4 Fallback: 0.883ms *HiFi1 max frequency is 250MHz. All others are run at 325MHz.   Software requirements: Go to the Cadence i.MX RT700 or Cadence i.MX RT685 pages to download the following software. Xtensa Xplorer IDE License Key HIFI DSP Configuration File (NEWLIB) If using a HiFi4 example then download the HiFi4 license and DSP configuration files. Likewise, if using a HiFi1, then will need the HiFi1 license and DSP configuration files. Also you will need to download the Windows or Linux version of these files depending on which host OS you are using on your PC. Finally add the following global system variables which should be set based on the location that Xtensa Explorer was installed (assuming RT700 with HiFi4): XCC_DIR= \XtDevTools\install\tools\RI-2023.11-win32\XtensaTools XTENSA_CORE= rt700_hifi4_RI23_11_nlib MCUXpresso SDK HiFi ML Examples: There are several HiFi related examples in MCUXpresso SDK for i.MX RT700: tflm_cifar10 – Uses Neutron NPU to inference the CIFAR10 model and uses the CM33 as the fallback for any non-NPU operators. tflm_cifar10_hifi1 – Uses HiFi1 to inference the CIFAR10 model. Does not use the Neutron NPU tflm_cifar10_hifi4 – Uses HiFi4 to inference the CIFAR10 model. Does not use the Neutron NPU tflm_cifar10_hifi4_neutron – Uses Neutron NPU to inference the CIFAR10 model and uses the HiFi4 as the fallback for any non-NPU operators. tflm_label_image – Uses Neutron NPU to inference the CIFAR10 model and uses the CM33 as the fallback for any non-NPU operators. tflm_label_image_hifi4 - Uses HiFi4 to inference the Mobilenet model. Does not use the Neutron NPU When using the HiFi eIQ projects provided in MCUXpresso SDK, ensure that the SDK is: Located in a short filename path (ie C:\nxp\RT700), as an excessively long filename path can cause compile issues Directory path contains no spaces If using VS Code import as a Repository project instead of Free Standing. Ensure using at least MCUXPresso SDK 26.09 as there are several important fixes in the 26.09 release for HiFi4 projects HiFi4 with Neutron: If using the cifar10_hifi_neutron example and you want to change the model, then the model needs to be converted using the --target imxrt700 option for Neutron Compiler. The Neutron libraries then need to be updated using the files in the \target\imxrt700\rt700\hifi4\RJ-2025.5 folder and copied into mcuxsdk\middleware\eiq\neutron\rt700\hifi4 The Neutron libraries in the hifi\RI-2021.6 folder are provided to provide compatibility with an older version of the Xtensa tools and are not recommended for new designs. Extending Memory Area in HiFi4 Examples for Larger Models: Open:  Github SDK Layout: \mcuxsdk\examples\_boards\mimxrt700evk\eiq_examples\tflm_cifar10_hifi4_neutron\linker\hifi4\gdbio\ldscripts\elf32xtensa.x Classic SDK Layout: \boards\mimxrt700evk\eiq_examples\tflm_cifar10_hifi4_neutron\linker\hifi4\min-rt\ldscripts\elf32xtensa.x  And make modifications below to extend the memory used for models.  dsp_core_seg :  org = 0x20200000, len = 0x200000  dsp_core_ncache_seg :  org = 0x20400000, len = 0x180000    _memmap_mem_dsp_core_start = 0x20200000;  _memmap_mem_dsp_core_end   = 0x20580000;  _memmap_seg_dsp_core_start = 0x20200000;  _memmap_seg_dsp_core_max   = 0x20580000;     Ensure that the stack heap is at 0x2058_0000:    PROVIDE(__stack = 0x20580000);    _heap_sentry = 0x20580000;      Now larger models will compile successfully in Xtensa.    Then after copying in the compiled HiFi4 binary files into the MCUXpresso IDE project, modify dsp_config.h file to update the DSP_SRAM_ADDRESS:  Github SDK Layout: \mcuxsdk\examples\_boards\mimxrt700evk\eiq_examples\tflm_cifar10_hifi4_neutron\dsp_config.h  Classic SDK Layout:  \boards\mimxrt700evk\eiq_examples\tflm_cifar10_hifi4_neutron\cm33_core0\dsp_config.h (or source\dsp_config.h in MCUXpresso IDE)  Then clean and build the project.  Mlongcalls (MCUXpresso SDK 26.06 or earlier): In older MCUXpresso SDK versions there was a compiler issue where -mlongcalls needs to be used to avoid issues when adding additional operators to the operators list. This modification is no longer needed in MCUXpresso SDK 26.09 or later.  Inside \mcuxsdk\examples\_boards\mimxrt700evk\eiq_examples\tflm_cifar10_hifi4\hifi4 edit the reconfig.cmake file in the mcux_add_xtensa_configuration options: mcux_add_xtensa_configuration( CC "-DXOS_CLOCK_FREQ=237500000 -std=c99 -mlongcalls" CX "-stdlib=libc++ \ -mlongcalls \ -std=c++17" )  HiFi Lab: See the attached lab document for more details on using the HiFi DSP modules to inference models.    
記事全体を表示
すべての例:MCAL S32K312 DS3.5 RTD-3.0.0  ------------------------------------------------------------------------------ * テスト用ハードウェア:S32K3X4EVB-Q172 * MCU:S32K312 * コンパイラ: S32DS3.5 * SDKリリース:RTD 3.0.0 * デバッガ:PE Micro * ターゲット:internal_FLASH ******************************************************************************** 例:MCAL S32K312 MEM_InFls DS3.5 RTD300 例:MCAL S32K312 MEM_InFls DS3.5 RTD300 - NXPコミュニティ 例:MCAL S32K312 FEE DS3.5 RTD300:-- 例:MCAL S32K312 FEE DS3.5 RTD300 - NXPコミュニティ 例:MCAL S32K312 FEEとMEM_InFls DS3.5 RTD300:-- 例:MCAL S32K312 FEEとMEM_InFls DS3.5 RTD300 - NXPコミュニティ 例:MCAL S32K312 PWM ICU、カスタムIRQ EMIOS DS3.5 RTD300を使用:-- 例:MCAL S32K312 PWM ICU、EMIOS DS3.5 RTD300を使用 - NXPコミュニティ 例:ASR S32K312 EMIO PWM Generation & Dutyキャプチャ、Interrupt DS3.5 RTD300を使用:-- 例:ASR S32K312 EMIO PWM Generation & Dutyキャプチャ、Interrupt DS3.5 RTD300を使用 - NXPコミュニティ  例:ASR S32K312 EMIO PWM Generation & Dutyキャプチャ、Polling DS3.5 RTD300を使用:-- 例:ASR S32K312 EMIO PWM Generation & Dutyキャプチャ、Polling DS3.5 RTD300を使用 - NXPコミュニティ
記事全体を表示
所有示例 MCAL S32K312 DS3.5 RTD-3.0.0 ------------------------------------------------------------------------------ * 测试硬件:S32K3X4EVB-Q172 * MCU:S32K312 * 编译器:S32DS3.5 * SDK 发布:RTD 3.0.0 * 调试器:PE Micro * 目标:internal_FLASH ******************************************************************************** 示例 MCAL S32K312 MEM_InFls DS3.5 RTD300:-- 示例 MCAL S32K312 MEM_InFls DS3.5 RTD300 - NXP 社区 示例 MCAL S32K312 FEE DS3.5 RTD300:-- 示例 MCAL S32K312 FEE DS3.5 RTD300 - NXP 社区 示例 MCAL S32K312 FEE 和 MEM_InFls DS3.5 RTD300:-- 示例 MCAL S32K312 FEE 和 MEM_InFls DS3.5 RTD300 - NXP 社区 MCAL S32K312 PWM ICU 使用自定义 IRQ EMIOS DS3.5 RTD300 的示例:-- MCAL S32K312 PWM ICU 使用 EMIOS DS3.5 RTD300 的示例 - NXP 社区 示例 ASR S32K312 EMIO PWM 生成与占空比捕获使用中断 DS3.5 RTD300 :-- 示例 ASR S32K312 EMIO PWM 生成与占空比捕获使用中断 DS3.5 RTD300 - NXP 社区  示例 ASR S32K312 EMIO PWM 生成与占空比捕获使用轮询 DS3.5 RTD300 :-- 示例 ASR S32K312 EMIO PWM 生成与占空比捕获使用轮询 DS3.5 RTD300 - NXP 社区 回复:所有示例 MCAL S32K312 DS3.5 RTD-3.0.0 Pe Micro 调试工具在每次重新烧录固件时都会擦除 DataFlash,导致 EEPROM 数据损坏。 在调试配置中完成以下修改后,问题得以解决。
記事全体を表示
All Example MCAL S32K312 DS3.5 RTD-3.0.0  ------------------------------------------------------------------------------ * Test HW: S32K3X4EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE Micro * Target: internal_FLASH ******************************************************************************** Example MCAL S32K312 MEM_InFls  DS3.5 RTD300 :-- Example MCAL S32K312 MEM_InFls DS3.5 RTD300 - NXP Community Example MCAL S32K312 FEE DS3.5 RTD300 :-- Example MCAL S32K312 FEE DS3.5 RTD300 - NXP Community Example MCAL S32K312 FEE and MEM_InFls DS3.5 RTD300 :-- Example MCAL S32K312 FEE and MEM_InFls DS3.5 RTD300 - NXP Community Example MCAL S32K312 PWM ICU using Custom IRQ EMIOS DS3.5 RTD300 :-- Example MCAL S32K312 PWM ICU using EMIOS DS3.5 RTD300 - NXP Community Example ASR S32K312 EMIO PWM Generation & Duty capture using Interrupt DS3.5 RTD300 :-- Example ASR S32K312 EMIO PWM Generation & Duty capture using Interrupt DS3.5 RTD300 - NXP Community  Example ASR S32K312 EMIO PWM Generation & Duty capture using Polling DS3.5 RTD300 :-- Example ASR S32K312 EMIO PWM Generation & Duty capture using Polling DS3.5 RTD300 - NXP Community Example MCAL S32K312 PIT ADC BTCU DS3.5 RTD300 :-- https://community.nxp.com/t5/S32K-Knowledge-Base/Example-MCAL-S32K312-PIT-ADC-BTCU-DS3-5-RTD300/ta-p/2424542 Re: All Example MCAL S32K312 DS3.5 RTD-3.0.0 Pe Micro use to delete the Dataflash, on every new FLashing of firmware, which corrupts the EEPROM data. After making this changes in debug configuration it worked..
記事全体を表示
PN7642EV/C100 与 PN7642EV/C102 第一个问题,我计划在新设计中使用PN7642EV/C102。我想添加PN7642EV/C100作为备选方案,因为它在主流代理商处有现货,可以减少潜在的长期供应链问题。在我看来,这两个PN7642EV/C100之间的唯一区别在于它们出厂时预装的固件版本。如果真是这样,那么安装PN7642EV/C100并更新到最新固件就相当于安装PN7642EV/C102并更新到最新固件。我的理解是否正确? 第二个问题,对于此应用,我们将读取基本的 NFC 标签、Google 钱包和 Apple 钱包。我知道读取 Google 和 Apple 钱包需要很多认证和权限,但就硬件而言,C100 和 C102 型号是否能够做到这一点? Re: PN7642EV/C100 vs PN7642EV/C102 你好@adamdoyle15 希望你一切都好。 PN7642 应具备 ECP 功能。另外,正如您所提到的,这些版本之间的主要区别在于C102出厂时预装了固件版本3.00。 问候, 爱德华多。 Re: PN7642EV/C100 vs PN7642EV/C102 您好, ECP 支持主要通过软件实现;硬件版本之间不应有区别。 问候, 爱德华多。 Re: PN7642EV/C100 vs PN7642EV/C102 感谢您的快速回复。 关于 ECP 功能,我从数据表中看到 PN7642 具备 ECP 功能,但我的问题是,从硬件角度来看,这是否足以兼容苹果钱包。
記事全体を表示