Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
HB200x AUTOSAR R21-11 Version 0.8.0 not supported by S32K3_RTD_6_0_0_D2506_ASR_REL_4_7_REV_0000_2025 Hello NXP, I tried to integrate the HB200x AUTOSAR spec SDK into the S32 Design Studio but I am getting the following error message: Issue: Mc33hb is not found in the toolchain/IDE project. The project will not compile! Level: Error Type: Validation Tool: Toolchain/IDE project Origin: Peripherals Target: Toolchain/IDE project: M7_0 Resource: platform.driver.mc33hb Even the files CDD_Mb33Hb.c CDD_Mb33Hb.h etc., have not been added when the SDK was installed in the S32 Design Studio application (v3.6.4) Re: HB200x AUTOSAR R21-11 Version 0.8.0 not supported by S32K3_RTD_6_0_0_D2506_ASR_REL_4_7_REV_0000_ Hi,  seems you are using wrong RTD version. Based on HB200x AUTOSAR R21-11 0.8.0 release note this software can be used on top of SW32K3_RTD_4.4_R21-11_3.0.0_D2303_DS_updatesite.zip (which needs to be installed in S32 Design Studio IDE v3.5). PetrS_0-1789471295419.png BR, Petr Re: HB200x AUTOSAR R21-11 Version 0.8.0 not supported by S32K3_RTD_6_0_0_D2506_ASR_REL_4_7_REV_0000_ Are there other versions of the HB200x SDK that support RTD 6.0.0 or greater, as we would like to use the newest AUTOSAR libraries for our use case? Re: HB200x AUTOSAR R21-11 Version 0.8.0 not supported by S32K3_RTD_6_0_0_D2506_ASR_REL_4_7_REV_0000_ Since we prefer using RTD 6.0.0 or greater. I would be helpful if there is a way to upgrade the existing driver such that it is compatible with RTD 6.0.0.. Requesting for guidance.
View full article
iMX8Mp_FALCON_MODE_RDC_FAILED こんにちは 環境の詳細: ボード: i.MX8M Plus EVK(i.MX8MP EVK) カーネルバージョン: 6.12.49 Yocto Environment:Yocto拠点のNXP BSP ブートモード:ファルコンモード i.MX8MPでFalconモードを有効にしたところ、エラーが発生しました。 ノードが見つかりませんでした!、エラー: -11! => この問題は、RDC ノードが構造化されていないことが原因であることがわかりました。 RDCノードが必要ですか?そうでなければ、こういうことにしよう。 ここにブートログを貼り付けます。 U-Boot SPL 2025.04-g4ddbad60eff3-dirty(2025年11月19日 07:56:58 +0000) DDRINFO: DRAM初期化開始 DDRINFO: DRAM レート 4000MTS                                                           DDRINFO: DDRHY キャリブレーションが完了しました DDRINFO: ddrmix 設定完了 SEC0: RNG がインスタンス化されました 通常起動 MMC2 から起動しようとしています ノードが見つかりませんでした!、エラー: -11!                                                       ノードが見つかりませんでした!、エラー: -11!                                                       注意:JR0はHABで使用可能なのでNSにリリースしないでください 通知:  BL31: v2.12.0(リリース):lf-6.12.49-2.2.0-dirty                         お知らせ:BL31:製造日時:2025年10月17日 10:13:07 p104p104p104 NXP i.MXリリース ディストリビューション 6.12-walnascar imx8mpevk ttymxc1   imx8mpevk ログイン: root root@imx8mpevk:~# i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: iMX8Mp_FALCON_MODE_RDC_FAILED こんにちは、 @Sanjiv_Mns 「imx8m,mcu_rdc」は、M7専用のリソースを割り当てるためのRDC構成を生成するために使用されます。もしこれが不要なら、 board_handle_rdc_configへの参照を削除できます。必要ならDTSに mcu_rdc を追加できます。 よろしくお願いします、 志明
View full article
[suggestion] Pin names should be shown in Port peripheral PortPin list When adding pins to the Port peripheral, you'll end up with a long PortPin and  UnTouchedPortPin list. The lists are numbered up from 0 with no visible reference to their name, so if you need to change one specific pin's setting, you'll have to click through the whole list to find it. Of course you could now create a list in some external tool that maps the ID to the pin name/function, but having that information immediately visible in the actual tool would be greatly preferrable. My suggestion: Inside the Ports peripheral PortPin and UntouchedPortPin list, besides the ID show the name of the pin. The name could either be taken from the PortPin setting, or from the Pin label, if you want to further automate the whole process. This improvement could also be applied to other lists that only show an ID at the moment, like PortContainer, DioPort, DioChannels etc. Eclipse IDE Usage and Settings General Re: [suggestion] Pin names should be shown in Port peripheral PortPin list Hi @daniel_meier  I understand your point that it is not easy to identify a specific pin based only on the PortPin and UnTouchedPortPin lists. Thank you for your suggestion. I will share your feedback with our software team so they can evaluate whether improvements can be made in future releases. Regarding the modification of a specific pin configuration, in the most recent RTD releases this should be done through the Pin Tool rather than the Peripherals Tool. In fact, most pin-related configurations are no longer editable from the Peripherals Tool and must be configured directly in the Pin Tool. BR, VaneB Re: [suggestion] Pin names should be shown in Port peripheral PortPin list @VaneB Thanks for the reply. So that explains why I can barely change anything there (only 'Lock Register' and 'Mode Changeable'). Does that mean I don't have to set up anything in the PortContainer section, unless I need the above options? Issue is, there's always at least one PortPin that defaults to PCR 0 and that cannot be removed. I am using S32K1 RTD AUTOSAR R21-11 Version 3.0.0 QLP06 for S32K116. Re: [suggestion] Pin names should be shown in Port peripheral PortPin list Hi @daniel_meier  Technically, yes. However, please consider that you need to add all the configured pins to the PortContainer, setting the corresponding PortPin PCR configuration for each pin. Regarding the Lock Register option, if you select "Locked" for a pin in the Pins Tool, an error will also be displayed for the corresponding pin in the Port driver within the Peripherals Tool. This can make it easier to identify the affected pin, especially when working with a long list of configured pins. Regarding the pin you mentioned that cannot be removed, I am not sure I fully understood the situation. When creating a new application with the Pins Tool enabled, PTA0 is added by default. However, once additional pins are configured, PTA0 can be deleted if it is not required by your application. Therefore, you should not have any issues removing it unless you need to keep it to change or configure its functionality for your application. Re: [suggestion] Pin names should be shown in Port peripheral PortPin list Ah, I see now what you mean. Yes, removing the default pin works when I add others. I took from your response that it will not be necessary to add any pins to the Port peripheral, but then I remembered that a colleague mentioned in another topic that the Pins tool will automatically add pins to the Port peripheral in future versions of the RTD.
View full article
iMX8Mp_FALCON_MODE_RDC_FAILED Hi Environment details: Board: i.MX8M Plus EVK (i.MX8MP EVK) Kernel Version: 6.12.49 Yocto Environment: Yocto-based NXP BSP Boot Mode: Falcon Mode As i have enabled the Falcon mode in i.MX8MP, getting a error:  Failed to find node!, err: -11!  => I Found this issue came from RDC node not structured. We need RDC node? else we can go with this. Here i am pasting my boot logs: U-Boot SPL 2025.04-g4ddbad60eff3-dirty (Nov 19 2025 - 07:56:58 +0000)         DDRINFO: start DRAM init                                                     DDRINFO: DRAM rate 4000MTS                                                   DDRINFO:ddrphy calibration done                                               DDRINFO: ddrmix config done                                                   SEC0:  RNG instantiated                                                       Normal Boot                                                                   Trying to boot from MMC2                                                     Failed to find node!, err: -11!                                               Failed to find node!, err: -11!                                               NOTICE:  Do not release JR0 to NS as it can be used by HAB                   NOTICE:  BL31: v2.12.0(release):lf-6.12.49-2.2.0-dirty                       NOTICE:  BL31: Built : 10:13:07, Oct 17 2025 p104p104p104 NXP i.MX Release Distro 6.12-walnascar imx8mpevk ttymxc1   imx8mpevk login: root root@imx8mpevk:~# i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: iMX8Mp_FALCON_MODE_RDC_FAILED Hi @Sanjiv_Mns  “imx8m,mcu_rdc” is used to generate an RDC configuration for allocating resources exclusively owned by the M7. If you do not need this, you can remove the reference to board_handle_rdc_config. If you do need it, you can add mcu_rdc to the dts. Best Regards, Zhiming
View full article
画像ボタンのサイズをパーセンテージで指定すると、バグが発生します。 GUI Guider 2.0.1 バージョンで UI を描画していた際に、画像ボタンにパーセンテージサイズを使用するとバグが発生することに気づきました。画像ボタンのサイズをパーセンテージに設定すると、自動生成される画像ソースのサイズもそのパーセンテージになるため、異常な画像表示の原因になることがあります。 回复: There is a bug when using the percentage size for the image buttons. こんにちは、 @Misarac さん。 情報ありがとうございます。 GUIGUIDERチームに報告します。 BR ハリー
View full article
Feasibility of KMS in S32G3 Can KMS functionality be implemented through custom logic in the HSE Demo application, or is the use of HSE_FWTYPE = 9 / HSE_FWTYPE = 22 mandatory? Re: Feasibility of KMS in S32G3 Hello, @Pranathi06  Thanks for the post. The KMS service mentioned in the demo app is targeted for using the custom HSE FW, which is the reason for HSE_FWTYPE = 9(22), since it is function included in the premium software, I suggest contacting your local NXP representative(if not available, raising tickets via support.nxp.com) for details. BR Chenyin  Re: Feasibility of KMS in S32G3 Hello, @Pranathi06  Thanks for your reply. Sorry that I am not sure what kind of the standard/spec your KMS implementation referring to,  I may not be able to provide a clear confirmation of it, sorry for your inconvenience. From my opinion, you may firstly check the latest standard HSE FW API document(with all APIs/services that be supported in the standard HSE FW including key import/export/generate, etc., which could be found from the HSE FW package), to clarify all key management services that HSE FW supported, then based on your crypto stack/custom application, to analyze if the full functions defined in your KMS could be implemented correctly based on current standard HSE FW of S32G3 BR Chenyin   Re: Feasibility of KMS in S32G3 Can KMS functionality be implemented through custom logic in the HSE Demo application[standard]?
View full article
为 i.MX 8M Plus 和 i.MX 95 寻找内存 你好, 我正在为一个新项目采购内存,但由于目前内存短缺,很难找到供应充足的零件。 根据目前的供货情况和采购便利性,您有什么具体的内存芯片推荐用于新设计吗? 该项目将使用 i.MX 8M Plus 或 i.MX 95。理想情况下,我希望在两个平台上都使用 LPDDR4/4X,以简化采购并有可能重复使用相同的内存元器件。 不过,如果为了方便采购,我也愿意为每个平台使用不同的内存类型。例如: -适用于 i.MX 8M Plus 的 LPDDR4(而非 DDR4,因为低功耗对于此特定应用至关重要) -i.MX 95 处理器支持 LPDDR4X 或 LPDDR5 内存 需要澄清的是,我主要不是在寻找已知与这些处理器兼容的内存设备推荐。相反,我更感兴趣的是目前容易获得且适合新设计的具体零件编号。 如果您能推荐一些更容易采购到的制造商或零部件,或提供一些见解,我们将不胜感激。 谢谢! Re: Souring RAM for i.MX 8M Plus and i.MX 95 嗨@Radeoic 抱歉,我对目前动态随机存取存储器\(DRAM\)的市场供应情况不太了解。您需要直接联系相关的动态随机存取存储器(DRAM)供应商进行咨询。 B.R Re: Souring RAM for i.MX 8M Plus and i.MX 95 如果你是一家位于中国的制造商,这非常困难;如果你位于其他国家,美国公司可以为你提供帮助。 Re: Souring RAM for i.MX 8M Plus and i.MX 95 你应该询问内存的具体型号。
View full article
why imx7d depends on imx6q Recently while trying to reduce kernel size on my builds i discovered that `busfreq-imx.c` is depending on `platsmp.c` file for definitions of `scu_base and `imx_smp_ops`. But for some reason imx7d support for compiling `platsmp` is removed by commit ``` Revert "ARM: imx: add smp support for imx7d" This reverts commit e34645f45805d8308866de7b69f117f554605bb6. It's not used by NXP vendor tree. Signed-off-by: Dong Aisheng ``` and vendor specific busfreq implementation is added by below commit but it's not selecting platsmp in makefile. ``` ARM: imx: add i.MX7D power management support This patch adds i.MX7D power management support, including low power idle, suspend with FastMix off, A7-M4 AMP power management support. Signed-off-by: Anson Huang [ Aisheng: remove duplicated imx7d_init_late definition ] Signed-off-by: Dong Aisheng [ Leo: updated to align with a2faac398("use .arch directives instead of assembler command line flags" ] Signed-off-by: Li Yang ``` Am i missing something or is this some hidden bug in BSP ? I'm using 6.18.37-2.1.x BSP on my builds   i.MX7Dual Suspected Software Defect Re: why imx7d depends on imx6q Hello, This seems to be a bug in source code. Could you use a previous configuration as a workaround to see if solves the issue? Best regards. Re: why imx7d depends on imx6q Yes right now i either have to select an imx6 device in defconfig or apply the patch below; ``` diff --git a/arch/arm/mach-imx/Makefile b/arch/arm/mach-imx/Makefile index 2f22af122c6e..cdc66bdaba1c 100644 --- a/arch/arm/mach-imx/Makefile +++ b/arch/arm/mach-imx/Makefile @@ -44,7 +44,7 @@ obj-$(CONFIG_HAVE_IMX_MMDC) += mmdc.o obj-$(CONFIG_HAVE_IMX_SRC) += src.o obj-$(CONFIG_HAVE_IMX_DDRC) += ddrc.o obj-$(CONFIG_HAVE_IMX_MU) += mu.o -ifneq ($(CONFIG_SOC_IMX6)$(CONFIG_SOC_LS1021A),) +ifneq ($(CONFIG_SOC_IMX6)$(CONFIG_SOC_LS1021A)$(CONFIG_SOC_IMX7D_CA7),) obj-$(CONFIG_SMP) += headsmp.o platsmp.o obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o endif ``` It would be really nice to have it fixed in next BSP
View full article
RW612ボタンはISPピンと多重化されている。 ボタンを押した状態でボードに電源が最初に投入されたときに、 RW612をISPモードで起動するようにしたいです。しかし、そのボタンは通常の操作中にも頻繁に押されるだろう。 このボタンはISP0とGPIO24の両方にコネクテッドされています。 データシートには、ブートローダーがフラッシュからコードの実行を開始すると、 ISP0ピンの機能がEXT_REQに変更されると記載されています。 通常動作中にEXT_REQピンがローレベルにプルダウンされた場合に何が起こるのか、正確にはわかりません。 通常動作中にEXT_REQが時折ローレベルに引き下げられた場合、何が起こるのでしょうか? ソフトウェア で機能を無効にする方法はありますか?起動後にボタンからEXT_REQを隔離しなければならないのでしょうか?それとも特に心配する必要はありませんか? 製品: WiFi RW6XX Re: RW612 button multiplexed with ISP pin こんにちは、 @Niwo さん。お元気でお過ごしでしょうか。 EXT_REQピンは 、RW612データシート の 6.3節 に記載されているように、PTAインターフェースを介して外部無線機と共存するために使われます。ただし、 UM11865の表45に記載されているように、GPIO[24]はUART ISPインターフェースのROMコードで使用されており、その機能は変更できません。 したがって、ボタン機能用に別のGPIOを検討し、ISPインターフェースを分離することをおすすめします。また、ISPは最終製品実装時に永久に無効化または制限されることがあり、MCUへのセキュリティアクセスを強化するため、デザイン時にこの機能を念頭に置くことが重要です。 お役に立てば幸いです! Re: RW612 button multiplexed with ISP pin @RomanVRさん、ご返信ありがとうございます。 ボタンに関する私の目的を明確にするために;ボタンはMCUをディープスリープから覚醒させるもので、ユーザーマニュアルの理解が正しければ、この機能はGPIO[24]とGPIO[25]のみがサポートしているはずです。 GPIO[24]はISPがUART機能に使っており、変更できないとおっしゃっていましたね。これはつまり、GPIO[24]は常にUARTピンのままで、自分のプログラム内でそれを変更できないということですか?それとも、ISPが稼働中にどのピンを使うかを改めず、その後はそのピンを自由に使えるという意味でしょうか? EXT_REQピンについては、開発用にはんだジャンパーを使い、後でIAPソフトウェアアップデートでボタンに永久接続するのではなく、 よろしくお願いいたします。 Re: RW612 button multiplexed with ISP pin こんにちは、 @Niwo さん。実装の詳細を教えていただきありがとうございます。 GPIO[24]の機能について、以前に明確に説明できていなかったら申し訳ありません。このGPIOの機能はアプリケーション内で変更可能です。しかし、ROMコードの観点から見ると、UART機能はGPIO[24]およびGPIO[26]専用であり、他のFlexcommインスタンスやGPIOに変更することはできません。 この情報であなたの疑問が解消されることを願っています。
View full article
i.MX 8M Plusおよびi.MX 95向けRAMの調達 こんにちは、 新しいプロジェクトのためにRAMを調達しているのですが、現在のメモリ不足のため、入手しやすい部品を見つけるのに苦労しています。 現在の入手状況や調達のしやすさを踏まえ、新しいデザインにおすすめのRAMチップはありますか? このプロジェクトでは、i.MX 8M Plusまたはi.MX 95のいずれかを使用する予定です。理想的には、LPDDR4/4Xを両プラットフォームで使い、ソーシングを簡素化し、同じメモリコンポーネントを再利用したいと考えています。 ただし、もし調達が楽になるなら、プラットフォームごとに異なるメモリタイプを使うことも検討しています。例えば: - i.MX 8M Plus向けLPDDR4(DDR4ではなく、この用途では低消費電力が重要) i.MX 95の場合はLPDDR4XまたはLPDDR5 念のため言っておくと、これらのプロセッサと互換性があると知られているメモリデバイスのおすすめを主に求めているわけではありません。むしろ、現在入手しやすく新しいデザインに適した特定の部品番号に興味があります。 どのメーカーや部品が入手しやすいかなど、何かおすすめや情報があれば大変ありがたいです。 ご回答をお待ちしています。 Re: Souring RAM for i.MX 8M Plus and i.MX 95 こんにちは、 @Radeoicさん 申し訳ありませんが、現在のDRAMのマーケット状況については詳しくありません。問い合わせは関連するDRAMサプライヤーに直接お問い合わせいただく必要があります。 B.R Re: Souring RAM for i.MX 8M Plus and i.MX 95 RAMの具体的なモデルを尋ねるべきです。 Re: Souring RAM for i.MX 8M Plus and i.MX 95 中国に拠点を置く製造業者の場合は非常に困難です。他国に拠点を置く場合は、米国企業が支援してくれます。
View full article
为什么 imx7d 依赖于 imx6q 最近,我在尝试减小版本中的内核大小时发现,`busfreq-imx.c` 依赖于 `platsmp.c`。文件用于定义 `scu_base` 和 `imx_smp_ops`。 但不知何故,imx7d 对编译 `platsmp` 的支持已被提交移除。 ``` 撤销“ARM:imx:为imx7d添加smp支持” 这将撤销提交 e34645f45805d8308866de7b69f117f554605bb6。 NXP 供应商树中未使用此功能。 签字人:董爱生 ``` 下面的提交添加了厂商特定的总线频率实现,但它没有在 Makefile 中选择 platsmp。 ``` Arm:imx:添加 i.MX7D 电源管理单元支持 此补丁增加了对 i.MX7D 电源管理单元的支持,包括 低功耗待机,FastMix 关闭时进入睡眠状态,A7-M4 AMP 电源 管理单元支持。 签字人:Anson Huang [爱生:删除重复的 imx7d_init_late 定义] 签字人:董艾生 [ Leo:已更新以符合 a2faac398 的要求(“使用 .arch 指令而不是汇编器命令行标志” ] 签字人:李阳 ``` 是我遗漏了什么,还是电路板支持包中存在某种隐藏的bug? 我使用的是 6.18.37-2.1.x 版本。我的版本中使用了电路板支持包。   i.MX7 双核 疑似软件缺陷 Re: why imx7d depends on imx6q 你好, 这似乎是源代码中的一个漏洞。 您能否使用之前的配置作为临时解决方案,看看是否能解决问题? 顺祝商祺! Re: why imx7d depends on imx6q 是的,目前我要么需要在 defconfig 中选择一个 imx6 设备,要么应用下面的补丁; ``` diff --git a/arch/arm/mach-imx/Makefile b/arch/arm/mach-imx/Makefile 索引 2f22af122c6e..cdc66bdaba1c 100644 --- a/arch/arm/mach-imx/Makefile +++ b/arch/arm/mach-imx/Makefile @@ -44,7 +44,7 @@ obj-$(CONFIG_HAVE_IMX_MMDC) += mmdc.o obj-$(CONFIG_HAVE_IMX_SRC) += src.o obj-$(CONFIG_HAVE_IMX_DDRC) += ddrc.o obj-$(CONFIG_HAVE_IMX_MU) += mu.o -ifneq ($(CONFIG_SOC_IMX6)$(CONFIG_SOC_LS1021A),) +ifneq ($(CONFIG_SOC_IMX6)$(CONFIG_SOC_LS1021A)$(CONFIG_SOC_IMX7D_CA7),) obj-$(CONFIG_SMP) += headsmp.o platsmp.o obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o endif ``` 如果能在下一个 电路板支持包。 版本中修复这个问题就太好了。
View full article
imx7dがimx6qに依存する理由 最近、ビルドのカーネルサイズを小さくしようとしていたところ、`busfreq-imx.c`が`platsmp.c`に依存していることを発見しました。`scu_base`と`imx_smp_ops`の定義ファイル。 しかし、なぜかimx7dによる「platsmp」コンパイルのサポートはコミットによって削除されています ``` 「ARM: imx: imx7dにSMPサポートを追加」に戻す これはコミット e34645f45805d8308866de7b69f117f554605bb6 を元に戻すものです。 NXPのベンダーツリーでは使用されていません。 署名者: Dong Aisheng 「`」 また、ベンダー固有の busfreq 実装は下記のコミットで追加されていますが、makefile で platsmp を選択していません。 ``` Arm: imx: i.MX7Dのパワーマネージメントサポートを追加 このパッチでは、i.MX7Dのパワーマネージメントサポートが追加され、以下の内容が含まれています。 低消費電力アイドル、FastMixオフでサスペンド、A7-M4 AMP パワー マネージメントサポート。 署名者: Anson Huang [Aisheng: 重複しているimx7d_init_late定義を削除] 署名者: Dong Aisheng [Leo: a2faac398("アセンブラのコマンドラインフラグの代わりに.archディレクティブを使用する")に合わせて更新しました] 署名者: Li Yang 「`」 何か見落としているのでしょうか、それともこれはBSPの隠れたバグなのでしょうか? 私は6.18.37-2.1.xを使用しています。私のビルドにおけるBSP i.MX7Dual ソフトウェア不具合の疑い Re: why imx7d depends on imx6q こんにちは、 これはソースコードのバグのようです。 以前の設定を使って回避策を試してみて、問題が解決するか試してみることはできますか? よろしくお願いいたします。 Re: why imx7d depends on imx6q はい、今はdefconfigでimx6デバイスを選択するか、下記のパッチを適用する必要があります。 ``` diff --git a/arch/arm/mach-imx/Makefile b/arch/arm/mach-imx/Makefile インデックス2F22af122C6e..CDC66BDA1C 100644 --- a/arch/arm/mach-imx/Makefile +++ b/arch/arm/mach-imx/Makefile @@ -44,7 +44,7 @@ obj-$(CONFIG_HAVE_IMX_MMDC) += mmdc.o obj-$(CONFIG_HAVE_IMX_SRC) += src.o obj-$(CONFIG_HAVE_IMX_DDRC) += ddrc.o obj-$(CONFIG_HAVE_IMX_MU) += mu.o -ifneq ($(CONFIG_SOC_IMX6)$(CONFIG_SOC_LS1021A),) +ifneq ($(CONFIG_SOC_IMX6)$(CONFIG_SOC_LS1021A)$(CONFIG_SOC_IMX7D_CA7),) obj-$(CONFIG_SMP) += headsmp.o platsmp.o obj-$(CONFIG_HOTPLUG_CPU) += hotplug.o endif 「`」 次のBSPで修正されると本当に嬉しいです。
View full article
FS2400 INIT_CRC_NOK_I 在频繁的电源循环(开/关)条件下,检测到了 FS2400 的 INIT_CRC_NOK_I 标志。在这种情况下,我读取了 FS_I_XXX 寄存器,其内容与我在 INIT 阶段写入的数据一致。此外,故障错误计数没有增加,仍然为0。请问这是否是误报,这种情况是否可以不予处理? Re: FS2400 INIT_CRC_NOK_I 您好, 当 FS2400 的循环 CRC 校验机制检测到每 5 毫秒对 INIT 寄存器重新计算的 CRC 与存储在 FS_CRC 寄存器中的值不匹配时,将设置 INIT_CRC_NOK_I 标志。这是一项真正的功能安全监控功能,在不了解其根本原因的情况下不应忽视。 即使您可以读取 FS_I_XXX 寄存器并发现其值与您写入的值一致,也不能排除 CRC 校验不匹配的可能性——这种情况最常见的原因是 MCU 正确写入了 INIT 寄存器,但在 INIT 阶段结束之前没有计算并将正确的 CRC 值存储在 FS_CRC 中(即,未执行任何操作)。在第一次正确的监视程序刷新之前)。请核实以下内容: 1. CRC 计算:必须对以下寄存器位域的连接进行 8 位 CRC 计算(按此顺序): FS_I_OVUV_CFG1[15:0] FS_I_OVUV_CFG2[15:0] FS_I_ERRMON_LIMP0_CFG[15:0] FS_I_FSSM_CFG[15:4] FS_I_WD_CFG[15:7] 要应用的多项式是:x⁸ + x⁴ + x³ + x² + 1(与 SPI CRC 相同)。 2. CRC 注册:MCU 必须在 INIT 阶段结束之前将计算出的 CRC 写入 FS_CRC(即,在 INIT 阶段结束之前)。在第一次正确的监视程序刷新之前)。如果在写入 CRC 之后修改了任何 INIT 寄存器,则必须重新计算并重新写入 CRC。 3. 故障错误计数器说明:我们注意到您提到故障错误计数仍为 0。请注意,根据设备数据手册,上电复位 (POR) 后故障错误计数器从 1 开始,而不是从 0 开始。每次 INIT_CRC_NOK 触发信号被触发时,该计数器都会加 1。请问您能否确认一下您正在读取哪个寄存器和字段中的值?如果计数器在多次上电循环中保持为 1(POR-RESET 值),则表明该标志在上电序列的早期就被观察到,可能在计数器有时间累积之前。我们希望您能具体说明一下,您观察到该标志出现的时间与 INIT 阶段完成时间之间的确切关系。 4. 电源循环考虑:INIT 阶段总是从 POR(完全断电和上电)重新进入。循环 CRC 校验仅在 INIT 阶段结束后的正常模式下激活。如果在 INIT 关闭后不久观察到 INIT_CRC_NOK_I 标志,则强烈表明在第一次 5 毫秒检查时,FS_CRC 寄存器值与当前的 INIT 寄存器内容不匹配。 BRs,托马斯
View full article
S32G3におけるKMSの実現可能性 KMS機能はHSEデモアプリケーションでカスタムロジックで実装できますか?それとも HSE_FWTYPE = 9 / HSE_FWTYPE = 22 の使用は必須ですか? Re: Feasibility of KMS in S32G3 こんにちは、 @Pranathi06 投稿ありがとうございます。 デモアプリで言及されているKMSサービスはカスタムHSEのFW使用を目的としており、これがHSE_FWTYPE = 9(22)の理由です。プレミアムソフトに機能が含まれているため、詳細は地元のNXP担当者に問い合わせることをおすすめします(対応できない場合は support.nxp.com を通じてチケットを提出してください)。 BR チェイン  Re: Feasibility of KMS in S32G3 こんにちは、 @Pranathi06 ご返信ありがとうございます。 申し訳ありませんが、貴社のKMS実装がどのような規格/仕様を参照しているのかが不明なため、明確な確認を提供できない可能性があります。ご不便をおかけして申し訳ございません。 私の意見では、まず最新の標準HSE FW APIドキュメント(HSEのFWパッケージから入手可能なキーのインポート/エクスポート/生成など、標準HSEファイアメントでサポートされているすべてのAPI/サービスを含む)を確認し、その後、あなたの暗号スタックやカスタムアプリケーションに基づいて、KMSで定義された全機能が現在の標準HSE FWであるS32G3に基づいて正しく実装可能かどうかを分析することをお勧めします BR チェイン   Re: Feasibility of KMS in S32G3 KMS機能はHSEデモアプリケーション[標準]のカスタムロジックで実装できますか?
View full article
LPC55S28 ISP_CMD_EN 未禁用 ISP 命令 你好, 我有一个 LPC55S28 MCU,附带 CMPA 和 CFPA 设置。我直接通过 python 使用 blhost 读取这些值,命令如下。所以这些数据直接来自实际的MCU。这是在MCU完全断电重启之后的情况。 通过USB接口读取CMPA数据。 UV run Python -m spsdk.apps.blhost -u 0x3972,0x3333 read-memory 0x0009E400 512 -f cmpa_dump.bin CMPA 解析为 yaml,且 UV run Python -m spsdk.apps.pfr parse -f lpc55s28 -t cmpa -b cmpa_dump.bin -o parsed_cmpa.YAML 然后,对于地址不同的 CFPA,情况也一样。我从地址 0x9DE00 读取了 CFPA,我认为这是临时版本。但除了 CMPA_PROG_IN_PROGRESS 读取到非零值之外,ping 和 pong 都匹配。但乒乓球的比赛就0x00了。 以下是附件全部文件的摘要。完整文件附上以获取更多细节 CMPA:PI,DLFT NIDEN = USE_DAP,残疾 DEGEN = USE_DAP,失效 TAPEN = USE_DAP,已停用 ISP_CMD_EN = USE_DAP,失效 FA_ME_CMD_EN = FIXED_STATE,启用 SEC_BOOT_EN = ENABLE_0 CFPA:PIN和DLT NIDEN = USE_DAP,残疾 DEGEN = USE_DAP,失效 TAPEN = USE_DAP,已停用 ISP_CMD_EN = USE_DAP,失效 FA_ME_CMD_EN = FIXED_STATE,启用 据我了解,在这种设置下,我应该无法使用 blhost 读取内存。我可以读取CMPA、CFPA、应用程序闪存和应用程序RAM,我可以通过blhost转储整个可执行文件,而无需DAP认证。 问题: 1.如果 ISP_CMD_EN 被禁用,是否意味着您无法读取和写入内部存储器?可以是 PFR 或应用程序内存。我仍然需要发送安全 .sb 文件的功能。不过,这些文件会被传输到引导加载程序。 2. ISP_CMD_EN 是否会禁用通过引导加载程序经由 USB 加载 .SB 文件的功能? 3. 我需要进行哪些设置才能保留使用 .SB 文件的 USB 引导加载程序功能,但禁用通过 ISP 命令读取和写入内存的功能? 4. 为什么我的MCU仍然允许blhost ISP命令,即使CMPA和CFPA已经禁用了该命令? 我已阅读此链接中的论坛帖子: https://community.nxp.com/t5/LPC-Microcontrollers-Knowledge/LPC55-Disable-ISP-and-SWD-to-utilize-code-protection/ta-p/1654157 但是设置中完全禁用了 ISP,这也会完全禁用引导加载程序。我认为那篇论坛帖子并没有解释为什么即使禁用了 ISP_CMD_EN,我的设置仍然允许通过 blhost 发送 ISP 命令。 Re: LPC55S28 ISP_CMD_EN not disabling ISP commands 嗨@guitardenver 关键在于 ISP_CMD_EN 不是所有 blhost 命令的全局启用/禁用位。它控制是否可以通过调试邮箱进入 ISP 模式命令。一旦设备通过另一条允许的启动路径进入 ROM ISP,USB blhost 命令将由 ROM 引导加载程序单独处理。 1. 内存读/写:禁用 ISP_CMD_EN 本身并不会禁用 ReadMemory 或 WriteMemory。这些命令仍然可以访问未受保护的内存。 2. SB 文件下载:ISP_CMD_EN 不会直接禁用 ROM ReceiveSBFile 命令。因此,不应将其视为 USB SB 文件更新的控制手段。 3. 阻止原始内存访问的同时进行 SB 更新:根据 LPC55S28 参考手册,目前没有配置可以在禁用 ReadMemory 和 WriteMemory 命令的同时保持 USB ISP 可用于 SB 更新。 4. 为什么 blhost 仍然有效:这种行为并不一定意味着您的 CMPA/CFPA 设置被忽略。该设备已进入 ROM ISP,而 ISP_CMD_EN 控制进入 ISP 的不同路径。 BR 哈里 Re: LPC55S28 ISP_CMD_EN not disabling ISP commands 嗨,哈里, 感谢您澄清了 ISP_CMD_EN 的作用,并确认 ROM ISP 处理程序一旦进入就缺少命令级过滤。 我们最初的设计假设是,LPC55S28 的认证 ROM 引导加载程序旨在作为生产现场通过 USB(经由签名的 SB2.1容器)进行更新的接口,而无需额外的闪存引导加载程序。然而,从您的回复来看,暴露 USB ROM ISP 接口实际上留下了一个完全开放的内存后门:任何拥有物理 USB 访问权限的人都可以发出原始的读取内存、写入内存和擦除闪存区域的命令。 虽然安全启动可以防止执行修改/未签名的代码,但攻击者仍然可以转储未加密的闪存 IP 或探测现场的SRAM 。 鉴于此,我有一些关于恩智浦希望客户如何在安全的商业产品中部署这项技术的具体问题: PRINCE + 开放式 USB ISP:如果我们启用 PRINCE 闪存加密来保护整个应用闪存中的静态 IP, NXP 对于在现场启用 USB ISP 的网络安全立场是什么?具体来说,在 ROM 启动加载程序内部对内部 SRAM 的任意读/写访问是否会构成实际的攻击面,从而导致密钥泄露或绕过启动逻辑?如果不会,那么我认为我会选择这条路。 推荐的现场更新架构:如果通过暴露的 USB 端口保持 ROM ISP 活动被认为是一种不安全的反模式,那么NXP 推荐的现场更新架构是什么? NXP 是否建议完全禁用 ROM ISP( DEFAULT_ISP_MODE = DISABLE )并使用 ROM IAP API 实现自定义双存储体/辅助引导加载程序来使用 SB 容器? Re: LPC55S28 ISP_CMD_EN not disabling ISP commands 嗨@guitardenver 感谢您提出的其他问题。我建议参考 AN12283 – LPC55Sxx 安全启动,特别是第 5、5.6 和 5.7 节。 AN12283 记录了安全启动、通过 ROM ISP receive-sb-file 命令进行 SB2/SB2.1 固件更新以及 PRINCE 闪存加密的使用。它还指出,PRINCE 密钥由片上 PUF 通过软件无法访问的内部硬件总线提供。 重要的一点是,要确认你的实际安全启动配置。根据 AN12283,SEC_BOOT_EN = 00 表示明文图像,而 01、10 和 11 表示签名图像。由于您之前的 SPSDK 输出显示 SEC_BOOT_EN = ENABLE_0,我建议您先检查其原始值。 有关安全启动、SB2.1 更新和 PRINCE 配置的详细信息,请参阅 AN12283。 LPC55Sxx 安全启动 BR 哈里
View full article
LPC55S28 ISP_CMD_EN not disabling ISP commands Hello,  I have an LPC55S28 MCU with the attached CMPA and CFPA settings. I got these value directly from reading via blhost via python with the commands below. So these came directly from the actual MCU. This was after a full power cycle of the MCU.  CMPA read via USB.  uv run python -m spsdk.apps.blhost -u 0x3972,0x3333 read-memory 0x0009E400 512 -f cmpa_dump.bin CMPA parse into yaml with uv run python -m spsdk.apps.pfr parse -f lpc55s28 -t cmpa -b cmpa_dump.bin -o parsed_cmpa.yaml Then the same thing for CFPA with different address. I read the CFPA from address 0x9DE00, which I think is the scratch version. But the ping and pong match other than the fact that the CMPA_PROG_IN_PROGRESS reads something non-zero for the scratch. But 0x00 for ping and pong. Below is a summary of the full files attached. Full files attached for more details CMPA: PIN, DFLT NIDEN = USE_DAP, DISABLED DEGEN = USE_DAP, DISABLED TAPEN = USE_DAP, DISABLED ISP_CMD_EN = USE_DAP, DISABLED FA_ME_CMD_EN = FIXED_STATE, ENABLED SEC_BOOT_EN = ENABLE_0 CFPA: PIN, DFLT NIDEN = USE_DAP, DISABLED DEGEN = USE_DAP, DISABLED TAPEN = USE_DAP, DISABLED ISP_CMD_EN = USE_DAP, DISABLED FA_ME_CMD_EN = FIXED_STATE, ENABLED From my understanding, with these settings, I should not be able to use blhost to read memory. I can read CMPA, CFPA, application flash, application RAM, I can dump my entire executable via blhost with no DAP authentication.  Questions: 1. If ISP_CMD_EN is disabled, does that mean you can not read and write to internal memory? Either PFR or application memory. I still need the ability to send secure .sb files to the bootloader though.  2. Does ISP_CMD_EN disable the ability to load .SB files via USB over the bootloader? 3. What settings do I need to keep USB bootloader functionality with .SB files, but disable the ability to read and write to memory over ISP commands? 4. Why is my MCU still allow blhost ISP commands even though the CMPA and CFPA have it disabled? I have read the forum post at this link: https://community.nxp.com/t5/LPC-Microcontrollers-Knowledge/LPC55-Disable-ISP-and-SWD-to-utilize-code-protection/ta-p/1654157 But the settings have it completely disable ISP, which disables the bootloader completely. I I don't think that forum post shows why my settings are still allowing ISP commands over the blhost, when the ISP_CMD_EN is disabled.  Re: LPC55S28 ISP_CMD_EN not disabling ISP commands Hi @guitardenver  The key point is that ISP_CMD_EN is not a global enable/disable bit for all blhost commands. It controls whether ISP mode can be entered through the Debug Mailbox Enter ISP Mode command. Once the device has entered ROM ISP through another permitted boot path, USB blhost commands are handled separately by the ROM bootloader. 1. Memory read/write: Disabling ISP_CMD_EN does not by itself disable ReadMemory or WriteMemory. These commands can still access memory that is not otherwise protected. 2. SB file download: ISP_CMD_EN does not directly disable the ROM ReceiveSBFile command. Therefore, it should not be treated as the control for USB SB-file updates. 3. SB update while blocking raw memory access: According to the LPC55S28 reference manual, there is currently no configuration that can keep USB ISP available for SB updates while disabling ReadMemory and WriteMemory commands. 4. Why blhost still works: This behavior does not necessarily mean your CMPA/CFPA settings are being ignored. The device has already entered ROM ISP, while ISP_CMD_EN controls a different path into ISP. BR Harry Re: LPC55S28 ISP_CMD_EN not disabling ISP commands Hi Harry, Thanks for clarifying the role of ISP_CMD_EN and confirming that the ROM ISP handler lacks command-level filtering once entered. Our original design assumption was that the LPC55S28's authenticated ROM bootloader was intended to serve as the production field update interface over USB (via signed SB2.1 containers) without needing a secondary flash bootloader. However, from your reply, it appears that exposing the USB ROM ISP interface effectively leaves a wide-open memory backdoor: anyone with physical USB access can issue raw read-memory, write-memory, and flash-erase-region commands. While Secure Boot prevents modified/unsigned code from executing, an attacker could still dump unencrypted flash IP or probe SRAM in the field. Given that, I have a few specific questions on how NXP expects customers to deploy this in a secure commercial product: PRINCE + Open USB ISP: If we enable PRINCE flash encryption across the entire application flash to protect IP at rest, what is NXP's security stance on leaving USB ISP enabled in the field? Specifically, does arbitrary read/write access to internal SRAM while inside the ROM bootloader present a realistic attack surface for compromising keys or bypassing boot logic? If not, this is the path I think I would take. Recommended Field-Update Architecture: If leaving ROM ISP active over an exposed USB port is considered an insecure anti-pattern, what is NXP's recommended architecture for field updates? Does NXP recommend disabling ROM ISP entirely (DEFAULT_ISP_MODE = DISABLE) and implementing a custom dual-bank / secondary bootloader using the ROM IAP API to consume SB containers? Re: LPC55S28 ISP_CMD_EN not disabling ISP commands Hi @guitardenver  Thanks for the additional questions. I would recommend referring to AN12283 – LPC55Sxx Secure Boot, especially Sections 5, 5.6 and 5.7. AN12283 documents the use of Secure Boot, SB2/SB2.1 firmware updates through the ROM ISP receive-sb-file command, and PRINCE flash encryption. It also states that the PRINCE keys are provided by the on-chip PUF through an internal hardware bus that is not software accessible. One important point is to confirm your actual Secure Boot configuration. According to AN12283, SEC_BOOT_EN = 00 means Plain image, while 01, 10, and 11 mean Signed image. Since your previous SPSDK output showed SEC_BOOT_EN = ENABLE_0, I recommend checking its raw value first. Please refer to AN12283 for the detailed Secure Boot, SB2.1 update, and PRINCE configuration. LPC55Sxx Secure Boot BR Harry
View full article
RW612 button multiplexed with ISP pin I would like to use a button to make the RW612 boot into ISP mode when power is first applied to the board while the button is pressed. But that button will also be pressed regularly during normal operation. The button is connected to both ISP0 and GPIO24. In the datasheet it is stated that the ISP0 pin will change its function to EXT_REQ when the bootloader starts the code execution from flash. I dont exactly know what happens when the EXT_REQ pin is pulled low during normal operation. What does happen when EXT_REQ is pulled low occasionally during normal operation? Is there a way to disable its function in software, do I have to isolate EXT_REQ from the button after boot or is there nothing I have to worry about? Product: WiFi RW6XX Re: RW612 button multiplexed with ISP pin Hi @Niwo, hope you are doing well. The EXT_REQ pin is used to coexist with an external radio through PTA interface as mentioned in section 6.3 of the RW612 Datasheet. However, please note that as stated in Table 45 of UM11865, GPIO[24] is used by the ROM code for UART ISP interface and such functionality cannot be changed. Therefore I'd suggest to consider another GPIO for your button functionality and isolate the ISP interface. Also, please consider that ISP can be permanently disabled or limited for a final product implementation to enhance security access to the MCU, therefore it is important to keep in mind this feature for your design. Hope this helps! Re: RW612 button multiplexed with ISP pin Thank you @RomanVR for your reply, To clarify my goals regarding the button; The button should also make the MCU wake up from deep sleep and if I understand the user manual correctly, only GPIO[24] and GPIO[25] support this functionality. You mentioned that GPIO[24] is used for UART functionality by the ISP and it cannot be changed. Does this mean that GPIO[24] will always be a UART pin and I can't change that in my own program? Or does it only mean that I cannot modify which pins the ISP uses while it is running, and afterwards I can do whatever I want with these pins? For the EXT_REQ pin I decided that I will use a solder jumper for development purposes and later use IAP software updates instead of connecting it permanently to the button. Best regards Re: RW612 button multiplexed with ISP pin Hi @Niwo, thank you for providing details on your implementation. I apologize if I was not clear before regarding GPIO[24] functionality; the function of this GPIO can be changed in your application. However, from a ROM code perspective the UART functionality is exclusive from GPIO[24] & GPIO[26] and cannot be changed to another Flexcomm instance or GPIOs. Hope this information clears out your doubts.
View full article
RW612按钮与ISP引脚复用 我希望使用一个按钮,使RW612启动到ISP模式,当首次给板通电并按下该按钮。但在正常操作过程中,该按钮也会经常被按下。 该按钮同时连接到ISP0和GPIO24 。 数据手册中指出,当引导加载程序从闪存开始执行代码时, ISP0引脚的功能将变为EXT_REQ 。 我不太清楚在正常运行期间将EXT_REQ引脚拉低时会发生什么情况。 正常运行期间,如果EXT_REQ偶尔被拉低,会发生什么情况?是否有办法通过软件禁用其功能?启动后是否需要将EXT_REQ与按钮隔离?或者我无需担心什么? 产品:WiFi RW6XX Re: RW612 button multiplexed with ISP pin 嗨@Niwo ,希望你一切都好。 如 RW612 数据手册 第 6.3 节 所述,EXT_REQ 引脚用于通过 PTA 接口与外部无线电共存。但是请注意,如UM11865的表 45 所述,GPIO[24] 由 ROM 代码用于 UART ISP 接口,并且此功能无法更改。 因此,我建议考虑使用另一个 GPIO 来实现按钮功能,并将 ISP 接口隔离。另外,请注意,为了增强对 MCU 的网络安全访问,最终产品实现中可以永久禁用或限制 ISP,因此在设计时务必牢记此功能。 希望这能帮到你! Re: RW612 button multiplexed with ISP pin 感谢@RomanVR的回复, 为了阐明我关于按钮的目标;该按钮还应该使 MCU 从深度睡眠中唤醒,如果我理解用户手册正确的话,只有 GPIO[24] 和 GPIO[25] 支持此功能。 您提到 GPIO[24] 被 ISP 用于 UART 功能,并且不能更改。这是否意味着 GPIO[24] 将始终是 UART 引脚,而我无法在自己的程序中更改它?或者这仅仅意味着我不能在 ISP 运行时修改它使用的引脚,而之后我可以随意使用这些引脚? 对于 EXT_REQ 引脚,我决定在开发过程中使用焊接跳线,之后使用 IAP 软件更新,而不是将其永久连接到按钮上。 顺祝商祺! Re: RW612 button multiplexed with ISP pin @Niwo你好,感谢你提供实施方面的详细信息。 如果我之前对 GPIO[24] 的功能解释得不够清楚,我深表歉意;此 GPIO 的功能可以在您的应用程序中更改。但是,从 ROM 代码的角度来看,UART 功能与 GPIO[24] 和 GPIO[26] 互不相同,不能更改为其他 Flexcomm 实例或 GPIO。 希望这些信息能消除您的疑虑。
View full article
FS2400 INIT_CRC_NOK_I Under frequent power cycling(power on/off) conditions, the INIT_CRC_NOK_I flag of the FS2400 was detected. In this situation, I read the FS_I_XXX registers, and the contents are consistent with the data I wrote during the INIT phase. In addition, the fault error count did not increase and remained at 0. Could you help me confirm whether this is a false alarm and whether this situation can be left untreated? Re: FS2400 INIT_CRC_NOK_I Hi, The INIT_CRC_NOK_I flag is set when the FS2400's cyclic CRC check mechanism detects a mismatch between the CRC it recalculates over the INIT registers every 5 ms and the value stored in the FS_CRC register. This is a genuine safety monitoring function and should not be dismissed without understanding its root cause. The fact that you can read the FS_I_XXX registers back and find the values consistent with what you wrote does not rule out a CRC mismatch — the most common cause in this scenario is that the MCU writes the INIT registers correctly but does not compute and store the correct CRC in FS_CRC before closing the INIT phase (i.e. before the first correct watchdog refresh). Please verify the following: 1. CRC computation: The 8-bit CRC must be computed over the concatenation of the following register bit-fields (in this order): FS_I_OVUV_CFG1[15:0] FS_I_OVUV_CFG2[15:0] FS_I_ERRMON_LIMP0_CFG[15:0] FS_I_FSSM_CFG[15:4] FS_I_WD_CFG[15:7] The polynomial to apply is: x⁸ + x⁴ + x³ + x² + 1 (same as the SPI CRC). 2. CRC registration: The MCU must write the computed CRC into FS_CRC before the INIT phase is closed (i.e. before the first correct watchdog refresh). If any INIT register is modified after the CRC has been written, the CRC must be recomputed and rewritten. 3. Fault error counter clarification: We note that you mention the fault error count remained at 0. Please be aware that, per the device datasheet, the fault error counter starts at 1 after a power-on reset (POR), not 0. INIT_CRC_NOK increments this counter by +1 each time it is triggered. Could you confirm which register and field you are reading for this value? If the counter remains at 1 (the POR-reset value) across power cycles, this would suggest the flag is being observed very early in the power-on sequence, possibly before the counter has had time to accumulate. We would appreciate clarification on the exact timing of when you observe the flag relative to the INIT phase completion. 4. Power cycling consideration: The INIT phase is always re-entered from POR (full power-down and power-up). The cyclic CRC check only activates in Normal mode after the INIT phase is closed. If the INIT_CRC_NOK_I flag is being observed very shortly after INIT closes, this strongly points to the FS_CRC register value not matching the current INIT register content at the time of the first 5 ms check. BRs, Tomas
View full article
RCCU, FCCU, and Lockstep Diagnostic Data Flow on S32G3 Dear NXP, Based on my understanding, RCCU detects Lockstep mismatches and reports errors to FCCU, which handles fault management and may provide diagnostic information through the Linux kernel log (dmesg). However, the BSP documentation describes this process only at a high level. Could you please provide more specific implementation guidance for the S32G378A with Linux BSP 48.0.0? Available diagnostic data: What types of data can be collected from RCCU and FCCU, such as error status, fault source, error type, or fault context? What information is actually available in hardware, and what can be reported through Linux dmesg? End-to-end data flow: What is the exact flow from a Lockstep mismatch being detected by RCCU, through FCCU fault handling, to Linux kernel reporting? Which registers, interrupts, drivers, or software components are involved? Source code and implementation: Which source files, device drivers, device-tree entries, or configuration files need to be modified or enabled in BSP 48.0.0 to collect and report this information? Does NXP provide an existing GitHub repository, reference implementation, or sample code demonstrating the complete flow? Lockstep input and output: What does the Lockstep mechanism actually compare as its input? Is the input generated internally by the redundant A53 execution paths, or must software configure or load any input data? Where is the relevant configuration performed, and what diagnostic output can software retrieve when a mismatch occurs? Please provide the relevant Reference Manual sections, source-code references, and a concrete implementation workflow, as the current BSP documentation does not explain these details sufficiently. Re: RCCU, FCCU, and Lockstep Diagnostic Data Flow on S32G3 Thank you for your reply. I would like to ask one more question. The Linux BSP 48.0.0 User Manual describes FCCU configuration using Device Tree properties such as `nxp,ncf_fault_list` and `nxp,ncf_actions`. Could you please clarify which source file we should modify to apply this configuration? After saving the changes, will they take effect through the Device Tree, or do we also need to modify the FCCU driver? If possible, please provide a simple example for S32G378A-EVB3. Best regards, Toan Re: RCCU, FCCU, and Lockstep Diagnostic Data Flow on S32G3 Hello, @Toan  Thanks for the post 1. The FCCU provides a hardware interface to collect faults when a failure is detected in the device, it is hardware behavior, different fault number would reflect different failure, you may refer the fault map file attached in S32G3 RM. The Linux FCCU driver in BSP48 allows updating the selected list of Non-Critical Faults handled in FCCU and selecting one of the supported NCF actions using device tree, if the reaction set is an alarm, then the alarm information is printed in the kernel’s log if the corresponding failure occurred. 2. When RCCU detected the issue, the FCCU will record it and then execute the actions set by the user, for example, if alarm is set as the action, then the information could be found in the kernel log, the Linux FCCU driver, DTS, FCCU alarm interrupt handler would be involved. 3. The corresponding information could be obtained from the Chapter 6 of BSP48 UM. 4.  In the lockstep mode, one cluster is considered the main cluster and the second cluster is considered the checker cluster. From a software perspective, the two clusters operate as a single cluster in the lockstep mode. Cortex-A53 Cluster0 is the main execution cluster, where Cortex-A53 Cluster1 follows execution of Cortex-A53 Cluster0. Equivalent operation of replicated resources is supervised by comparators (RCCU) on all functional signals leaving the cluster for the rest of the MCU. Any operational deviations between the supervised signals causes the FCCU to be notified of the discrepancy. In S32G3 A53 Lockstep mode, software does not need to provide or load input data for the Lockstep comparison. The comparison is performed internally by the hardware during normal A53 execution and is transparent to application software. Software mainly configures the Lockstep operating mode, rather than the comparison data. Software can set the corresponding action for the fault. If a mismatch is detected, it is reported through the RCCU/FCCU safety fault mechanism and the relevant actions would be executed. BR Chenyin
View full article