BMA7426TBユーザーマニュアルおよび こんにちは、 BMA7426TB AFEを使用して燃料電池の電圧を監視したい。しかし、長いデータシートがなく、長いデータシートやユーザーマニュアル、そして助けが必要です。 1.バランス機能が不要なら、CBxのピンはどのようにコネクテッドすればよいのでしょうか?フローティングしているのか、それともセルにコネクテッドしなければならないのか? 2. もしCBxをセルにコネクテッドする必要がある場合、このピンは短時間-3Vに耐えられるのか?(<1秒) 3. 電源ピンVBATおよびVBATSWを24V DC/DCのような絶縁されたDC/DCにコネクテッドできるか。 ありがとうございます。 Re: BMA7426TB user manual and こんにちは、 BMA7426xBの完全なデータシートおよびリファレンスマニュアルは以下で入手可能です: https://www.nxp.com/products/BMA742X これらは機密文書であり、秘密保持契約（NDA）の締結が必要となることにご注意ください。 https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS これらの文書には、あなたの質問に対する回答が記載されています。 BRs、トーマス

Anyone on here use Smart Cards in their environment? I ask because I rarely see threads about it but I would imagine there has to be people out there who enforce Smart Card auth in their organization. Smart Cards on Mobile Re: Anyone on here use Smart Cards in their environment? Hello @ferio23 Hope you are doing well. Smart Cards are widely used in applications implementing authentication, access control, among others. To develop a complete solution and operate smart cards, you will need appropriate middleware or enablement software. For additional guidance, please refer to our Partner Directory for recommended vendors and solution providers. Regards, Eduardo.

Looking for DDR2 Register Parameter Architecture (RPA) Calculator for PQ2 Pro (MPC830x) The MPC830x pages here at NXP have a number of design documents, but I've been led to believe there is some sort of calculator (spreadsheet?) which helps with computing DDR2 register settings, possibly named: MPC830x_DDR2_RPA.xls or some variation of that.  Even if it's for some other PowerQuicc 2 (i.e. not exactly MPC830x) that used DDR2, it might be useful. Any chance it's stored away in an archive or with an eval board collateral? Thank you! Re: Looking for DDR2 Register Parameter Architecture (RPA) Calculator for PQ2 Pro (MPC830x) Hi @mrand , As the MPC830x family has been EOL for over three years, the requested file or download link is no longer available. Please refer to AN3369 for DDR register-programming guidance. Thank you.   Best Regards, June

iMX93における外部発振器の使用方法の明確化 こんにちは、 iMX93を使用したカスタムボードを開発しているのですが、24MHzの水晶発振器に関して少し混乱しており、外部発振器を使用できるかどうか疑問に思っています。 IMX93IECデータシートの表3には、「システムはXTALI/XTALOで24MHzを必要とします」と記載されています。外部の24MHz発振器では結晶を消す ことはできません 。」 しかし、リファレンス・マニュアルの発振器29.4.2節には次のように記されています。 「各XTALモジュールはレジスタ構成を通じて以下のモードをサポートしています: ノーマルオシレーターモード - XTALはクリスタルオシレーター入力に基づいて安定した方形波を生成します。 バイパスモード - 外部クロックはXTALパッド経由で入力可能です。" また、IMX93QSBの回路図には次のような注記があります。 「24MHz水晶発振器について」 バイパスモードを選択する必要があります。このモードでは、水晶発振器アンプはオフになり、「cosc_en_lv」、「osc_comp_enable_lv」、および「pwd_lv」は非アクティブ（論理0）になります。外部(XI)でのレールツーレール入力信号のみが必要で、XO(XO)は浮動信号または接地信号のいずれかで対応可能です。バイパスモードの設定は、FXOSCとSXOSCの両方のブロックガイドに記載されています。 参照されているレジスタ／コマンド／ビットとは何ですか？FXOSCとSXOSCのブロックガイドはどこにありますか？これらのものはリファレンス・マニュアルで検索しても見つからないのですか? では、iMX93で外部発振器を使うことは可能でしょうか(またはサポートされている)のでしょうか? Re: Clarifying usage of external oscillator with iMX93 こんにちは、 @AEi さん、 では、iMX93で外部発振器を使うことは可能でしょうか(またはサポートされている)のでしょうか? A：外部24MHz発振器の場合はいいえ。私たちのデータシートでそれがわかります。 RMはモジュールにノーマルモードとバイパスモードがあることを示します。基板レベルデザインに関しては、外部クロック交換クリスタルの明確な適用シナリオはRTCの32.768 kHz入力であり、24 MHzのマスタークロックではありません。 これがあなたの役に立てば幸いです ご質問があれば、どうぞお気軽にお問い合わせください 素敵な一日をお過ごしください よろしくお願いいたします。 リタ

