Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
NFC 目前,我们发现支持的 PN7XX 芯片在某些 NFC XTS 测试用例中出现故障。请问谷歌是否计划从未来的 XTS 测试套件中移除相关的 B 型和 F 型卡模拟测试项?另外,NXP是否已向谷歌确认过这一具体方面? #PN7220 Re: NFC 你好@Max4 是的,这个问题已经提交,将会发布官方声明。 请稍等片刻。
View full article
模拟前端布局 我正在设计一款基于TI CC1310的PCB。我计划使用 SMA 连接的鞭状天线,在 915 MHz 左右的频率下运行。理想情况下,我希望在 50 kbs 或更低的速度下获得 4-5 公里的视距传输距离,如果我有一个不错的射频前端,这似乎是可以实现的。然而,射频绝对不是我的专长,所以我的计划就是尽可能地复制 CC1310 平衡-不平衡转换器和滤波器的布局。不幸的是,这比我预想的要复杂和昂贵得多,所以我很想知道在布局方面我还有多少回旋余地,以免彻底毁掉我的演出。 具体来说,TI 采用了一种堆叠结构,其接地层和顶部信号层之间的厚度为 0.175 毫米。如果我把尺寸扩大到 0.21 毫米,就能省下一些钱,我觉得这不会对性能产生太大影响,但我也不确定。我也可以通过更换一些被动元器件来节省一些精力,但我不知道这样做有多大风险。我注意到,即使是相同的零件编号,其封装尺寸也与TI电路板上使用的尺寸不同。我想这应该不会造成太大影响。最后,我想缩短滤波器末端与天线连接器/阻隔电容之间的线路,我估计只要保持阻抗为 50 欧姆,就不会有太大影响。 假设我将元器件保持得非常接近,并且布局对称,那么在不必担心性能下降的情况下,我可以对布局进行多大的改变?如果我进行上述任何更改,是否需要选择新的前端组件? 电平位移器 Re: Analog Front End Layout 你好s1hukla 关于NXP产品支持,我能为您做些什么? 谢谢您!
View full article
PN7160 Burning Hello, I am currently using a PN7160 kit ending with EVK, and we used the hat that connects to the pi, making sure it was seated correctly (as far as we know) and it worked perfectly yesterday making sure it was communicating over I2C, but today when we came back to the lab and plugged it in (unchanged from last night) some smoke started coming out of the IC on the PN7160, so we unplugged it The Pi boots up normally without the pn7160 on so I’m not sure what happened between yesterday and today but it was locked away and I am the only one with a key. We’re doing a sponsored project with Toyota, and he advised us to talk to the support team, so we were just seeing if y’all had any advice or idea what happened Re: PN7160 Burning We don't meet this issue before. I would suggest you to try another PN7160 EVK board.
View full article
RW612 - Triple Antenna RF front-end Hello I would like to use RW612 in Triple Antenna setup where Bluetooth, Wi-Fi 2GHz and Wi-Fi 5GHz  has own antenna. In your document AN14002 - RW61x Design Guide you only describe double and single antenna configuration. What is the correct RF front-end impedance matching (50 Ω) for pins RF_TR_5 (Wi-Fi 5GHz) and RF_TR_2 (Wi-Fi 2GHz) when each has own antenna? Is NXP providing a Front-end module (FEM) calibration file for triple antenna setup? Re: RW612 - Triple Antenna RF front-end Hello @MarcinM  We don't have sample tri antenna design for you refer. You may develop it yourself. About FEM calibration file, the calibration guide shows how to configure FEM part. You could refer to that document to custom your FEM calibration file. Best Regards Shaun
View full article
S32K14X_MCAL_安装 我尝试了很多次,但仍然无法成功安装许可证。造成这种情况的原因可能是什么? 无效的许可证文件。需要功能 AUTOSAR_MCAL_S32K14X 版本 4.2。 Re: S32K14X_MCAL_install 你好@xiaomingchen , 要使用 SW32K14-SMCL431-RTMC-1.0.1 软件包,需要一个 license.dat 文件。您可以在“许可证密钥”选项卡中下载所需的许可证,选择要下载的许可证(就您的情况而言,我看到您正在使用适用于 S32K1XX 平台的 AUTOSAR 4.3 RTM 1.0.3 版本 / SW32K14-SMCL431-RTMC-1.0.1 ),向下滚动并选择“查看”,最后选择“全部保存”。 这将生成一个license.dat文件,您需要在安装向导中输入该文件: 但是,该软件已停止支持和维护。我们建议改用最新的 RTD 驱动程序:实时驱动 (RTD) | NXP 半导体 。 此致, 朱利安
View full article
S32K14X_MCAL_install 何度も試しましたが、それでもライセンスを正常にインストールできません。これは何が原因でしょうか? ライセンスファイルが無効です。AUTOSAR_MCAL_S32K14X 機能バージョン 4.2 が必要です。 Re: S32K14X_MCAL_install こんにちは、 @xiaomingchen さん、 SW32K14-SMCL431-RTMC-1.0.1パッケージを使用するには、license.datファイルが必要です。必要なライセンスは「License Keys」タブでダウンロードし、ダウンロードするライセンスを選択してください(あなたの場合はS32K1XXプラットフォーム用のAUTOSAR 4.3 RTM 1.0.3リリース/SW32K14-SMCL431-RTMC-1.0.1を使っています)、スクロールして「表示」を選び、最後に「すべて保存」を選びます。 これにより、インストールウィザードに入力するlicense.datファイルが生成されます。 しかし、このソフトウェアは現在サポートおよびメンテナンスされていません。代わりに最新のリアルタイム・ドライバを使用することを推奨します:Real-Time ドライバ (RTD) |NXP半導体。 よろしくお願いします、 ジュリアン
View full article
RW612 - トリプルアンテナRFフロントエンド こんにちは Bluetooth、Wi-Fi 2GHz、Wi-Fi 5GHzそれぞれに専用アンテナを備えたトリプルアンテナ構成でRW612を使用したいと考えています。 あなたのドキュメントAN14002 - RW61x設計ガイド では、ダブルアンテナとシングルアンテナの構成のみが説明されています。 ピン RF_TR_5 (Wi-Fi 5GHz)と RF_TR_2 (Wi-Fi 2GHz)それぞれにアンテナがある場合、正しいRFフロントエンドインピーダンス整合(50 Ω)はどれくらいでしょうか? NXPは、トリプルアンテナ構成用のフロントエンドモジュール(FEM)校正ファイルを提供していますか? Re: RW612 - Triple Antenna RF front-end こんにちは、 @MarcinM さん。 参考までに、トライアンテナ設計のサンプルはありません。ご自身で開発することも可能です。FEMキャリブレーションファイルについては、キャリブレーションガイドにFEM部品の設定方法が記載されています。そのドキュメントを参照してFEMキャリブレーションファイルをカスタムできます。 よろしくお願いいたします。 ショーン
View full article
S32K312MINI-EVB: RESET LED stays on after first successful debug, cannot connect anymore Hello, Board: S32K312MINI-EVB / IDE: S32DS 3.5 / Debugger: on-board (Embedded Multilink Rev A) Power: 12V via J1, J19/J20 = 2-3 (also tried USB-C with 1-2) 1.With 12V power, the factory demo was running (D3 blue ON), and I successfully debugged and flashed an empty S32DS project (main.cwith only for(;;)). 2.After that, I cannot connect anymore.Error: “PEmicro GDB Launch Failure: The GDB Server was not able to establish a connection to the target processor (E54431355)”. 3.The RESET LED stays ON continuously, even right after power-up and before starting debug.(Before the first flash, the RESET LED turned off after aborting the connection.) 4.Voltages at J23 (VBAT) and J16 (P5V0) are normal.I tried full power removal (30 s), different power-up orders, delay after reset, and lower speed. I suspect the FS26 watchdog is not serviced by my empty application, so FS26 keeps the MCU in reset. How can I put the FS26 into debug mode (watchdog disabled) on the MINI-EVB, or otherwise recover the board? Thank you. Re: S32K312MINI-EVB: RESET LED stays on after first successful debug, cannot connect anymore Hello @hjkimmmm, By default, the FS26 operates in debug mode. To switch to normal operation, hardware modifications are required. Specifically, resistor R147 is populated by default to keep the FS26 in debug mode. To enable normal mode, R147 must be removed and R146 must be populated instead. You can see this from the FRDM-A-S32K312 schematic: Which LED indicator is on after flashing this blank project? D9 or D10 (or both)? Are you able to attach to the MCU (Debug Configuration > Startup > Attach to Running Target)? Have you tried to connect with an external debugger (using Ten-pin cortex debug interface on J7)? Can you share the blank project so I can analyze if any other configuration was uploaded by mistake to the MCU?  Best regards, Julián
View full article
S32K312MINI-EVB: RESET LED stays on after first successful debug, cannot connect anymore Hello, Board: S32K312MINI-EVB / IDE: S32DS 3.5 / Debugger: on-board (Embedded Multilink Rev A) Power: 12V via J1, J19/J20 = 2-3 (also tried USB-C with 1-2) 1.With 12V power, the factory demo was running (D3 blue ON), and I successfully debugged and flashed an empty S32DS project (main.c with only for(;;)). 2.After that, I cannot connect anymore. Error: “PEmicro GDB Launch Failure: The GDB Server was not able to establish a connection to the target processor (E54431355)”. 3.The RESET LED stays ON continuously, even right after power-up and before starting debug. (Before the first flash, the RESET LED turned off after aborting the connection.) 4.Voltages at J23 (VBAT) and J16 (P5V0) are normal. I tried full power removal (30 s), different power-up orders, delay after reset, and lower speed. I suspect the FS26 watchdog is not serviced by my empty application, so FS26 keeps the MCU in reset. How can I put the FS26 into debug mode (watchdog disabled) on the MINI-EVB, or otherwise recover the board? Thank you. Re: S32K312MINI-EVB: RESET LED stays on after first successful debug, cannot connect anymore 你好@hjkimmmm , FS26 默认以调试模式运行。要恢复正常运行,需要进行硬件改造。 具体来说,电阻 R147 默认安装,以使 FS26 保持调试模式。要启用正常模式,必须移除 R147,并替换为 R146。从FRDM-A-S32K312原理图中可以看出这一点: 刷新此空白项目后,哪个 LED 指示灯亮起?D9 或 D10(或两者都有)? 您能否连接到 MCU(调试配置 > 启动 > 连接到运行目标)? 你试过连接外部调试器(使用 J7 上的十针 Cortex 调试接口)吗? 能否分享一下空白项目文件,以便我分析是否误将其他配置上传到了MCU? 此致, 朱利安
View full article
[i.MX8QXP] 256バイトを超えるI2C読み取りはタイムアウト。256バイトおよびページングされた読み取りは合格。 こんにちは、NXP チームの皆様、 AppleのMFi認証ICにアクセスしている際に、i.MX8QXP C0 MEKプラットフォームでI2Cのロングリード問題に直面しています。 MFiデバイスは、最大256バイトまでの読み取りにおいて正しく通信します。しかし、256バイトを超える単一の読み取りは必ずタイムアウトする。完全な証明書は128バイトのページに分割すると正常に読み取ることができます。 この問題が i.MX LPI2C PIOドライバの既知の制限や問題かどうかを確認するためのサポートを必要としており、適切なドライバ修正やDMA設定を推奨したいのです。 プラットフォームの詳細 プラットフォーム:NXP i.MX8QXP C0 MEK カーネル: Linux 6.6.52-lynx-lts-next Yocto baseline: Scarthgap-based build I2Cコントローラ: 5a810000.i2c Linuxアダプター: /dev/i2c-1 ドライバ: drivers/i2c/busses/i2c-imx-lpi2c.c コントローラーモード:PIO MFiスレーブアドレス: 0x10 I2C周波数:400kHz 証明書長レジスタ: 0x30 証明書データレジスタ: 0x31以降 このデバイスの証明書の長さ:608バイト 再現性:100% カーネル初期化によりPIOモードが確認されます。 imx-lpi2c 5a810000.i2c:pioモードを使用する i2c i2c-1: LPI2Cアダプタが登録されました ライブデバイスツリーは400kHzであることを確認しています。 MFiアプリケーションは以下のシーケンスを実行します。 レジスタ0x30を選択します。 2バイトの証明書の長さを読み取ります。 返された証明書の長さ: 0x0260 、つまり608バイト。 レジスタ0x31を選択します。 608バイトの読み取りを1回要求します。 申請結果: Reading Certificate Size Setting register 0x30 Reading register 0x30, 2 bytes Allocating Certificate Size: 608 bytes Reading Certificate Data Setting register 0x31 Reading register 0x31, 608 bytes Reading register 0x31, 608 bytes failed: EIO Reading register 0x31, 608 bytes Reading register 0x31, 608 bytes failed: ETIMEDOUT Reading register 0x31, 608 bytes Reading register 0x31, 608 bytes failed: ETIMEDOUT 動的デバッグ出力: i2c i2c-1: exit with: error: -5 i2c i2c-1: exit with: error: -110 i2c i2c-1: exit with: error: -110   Re: [i.MX8QXP] I2C reads above 256 bytes time out; 256-byte and paged reads pass こんにちは、 256バイトという制限は、単一のLPI2C受信コマンドの制限であり、必ずしもI2C転送全体の制限ではありません。受信コマンドには8ビットバイトカウントフィールドが含まれているため、1つのコマンドで最大256バイトを要求できます。608バイトの証明書の読み取りなど、より長い転送は、複数の受信コマンドとして実装する必要があり、通常は256バイトのチャンクと、最後に短いチャンクを使用します。 したがって、pioモードを使用するというメッセージ自体は、256バイトを超える転送が不可能であることを意味するものではありません。PIOモードでは、256バイトのチャンクが消費された時点で、ドライバーは次の受信コマンドを正しく発行しなければなりません。カーネルツリー内のlpi2c_imx_read_init()とlpi2c_imx_read_rxfifo()パスを確認し、現在のNXP/Linux LPI2Cドライバ実装と比較してください。コマンド長を608バイトに増やしても、コマンドフィールドがその値を表現できないため有効ではありません。 eDMAを使いたい場合は、TXとRX DMAの両方のチャネルが必要です。TXチャネルはデータの送信だけでなく、受信コマンドワードをLPI2C TX FIFOに入力するためにも使用されます。i.MX8QXP デバイスツリーノードに、ご使用の BSP に対応する正しい dmas および dma-names = "tx", "rx" エントリが含まれていること、および対応する eDMA リソースが利用可能であることを確認してください。チャネルIDは、他の i.MX デバイスからではなく、対応するi.MX8QXP BSPデバイスツリーから取得すべきです。 次のデバッグステップとして、256バイト、257バイト、608バイトの読み取り用にI2Cバスをキャプチャしてください。256バイトの境界で、コントローラが次の受信コマンドを出すか、ターゲットがACKまたはNACKを返すかを確認します。これにより、ドライバーコマンドやFIFOの問題とMFiデバイスプロトコルの制限を区別できます。 また、MFiデバイスが608バイトすべてに対してレジスタ0x31からの連続読み取りをサポートしているかも確認してください。デバイスがページサイズの読み取りを必要とする場合、128バイトのページを引き続き使用することが適切な回避策となります。 よろしくお願いいたします。 アルド。
View full article
MCALポートモジュールのPortPinModeはEB tresos 30.0で選択できませんでした EB tresos 30.0は29.0とは全く違うと感じます。バージョン29.0ではすべて順調だったが、バージョン30.0では多くの問題が発生した。 ポートモジュールの「PortPin Mode」設定項目については、GPIO以外の選択肢が見当たりませんでした。 例えばUART TXピンの場合、UART TXオプションに変更できませんでした。 その理由は?どうすれば解決できますか? Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 どなたかアドバイスをいただけませんか? Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 こんにちは、使っているChipとRTDのバージョンを教えてもらえますか? それに、従来の編集ソフトで試してみましたか? 1. EBをシャットダウンする。 2. C:\EB\tresos_32_1_4\configuration のdefaultPreferences.properties を編集します。 setLegacyEditorAsDefault: true 3. 保存してEBとモジュールを再度開き、設定を試してください。 Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 こんにちは、ご返信ありがとうございます。レガシーエディターに切り替えると正常に見えます。 その理由は?最新バージョンのエディタ(バージョン30.0)を使用すると、なぜそのような問題が発生するのでしょうか? Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 これはEB Tresos 30.0の新しいエディタとMCU/Portプラグインとの互換性の問題に関連している可能性があります。いずれにせよ、レガシーエディタに切り替えたことで問題が解決したと聞いて安心しました。
View full article
关于74AHC1G04GW的VOH和VOL特性的问题 我有一个关于 74AHC1G04GW 的 VOH 和 VOL 特性的问题。 根据数据手册,VOH 和 VOL 规格是在输出电流为 8 mA 时提供的。 但是,当实际输出电流小于 8 mA 时,我不知道如何确定或估计 VOH 和 VOL。 请问能否提供一些特性曲线、参考数据或推荐方法,用于估算输出电流低于 8 mA 时的 VOH 和 VOL? 如果在这种低电流条件下进行设计计算时,有推荐的 VOH 和 VOL 值可以使用,请告诉我。
View full article
FRDM-IMX93 ブートが「M33 prepare ok」で停止する原因は、JSC DDR (JSL4BAG167ZAMF) との非互換性です。 こんにちは、NXPコミュニティの皆さん、 現在、FRDM-IMX93開発ボードを使い、公式のFlexbuildツール(lsdk2606)を使ってDebianシステムを構築しています。しかし、ハードウェアの変更に関連していると思われるブートハングの問題に直面しています。 1. 問題点: ビルドしたイメージをSDカードに書き込み、ボードを起動した後、以下のSPLログが表示された後、システムがハングアップします。それ以降、出力はありません。 文章 编辑       1U-Boot SPL 2025.04 (Oct 14 2026 - 09:56:14 +0800)2PMIC: PCA9451A 3PMIC: Over Drive Voltage Mode 4DDR: 3733MTS 5DDR: 3733MTS 6M33 prepare ok 2.根本原因分析: 私のFRDM-IMX93ボード上のDDRチップは JSC LPDDR4X(部品番号:JSL4BAG167ZAMF)は、回路図に記載されているオリジナルのMicron DDRとは異なります。 U-Bootのソースコード(board/freescale/imx93_frdm/spl.c and Makefile)を分析したところ、Flexbuildが提供するデフォルトの lpddr4x_2gb_timing.c はMicron DDR向けに最適化されている可能性が高いことが分かりました。U-BootがこのMicronタイミングで3733MTSでJSC DDRを初期化しようとすると、初期化が失敗します( ddr_init() ループが「found DRAM ...matched」を印刷せずに2回実行されます)。その結果、Cortex-M33コアは初期化されていない/不安定なDDRメモリにアクセスしようとした際にハングします。 3. 質問: NXPは 、FRDM-IMX93ボード上のJSC DDR(JSL4BAG167ZAMF)向けに公式に検証された、 更新されたU-Boot BSPまたは特定のLPDDR4Xタイミングファイル(lpddr4x_2gb_timing.c)を提供していますか ? もし事前に構築されたタイミングファイルがなければ、この特定のJSCチップに推奨されるDDRパラメータ(例:ODT、Vref、tRFCなど)を教えてもらえますか?または正しいConfig Toolsテンプレートを教えていただけませんか? このDDRベンダーの変更に関して、FRDM-IMX93に関して特定のソフトウェアパッチが必要な既知のエラッタやハードウェアリビジョンはありますか? 何らかのガイダンスや公式の計時データがあれば大変ありがたいです。ありがとう! Re: FRDM-IMX93 Boot Hangs at "M33 prepare ok" due to JSC DDR (JSL4BAG167ZAMF) Incompatibil こんにちは、迅速かつ役立つご回答、本当にありがとうございます!U-Bootのソースツリーを確認したところ、ご指摘のコミット(4c35a6086aed)が確かに欠落していることが確認できました。このアップデートでJSC JSL4BAG167ZAMF 2CS LPDDR4Xデバイスのサポートを追加した結果、問題は完全に解決され、ボードは期待通りに動作しています。 Re: FRDM-IMX93 Boot Hangs at "M33 prepare ok" due to JSC DDR (JSL4BAG167ZAMF) Incompatibil 以下のアップデートがU-Bootのソースツリーに含まれているか確認していただけますか? https://github.com/nxp-imx/uboot-imx/commit/4c35a6086aedca2f6220382920242ad81ae372f6 このアップデートでは、新しいFRDM-IMX93ボードで使用されるJSC JSL4BAG167ZAMF 2CS LPDDR4Xデバイスのサポートが追加されました。 このアップデートが現在お使いのU-Bootバージョンに含まれていない場合、発生している問題の原因となっている可能性があります。 ありがとうございます。
View full article
PortPinMode of mcal port module could not be select in EB tresos 30.0 I find EB tresos 30.0 is very different from 29.0. Everything go smoothly in 29.0, but has many problem on 30.0. As for the configuration item "PortPin Mode" of port module, I could not see any option except GPIO. Such as this one for UART TX pin, I could not modify it to UART TX option. What's the reason for this? How to solve it? Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 Could any one give some advice? Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 Hi, Can you pls provide the Chip and RTD version you are using? Besides, have you tried in legacy editor?: 1. Shutdown EB。 2. Edit defaultPreferences.properties in C:\EB\tresos_32_1_4\configuration setLegacyEditorAsDefault: true 3. save, reopen EB and Module and try your configuration Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 It may be related to a compatibility issue between the new editor in EB tresos 30.0 and the MCU/Port plugin. In any case, I’m glad to hear that switching to the legacy editor resolved the issue. Re: PortPinMode of mcal port module could not be select in EB tresos 30.0 Hi, thanks for your reply. It looks normal after I switch to legacy editor. What's the reason for this? Why it has that problem when using latest editor of version 30.0?
View full article
MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) We cannot establish an SWD debug connection to any of our MCXW727CMFTBT samples (2 units, custom board), while the exact same probe/cable/setup connects immediately to an MCXW716C on an otherwise identical board (same schematic, same BOM, only the MCU differs). Part: MCXW727CMFTBT, HVQFN-48, date code 9D2604, lot PF2R73.00 Boards: custom PCB (10-pin Cortex Debug SWD, no ISP button), factory-blank/never-programmed SDK: MCUXpresso SDK 26.06.00 — application builds/links fine, failure is purely at debug-connect stage Symptom Fails identically with both NXP LinkServer 25.12.83 and a genuine SEGGER J-Link Plus:   LinkServer: Error: Wire Ack Fault - target connected? Ed:02: Failed on connect: Ee(42). No connection to chip's debug port J-Link: device MCXW727C_M33_0 / connect (VTref correctly read at 3.025V) ERROR: Wrong DM-AP IDCODE detected: 0xFFFFFFFF LinkServer's own MCXW7XX pre-connect script (LS_preconnect_MCXW7XX.scp) does issue a Debug Session Request automatically — still fails. nxpdebugmbox (SPSDK) manual Start Debug Session also fails with the same WIRE ACK FAULT. Already ruled out Probe/cable/adapter: confirmed working (same setup connects fine to MCXW716C) VDD_IO / P3V3 at the MCU: ~3.3V, correct SWDIO/SWDCLK continuity: good VDD_CORE (internal LDO): 1.065V, in range RESET_b at rest, cable unplugged: reads 0V instead of expected internal-pull-up ~3.3V (Ref. Manual §22.3.1) — on both units RESET_b forced externally to 3.3V during connect attempt (with VTref correctly read at 3.025V): no change, still fails with the same Wrong DM-AP IDCODE 0xFFFFFFFF Reproducible on 2 separate physical units / 2 separate boards Related thread Same exact error (Wrong DM-AP IDCODE 0xFFFFFFFF) reported here on the same device name, though in a different scenario (board worked, then broke after an erase/reprogram cycle): FRDM-MCXW72 no longer connects. Our units have never been flashed at all, so if there's a link to NBU/core state as that thread suggests, it apparently can also affect units that were never touched by the customer. Questions Any known erratum / boot-config requirement / default life-cycle state for early-production MCXW727CMFTBT (lot PF2R73.00) that would block SWD on a blank device beyond the standard Debug Mailbox procedure? RESET_b reading 0V at rest (contrary to documented internal pull-up) on both units — fabrication issue with this lot, or something else expected to drive this pin at POR? Recommended recovery procedure for this exact case that doesn't require UART-based ISP (our board has no on-board USB-UART bridge)? Happy to provide full logs, oscilloscope captures, or anything else useful on request. Protocol: BLE -> connectivity Protocol: Thread Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Thank you for the quick follow-up! To clarify, we tested with both probes, each with its own appropriate tool — not mixing LinkServer with the J-Link probe: NXP MCU-Link Pro, accessed through LinkServer 25.12.83, via the MCUXpresso for VS Code debug/flash integration (which launches LinkServer's gdbserver/flash-programmer under the hood). This is our normal day-to-day setup. Result: Wire Ack Fault - target connected? / Ed:02: Failed on connect: Ee(42). No connection to chip's debug port, including when LinkServer automatically runs its MCXW7XX-specific pre-connect script (LS_preconnect_MCXW7XX.scp, which issues a Debug Session Request). A separate, genuine SEGGER J-Link Plus (firmware V11.00) + J-Link Adapter CortexM (20-pin → 10-pin 0.05"), accessed through J-Link Commander V9.74 directly (not through LinkServer). Result: ERROR: Wrong DM-AP IDCODE detected: 0xFFFFFFFF on connect, with VTref correctly read at 3.025 V. We ran this second test specifically to rule out any LinkServer/MCU-Link-specific issue. Using this exact same J-Link Plus + adapter + cable + lab power supply setup, swapping only the target board for our MCXW716C variant (identical PCB, only the MCU differs), J-Link Commander connects successfully and identifies the Cortex-M33 core — so the probe, cable, adapter, and tool are confirmed working correctly; the failure appears specific to the MCXW727C part/board. We have not yet tried J-Flash or LinkFlash specifically, only J-Link Commander (connect) and LinkServer's built-in "debug" and "resurrect" flash-programmer modes — happy to try either of those if it would help narrow this down further. Let us know if there's any additional information or logs that would be useful. Best regards! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @Rwaka, hope you are doing well. In order to better understand the behavior you are observing, would you please confirm if for each case you are using an external J-Link debugger? Or have you tried also with an MCU-Link Pro? Additionally, please provide which tool (LinkFlash, J-Flash, J-Link Commander) you are using to access through SWD, as Linkserver is a utility for launching and managing GDB servers for NXP debug probes (e.g. MCU-Link Pro), therefore it is expected that a J-Link probe will not be detected by Linkserver. While the J-Link Plus probe will only be detected and usable along J-Link Commander/J-Flash tools. Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @Rwaka, thank you for providing additional information. I noticed that you mentioned that your Reset_b signal was reading 0V, this means that the device is in a constant reset state. Given this, I will ask some questions that will help to further analyze the observed behavior: Would you please clarify if there is any connected hardware/circuitry to the PTD0/RESET_b pin of the MCU? Is it floating? Is the VDD_IO_D rail measuring the proper voltage? Since this power domain drives voltage on the reset system. You may refer to AN14742 for reference on the power management hardware recommendations. Are you able to measure any resistance at RESET_b pin? If so, please provide the measured value. When you performed the forced reset externally, did you connect the external voltage directly to the reset pin? Please let me know the requested information. Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @Rwaka, thank you for the information. In order to better analyze the observed measurements, would you please share the schematic of your board? Additionally, given that the measured resistance had a low value, would you please try adding an external pull-up resistor of a value between 10kΩ-100kΩ? As recommended in the following community post: Design Considerations for Debug. Also, would you please share an oscilloscope capture of the observed reset signal at the RESET_b pin? Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @RomanVR, Thank you for your support. Here are the measurements and details regarding our hardware setup: Circuitry on PTD0/RESET_b: The PTD0/RESET_b pin (pin 23) is routed directly to pin 10 of our 10-pin SWD debug header (FTSH-105). There are no external pull-up resistors or decoupling capacitors on this net on the PCB; it relies entirely on the MCU's internal pull-up. VDD_IO_D Rail Voltage: The rail measures 3.28V directly at the pin, which is well within the expected nominal voltage per AN14742. Resistance at RESET_b pin: With the board unpowered, I measured an abnormally low resistance of 38 Ohms to GND on the RESET pin. External reset test: I added an external 4.7 kOhm pull-up resistor to 3.3V on the reset line to test if it would bring the pin high. However, it had no effect and the SWD connection still fails, which aligns with the 38 Ohms impedance to GND completely overpowering the pull-up resistor. Given that this exact 38 Ohms near-short to GND is present on both of our factory-blank MCXW727CMFTBT units—whereas our MCXW716C variant works out of the box on the same PCB layout—could this indicate a silicon/fabrication defect on this lot (lot PF2R73.00), or is there an internal hardware condition that would pull this line low? Best regards, Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello again, Follow-up with the requested tests, all performed on our third, genuinely virgin unit (never powered/touched before this): External pull-up (10 kΩ, within your requested 10kΩ–100kΩ range): RESET_b, unpowered, with 10 kΩ pull-up in place: 16 kΩ (healthy — consistent with the internal ~313 kΩ measured in isolation, in parallel with our external 10 kΩ) RESET_b, as soon as the board is powered, same 10 kΩ pull-up still in place: collapses to 0.013 V SWD connect attempt (same setup): still fails identically — ERROR: Wrong DM-AP IDCODE detected: 0xFFFFFFFF Oscilloscope on RESET_b (PTD0) at power-up: not a hard flat line as we initially reported — closer inspection (1ms/div, 500mV/div) shows a genuine transient: the pin rises to approximately 1V (not 3.3V), holds that partial level for ~1ms with a slight upward ramp, then drops sharply back down and stays low. This same transient shape is present both with and without the external 10 kΩ pull-up, and was confirmed probing directly at the MCU pin (not just at the debug connector) — so it's a genuine signal at the pin, not a cable/connector artifact. Widening the timebase to 100ms/div and then 1s/div confirms this is a single, one-time event — no retries, no repeating cycle. This looks like the MCU making one failed/partial attempt to release RESET_b, then permanently stalling, rather than a repeating brownout/watchdog loop or the pin being held at a hard 0V from the very first instant. Oscilloscope on OSC1 output (pin 3, SIT8918BA active oscillator): clean 32.000 MHz square wave confirmed present and stable — so the main system clock reaching EXTAL is ruled out as a cause. Additional data point — official FRDM-MCXW72 board: using this exact same probe, we successfully connected to and flashed a genuine NXP FRDM-MCXW72 evaluation board without any issue. The MCU marking on this board reads: MCXW72 / 7CMFTB / 3P57K / S1953603 — confirming it's the same part number (MCXW727CMFTB) and same mask set (3P57K) as our failing custom-board units, just a different lot/date code (S1953603 vs. our PF2R73.00). This strongly confirms the probe/cable/tooling are not at fault, and points to something specific to lot PF2R73.00 rather than the part number or mask set in general. Summary: RESET_b is electrically healthy pre-power (313 kΩ isolated / 16 kΩ with external pull-up), the 32 MHz oscillator is running correctly, yet RESET_b collapses to near-0V the instant power is applied and stays there — even against a 10 kΩ external pull-up — with SWD permanently unable to connect, including with reset held (r/h/connect). This points to the MCU itself actively driving/holding RESET_b low very early in its boot sequence and never releasing it, rather than a passive/external electrical issue. Reproducible on a completely untouched unit, with a working FRDM-MCXW72 (same probe) as a positive control. Schematic excerpt (RESET_b / SWD header net, clock section) attached. Let us know what would help most next — happy to try SWDCLK/SWDIO scope captures during a connect attempt, or any other test. Best regards! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @Rwaka, thanks for performing the requested tests Would you please share detailed pictures of your IC's? From both your custom boards and the used FRDM board. Additionally, about your schematic, I'd suggest referring to AN14802 - Migration Guide from MCX W71 to MCX W72 and AN14742 - Power Management Hardware for the MCX W72 in order to ensure that proper power supply configurations were taken (e.g. rule out unsupported power mode implementations or power misconfigurations) and narrow down the observed behavior. Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @Rwaka, Could you please confirm which power configuration approach have you implemented in your design? The previous question provides important context, given that, if you are using the "low-cost/bypass" supply configuration, it is recommended to leave DCDC_LX pin floating as stated in AN14742, if you have not implemented this supply configuration, the pin must not be left floating. Related to this topic, I'd suggest referring to Table 58. Recommended connection for unused interfaces of the MCXW72 Datasheet to ensure having a proper pin connection for your unused interfaces depending on your supply configuration. Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello, Went through AN14802/AN14742 against our schematic — one question before the IC pictures. DCDC_LX: left floating on our board (no external inductor), matching AN14742's "low-cost" config. But disabling the DC-DC requires a software write, which never happens on our blank/never-programmed units — so DC-DC stays at its hardware-default-enabled state with LX floating. Same exact layout is used on our working MCXW716C boards though. Could this (DC-DC enabled, LX floating) realistically block boot/SWD on a blank MCXW727C before any code runs? Would temporarily tying DCDC_LX to GND be a safe test, or should we avoid it (internal switch node, no inductor/snubbing)? IC pictures attached (custom board + FRDM board, chip markings). Best regards! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello, To confirm: our board uses the "low-cost/bypass" supply configuration — no external DC-DC inductor, DCDC_LX left floating. We cross-checked against Table 58 (Datasheet) as suggested. Our layout matches the recommendations there for the DC-DC related pins: DCDC_LX: floating ✓ (matches "Float" recommendation) VSS_DCDC: tied to GND ✓ (matches "Always connect to VSS" recommendation) We didn't find a discrepancy on this specific section of the schematic. Let us know if there's another pin/area from Table 58 you'd like us to specifically re-check, or if you have another angle to investigate next. Best regards! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @Rwaka, thanks for cross-checking with the shared documentation. Could you please share oscilloscope measurements of the signals at VDD_CORE/VOUT_CORE pins and at VDD_LDO_CORE pin? Additionally, if you cannot share your full schematic, would you please refer to the following community post: The best way to build a PCB first time right with KW47 (Automotive) or MCX W72 (IoT/Industrial)? At the end of the post, the following two files are shared: KW47 MCXW72 Design In checklist V3.xlsx: Checklist to determine if the design fully complies with the proper characteristics for the W72. KW45 - MCX W71 - KW47 - MCX W72 Minimum BoM Presentation Customers May26.pdf: Guidance on the recommended external components and connections for your configuration (LDO Mode). Please perform a crosscheck within the two specified files and let me know your findings. Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello, We found it — thank you for the guidance that led us there! Root cause: VOUT_SYS/VDD_SYS (pin 22) had no decoupling capacitor at all on our custom board — completely floating, no connection whatsoever. Comparing against the official FRDM-MCXW72 schematic you pointed us to, that board decouples this pin with 4.7µF + 1.5µF + 0.1µF in parallel (R36/LDO_SYS_BYPASS is DNP there too, so VDD_SYS is purely internally-generated, just heavily decoupled). We added a single 4.7µF capacitor between VDD_SYS and GND on our third (previously untouched) unit — SWD connects immediately and flashing works. Interestingly, the exact same floating VDD_SYS (no cap at all) is present on our MCXW716C boards and those work fine — so this appears to be a real behavioral difference between the W71 and W72 power management block (possibly related to the new DC-DC ramp control feature mentioned in AN14664, which W71 doesn't have), rather than a documentation gap — Table 58 does list VDD_SYS as "floating except the decoupling capacitor," but doesn't specify a minimum value, and it's easy to miss how critical it apparently is on the W72 specifically. We'll add proper decoupling (matching your reference value) to VDD_SYS on our next board revision, and will also check our other two units (which additionally had a self-inflicted RESET_b anomaly from earlier testing, unrelated to this). Thank you very much for staying with us through this — the Table 58 / minimum BOM cross-check suggestion was exactly what we needed. Really appreciate the support. Best regards! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Subject: Recommendation request: MCX W71 vs MCX W72 for a CE-certified industrial product with a life of more than 15 years Dear NXP team, We are developing an industrial product (contactless power and data connector) with a proprietary 2.4 GHz GenFSK link. Our PCB (48QFN) works with both the MCX W71 (MCXW716CMFTAT) and the MCX W72 (MCXW727CMFTB, supplied as MCXW727CMFTBT). We must now choose one of them and freeze the design before CE (RED) certification. The expected life of our product exceeds 15 years, and we cannot afford to re-certify if the component is discontinued or changed. Could you tell us which one you recommend for this use case, and why? In particular: 1. Which device do you recommend for a new design requiring availability for more than 15 years? Is either of them positioned as a legacy or non-recommended device for new designs? 2. For each of them, please confirm in writing the current lifecycle status, the minimum longevity period (10 or 15 years), the launch date used as reference, and the "remains in program until" date in the Product Longevity Program. An NXP community answer mentions "until 2040" for the W72, but we found no published end date for the W71. 3. Since our target exceeds the standard 15-year period, can the longevity of either device be extended ("Extended" status of the program)? If not, what do you recommend for covering a life of more than 15 years (last-time-buy, notice period before EOL, form-fit-function successor)? 4. Any planned PCN, NRND or EOL, and the planned migration path, if any. 5. Any planned mask/silicon revision or manufacturing site transfer that could change RF characteristics (output power, harmonics, spurious emissions). The two devices use different radio generations, so we assume our radio test report cannot be shared between them. Is that correct, and do you have RF characterization data that could help our test lab? A formal longevity statement that we can include in our certification file would be very helpful. Thank you in advance. Best regards, Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) Hello @Rwaka, hope you are doing well. Could you please help us create a separate post with your inquiry in order to redirect and properly address your questions to the corresponding team?  This helps us to have a better tracking of the technical questions, and to have a better support for our customers. Thank you for your understanding.
View full article
PCA82C251T/YM,118のVOL特性に関する質問 PCA82C251T/YM,118のVOL特性について質問があります。 データシートによると、最大VOLは出力電流10mAで1.5V、出力電流1mAで0.2×VCCと規定されている。 しかし、実際の出力電流が1mA未満の場合、VOLをどのように決定または推定すればよいのか分かりません。 出力電流1mA未満でのVOL推定の特性曲線、参考データ、または推奨される方法を教えていただけますか? このような低電流条件下での設計計算に推奨されるVOL値があれば、ぜひ教えてください。 Re: Question about VOL characteristics of PCA82C251T/YM,118 こんにちは、 yoshiki11457901 51 IVN製品については、データシート以外に追加のパラメータは提供していません。 したがって、電流から1mAを引いた場合、I4 = 1 mAのテスト条件下でのVOL値を参照できます。
View full article
MCXW727CMFTBT — 出厂空白设备上的 SWD 连接失败(2 台设备,故障相同) 我们无法与任何MCXW727CMFTBT 样品(2 个单元,定制板)建立 SWD 调试连接,而完全相同的探针/电缆/设置却能立即连接到其他方面完全相同的板(相同的原理图,相同的物料清单,只有 MCU 不同)上的 MCXW716C。 元件: MCXW727CMFTBT,HVQFN-48封装,日期代码9D2604,批号PF2R73.00;板:定制PCB(10引脚Cortex调试SWD,无ISP按钮),出厂空白/从未编程; SDK: MCUXpresso SDK 26.06.00 — 应用程序构建/链接正常,故障仅在调试连接阶段出现。 症状 使用 NXP LinkServer 25.12.83 和正版 SEGGER J-Link Plus 均出现完全相同的故障:   LinkServer: Error: Wire Ack Fault - target connected? Ed:02: Failed on connect: Ee(42). No connection to chip's debug port J-Link: device MCXW727C_M33_0 / connect (VTref correctly read at 3.025V) ERROR: Wrong DM-AP IDCODE detected: 0xFFFFFFFF LinkServer 自身的 MCXW7XX 预连接脚本 (LS_preconnect_MCXW7XX.scp) 会自动发出调试会话请求 — 但仍然失败。nxpdebugmbox (SPSDK) 手动启动调试会话也失败,出现相同的 WIRE ACK FAULT 错误。 已经排除 探头/电缆/适配器:已确认工作正常(同样的配置连接到MCXW716C也没问题) MCU 端的 VDD_IO / P3V3:~3.3V,正确 SWDIO/SWDCLK 连续性:良好 VDD_CORE(内部 低压差线性稳压器(LDO)):1.065V,在范围内 RESET_b 处于静止状态,电缆拔出:读取0V而不是预期的内部上拉 ~3.3V(参考)。手册第22.3.1节)— 两个单元 连接尝试期间,强制外部将 RESET_b 设置为 3.3V(VTref 读取正确为 3.025V):无变化,仍然失败,并出现相同的错误:DM-AP IDCODE 错误 0xFFFFFFFF 在两台独立的物理设备/两块独立的电路板上均可复现。 相关帖子 这里报告了完全相同的错误(DM-AP IDCODE 0xFFFFFFFF),设备名称相同,但情况不同(板卡工作正常,但在擦除/重新编程周期后损坏): FRDM-MCXW72 不再连接。我们的设备从未进行过任何刷机,因此如果像该帖子所暗示的那样与 NBU/核心状态有关联,那么它显然也会影响客户从未触碰过的设备。 问题 对于早期生产的 MCXW727CMFTBT(批号 PF2R73.00),是否存在任何已知的勘误/启动配置要求/默认生命周期状态,导致在标准调试邮箱程序之外的空白设备上阻止 SWD 操作? 两个单元的 RESET_b 在静止状态下读数均为 0V(与文档中记录的内部上拉电阻相反)——是该批次产品的制造问题,还是上电时会有其他因素驱动该引脚? 针对这种情况,有没有不需要基于UART的ISP(我们的板子没有板载USB-UART桥接器)的推荐恢复方法? 乐意根据要求提供完整日志、示波器捕获或其他任何有用的信息。 协议:BLE -> 连接性 协议:Thread Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 感谢您的快速跟进! 为了澄清,我们使用两种探针分别进行了测试,每种探针都使用各自合适的工具——没有将 LinkServer 与 J-Link 探针混用: NXP MCU-Link Pro ,通过LinkServer 25.12.83访问,通过 MCUXpresso for VS Code 调试/闪存集成(它会在底层启动 LinkServer 的 gdbserver/flash-programmer)。这是我们日常的正常工作安排。 结果:线路确认故障 - 目标已连接?/ Ed:02: 连接失败: Ee(42)。无法连接到芯片的调试端口,即使 LinkServer 自动运行其 MCXW7XX 特定的预连接脚本(LS_preconnect_MCXW7XX.scp,该脚本会发出调试会话请求)时也是如此。 一个独立的、正品的SEGGER J-Link Plus (固件 V11.00)+ J-Link Adapter CortexM(20 针 → 10 针 0.05 英寸),通过J-Link Commander V9.74直接访问(而不是通过 LinkServer)。 结果:错误:检测到错误的 DM-AP IDCODE:连接时为 0xFFFFFFFF,VTref 已正确读取为 3.025 V。 我们专门进行了第二次测试,以排除任何 LinkServer/MCU-Link 特有的问题。使用完全相同的 J-Link Plus + 适配器 + 电缆 + 实验室电源设置,仅将目标板更换为我们的 MCXW716C 型号(PCB 相同,只有 MCU 不同), J-Link Commander 连接成功并识别出 Cortex-M33 内核——因此确认探针、电缆、适配器和工具工作正常;故障似乎是 MCXW727C 部件/板特有的。 我们还没有专门尝试过 J-Flash 或 LinkFlash,只尝试过 J-Link Commander(连接)和 LinkServer 的内置“调试”和“恢复”闪存编程器模式——如果这有助于进一步缩小问题范围,我们很乐意尝试其中任何一个。 与我们联系,如果需要提供任何其他信息或日志。 顺祝商祺! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好@Rwaka ,希望你一切都好。 为了更好地了解您观察到的现象,请您确认一下,在每种情况下,您是否都使用了外部 J-Link 调试器?或者您是否也尝试过使用 MCU-Link Pro? 此外,请提供您用于通过 SWD 访问的工具(LinkFlash、J-Flash、J-Link Commander),因为 Linkserver 是用于启动和管理 NXP 调试探针的 GDB 服务器的实用程序(例如,因此,MCU-Link Pro),预计 Linkserver 不会检测到 J-Link 探针。J-Link Plus 探针只能与 J-Link Commander/J-Flash 工具一起被检测到和使用。 Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好@Rwaka ,感谢你提供补充信息。 我注意到您提到 Reset_b 信号读数为 0V,这意味着设备处于持续 RESET 状态。鉴于此,我将提出一些问题,以帮助进一步分析观察到的行为: 请问MCU的PTD0/RESET_b引脚是否连接了任何硬件/电路?它浮空吗? VDD_IO_D 轨电压测量结果是否正常?因为该电源域驱动复位系统上的电压。有关电源管理硬件建议,您可以参考AN14742 。 您能否测量 RESET_b 引脚的电阻?如果可以,请提供测量值。 当您从外部执行强制复位时,是否将外部电压直接连接到复位引脚? 请告知我所需信息。 Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好@Rwaka ,谢谢你提供的信息。 为了更好地分析观测到的测量结果,能否请您分享一下电路板的原理图? 此外,鉴于测得的电阻值较低,请尝试添加一个阻值在 10kΩ-100kΩ 之间的外部上拉电阻?正如以下社区帖子中所建议的:调试的设计考虑因素。 另外,能否请您提供一下在 RESET_b 引脚上观察到的 RESET 信号的示波器波形图? Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好@RomanVR , 感谢您的支持。以下是我们硬件配置的尺寸和详细信息: PTD0/RESET_b 上的电路: PTD0/RESET_b 引脚(引脚 23)直接连接到我们的 10 针 SWD 调试接头(FTSH-105)的引脚 10。该PCB网络上没有外部上拉电阻或去耦电容;它完全依赖于MCU的内部上拉电阻。 VDD_IO_D 轨电压:直接在引脚处测量到轨电压为3.28V ,这完全在 AN14742 规定的预期标称电压范围内。 RESET_b 引脚的电阻:在电路板未通电的情况下,我测量到 RESET 引脚对地电阻异常低,为 38 欧姆。 External RESET test: 我在 RESET 线上的 3.3V 处添加了一个外部 4.7 kΩ 上拉电阻,以测试它是否会将引脚拉高。然而,这样做并没有效果,SWD 连接仍然失败,这与 38 欧姆的接地阻抗完全压倒上拉电阻的情况相符。 鉴于我们两块出厂空白的 MCXW727CMFTBT 芯片都存在 38 欧姆近乎短路到地线的情况——而我们的 MCXW716C 芯片在相同的 PCB 布局上开箱即用——这是否表明该批次(批号 PF2R73.00)存在硅/制造缺陷,或者是否存在内部硬件状况导致该线路拉低? 顺祝商祺! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好,又见面了。 后续所有测试均在我们第三台全新未使用过的设备(此前从未通电/触碰过)上进行: 外部上拉电阻(10 kΩ,在您要求的 10kΩ–100kΩ 范围内): RESET_b,未通电,接有 10 kΩ 上拉电阻: 16 kΩ (正常 - 与单独测量的内部 ~313 kΩ 一致,与我们的外部 10 kΩ 并联) RESET_b,电路板上电后,由于仍然使用相同的 10 kΩ 上拉电阻,电压立即降至0.013 V。 SWD 连接尝试(相同设置):仍然失败,错误信息相同——错误:检测到错误的 DM-AP IDCODE:0xFFFFFFFF 上电时 RESET_b (PTD0) 的示波器波形:并非如我们最初报告的那样是一条硬平线——仔细观察(1ms/div,500mV/div)显示了一个真实的瞬态过程:引脚上升到大约1V (而不是 3.3V),以轻微的上升斜坡保持该部分电平约1ms ,然后急剧下降并保持低电平。无论是否使用外部 10 kΩ 上拉电阻,都会出现相同的瞬态波形,并且通过直接探测 MCU 引脚(而不仅仅是调试连接器)证实了这一点——因此,这是引脚上的真实信号,而不是电缆/连接器产生的伪影。将时间基准扩大到 100 毫秒/格,然后再扩大到 1 秒/格,可以确认这是一个单一的、一次性的事件——没有重试,没有重复循环。这看起来像是 MCU 尝试释放 RESET_b 一次失败/部分尝试,然后永久停止,而不是重复的欠压/看门狗循环,或者引脚从一开始就被保持在 0V。 示波器在 OSC1 输出端(引脚 3,SIT8918BA 有源振荡器)上显示:确认存在且稳定的干净 32.000 MHz 方波——因此,主系统时钟到达 EXTAL 的原因可以排除。 补充数据点——官方 FRDM-MCXW72 板:使用完全相同的探针,我们成功连接并刷写了真正的 NXP FRDM-MCXW72 评估板,没有任何问题。该板上的 MCU 标记显示为:MCXW72 / 7CMFTB / 3P57K / S1953603 — 确认其零件编号 (MCXW727CMFTB) 和掩模组 (3P57K) 与我们故障的定制板单元相同,只是批号/日期代码不同 (S1953603 对比我们的 PF2R73.00)。这有力地证实了探头/电缆/工具没有问题,并指出问题出在 PF2R73.00 批次上,而不是零件号或掩模组本身。 摘要:上电前 RESET_b 电气性能良好(313 kΩ 隔离 / 16 kΩ 带外部上拉),32 MHz 振荡器运行正常,但上电后 RESET_b 电压瞬间降至接近 0V 并保持在该电压状态——即使施加 10 kΩ 外部上拉电阻——SWD 始终无法连接,即使按住复位键(r/h/connect)也是如此。这表明 MCU 本身在其启动序列的早期就主动将 RESET_b 拉低,并且从未释放它,而不是被动/外部电气问题。在完全未改动的设备上可重复,以一台工作正常的 FRDM-MCXW72(相同探头)作为阳性对照。 附上原理图摘录(RESET_b / SWD 接头网络、时钟部分)。 请告诉我们接下来什么最有帮助——我们很乐意在连接尝试期间尝试 SWDCLK/SWDIO 示波器捕获,或者进行任何其他测试。 顺祝商祺! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) @Rwaka你好,感谢你执行了所需的测试。 请问您能否分享一下您的集成电路的详细照片?包括您定制的电路板和二手的FRDM电路板。 此外,关于您的原理图,我建议您参考AN14802 - MCX W71 到 MCX W72 的迁移指南和AN14742 - MCX W72 的电源管理单元硬件,以确保电源配置正确(例如)。排除不支持的电源模式实现或电源配置错误),并缩小观察到的行为范围。 Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好, 对照我们的原理图检查了 AN14802/AN14742——在 IC 图片之前有一个问题。 DCDC_LX:在我们的电路板上悬空(没有外部电感器),与 AN14742 的“低成本”配置相匹配。但禁用 DC-DC 需要软件写入,而这在我们空白/从未编程的设备上永远不会发生——因此 DC-DC 保持其硬件默认启用状态,LX 处于浮空状态。不过,我们正常工作的 MCXW716C 电路板也采用了完全相同的布局。 这种(DC-DC启用,LX浮空)是否真的能阻止空白MCXW727C在任何代码运行之前启动/写入? 将 DCDC_LX 暂时连接到 GND 是否是一种安全的测试方法,还是应该避免这样做(内部开关节点,没有电感器/缓冲电路)? 附图为集成电路图片(定制板+FRDM板,芯片标记)。 顺祝商祺! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好@Rwaka , 请问您在设计中采用了哪种电源配置方案? 前面的问题提供了重要的背景信息,因为如果您使用的是“低成本/旁路”供电配置,建议按照 AN14742 中所述将 DCDC_LX 引脚浮空;如果您没有实现此供电配置,则该引脚不能悬空。 关于这个主题,我建议参考MCXW72 数据手册中的表 58。表 58 为未使用的接口推荐连接,以确保根据您的电源配置,未使用的接口具有正确的引脚连接。 Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好@Rwaka ,感谢你对照共享文档进行核对。 能否提供一下VDD_CORE/VOUT_CORE引脚和VDD_LDO_CORE引脚的信号示波器测量结果? 此外,如果您无法分享完整的原理图,请参考以下社区帖子:使用 KW47(汽车)或 MCX W72(物联网/工业)首次正确构建 PCB 的最佳方法?文章末尾分享了以下两个文件: KW47 MCXW72 设计检查清单 V3.xlsx:用于确定设计是否完全符合 W72 的正确特性的检查清单。 KW45 - MCX W71 - KW47 - MCX W72 最低物料清单演示客户 5 月 26 日.pdf:针对您的配置(LDO 模式)推荐的外部组件和连接提供指导。 请对这两个指定的文件进行交叉核对,并将结果告知我。 Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好, 确认:我们的板采用“低成本/旁路”供电配置——没有外部 DC-DC 电感,DCDC_LX 浮空。 我们按照建议,对照表 58(数据表)进行了交叉核对。我们的布局符合那里关于直流-直流相关引脚的建议: DCDC_LX:浮空 ✓(符合“浮动”建议) VSS_DCDC:接地 ✓(符合“始终连接到 VSS”建议) 我们没有发现原理图这一部分存在任何差异。如果您希望我们专门重新检查表 58 中的其他引脚/区域,或者您有其他角度需要调查,请告诉我们。 顺祝商祺! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好, 我们找到了——感谢您的指导! 根本原因:我们定制的电路板上的VOUT_SYS/VDD_SYS(引脚 22)根本没有去耦电容——完全悬空,没有任何连接。与您指出的官方 FRDM-MCXW72 原理图相比,该板使用 4.7µF + 1.5µF + 0.1µF 并联对该引脚进行去耦(R36/LDO_SYS_BYPASS 在那里也是 DNP,因此 VDD_SYS 完全是内部生成的,只是进行了深度去耦)。 我们在第三个(之前未改动过的)单元的 VDD_SYS 和 GND 之间添加了一个 4.7µF 的电容——SWD 立即连接,刷写功能也正常工作。 有趣的是,我们的 MCXW716C 板上也存在完全相同的浮动 VDD_SYS(完全没有电容),而且这些板工作正常——因此,这似乎是 W71 和 W72 电源管理单元之间真正的行为差异(可能与 AN14664 中提到的新的 DC-DC 斜坡控制功能有关,W71 没有此功能),而不是文档上的疏漏——表 58 确实将 VDD_SYS 列为“除了去耦电容外,其余部分为浮动”,但没有指定最小值,很容易忽略它在 W72 上有多么关键。 我们将在下一个板版本中为 VDD_SYS 添加适当的去耦(与您的参考值匹配),并且还将检查我们的另外两个单元(它们在之前的测试中还出现了与此无关的自致 RESET_b 异常)。 非常感谢您一直陪伴我们——表 58 / 最小物料清单交叉检查建议正是我们所需要的。非常感谢您的支持。 顺祝商祺! Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 你好@Rwaka ,希望你一切都好。 请您另开一个帖子,详细说明您的问题,以便我们能将您的问题转交给相应的团队并得到妥善解答。 这有助于我们更好地跟踪技术问题,并为客户提供更好的支持。 感谢您的理解。 Re: MCXW727CMFTBT — SWD connection fails on factory-blank devices (2 units, identical failure) 主题:推荐请求:MCX W71 与 MCX W72,适用于寿命超过 15 年的 CE 认证工业产品 尊敬的恩智浦团队: 我们正在开发一款工业产品(非接触式电源和数据连接器),采用专有的 2.4 GHz GenFSK 链路。我们的 PCB(48QFN)可与 MCX W71(MCXW716CMFTAT)和 MCX W72(MCXW727CMFTB,以 MCXW727CMFTBT 形式提供)配合使用。我们现在必须从中选择其中一个,并在获得 CE(RED)认证之前确定设计方案。我们产品的预期寿命超过 15 年,如果元器件停产或更换,我们无法承担重新认证的费用。 您能否告诉我们,对于这种使用场景,您推荐哪一款,以及原因?尤其: 1. 对于需要保持可用性超过 15 年的新设计,您推荐哪种设备?它们是否被定位为过时设备或不推荐用于新设计的设备? 2. 请以书面形式确认每款产品的当前生命周期状态、最短使用寿命(10 年或 15 年)、作为参考,引用的用上市,不用发布上市日期以及产品寿命计划中的“计划截止日期”。NXP 社区的回答中提到 W72 的停产日期为“至 2040 年”,但我们没有找到 W71 的已公布停产日期。 3. 由于我们的目标超过了标准的 15 年期限,能否延长任一设备的寿命(该计划的“延长”状态)?如果没有,对于使用寿命超过 15 年的产品(最后一次购买、停产前通知期、外形、功能和尺寸都合适的后续产品),您有什么建议? 4. 任何计划中的产品变更通知 (PCN)、产品终止通知 (NRND) 或产品生命周期结束通知 (EOL),以及计划中的迁移路径(如有)。 5. 任何计划中的掩模/硅修改或制造地点转移,都可能改变射频特性(输出功率、谐波、杂散发射)。这两个设备使用不同世代的无线电技术,因此我们认为我们的无线电测试报告无法在它们之间共享。是这样吗?你们是否有可以帮助我们测试实验室的射频特性数据? 如果能有一份正式的资历证明,并将其纳入我们的认证文件中,将会非常有帮助。 提前谢谢您。 顺祝商祺!
View full article
Can_43_LLCE 1.0.9 (S32G): is post-build loadable configuration supported or planned? Hello, We are following up on "Do CAN_LLCE and LLCE_Af support Postbuild Loadable?" (April 2025). NXP support answered "Postbuild model" for Can_43_LLCE. The loadable question was left open. Do CAN_LLCE and LLCE_Af support Postbuild Loadable? - NXP Community Setup: S32G274A, S32G_LLCE_1_0_9 (Can_43_LLCE 1.0.9, RTD AUTOSAR 4.4). Goal: update CAN config as post-build loadable without reflashing the full application image. In the 1.0.9 package, we see: Post-build tables are const structures with absolute pointers, compiled into the application image. We found no loadable or relocatable format, S-record output, or loader for post-build data. Questions: Is post-build loadable configuration supported/planned for Can_43_LLCE? If yes, which version and when? If not, what is the supported way to update CAN filters without a full reflash? Is there an application note for post-build with Can_43_LLCE and Llce_Af? Thanks in advance, Ayman Re: Can_43_LLCE 1.0.9 (S32G): is post-build loadable configuration supported or planned? Hi,AymanYounis Thank you for contacting us and your information. I have received your question and will help you to check it. BR Joey Re: Can_43_LLCE 1.0.9 (S32G): is post-build loadable configuration supported or planned? Hi,AymanYounis Thank you for contacting us. According to the latest LLCE manual, currently CAN_LLCE and LLCE_Af do not support Postbuild Loadable. There are no definite plans to add this feature. According to internal suggestions, if a customer wants to propose a new change request, this requires consulting the marketing. More business information needs to be provided. We currently do not have relevant documents for reference. Apologize for the inconvenience caused. BR Joey
View full article
[i.MX8QXP] I2C 读取超过 256 字节的数据超时;256 字节读取和分页读取通过 您好,NXP团队: 我们在 i.MX8QXP C0 换成产品名,如“i.mx8-mek是……” 平台上访问 Apple MFi 认证 IC 时遇到了 I2C 长读取问题。 MFi 设备可以正确读取最多 256 字节的数据。但是,任何超过 256 字节的单次读取都会超时。将完整的证书分成 128 字节的页面后,即可成功读取。 我们需要技术支持来确认这是否是 i.MX LPI2C PIO 驱动程序中已知的限制或问题,并推荐合适的驱动程序修复或 DMA 配置? 平台详情 平台:NXP i.MX8QXP C0 MEK 内核: Linux 6.6.52-lynx-lts-next Yocto 基线:基于 Scarthgap 的版本 I2C 控制器: 5a810000.i2c Linux适配器: /dev/i2c-1 驱动程序: drivers/i2c/busses/i2c-imx-lpi2c.c 控制器模式:PIO MFi 从机地址: 0x10 I2C频率:400 kHz 证书长度寄存器: 0x30 证书数据寄存器: 0x31及之后 此设备上的证书长度:608 字节 可重复性:100% 内核初始化确认 PIO 模式: imx-lpi2c 5a810000.i2c:使用 PIO 模式 i2c i2c-1:LPI2C适配器已注册 实时设备树确认频率为 400 kHz: MFi应用程序执行以下操作: 选择寄存器0x30 。 读取两字节的证书长度。 返回的证书长度: 0x0260 ,即 608 字节。 选择寄存器0x31 。 请求读取单个 608 字节的数据。 申请结果: Reading Certificate Size Setting register 0x30 Reading register 0x30, 2 bytes Allocating Certificate Size: 608 bytes Reading Certificate Data Setting register 0x31 Reading register 0x31, 608 bytes Reading register 0x31, 608 bytes failed: EIO Reading register 0x31, 608 bytes Reading register 0x31, 608 bytes failed: ETIMEDOUT Reading register 0x31, 608 bytes Reading register 0x31, 608 bytes failed: ETIMEDOUT 动态调试输出: i2c i2c-1: exit with: error: -5 i2c i2c-1: exit with: error: -110 i2c i2c-1: exit with: error: -110   Re: [i.MX8QXP] I2C reads above 256 bytes time out; 256-byte and paged reads pass 你好, 256 字节边界是单个 LPI2C 接收命令的限制,不一定是整个 I2C 传输的限制。接收命令包含一个 8 位字节计数字段,因此一条命令最多可以请求 256 字节。较长的传输(例如读取 608 字节的证书)必须通过多个接收命令来实现,通常使用 256 字节的块和一个较短的块。 因此,使用 pio 模式消息本身并不意味着超过 256 字节的传输是不可能的。在 PIO 模式下,驱动程序必须在每消耗完一个 256 字节的数据块后,正确地发出下一个接收命令。请检查内核树中的 lpi2c_imx_read_init() 和 lpi2c_imx_read_rxfifo() 路径,并将其与当前的 NXP/Linux LPI2C 驱动程序实现进行比较。将命令长度增加到 608 字节是无效的,因为命令字段无法表示该值。 如果要使用 eDMA,则需要 TX 和 RX DMA 通道。TX 通道不仅用于发送数据,还用于将接收命令字馈送到 LPI2C TX FIFO。请验证 i.MX8QXP 设备树节点是否包含 电路板支持包。 的正确 dmas 和 dma-names = "tx", "rx" 条目,以及相应的 eDMA 资源是否可用。通道 ID 应该来自匹配的 i.MX8QXP 电路板支持包。设备树,而不是来自另一个 i.MX 设备。 作为下一步调试步骤,请捕获 I2C 总线 256 字节、257 字节和 608 字节读取的数据。在 256 字节边界处,检查控制器是否发出下一个接收命令,以及目标是否返回 ACK 或 NACK。这将区分驱动程序命令/FIFO 问题和 MFi 设备协议中的限制。 还要验证 MFi 设备是否支持从寄存器 0x31 连续读取全部 608 字节。如果设备需要页面大小的读取,继续使用 128 字节的页面是合适的解决方法。 此致敬礼/Saludos, 阿尔多。
View full article
FRDM-ADPT-MCX-M2: Wi-Fi Server Temperature Monitor In this lab, we'll learn how to access Application Code Hub directly from Visual Studio Code, download a https-wifi-server-temperature-monitor-demo, and run it on the FRDM-MCXN947 using IW610G-M2 + FRDM-ADPT-MCX-M2 to add WiFi capabilities. Hardware Requirements: FRDM-MCXN947 FRDM-ADPT-MCX-M2 IW610G-M2 Type C USB Cable Software Requirements: IDE: Visual Studio Code 1.130 or later SDK: V26.06.00 LTS Wi-Fi Server Temperature Monitor Lab Guide (function() { var wrapper = document.getElementById('lia-vid-6405436914112w960h540r316'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (view in My Videos) Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here 
View full article