Replacement issue of FS32K144UAT0VLLT and FS32K144HAT0MLLT manager: We are currently using your FS32K144UAT0VLLT, 112MHz, LQFP-100, with an operating temperature range of -40°C to 105°C. The design is for a gasoline engine ECU for automobiles, and the goal is to replace it with an automotive-grade one. The current selection is FS32K144HAT0MLLT, LQFP-100, 80MHZ, LQFP100, with an operating temperature of -40°C to 125°C. Excuse me: 1. Can the two microcontrollers be interchanged pin-to-pin? Only their clock speeds and operating temperatures differ? 2. Are there any microcontrollers that can be pin-to-pin replaced with the FS32K144UAT0VLLT, with a main frequency of 112kHz and automotive grade? Please send the model number, thank you! 3. In FS32K144HAT0MLLT, does A represent CAN FD, FlexIO, or Security? What is the difference between FS32K144HFT0MLLR, where F represents CAN FD and FlexIO? What do CAN FD, FlexIO, and Security mean? 4. We purchase from websites like Taobao, but we're concerned about the legitimacy of these channels. Could you please send us a link to the NXP microcontroller distributor in North China or their contact information? Thank you! Re: FS32K144UAT0VLLT和FS32K144HAT0MLLT替换问题 Hi@ YF666666 Senlent_0-1789959640629.png 1. Can the two microcontrollers be interchanged pin-to-pin? Only their clock speeds and operating temperatures differ? Yes 2. Are there any microcontrollers that can be pin-to-pin replaced with the FS32K144UAT0VLLT, with a main frequency of 112kHz and automotive grade? Please send the model number, thank you! Pin-to-pin connectors can only be from the same series. For example, some models of S32K144 or S32K146 have the same pins and package. You can find it in the attachment based on the ordering information above. 3. In FS32K144HAT0MLLT, does A represent CAN FD, FlexIO, or Security? What is the difference between FS32K144HFT0MLLR, where F represents CAN FD and FlexIO? What do CAN FD, FlexIO, and Security mean? Yes, there is no difference, except that F does not support Security, meaning this chip does not support the CSE module. It supports CAN FD, FLEXIO module, and Security (CSEc engine). 4. Information about Distributors: You can find information on all our distributor partners in China at the link below. You can choose any distributor: https://www.nxp.com/support/sample-and-buy/distributor-network:DISTRIBUTORS#CHINA

a replacement product for MCF51JE256 I would like to ask for your recommendation on an MCU chip that meets the following requirements: 32-bit data bus/transfer Program memory space of 1 MByte or larger Integrated with at least one I2C bus controller Integrated with at least two SPI bus controllers At least six or more A/D analog-to-digital conversion channels Integrated with at least a 3×3 matrix keyboard controller Integrated with at least two or more timers Integrated with TOD (Time-of-Day) timer interrupts and other external interrupts Integrated with a USB interface controller That is all — thank you for your help. We hope to find a chip that can replace the functionality of the MCF51JE256, which is our current chip. If you'd like, I can also help you search for specific MCU recommendations that match these requirements. Analog(ADC|CMP|DAC|OpAmps) Audio(PDM | I2S | SAI) Communication & Control(I3C | I2C | SPI | FlexCAN | Ethernet | FlexIO) Re: a replacement product for MCF51JE256 Hello @ly_12_31  I recommend considering the MCXA or MCXN series, as they are NXP's latest mainstream MCU families and are actively promoted for new designs. These devices can meet all of your requirements except for the dedicated 3×3 matrix keyboard controller. However, this functionality can be implemented using GPIOs in software. MCX A13 A14x MCX A15x Arm Cortex-M33- Low Power and Intelligent Peripherals | NXP Semiconductors MCX N94, N54, N53, N52 and N24 MCUs | NXP Semiconductors  Thank you. BR Alice 回复： a replacement product for MCF51JE256 Dear Alice, Thank you for your reply, and thank you for the alternative chip solutions your company previously recommended — they have been very helpful to our evaluation. At present, our company is assessing the feasibility of alternative chips from multiple perspectives, and the specific solution is still under further review and confirmation. Once the plan is finalized, we will communicate with you in a timely manner and look forward to advancing the next steps of cooperation with your company. Thank you again for your support and assistance!   Best regards, Liu Ying