寻找适用于 PQ2 Pro (MPC830x) 的 DDR2 寄存器参数架构 (RPA) 计算器 NXP 网站上的 MPC830x 页面有很多设计文档，但我听说里面还有某种计算器（电子表格？）。这有助于计算 DDR2 寄存器设置，可能命名为： MPC830x_DDR2_RPA.xls 或者类似的表达。即使是其他 PowerQuicc 2（例如虽然不是使用 DDR2 的 MPC830x，但它可能有用。 有没有可能它被保存在档案馆里或者评估委员会的资料中？ 谢谢！ Re: Looking for DDR2 Register Parameter Architecture (RPA) Calculator for PQ2 Pro (MPC830x) 嗨@mrand ， 由于 MPC830x 系列产品已经停产三年多了，因此请求的文件或下载链接不再可用。 有关 DDR 寄存器编程指南，请参阅 AN3369。 谢谢。   顺祝商祺！ 六月

BMA7426TB 用户手册和 您好， 我想使用 BMA7426TB AFE 来监测燃料电池电压。但我没有详细的数据手册，我需要详细的数据手册或用户手册以及一些帮助。 1.如果不需要平衡功能，CBx引脚应该如何连接？是浮空还是必须连接到电池？ 2. 如果CBx必须连接到电池，这些引脚能否短时间（<1秒）承受-3V电压？ 3. 电源引脚 VBAT 和 VBATSW 能否连接到隔离式 DC/DC，例如 24V dc/dc。 谢谢。 Re: BMA7426TB user manual and 您好， BMA7426xB 的完整数据手册和参考手册可在以下网址获取： https://www.nxp.com/products/BMA742X 请注意，这些是需要签署保密协议的机密文件： https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS 这些文件中将包含您问题的答案。 BRs，托马斯

BMA7426TB user manual and Hi, I want to use BMA7426TB AFE to monitor fuel cell voltage. But I have no long data sheet, and I need long data sheet or user manual  and some help. 1. If the balancing function is not required, how should the CBx pins be connected? Be floating or must be connected to cell? 2. if the CBx must be connected  to cell, could this pins withstand -3V for short time?（<1s） 3. Could power supply pins VBAT and VBATSW be connected to a isolated DC/DC, such as 24V dc/dc. thanks. Re: BMA7426TB user manual and Hi, The full datasheet and reference manual for the BMA7426xB are available at: https://www.nxp.com/products/BMA742X Please note that these are secure documents requiring an NDA: https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS In these documents you will find answers to your questions. BRs, Tomas

Clarifying usage of external oscillator with iMX93 Hi, I am developing a custom board using the iMX93 and I am a bit confused regarding the 24 MHz XTAL and if it is possible at all to use an external oscillator. Table 3 of the IMX93IEC datasheet says: "The system requires 24 MHz on XTALI/XTALO. The crystal cannot be eliminated by an external 24 MHz oscillator." But then the Oscillator section 29.4.2 in the reference manual states: "Each XTAL module supports the following mode through register configuration: Normal oscillator mode - XTAL generates stable square wave based on the crystal oscillator input. Bypass mode - external clock can be input through XTAL pad." Also the IMX93QSB schematic has a note that says: "Regarding 24MHz crystal oscillator: Bypass mode need to be selected. In this mode, the crystal oscillator amplifier is off with “cosc_en_lv”, "osc_comp_enable_lv" and “pwd_lv” deasserted (logic 0). Only rail to rail input signal at extal (XI) is needed with xtal (XO) could be either floating or ground. Bypass mode configuration is provide in both FXOSC and SXOSC block guides." What are these registers/commands/bits that are referenced? Where is FXOSC and SXOSC block guides? None of these are turn up in a search in the reference manual? So, is it or is it not possible (and supported) to use an external oscillator with the iMX93? Re: Clarifying usage of external oscillator with iMX93 Hi @AEi ， So, is it or is it not possible (and supported) to use an external oscillator with the iMX93? A： No for the external 24 MHz oscillator. In our datasheet you can see that. The RM indicates that the module has normal and bypass modes.When it comes to board level design, the clear applicable scenario for external clock replacement crystals is the 32.768 kHz input of RTC, not the 24 MHz master clock. Hope this can do help for you Any questions please contact me freely Wish you have a nice day Best Regards Rita

