Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
LX2160ARDB:DDR验证 您好, 我们已将 LSDK 中的 RCW 文件 (rcw_2200_750_2900_19_5_2.bin) 加载到 SD 卡中,在 DDR 配置面板中,读取 SPD完成后,出现“不支持的原始卡版本。请手动将 CLK 设置为 DQS 偏移值。” 如何在QCVS工具中对LX2160ARDB执行DDR验证 Priyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.png Re: LX2160ARDB: DDR validation 嗨,六月卢, 感谢您的支持 对于 USB 接口,该命令的结果是: (bin)51% findcc cwtaps 0 (箱)51% 以及以太网连接 (bin)51% findcc cwtaps FSL07E3D5 (10.1.66.150):CodeWarrior TAP v2 Cortex-10探针尖端 启动加载程序 v1.0.1 操作系统版本 1.0.5 1 目前我们能否使用以太网连接进行 DDR 验证? Re: LX2160ARDB: DDR validation (bin)52% 显示 cc 0:USB 开路失败 未配置任何命令变流器。 这表明无法通过 USB 连接检测到 CWTAP。 请检查 USB 连接线连接情况,并确保主机能够正确识别 CWTAP。 另外,请运行以下命令并分享结果: (bin)6% findcc cwtaps 谢谢。 Re: LX2160ARDB: DDR validation 嗨,六月卢, CodeWarrior 版本- Priyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.png (bin)49% log v CCS Linux 版本 503.0.0.220812-p0 详细日志记录 (bin)50% 全部删除 (bin)51% 配置 cc cwtap (bin)52% 显示 cc 0:USB 开路失败 未配置任何命令变流器。 (箱)53% (bin)53% 源 IDcode.tcl 正在扫描通过 USB 连接的可用 TAP…… 未找到通过 USB 连接的 TAP ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + 可用的远程连接 + +1 - CodeWarriorTAP - +2 - GigabitTAP - + + x - 不进行任何更改地退出脚本 + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 指定连接方式: 无法读取“CONNECTION()”:数组中不存在此元素 (箱)54% (箱)54% 能够通过以太网连接并 ping 通目标设备。即使将 CodeWarrior 更新到 v11.5.12 版本后,读取 SPD 仍然显示“不支持的原始卡版本。请手动设置 CLK 到 DQS 偏移值。” 谢谢 Re: LX2160ARDB: DDR validation 请从“帮助”→“关于 CodeWarrior Development Studio for QorIQ LS Series (ARM v8 ISA)”确认 CodeWarrior 版本。 请按照“CCS Windows Release Build 503.0.0.220812-p0.txt”中的说明验证连接状态。 我们建议先测试 USB 连接,然后再测试以太网连接。 IP地址似乎已更改。请问您是否可以成功 ping 通目标设备? Re: LX2160ARDB: DDR validation 嗨,六月卢, 我们使用的是 CodeWarrior 11.5.0,DIMM 是 LX2160ARDB 主板原装的内存条。 CodeWarrior 已更新,存档为com.freescale.armv8.11.5.12.GA.Lin.updatesite.221209.zip适用于 v11.5.12 现在无法检测到JTAG Priyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.png 谢谢 Re: LX2160ARDB: DDR validation 我按照你的步骤操作,成功读取了SPD数据。 请问您使用的是哪个版本的CodeWarrior?是 CodeWarrior 11.5.12 吗? 另外,这个内存条是原装的吗? 谢谢。 Re: LX2160ARDB: DDR validation 嗨,六月卢, 通过 FlexSPI 启动后,使用 tftpboot 在 u-boot 中加载 RCW 文件,并执行如下 mmc 写入命令。 => tftpboot 0x90000000 rcw_2200_750_2900_19_5_2.bin -> mmc 设备 0;mmc 写入 0x90000000 8 1 => qixis_reset sd(执行此命令期间,D19 被打开和关闭) 对于 DDR 配置,从 SPD 读取时显示“不支持的原始卡版本。请手动将 CLK 设置为 DQS 偏移值。” Re: LX2160ARDB: DDR validation 如何将 LSDK 中的 RCW 文件(rcw_2200_750_2900_19_5_2.bin)加载到 SD 卡中? D19 是否已开启和关闭? 您可以参考以下关于使用 QCVS 工具对 LX2160ARDB 进行 DDR 验证的信息: QCVS_DDR_用户指南 谢谢! Re: LX2160ARDB: DDR validation (bin)50% 全部删除 (bin)51% 配置 cc cwtap:10.1.66.150 (bin)52% 显示 cc (bin)53% 源 IDcode.tcl 如果您能找到与“CCS Windows 版本 503.0.0.220812-p0.txt”相同的 LX2160A。 您可以使用以太网连接,IP 地址为:10.1.66.150 进行 DDR 验证。 谢谢! Re: LX2160ARDB: DDR validation 这是截图成功的结果。 June_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.png 我使用 USB 连接到 CWTAP。您需要为探测器设置正确的 IP 地址。 您能否成功运行“诊断连接”? June_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.png Re: LX2160ARDB: DDR validation 嗨,六月卢, 通过以太网连接,并能找到文本文件中提供的 LX2160A。 Priyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.png 但读取 SPD 时,DDR 配置窗口中显示“不支持的原始卡版本。请手动设置 CLK 到 DQS 偏移值。” 如何验证SPD值是否读取成功? Re: LX2160ARDB: DDR validation 连接诊断成功 Priyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.png 读取 SPD 后,DDR 配置如下所示 Priyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.png 请问DDR验证是否已成功启动? 我遇到的问题是, “开始验证”按钮已启用,但验证开始后立即被取消了。 Re: LX2160ARDB: DDR validation 嗨,六月卢, 按照用户指南,我再次创建了一个项目来进行DDR配置,并已完成SPD读取,如下所示。 Priyaa_0-1788498272408.pngPriyaa_0-1788498272408.pngPriyaa_0-1788498272408.pngPriyaa_0-1788498272408.png DIMM 模块插入 RDB 的 J14、J17 连接器中。 Re: LX2160ARDB: DDR validation 嗨,六月卢, 将开关(SW1)切换到 SD 卡模式(RCW 源存在)后,我们就能进行验证了。 感谢大家的支持。 Re: LX2160ARDB: DDR validation 你的屏幕截图似乎和我的不一样,缺少“返回”和“取消”按钮。 您是否已按照QCVS_DDR_User_Guide 1.1.1 进行操作?使用DDR配置工具吗? 谢谢! Re: LX2160ARDB: DDR validation 看起来你已经成功读取了 SPD,虽然截图和我这边看到的略有不同。 请将 SW1[1:4] 设置为 1001 以从 eMMC 启动,其中 RCW 源已配置为 DDR 验证。 另外,请确认“目标连接”是否显示为已连接,请参见屏幕截图。 确认后,即可进行 DDR 验证。 June_Lu_0-1788504721222.png Re: LX2160ARDB: DDR validation 嗨,六月卢, 要从 SD 卡启动 LX2160ARDB,是否需要在 u-boot 源代码中修改 DDR 寄存器值,还是直接从 DIMM 的 SPD 读取? 请帮忙澄清一下……谢谢。 Re: LX2160ARDB: DDR validation 对于带有 DIMM 插槽的标准 LX2160ARDB,DDR 寄存器通过读取已安装 DIMM 的 SPD 进行自动配置——此过程由 TF-A BL2 阶段 (ddr_init.c) 处理,而非 U-Boot。只有在 LX2160ARDB 上使用自定义 DIMM 时才需要修改 ATF 源代码。 如果还有其他问题,请另开新帖,以便我们更好地跟踪,因为这个案例已经很久没有更新了。 谢谢。
View full article
How to create a project without a board or device number listed in the VSC extension How do we create a new project in the VSCode MCUXpresso extension if the device/board is not listed in the library? The VSCode version is 1.135.0 and the MCUXpresso extension is 26.06.123. The MCUXpresso SDK dev is installed to version 26.06 and Arm GNU Toolchain is installed to 14.2.1.  We re-spin the code repo for LPC1768. It seems like if the part number is not in the list, we can't create the project...... (The create project button is greyed out in the attached snapshot.) Please advise. #VSCode #MCUXpress LPC1768FBD100  回复: How to create a project without a board or device number listed in the VSC extension Hi @Microsystemca  The New Project Wizard can only create projects for devices or boards that are included in an imported MCUXpresso SDK repository (or SDK Builder package). If the target device is not available in the SDK package, the wizard cannot find the required device or board definitions and therefore cannot create a new project directly. New Project Wizard — MCUXpresso for VS Code 26.08 documentation As a workaround, you can use MCUXpresso IDE to install the corresponding device support package and create a project for the target device there. Once the project has been successfully created and built in MCUXpresso IDE, you can then use the Import Project feature in MCUXpresso for VS Code to import the existing project and continue development within the VS Code environment. BR Harry 回复: How to create a project without a board or device number listed in the VSC extension Thank you for the workaround. We did that and it seems to be working. Quick note, MCUXpresso IDE is not fully compatible with the security standards adopted by some companies and it triggered a full scan of the computer after installation. The SHA/MCX hash is from unknown publisher. VSCode MCUXpresso is a direct installation because of the Microsoft certification. That's why users would prefer to have all the parts listed in the VSCode MCUXpresso repo.
View full article
88W9098 エネルギー検出 (ed_mac) チューニング こんにちは、 私たちは、SDIO経由でSDR50で動作するu-blox M2-JODY-W377に88W9098を使用しています。githubからlf-6.18.20_2.0.0のドライバ/ファームウェアバージョンがあります。2.4GHzチャネル6のアクセスポイントとして使っています。 ed_macを有効にする(wifi_mod_para.confで「init_hostcmd_cfg=nxp/ed_mac.bin」を使ったり、mlanutlをed_mac_ctrl_V3_909x.confで使用したり)すると、社内の適用テストの安定性やレイテンシが大幅に悪化する問題に直面しています: ed_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.png ここで詳しくは説明できませんが、これは複数のマシンを使い、88W9098アクセスポイントを中央に配置して、特定の社内段階をエンドツーエンドでレイテンシ測定するものです。ed_macを使うと平均200〜250ms高い曲線もありますが、全体的にカゲが強く、ランダムな「レイテンシ」が増えることもあります。 オフセット「ed_ctrl_2g.offset」を調整してみました。そして「ed_ctrl_5g.offset」をデフォルトの0x8とは異なる値に設定しましたが、試したどの値もテストには影響しませんでした。影響を与える唯一の方法は、有効化(2g/5g)を0にするか、起動時にファイルを読み込まないことです。 他に試せることはある? Re: 88W9098 Energy Detect (ed_mac) tuning @mjourdan様、 詳細な説明とテストデータをありがとうございました。ed_mac(エネルギー検出MAC)機能の設計上、実際に見られる動作は想定内ですが、いくつか確認して明確にしておくべき点があります。 なぜed_mac APモードでレイテンシが高くなるのか ed_mac機能は、EU ETSI EN 300 328適応性適合性試験のために特別に設計されています。その基本的な仕組みは、ファームウェアがチャネル上のエネルギーを閾値以上に検知した場合に、送信を能動的に抑制することです。アクセスポイントのシナリオでは、無線機が周囲エネルギーを検知するとバッファリングされたダウンリンクパケットが直接遅延し、測定しているレイテンシスパイクや「バースト」が発生します。オフセットパラメータを調整すると閾値感度(無線機のトリガーのしやすさ)は変わりますが、抑制動作自体は消えません。だからこそ、オフセット値がエンドツーエンドのレイテンシテストに測定可能な影響を与えなかったのです。 設定ファイルの不一致 あなたはed_mac_ctrl_V3_909x.confを使用しているようですね。当社のアプリケーションノートAN13756によると、88W9098の正しい設定ファイルは ed_mac_ctrl_V2_909x.conf です(デフォルトはed_ctrl_2g.offset = 0x08、ed_ctrl_5g.offset = 0x08)。V3バージョンは、ed_ctrl_txq_lockフィールドの値が異なり、このデバイスの検証済み構成ではありません。ed_mac_ctrl_V2_909x.confを使って、レイテンシの影響が改善するか試してみてください。 重要な質問:貴社の展開において、EUの適応性に関する要件を満たす必要がありますか? ETSI EN 300 328の適応性要件は、EU/EEA市場で運用され、最大RF出力が10 dBm EIRP以上と宣言されている機器にのみ適用されます。確認いただけますか: この機器はEU域内で展開されており、ETSI EN 300 328認証の対象となっていますか? あなたのモジュール(u-blox M2-JODY-W377)の宣言されたRF出力電力はどれくらいですか? EU準拠があなたのユースケースに必要でない場合、正しい解決策は単純 にed_mac構成をロードしない ことです。すでに確認済みでレイテンシ問題は完全に解決されます。 コンプライアンスが必要な場合は、まずed_mac_ctrl_V2_909x.confに切り替えることをおすすめします。レイテンシの問題が続く場合は、APモードの挙動を改善するための新しいファームウェアバージョンがあるかどうか検討できます。 上記の質問への回答をお知らせください。それに応じて対応させていただきます。 よろしくお願いいたします。 維東 Re: 88W9098 Energy Detect (ed_mac) tuning ウェイドンさん、ありがとう。はい、製品は確実に10dBm以上のEIRPを出力しており、EN 300 328準拠が必要です。 ed_mac_ctrl_V2_909x.conf ( https://github.com/u-blox/u-blox-sho-host-based/blob/main/JODY-W3/txpower_config/ed_mac_ctrl_V2_909x.conf ) を試してみましたが、動作に変化はありませんでした。 私たちが理解していないのは、このモジュールをDoodleLabs(QCA988Xベース)のものと交換し、同じ環境で同じテストを行うと、EN 300 328も認証される一方で、レイテンシの問題は全くないということです。だから、なぜ88W9098のed_mac実装がこのような問題を引き起こすのに、他のチップメーカーのものは起きないのか疑問に思っています。 バージョンlf-6.18.20_2.0.0の他に、hotfix/lf-6.12.49_2.2.0_hotfixも試しましたが、問題は依然として発生しています。 さらに詳しい情報はこちら: * JODYのアクセスポイントには2つのステーションがあります。 * テスト中にステーションとJODYの間で使用される帯域幅は非常に低い(約6KiB/s)ですが、主にSTA→AP方向の小さなパケットが多数含まれています。 Re: 88W9098 Energy Detect (ed_mac) tuning @mjourdan様、   お客様のご依頼内容を社内チームに報告いたしました。専門家の回答を一緒に待ちましょう。何か新しい情報が入り次第、すぐに皆さんと共有します。   よろしくお願いいたします。 維東 Re: 88W9098 Energy Detect (ed_mac) tuning @mjourdan様、 内部チームがこの問題を分析中です。以下の情報を教えていただけますか?社内チームから以下のフィードバックを受けました。 ====================================================== ドライバーのロードパラメータと、問題を再現するために使われた完全なドライバーのロード/アンロードコマンドシーケンス。 ed_mac_ctrl_V2_909x.conf 設定ファイル。 ログ さらなる調査のために、問題を再現する際に取得した画像です。 ホストの詳細(以下を含む): ホストプラットフォーム カーネルバージョン ドライバーバージョン 使用されているインターフェース(PCIe/SDIO)   これらの詳細は、お客様のセットアップと社内テストを関連付け、分析を迅速化するのに役立ちます。 ====================================================== ありがとうございます よろしくお願いいたします。 維東 Re: 88W9098 Energy Detect (ed_mac) tuning @mjourdan様、 何か進展はありましたか? よろしくお願いします! よろしくお願いいたします。 維東 Re: 88W9098 Energy Detect (ed_mac) tuning こんにちは、ウェイドンさん。現在you-bloxで問題のトラブルシューティングを行っているので、もしNXPにエスカレーションされた場合に備えて衝突を防ぐため、今は彼らとだけ相談するつもりです。助けてくれてありがとう。 Re: 88W9098 Energy Detect (ed_mac) tuning @mjourdan様、 はい、わかりました。 最新情報のご提供ありがとうございます。 よろしくお願いいたします。 維東 Re: 88W9098 Energy Detect (ed_mac) tuning @mjourdan様、 弊社の社内チームは、お客様からご報告いただいた問題に関して、追加のテストを実施いたしました。検査結果を皆様と共有したいと思います。調査に役立つ洞察が得られれば幸いです。 ================================================ リリースSD9098---17.92.1.p149.159-MM6X17552.p22 (FP92)を使用したQA環境で問題を検証しましたが、問題は再現しませんでした。 観察されたpingレイテンシは 約1〜2秒でした。 テスト手順: ビルドをロードし、リリース構成フォルダにあるデフォルトのed_mac_ctrl_V2_909x.confを使用してEDMACを有効にしました。 CH6でAPUTを起動しました。 2人の元STAをつなげた。 旧STAからAPUTへのpingテストを実施しました。 テストされたシナリオ: auto_ds=1、ps_mode=1 auto_ds=2、ps_mode=2 HT20およびHT40で構成されたAPUT セキュリティモード:OPENおよびWPA3 旧STA省電力モード:有効と無効 顧客が観察した問題を分析し再現するために、以下の情報も提供していただけませんか: お客様が使用するファイル/ビルドの詳細を読み込む 構成とテスト環境の詳細 顧客のセットアップで観察されたノイズ/干渉レベル 顧客側からの関連ログ この情報を得れば、より深い分析を行い、問題の再現を試みることができます。 ================================================ ありがとうございます。 よろしくお願いいたします。 維東
View full article
LX2160ARDB: DDR validation Hi, We have loaded the RCW file(rcw_2200_750_2900_19_5_2.bin) from the LSDK into SD card and in DDR configuration panel, when Read SPD is done we are getting as "Unsupported raw card revision. Set the CLK to DQS skew values manually."  How to perform DDR validation of LX2160ARDB in QCVS tool Priyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.png Re: LX2160ARDB: DDR validation Hi June Lu, Thanks for the support for USB the result of the command is (bin) 51 % findcc cwtaps 0 (bin) 51 % and for ethernet connection (bin) 51 % findcc cwtaps FSL07E3D5 (10.1.66.150): CodeWarrior TAP v2 Cortex-10 Probe Tip Boot Loader v1.0.1 Operating System v1.0.5 1 for now can we proceed further using ethernet connection for ddr validation? Re: LX2160ARDB: DDR validation (bin) 52 % show cc 0: USB open failure There are no command converters configured it indicates that the CWTAP cannot be detected through the USB connection. Please check the USB cable connection and ensure the CWTAP is properly recognized by the host PC. Also, please run the command below and share the result: (bin) 6 % findcc cwtaps Thanks. Re: LX2160ARDB: DDR validation Hi June Lu, CodeWarrior Version- Priyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.png (bin) 49 % log v CCS Linux Release Build 503.0.0.220812-p0 verbose logging (bin) 50 % delete all (bin) 51 % config cc cwtap (bin) 52 % show cc 0: USB open failure There are no command converters configured (bin) 53 % (bin) 53 % source IDcode.tcl Scanning for available TAPs connected via USB..... No TAPs found connected via USB ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + Available Remote Connections + + 1 - CodeWarriorTAP - + 2 - GigabitTAP - + + x - Exit Script without Changes + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Specify connection: can't read "CONNECTION()": no such element in array (bin) 54 % (bin) 54 % Able to connect through ethernet and ping the target. Even after updating CodeWarrior to v11.5.12, reading SPD gives same as "Unsupported raw card revision. Set the CLK to DQS skew values manually." Thank you Re: LX2160ARDB: DDR validation Please confirm the CodeWarrior version from Help → About CodeWarrior Development Studio for QorIQ LS Series (ARM v8 ISA). Please follow the instructions in "CCS Windows Release Build 503.0.0.220812-p0.txt" to verify the connection status. We recommend testing the USB connection first, followed by the Ethernet connection. It seems that the IP address has changed. Could you please confirm whether you can successfully ping the target? Re: LX2160ARDB: DDR validation Hi June Lu, We are using CodeWarrior 11.5.0 and the DIMM is original module given with the LX2160ARDB Updated CodeWarrior with archive com.freescale.armv8.11.5.12.GA.Lin.updatesite.221209.zip for v11.5.12 Now unable to detect the JTAG Priyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.png Thankyou Re: LX2160ARDB: DDR validation I followed your sequence and was able to read the SPD successfully. Could you please confirm which version of CodeWarrior you are using? Is it CodeWarrior 11.5.12? Also, is the DIMM an original module? Thanks. Re: LX2160ARDB: DDR validation Hi June Lu, After booting through FlexSPI, loaded the RCW file through tftpboot at u-boot and mmc write commands as below => tftpboot 0x90000000 rcw_2200_750_2900_19_5_2.bin => mmc dev 0; mmc write 0x90000000 8 1 => qixis_reset sd (during this command the D19 got turned on and off) And for DDR configuration, when reading from SPD getting as "Unsupported raw card revision. Set the CLK to DQS skew values manually." Re: LX2160ARDB: DDR validation How do you load the RCW file(rcw_2200_750_2900_19_5_2.bin) from the LSDK into SD card? Has the D19 turned on and off? DDR validation of LX2160ARDB in QCVS tool, you could refer to: QCVS_DDR_User_Guide Thanks Re: LX2160ARDB: DDR validation Diagnose Connection successfully done Priyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.png And DDR configuration after reading SPD is as below Priyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.png Could you please confirm whether DDR validation is started successully? Cause I'm facing an issue that the Start Validation button is enabled but the validation getting cancelled just after the start.. Re: LX2160ARDB: DDR validation Hi June Lu, Connected through ethernet and able to find LX2160A as provided in the text file Priyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.png But reading SPD gives as "Unsupported raw card revision. Set the CLK to DQS skew values manually." in DDR configuration window And how to verify the SPD values are read successfully? Re: LX2160ARDB: DDR validation This is the successful screenshot. June_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.png I used the USB to connect to the CWTAP. You need to set the Probe with correct IP address. Could you run the "Diagnose Connection" successfully? June_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.png Re: LX2160ARDB: DDR validation (bin) 50 % delete all (bin) 51 % config cc cwtap:10.1.66.150 (bin) 52 % show cc (bin) 53 % source IDcode.tcl If you could find LX2160A same as the "CCS Windows Release Build 503.0.0.220812-p0.txt". You could proceed using ethernet connection with IP address: 10.1.66.150 for ddr validation. Thanks Re: LX2160ARDB: DDR validation Hi June Lu, Following the user guide, created a project again for DDR configuration and reading of SPD has done as below Priyaa_0-1788498272408.pngPriyaa_0-1788498272408.pngPriyaa_0-1788498272408.pngPriyaa_0-1788498272408.png And the DIMM modules are inserted in the J14, J17 connectors of RDB Re: LX2160ARDB: DDR validation Hi June Lu, After changing the switch(SW1) to SD card mode where the RCW source is present, we were able to do the validation. Thanks for the support.. Re: LX2160ARDB: DDR validation It seem your screen shot is not same as me, missing button "Back" and "Cancel". Have you follow the QCVS_DDR_User_Guide, 1.1.1 Using DDR configuration tool? Thanks Re: LX2160ARDB: DDR validation It looks like you were able to read the SPD successfully, although the screenshot is slightly different from what I see on my side. Please set SW1[1:4] to 1001 to boot from eMMC, where the RCW source has been configured for DDR validation. Also, please confirm that "Target Connects" shows as connected see the screen shot. Once confirmed, you can proceed with the DDR validation. June_Lu_0-1788504721222.png Re: LX2160ARDB: DDR validation Hi June Lu, To boot the LX2160ARDB from SD card is DDR register values has to be modified in the u-boot source or it reads from SPD of DIMMs? Kindly clarify...thank you Re: LX2160ARDB: DDR validation For the standard LX2160ARDB with DIMM slots, DDR registers are configured automatically by reading SPD from the installed DIMMs — handled by the TF-A BL2 stage (ddr_init.c), not U-Boot. You only need to modify the ATF source if using custom DIMMs on the LX2160ARDB. If there are any new questions, please create a new thread so we can track them properly, as this case has been inactive for quite some time. Thanks.
View full article
S32k344 MBIST LBIST I'm in the process of implementing S32k344 BISTs in a green hills project. I'm using  SW32K3_SPD_1.0.6_D2512 in the source code form since I don't use Tresos or NXP DS. I was able to import most of the bist functions, except few defines that I'm not sure about (can't find them anywhere). Can anybody answer below questions. 1. Can I run LBIST MBIST while S32k344 is in lock step mode? 2. Is the following defines correct, I guessed by examining the code? #define BIST_MBIST_0 1U #define BIST_MBIST_1 2U #define BIST_MBIST_2 3U #define BIST_MBIST_3 4U #define BIST_MBIST_4 5U #define BIST_MBIST_5 6U #define BIST_MBIST_6 7U #define BIST_MBIST_7 8U #define BIST_MBIST_8 9U #define BIST_MBIST_9 10U #define BIST_MBIST_10 11U #define BIST_LBIST_0 0U the config data I used are as follows: static const BIST_CHANNEL_CONFIG_TYPE BistConfig[BIST_SAFETYBOOTCFG_NB] = { { (BIST_CHANNEL_TYPE)BIST_MBIST_0, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_1)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_1, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_2)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_2, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_3)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_3, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_4)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_4, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_5)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_5, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_6)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_6, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_7)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_7, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_8)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_8, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_9)) }, //#endif { (BIST_CHANNEL_TYPE)BIST_MBIST_9, (BIST_CONTROL_TYPE)((0x80100000U) | BIST_MBIST_PTR_VAL(BIST_MBIST_10)) }, { (BIST_CHANNEL_TYPE)BIST_MBIST_10, (BIST_CONTROL_TYPE)(0x00100000U) }, { (BIST_CHANNEL_TYPE)BIST_LBIST_0, (BIST_CONTROL_TYPE)((0x00001108U) | BIST_LBIST_PTR_VAL(BIST_NIL)) } }; Re: S32k344 MBIST LBIST Hello, 1. Can I run LBIST MBIST while S32k344 is in lock step mode? Yes. The S32K344 lockstep architecture does not prevent execution of STCU2 LBIST/MBIST. The BIST mechanism is part of the device safety infrastructure and is designed to test logic and memories managed by STCU2. The S32K3 Safety Manual explicitly lists both lockstep and STCU2 LBIST/MBIST as safety mechanisms of the device. 2. Is the following defines correct, I guessed by examining the code? The numerical values are essentially correct for S32K344, but including MBIST_10 (HSE_ROMs) in the Safety Boot configuration is not required from a safety perspective, and the recommended path is to use the validated SPD configurations directly. Best regards, Peter Re: S32k344 MBIST LBIST Peter,   Thank you very much for replying. I have been stuck with this BIST test issues for few days now. I'm testing with S32k344 White board, code is build with green hills multi IDE rev 8.1. The safety boot BIST is not passing. I'm sure the max clock requirement is met for core and peripherals. I have core_clk at 160Mhz from external crystal 16Mhz and PLL, AIPS_PLAT_CLK is 80Mhz, AIPS_SLOW_CLK is 40Mhz, DCM_CLK as 40 MHz, LBIST_CLK is 40Mhz,  QSPI_MEM_CLK is 160Mhz. I have this error when unit reset from bist run, DES register has 0x00408175, few reserved bits get set, and FES register has 0x2000 (doesn't make sense). would you kindly answer following questions? 1. with all the clock signals mentioned above, should they be enabled through MC_CGM->MUX_0_DC_x registers? I'm getting conflicting information, currently they are enabled. 2. In the reference manual, STCU2 chapter, there is this "While running MBIST on EMAC time stamp memory, MC_CGM.MUX_9_DC_0[DIV] should be appropriately configured to ensure EMAC_CLK_TS should be at least 1.5 times the AIPS_SLOW_CLK frequency." does that mean I have to config configure the clock and enable it in the MC_CGM->MUX_9_DC_0 register? 3. If I want to see the example code S32_SPD_Demo in SW32K3_SPD_1.0.6_D2512 package, I guess I need to install latest NXP design studio, import the spd zip file as update site, and also the RTD package, is that right? 4. I believe MBIST 10 is HSE_RAMS, MBIST 11 is HSE_ROMS, please see the table below from SPD doc folder. MBIST BIST ID BIST Instance Name Reset Domain Safety Boot Safety Diagnostic 0 SYS0_RAMS Main ü ü 1 SYS1_RAMS Main ü ü 2 DMA_TCD_RAM Main ü ü 3 CM7_0_TOP Main ü ü 4 CM7_1_TOP Main ü ü 5 FLEX_CAN_RAMS Main ü ü 6 QSPI_PERI_RAMS Main ü ü 7 EMAC_TSN_RAM Main ü ü 8 EMAC_RAMS Main ü ü 9 b03_ETF_RAMS Main ü ü 10 HSE_RAMS Main ü ü 11 HSE_ROMS Main   ü Re: S32k344 MBIST LBIST An update to my problem, after I enabled bit 8 and 9 in the STCU_RUNSW_REG to use PLL, I'm consistently seeing DES register 0x11 and FES register of 0x10. The bist_get_exec_status(BIST_SAFETYBOOT_CFG) return value is NOT RUN (0x03). There is nothing in the BIST ERR_STAT register, none of the END flag is set. In the FCCU NCF_S0 register, bit 2 is set. It seems BIST didn't start, but I do see the reset. I captured the register setting by writing to flash in the other bank. Re: S32k344 MBIST LBIST Hello, the STCU self-test sequence is being entered and reaches the ST_DONE reset phase. However, the STCU also reports an unrecoverable fault (STCU_URF), which explains why the SAF BIST driver subsequently reports BIST_NORUN. The issue therefore appears to be an STCU execution/configuration failure rather than a case where BIST was never triggered. On S32K3, seeing both a destructive and functional reset indication simultaneously is often a sign that you are looking at a reset history, not necessarily the immediate reset source Since you are porting the SW, I would start with simply just MBIST only test to see if it pass sourced from PLL. Also I would double check the clock settings for the tests. Best regards, Peter Re: S32k344 MBIST LBIST I checked the all possible clocks, I believe they are correct. I also compared the config data in the register with values from NXP studio spd example project, they are also correct. One new information. After system come back from BIST reset, I see value 0x18 in DCMROD3 register. How do I resolve this error? Thanks. XRen_Parker_0-1788544110794.pngXRen_Parker_0-1788544110794.pngXRen_Parker_0-1788544110794.pngXRen_Parker_0-1788544110794.png Re: S32k344 MBIST LBIST Hello, On S32K344, RCCU reports lockstep mismatches, and when connected with a debugger, it is not uncommon to get RCCU-related faults that would never occur in standalone execution. In case you follow the setting from example, you are looking at full BIST. Example is tested and it is fully working by default. But your port reporting URF fault, which tells me not everything is identical. Looking at STCU documentation user can set pointer to tests. 54.9.4 STCU2 Configuration (CFG) petervlna_0-1788766597312.pngpetervlna_0-1788766597312.pngpetervlna_0-1788766597312.png You can try shrinking tests first and the slowly add more tests. In MBIST and LBIST control registers you can set which test will be last: petervlna_1-1788766735386.pngpetervlna_1-1788766735386.pngpetervlna_1-1788766735386.png By pointing to for example in CFG register you can execute single MBIST partition: petervlna_2-1788766853581.pngpetervlna_2-1788766853581.pngpetervlna_2-1788766853581.png petervlna_3-1788766973925.pngpetervlna_3-1788766973925.pngpetervlna_3-1788766973925.png Best regards, Peter Re: S32k344 MBIST LBIST I tried to run mbist sequentially, and also tried individual mbist test ID. The outcome is the same, no new status observed. Can you confirm the following SCU2 register settings for safety boot right before trigger is set? Thanks. XRen_Parker_0-1788899133217.pngXRen_Parker_0-1788899133217.png Re: S32k344 MBIST LBIST This is for people in the community who are struggling with implementing LBIST/MBIST in the S32k344 microcontroller. After days of no progress made, I was able to see the test pass. I did with custom porting of the SPD driver 1.06. The driver code works except the fault need to be configured to unrecoverable fault. The following are the clocks that need to be configured, if any one of them is not set up correctly, the test will fail with BIST_NORUN(0x03) status because test sequence runs concurrently, no other status is seen, no completion bits set. 1. Config FXOSC module CTRL register to use external oscillator or crystal, this is the only way to get 160MHz, max for S32k344. 2. Config PLLDIG module for the PLL circuit, make sure max frequency is the output by configuring rdiv, mfi, and odiv2 bits in the PLLDV register. 3. Switch in the PLL clock for core_clk and emac_clk by following the reference manual steps,  MC_CGM_MUX_x registers setting. 4. config MC_CGM->MUX_0 and MC_CGM->MUX_9 registers to get following clock signals.   AIPS_PLAT_CLK as 80 MHz   AIPS_SLOW_CLK as 40 MHz   HSE_CLK as 80 MHz   DCM_CLK as 40 MHz   LBIST_CLK as 40MHz   QSPI_MEM_CLK as 160MHz    EMAC_CLK as 80MHz     Note: DON'T SET BIT 8 AND 9 IN THE RUNSW REGISTER, THE TEST WILL FAIL IF THEY ARE SET. This is not done in the SPD driver code. I mention this because there is conflicting info in the reference manual.
View full article
S32DS许可证将于2天后到期。 您好,NXP技术支持, 我需要延长我的 S32 Design Studio for S32 Platform 3.4 的评估许可证。 我在IDE许可窗口中找不到“申请许可”按钮。 许可证信息如下: 产品:S32平台专用S32设计工作室 版本:3.4 激活ID:60D2-8F18-EC11-211F 剩余评估天数:2 功能版本:3.4 功能状态:评估中(2天) 请帮忙延长此评估许可期限。 谢谢 & 此致敬礼 Re: S32DS License expiring in 2 day(s). 你好, 您的S32DS许可证已延期。请使用您之前的激活码重新激活S32DS。 Re: S32DS License expiring in 2 day(s). 你好, 我已经帮你申请了延期。 顺祝商祺! Peter
View full article
Interfacing the MC33665ATS4AE to the MC33774AtP1e daisy chain via tpl3 to a non-nxp MCU Hi, I am building a 36s system where for cell monitoring I am planning to use MC33774ATP1E in daisy chain via TPL3. To communicate with an mcu, I need an MC33665ATS4AE. For MCU, I am thinking of using a stm32 chip.  I need help with the drivers and communication. Will the autosar drivers SDK provided after NDA process, will help?  Re: Interfacing the MC33665ATS4AE to the MC33774AtP1e daisy chain via tpl3 to a non-nxp MCU Hello sahilHastin Good day! Yes, but since this involves secure documentation, I recommend opening a case on our official website, where we can assist you more privately. Have a great day and best of luck.
View full article
VSC拡張機能にボード番号やデバイス番号が記載されていないプロジェクトを作成する方法 VS CodeのMCUXpresso拡張機能で、デバイス/ボードがライブラリに表示されていない場合、新しいプロジェクトを作成するにはどうすればよいですか? VS Codeのバージョンは1.135.0、MCUXpresso拡張機能のバージョンは26.06.123です。MCUXpresso SDKの開発はバージョン26.06に、Arm GNU Toolchainは14.2.1にインストールされています。 LPC1768向けにコードリポジトリを再構築しました。部品番号がリストになければ、プロジェクトを作成できないようです......(添付のスナップショットでは「プロジェクト作成」ボタンがグレーアウトしています。) お知らせ下さい。 # VSCode #MCUXpress LPC1768FBD100 回复: How to create a project without a board or device number listed in the VSC extension こんにちは、 @Microsystemca 新しいプロジェクトウィザードは、インポートされたMCUXpresso SDKリポジトリ(またはSDK Builderパッケージ)に含まれるデバイスやボード用プロジェクトのみを作成できます。ターゲットデバイスがSDKパッケージに含まれていない場合、ウィザードは必要なデバイスやボードの定義を見つけられず、新しいプロジェクトを直接作成できません。 新しいプロジェクトウィザード — MCUXpresso for VS Code 26.08 ドキュメント 回避策として、MCUXpresso IDEを使って対応するデバイスサポートパッケージをインストールし、そこでターゲットデバイス用のプロジェクトを作成することができます。プロジェクトがMCUXpresso IDEで正常に作成・構築されたら、MCUXpresso for VS Codeの「プロジェクトインポート」機能を使って既存のプロジェクトをインポートし、VS Code環境内での開発を継続できます。 BR ハリー 回复: How to create a project without a board or device number listed in the VSC extension 回避策を教えていただきありがとうございます。私たちはそれを実行しましたが、うまくいっているようです。ちなみに、MCUXpresso IDEは一部の企業が採用しているセキュリティ標準と完全に互換性がなく、インストール後にコンピュータのフルスキャンがトリガーされました。SHA/MCXハッシュは発行元不明です。VSCode MCUXpressoは、Microsoftの認証を受けているため、直接インストールできます。だからユーザーはすべてのパーツをVSCode MCUXpressoリポジトリにまとめておきたいのです。
View full article
S32K142 PWM Signal input reading Hello Team, Is there any example available for PWM reading in S32K142 using FTM input capture? If yes, please share the example. Re: S32K142 PWM Signal input reading Hello @Julián_AragónM , Thank you so much for quick reply. One small doubt, can i use single CH to measure both duty cycle and period?  If i set input capture mode as DETECT BOTH EDGE. What measurement value i will get from IC_GetMeasurement? Re: S32K142 PWM Signal input reading Hello @nirmal_masilamani, You can refer to: Example 4. from AN5303: Features and Operation Modes of FlexTimer Module on S32K – Application Note. Example 2.5 Timed I/O (FTM) from AN5413: S32K1xx Series Cookbook – Application Note Ftm_Icu_Ip_BlinkLed_S32K144 example from RTD package (uses Ftm_Icu_Ip_EnableEdgeDetection API) ic_pal & ftm_signal_measurement examlpes from SDK You can also refer to some community posts: s32k1:How to measure PWM frequency and duty cycle on the same FTM channel S32K Input Capture S32K1-Calculate the motor speed based on the FTM Hope this helps. Best regards, Julián   Re: S32K142 PWM Signal input reading Hello @nirmal_masilamani, Input capture supports 3 modes: Capture on Rising Edge Only -> period only Capture on Falling Edge Only -> period only Capture on Rising or Falling Edge -> Need to read the level status through GPIO or CnSC [CHIS] bit to know the high-level pulse width or the low-level pulse width. NOTE: The CHIS bit should be ignored when the channel (n) is not in an input mode. NOTE: When the pair channels is on dual edge mode, the channel (n+1) CHIS bit is the channel (n+1) input value and not the channel (n) input value (this signal is the input signal used by the dual edge mode). For PWM duty cycle capture, you should use dual edge capture. Otherwise, you will only get the period of high level or low level. In the dual edge capture mode, only channel (n) input is used and channel (n+1) input is ignored. Julin_AragnM_0-1788457862022.pngJulin_AragnM_0-1788457862022.png IC_GetMeasurement will return the pulse width in ticks, which you can then use to calculate signal frequency:  /* Get the latest value */ inputCaptureMeas = IC_GetMeasurement(&ic_pal_1_instanceConfig, channel); /* Calculate the signal frequency using recorded data*/ inputCaptureMeas = frequency / (inputCaptureMeas); Best regards, Julián Re: S32K142 PWM Signal input reading Hello @Julián_AragónM , Thank you for reply. I am still little confused. To measure PWM signal, how many pins i need?  I am using IC_PAL for measuring. But i am unable to measure PWM using signal pin and single ch. RTD used V4.0.0
View full article
rt1186 调试问题 在 FRDM-IMXRT1186 开发板上启用 OEM_CLOSE 后,我无法再调试该设备。我在参考手册中看到可以使用 nxpdebugmbox 重新启用调试功能,但我尝试后没有成功。 yanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.pngyanyanwang_0-1788347257012.png 开发板 MCXC 安全(Edgelock | 安全启动 | OTP) Re: rt1186 debug issues 我已查看您提供的链接并按照推荐的步骤操作,但我仍然遇到同样的问题。 我只对图像进行了签名,并没有对其进行加密。我还设置了 OEM_CLOSE。 我使用 nxpdebugmbox 只是为了重新启用调试功能。 我已将高效密码学标准\\(SEC\\)项目及其相关日志作为附件上传。请您帮忙分析项目和日志,找出问题的原因吗? Re: rt1186 debug issues 你好@yanyanwang 在 高效密码学标准\\(SEC\\) 工具文档中,您可以找到有关调试身份验证的故障排除信息: https://docs.mcuxpresso.nxp.com/secure/latest/09_troubleshooting.html#debug-authentication 您还可以在以下位置找到一些有用的技巧: https://docs.mcuxpresso.nxp.com/secure/latest/07_generic_workflows.html#debug-authentication-workflow 如果这样还是不行,能否提供详细的配置信息?能否分享一下高效密码学标准(SEC)工具的工作区设置? Re: rt1186 debug issues @yanyanwang 这个问题似乎与 高效密码学标准\\(SEC\\) 26.03 有关。我们建议更新至高效密码学标准(SEC) 26.06版本。 给您带来的不便,我们深表歉意。 注:高效密码学标准(SEC) 26.06 还包含对 SPARSE 映像格式的修复。 Re: rt1186 debug issues 是的,谢谢。身份验证成功,但我仍然无法调试设备。 具体步骤如下: 1. 使用高效密码学标准(SEC)工具执行身份验证。 2. 身份验证成功。 3. 然后点击调试按钮开始调试。 4.然而,调试尝试失败了。
View full article
S32K142 PWM信号输入读取 各位团队成员,大家好! 是否有使用 FTM 输入捕获在 S32K142 中读取 PWM 的示例? 如果可以,请分享一下例子。 Re: S32K142 PWM Signal input reading 你好@Julián_AragónM , 非常感谢您的快速回复。 还有一个小疑问,我可以用单个通道同时测量占空比和周期吗? 如果我将输入捕获模式设置为检测两侧边缘。我从IC_GetMeasurement 函数会得到什么测量值? Re: S32K142 PWM Signal input reading 你好@nirmal_masilamani , 您可以参考: 示例 4.来自AN5303:S32K 上 FlexTimer 模块的特性和操作模式 – 应用笔记。 示例 2.5 定时 I/O (FTM) (摘自AN5413:S32K1xx 系列应用笔记) 来自 RTD 包的 Ftm_Icu_Ip_BlinkLed_S32K144 示例(使用Ftm_Icu_Ip_EnableEdgeDetection API) SDK 中的 ic_pal 和 ftm_signal_measurement 示例 您还可以参考一些社区帖子: s32k1:如何在同一FTM通道上测量PWM频率和占空比 S32K 输入捕获 S32K1 - 基于 FTM 的电机速度计算 希望这能帮到您。 此致, 朱利安   Re: S32K142 PWM Signal input reading 你好@nirmal_masilamani , 输入捕获支持 3 种模式: 仅限 上升沿 捕获 -> 句号 仅捕捉下落边缘 -> 句号 上升沿或下降沿捕获 -> 需要通过 GPIO 或 CnSC [CHIS] 位读取电平状态,以了解高电平脉冲宽度或低电平脉冲宽度。 注意:当通道 (n) 不在输入模式下时,应忽略 CHIS 位。 注意:当通道对处于双边沿模式时,通道 (n+1) CHIS 位是通道 (n+1) 输入值,而不是通道 (n) 输入值(此信号是双边沿模式使用的输入信号)。 对于PWM占空比捕获,应使用双边沿捕获。否则,你只会经历高水平或低水平的时期。在双边沿捕获模式下,仅使用通道(n)输入,而忽略通道(n+1)输入。 Julin_AragnM_0-1788457862022.pngJulin_AragnM_0-1788457862022.png IC_GetMeasurement 函数会返回以时钟周期为单位的脉冲宽度,然后你可以用它来计算信号频率: /* Get the latest value */ inputCaptureMeas = IC_GetMeasurement(&ic_pal_1_instanceConfig, channel); /* Calculate the signal frequency using recorded data*/ inputCaptureMeas = frequency / (inputCaptureMeas); 此致, 朱利安 Re: S32K142 PWM Signal input reading 你好@Julián_AragónM , 感谢您的回复。 我还是有点困惑。 要测量PWM信号,需要多少个引脚? 我使用IC_PAL进行测量。但我无法使用信号引脚和单个通道测量 PWM。 RTD 使用的是 V4.0.0 版本
View full article
MC33665ATS4AEをMC33774AtP1eデイジーチェーンにtpl3経由で非NXP MCUに接続します こんにちは。私は36sシステムを作っていて、セルモニタリングにはTPL3経由でデイジーチェーンで使うMC33774ATP1Eを計画しています。MCUとコミュニケーションを取るにはMC33665ATS4AEが必要です。MCUではSTM32チップを使うことを考えています。 ドライバやコミュニケーションについて助けが必要です。NDAプロセス後に提供されたAUTOSARドライバSDKsは役に立つでしょうか? Re: Interfacing the MC33665ATS4AE to the MC33774AtP1e daisy chain via tpl3 to a non-nxp MCU こんにちは、sahilHastinさん 良い一日! はい、しかしこれは安全なドキュメントが必要なため、公式ウェブサイトでケースを申し立てることをおすすめします。よりプライベートにお手伝いできるところです。 良い一日をお過ごしください。幸運を祈ります。
View full article
Regarding support for the CAN driver on the IMX95 FRDM board. Hi, I am currently working on the i.MX95 15x15 FRDM #https://www.nxp.com/design/design-center/development-boards-and-designs/FRDM-IMX95 platform and running FreeRTOS on the Cortex-A55 core. I am trying to bring up and enable the CAN interface from the A55 core. I am looking for any reference implementation, example project, driver code, or available code base that demonstrates how to initialize and use the CAN controller on the i.MX95 when running FreeRTOS on the A55 core. I have already tried referring to the Yocto/Linux CAN driver and device tree sources. However, I am facing difficulties in properly configuring and routing the CAN interface, mainly due to the involvement of: SCMI configuration Mailbox communication Pin multiplexing (IOMUX) from I2c CAN controller initialization and clock/resource configuration Because of these dependencies, it is difficult to directly adapt the Linux/Yocto driver and DTB configuration for my FreeRTOS environment. It would be very helpful if NXP could provide or point me to: Any FreeRTOS example demonstrating CAN bring-up on the i.MX95 A55 core. A reference CAN driver or BSP code for the i.MX95 15x15 FRDM. Examples showing the required SCMI and mailbox configuration for enabling CAN from the A55 core. Any documentation or reference for configuring the required pin muxing, clocks, and resources for CAN. Any available reference code, SDK example, or guidance would be greatly appreciated. Thank you for your support. Re: Regarding support for the CAN driver on the IMX95 FRDM board. Hi, For RTOS on A55 and testing CAN on it, please refer zephyr document. https://docs.zephyrproject.org/latest/boards/nxp/imx95_evk_15x15/doc/index.html https://docs.zephyrproject.org/latest/build/dts/api/bindings/can/nxp%2Cflexcan-fd.html#std-dtcompatible-nxp-flexcan-fd Best Regards, Zhiming
View full article
i.MX 95 的 ISP 调优 我所在的公司正在设计一款支持 Wi-Fi 功能的内窥镜。我们使用 i.MX8M 对 POC 进行了测试。我们使用的摄像头模块自带图像信号处理器(ISP),因此我们能够使用i.MX8M。 接下来我们希望使用 i.MX95,因为它自带 ISP。然而,我们注意到我们想要使用的图像传感器不在i.MX95 ISP 相机兼容性指南的列表中。我们计划使用 OV2740 或 OH02A10。 请问如何使用 i.MX95 ISP 来驱动这些传感器? Re: ISP tuning of i.MX 95 对于 i.MX95 上的 OV2740 或 OH02A10,请将这些传感器视为自定义/不支持的 ISP 启动,而不是开箱即用的相机模块。我不会因为兼容性指南中缺少某些架构就阻止这种架构选择,但我会计划驱动程序、设备树、媒体图和 ISP 调优工作。 要点: 项目 指导 兼容性指南状态 查阅到的 i.MX95 ISP 摄像头兼容性指南列出了 NXP 支持的传感器,例如 OmniVision OS08A20、OX05B1S、OX03C10 和 Onsemi AR0144,以及一些合作伙伴支持的传感器;我在查阅该指南、i.MX95 系列文档以及网络/社区资源后,并未在该列表中找到 OV2740 或 OH02A10。 i.MX95 ISP 功能 i.MX95集成的ISP支持多传感器应用,聚合处理性能高达500 MPixel/s,因此,如果传感器接口和带宽匹配,该平台在架构上非常适合用于RAW相机处理流程。 什么因素使新型传感器可行 NXP 的指导原则是,如果传感器与RAW Bayer输出兼容,并且遵循使用V4L2/媒体控制器的Linux 相机子系统,则可以移植尚未支持的传感器;UG10215 是开发所需集成的参考。 ISP路径 原始相机需要 i.MX95 NEO-ISP来解码和后处理原始传感器输出。 所需工作 UG10215涵盖了以下所需领域:i.MX95相机带宽计算、Linux内核启用、为新传感器实现libcamera CameraHelper、更新ISP/uGuzzi IPA配置文件、编译/更新、生成校准文件以及将新传感器添加到uGuzzi IPA配置中。 调优要求 uGuzzi IPA 使用动态调谐参数 (DTP) 文件中的传感器特定调谐数据;因此,新的 OV2740/OH02A10 设计应该包括 ISP 调谐/校准工作,而不仅仅是传感器流。 我的建议是: 如果进度风险至关重要,请优先选择 i.MX95 ISP 兼容性指南中已列出的传感器,因为这些模块具有 电路板支持包/软件包启用功能和经过验证的 ISP 调优资料。 如果内窥镜光学/外形尺寸需要 OV2740 或 OH02A10 ,则继续使用 i.MX95,但将其作为定制的摄像头端口进行配置: 确认传感器的具体模式:分辨率、帧速率、RAW Bayer 位深度、通道数、通道速率、MIPI CSI-2 时序、嵌入式数据使用情况; 使用 UG10215 的带宽计算流程验证 i.MX95 CSI/ISP 带宽; 开发或改编 Linux V4L2 子设备驱动程序; 创建设备树端点和媒体控制器链接; 实现/更新 libcamera 支持,包括 CameraHelper; 为镜头+传感器+照明环境生成ISP校准/调优文件; 在医疗应用场景的照明范围内验证图像质量。 不要以为仅仅一个 OV2740 Linux 驱动程序就足够了。NXP社区中关于i.MX93平台上OV2740传感器的类似案例表明,当前的电路板支持包。/设备树/驱动程序并未针对该传感器进行配置,需要进行自定义驱动程序/设备树的开发;虽然该案例涉及的是i.MX93而非i.MX95,但值得注意的是,“传感器有驱动程序”并不等同于“平台已准备好ISP”。 在这两个传感器之间,我的选择更多地取决于哪个供应商/模块供应商能够提供完整的传感器启动包,而不是兼容性列表:精确模式的寄存器表、MIPI 时序、镜头/遮光数据、颜色校准目标以及对 ISP 调谐的支持。对于生产型内窥镜而言,最大的风险可能不是基本的 CSI 采集;而是在照明、温度、镜头变化和制造差异的情况下实现稳定的 ISP 图像质量。 结论:根据已检索到的兼容性证据,OV2740/OH02A10 不是即插即用的 i.MX95 ISP 选择;只有当您预算了完整的 i.MX95 RAW Bayer 传感器端口和使用 UG10215 进行 ISP 调谐工作时,它们才是可行的候选方案。
View full article
MAC Not Generated in Virtual ECU Level 4 with HSE 108.0 HEX Image Description We are working with Synopsys on the Level-4 Virtual ECU (vECU) for the GM program. For the latest HSE integration, we have adopted HSE version 108.0. During validation in the virtual environment, we observed different behavior depending on the HSE image format: HSE Envelop Format HSE image size: approximately 157 KB HSE loads successfully in the virtual environment. MAC is generated successfully. CYS Info Block is initialized as expected. 2. HSE HEX Format HSE image size: approximately 378 KB HSE image loads into the virtual environment. However, MAC is not generated. Due to the missing MAC generation, the CYS Info Block is not initialized. Based on our discussion with Synopsys-GM, we understand that the existing PFLASH_iROM script needs to be updated to support/adopt the new HSE HEX image format. Request We would like to have a discussion to walk through the issue we are facing in the virtual environment and understand the required changes to the PFLASH_iROM script/configuration for supporting the new HEX-based HSE image. Could we schedule a discussion on September 4 at 9:00 AM EST?/ you can provide your convenient time We can demonstrate the issue and compare the behavior between the Envelop and HEX formats during the discussion. Environment: Program: GM EAGM Platform: Level-4 Virtual ECU MCU: NXP S32K388 HSE Version: 108.0 Virtualization Environment: Synopsys Issue Area: PFLASH_iROM script update Re: MAC Not Generated in Virtual ECU Level 4 with HSE 108.0 HEX Image Hi @DhilipRaja91  Please note that the HSE FW version currently in use is a Premium version. Support for this firmware through this support channel falls outside our scope, as we do not have access to the required information due to the security restrictions associated with automotive software of this nature. We kindly ask that you contact your NXP representative for further assistance regarding this matter. They will be able to provide the appropriate support and guidance. We appreciate your understanding and cooperation. BR, VaneB
View full article
NXP S32G2RDB2 EVB EMMC を使用して BL32 と fip.bin をフラッシュしています -「通知: リセット状態: 電源投入リセット」 こんにちは、 @nxp TechSupport さん。 EMMC「「NOTICE: リセット状態:電源オンリセット」の問題について、S32G2RDB2ボードでサポートをお願いします。 1. QSPIは正常に動作しており、Enterキーを押すとU-bootコマンドプロンプトが表示されます。 2. SDカードも動作します。ユーザーマニュアルに記載されたセクターでU-bootコマンドプロンプトに入るパーティションテーブルを作成しました:「「p1 8192, p2 16384, p3 147456」 3. EMMCを発行する: EMMC は「NOTICE: Reset status: Power-On Reset」という問題を示しています。パーティションを作成するために、SD カードと同じ手順に従いました。 a) 最初の512はMBR用に予約されています b) bl2_w_dtb.s32が0で点滅 c) fip.binがアドレス0x400000で点滅している EMMCの問題を直すためにできるだけ早くサポートしてください。実際の要件は EMMCだけです。 ログ: EMMC_auto_boot.txt - 問題ログ EMMC_image_flashed_via_SD_logs.txt - SDカードで試した同じEMMCイメージの動作ログ EMMCイメージ:EMMC_BL2_FIP_FAT.zip Re: NXP S32G2RDB2 EVB Flashing BL32 and fip.bin using EMMC -"""NOTICE: Reset status: こんにちは、イエスット サポートシステムで同じCASEを受け取りました。サポートし、返信します。 BR ジョーイ
View full article
NXP S32G2RDB2 EVB Flashing BL32 and fip.bin using EMMC -"""NOTICE: Reset status: Power-On Reset""" Hi @nxp TechSupport Kindly support me for the issue with EMMC """NOTICE: Reset status: Power-On Reset""" on S32G2RDB2 board. 1. QSPI is working able to see U-boot command prompt after hitting enter. 2. SD card also working -created the partition table it is allowing to enter U-boot command prompt with mentioned sectors in the user manual as follows : """p1 8192, p2 16384, p3 147456""" 3. ISSUE EMMC: EMMC is giving an issue as """NOTICE: Reset status: Power-On Reset""" followed the same SD card procedure for creating partitions. a) first 512 reserved for MBR  b) bl2_w_dtb.s32 flashing at 0 c) fip.bin flashing at 0x400000 Please support me ASAP to fix issue with EMMC, Actual requirement is only with EMMC. Logs: EMMC_auto_boot.txt- issue logs EMMC_image_flashed_via_SD_logs.txt- same EMMC image tried with SD card its working logs' EMMC Image: EMMC_BL2_FIP_FAT.zip  Re: NXP S32G2RDB2 EVB Flashing BL32 and fip.bin using EMMC -"""NOTICE: Reset status: Hi,yesut I have received your same case in the support system; I will support and reply to you on it. BR Joey
View full article
NXP S32G2RDB2 EVB 使用 EMMC 刷写 BL32 和 fip.bin -“注意:RESET 状态:上电复位” 您好@nxp技术支持 请协助我解决 S32G2RDB2 板上的 EMMC“注意:RESET 状态:上电复位”问题。 1. QSPI 工作正常,按下回车键后可以看到 U-boot 命令提示符。 2. SD 卡也正常工作——已创建分区表,允许使用用户手册中提到的扇区进入 U-boot 命令提示符,如下所示:"""p1 8192, p2 16384, p3 147456""" 3. EMMC 问题: EMMC 出现问题,提示“通知:RESET 状态:上电复位”。创建分区时,我按照相同的 SD 卡步骤进行操作。 a) 前 512 个座位预留给 MBR b) bl2_w_dtb.s32 闪烁频率为 0 c) fip.bin 正在 0x400000 处刷写 请尽快协助我解决EMMC的问题,实际需求仅需使用EMMC。 日志: EMMC_auto_boot.txt - 问题日志 EMMC_image_flashed_via_SD_logs.txt - 相同的 EMMC 镜像尝试使用 SD 卡,其日志正常。 EMMC镜像:EMMC_BL2_FIP_FAT.zip Re: NXP S32G2RDB2 EVB Flashing BL32 and fip.bin using EMMC -"""NOTICE: Reset status: 你好,是的 我已在支持系统中收到您提出的相同问题;我会为您提供支持并回复您。 BR 乔伊
View full article
ISP tuning of i.MX 95 The company I am working for is designing a wifi enabled endoscope. We tested the POC using the i.MX8M. The camera modules that we used had their own ISP so we were able to use the i.MX8M.  Moving forward we would like to use the i.MX95 since it comes with its own ISP. However, we noticed that the image sensor that we would like to use is not in the list of i.MX95 ISP Camera Compatibility Guide. We plan on using either OV2740 or OH02A10. Kindly advise on using the i.MX95 ISP for these sensors. Re: ISP tuning of i.MX 95 For OV2740 or OH02A10 on i.MX95, treat the sensors as custom/unsupported ISP bring-up , not as out-of-box supported camera modules. I would not block the architecture choice on the fact that they are absent from the compatibility guide, but I would plan for driver, device-tree, media graph, and ISP tuning work. Key points: Item Guidance Compatibility-guide status The retrieved i.MX95 ISP Camera Compatibility Guide lists NXP-supported sensors such as OmniVision OS08A20, OX05B1S, OX03C10, and Onsemi AR0144, plus several partner-enabled sensors; I did not retrieve OV2740 or OH02A10 in that list after checking the guide, i.MX95 family docs, and web/community paths.  i.MX95 ISP capability i.MX95’s integrated ISP supports multi-sensor use and up to 500 MPixel/s aggregate processing performance, so the platform is architecturally appropriate for raw-camera pipelines if the sensor interface and bandwidth fit.  What makes a new sensor viable NXP guidance is that a sensor not already supported can be ported if it is compatible with RAW Bayer output and follows the Linux camera subsystem using V4L2/media controller ; UG10215 is the reference for developing the required integration.  ISP path Raw cameras require the i.MX95 NEO-ISP to decode and post-process the raw sensor output.  Work required UG10215 covers the needed areas: i.MX95 camera bandwidth calculation, Linux kernel enablement, implementing a libcamera CameraHelper for a new sensor, updating ISP/uGuzzi IPA configuration files, compiling/updating, calibration-file generation, and adding a new sensor to the uGuzzi IPA configuration.  Tuning requirement uGuzzi IPA uses sensor-specific tuning data in a dynamic tuning parameters — DTP — file ; therefore, a new OV2740/OH02A10 design should include ISP tuning/calibration effort, not just sensor streaming.  My recommendation is: Prefer a sensor already listed in the i.MX95 ISP compatibility guide if schedule risk is critical, because those modules have BSP/software-pack enablement and validated ISP tuning collateral. If OV2740 or OH02A10 is required by the endoscope optics/form factor , proceed with i.MX95, but scope it as a custom camera port: confirm the exact sensor mode: resolution, frame rate, RAW Bayer bit depth, lane count, lane rate, MIPI CSI-2 timing, embedded-data usage; verify the i.MX95 CSI/ISP bandwidth using UG10215’s bandwidth-calculation flow; develop or adapt the Linux V4L2 subdevice driver; create the device-tree endpoints and media-controller links; implement/update libcamera support, including CameraHelper ; generate ISP calibration/tuning files for the lens + sensor + illumination environment; validate image quality over the medical use-case lighting range. Do not assume that an OV2740 Linux driver alone is sufficient. A similar NXP community case for OV2740 on i.MX93 showed that the current BSP/device tree/drivers were not configured for that sensor and that custom driver/device-tree work would be required; while that is i.MX93 rather than i.MX95, it is a useful caution that “sensor has a driver” does not equal “platform ISP-ready.”  Between the two sensors, I would base the choice less on the compatibility list and more on which vendor/module supplier can provide the complete sensor bring-up package: register tables for the exact modes, MIPI timing, lens/shading data, color calibration targets, and support for ISP tuning. For a production endoscope, the largest risk is likely not basic CSI capture; it is achieving stable ISP image quality across illumination, temperature, lens variation, and manufacturing spread. Bottom line: OV2740/OH02A10 are not plug-and-play i.MX95 ISP choices from the compatibility evidence retrieved; they are feasible candidates only if you budget for a full i.MX95 RAW Bayer sensor port and ISP tuning effort using UG10215.
View full article
使用 HSE 108.0 HEX 映像时,虚拟 ECU 4 级未生成 MAC 地址。 说明 我们正在与 Synopsys 合作,为通用汽车项目开发 4 级虚拟 ECU (vECU) 。 对于最新的 HSE 集成,我们采用了HSE 版本 108.0 。 在虚拟环境中进行验证时,我们观察到HSE图像格式的不同会导致不同的行为: HSE信封格式 HSE图像大小:约157 KB HSE已成功加载到虚拟环境中。 MAC地址生成成功。 CYS 信息块已按预期初始化。 2. HSE HEX 格式 HSE图像大小:约378 KB HSE镜像加载到虚拟环境中。 但是, MAC地址并未生成。 由于缺少 MAC 生成, CYS 信息块未初始化。 根据我们与 Synopsys-GM 的讨论,我们了解到现有的PFLASH_iROM 脚本需要更新以支持/采用新的 HSE HEX 映像格式。 申请它 我们希望进行一次讨论,以了解我们在虚拟环境中遇到的问题,并了解为了支持新的基于 HEX 的 HSE 映像,PFLASH_iROM 脚本/配置需要进行哪些更改。 我们能否安排在9月4日上午9点(美国东部时间)进行讨论?您可以提供您方便的时间。 我们可以演示这个问题,并在讨论过程中比较 Envelop 格式和 HEX 格式的行为。 环境: 程序:GM EAGM 平台:4级虚拟ECU MCU:NXP S32K388 HSE 版本:108.0 虚拟化环境:Synopsys 问题区域:PFLASH_iROM 脚本更新 Re: MAC Not Generated in Virtual ECU Level 4 with HSE 108.0 HEX Image 你好@DhilipRaja91 请注意,目前使用的 HSE FW 版本为高级版。由于此类汽车软件的**网络安全**限制,我们无法获取所需信息,因此通过此支持渠道为此固件提供支持超出了我们的服务范围。 请您联系您的恩智浦代表,以获取有关此事的进一步帮助。他们将能够提供适当的支持和指导。 感谢您的理解与合作。 BR,VaneB
View full article