i.MX8M Plus 上的 U-Boot 进行 SWUpdate A/B OTA 更新 您好，NXP团队： 我正在使用以下方法在i.MX8M Plus LPDDR4 EVK上实现 OTA： 约克托·沃诺斯 Linux 6.18.20 U-Boot 2026.04 SWUpdate 2026.05.1 当前进展 SWUpdate 已成功集成到 Yocto 中。 已成功生成 .swu 文件代码包，软件包. SWUpdate软件包安装正常。 硬件兼容性检查正在进行中。 使用 SWUpdate 成功更新了 /etc/ota-version。 原始文件处理程序正在运行。 现在我想实现生产级别的 A/B OTA，具备自动回滚和签名更新功能。 问题 请问NXP推荐的以下解决方案是什么？ A/B 根文件系统分区布局。 基于 U-Boot 启动计数/启动限制的回滚。 SWUpdate 与 U-Boot 环境集成。 更正 fw_env.config / libubootenv 配置。 签名 .swu包裹核实。 防回滚/版本保护。 安全启动 + 软件更新集成。 目前，OTA 更新已完成，但 SWUpdate 报告： Cannot initialize environment from /etc/fw_env.config Cannot persistently store update state NXP是否有关于i.MX8M Plus上SWUpdate + A/B + U-Boot回滚 + 签名OTA的参考设计、应用笔记或示例？ 谢谢。 i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Yocto Project Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus 你好， 我们不提供开箱即用的标准 EVK A/B 更新框架。A/B 更新、回滚策略和断电故障保护启动选择是系统级功能，您必须使用 U-Boot + SWUpdate 来实现。最接近的参考文献有： AN12900 - 使用 CAAM 和 Mender 或 SWUpdate 的 Linux 安全 OTA 原型。 AN13872 - 启用 SWUpdate。 meta-swupdate-imx - 带有 SWUpdate 的 NXP Yocto 层。 顺祝商祺！ Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus 嘿vp1 ， 虽然我没有确切的答案，但我希望您知道 Torizon 现在支持任何 i。MX SoC。它已在全球许多关键的 i.MX8MPlus 产品中部署（主要在 Toradex 系统模块上）。它确实具有高度可靠的OTA升级功能（默认是OSTree，但可以更改）。 它包含开箱即用的安全启动、防回滚、漏洞管理（符合欧盟 CRA 标准）等功能。 该操作系统是免费开源的；如果您需要帮助，我们很乐意提供帮助。如果您想在 i.MX8M Plus LPDDR4 EVK 或您自己的硬件上进行尝试，请联系我们。 www.torizon.io 不好意思打个广告，我在Torizon工作，觉得这个话题可能跟我相关。 Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus 感谢你提供的信息。 我想就我们 i.MX 8M Plus evk 的推荐 OTA 架构获得一些指导。 对于我们的 i.MX 8M Plus evk，我们需要一个安全的 OTA 解决方案，该方案需具备以下功能： A/B 或故障保护更新 已签名/已认证的OTA代码包，软件包 安全启动集成 防回滚 更新失败/断电后自动恢复 关键轮换/撤销 设备身份/配置的保存 工厂恢复和更新日志 针对这些要求，请问对于 i.MX 8M Plus evk，推荐采用哪种方法？ 具体来说，我们应该继续采用本帖中讨论的 U-Boot + A/B + SWUpdate 方法，还是您会推荐其他解决方案，例如RAUC、Mender 或 NXP 支持的 OTA 架构？

MCF51JE256 的替代产品 我想请您推荐一款符合以下要求的MCU芯片：32位数据总线/传输；1MB或更大的程序存储空间；集成至少一个I2C总线控制器；集成至少两个SPI总线控制器；至少六个或更多A/D模数转换通道；集成至少一个3×3矩阵键盘控制器；集成至少两个定时器；集成TOD（时间）定时器中断和其他外部中断；集成USB接口控制器。以上就是全部要求——谢谢您的帮助。我们希望找到一款能够替代我们目前使用的芯片 MCF51JE256 功能的芯片。如果您需要，我还可以帮助您寻找符合这些要求的特定MCU推荐产品。 模拟（ADC|CMP|DAC|运算放大器） 音频（PDM | I2S | SAI） 通信与控制（I3C | I2C | SPI | FlexCAN | 以太网 | FlexIO） Re: a replacement product for MCF51JE256 你好@ly_12_31 我建议考虑MCXA或MCXN系列，因为它们是恩智浦最新的主流MCU系列，并且正在积极推广用于新设计。 除了专用的 3×3 矩阵键盘控制器之外，这些设备可以满足您的所有要求。然而，这种功能可以通过软件中的 GPIO 来实现。 MCX A13 A14x MCX A15x Arm Cortex-M33 - 低功耗智能外设 | 恩智浦半导体 MCX N94、N54、N53、N52 和 N24 MCU | 恩智浦半导体 谢谢！ BR 爱丽丝 回复： a replacement product for MCF51JE256 亲爱的爱丽丝， 感谢您的回复，也感谢贵公司之前推荐的替代芯片解决方案——它们对我们的评估非常有帮助。 目前，我公司正在从多个角度评估替代芯片的可行性，具体解决方案仍在进一步审查和确认中。计划最终确定后，我们将及时与您沟通，并期待与贵公司推进下一步的合作。 再次感谢您的支持和帮助！   顺祝商祺！ 刘英

MCF51JE256の代替製品 以下の要件を満たすMCUチップについて、ご提案をお願いしたいです。32ビットデータバス/転送、プログラムメモリ空間1MByte以上、少なくとも1つのI2Cバスコントローラと統合、少なくとも2つのSPIバスコントローラと統合、6つ以上のA/Dアナログからデジタルへの変換チャネル、少なくとも3×3マトリックスキーボードコントローラと統合、少なくとも2つのタイマーと統合、TOD(時間割り込み)タイマー割り込みおよびその他の外部割り込みと統合、USBインターフェースコントローラと統合。以上です。ご協力ありがとうございます。現在のチップであるMCF51JE256の機能を置き換えられるチップを見つけたいと考えています。もしよければ、これらの要件に合う特定のMCUのおすすめを探す手助けもできます。 アナログ(ADC|CMP|DAC|オペアンプ) オーディオ(PDM |I2S |SAI) 通信・制御(I3C |I2C |SPI |FlexCAN |イーサネット |FlexIO) Re: a replacement product for MCF51JE256 こんにちは@ly_12_31 MCXAやMCXNシリーズを検討することをおすすめします。これらはNXPの最新のメインストリームMCUファミリであり、新しいデザインのプロモーションも積極的に行っています。 これらのデバイスは専用の3×3マトリックスキーボードコントローラを除き、すべての要件を満たします。しかし、この機能はソフトウェア内のGPIOを用いて実装可能です。 MCX A13 A14x MCX A15x Arm Cortex-M33 - 低消費電力かつインテリジェントなペリフェラル | NXP Semiconductors MCX N94、N54、N53、N52、N24 MCU |NXPセミコンダクターズ  よろしくお願いします。 BR アリス 回复： a replacement product for MCF51JE256 アリス様、 ご返信ありがとうございます。また、御社が以前に推奨していた代替チップソリューションにも感謝します。評価に非常に役立ちました。 現在、当社は複数の視点から代替チップの実現可能性を評価しており、具体的な解決策はまださらなる検討と確認中です。計画が確定次第、迅速にご連絡し、今後の協力のステップを進めていくことを楽しみにしています。 改めてサポートとご協力に感謝いたします!   よろしくお願いいたします。 劉英