使用S32K312 MCU时，整车控制器VCU会卡顿110秒后恢复。 尊敬的恩智浦技术支持： 我们最近在使用S32K312 MCU时，在使用DFlash模拟EEPROM进行数据读写时遇到了一个奇怪的问题：控制器偶尔会卡顿110秒，然后恢复正常。我们目前怀疑在闪存擦除或写入过程中，由于某些未知原因， Fls_GetJobResult长时间无法更新到正确的状态（我们使用以下方法等待擦除/写入状态）： c do { Fls_MainFunction(); Fls_JobResult = Fls_GetJobResult(); } while (Fls_JobResult == MEMIF_JOB_PENDING); 由于这种情况发生在车辆中，而且非常偶发，因此我们无法通过调试来捕获异常。我们想问问您有没有什么好的建议。或者还有其他人遇到过类似的问题，即闪存擦除/写入调用卡住的情况吗？ 我们期待您的回复。 Re: VCU controller hangs for 110 seconds and then recovers when using s32k312 MCU 嗨@赵宁 我发现了一个可能与您目前遇到的问题类似的问题。 https://community.nxp.com/t5/S32K/long-Fee-cluster-swap-times/m-p/1951280#M40791 根据所提供的信息，我们目前还无法确定问题的确切原因；但是，您可以从调查“集群交换”入手。

