Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
imx8mp Android システムファストブートソリューション 你好! 我参考Android システム高速ブート ソリューション - Hibernate_v1.pdf の調査と概要 imx8mp android14 で  源码是source imx-android-14.0.0_1.0.0/imx_android_setup.sh GPU の不具合が発生する可能性があるため、アクセサリの修正が完了しました。これには解決が必要です Re: imx8mp Android System Fast Boot Solution こんにちは@jieh朱 デフォルトのBSP GPUドライバコードは、GPUの休止状態および電源投入時の実行をサポートしていません。NXPはこの点についてテストを行っていません。`echo mem`の電源投入/電源オフ時の処理については参考になりますが、`echo disk`ではGPUドライバとバッファのリカバリについて別途検証が必要です。 よろしくお願いします、 志明
View full article
KW47 Deep Sleep During BLE Advertising - Recommended Approach and Reference Example Dear NXP Support, I would like to inquire about the low power functionality of the KW47. Environment MCU: KW47 SDK: SDK_26_03_00_KW47-EVK IDE: IAR Embedded Workbench RTOS: FreeRTOS Hardware: Custom Board Our goal is to reduce power consumption while operating as a BLE Peripheral. I have attached a diagram illustrating the intended behavior. Please note that the figure is a conceptual illustration and does not represent actual current consumption values. It is intended to show the expected relationship between Deep Sleep operation and BLE-related events. The intended behavior is as follows: Deep Sleep is used as the low power mode. Advertising transmission is handled by the BLE stack and SDK. Low power operation is enabled immediately after startup. The device automatically enters Deep Sleep when FreeRTOS enters the Idle state. While operating as a BLE Peripheral and continuing advertising, the CPU enters Deep Sleep whenever it becomes idle. The device wakes only when BLE stack processing is required, such as during Advertising Events, Connection Requests, or Connection Events, and returns to Deep Sleep after the required processing has completed. Based on the Low Power Application Developers Guide, it appears that Bluetooth LE applications can use Deep Sleep even while advertising. However, we could not determine which SDK example project should be used as a reference for this implementation. Could you please advise on the following points? What is the recommended approach to achieve the behavior described above? Which SDK example project should be used as a reference? Is there any example that automatically enters Sleep/Deep Sleep while advertising and automatically wakes up when BLE events occur? What is the recommended behavior while a BLE connection is established? Is it recommended to enter Deep Sleep between Connection Intervals, or should the device remain active while connected? Thank you for your support. Best regards,     Protocol: Bluetooth Re: KW47 Deep Sleep During BLE Advertising - Recommended Approach and Reference Example Hi Habib, Thank you for the information and for sharing AN14554. I will review the document, especially Sections 3.2.1 and 4.2.2.6, to better understand the recommended low-power software configuration and Deep Sleep behavior during BLE connection. I appreciate your support. Best regards, hyama Re: KW47 Deep Sleep During BLE Advertising - Recommended Approach and Reference Example Hello @hyama, Please refer to AN14554, which provides the configuration steps to achieve an optimized low-power profile while maintaining high system performance. It also describes the measurement setup and procedures used to measure the current consumption of the KW47. Specifically, Section 3.2.1 describes the recommended software configuration for low-power operation. this example is available in both baremetal and FreeRTOS versions. Also, section 4.2.2.6 covers the connection mode measurements and confirms that the device enters Deep Sleep between Connection Intervals.  BR, Habib
View full article
Fuses programming on 8ULP - for booting from eMMC Hello everybody, Recently I spent some time for trying to program Fuses on an 8ULP board to get it booted from eMMC. These findings might be helpful for those who need to perform this: Manual Procedure: Boot into U-Boot via UUU, stop autoboot, then: => fuse prog -y 4 1 0x00400000 => fuse prog -y 3 7 0x00008000 => reset After reboot, verify: => fuse read 4 1 Word 0x00000001: 00400000 => fuse read 3 7 Word 0x00000007: 00008000 Disconnect USB, power cycle - board boots from eMMC. UUU script: uuu_version 1.2.39 # prog-boot-fuses-evk.lst # Programs eMMC-boot fuses (Boot Config and BT_FUSE_SEL) on a CLEAN EVK-board 8ULP #SDPS: boot -f flash.bin SDPS: boot -f u-boot-imx8ulp-evk-uuu.imx SDPV: delay 2000 #SDPV: write -f flash.bin -skipspl SDPV: write -f u-boot-imx8ulp-evk-uuu.imx -skipspl SDPV: jump FB: ucmd fuse prog -y 4 1 0x00400000 FB: ucmd fuse prog -y 3 7 0x00008000 i.MX8ULP Re: Fuses programming on 8ULP - for booting from eMMC For anyone visiting this page while searching for the fuse map for the imx8ulp, it's attached as the reference manual (IMX8ULPRM) as a spreadsheet. It's not retrievable when viewing in a browser, you must use a PDF viewer like Okular. This is a bad trend by NXP to hide documentation like this. I also encountered the 'feature' when searching for pinmux options for the imx8ulp, which were attached to the Data Sheet (IMX8ULPCEC).
View full article
熔丝在 8ULP 上编程-用于从 eMMC 启动 大家好 最近我花了一些时间尝试在 8ULP 板上对 熔丝 进行编程,让它从 eMMC 启动。 这些发现可能会对需要进行这项工作的人有所帮助: 手动程序: 通过 UUU 启动 U-Boot,停止自动启动,然后: = > 熔丝 prog-y 4 1 0x00400000 = > 熔丝 prog-y 3 7 0x00008000 = > RESET 重新启动后,进行验证: => 熔丝 read 4 1 字 0x00000001: 00400000 => 熔丝 read 3 7 Word 0x00000007: 00008000 断开 USB 连接,重启电源-从 eMMC 启动主板。 UUU 脚本: uuu_version 1.2.39 # prog-boot-fuses-evk.lst # 在 CLEAN EVK-Board 8ULP 上编程 eMMC-boot 熔丝(启动配置和 BT_FUSE_SEL) #SDPS: 启动 -f flash.bin SDPS: 启动 -f u-boot-imx8ulp-evk-uuu.imx SDPV: delay 2000 #SDPV: write -f flash.bin -skipspl SDPV: write -f u-boot-imx8ulp-evk-uuu.imx -skipspl SDPV: jump FB: ucmd 熔丝 prog -y 4 1 0x00400000 FB: ucmd 熔丝 prog -y 3 7 0x00008000 i.MX8ULP Re: Fuses programming on 8ULP - for booting from eMMC 对于任何在搜索 imx8ulp 的 fuse map 时访问此页面的用户,它以电子表格的形式作为参考手册 (IMX8ULPRM) 附上。在浏览器中查看时无法读取,必须使用像 Okular 这样的 PDF 查看器。NXP 这样做隐藏文档,是一种不好的做法。我在查找 imx8ulp 的引脚复用选项时也遇到了这个“功能”,这些选项附在数据手册 (IMX8ULPCEC) 中。
View full article
imx8mp 安卓系统快速启动解决方案 你好! 我参考Android系统快速启动解决方案-Hibernate_v1的学习与总结.pdf 在imx8mp android14  是源码imx-android-14.0.0_1.0.0/imx_android_setup.sh 修改完成会出现GPU的报错,详情见附件,这个需要怎么解决 Re: imx8mp Android System Fast Boot Solution Hi @jieh朱  默认BSP的GPU驱动代码不支持GPU休眠重新上电执行,NXP没有测试过。可以参考 echo mem 的上下电处理,但 echo disk 必须单独验证 GPU 驱动和缓冲区的恢复。 Best Regards, Zhiming
View full article
KW47 在 BLE 广播期间进入深度睡眠状态 - 推荐方法和参考示例 尊敬的NXP技术支持: 我想咨询一下KW47的低功耗功能。 环境 MCU:KW47 SDK:SDK_26_03_00_KW47-EVK IDE:IAR Embedded Workbench 实时操作系统:FreeRTOS 硬件:定制板 我们的目标是在作为 BLE 外设运行时降低功耗。 我附上了一张图表,说明了预期的行为。 请注意,该图为概念示意图,并不代表实际的当前消耗值。其目的是展示深度睡眠操作与 BLE 相关事件之间的预期关系。 预期行为如下: 深度睡眠模式用作低电源模式。 广告传输由 BLE 协议栈和 SDK 处理。 启动后立即启用低功耗模式。 当 FreeRTOS 进入IDLE状态时,设备会自动进入深度睡眠状态。 当 CPU 作为 BLE 外围设备运行并持续广播时,CPU 会在空闲时进入深度睡眠状态。 设备仅在需要 BLE 协议栈处理时才会唤醒,例如在广播事件、连接请求或连接事件期间,并在所需处理完成后返回深度睡眠。 根据低功耗应用开发者指南,蓝牙低功耗应用即使在广播期间也可以使用深度睡眠模式。但是,我们无法确定应该使用哪个 SDK 示例项目作为此实现的参考。 请您就以下几点提供建议? 为实现上述行为,推荐采用什么方法? 应该使用哪个 SDK 示例项目作为参考? 是否有任何示例可以在广播时自动进入睡眠/深度睡眠状态,并在发生 BLE 事件时自动唤醒? 建立 BLE 连接时,建议采取哪些行为?是否建议在连接间隔期间让设备进入深度睡眠状态,还是应该在连接期间保持设备处于活动状态? 感谢您的支持。 顺祝商祺!     协议:蓝牙 Re: KW47 Deep Sleep During BLE Advertising - Recommended Approach and Reference Example 你好,哈比卜, 感谢您提供的信息和分享 AN14554。 我将仔细阅读该文档,特别是第 3.2.1 节和第 4.2.2.6 节,以便更好地了解推荐的低功耗软件配置和 BLE 连接期间的深度睡眠行为。 感谢您的支持。 此致, 海马 Re: KW47 Deep Sleep During BLE Advertising - Recommended Approach and Reference Example 你好@hyama , 请参考AN14554 ,其中提供了在保持高系统性能的同时实现优化低功耗我的的配置步骤。它还描述了用于测量 KW47 电流消耗的测量装置和程序。 具体而言,第 3.2.1 节描述了低功耗运行的推荐软件配置。此示例在裸机和 FreeRTOS 版本中均可用。此外,4.2.2.6 节涵盖了连接模式的测量,并确认设备在连接间隔期间进入深度睡眠状态。 BR, 哈比卜
View full article
i.MX95でセキュアブートを実装するにはどうすればよいですか? imx8mpのセキュアブートプロセスを完了しました。 セキュアブートは、8mp上でHABv4を使用して実現されます。 imx95もセキュアブートの実装にHABv4を使用していますか? flash.binをコンパイルした際、CSFブロックやsld habブロックなどの情報は表示されませんでした。 IMX95でセキュアブートを実行するにはどうすればよいですか? Re: How do I implement Secure Boot on the i.MX95? こんにちは@yyn お元気でお過ごしのことと思います。 U-ブート のドキュメントにある introduction_ahab をご覧ください。 i.MX9ファミリーのSecure Bootプロセスについて説明しています。 よろしくお願いいたします。 サラス。 Re: How do I implement Secure Boot on the i.MX95? こんにちは、 i.MX95でセキュアブートに取り組んでいる他のユーザーのために、実用的な参考情報としてここに追加しておきます。 前述の通り、i.MX95はi.MX8MPで使われているHABv4方式ではなくAHABを使用しているため、署名と起動認証のワークフローが異なります。 RidgeRunでは、Yoctoを使ったi.MX95へのSecure Boot実装に関するステップバイステップガイドを公開しており、AHABキー生成、SRKヒューズテーブル生成、NXPのCSTによるイメージ署名、署名付きブートイメージの検証をカバーしています。また、PKCS#11とSoftHSM2を使用した代替署名ワークフローも含まれています。 ガイドはToradex Verdin i.MX95を参考プラットフォームとして使用し、セキュリティヒューズのプログラミングやデバイスのクローズを行わず、開発段階での署名と検証に焦点を当てています。 NXPのドキュメントに加えて実践形式の参考資料を探している方は、こちらでご覧いただけます: https://developer.ridgerun.com/wiki/index.php/RidgeRun_Platform_Security_Manual/Getting_Started/NXP_i.MX95/Yocto_Build_Process/Secure_Boot i.MX95のセキュリティに取り組んでいる方々の参考になれば幸いです! よろしくお願いいたします。
View full article
i.MX 93 AHAB Keys revocation procedure doubts Hello, we are working on SRK revocation for an i.MX93 product that is updated over the air, and we could not find a complete description of the procedure. We have read the thread imx93: SRK revocation (https://community.nxp.com/t5/i-MX-Processors/imx93-SRK-revocation/td-p/1827004), the Reference Manual (§9.5.1.3.2.3, SRK revoke) and AN14954, and we would like to confirm a few points. 1. ahab_commit in the field In the thread above, a container signed with SRK2 and Revocations = 0x1 did not revoke SRK1 until ahab_commit 0x10 was run. We would like to understand how the commit is meant to be used on devices that receive later updates: - Is it enough to run the commit once, after the container carrying the revoke mask has been authenticated? - Or can the commit be left permanently in the boot command once at least one key has been revoked, so that any build installed afterwards applies the revocation? Is it safe and without effect when there is nothing new to commit? - Must the containers of later builds keep the same srk_revocations value (the Reference Manual says the ELE checks that the revoke bits in the container match what is already set in the fuses), and which containers have to carry it (the boot container and the OS container)? 2. Multiple or cross revocation A container signed with one SRK can revoke a different one (as in the thread). Can the revoke mask contain several bits, including all the other SRKs? Is there a check in the ELE that prevents a container signed with a compromised SRK from revoking the remaining ones, or is this something that has to be handled by key management? 3. Checking the revocation state Is there a supported way to know which SRKs are revoked, from U-Boot or from Linux? With fuse sense most words beyond bank 6 return ERROR on our board, and the nvmem interface shows zeros for them. Would a functional check (authenticating a small container signed with each SRK and looking at the ELE events) be a reasonable approach? 4. fuse override for tests From AN14954 we understood that the shadow fuses can be overridden in OEM Open without burning the e-fuses. Does the ELE use the shadow value of the SRK hash fuses when authenticating containers, so that the signing chain can be tested this way without writing the hash? And is there any way to simulate a revocation with this mechanism? 5. SRK table after closing The hash covers the whole SRK table (4 keys). Once the hash is written, can the table still be changed (guess no since they are fused), even for positions that were left empty at the time? So basically, is it possible to only write 2 keys and add 2 later? We understand that part of the fuse information is covered by the Security Reference Manual under NDA. If so, a pointer to the relevant document or section, or even a high-level description of the procedure, would already help a lot. Given the upcoming Cyber Resilience Act, key revocation is going to become a standard requirement for many products, so a clear public description would be very valuable Thanks in advance
View full article
i.MX 93 AHABキーの失効手続きに関する疑問 こんにちは、 現在、i.MX93製品のSRK取り消しを進めており、無線で更新されていますが、手順の完全な説明は見つかりませんでした。私たちはThread imx93を読みました:SRK取り消し(https://community.nxp.com/t5/i-MX-Processors/imx93-SRK-revocation/td-p/1827004)、リファレンス・マニュアル(§9.5.1.3.2.3、SRK取り消し)、およびAN14954。いくつかの点を確認したいと思います。 1. 現場でのahab_commit 上記のThreadでは、SRK2とRevocations = 0x1で署名されたコンテナは、ahab_commit 0x10実行されるまでSRK1を取り消しませんでした。私たちは、コミットが後のアップデートを受けるデバイスでどのように使われるのかを理解したいと考えています。 - リヴォークマスクを搭載したコンテナが認証された後、コミットを一度実行するだけで十分でしょうか? - あるいは、少なくとも1つのキーが取り消された後も、コミットをブートコマンドに永久に残し、SO、その後インストールされたビルドがその取り消しを適用できるようにできますか?新しい行動がなければ安全で効果がないのでしょうか? - 後のビルドのコンテナは同じsrk_revocations値を保持しなければなりませんか?(リファレンス・マニュアルによると、ELEはコンテナ内のリボークビットがヒューズに既に設定されているものと一致しているかを確認します)、どのコンテナ(ブートコンテナとOSコンテナ)がそれを運ぶ必要がありますか? 2. 複数またはクロスの取り消し 1つのSRKで署名されたコンテナは、別のSRKを取り消すことができます(Threadのように)。リヴォークマスクは他のすべてのSRKを含めて複数のビットを含めることはできますか?ELEに、侵害されたSRKで署名されたコンテナが残りのSRKを取り消すのを防ぐチェック機能はありますか?それとも鍵マネジメントが処理しなければならないのでしょうか? 3. 取り消し状態の確認 どのSRKが取り消されたか、U-BootからかLinux側で確認できるサポートされた方法はありますか?ヒューズセンスを使うと、バンク6以降のほとんどのワードはボード上でエラーを返し、nvmemインターフェースではそれらに対してゼロが表示されます。機能チェック(各SRKに署名された小さなコンテナを認証し、ELEイベント情報を確認する)は妥当な方法でしょうか? 4. 試験用のヒューズオーバーライド AN14954から、OEM Openではシャドウヒューズを上書きしてもeヒューズを焼き切れないと分かりました。ELEはコンテナ認証時にSRKハッシュヒューズのシャドウ値を使い、ハッシュを書かずにこの方法で署名チェーンをテストできるのでしょうか?この仕組みを使って、免許の取り消しをシミュレートする方法はありますか? 5. 閉鎖後のSRKテーブル このハッシュはSRKテーブル全体(4つのキー)をカバーしています。ハッシュが書き込まれた後、テーブルは(フュージョンされているのでおそらく無理です)変更できますか?その時点で空いた位置でも?SO、2つのキーだけを書いて後で2つ追加することは可能でしょうか? 信管情報の一部はNDAに基づくセキュリティリファレンスマニュアルでカバーされていると理解しています。もしそうなら、関連する文書やセクションへのポインタ、あるいは手順の高レベルの説明があれば、すでに大いに役立ちます。今後のサイバーレジリエンス法(Cyber Resilience Act)を踏まえ、キーの取り消しは多くの製品で標準的な要件となるため、明確な公開説明は非常に価値があります 前もって感謝します
View full article
KW47 BLEアドバタイジング中のディープスリープ - 推奨アプローチと参考例 NXPサポートの皆様、 KW47の低電力機能についてお伺いしたいのですが。 環境 MCU:KW47 SDK:SDK_26_03_00_KW47-EVK IDE:IAR Embedded Workbench RTOS: FreeRTOS ハードウェア: カスタムボード 私たちの目標は、BLEペリフェラルとして運用する際の消費電力を削減することです。 意図した動作を示す図を添付しました。 この図は概念的な図解であり、実際の現在の消費量を表すものではないことにご注意ください。これは、ディープスリープ作戦とBLE関連イベント情報との期待される関係を示すことを目的としています。 意図された動作は以下のとおりです。 ディープスリープは低電力モードとして使用されます。 広告の送信はBLEスタックとSDKによって処理されます。 起動直後から低消費電力動作が有効になります。 FreeRTOSがアイドル状態になると、デバイスは自動的にディープスリープ状態に入ります。 BLEペリフェラルとして動作し、広告を続けている間、CPUはアイドルになるとディープスリープに入ります。 デバイスはBLEスタックプロセッシングが必要な場合のみ、例えば広告イベント情報、接続リクエスト、接続イベント情報の際にのみ起動し、必要なプロセッシングが完了するとディープスリープに戻ります。 Low Power Application Developers Guideによると、Bluetooth LEアプリケーションは広告中でもディープスリープを利用できるようです。しかし、この実装の参照としてどのSDKサンプルプロジェクトを使うべきかは判断できませんでした。 以下の点についてアドバイスいただけますか? 上記のような動作を実現するための推奨されるアプローチは何ですか? どのSDK例プロジェクトを参考にすべきでしょうか? 広告中に自動的にスリープ/ディープスリープに入り、BLEイベント情報が発生すると自動的に起きる例はありますか? BLE接続確立時の推奨される動作は何ですか?接続間隔の間にディープスリープに入るのが推奨されますか?それともコネクテッド中はデバイスはアクティブのままにすべきでしょうか? 再開まで今しばらくお待ちください。 よろしくお願いいたします。     プロトコル:Bluetooth Re: KW47 Deep Sleep During BLE Advertising - Recommended Approach and Reference Example こんにちは、ハビブさん。 情報提供とAN14554の共有、ありがとうございます。 特に3.2.1および4.2.2.6のセクションを確認し、BLE接続時の推奨される低消費電力ソフトウェア構成とディープスリープの挙動をよりよく理解します。 サポートいただき感謝します。 よろしくお願いします、 ヒヤマ Re: KW47 Deep Sleep During BLE Advertising - Recommended Approach and Reference Example こんにちは、 @hyama さん。 最適な低消費電力プロファイルを実現しつつ、高いシステム性能を維持するための設定手順については、 AN14554を参照してください。また、KW47の電流消費量を測定するために使用された測定設定と手順についても説明しています。 具体的には、セクション3.2.1は低消費電力動作のための推奨ソフトウェア構成を説明しています。このサンプルは、ベアメタル版とFreeRTOS版の両方で利用可能です。また、4.2.2.6項では接続モードの測定について説明し、接続間隔中にデバイスがディープスリープ状態に入ることを確認しています。 BR、 ハビブ
View full article
MCUXpresso Tooltime Episodes NXP LinkedIn Live series Tool Time: practical embedded development, on demand Catch up on conversations and demonstrations featuring NXP development tools, SDK workflows, board enablement, debugging, visualization, configuration and user-interface design. Browse past episodes See how the MCUXpresso ecosystem comes together Tool Time brings developers closer to the software and workflows used to build with NXP microcontrollers. Across the series, the episodes cover MCUXpresso SDK releases, VS Code integration, CMake and Kconfig projects, Configuration Tools, GUI Guider, FreeMASTER, LinkServer, Serial Memory Tool, MCUXpresso Installer, cloud connectivity and FRDM board expansion. Use this replay library to explore each topic, meet the hosts and guests, and go directly to the available LinkedIn episode. What the series provides Focused sessions on MCUXpresso tools and embedded-development workflows Topics spanning setup, configuration, build systems, debug, visualization and prototyping Conversations with NXP specialists and ecosystem guests Direct links to rewatch each available episode on LinkedIn Watch past episodes Choose an episode and select Watch on LinkedIn. Newest episodes are listed first. NOVEMBER 2026   |   EMBEDDED UI with GUI GUIDER From Prompt to Embedded UI with GUI Guider Describe the GUI you want and let AI help bring the concept to life. Host: Mike Susen   Guest: Zhenhua Luo Watch on LinkedIn OCTOBER 2026   |   AGENTIC AI Introducing our new Agentic AI Toolkit Explore how AI agents can discover, understand and use products to help improve customer enablement. Host: Kyle Dando   Guest: Marius-Lucian Andrei Watch on LinkedIn SEPTEMBER 2026   |   HARDWARE EXPANSION Adding a click shield to a FRDM board (G-Knob) A Tool Time episode focused on adding a G-Knob click shield to a FRDM board. Host: Kyle Dando   Guest: Patrik Fillner Watch on LinkedIn AUGUST 2026   |   INSTALLATION MCUXpresso Installer A focused discussion and demonstration of MCUXpresso Installer. Host: Jose Ocampo Hernandez   Guest: Alexandra Maracine Watch on LinkedIn JULY 2026   |   SERIAL MEMORY Serial Memory Tool A Tool Time session featuring the Serial Memory Tool. Host and guest: Patrik Fillner Watch on LinkedIn JUNE 2026   |   DEBUG LinkServer A focused episode covering LinkServer. Host: Kyle Dando   Guest: Cristian Lupascu Watch on LinkedIn MAY 2026   |   DATA VISUALIZATION FreeMASTER data visualization A Tool Time session focused on FreeMASTER data visualization. Host: Kyle Dando   Guest: Patrik Fillner Watch on LinkedIn APRIL 2026   |   EMBEDDED GUI GUI Guider A focused discussion and demonstration of GUI Guider. Host: Kyle Dando   Guest: Mike Susen Watch on LinkedIn MARCH 2026   |   CONFIGURATION MCUXpresso Configuration Tools A Tool Time episode focused on MCUXpresso Configuration Tools. Host: Patrik Fillner   Guest: Petr Hradsky Watch on LinkedIn FEBRUARY 2026   |   CLICK BOARDS 6 clicks A Tool Time episode titled “6 clicks.” Host: Kyle Dando   Guest: Stella Or Watch on LinkedIn JANUARY 2026   |   BUILD CONFIGURATION CMake and Kconfig projects on FRDM-MCXN947 A session on CMake and Kconfig projects using the FRDM-MCXN947. Host: Kyle Dando   Guest: Jose Ocampo Hernandez Watch on LinkedIn DECEMBER 2025   |   CLOUD CONNECTIVITY Bluetooth to Cloud on MCX W71 and RW612 A Bluetooth-to-cloud project running on the MCX W71 and RW612. Host: Kyle Dando   Guest: Chris Gammell, Golioth Watch on LinkedIn NOVEMBER 2025   |   RELEASE HIGHLIGHTS SDK 25.10, VS Code and Configuration Tools A session covering the 25.10 SDK release, VS Code integration and streamlined Configuration Tools. Host: Kyle Dando   Guest: Jose Ocampo Hernandez Watch on LinkedIn OCTOBER 2025   |   SERIES OVERVIEW MCUXpresso IDEs, SDK, Configuration and Security A session covering MCUXpresso IDEs, SDK, Configuration Tools and security tooling. Host: Kyle Dando Replay link not listed Episode links open LinkedIn in a new browser tab. LinkedIn sign-in may be required to view some replays. Application Code Hub FreeMASTER LinkServer MCUXpresso Config Tools MCUXpresso for VS Code MCUXpresso SDK
View full article
S32DS 3.5のライセンス延長申請 こんにちは、 私のS32 Design Studioのライセンスがもうすぐ切れる。延長を手伝ってもらえますか? アクティベーションID: 5E5E-87D6-4F85-9A22 バージョン: 3.5 よろしくお願い申し上げます。 製品に適用されるライセンス: バージョン説明 3.5S32 プラットフォーム v.3.5 Design Studio ライセンス数:1 フルフィルメントID:201997687 有効期限:2026年11月4日 製品:S32 プラットフォーム v.3.5用 S32 Design Studio 機械: 6EF78E1197D8A04DBC0B058E7DE51D3F39A0F67C アクティベーションコード:5E5E-87D6-4F85-9A22
View full article
FS26 can't enter LPOFF/StandBy state We use the infineon MCU TC37x With FS26 SBC. when request power down, SBC can't entry LPOFF/StandBy mode from Normal mode. the request command is normal, but sbc still in normal mode. I want to know which conditions prevent the state transform? Re: FS26 can't enter LPOFF/StandBy state Hi Liu, Please check the following: 1. Confirm the fail-safe state before requesting low-power mode The low-power transition shown in the state diagram starts from the fail-safe Normal mode. Before sending the request, please read: FS_STATES at address 0x57 FS_DIAG_SAFETY1 at address 0x54 FS_DIAG_SAFETY2 at address 0x55 FS_OVUV_REG_STATUS at address 0x50 FS_STATES[4:0] = 0x0B indicates that the fail-safe state machine is in Normal mode. The diagnostic registers can also show whether a watchdog, SPI, FCCU, ERRMON, BIST or voltage-monitoring event has occurred. 2. Verify the complete two-step command sequence For LPOFF mode, write the following values to FS_LP_REQ at address 0x58: FS_LP_REQ[7:0] = 0xA5, which requests Pre-LPOFF mode. FS_LP_REQ[7:0] = 0x5A, which completes the transition to LPOFF mode. For Standby mode, the corresponding sequence is: 0xAA, which requests Pre-Standby mode. 0x55, which completes the transition to Standby mode. The second command must be received within 10 ms of the first. Please send the two commands back-to-back and confirm that both SPI frames use the correct fail-safe register selection, address, CRC and number of clock cycles. If the second command is missing, invalid or not received within the required interval, the requested low-power transition will not be completed.  3. Check for SPI errors Immediately after the first request, check FS_DIAG_SAFETY1 for: SPI_FS_CLK SPI_FS_REQ SPI_FS_CRC These bits indicate an incorrect number of SPI clocks, an invalid fail-safe SPI access, or a CRC error. Any of these conditions can explain why the low-power command was not accepted. 4. Exclude an immediate wake-up An enabled wake-up source that is already active, or that becomes active during the transition, can make the device wake up immediately and therefore appear to remain in Normal mode. Please check M_WIO_CFG for the enabled wake-up sources and their configured polarities: WAKE1 and WAKE2 GPIO1 and GPIO2 LDT SPI CSB transition In particular, if CSBWUEN = 1, subsequent SPI activity can wake the FS26 through a high-to-low CSB transition. After the device wakes up, M_WIO_FLG.WUEVENT[3:0] can be read to identify the detected wake-up source. Finally, please note that VPRE remains enabled in Standby mode and LDO1 or LDO2 may also remain enabled depending on the OTP configuration. Therefore, the presence of these rails alone does not prove that the FS26 remained in Normal mode. In LPOFF, the regulators are switched off and RSTB is low. BRs, Tomas
View full article
country of origin of S32Z280ABCK0MJFT which is the COO of S32Z280ABCK0MJFT Re: country of origin of S32Z280ABCK0MJFT Please, contact export control team at: [email protected] for more information.
View full article
MKW38 BLE Scan not working when long time test Dear Christine Li and NXP team   Thank your for support   Following up on the BLE scan issue we reported earlier, we would like to share additional analysis results from our long-run test and ask a few questions.     1. Summary During continuous scanning, the controller sometimes stops delivering any LE Advertising Reports to the host. During this period, the LL registers show that scanning is still active (SCAN_STATUS.Scan_on = 1), but no packet is received at all. PKT_RSSI_STATUS and CH_ADDR do not change. In most cases the controller recovers by itself within 1 s – 2.5 min. In one case it never recovered (more than 8 hours, until the log ended). We were informed that SDK 2.6.916 fixes this issue. However, the issue was reproduced within about one week with the SDK 2.6.916 libraries. Test conditions   Units / duration: 5 units, approx. 14.6 days each, no MCU reset during the test Controller library: imported in Apr 2023, 2.6.615 or later (contains Controller_SetPeripheralDiscThreshold(); exact version unknown) lib_ble_kw38a4_controller_gcc.a, 617,384 bytes, MD5 prefix 50417a8d65 Separate test: SDK 2.6.916 libraries – same symptom reproduced within about 1 week Scan parameters: Active scan, interval 0x0011 (10.625 ms), window 0x0008 (5 ms) Filter policy: accept all, duplicate filtering disabled Continuous scanning (gGapScanContinuously_d), extended scanning (scanning PHY register 0x14E = 0x0005) Scan start/stop: started once after boot; no scan stop/start during the test Environment: approx. 75–110 advertising reports per second in normal operation Application-side register access: Read-only polling of LL registers every 1 s (0x01C, 0x01E, 0x064, 0x0C4, 0x0D2, 0x0D4, 0xF28) One 16-bit read of INIT_SCN_ADV_RX_FIFO (0x4008007C) every 180 s for diagnostics No LL register is written by the application 3. How we detect the issue We count advertising reports at each layer every second: L1: LE (Extended) Advertising Report events passed from the controller to the host. Counted in a wrapper around Ble_HciRecv() registered with Controller_Init(). L2: gDeviceScanned_c / gExtDeviceScanned_c delivered to the application callback. L4: Reports processed by the application task. When the issue occurs, all counters stop at L1. The controller stops generating advertising reports. Host and application are not involved: Ble_HciRecv() reports no failure at that time. Application message allocation does not fail. The application queue is empty. 4. Statistics (5 units, approx. 14.6 days) Unit #1: 8 stall events, 8 recovered (duration 11 – 35 s) Unit #2: 9 stall events, 8 recovered (duration 11 – 159 s); last event not recovered (> 8 h) Unit #3: 7 stall events, 7 recovered (duration 11 – 78 s) Unit #4: 2 stall events, 2 recovered (duration 11 – 30 s) Unit #5: 3 stall events, 3 recovered (duration 12 – 14 s) Total: 29 stall events, 28 recovered (Duration includes the 10 s detection time.) Key observation: In all 28 recovered events, the last received packet before the stall was on a secondary advertising channel. The CH_ADDR RX index was one of 0x06, 0x0A, 0x0C, 0x0E, 0x10, 0x12, 0x14, 0x16, 0x1E, 0x22, 0x26, 0x28, 0x2A, 0x30, 0x3E, 0x4A. In most cases PKT_PAYLOAD_STATUS = 0x0007, i.e. a 7-byte payload. This suggests the stall starts right after receiving an AUX packet. In the non-recovered event, the last received packet was on primary channel 37 (CH_ADDR = 0x0018, PKT_PAYLOAD_STATUS = 0x0025). 5. Register snapshot of the non-recovered event (unit #2)  -SCAN_STATUS(0x01C) = 0x0900 (Scan_on = 1, no pending interrupt)  -SCAN_NEXT_INSTANT(0x01E) = 0xB4B7  -REF_CLK(0x064) = 0xB4AD  -CH_ADDR(0x0C4) = 0x0018  -PKT_PAYLOAD_STATUS(0x0D2) = 0x0025  -PKT_RSSI_STATUS(0x0D4) = 0x3FB3  -SCAN_SYNC_RX_PKT_CNT(0xF28) = 0x0000   SCAN_STATUS, CH_ADDR, PKT_RSSI_STATUS and SCAN_SYNC_RX_PKT_CNT stayed unchanged for more than 8 hours. The L1 report counter also stayed constant during this period. 6. Release note review The only scan-related item in SDK 2.6.212 – 2.6.916 is in 2.6.815. Link Layer fixes/changes by version: 2.6.212 (ble_controller 1.6.11.1): No changes 2.6.415 (2022-05, 1.6.14): Host fixes only 2.6.615 (2023-02, 1.6.14.1): Premature ACL termination option (Controller_SetPeripheralDiscThreshold) 2.6.715 (2023-03, 1.6.14.3): MD bit handling 2.6.815 (2023-05, 1.6.14.4): Channel map fix; “Fixed a Scan issue causing Advertising to be missed for some cases.” 2.6.915 (2023-09, 1.6.14.5): EnhancedNotification alignment fix; Autonomous Length Procedure disabled 2.6.916 (2023-10, 1.6.14.6): Return unmapped ChannelNumber in EnhancedNotification (Algo #1) 7. Questions Is this a known issue of the KW38 BLE controller? Is it related to the 2.6.815 fix “Scan issue causing Advertising to be missed”? If so, could you describe the exact condition that was fixed? Can extended scanning (following an AUX pointer to a secondary channel) put the LL scanner into a state where it no longer receives on any channel while SCAN_STATUS.Scan_on stays 1? Since the issue was reproduced with SDK 2.6.916, is there a newer controller library or patch that addresses it? What is the recommended way to detect and recover from this state at application level? For example: Is Gap_StopScanning() / Gap_StartScanning() sufficient? Is a controller reset required (e.g. HCI Reset or the LL SOFT_RESET command)? Is there any LL status register we should check? Would disabling extended scanning (legacy scanning only) avoid this issue? Is it allowed to read INIT_SCN_ADV_RX_FIFO (0x4008007C) from the application for diagnostics? Could this read affect the controller’s FIFO handling? Re: MKW38 BLE Scan not working when long time test Key observations: [modified] -In all 28 recovered events, the last received packet was on a secondary advertising channel, and in most cases PKT_PAYLOAD_STATUS = 0x0007 (7-byte payload, typical of an extended advertising PDU carrying an AuxPtr). This suggests these stalls start while the scanner follows an AUX pointer. -The non-recovered event (unit #2) has a different signature: the last received packet was on primary channel 37 with a 37-byte payload (PKT_PAYLOAD_STATUS = 0x0025), i.e. most likely a legacy advertising PDU. We found no indication of extended advertising involvement in this case. INIT_SCN_ADV_RX_FIFO read as 0 every 3 minutes during the stall, and the controller did not recover for more than 8 hours. Re: MKW38 BLE Scan not working when long time test Note: In an earlier firmware, the application periodically wrote 0xFFFF to SCAN_INTR_CLEAR (0x4008001C). In that firmware we observed a different stall where INIT_SCN_ADV_RX_FIFO still held data while SCAN_SYNC_RX_PKT_CNT was 0, and reading 0x4008007C once via J-Link immediately recovered scanning. We have since removed that write. The statistics in this report are from the current firmware, where the FIFO reads 0 during the stall and reading it does not affect recovery. Re: MKW38 BLE Scan not working when long time test Hi, @JungkyuHan1  Thanks for creating new case to us. I will check the detailed info and updates to you ASAP. BR, Christine. Re: MKW38 BLE Scan not working when long time test Hi, @JungkyuHan1  Please allow me some more time to reply to you.  I need to check some points with our internal team. BR, Christine. Re: MKW38 BLE Scan not working when long time test Hi, @JungkyuHan1  If I am correct, I received your email that mentioned " We have conducted the BLE Scan test With the SDK 2.6.916. It works pretty well. There was no scan error for more than 8days." in the December of 2025.  But now you meet this issue: "However, the issue was reproduced within about one week with the SDK 2.6.916 libraries." May I ask whether have any test differences between these OK and NOK cases? If we know the differences, it will be really helpful for us to track it further. For your questions: Is this a known issue of the KW38 BLE controller? Is it related to the 2.6.815 fix “Scan issue causing Advertising to be missed”? If so, could you describe the exact condition that was fixed? ==>[Christine]: As our communicated before, yes, it is a known issue. And as we know,  the 2.6..916 is the version I know so far that at least have a work around can help on scan issue. As far as I know, the scan issue is because an conflict on scan FIFO, so it needs flush the scan FIFO.  Can extended scanning (following an AUX pointer to a secondary channel) put the LL scanner into a state where it no longer receives on any channel while SCAN_STATUS.Scan_on stays 1? Since the issue was reproduced with SDK 2.6.916, is there a newer controller library or patch that addresses it? ==>[Christine]:Sorry, no we do not have other newer SDK release which fixed this issue than SDK 2.6.916. What is the recommended way to detect and recover from this state at application level? For example: Is Gap_StopScanning() / Gap_StartScanning() sufficient? Is a controller reset required (e.g. HCI Reset or the LL SOFT_RESET command)? Is there any LL status register we should check? ==>[Christine]: The workaround you may need manually add in applicaiton code as below there should have an function ll_flush_adv_rx_fifo(). The code by this function does not exist in applicaiton code, so you need use "extern" declare it . After externing this function, the input parameter and return value are both void, and then call: 1. Call before stopping scan every time 2. If the device is not scanned for a long time, stop scanning and call it again, than start scaning. Would disabling extended scanning (legacy scanning only) avoid this issue? Is it allowed to read INIT_SCN_ADV_RX_FIFO (0x4008007C) from the application for diagnostics? Could this read affect the controller’s FIFO handling? ==>[Christine]:For these 2 questions, let me check further then reply to you.   BR, Christine. Re: MKW38 BLE Scan not working when long time test Hi Christine, Thank you for your reply. Regarding the difference between the OK case (December 2025) and the NOK case: We found a mistake in our SDK 2.6.916 migration. We are now re-testing with the correct SDK 2.6.916 libraries. The test setups were also different: Previous test (OK): 3 units (2 sample units and 1 development unit), without antennas. Current test: 5 new mass-production units, all with antennas installed. We also have some additional questions: Is the 2.6.815 fix “Fixed a Scan issue causing Advertising to be missed for some cases” the same fix as the scan FIFO lockup workaround (ll_flush_adv_rx_fifo()) in SDK 2.6.916? After the flush, the scan is restarted with the legacy START_SCAN command (0x42). When extended scanning is enabled, does AUX (secondary channel) reception resume correctly after this restart? Is it safe to call ll_flush_adv_rx_fifo() directly from an application task while the controller ISR is running? Is there any concurrency or synchronization issue with the controller’s scan interrupt handling? In the SDK 2.6.615 controller library, what is the meaning of bit 0 of ll_self_device_data[18]? (We are considering applying the same flush manually on 2.6.615.) Best regards, Jungkyu Han Re: MKW38 BLE Scan not working when long time test Hi, @JungkyuHan1  Thanks for the info. I am still checking with our internal team to get the answers for your questions. Once have any updates, I will let you know. BR, Christine. Re: MKW38 BLE Scan not working when long time test Hi, @JungkyuHan1  Below is our internal team's reply, for your referrence. 1. Would disabling extended scanning (legacy scanning only) avoid this issue? [NXP]: The answer is no, although we not test this case, but it should no relate to extended scanning. 2.Is it allowed to read INIT_SCN_ADV_RX_FIFO (0x4008007C) from the application for diagnostics? Could this read affect the controller’s FIFO handling? [NXP]: It's better not read from applicaiton side in any time, you can stop scanning first, then read it and start scanning again 3.Is the 2.6.815 fix “Fixed a Scan issue causing Advertising to be missed for some cases” the same fix as the scan FIFO lockup workaround (ll_flush_adv_rx_fifo()) in SDK 2.6.916? [NXP]: I'm not sure for now, need some time to investigate it. 4.After the flush, the scan is restarted with the legacy START_SCAN command (0x42). When extended scanning is enabled, does AUX (secondary channel) reception resume correctly after this restart? [NXP]: Yes. But you need to follow this process, stop scanning > ll_flush_adv_rx_fifo() > start scaning again. 5.Is it safe to call ll_flush_adv_rx_fifo() directly from an application task while the controller ISR is running? [NXP]: As mentioned in above, it better call ll_flush_adv_rx_fifo() when you stop the scanning 6.Is there any concurrency or synchronization issue with the controller’s scan interrupt handling? [NXP]: what do you mean concurrency or synchronization issue ? can you clarify it? If do as mentioned above, stop scan and flush, then re-start the scan, I do not think it will causing any concurrency or synchronization issue.  7.Can extended scanning (following an AUX pointer to a secondary channel) put the LL scanner into a state where it no longer receives on any channel while SCAN_STATUS.Scan_on stays 1? [NXP]: So far, we not observe such issue. BR, Christine. Re: MKW38 BLE Scan not working when long time test Hi, @JungkyuHan1  3.Is the 2.6.815 fix “Fixed a Scan issue causing Advertising to be missed for some cases” the same fix as the scan FIFO lockup workaround (ll_flush_adv_rx_fifo()) in SDK 2.6.916? [NXP]: Not same, but have correlation, the fix in 2.6.815 not enough for scan FIFO lockup workaround, so that fix no completely fix the scan fifo issue, so better add that workaround. Please let me know if still have any other concerns in this thread. BR, Christine.
View full article
MKW38 BLE 扫描在长时间测试后无法工作 尊敬的 Christine Li 和 NXP 团队   感谢您的支持   针对我们之前报告的 BLE 扫描问题,我们想分享我们长期测试的更多分析结果,并提出一些问题。     1. 总结 在连续扫描期间,控制器有时会停止向主机发送任何 LE 广告报告。 在此期间,LL 寄存器显示扫描仍在进行中(SCAN_STATUS.Scan_on = 1),但根本没有收到任何数据包。PKT_RSSI_STATUS 和 CH_ADDR 不会改变。 大多数情况下,控制器会在 1 秒至 2.5 分钟内自行恢复。其中一次,它始终未能恢复(超过 8 小时,直到日志结束)。 我们获悉 SDK 2.6.916修复了此问题。但是,使用 SDK 2.6.916 库大约一周后,该问题再次出现。 测试条件   单元数/持续时间:约 5 个单元每次测试持续14.6天,测试期间MCU未发生RESET。 控制器库:于 2023 年 4 月导入,版本为 2.6.615 或更高版本(包含 Controller_SetPeripheralDiscThreshold();确切版本未知) lib_ble_kw38a4_controller_gcc.a,617,384 字节,MD5 前缀 50417a8d65 单独测试: SDK 2.6.916图书馆 – 大约一周内出现相同症状。 扫描参数: 活动扫描,间隔 0x0011 (10.625 毫秒),窗口 0x0008 (5 毫秒) 筛选策略:全部接受,禁用重复项筛选 连续扫描(gGapScanContinuously_d),扩展扫描(扫描 PHY 寄存器 0x14E = 0x0005) 扫描启动/停止:启动后启动一次;测试期间不进行扫描停止/启动。 环境:约正常运行时每秒发送 75-110 条广告报告 应用层寄存器访问: 每隔 1 秒对 LL 寄存器进行只读轮询(0x01C、0x01E、0x064、0x0C4、0x0D2、0x0D4、0xF28) 每隔 180 秒对 INIT_SCN_ADV_RX_FIFO (0x4008007C) 进行一次 16 位读取,用于诊断。 应用程序不会写入任何LL注册表。 3. 我们如何检测问题 我们每秒都会统计每一层的广告报告数量: L1: LE(扩展)广告报告事件从控制器传递到主机。在通过 Controller_Init() 注册的 Ble_HciRecv() 的包装器中进行计数。 L2: gDeviceScanned_c / gExtDeviceScanned_c 已传递给应用程序回调。 L4:应用程序任务处理的报告。 当出现问题时,所有计数器都停止在 L1。控制器停止生成广告报告。主机和应用程序不参与其中: 当时ble_HciRecv()没有报告任何故障。 应用程序消息分配不会失败。 应用程序队列为空。 4. 统计学(5 个单元,约 100 个学分)14.6天) 单元 1:8 次停滞事件,8 次恢复(持续时间 11 – 35 秒) 单元 #2:9 次失速事件,8 次已恢复(持续时间 11 – 159 秒);最后一次失速事件未恢复(> 8 小时) 单元#3:7次停滞事件,7次恢复(持续时间11-78秒) 单元#4:2次停滞事件,2次恢复(持续时间11-30秒) 单元#5:3次停滞事件,3次恢复(持续时间12-14秒) 总计:29起停滞事件,28起已恢复 (持续时间包含10秒检测时间。) 关键观察结果: 在所有 28 个恢复事件中,停滞之前接收到的最后一个数据包是在辅助广告频道上。CH_ADDR RX 索引为 0x06、0x0A、0x0C、0x0E、0x10、0x12、0x14、0x16、0x1E、0x22、0x26、0x28、0x2A、0x30、0x3E、0x4A 之一。大多数情况下,PKT_PAYLOAD_STATUS = 0x0007,即 7 字节有效载荷。这表明,在接收到 AUX 数据包后,故障立即开始出现。 在未恢复的事件中,最后一个接收到的数据包位于主通道 37上(CH_ADDR = 0x0018,PKT_PAYLOAD_STATUS = 0x0025)。 5. 注册未恢复事件的快照(单元 #2) -SCAN_STATUS(0x01C) = 0x0900 (Scan_on = 1,无待处理的中断) -SCAN_NEXT_INSTANT(0x01E) = 0xB4B7 -REF_CLK(0x064) = 0xB4AD -CH_ADDR(0x0C4) = 0x0018 -PKT_PAYLOAD_STATUS(0x0D2) = 0x0025 -PKT_RSSI_STATUS(0x0D4) = 0x3FB3 -SCAN_SYNC_RX_PKT_CNT(0xF28) = 0x0000   SCAN_STATUS、CH_ADDR、PKT_RSSI_STATUS 和 SCAN_SYNC_RX_PKT_CNT超过 8 小时保持不变。在此期间,L1报告计数器也保持不变。 6. 版本说明回顾 SDK 2.6.212 中唯一与扫描相关的项– 2.6.916 包含在 2.6.815 中。链路层各版本修复/更改: 2.6.212(ble_controller 1.6.11.1):无变化 2.6.415(2022-05,1.6.14):仅主机修复 2.6.615(2023-02,1.6.14.1):提前终止 ACL 选项(Controller_SetPeripheralDiscThreshold) 2.6.715(2023-03,1.6.14.3):MD 位处理 2.6.815(2023-05,1.6.14.4):频道映射修复; “修复了扫描问题,该问题会导致某些情况下广告无法显示。” 2.6.915(2023-09,1.6.14.5):增强通知对齐修复;自主长度程序已禁用 2.6.916(2023-10,1.6.14.6):在增强通知中返回未映射的 ChannelNumber(算法 #1) 7. 问题 这是KW38 BLE控制器的已知问题吗?它与 2.6.815 有关吗?修复“扫描问题导致广告漏播”?如果是这样,您能否详细描述一下具体修复了什么问题? 扩展扫描(跟随 AUX 指针到辅助通道)是否会导致 LL 扫描器进入一种状态,即当SCAN_STATUS.Scan_on保持为 1时,它不再接收任何通道的信号? 由于该问题已在 SDK 2.6.916 中重现,是否有更新的控制器库或补丁可以解决该问题? 在应用层,检测和恢复这种状态的推荐方法是什么?例如: Gap_StopScanning() / Gap_StartScanning() 是否足够? 是否需要RESET控制器(例如,HCI RESET 或 LL SOFT_RESET 命令? 是否有任何LL状态登记册需要查阅? 禁用扩展扫描(仅使用传统扫描)是否可以避免这个问题? 是否允许从应用程序中读取 INIT_SCN_ADV_RX_FIFO (0x4008007C) 以进行诊断?这次读取操作是否会影响控制器的 FIFO 处理? Re: MKW38 BLE Scan not working when long time test 主要观察结果:[已修改] -在所有 28 个恢复事件中,最后一个接收到的数据包位于辅助广告通道上,并且在大多数情况下,PKT_PAYLOAD_STATUS = 0x0007(7 字节有效载荷,是携带 AuxPtr 的扩展广告 PDU 的典型值)。这表明这些卡顿现象是在扫描仪跟随 AUX 指针时开始发生的。 -未恢复的事件(单元 #2)具有不同的签名:最后一个接收到的数据包在主通道 37 上,有效载荷为 37 字节(PKT_PAYLOAD_STATUS = 0x0025),即很可能是一个传统的通告 PDU。我们没有发现任何迹象表明本案涉及大量广告宣传。在系统卡死期间,INIT_SCN_ADV_RX_FIFO 每 3 分钟读取一次为 0,并且控制器超过 8 小时没有恢复。 Re: MKW38 BLE Scan not working when long time test 注意:在早期固件中,应用程序会定期向 SCAN_INTR_CLEAR (0x4008001C) 写入 0xFFFF。 在该固件中,我们观察到不同的停滞情况,即 INIT_SCN_ADV_RX_FIFO 仍然保存着数据,而 SCAN_SYNC_RX_PKT_CNT 为 0,通过 J-Link 读取一次 0x4008007C 后,扫描立即恢复。 我们已删除该条记录。本报告中的统计数据来自当前固件,其中 FIFO 在卡顿期间读取 0,读取 0 不会影响恢复。 Re: MKW38 BLE Scan not working when long time test 你好, @JungkyuHan1 感谢您向我们提交新的案件。 我会尽快核实详细信息并向您汇报最新情况。 BR, Christine。 Re: MKW38 BLE Scan not working when long time test 你好, @JungkyuHan1 请允许我再花些时间回复您。 我需要和内部团队确认一些事项。 BR, Christine。 Re: MKW38 BLE Scan not working when long time test 你好, @JungkyuHan1 如果我理解正确,我收到了您提到“ 我们使用SDK 2.6.916进行了 BLE 扫描测试,效果非常好。超过 8 天没有出现扫描错误。 “2025 年 12 月。” 但现在您遇到了这个问题:“然而,使用 SDK 2.6.916 库大约一周后,该问题再次出现。 ” 请问OK和NOK病例在测试方面是否存在任何差异? 如果我们知道这些差异,对我们进一步追踪它将会非常有帮助。 关于您的问题: 这是KW38 BLE控制器的已知问题吗?它与 2.6.815 有关吗?修复“扫描问题导致广告漏播”?如果是这样,您能否详细描述一下具体修复了什么问题? ==>[Christine]: 正如我们之前沟通的那样,是的,这是一个已知问题。我们知道, 目前我知道的版本 2.6..916 至少有一个变通方法可以帮助解决扫描问题。据我所知,扫描问题是由于扫描 FIFO 冲突引起的,因此需要刷新扫描 FIFO。  扩展扫描(跟随 AUX 指针到辅助通道)是否会导致 LL 扫描器进入一种状态,即当SCAN_STATUS.Scan_on保持为 1时,它不再接收任何通道的信号? 由于该问题已在 SDK 2.6.916 中重现,是否有更新的控制器库或补丁可以解决该问题? ==>[Christine]:抱歉,我们没有比 SDK 2.6.916 更新的 SDK 版本修复此问题。 在应用层,检测和恢复这种状态的推荐方法是什么?例如: Gap_StopScanning() / Gap_StartScanning() 是否足够? 是否需要RESET控制器(例如,HCI RESET 或 LL SOFT_RESET 命令? 是否有任何LL状态登记册需要查阅? ==>[克里斯汀]: 您可能需要手动在应用程序代码中添加以下解决方法 应该有一个函数 ll_flush_adv_rx_fifo()。该函数的代码在应用程序代码中不存在,因此需要使用“extern”声明它。将此函数外部化后,输入参数和返回值均为 void,然后调用: 1.每次停止扫描前都要打电话 2. 如果设备长时间未扫描,请停止扫描并重新呼叫,然后再开始扫描。 禁用扩展扫描(仅使用传统扫描)是否可以避免这个问题? 是否允许从应用程序中读取 INIT_SCN_ADV_RX_FIFO (0x4008007C) 以进行诊断?这次读取操作是否会影响控制器的 FIFO 处理? ==>[Christine]:关于这两个问题,我需要进一步了解后再回复你。   BR, Christine。 Re: MKW38 BLE Scan not working when long time test 嗨,克里斯汀, 感谢您的回复。 关于OK案例(2025年12月)和NOK案例之间的区别: 我们在 SDK 2.6.916 中发现了一个错误迁移。我们现在正在使用正确的 SDK 2.6.916 版本重新进行测试。图书馆。 测试设置也不同: 先前测试(合格):3 个单元(2 个样品单元和 1 个开发单元),无天线。 当前测试:5 台全新量产机型,全部安装天线。 我们还有一些其他问题: 是 2.6.815修复“修复了某些情况下导致广告丢失的扫描问题”是否与 SDK 2.6.916 中的扫描 FIFO 锁定解决方法 (ll_flush_adv_rx_fifo()) 相同? 刷新后,使用传统的 START_SCAN 命令 (0x42) 重新启动扫描。启用扩展扫描后,重启后 AUX(辅助频道)接收是否能正常恢复? 在控制器中断服务例程 (ISR) 运行时,直接从应用程序任务调用 ll_flush_adv_rx_fifo() 是否安全?控制器的扫描中断处理是否存在并发或同步问题? 在 SDK 2.6.615 中控制器库中,ll_self_device_data[18]的第0位是什么意思?(我们正在考虑在2.6.615版本上手动执行相同的刷新操作。) 此致, 韩正奎 Re: MKW38 BLE Scan not working when long time test 你好, @JungkyuHan1 谢谢你提供的信息。 我仍在向我们的内部团队核实,以获取您问题的答案。 如有任何更新,我会通知您。 BR, Christine。 Re: MKW38 BLE Scan not working when long time test 你好, @JungkyuHan1 以下是我们内部团队的回复,供您参考。 1. 禁用扩展扫描(仅使用传统扫描)是否可以避免此问题? [NXP]:答案是否定的,虽然我们没有测试过这种情况,但这应该与扩展扫描无关。 2.是否允许从应用程序中读取 INIT_SCN_ADV_RX_FIFO (0x4008007C) 以进行诊断?这次读取操作是否会影响控制器的 FIFO 处理? [NXP]:最好不要从应用程序端读取数据,可以先停止扫描,读取后再继续扫描。 3.是2.6.815吗?修复“修复了某些情况下导致广告丢失的扫描问题”是否与 SDK 2.6.916 中的扫描 FIFO 锁定解决方法 (ll_flush_adv_rx_fifo()) 相同? [NXP]:目前我还不确定,需要一些时间进行调查。 4.刷新后,使用传统的 START_SCAN 命令 (0x42) 重新启动扫描。启用扩展扫描后,重启后 AUX(辅助频道)接收是否能正常恢复? [NXP]:是的。但您需要按照以下步骤操作:停止扫描 > ll_flush_adv_rx_fifo() > 重新开始扫描。 5.当控制器中断服务例程运行时,直接从应用程序任务调用 ll_flush_adv_rx_fifo() 是否安全? [NXP]:如上所述,最好在停止扫描时调用 ll_flush_adv_rx_fifo() 函数。 6.控制器的扫描中断处理是否存在并发或同步问题? [NXP]:您说的并发或同步问题是什么意思?能否详细说明一下?如果按照上述步骤操作,停止扫描并刷新,然后再重新启动扫描,我认为不会导致任何并发或同步问题。 7.扩展扫描(跟随 AUX 指针到辅助通道)是否会导致 LL 扫描器进入一种状态,即当 SCAN_STATUS.Scan_on 保持为 1 时,它不再接收任何通道的信号? [NXP]:到目前为止,我们还没有发现此类问题。 BR, Christine。 Re: MKW38 BLE Scan not working when long time test 你好, @JungkyuHan1 3. 2.6.815 版本中的修复程序“修复了某些情况下导致广告丢失的扫描问题”是否与 SDK 2.6.916 中的扫描 FIFO 锁定解决方法 (ll_flush_adv_rx_fifo()) 相同? [NXP]:虽然不完全相同,但存在关联。2.6.815 中的修复不足以解决扫描 FIFO 锁定问题,因此该修复无法完全解决扫描 FIFO 问题,所以最好添加该解决方法。 如果您对此帖还有其他疑问,请告诉我。 BR, Christine。
View full article
S32Z280ABCK0MJFT 的原产国 他是 S32Z280ABCK0MJFT 的首席运营官 Re: country of origin of S32Z280ABCK0MJFT 请联系出口管制团队: [email protected] 了解更多信息。
View full article
FS26 无法进入 LPOFF/待机状态 我们使用英飞凌 TC37x MCU 和 FS26 单板计算机 (SBC)。当发出断电请求时,SBC 无法从正常模式进入 LPOFF/待机模式。断电请求命令正常,但 SBC 仍然处于正常模式。我想知道哪些条件会阻止状态转换? Re: FS26 can't enter LPOFF/StandBy state 您好,刘, 请检查以下内容: 1. 在请求低功耗模式之前,请确认故障保护状态。 状态图中所示的低功耗转换从故障保护正常模式开始。发送请求前,请阅读以下内容: FS_STATES 地址 0x57 FS_DIAG_SAFETY1 地址 0x54 FS_DIAG_SAFETY2 地址 0x55 FS_OVUV_REG_STATUS 地址 0x50 FS_STATES[4:0] = 0x0B 表示故障保护状态机处于正常模式。诊断寄存器还可以显示是否发生了看门狗、SPI、FCCU、ERRMON、BIST 或电压监控事件。 2. 验证完整的两步命令序列 对于 LPOFF 模式,将以下值写入地址 0x58 处的 FS_LP_REQ: FS_LP_REQ[7:0] = 0xA5,请求 Pre-LPOFF 模式。 FS_LP_REQ[7:0] = 0x5A,完成向 LPOFF 模式的转换。 待机模式下,相应的序列为: 0xAA,请求进入预待机模式。 0x55,完成向待机模式的转换。 第二条命令必须在收到第一条命令后的 10 毫秒内收到。请连续发送这两个命令,并确认两个 SPI 帧都使用了正确的故障保护寄存器选择、地址、CRC 和时钟周期数。 如果第二个命令缺失、无效或未在规定时间内收到,则请求的低功耗转换将无法完成。 3. 检查 SPI 错误 首次请求后,立即检查 FS_DIAG_SAFETY1 是否存在以下情况: SPI_FS_CLK SPI_FS_REQ SPI_FS_CRC 这些位表示 SPI 时钟数不正确、故障保护 SPI 访问无效或 CRC 错误。以上任何一种情况都可能解释为什么低功耗命令未被接受。 4. 排除立即唤醒 如果已启用的唤醒源处于活动状态,或者在转换过程中变为活动状态,则设备可以立即唤醒,因此看起来仍处于正常模式。 请检查 M_WIO_CFG 以了解已启用的唤醒源及其配置的极性: WAKE1 和 WAKE2 GPIO1 和 GPIO2 激光动力测试 SPI CSB 过渡 特别是,如果 CSBWUEN = 1,则后续的 SPI 活动可以通过 CSB 从高到低的转换唤醒 FS26。设备唤醒后,可以读取 M_WIO_FLG.WUEVENT[3:0] 来识别检测到的唤醒源。 最后请注意,VPRE 在待机模式下仍保持启用状态,并且 LDO1 或 LDO2 也可能根据 OTP 配置保持启用状态。因此,仅凭这些轨道的存在并不能证明 FS26 保持正常模式。在 LPOFF 状态下,稳压器关闭,RSTB 为低电平。 BRs,托马斯
View full article
S32Z280ABCK0MJFTの原産国 これはS32Z280ABCK0MJFTのCOOです。 Re: country of origin of S32Z280ABCK0MJFT どうぞ、輸出管理チームまでお問い合わせください: [email protected] 詳細については、こちらをご覧ください。
View full article
License Extension Request for S32DS 3.5 Hello, My S32 Design Studio license is about to expire. Could you please help extend it? Activation ID: 5E5E-87D6-4F85-9A22 Version: 3.5 Thank you License Applicable to Product(s):    Version    Description    3.5    S32 Design Studio for S32 Platform v.3.5 License Quantity: 1 Fulfillment ID: 201997687 Expiration Date: Nov 4, 2026 Product: S32 Design Studio for S32 Platform v.3.5 Machine: 6EF78E1197D8A04DBC0B058E7DE51D3F39A0F67C Activation Code: 5E5E-87D6-4F85-9A22
View full article