SWUpdate A/B OTA with U-Boot on i.MX8M Plus Hi NXP Team, I am implementing OTA on i.MX8M Plus LPDDR4 EVK using: Yocto Wrynose Linux 6.18.20 U-Boot 2026.04 SWUpdate 2026.05.1 Current Progress SWUpdate integrated successfully into Yocto. Successfully generated .swu packages. SWUpdate package installation is working. Hardware compatibility checking is working. Successfully updated /etc/ota-version using SWUpdate. rawfile handler is working. Now I want to implement production-level A/B OTA with automatic rollback and signed updates. Questions Could you please guide me on the recommended NXP approach for: A/B rootfs partition layout. U-Boot bootcount/bootlimit based rollback. SWUpdate integration with U-Boot environment. Correct fw_env.config / libubootenv configuration. Signed .swu package verification. Anti-rollback/version protection. Secure Boot + SWUpdate integration. Currently, the OTA update completes, but SWUpdate reports: Cannot initialize environment from /etc/fw_env.config Cannot persistently store update state Is there an NXP reference design, application note, or example for SWUpdate + A/B + U-Boot rollback + signed OTA on i.MX8M Plus? Thanks. i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Yocto Project Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus Hello, We do not provide a standard EVK A/B update framework out of the box. A/B update, rollback policy, and power-fail-safe boot selection are system-level features you must implement using U-Boot + SWUpdate. The closest references are: AN12900 - Secure OTA prototype for Linux using CAAM and Mender or SWUpdate. AN13872 - Enabling SWUpdate. meta-swupdate-imx - NXP Yocto layer with SWUpdate. Best regards. Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus Hey vp1, While I do not have an exact answer, I would like to make you aware that Torizon now supports any i. MX SoCs. It's deployed in many critical i.MX8MPlus products worldwide (mostly on Toradex SoMs). It does feature highly reliable OTA (default is OSTree but can be changed)  It includes out-of-the-box secure boot, anti-rollback, vulnerability management (for EU CRA compliance), and more.  The OS is free and open source; we are happy to help if you like. Contact us if you like to give it a try on the i.MX8M Plus LPDDR4 EVK or your own HW. www.torizon.io  Sorry for the pitch, i work for Torizon and this seemed relevant.  Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus Thanks for the information. I would like to get some guidance on the recommended OTA architecture for our i.MX 8M Plus evk. For our i.MX 8M Plus evk, we need a secure OTA solution with: A/B or fail-safe updates Signed/authenticated OTA packages Secure Boot integration Anti-rollback Automatic recovery after failed/power-interrupted updates Key rotation/revocation Preservation of device identity/configuration Factory recovery and update logging For these requirements, could you please suggest which approach is recommended for the i.MX 8M Plus evk? Specifically, should we continue with the U-Boot + A/B + SWUpdate approach discussed in this thread, or would you recommend another solution such as RAUC, Mender, or an NXP-supported OTA architecture?

i.MX8M Plus での U-Boot を使用した SWUpdate A/B OTA こんにちは、NXP チームの皆様、 i.MX8M Plus LPDDR4 EVK上でOTAを以下で実装しています: ヨクト・ライノーズ Linux 6.18.20 U-Boot 2026.04 SWアップデート 2026.05.1 現在の進捗状況 SWUpdateはYoctoにうまく統合されました。 .swu ファイルの生成に成功しましたパッケージ. SWUpdateパッケージのインストールは動作しています。 ハードウェアの互換性チェックは正常に動作しています。 SWUpdateを使用して/etc/ota-versionを正常に更新しました。 rawfileハンドラーは正常に動作しています。 今度は、自動ロールバックと署名付きアップデートを備えた、本番環境レベルのA/B OTAを実装したいと考えています。 質問 以下について推奨されるNXPのアプローチについて教えていただけますか: A/Bルートファイルシステムのパーティションレイアウト。 U-Bootのブート回数/ブート制限に基づくロールバック。 SWUpdateとU-Boot環境の統合。 fw_env.config / libubootenv の設定を正しく行ってください。 署名済み .swuパッケージの検証。 ロールバック防止／バージョン保護機能。 セキュアブートとソフトウェアアップデートの統合。 現在、OTAアップデートは完了していますが、SWUpdateは次のように報告しています。 Cannot initialize environment from /etc/fw_env.config Cannot persistently store update state NXPのリファレンスデザイン、アプリケーションノート、またはi.MX8M Plus上の SWUpdate + A/B + U-Bootロールバック+署名済みOTA の例はありますか? ありがとうございます。 i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Yocto Project Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus こんにちは、 EVK A/Bテスト用の標準アップデートフレームワークは、標準では提供しておりません。A/Bアップデート、ロールバックポリシー、および電源障害時のセーフブート選択は、U-Boot + SWUpdateを使用して実装する必要のあるシステムレベルの機能です。最も近い参考文献は以下のとおりです。 AN12900 - CAAMやMender、またはSWUpdateを用いたLinux向けの安全なOTAプロトタイプ。 AN13872 - SWUpdateの有効化。 meta-swupdate-imx - SWUpdateを使ったNXP Yoctoレイヤー。 よろしくお願いいたします。 Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus こんにちは、 vp1さん、 正確な答えは持っていませんが、トリゾンが現在はどのiもサポートしていますことを知っておいてほしいです。MX SoC。世界中の多くの重要なi.MX8MPlus製品(主にToradex SoM)に搭載されています。非常に信頼性の高いOTA機能があり(デフォルトはOSTreeですが変更可能です) 標準装備のセキュアブート、アンチロールバック、脆弱性管理(EU CRA準拠用)などが含まれています。 OSは無料のオープンソースです。ご希望であれば喜んでお手伝いいたします。i.MX8M Plus LPDDR4 EVKやご自社のハードウェアで試してみたい方は、ぜひご連絡ください。 www.torizon.io  宣伝になってしまってすみません。私はTorizonに勤めていて、これは関連性があると思ったのでお伝えしました。 Re: SWUpdate A/B OTA with U-Boot on i.MX8M Plus 情報をありがとうございます。 i.MX 8M Plus evk に推奨される OTA アーキテクチャについて、いくつかアドバイスをいただきたいです。 i.MX 8M Plus evk には、以下の機能を備えたセキュアな OTA ソリューションが必要です。 A/Bテストまたはフェイルセーフアップデート 署名済み/認証済みOTAパッケージ セキュアブートの統合 アンチロールバック アップデート失敗時／電源中断後の自動復旧 鍵のローテーション／取り消し デバイスの識別情報／構成情報の保持 工場出荷時の復旧と更新ログ これらの要件について、i.MX 8M Plus EVKにどのアプローチが推奨されているか教えていただけますか? 具体的には、 このスレッドで議論したU-Boot + A/B + SWUpdateのアプローチを継続すべきか、それとも RAUC、Mender、あるいはNXP対応のOTAアーキテクチャなど他のソリューションを推奨しますか?