PQ2 Pro(MPC830x)用のDDR2レジスタパラメータアーキテクチャ(RPA)カリキュレータを探しています NXPのMPC830xページには多くの設計ドキュメントがありますが、何らかのカリキュレータ(スプレッドシート?)があると聞いています。これはDDR2レジスタ設定の計算に役立ち、おそらく次のような名前が付けられます。 MPC830x_DDR2_RPA.xls あるいは、そのバリエーション。たとえそれが他の PowerQuicc 2 (つまり、DDR2 を使用した MPC830x と全く同じではありませんが、役に立つかもしれません。 アーカイブや評価ボードの資料と一緒に保管されている可能性はありますか? ご回答をお待ちしています。 Re: Looking for DDR2 Register Parameter Architecture (RPA) Calculator for PQ2 Pro (MPC830x) こんにちは、 @mrand さん。 MPC830xファミリーは3年以上前に終了しているため、リクエストされたファイルやダウンロードリンクはもはや利用できません。 DDRレジスタのプログラミングに関するガイダンスについては、AN3369を参照してください。 ありがとう。   よろしくお願いいたします。 6月

阐明iMX93外部振荡器的使用方法 您好， 我正在使用 iMX93 开发一款定制板，我对 24 MHz 晶振以及是否可以使用外部振荡器有些困惑。 IMX93IEC 数据表第 3 表指出：“该系统需要 XTALI/XTALO 上的 24 MHz 频率。外部24兆赫振荡器无法消除晶体的影响。 但是，参考手册的振荡器部分 29.4.2 节却指出： 每个晶振模块都通过寄存器配置支持以下模式： 普通振荡器模式 - XTAL 根据晶振（晶体振荡器）的输入产生稳定的方波。 旁路模式——可通过晶振焊盘输入外部时钟信号。 此外，IMX93QSB原理图上还有一条注释： 关于24MHz晶振（晶体振荡器）： 需要选择旁路模式。在此模式下，晶振（晶体振荡器）放大器关闭，“cosc_en_lv”、“osc_comp_enable_lv”和“pwd_lv”被取消置位（逻辑 0）。只需要在晶振 (XI) 处输入轨到轨信号，晶振 (XO) 可以是浮空或接地。FXOSC 和 SXOSC 模块指南中均提供了旁路模式配置。 这里提到的寄存器/命令/位是什么？FXOSC和SXOSC模块的指南在哪里？在参考手册中搜索不到这些内容吗？ 那么，iMX93 是否可以使用（并支持）外部振荡器？ Re: Clarifying usage of external oscillator with iMX93 嗨@AEi ， 那么，iMX93 是否可以使用（并支持）外部振荡器？ A：不需要外部24 MHz振荡器。您可以在我们的产品规格表中看到这一点。 RM 表示该模块具有正常模式和旁路模式。就电路板级设计而言，外部时钟替代晶振的明确适用场景是 RTC 的 32.768 kHz 输入，而不是 24 MHz 主时钟。 希望这对您有所帮助。 如有任何疑问，请随时与我联系。 祝你今天过得愉快 顺祝商祺！ Rita

i.MX93 AHAB: Security implications of keeping SDP enabled in OEM_CLOSED Hello NXP Support, We have received several questions from a customer using the i.MX93 (VAR-SOM-MX93) regarding the security implications of leaving Serial Download Protocol (SDP) enabled in production devices with AHAB enabled and the lifecycle set to OEM_CLOSED. The customer would like to retain USB recovery functionality for troubleshooting and device recovery, while ensuring that this does not introduce security vulnerabilities. They have reviewed the i.MX93 Reference Manual and Security Reference Manual but would appreciate clarification on the following points: SDP access restrictions in OEM_CLOSED What memory, register, and eFuse read/write operations are permitted through SDP when the device is in OEM_CLOSED? Can an unauthenticated host access sensitive memory or perform write operations „outside“ the authenticated recovery process? BOOT_CFG10 eFuse settings The i.MX93 Reference Manual (Section 9.9.3, Table 57) documents the SDP_WO and SDP_READ_DISABLE settings. Could you clarify their meaning and behavior; how they affect SDP in OEM_CLOSED, and their intended use cases? The customer was also unable to locate these settings in the RM itself, in the fusemap spreadsheet nor in the Security Reference Manual. Security implications of OEM_CLOSED vs. OEM_LOCKED From NXP's perspective, what additional security risks should be considered when leaving SDP enabled in OEM_CLOSED compared to disabling USB recovery through OEM_LOCKED? Are there any recommended configurations or mitigations for production devices that require authenticated USB recovery? We would appreciate your guidance or references to further documentation covering these aspects. Thank you. Best regards, Alex Security Re: i.MX93 AHAB: Security implications of keeping SDP enabled in OEM_CLOSED Hi, Thank you for your interest in NXP Semiconductor products, 1. SDP is used to download images, production devices could have SDP enabled, new images could be overwritten only if they are signed. Aside from that, if devices have a signed image flashed, U-boot command line tools like md, mw, fuse read, write could be executed or code actions could be performed. 2. I am confirming their descriptions internally. 3. OEM_CLOSED and OEM_LOCKED are similar, except no debug/DFT/Boundary Scan/USB recovery and No Field Return in OEM_LOCKED. Regards

这里有人在工作中使用智能卡吗？ 我这么问是因为我很少看到相关的讨论帖，但我认为肯定有人会在他们的组织中强制使用智能卡认证。 移动设备上的智能卡 Re: Anyone on here use Smart Cards in their environment? 你好@ferio23 希望你一切都好。 智能卡广泛应用于身份验证、访问控制等领域。要开发完整的解决方案并运行智能卡，您需要合适的中间件或启用软件。如需更多指导，请参阅我们的合作伙伴目录，了解推荐的供应商和解决方案提供商。 问候， 爱德华多。

VCUコントローラは110秒間フリーズし、その後s32k312 MCUを使用すると復旧します NXPテクニカルサポートの皆様、 最近S32K312 MCUを使っているのですが、DFlashを使ってEEPROMをエミュレートしてデータ読み書きを行った際に奇妙な問題が発生しました。コントローラが時々110秒間フリーズし、その後復旧することがあります。現在、フラッシュ消去や書き込み中に何らかの理由で Fls_GetJobResult が長い間正しい状態に更新できないのではないかと疑っています(消去・書き込みのタイミングを待つために以下の方法を使っています): c do { Fls_MainFunction(); Fls_JobResult = Fls_GetJobResult(); } while (Fls_JobResult == MEMIF_JOB_PENDING); これは車載で非常に断続的に発生するため、デバッグでは例外をキャプチャできません。何か良いご提案があればお聞かせください。あるいは、フラッシュメモリの消去/書き込み処理がハングアップするという同様の問題に遭遇した方は他にいますか？ ご返信をお待ちしております。 Re: VCU controller hangs for 110 seconds and then recovers when using s32k312 MCU こんにちは@昭寧 あなたが現在経験している問題と類似している可能性のある問題を発見しました。 https://community.nxp.com/t5/S32K/long-Fee-cluster-swap-times/m-p/1951280#M40791 提供された情報に基づき、問題の正確な原因はまだ特定できません。しかし、「クラスター・スワップ」について調査を始めることは可能です。

i.MX93 AHAB:OEM_CLOSEDでSDPを有効にし続けることのセキュリティ上の影響 こんにちは、NXPサポートの皆さん、 i.MX93(VAR-SOM-MX93)を使用しているお客様から、AHABを有効にしてライフサイクルをOEM_CLOSEDに設定したまま、本番機でシリアルダウンロードプロトコル(SDP)を有効化したままにしておくことのセキュリティ上の影響について、いくつかの質問をいただいています。 お客様はトラブルシューティングやデバイス復旧のためにUSB復旧機能を保持しつつ、セキュリティの脆弱性を生まないことを望んでいます。 彼らはi.MX93リファレンスマニュアルおよびセキュリティリファレンスマニュアルをレビューしましたが、以下の点についての説明を歓迎します。 OEM_CLOSEDにおけるSDPのアクセス制限 デバイスがOEM_CLOSED中の場合、SDPを通じてどのようなメモリ、レジスタ、eFuseの読み書き操作が許可されていますか?認証されていないホストが、認証済みの復旧プロセスの「外側」で敏感なメモリにアクセスしたり書き込み操作を行ったりすることはできますか? BOOT_CFG10 eFuse設定 i.MX93 リファレンスマニュアル(セクション9.9.3、表57）は、SDP_WOおよびSDP_READ_DISABLEの設定について説明しています。 その意味や挙動について、OEM_CLOSEDにおけるSDPにどのように影響し、意図された用途について説明していただけますか?お客様はRM本体、ヒューズマップスプレッドシート、セキュリティリファレンス・マニュアルでもこれらの設定を見つけることができませんでした。 OEM_CLOSEDとOEM_LOCKEDのセキュリティ上の影響 NXPの視点から、OEM_CLOSEDでSDPを有効にしたままにする際、OEM_LOCKEDを通じたUSBリカバリーを無効にする場合と比べて、どのような追加のセキュリティリスクを考慮すべきでしょうか? 認証済みUSBリカバリーが必要な本番機向けの推奨設定や対策はありますか? これらの側面に関するさらなるドキュメントのご参考やご指名をいただけるとありがたいです。 ありがとう。 よろしくお願いします、 アレックス Security Re: i.MX93 AHAB: Security implications of keeping SDP enabled in OEM_CLOSED こんにちは、 NXP Semiconductors製品にご関心いただきありがとうございます。 1. SDPはイメージのダウンロードに使われ、本番機器はSDPを有効にし、新しい画像は署名されていなければ上書きできません。それ以外にも、デバイスに署名済みイメージがフラッシュされている場合、md、mw、fuseの読み書きなどのUブートコマンドラインツールを実行したり、コードアクションを実行したりすることができます。 2. 私は彼らの説明内容を社内で確認しています。 3. OEM_CLOSED と OEM_LOCKED は似ていますが、OEM_LOCKED ではデバッグ/DFT/境界スキャン/USB リカバリおよびフィールド リターンは行われません。 よろしくお願いします。

i.MX93 AHAB：在 OEM_CLOSED 模式下保持 SDP 启用的网络安全隐患 您好，NXP技术支持， 我们收到了一些使用 i.MX93 (VAR-SOM-MX93) 的客户提出的问题，询问在启用 AHAB 且生命周期设置为 OEM_CLOSED 的生产设备中启用串行下载协议 (SDP) 的网络安全隐患。 客户希望保留 USB 恢复功能以进行故障排除和设备恢复，同时确保这不会引入网络安全漏洞。 他们已查阅了 i.MX93 参考手册和网络安全参考手册，但希望就以下几点获得澄清： OEM_CLOSED 中的 SDP 访问限制 当设备处于 OEM_CLOSED 状态时，通过 SDP 允许执行哪些内存、寄存器和 eFuse 读/写操作？未经身份验证的主机能否在经过身份验证的恢复过程“之外”访问敏感内存或执行写入操作？ BOOT_CFG10 eFuse 设置 i.MX93 参考手册（第 9.9.3 节，表 57) 记录了 SDP_WO 和 SDP_READ_DISABLE 设置。 能否解释一下它们的含义和行为；它们如何影响 OEM_CLOSED 中的 SDP，以及它们的预期用途？客户也无法在 RM 本身、fusemap 电子表格或网络安全参考手册中找到这些设置。 OEM_CLOSED 与 OEM_LOCKED 的网络安全隐患 从 NXP 的角度来看，与通过 OEM_LOCKED 禁用 USB 恢复相比，在 OEM_CLOSED 中启用 SDP 会带来哪些额外的网络安全风险？ 对于需要经过身份验证的 USB 恢复的生产设备，是否有任何推荐的配置或缓解措施？ 我们非常感谢您能提供这方面的指导或相关文件资料。 谢谢。 此致， 亚历克斯 安全 Re: i.MX93 AHAB: Security implications of keeping SDP enabled in OEM_CLOSED 您好， 感谢您对恩智浦半导体产品的关注， 1. SDP 用于下载图像，生产设备可以启用 SDP，只有经过签名的新图像才能被覆盖。除此之外，如果设备已刷入签名镜像，则可以执行 U-boot 命令行工具（如 md、mw、熔丝 read、write）或执行代码操作。 2. 我正在内部确认他们的描述。 3. OEM_CLOSED 和 OEM_LOCKED 类似，只是 OEM_LOCKED 没有调试/DFT/边界扫描/USB 恢复功能，也没有字段返回功能。 此致

このフォーラムでスマートカードを使っている方はいらっしゃいますか？ この件についてのThreadはあまり見かけませんが、組織内でスマートカード認証を強制している人はいるはずだと思います。 モバイルのスマートカード Re: Anyone on here use Smart Cards in their environment? こんにちは、@ferio23さん あなたの調子が良いといいのですが。 スマートカードは認証やアクセス制御などのアプリケーションで広く使われています。完全なソリューションを開発しスマートカードを運用するには、適切なミドルウェアやイネーブルメントソフトウェアが必要です。追加のガイダンスについては、 推奨ベンダーやソリューションプロバイダーについては パートナー一覧 をご参照ください。 よろしくお願いいたします。 エドゥアルド。

Zephyr GUI Development with GUI Guider In recent years, Zephyr has gained strong momentum in embedded development. With broad hardware support, an active open-source ecosystem, and flexible extensibility, it is increasingly being used in consumer electronics, IoT devices, and industrial control systems. At the same time, as embedded products place higher demands on graphical user interfaces, developers are looking for more efficient ways to design GUIs and deploy them quickly on Zephyr-based platforms. This article uses GUI Guider 2.0.1, the i.MX RT1064-EVK development board, and the RK043FN66HS-CTG display as an example. It walks through the complete workflow, from UI design and Zephyr application export to project build, flashing, and runtime verification, so you can get your designed interface running on the board with confidence. Let’s start with the development environment and complete this hands-on GUI Guider and Zephyr workflow step by step. 1. Set Up and Verify the Zephyr Development Environment Before getting started, follow the Zephyr development environment setup section in the official GUI Guider User Guide. Then use an official sample to confirm that the target board can be built, flashed, and run successfully. 2. Generate and Export the Zephyr Application 1. Create a Project and Generate Code After creating an i.MX RT1064-EVK-based project in GUI Guider and completing the UI design, click Generate Code to generate the application code. 2. Export the Zephyr Application Click OS > Zephyr to export the application to the target directory in your Zephyr workspace, for example: /gui_guider_demo 3. Check the Exported Files After the export is complete, the application directory should contain the following files and folders: gui_guider_demo/ ├── CMakeLists.txt ├── prj.conf └── src/     ├── main.c     ├── custom/     └── generated/ CMakeLists.txt: defines the Zephyr application build entry point and specifies the source files to compile. prj.conf: configures options such as LVGL, memory, and thread stack settings. src/main.c: the application entry file, responsible for initializing the UI and starting the application logic. src/custom/: stores custom business logic to avoid being overwritten when code is regenerated. src/generated/: stores UI code automatically generated by GUI Guider. Direct modification is not recommended. 3. Build and Flash the Zephyr Application Open a terminal, go to the root directory of the exported Zephyr application, and run the following commands: west build -p always -b mimxrt1064_evk --shield rk043fn66hs_ctg . west flash Note: The . in the command indicates the current application directory. This applies to Windows, Linux, and macOS. 4. Verify the Runtime Result Runtime verification: After flashing is complete, check that the screen displays the designed UI correctly and that touch interactions respond as expected. If these checks pass, the deployment workflow from GUI Guider to Zephyr is working properly. Common issues: No display output or abnormal UI behavior: check the serial log, display shield configuration, and display resolution settings in the GUI Guider project. Out-of-memory errors during build or runtime: increase CONFIG_LV_Z_MEM_POOL_SIZE in prj.conf as needed. Main thread stack overflow or unexpected reboot: increase CONFIG_MAIN_STACK_SIZE. After updating the configuration, rebuild and flash the application again. The exact values should be determined based on the error logs, UI complexity, and available hardware resources. 5. Establish a Repeatable UI Iteration Workflow After the first build and deployment are complete, you can iterate on future UI changes using the following workflow: Regenerate code → Export Zephyr application → Build → Flash → Verify   To prevent custom logic from being overwritten when code is regenerated, keep business logic in the custom code area. It is also recommended to put both the GUI Guider project and the exported Zephyr application under version control. Summary GUI Guider provides a complete path from UI design to Zephyr application export. Once the initial environment setup is complete, future UI updates only require repeating the generate, export, build, and verify workflow. This can significantly reduce the effort required for UI iteration and board-level deployment.

From Figma to GUI Guider: Accelerating Embedded GUI Development Bridging design and engineering to move embedded GUI projects from concept to implementation faster 1. Why a Smoother Path from Design to Embedded GUI Matters In embedded GUI projects, the interface design is often completed in Figma, while the engineering implementation still needs to be rebuilt in GUI Guider by creating widget hierarchies, configuring resources, and validating the final result. For projects with many screens or frequent design iterations, this process can be repetitive and may introduce gaps between the design intent and the implemented interface. Figma to GUI Guider offers a structured workflow that helps convert Figma designs into GUI Guider project assets. It maps Figma layers and components to LVGL widgets, generates GUI Guider project JSON, and exports a project package that can be imported into GUI Guider. The converted result provides a practical engineering starting point, while developers can continue editing, simulating, and validating the project in GUI Guider. Positioning This plugin is designed to shorten the initial conversion path from design handoff to engineering implementation. Figma designs should be treated as implementation references, rather than a complete guarantee of embedded runtime behavior. Actual projects still need to be adapted and validated against the resource constraints and rendering capabilities of the target platform. 2. How the Plugin Connects Design and Engineering Capability Description Read the Figma design tree Displays the Figma Design Tree in the plugin panel, helping developers review the node hierarchy of the design. Configure LVGL type mapping Sets the appropriate LVGL widget type for each design node and controls whether the node is included in conversion. Generate GUI Guider project JSON After conversion, previews the generated GUI Guider project JSON in the output area. Export the project package Exports a zip package via Download, including the converted project files and related image resources. Import into GUI Guider After extracting the exported package, import the .guiguider file in GUI Guider through Import Project and continue development. 3. Quick Start: Running the Plugin in Figma The Figma to GUI Guider plugin is available on Figma Community and can be launched directly from the Figma desktop app or browser version, without manually downloading a plugin package. The current release supports Windows. Open the Figma desktop app or browser version and sign in to your Figma account. Go to the Figma to GUI Guider plugin page, or search for the plugin name in Figma Community. On the plugin page, click Open in… to run it directly, or save it to your account for future use. Open the target design file and launch the plugin from the Plugins menu. You can also right-click on the canvas and run it from the Plugins menu. 4. Understanding the Plugin Interface After the plugin is launched, it appears as a panel inside the Figma workspace. For first-time users, we recommend becoming familiar with the key areas of the interface before configuring mappings and running the conversion. Figma Design Tree: Shows the layer and component hierarchy of the current design file. Each node can be configured with an LVGL type and conversion status. Design Node: Displays the node name and Figma type, and uses the LVGL Type Selector to define the widget type after conversion. Refresh / Convert: Refresh reloads the current Figma file structure, while Convert generates the output based on the current mapping configuration. About: Provides plugin information, version details, support contacts, and reference links. GUI Guider Project JSON: Shows the generated project JSON after conversion, making it easy to quickly review the structure. Clear / Copy / Download: Clears the output, copies the JSON, or exports the project zip package and image resources. 5. Recommended Workflow: Review Mapping Before Generating the Project When the plugin is opened for the first time, it generates an initial mapping based on the Figma nodes. Instead of converting immediately, reviewing and adjusting the node mappings first usually produces a project structure that better matches engineering expectations. 1 Review the automatic mapping Browse the design tree and confirm that text, buttons, images, and other nodes are assigned appropriate LVGL widget types. 2 Adjust widget types If the automatic mapping does not meet expectations, update the node type through the Type Selector. Mapping settings are saved in the Figma project. 3 Control the conversion scope Use Disable in Conversion for nodes that should not be included in the output. Disabled nodes will not appear in the generated JSON, while their child hierarchy is preserved. 4 Run Convert After configuration is complete, click Convert to generate the GUI Guider project JSON and review the result in the output area. 6. Generate the Project and Import It into GUI Guider After conversion is complete, first review the structure in the GUI Guider Project JSON area. If the node type, hierarchy, or disabled status does not match expectations, return to the design tree, adjust the mapping, and run Convert again. Once the result is confirmed, click Download to export the zip package. The exported package includes the converted project files and related image resources. Extract the zip file, open GUI Guider, select Import Project on the home page, and choose the .guiguider file from the extracted folder to complete the import. If the design uses custom fonts, copy the font files to the resources/font folder in the project directory. After import, developers can continue editing the interface in GUI Guider and validate the project using the JS simulator, the C simulator, or the target platform. 7. Use Cases and Best Practices This plugin is especially useful for teams that already have Figma designs and want to quickly create a GUI Guider project starting point. It can support projects with clear page structures, frequent design iterations, or a need to reduce repetitive communication between design handoff and embedded GUI development. Keep the design structure close to the widget hierarchy: The closer the Figma layer structure is to the parent-child relationship of LVGL widgets, the easier the converted result is to understand and maintain. Treat the converted result as an engineering starting point: The plugin helps reduce initial setup work, but resources, fonts, rendering capabilities, and runtime behavior still need to be validated on the embedded platform. Keep the import environment clean if import fails: If the project cannot be imported successfully into GUI Guider, remove the previously imported design project and retry from a clean state. 8. Summary: Bringing Design into the Engineering Workflow Faster The Figma to GUI Guider plugin provides a more direct connection between Figma designs and GUI Guider projects. Through design tree parsing, LVGL type mapping, node-level conversion control, JSON preview, and project package export, developers can bring existing design assets into the GUI Guider workflow faster, then continue with engineering edits, simulation, and target-platform validation. For teams that already use Figma for interface design, this plugin helps reduce repetitive interface-building work and enables smoother collaboration between design handoff and embedded GUI development. Search for Figma to GUI Guider in Figma Community to try the plugin, then use GUI Guider to continue editing, simulation, and target-platform validation. We welcome your questions, suggestions, and practical feedback as we continue improving the workflow from design to embedded GUI implementation.

Using the I8 Image Format within GUI Guider Reducing image resource usage in embedded GUI applications When developing embedded GUIs, many projects encounter a familiar challenge: image resources begin consuming a significant amount of Flash before the interface becomes complex. Icons, buttons, status indicators, logos, and other assets may seem small individually, but their cumulative footprint can reduce the space available for future features. I8 (Indexed 8-bit) is an effective option for reducing image storage while preserving acceptable visual quality. This guide explains the fundamentals of I8, its suitable use cases, and practical recommendations for using it in GUI Guider projects. 1. Why Use the I8 Image Format? In MCU-based projects, image resources often occupy a large portion of Flash. For assets with a limited number of colors, such as icons, status images, logos, and industrial HMI elements, I8 can reduce storage usage while preserving the essential visual appearance. I8 stores an image using a pixel-index and color-palette mechanism. Each pixel stores a one-byte index, which maps to an actual color in the palette. This makes I8 especially suitable for UI assets with concentrated color sets, clear boundaries, and highly graphical content. Storage Comparison of Common Image Formats Image Format Typical Storage per Pixel Suitable Use Cases RGB888 3 bytes Images with rich colors and high color-fidelity requirements RGB565 2 bytes Common MCU displays balancing visual quality and resource usage ARGB8888 4 bytes Images requiring an alpha channel and high-quality rendering I8 1 byte + palette Icons, logos, and HMI elements with a limited color set 2. What Is an I8 Image? I8 stands for Indexed 8-bit. Instead of storing complete color information in every pixel, an I8 image stores an 8-bit index that points to a color in a palette. Because an 8-bit value represents up to 256 indices, an I8 image supports a maximum of 256 colors. This format is well suited to UI assets with limited colors, sharp boundaries, and graphic-style content. Key Advantages Smaller image files and lower Flash consumption. Lightweight resource loading for memory-constrained MCUs. Well suited to icons, industrial HMI elements, status images, and logos. More flexible UI resource management when combined with the LVGL 9.4 image display mechanism. Limitations Supports no more than 256 colors. Not suitable for photographs, video frames, product renderings, or other color-rich assets. Images with excessive colors may show banding, color distortion, or unnatural transitions after conversion. 3. Recommended Workflow in GUI Guider Step 1: Prepare the Image Resources Prefer PNG assets with a limited number of colors. Before importing an image, check whether it contains excessive gradients or photographic content. Step 2: Import Images into GUI Guider Add the image resources through Resource Manager and select an appropriate color format based on the display requirements of the project. Step 3: Select the I8 Color Format Convert suitable resources to I8 and preview the visual result in GUI Guider. Step 4: Validate in the Simulator Use GUI Guider Simulator to check color rendering, transparent regions, edge transitions, and the overall appearance of the page. Step 5: Generate Code and Validate on the Target After confirming that the result meets the requirements, generate the code and verify the application on the target development board. 4. Resource Usage Comparison: I8 vs. RGB565 The following theoretical estimates illustrate the resource usage of different formats. Actual size depends on image content, palette size, compression, and project configuration. Test Resource Image Format Theoretical Data Size 128 × 128 icon RGB565 Approximately 32 KB 128 × 128 icon ARGB8888 Approximately 64 KB 128 × 128 icon I8 Approximately 16 KB + palette From a resource-budget perspective, I8 reduces image storage when the color count can be controlled. The cumulative savings become more significant in HMI projects that contain many icons and status images. 5. Important Considerations When Using I8 1. Prefer Images with Fewer Than 256 Colors The core limitation of I8 is the palette size, so images with fewer colors are the best candidates. 2. Always Check the Visual Result After Conversion Even when an image contains relatively few colors, verify the result both in GUI Guider Simulator and on the target hardware. 3. Pay Attention to Transparency and Edge Transitions For images with transparent or anti-aliased edges, check for jagged borders, artifacts, or unnatural colors after conversion. 4. Do Not Convert Every Image Blindly I8 is an optimization technique, not the default choice for every asset. Complex backgrounds and photographic resources should continue to use a more appropriate color format. 6. Project Practice Recommendations In the GUI Guider Air Conditioner and Agriculture Control templates, selected images use I8 to save storage space and enable deployment on the FRDM-MCXN236 development board. Set suitable icons and status images to the I8 format. Compare the visual quality and resource size before and after conversion. After code generation, confirm that generated resources use the expected image format. Validate visual quality, refresh performance, and memory usage on the target platform. Example 1: Air Conditioner The Air Conditioner application template contains many animations and small icons. The comparison below shows ARGB8888 and I8 results. While maintaining image quality, I8 saves approximately 950 KB, allowing the application to run on the FRDM-MCXN236 development board. Figure 1. Air Conditioner comparison: I8 (left) and ARGB8888 (right). Example 2: Agriculture Control In the Agriculture Control application template, using I8 saves approximately 16.5 KB of storage. Figure 2. Agriculture Control comparison: I8 (left) and ARGB8888 (right). Conclusion For small and medium-sized HMI projects on platforms such as MCX and i.MX RT, I8 is a practical method for optimizing image resources. It is particularly useful when a project contains many icons, status indicators, menu graphics, and decorative elements. Applied selectively and validated carefully, I8 can release more Flash space while maintaining an appropriate visual experience.