FS32K144UAT0VLLTおよびFS32K144HAT0MLLTの交換に関するお知らせ マネージャー： 現在、弊社では御社のFS32K144UAT0VLLT（112MHz、LQFP-100パッケージ）を使用しており、動作温度範囲は-40℃～105℃です。 この設計は自動車用ガソリンエンジンECUを対象としており、目標は既存のECUを車載グレードのものに置き換えることです。現在選定されているのはFS32K144HAT0MLLT、LQFP-100、80MHz、LQFP100パッケージで、動作温度範囲は-40℃～125℃です。 すみません： 1. 2つのマイクロコントローラはピン配置をそのまま交換できますか？クロック速度と動作温度だけが異なりますか？ 2. FS32K144UAT0VLLTとピン互換性があり、メイン周波数が112kHzで車載グレードのマイクロコントローラはありますか？型番をお知らせください。よろしくお願いいたします。 3. FS32K144HAT0MLLTにおいて、AはCAN FD、FlexIO、またはセキュリティのどれを表していますか？FがCAN FDとFlexIOを表すFS32K144HFT0MLLRとの違いは何ですか？CAN FD、FlexIO、およびセキュリティとは何を意味しますか？ 4. 私たちは淘宝（タオバオ）などのウェブサイトから購入していますが、これらの販売チャネルの信頼性について懸念しています。北中国のNXPマイクロコントローラー販売代理店のウェブサイトへのリンク、または連絡先情報をお送りいただけますでしょうか？ よろしくお願いいたします。 Re: FS32K144UAT0VLLT和FS32K144HAT0MLLT替换问题 こんにちは@ YF666666 Senlent_0-1789959640629.png 1. 2つのマイクロコントローラはピン配置をそのまま交換できますか？クロック速度と動作温度だけが異なりますか？ はい 2. FS32K144UAT0VLLTとピン互換性があり、メイン周波数が112kHzで車載グレードのマイクロコントローラはありますか？型番をお知らせください。よろしくお願いいたします。 ピン対ピンコネクタは、同じシリーズのものしか使用できません。例えば、S32K144やS32K146の一部のモデルは、同じピン配置とパッケージを使用しています。 上記の注文情報に基づいて、添付ファイルをご確認ください。 3. FS32K144HAT0MLLTにおいて、AはCAN FD、FlexIO、またはセキュリティのどれを表していますか？FがCAN FDとFlexIOを表すFS32K144HFT0MLLRとの違いは何ですか？CAN FD、FlexIO、およびセキュリティとは何を意味しますか？ はい、違いはありません。ただし、Fはセキュリティをサポートしていないため、このチップはCSEモジュールをサポートしていません。 CAN FD、FLEXIOモジュール、およびセキュリティ（CSEcエンジン）をサポートしています。 4. 販売代理店に関する情報：中国における当社のすべての販売代理店パートナーに関する情報は、以下のリンクからご覧いただけます。どの販売代理店でもお選びいただけます。 https://www.nxp.com/support/sample-and-buy/distributor-network:DISTRIBUTORS#CHINA

FS32K144UAT0VLLT和FS32K144HAT0MLLT替换问题 经理： 目前使用你们FS32K144UAT0VLLT，112MHZ，LQFP-100，工作温度-40°~105°， 设计汽车汽油发动机ECU使用，希望替换为汽车级，目前选择FS32K144HAT0MLLT，LQFP-100，80MHZ，LQFP100，工作温度-40°~125°。 请问： 1. 两种单片机可以pin对pin替换吧？只是主频和工作温度不同？ 2. 和FS32K144UAT0VLLT可以pin对pin替换的单片机，有主频112KHZ，汽车级的吗？请发来型号，谢谢！ 3. FS32K144HAT0MLLT其中A是CAN FD,FlexIO,Security吗？和FS32K144HFT0MLLR，其中F是CAN FD,FlexIO有什么区别？CAN FD,FlexIO,Security是什么意思？ 4. 我们从淘宝等网站采购,担心渠道不正规，麻烦经理发来NXP单片机华北代理链接或联系方式，谢谢！ Re: FS32K144UAT0VLLT和FS32K144HAT0MLLT替换问题 Hi@YF666666 Senlent_0-1789959640629.png 1. 两种单片机可以pin对pin替换吧？只是主频和工作温度不同？ 是的 2. 和FS32K144UAT0VLLT可以pin对pin替换的单片机，有主频112KHZ，汽车级的吗？请发来型号，谢谢！ PIN-TO- PIN的只能是同一个系列了，例如S32K144或者S32K146的部分型号，相同管脚和封装的都是PIN-TO-PIN的。 你可以在附件中根据上面的ordering information来找。 3. FS32K144HAT0MLLT其中A是CAN FD,FlexIO,Security吗？和FS32K144HFT0MLLR，其中F是CAN FD,FlexIO有什么区别？CAN FD,FlexIO,Security是什么意思？ 是的，没有区别，只是F并不支持Security，就是说这颗料不支持CSE模块。 就是支持CAN FD，支持FLEXIO模块，支持Security(CSEc引擎)。 4.关于代理商的信息 在下面的链接中你可以看到中国区的所有代理合作伙伴的信息，你可以选择任意一家代理商： https://www.nxp.com/support/sample-and-buy/distributor-network:DISTRIBUTORS#CHINA

i.MX93 M33 Can't Use System TCM RAM for Allocation We're evaluating the i.MX9352 for an IoT device. I've created an application for the M33 core for time-critical IO operations which include collecting a large number of samples from peripherals. For development purposes, I am loading and starting the M33 code from Linux with remoteproc. Code is written in C and using MPUXpresso 26.06.00 SDK. I got the code working well, but now I need a large buffer for samples (~24 kB). I have tried adding this as either a static array or heap allocated with `malloc`. In either case, I seem to tun out of RAM even though the compile output indicates there is plenty. Working Version: Here's the memory information for a build with a small buffer, which **works OK** (but the buffer is too small for our requirements). Memory region Used Size Region Size %age Used m_interrupts: 1140 B 1144 B 99.65% m_text: 78300 B 129928 B 60.26% m_m33_suspend_ram: 0 B 8 KB 0.00% m_a55_suspend_ram: 0 B 4 KB 0.00% m_data: 48016 B 108 KB 43.42% m_rsc_tbl: 0 B 4 KB 0.00% build finished successfully. Here is some info from the ELF file: readelf -l imx_m33.elf Elf file type is EXEC (Executable file) Entry point 0xffe0595 There are 4 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x0ffe0000 0x0ffe0000 0x00474 0x00474 R 0x1000 LOAD 0x001478 0x0ffe0478 0x0ffe0478 0x131dc 0x131dc RWE 0x1000 LOAD 0x015000 0x20003000 0x0fff3654 0x00170 0x00170 RW 0x1000 LOAD 0x000180 0x20003180 0x0fff37e0 0x00000 0x0ba10 RW 0x1000 Section to Segment mapping: Segment Sections... 00 .interrupts 01 .resource_table .text .ARM .init_array .fini_array 02 .data 03 .bss .heap .stack Large Static Allocation: Here's the memory and ELF file info for a build with a **24 kB static allocated buffer**. I.e.: static uint32_t m_sample_queue[SAMPLE_QUEUE_LENGTH]; // SAMPLE_QUEUE_LENGTH = 6000 Memory region Used Size Region Size %age Used m_interrupts: 1140 B 1144 B 99.65% m_text: 78240 B 129928 B 60.22% m_m33_suspend_ram: 0 B 8 KB 0.00% m_a55_suspend_ram: 0 B 4 KB 0.00% m_data: 72016 B 108 KB 65.12% m_rsc_tbl: 0 B 4 KB 0.00% build finished successfully. ### (As expected, the `m_data` section has increased in size.) ### readelf -l imx_m33.elf Elf file type is EXEC (Executable file) Entry point 0xffe0595 There are 4 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x0ffe0000 0x0ffe0000 0x00474 0x00474 R 0x1000 LOAD 0x001478 0x0ffe0478 0x0ffe0478 0x131a0 0x131a0 RWE 0x1000 LOAD 0x015000 0x20003000 0x0fff3618 0x00170 0x00170 RW 0x1000 LOAD 0x000180 0x20003180 0x0fff37a0 0x00000 0x117d0 RW 0x1000 Section to Segment mapping: Segment Sections... 00 .interrupts 01 .resource_table .text .ARM .init_array .fini_array 02 .data 03 .bss .heap .stack When I try to start this version in Linux with remoteproc, it fails to start and dmesg shows the following errors: [ +0.001258] imx-rproc remoteproc-cm33: Translation failed: da = 0xfff37a0 len = 0x117d0 [ +0.000021] remoteproc remoteproc0: bad phdr da 0xfff37a0 mem 0x117d0 [ +0.000006] remoteproc remoteproc0: Failed to load program segments: -22 [ +0.008868] remoteproc remoteproc0: Boot failed: -22 Claude tells me this is a problem with the .bss .heap .stack section, because the PhysAddr is `0x0fff37a0` and the size is now `0x117d0`. `0x0fff37a0 + 0x117d0 = 0x10004f70` which exceeds the M33 Code TCM address range 0x0ffe0000 .. 0x10000000. The explaination was confusing but my interpretation is that the static initialisation has to go into the "code" section, causing it to overflow even though there is plenty of space in the "system" TCM range (the other 128 kB). So maybe this makes sense. Dynamic (Heap) Allocation: E.g.: uint32_t *p_sample_queue = malloc(SAMPLE_QUEUE_LENGTH, sizeof(uint32_t)); The default heap size available to C is only 1 kB, so malloc fails with our large buffer. I modified the CMake for the project to allocate a larger heap (32 kB) via __heap_size__ which feeds into the linker script: mcux_add_linker_symbol( SYMBOLS "__stack_size__=0x400 \ __heap_size__=0x8000 \ <---- Added __use_shmem__=1 \ __multicore__=1 \ " ) Build output and ELF file info: Memory region Used Size Region Size %age Used m_interrupts: 1140 B 1144 B 99.65% m_text: 78240 B 129928 B 60.22% m_m33_suspend_ram: 0 B 8 KB 0.00% m_a55_suspend_ram: 0 B 4 KB 0.00% m_data: 103760 B 108 KB 93.82% m_rsc_tbl: 0 B 4 KB 0.00% build finished successfully. #### ELF file info: #### readelf -l imx_m33.elf Elf file type is EXEC (Executable file) Entry point 0xffe0595 There are 4 program headers, starting at offset 52 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x0ffe0000 0x0ffe0000 0x00474 0x00474 R 0x1000 LOAD 0x001478 0x0ffe0478 0x0ffe0478 0x131a0 0x131a0 RWE 0x1000 LOAD 0x015000 0x20003000 0x0fff3618 0x00170 0x00170 RW 0x1000 LOAD 0x000180 0x20003180 0x0fff37a0 0x00000 0x193d0 RW 0x1000 Section to Segment mapping: Segment Sections... 00 .interrupts 01 .resource_table .text .ARM .init_array .fini_array 02 .data 03 .bss .heap .stack This seems to make the problem WORSE, not better (.bss/.heap/.stack at PhysAddr 0x0fff37a0, size 0x193d0). [ +0.001320] imx-rproc remoteproc-cm33: Translation failed: da = 0xfff37a0 len = 0x193d0 [ +0.000019] remoteproc remoteproc0: bad phdr da 0xfff37a0 mem 0x193d0 [ +0.000006] remoteproc remoteproc0: Failed to load program segments: -22 [ +0.002908] remoteproc remoteproc0: Boot failed: -22 I thought using heap allocation should allow the code section to be smaller and allocate the memory from the data section. The "m_data" section shown in the build output above is indeed bigger. I don't really understand the "PhysAddr", which matches the "Code TCM" range from the ref manual, even for things which should be in the "System TCM" region (I think?). The addresses under "VirtAddr" seem correct. Why does the ELF file still try to place this .bss/.heap/.stack data at PhysAddr 0x0fff37a0, why is it so big when using runtime heap allocation, and is there a way to allocate my large buffer in the "System TCM" region? Re: i.MX93 M33 Can't Use System TCM RAM for Allocation Hi @jcolebaker  You can choose to change the LMA for data/bss/heap/stack to System TCM. In the MCUX linker script, change the load address (AT) for the data segment from code TCM to System TCM, so that PhysAddr also falls at 0x2000_0000: .data : { ... } > m_data AT> m_data /* Do not use AT> m_text */ .bss : { ... } > m_data When LMA == VMA and both are in System TCM, PhysAddr becomes 0x2000_xxxx, which matches an entry in the {0x20000000, …, 0x00040000} (256 KB) range in remoteproc driver, allowing remoteproc to translate correctly. Best Regards, Zhiming Re: i.MX93 M33 Can't Use System TCM RAM for Allocation Thanks, that did it! Note, the main segment I needed to move in order to use a much larger heap was the "heap" segment:  .heap : { ... } > m_data AT> m_data

p3h2840调试问题咨询 目前基于P3H2840的官方demo进行调试，发现在I2C/I3C 模式下 demo 上温度传感器读到的值有差异（如下图所示），是正常的吗？ Re: p3h2840调试问题咨询 您好， 每次读取 I3C 模式寄存器时看到的第二个字节 0xff 都是不正确的，这表明集线器配置存在问题。作为参考，P3H2x4xHN-ARD 上的板载温度传感器是 NXP P3T1755DP 设备，完全支持 I3C，因此一旦集线器正确设置，两种模式下的读数应该相同。 请检查以下三项： 动态地址分配— P3T1755DP 在 I2C 模式下启动，必须先接收动态地址（通过 ENTDAA、SETAASA 或 SETDASA），然后 I3C 私有传输才能工作。如果在此步骤完成之前调用 i3c_xfer ，则设备无法正确响应 I3C 帧，并且第二个字节将读取为 0xff 。确认地址分配 CCC 已成功运行，并且 0x4c 是分配的动态地址。 突发长度使能 — REG#17[6] (BL_ENABLE) — 如果设置此位，则 I3C 写入阶段必须在寄存器指针之后包含一个突发长度字节。如果您的 i3c_xfer 调用仅发送 1 个写字节（寄存器地址），则集线器会收到不完整的帧，并且读取响应未对齐，导致第二个字节出现 0xff 。请读取寄存器#17，并确认第6位是否已设置。如果是，要么将 BL 字节添加到写入有效载荷中，要么在不需要时清除 BL_ENABLE。 目标端口 VCCIO — REG#22 — 在 I3C 模式下，目标端口使用参考 REG#22 中的 VCCIO 设置的推挽驱动电平。如果这与 P3T1755DP 的实际供电电压不匹配，则在推挽模式下传输的数据字节可能会损坏。请确认 REG#22 显示的电压是否为传感器所连接的目标端口的正确工作电压。 Re: p3h2840调试问题咨询 感谢您的回复， 应该是器件不支持SETAASA，目前改成SETDASA进入I3C后正常了，感谢您的支持

S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link Sta Platform: S32K344 with AB-Swap scheme. Separate firmware images reside in Active and Passive blocks. Observation: After executing HSE_ActivatePassiveBlock() to swap active/passive partitions, a full power cycle does not trigger automatic firmware startup. Firmware executes successfully only when J-Link is attached and Start Application is triggered from debugger. Could anyone explain the root cause and provide recommended fixes? Re: S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link Hi @HQZ  Are you sure there is a valid image in the passive partition? What do you observe if you attach a debugger to the running target without resetting it after power-up? Did the device enter JTAG recovery mode? Or you can simply reset the device by your debugger and then check if it reached the entry point of your application.  If the device is stuck in an endless loop at address 0x2040012C, it indicates that it has entered JTAG recovery mode. This could also point to an issue with the IVT configuration or IVT integrity. Also, is the image in the passive partition linked to run from the active partition address space, i.e. starting at 0x00400000? Finally, are you using Secure Boot? Regards, Lukas Re: S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link Hi @HQZ  “while Partition B firmware is linked starting at 0x600000” – this is the problem. Both images must be linked for active partition addresses – 0x400000. The applications are always running from active partition, not from passive partition. Solution – use the same linker file for both projects. It works with your debugger because debuggers set the program counter “manually” to entry point address which is found in elf file. Regards, Lukas Re: S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link Hello@lukaszadrapa  Platform: S32K344, AB-Swap architecture. Independent firmware images are stored in Active Block and Passive Block separately. HSE Secure Boot is disabled. Problem Description: After calling HSE_ActivatePassiveBlock() to complete the Active/Passive partition switch, the device cannot automatically boot the target firmware after power cycle and reset. However, if the J-Link debugger is connected to the chip and "Start Application" is clicked within the debugger software, the swapped firmware runs normally. Additional background: Firmware resides in both Partition A and Partition B. The only difference between the two images is the LED blinking frequency. Partition A firmware is linked starting at 0x400000, while Partition B firmware is linked starting at 0x600000. After invoking HSE_ActivatePassiveBlock() and reset, I dumped flash contents with J-Link. The contents of Partition A and Partition B have been physically swapped, confirming that HSE_ActivatePassiveBlock() takes effect. Questions: 1. What is the root cause of this behavior? Why does cold power-on boot behave differently from debugger-triggered "Start Application"? 2. What feasible solutions can resolve the auto-boot failure after AB partition swap? Thanks for your support. Re: S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link Hello@lukaszadrapa  I have tried the AB‑partition swap according to previous suggestions, but the issue still persists. The HSE firmware version used is s32k344_hse_fw_1.5.0_2.40. Test setup for validating AB‑swap: Single linker script with application‑based self‑update. The application is responsible for programming the new firmware image into the passive partition. Linker script: Only one linker script is used, and the firmware start address is always set to 0x00400000. Workflow: 1. The application running in Partition A (logical address 0x00400000) receives new firmware over CAN. The only difference between Partition A and Partition B firmware is the LED‑blinking frequency. 2. The application programs the new firmware directly into the physical address of the passive partition (0x00600000). 3. After programming completes, the HSE_ActivatePassiveBlock() service is called. 4. The chip is then reset. Observation: The firmware fails to run after reset. However, when J‑Link is connected and "Start Application" is triggered from the debugger, the firmware from Partition B executes correctly. What other root causes can lead to unsuccessful partition swap, and what are the corresponding solutions? Regards Re: S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link I’m sorry for delayed response. Here are some typical issues: When you run HSE_ActivatePassiveBlock() and when you reset the device, it takes about 1s until HSE is ready to accept new service requests. That’s because HSE takes a backup of HSE firmware to passive partition. HSE_STATUS_INIT_OK flag in FSR register is set once the operation is completed. So, it’s not possible to use HSE until it’s finished. Sometimes this is the reason of troubles. This has been optimized in firmware versions 0.2.55.0 and newer and the firmware is copied to passive partition only if it is updated. If it is still the same, HSE will skip this operation and the swap is much faster. Then I recommend to read description in HSE Firmware reference manual rev. 2.7 in section: “14.6.5  Synchronizing flash read/write access between HSE and application core”: https://www.nxp.com/webapp/sd/collateral/1765990353647716033651?version=2.7 There are tables 149, 150 and 151 where you can find details about typical scenarios. In your case: when HSE takes backup of itself to passive partition, it is not possible to access flash block 3 because HSE performs flash operations on that block. Also you can’t perform flash operations on block 1 because HSE firmware is running from this block. Another thing is that if HSE is running, it is not possible to change HSE_CLK. This can be a problem after the swap when HSE is running about 1s after the reset. When changing HSE_CLOCK, HSE must be in idle state. It is not possible to change the clock while HSE is running. This can lead to unpredictable behavior. It is explicitly mentioned in the S32K3 reference manual: “Before configuring HSE_CLK, you must wait for the SBAF to enter WFI by reading core status register of HSE CPU (PRTN0_CORE2_STAT).” This could be a problem when using older versions of RTD drivers because the drivers did not check mentioned status register. This check was implemented to RTD version 5.0.0 and higher. If you have older version, it’s up to user to poll the WFI before clock initialization. So, this may be also the reason why it is failing. 回复： S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link Hello，bro I also encountered the same problem. Could you please tell me how you solved it? 回复： S32K344 AB-Swap auto-boot failure after HSE_ActivatePassiveBlock; firmware boots only via J-Link Hello, Apologies for the delayed response—I just saw your message. Has the issue been resolved now, or do you still need assistance?

सीखो अप में शिकायत कैसे दर्ज करें Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें9279-187863 सीखो अप का तुरंत समाधान, क्योंकि हर कंपनी जुड़ी है राष्ट्रीय उपभोक्ता हेल्पलाइन से शिकायत दर्ज करने के लिए, कॉल करें उपभोक्ता हेल्पलाइन पर या व्हाट्सएप नंबर पर SMS भेजें।   Re: सीखो अप में शिकायत कैसे दर्ज करें Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें9279-187863 सीखो अप का तुरंत समाधान, क्योंकि हर कंपनी जुड़ी है राष्ट्रीय उपभोक्ता हेल्पलाइन से शिकायत दर्ज करने के लिए, कॉल करें उपभोक्ता हेल्पलाइन पर या व्हाट्सएप नंबर पर SMS भेजें।  

NXP是否有支持Sonic OS的MPU？ 您好，NXP， 我们需要一款能够支持 SONIC OS 的处理器。 我在NXP网站上找不到这条消息。 您能帮忙再核实一下吗？ 非常感谢。 i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Does NXP has MPU supporting sonic OS ? 嗨志明， 知道了。 非常感谢。 Re: Does NXP has MPU supporting sonic OS ? 嗨@jimmyli NXP官方并不支持SONIC OS。 此致， 志明

在 vscode 中安装 mcuxpresso 配置工具时出错 亲爱的各位 我正在安装用于 vscode 的 MCUxpresso，但当我尝试安装用于 vs 代码的 MCUXpresso 配置工具时，却出现了以下错误： [error] 无法获取 MCUXPRESSO-CT-WIN64-26.03 的下载 URL：200: OK。跳过下载... [error] 安装 MCUXpresso 配置工具时发生错误： 无法获取 MCUXPRESSO-CT-WIN64-26.03 的下载 URL。 跳转... *** 安装错误 *** 我的 VScode 版本是 版本：1.118.1 (用户设置) Commit：034f571df509819cc10b0c8129f66ef77a542f0e 日期：2026-04-29T17:36:44+03:00 Electron: 39.8.8 ElectronBuildId：13870025 Chromium: 142.0.7444.265 Node.js: 22.22.1 V8: 14.2.231.22-electron.0 操作系统：Windows_NT x64 10.0.26200 这是 VScode 自动打开的表单 _Ferrari__0-1778425696101.png 您遇到过类似问题吗？ 你是怎么修好的？ 非常感谢你们的帮助与合作 顺祝商祺！ Re: error while installing mcuxpresso config tool in vscode 您好， MCUXpresso 安装程序以前在从 nxp.com 下载时遇到过兼容性问题。这个问题已在几天前发布的最新版本中得到解决。请使用自动更新功能更新 MCUXpresso 安装程序，然后重新尝试安装 MCUXpresso 配置工具。 AlexandraMaracine_0-1778479402779.png 谢谢！ 亚历山德拉 Re: error while installing mcuxpresso config tool in vscode 20260920 你好， 我已按照您建议的方法操作，但问题仍然存在。今天是2026年9月20日。我已经确认我的 MCUXpresso 安装程序已更新到最新版本。但是，我在安装 MCUXpresso 配置工具和安全配置时仍然会遇到错误。 您能帮忙进一步核实一下吗？ 谢谢。 1.png 2.png

Sikho app mein shikayat kaise karen Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें  का तुरंत समाधान, क्योंकि हर कंपनी जुड़ी है राष्ट्रीय उपभोक्ता हेल्पलाइन से  शिकायत दर्ज करने के लिए, कॉल करें  उपभोक्ता हेल्पलाइन पर या व्हाट्सएप नंबर पर SMS भेजें।   Re: Sikho app mein shikayat kaise karen Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें का तुरंत समाधान, क्योंकि हर कंपनी जुड़ी है राष्ट्रीय उपभोक्ता हेल्पलाइन से शिकायत दर्ज करने के लिए, कॉल करें उपभोक्ता हेल्पलाइन पर या व्हाट्सएप नंबर पर SMS भेजें।  

Advice Needed for Trusted Online Resource of Free Software Hi everyone, I’m looking for reliable online resource for cybersecurity, wireless networking, website development software. In particular, software solution for website optimization, networking, digital security, or online productivity I’ve heard about thefreetech.com as one option, but I’m curious how it compares to other popular platforms. Has anyone used it recently? How accurate and user-friendly is it? Any insights, tips, or alternative recommendations would be really helpful! Thanks in advance!

Sikho 应用程序 mein shikayat kaise karen Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें  का तुरंत समाधान， क्योंकिहरकंपनीजुड़ीहैराष्ट्रीयउपभोक्ता हेल्पलाइनसे  शिकायत दर्ज करने के लिए, कॉल करें  उपभोक्ता短信 短信 短信   Re: Sikho app mein shikayat kaise karen Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें का तुरंत समाधान， क्योंकिहरकंपनीजुड़ीहैराष्ट्रीयउपभोक्ता हेल्पलाइनसे शिकायत दर्ज करने के लिए, कॉल करें उपभोक्ता短信 短信 短信  

Request to extend expired license for S32 Design Studio for ARM v2.2 Hello NXP License Team, My S32 Design Studio for ARM v2.2 license will expire and I would like to continue using it. Both the License Expiration and the Entitlement Expiration dates show July 5, 2026, so the entitlement itself will expire and re-activating with the existing activation code no longer produces a valid license. Could you please extend the entitlement so that I can re-activate? Details below: Product: S32 Design Studio for ARM v2.2 Activation Code: CCB1-BEC2-FF96-4859 Thank you very much for your great help.       Re: Request to extend expired license for S32 Design Studio for ARM v2.2 Hi,  your S32DS license has been extended. Please activate S32DS again with your old code.  Re: Request to extend expired license for S32 Design Studio for ARM v2.2 Hello NXP License Team, Thansks for your help. However, My S32DS License details is still  "Evaluation" Coudl you please check it again. Thanks for your great support. S32 Design Studio for ARM ActivationId: CCB1-BEC2-FF96-4859 Evaluation Days: 20 Feature Version: 2.2 Feature Status: Evaluation (20 days) Re: Request to extend expired license for S32 Design Studio for ARM v2.2 Hi, I've been re-compiled my code code with S32DS ARM 2.2 However, my S32DS ARM 2.2 license is still not extened. Does anyone can help me? 回复： Request to extend expired license for S32 Design Studio for ARM v2.2 Hi，    Request to extend expired license for S32 Design Studio for ARM v2.2，tks Tony_lv_1-1789897641124.png

सीखो अप में शिकायत कैसे दर्ज करें Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें9279-187863 सीखो अप का तुरंत समाधान, क्योंकि हर कंपनी जुड़ी है राष्ट्रीय उपभोक्ता हेल्पलाइनसेशिकायतदर्जकरनेकेलिए，कॉलकरें उपभोक्ता हेल्पलाइन पर या व्हाट्सएप नंबर पर SMS भेजें।   Re: सीखो अप में शिकायत कैसे दर्ज करें Shikho shikayat Karen 9279-187863 sikho app शिकायत दर्ज करें9279-187863 सीखो अप का तुरंत समाधान, क्योंकि हर कंपनी जुड़ी है राष्ट्रीय उपभोक्ता हेल्पलाइनसेशिकायतदर्जकरनेकेलिए，कॉलकरें उपभोक्ता हेल्पलाइन पर या व्हाट्सएप नंबर पर SMS भेजें।