Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
#ftm_pwm_S32K116 こんにちは、NXPの同僚の皆様: ftm_pwm_s32k116プロジェクトについて助けを求めています。実際のところ、コードや設定をどう変えても、MCUはデフォルトチャネル(FTM0-チャネル0、つまりPTD15)。 これが私の手順です。 1.サンプルから新しいプロジェクトをインポートします。 2.コンパイルするとすべて合格し、ピンマルチプレクサとフレックスタイマーの設定を確認しましたが問題はありませんでした(実際にはNXPのサンプルからなので、完全に正しいと思います)。 3.次に、それをS32K116に書き込みます。 4.PTD15の波形を観察しましたが、何も見つかりませんでした。ほぼ2日間試しました。 私のプロジェクトのzipファイルは以下のとおりです。ありがとうございます。 Re: #ftm_pwm_S32K116 プロジェクトを添付してください Re: #ftm_pwm_S32K116 こんにちは、 @Tracy_Lu さん。 まず、プロセッサ Expertを使っているので、古いソフトウェアバージョンを使っているようですね。S32K1デバイスで開発を始める場合は、最新のソフトウェアとツール、現在S32K1_S32M24X リアルタイム・ドライバ AUTOSAR R21-11 バージョン3.0.0の使用をお勧めします(S32K1用のリアルタイム・ドライバ)とS32プラットフォーム向けのS32 Design Studio(S32 Design Studio |NXP Semiconductors)を共同で提供しています。 しかし、S32K1 SDKsを使い続けたい場合は、最新のSDKsバージョンがS32 Design Studio for S32 プラットフォーム 3.4に付属していました。 また、EVBを使っているのかカスタムボードなのか教えていただけますか? 現在のソフトウェア環境を維持したい場合は、使っている正確なS32K1 SDKバージョンも共有していただけると助かります。 BR、VaneB Re: #ftm_pwm_S32K116 こんにちは、NXPの同僚の皆様: 迅速かつプロフェッショナルなご回答ありがとうございます。サンプルから別のプロジェクトS32K116_Project_FTMに変更し、コードを修正しました(gemini AIの支援を受けて)。コンパイルとデバッグ中に問題が発生するエンジニアの方々が解決できるよう、以下の点を共有したいと思います。 1.私はFTM機能を使用して、PMIC(TPS650366)のESM(エラー信号モニタリング)に応答します。 2.at 最初にftm_pwm_S32k116プロジェクトを使い、約2日間コンパイルとデバッグに失敗しました。割り当てられたピンで出力PWMが見当たりません。そして、Gemini AIの助けを借りて正しい設定とデバッグをしているはずです。 3.次に、S32K116_Project_FTM という名前の別の例を見つけ、それを試してコンパイルしましたが、エラーはありませんでした。そして、PTD15(FTM0CH0)/16(FTM0CH1) という構成済みピンの出力が得られました。初期周波数は 1Hz/5Hz ですが、ゴールが近いことがわかりました。 4. 実はPWM周波数は40KHz付近で必要なので、次のステップはシステムの周波数プリスケーラ、MOD値、CnV(デューティサイクル)を変更することだと分かっていますが、MOD値は変更できません(値は変えるだけでMCUのルート場所に書き込めません)。何度も試して、役立つ情報を探しました。 5.最後に、MOD値を変更したい場合は、いくつかの前提条件を満たす必要があることがわかりました。たとえば、クロックを閉じ、書き込み保護を解除する必要があります...。 6.以下はコンパイル後の私のコードで、正常に動作します(PTD16で約48KHzの出力)。 int main(void) { /*! * 初期化: * ======================= */ WDOG_disable(); /* ウォッチドッグを無効にする */ SOSC_init_40MHz(); /* 40 MHz水晶発振器用のシステム発振器を初期化します */ RUN_mode_48MHz(); /* クロックを初期化: 48 MHz システム、コア、バス、 24 MHz フラッシュ。*/    FTM0_init(); /* 8 MHz SIRCDIV1_CLK を使用して FTM0 を初期化します */    //FTM0_CH0_OC_init();    /* FTM0 CH0、PTD15 を初期化 */   FTM0_CH1_PWM_init();    /* FTM0 CH1、PTD16 を初期化 */   FTM0_CH6_IC_init();    /* FTM0 CH6、PTE8 を初期化します  */ FTM1_Init(); FTM1_CH1_PWM_init(); PORT_init(); /* ポートの設定 */   start_FTM0_counter();  /* FTM0カウンタを開始 */   /*! * 無限: * ======================== */ のために(;;)   { //FTM0_CH0_output_compare();/* 出力比較が一致した場合: */   /* ピンの切り替え(ハードウェアによる自動切り替え) */   /* フラグ 8 をクリア */   /* リロードタイマー */ //FTM0_CH6_input_capture(); /* 入力がキャプチャされた場合:フラグをクリアし、タイマーを読み取る */   } } 7.インポートコードは以下のとおりです(FTM0_init()、FTM0_CH1_PWM_init()): void FTM0_init(void) {/** * FTM0 クロック: * ================================================== */ PCC->PCCn[PCC_FTM0_INDEX] &= ~PCC_PCCn_CGC_MASK; /* 設定のためにクロックが無効になっていることを確認します */ PCC->PCCn[PCC_FTM0_INDEX] |= PCC_PCCn_PCS(0b010) /* クロックソース=1、8 MHz SIRCDIV1_CLK */ | PCC_PCCn_CGC_MASK; /* FTMレジスタのクロックを有効にする */ /*! * FTM0 の初期化: * =================================================== */ // 1. 最初のステップ:FTM 時間钟彻底关闭(CLKS = 0)、この時点では完全に構成可能な状態です FTM0->SC = 0x00000000; // 2. 2 番目:写保护并开启 FTM 完全モード volatile uint32_t dummy = FTM0->MODE; FTM0->MODE |= FTM_MODE_WPDIS_MASK; /* 禁止用写保护 */ FTM0->MODE |= FTM_MODE_FTMEN_MASK; /* 开启 FTM 完全モード */ // 3. 第三步:時钟关闭の安全状態下、顺利ハンドルMODと比较值写进去 FTM0->CNTIN = 0U; FTM0->MOD = 166 - 1; /* 8MHz / 166 ≈ 48.19 kHz */ // 4. 4 番目: 構成チャネル 1 (PTD16) は周縁 PWM モードです FTM0->CONTROLS[1].CnSC = FTM_CnSC_MSB_MASK | FTM_CnSC_ELSB_MASK; FTM0->コントロール[1].CnV = 83; /* 50% 占空比 (83 < 165) */ // 5. 第五章:极性と組み合わせモード清零 FTM0->COMBINE = 0x00000000; FTM0->POL = 0x00000000; // 6. 最後の一步:すべてのパラメータ已经安稳書入後,才真正开启道输出和時間钟源! FTM0->SC = FTM_SC_PWMEN0_MASK | FTM_SC_PWMEN1_マスク | FTM_SC_PS(0) /* PS = 0 (不分周波数) */ | FTM_SC_CLKS(1); /* CLKS = 1 (最終启アニメーション计数器) */ } void FTM0_CH1_PWM_init(void) { /** * FTM0、PWMモードでのチャネル1: * ================================================== */ FTM0->CONTROLS[1].CnSC = FTM_CnSC_MSB_MASK |FTM_CnSC_ELSB_MASK;  /* FTM0 ch1: エッジアラインメント PWM、低真パルス */ /* CHIE (ちゃん割り込みエナ) = 0 (デフォルト) */ /* MSB:MSA (チャンネルモード選択)=0b10、エッジアラインPWM */ /* ELSB:ELSA (chan Edge/Level Select)=0b10、low true */   FTM0->CONTROLS[1].CnV =  46875; /* FTM0 ch1 比較値 (デューティサイクル約75%) */ }
View full article
i.MX 8ULP SPI NANDブート:FCB0が破損した場合、ブートROMはFCB1にフォールバックしない こんにちは、NXPコミュニティの皆さん、 私はi.MX 8ULPを使用しており、SPI NANDフラッシュ(Winbond W25N04LW)からブートしています。 私の理解では、FCB0が破損した場合、ブートROMは自動的にFCB1に切り替わるはずです。しかし、 FCB0が破損すると、システムは起動に失敗します。具体的には、ブートROMはFCB1を読み込もうとすらしないようです。 以下は私の「SPI NANDブートパラメータ」ヒューズ設定です。 FlexSPI NAND検索ストライド :00(64ページ) FlexSPI NAND検索回数 :00(2) FlexSPI NAND CS間隔:00(100ns) FlexSPI NAND 列アドレス幅: 01 (13) その他のヒューズはすべてデフォルト値のままです。 プロトコルアナライザを使用してSPI通信を監視しました。電源投入時に、 i.MX 8ULPはページアドレス0x000000のFCB0を読み取るページデータ読み取り(13h)を発行します。 FCB0が破損しているため、Boot ROMは64ページの検索ストライドに基づくページアドレス0x000040でFCB1を読み取ると思っていました。しかし実際には、FCB1を試さずに再度FCB0を読み込もうとします。 参考までに、私のSPI NANDメモリマップは以下のとおりです。 0x00000000 ┌─────────────────────────────────┐ │ ブロック 0 : FCB0 │ 0x00040000 ├─────────────────────────────────┤ │ ブロック 1 : FCB1 │ 0x00080000 ├─────────────────────────────────┤ │ ブロック 2 : DBBT0 │ 0x000C0000 ├─────────────────────────────────┤ │ ブロック 3 : DBBT1 │ 0x00100000 ├─────────────────────────────────┤ │ ブロック4-15:プライマリファームウェア │ 0x00400000 ├─────────────────────────────────┤ │ ブロック 16~31:セカンダリファームウェア│ 0x00800000 └─────────────────────────────────┘ FCB0を意図的に破損させるために2つの異なる方法を試しましたが、どちらの場合も挙動は同じでした(FCB1は一度も読み取られませんでした): ブロック0を完全に消去しました。 FCBの指紋を「NFCB」から「NFC@」に変更しました。 質問: FCB0が破損した場合にフォールバックメカニズムでFCB1を読み取るために、追加のFuse設定や特定の構成が必要ですか? サポートありがとうございます。 i.MX8ULP Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted 追記として、追加の観察事項と質問を述べたいと思います。 もしBoot ROMが特定のFCBを読み取れなかった場合、停止する前に同じFCBを一度だけ読み直すように設計されているのかもしれません。もしこの仮説が正しければ、「FlexSPI NAND検索カウント」ヒューズを増やすことで、起動ROMにさらに探索を強制することで問題が解決されるかもしれません。 i.MX 8ULPリファレンスマニュアルには明示的に詳述されていませんが、i.MX 91(互換性のあるSPI NANDブートアーキテクチャを共有していると思われる)のFusemapでは、検索カウントを次のように説明しています。 FlexSPI NAND検索カウント 00 - 2 01 - 2 10 - 4 11 - 8 この検索数の仕様は i.MX 8ULPでも同一であると考えてよいのでしょうか? どんなご意見でも大変ありがたく思います。 Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted こんにちは、リタさん。 迅速なご返信とサポート、ありがとうございます! 念のため確認すると、私たちが観察している問題は内部のBoot ROM実行フェーズのみで発生しており、これはBSPやユーザーソフトウェアが読み込まれたり実行されたりする前の段階です。このため、BSPのバージョンはこの特定の動作には影響しないはずです。 私の核心的な質問は、ブートROMの内部仕様に関するものです。FCB0が破損している場合、i.MX 8ULPブートROMは具体的にどのような条件下でFCB1の読み取りを試みるのでしょうか? また、前回のフォローアップで述べたように、このフォールバック動作は i.MX 91のように「FlexSPI NAND 検索 Count」ヒューズ設定に関係しているのでしょうか? この内部ロジックについて、Boot ROMのエンジニアリングチームにご相談いただけると大変ありがたいです。 お時間を割いていただき、またご協力いただき、ありがとうございました! よろしくお願いします、 ミゾ族 Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted こんにちは@DaisukeMizobuchiさん 使用しているBSPのバージョンは何ですか? 素敵な一日をお過ごしください よろしくお願いいたします。 リタ Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted こんにちは、リタさん。 このThreadについて、さっさと続けてお願いします。Boot ROMのフォールバック動作や検索 Countのヒューズについて、社内のエンジニアリングチームに確認する機会はありましたか? たとえまだ調査中であっても、最新情報をお知らせいただければ大変ありがたいです。 ありがとう、 ミゾ族
View full article
IAR Plugin Manager for S32DS3.5 I am trying to integrate IAR EWARM FS 8.50.10 into S32 Design Studio 3.5. According to the NXP integration guide, the recommended flow is to install the IAR Plugin Manager from the IAR Eclipse update site and then use the Plugin Manager to install the corresponding IAR Eclipse plugin. However, the latest IAR Plugin Manager available from the current update site requires Java 17, while S32DS 3.5 is running with Java 11.0.11. As a result, the Plugin Manager cannot be resolved/started in S32DS 3.5. The Error Log shows: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))" Could anyone confirm: Which IAR Plugin Manager version/build was validated with S32DS 3.5? Where can I download the older Java 11-compatible IAR Plugin Manager package/update site? For IAR EWARM FS 8.50.10, which IAR Eclipse plugin version/build should be used with S32DS 3.5? If anyone still has a working S32DS 3.5 + IAR 8.50.10 environment, could you please share the installed IAR Plugin Manager/plugin version numbers? Thanks! Re: IAR Plugin Manager for S32DS3.5 Hello @LeoYang-, I have sent you a private message. Best regards, Julián
View full article
i.MX 8ULP SPI 与非 启动:当 FCB0 损坏时,启动 ROM 不会回退到 FCB1。 NXP社区的各位好, 我正在使用 i.MX 8ULP,并从 SPI 与非 闪存(Winbond W25N04LW)启动。 我的理解是,如果 FCB0 损坏,启动 ROM 应该会自动回退到 FCB1。然而,当 FCB0 损坏时,系统却无法启动。具体来说,启动 ROM 似乎根本没有尝试读取 FCB1。 以下是我的“SPI 与非 启动参数”熔丝设置: FlexSPI 与非 搜索步长:00(64 页) FlexSPI 与非 搜索计数:00 (2) FlexSPI 与非 CS 间隔:00 (100ns) FlexSPI 与非列地址宽度:01 (13) 其他所有熔丝均保持默认值。 我使用协议分析仪监测了 SPI 通信。 上电后, i.MX 8ULP 发出页面数据读取 (13h) 请求,读取页面地址 0x000000 处的 FCB0。 由于 FCB0 已损坏,我预期启动 ROM 会读取地址为 0x000040 的 FCB1 (基于 64 页的搜索步长)。然而,它却直接尝试再次读取 FCB0,而没有尝试读取 FCB1。 作为参考,我的SPI 与非存储器映射如下: 0x00000000 ┌──────────────────────────────────┐ │ 区块 0:FCB0 │ 0x00040000 ├──────────────────────────────────┤ │ 区块 1:FCB1 │ 0x00080000 ├──────────────────────────────────┤ │ 模块 2:DBBT0 │ 0x000C0000 ├──────────────────────────────────┤ │ 模块 3:DBBT1 │ 0x00100000 ├──────────────────────────────────┤ │ 第 4–15 块:主固件 │ 0x00400000 ├──────────────────────────────────┤ │ 第 16–31 块:辅助固件 │ 0x00800000 └────────────────────────────────────┘ 我尝试了两种不同的方法来故意破坏 FCB0,但两种情况下行为都相同(FCB1 从未被读取): 已完全擦除第 0 块。 将 FCB 指纹从“NFCB”修改为“NFC@”。 问:当 FCB0 损坏时,是否需要任何额外的熔丝设置或特定配置才能启用回退机制以读取 FCB1? 感谢您的支持。 i.MX8ULP Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted 作为更新,我想补充一点后续观察和问题。 如果启动 ROM 读取某个 FCB 失败,它会不会设计成在停止之前重试读取该 FCB 一次?如果这个假设是正确的,增加“FlexSPI 与非 搜索计数”熔丝可能会通过强制启动 ROM 进行更远距离的搜索来解决问题。 虽然 i.MX 8ULP 参考手册中没有明确详细说明,但 i.MX 91 的熔丝图(我认为它采用兼容的 SPI 与非启动架构)对搜索计数的描述如下: FlexSPI 与非 搜索计数 00 - 2 01-2 10 - 4 11 - 8 是否可以假设 i.MX 8ULP 的搜索计数规范与此相同? 任何见解都将不胜感激。 Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted 嗨,丽塔, 感谢您的及时回复和支持! 需要澄清的是,我们观察到的问题完全发生在内部 启动 ROM 执行阶段,也就是在任何 电路板支持包。 或用户软件加载或执行之前。因此,电路板支持包。版本不应是造成这种特定行为的因素。 我的核心问题严格来说与内部启动 ROM 规范有关:当 FCB0 损坏时,i.MX 8ULP 启动 ROM 在什么情况下会尝试读取 FCB1? 另外,正如我在之前的后续问题中提到的,这种回退行为是否与“FlexSPI 与非 搜索计数”熔丝设置有关,类似于它在 i.MX 91 上的工作方式? 如果您能就此内部逻辑咨询一下启动 ROM 工程团队,我将不胜感激。 再次感谢您抽出时间提供帮助! 此致, 米佐 Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted 嗨@DaisukeMizobuchi , 你使用的是哪个版本的电路板支持包? 祝你今天过得愉快 顺祝商祺! Rita Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted 嗨,丽塔, 就此帖作个简单的后续补充。您有没有机会向内部工程团队核实一下启动 ROM 回退行为和搜索计数熔丝的相关情况? 即使仍在调查中,任何快速更新都将不胜感激。 谢谢, 米佐
View full article
i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted Hi NXP Community, I am working with the i.MX 8ULP and booting from an SPI NAND flash (Winbond W25N04LW). My understanding is that if FCB0 is corrupted, the Boot ROM should automatically fall back to FCB1. However, when FCB0 is corrupted, the system fails to boot. Specifically, it appears that the Boot ROM does not even attempt to read FCB1. Here are my "SPI NAND boot parameters" Fuse settings: FlexSPI NAND Search Stride : 00 (64 pages) FlexSPI NAND Search Count : 00 (2) FlexSPI NAND CS Interval : 00 (100ns) FlexSPI NAND Column Address Width : 01 (13) All other Fuses are left at their default values. I monitored the SPI communication using a protocol analyzer. Upon power-on, the i.MX 8ULP issues a Page Data Read (13h) to read FCB0 at Page Address 0x000000. Since FCB0 is corrupted, I expected the Boot ROM to read FCB1 at Page Address 0x000040 (based on the 64-page search stride). Instead, it simply attempts to read FCB0 again without trying FCB1. For context, my SPI NAND memory map is as follows: 0x00000000 ┌─────────────────────────────────┐ │ Block 0 : FCB0 │ 0x00040000 ├─────────────────────────────────┤ │ Block 1 : FCB1 │ 0x00080000 ├─────────────────────────────────┤ │ Block 2 : DBBT0 │ 0x000C0000 ├─────────────────────────────────┤ │ Block 3 : DBBT1 │ 0x00100000 ├─────────────────────────────────┤ │ Block 4–15 : Primary firmware │ 0x00400000 ├─────────────────────────────────┤ │ Block 16–31 : Secondary firmware│ 0x00800000 └─────────────────────────────────┘ I tried two different methods to intentionally corrupt FCB0, but the behavior was identical in both cases (FCB1 was never read): Erased Block 0 completely. Modified the FCB fingerprint from 'NFCB' to 'NFC@'. Question: Are there any additional Fuse settings or specific configurations required to enable the fallback mechanism to read FCB1 when FCB0 is corrupted? Thanks in advance for your support. i.MX8ULP Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted As an update, I would like to add a follow-up observation and question. Could it be that if the Boot ROM fails to read a given FCB, it is designed to retry reading that same FCB exactly once before stopping? If this hypothesis is correct, increasing the "FlexSPI NAND Search Count" fuse might resolve the issue by forcing the Boot ROM to search further. Although this is not explicitly detailed in the i.MX 8ULP Reference Manual, the Fusemap for the i.MX 91 (which I believe shares a compatible SPI NAND boot architecture) describes the Search Count as follows: FlexSPI NAND Search Count 00 - 2 01 - 2 10 - 4 11 - 8 Is it correct to assume that this search count specification is identical for the i.MX 8ULP? Any insights would be greatly appreciated. Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted Hi Rita, Thank you for your prompt reply and support! Just to clarify, the issue we are observing occurs purely during the internal Boot ROM execution phase, which is before any BSP or user software is loaded or executed. Because of this, the BSP version should not be a factor in this specific behavior. My core question is strictly about the internal Boot ROM specifications: under what exact conditions does the i.MX 8ULP Boot ROM attempt to read FCB1 when FCB0 is corrupted? Also, as I mentioned in my previous follow-up, could this fallback behavior be tied to the "FlexSPI NAND Search Count" fuse setting, similar to how it works on the i.MX 91? I would greatly appreciate it if you could consult with the Boot ROM engineering team regarding this internal logic. Thanks again for your time and assistance! Best regards, mizo Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted Hi @DaisukeMizobuchi , Which version BSP are you using? Wish you have a nice day Best Regards Rita Re: i.MX 8ULP SPI NAND Boot: Boot ROM does not fall back to FCB1 when FCB0 is corrupted Hi Rita, Just a gentle follow-up on this thread. Have you had a chance to check with the internal engineering team regarding the Boot ROM fallback behavior and the Search Count fuse? Even if it is still under investigation, any quick update would be greatly appreciated. Thanks, mizo
View full article
从样例中导入的工程报错 IDE版本: S32 Design Studio for S32 Platform Version: 3.6.1 Build id: 250327 RTD为:SW32ZE_RTD_R21-11_2.0.1_D2505_DesignStudio_updatesite.zip Re: 从样例中导入的工程报错 Hi,zzf Thank you for contacting us. Which example are you using? Have you used the update code button before building this project? BR Joey
View full article
适用于 S32DS3.5 的 IAR 插件管理器 我正在尝试将IAR EWARM FS 8.50.10集成到S32 Design Studio 3.5中。 根据 NXP 集成指南,推荐的流程是从 IAR Eclipse 更新站点安装IAR 插件管理器,然后使用插件管理器安装相应的 IAR Eclipse 插件。 然而,当前更新站点提供的最新 IAR 插件管理器需要Java 17 ,而 S32DS 3.5 运行的是Java 11.0.11 。因此,在 S32DS 3.5 中无法解析/启动插件管理器。错误日志显示: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))" 请问有人能确认一下吗? 哪个 IAR Plugin Manager 版本/构建版本已通过 S32DS 3.5 验证? 哪里可以下载旧版兼容 Java 11 的 IAR 插件管理器软件包/更新站点? 对于IAR EWARM FS 8.50.10 ,应该使用哪个 IAR Eclipse 插件版本/构建版本与 S32DS 3.5 配合使用? 如果还有人拥有可用的S32DS 3.5 + IAR 8.50.10环境,能否请您分享一下已安装的 IAR 插件管理器/插件版本号? 谢谢您! Re: IAR Plugin Manager for S32DS3.5 你好@LeoYang- , 我已向您发送私信。 此致, 朱利安
View full article
#ftm_pwm_S32K116 您好,尊敬的NXP同事: 我正在寻求关于ftm_pwm_s32k116项目的帮助,问题是无论我如何尝试更改代码或配置,MCU都无法在默认通道(FTM0-通道0,即)上输出PWM信号。PTD15)。 我的步骤如下: 1.从示例中导入新项目; 2.编译通过,我检查了引脚复用器和Flextimer配置,没有发现问题(实际上它是NXP的示例,我认为完全正确); 3.然后我把它刷入S32K116; 4.观察PTD15上的波形,没有发现任何问题,我尝试了将近两天; 我的项目压缩文件如下,谢谢。 Re: #ftm_pwm_S32K116 附上我的项目。 Re: #ftm_pwm_S32K116 嗨@Tracy_Lu 首先,我注意到您正在使用 Processor Expert,所以看来您使用的是较旧的软件版本。如果您开始使用 S32K1 设备进行开发,我们建议您使用最新的可用软件和工具,目前推荐使用 S32K1_S32M24X 实时驱动程序 AUTOSAR R21-11 版本 3.0.0。( S32K1 的实时驱动程序)以及适用于 S32 平台的 S32 设计工作室( S32 设计工作室 | NXP 半导体)。 但是,如果您想继续使用 S32K1 SDK,则最新的 SDK 版本已随 S32 Design Studio for S32 Platform 3.4 提供。 另外,请与我们联系您使用的是EVB电路板还是定制电路板? 如果您希望继续使用当前的软件配置,也请您分享您正在使用的确切 S32K1 SDK 版本。 BR,VaneB Re: #ftm_pwm_S32K116 您好,尊敬的NXP同事: 感谢您快速专业的回复。我根据示例项目 S32K116_Project_FTM 修改了代码(在 Gemini AI 的协助下),我想分享以下几点,以帮助像我一样的工程师解决编译和调试过程中遇到的问题: 1.我使用FTM功能来响应我的PMIC(TPS650366)的ESM(错误信号监控); 2.一开始我使用ftm_pwm_S32k116项目,但编译和调试都失败了,持续了大约两天。我在指定的引脚上看不到任何PWM输出。我确信我配置和调试都正确,而且是在Gemini AI的帮助下完成的; 3.然后我找到了另一个名为 S32K116_Project_FTM 的示例,我尝试编译它,没有出现错误。我得到了配置引脚的输出,即 PTD15(FTM0CH0)/16(FTM0CH1),虽然初始频率为 1Hz/5Hz,但我知道我离成功很近了; 4.实际上,我需要PWM频率在40KHz左右,所以我知道下一步是修改系统频率预分频器、MOD值、CnV(占空比),但我发现我无法更改MOD值(我更改了该值,但无法写入MCU的根目录),我反复尝试,搜索了所有可能对我有帮助的信息; 5.最后我发现,如果要更改 MOD 值,需要满足几个前提条件,例如关闭时钟、解除写保护……; 6.这是我编译后的代码,运行正常(在 PTD16 上输出约为 48KHz); int main(void) { /*! * 初始化: * ======================= */ WDOG_disable(); /* 禁用看门狗 */ SOSC_init_40MHz(); /* 初始化 40 MHz 晶振系统 */ RUN_mode_48MHz(); /* 初始化时钟:48 MHz 系统、核心和总线, 24 MHz 闪存。*/    FTM0_init(); /* 使用 8 MHz SIRCDIV1_CLK 初始化 FTM0 */   //FTM0_CH0_OC_init(); /* 初始化 FTM0 CH0,PTD15 */ FTM0_CH1_PWM_init(); /* 初始化 FTM0 CH1,PTD16 */ FTM0_CH6_IC_init(); /* 初始化 FTM0 CH6,PTE8 */ FTM1_Init(); FTM1_CH1_PWM_init(); PORT_init(); /* 配置端口 */ start_FTM0_counter(); /* 启动 FTM0 计数器 */   /*! * 无限: * ======================== */ 为了(;;)   { //FTM0_CH0_output_compare();/* 如果输出比较匹配:*/ /* 引脚切换(由硬件自动完成)*/ /* 清除标志 8 */ /* 重新加载计时器 */ //FTM0_CH6_input_capture(); /* 如果捕获到输入:清除标志,读取定时器 */   } } 7.导入代码如下(FTM0_init(),FTM0_CH1_PWM_init()): void FTM0_init(void) {/** * FTM0 时钟: * ================================================== */ PCC->PCCn[PCC_FTM0_INDEX] &= ~PCC_PCCn_CGC_MASK; /* 确保配置过程中禁用时钟 */ PCC->PCCn[PCC_FTM0_INDEX] |= PCC_PCCn_PCS(0b010) /* 时钟源=1,8 MHz SIRCDIV1_CLK */ | PCC_PCCn_CGC_MASK; /* 使能 FTM 寄存器时钟 */ /*! * FTM0 初始化: * =================================================== */ // 1. 第一步:确保FTM时钟彻底关闭(CLKS = 0),此时完全可配置状态 FTM0->SC = 0x00000000; // 2.第二步:解除写保护并开启FTM完整模式 volatile uint32_t dummy = FTM0->MODE; FTM0->模式|= FTM_MODE_WPDIS_MASK; /* 取消写保护 */ FTM0->模式|= FTM_MODE_FTMEN_MASK; /* 开启FTM完整模式 */ // 3.第三步:在时钟关闭的安全状态下,顺利把MOD和比较值写进去 FTM0->CNTIN = 0U; FTM0->MOD = 166 - 1; /* 8MHz / 166 ≈ 48.19 kHz */ // 4.第四步:通道配置1 (PTD16) 为边沿着对齐PWM模式 FTM0->CONTROLS[1].CnSC = FTM_CnSC_MSB_MASK | FTM_CnSC_ELSB_MASK; FTM0->控制[1].CnV = 83; /* 50% 占空比 (83 < 165) */ // 5.第五步:其余和组合模式清零 FTM0->COMBINE = 0x00000000; FTM0->POL = 0x00000000; // 6.最后一步:所有参数已经安稳写入后,才真正开启通道输出和时钟源! FTM0->SC = FTM_SC_PWMEN0_MASK | FTM_SC_PWMEN1_MASK | FTM_SC_PS(0) /* PS = 0 (不分频) */ | FTM_SC_CLKS(1); /* CLKS = 1 (最后启动成分) */ } void FTM0_CH1_PWM_init(void) { /** * FTM0,PWM模式下的通道1: * ================================================== */ FTM0->CONTROLS[1].CnSC = FTM_CnSC_MSB_MASK |FTM_CnSC_ELSB_MASK;  /* FTM0 通道 1:边沿对齐 PWM,低真实脉冲 */ /* CHIE(通道中断赋值)= 0(默认值)*/ /* MSB:MSA(通道模式选择)=0b10,边沿对齐 PWM */ /* ELSB:ELSA(通道边缘/电平选择)=0b10,低电平为真 */   FTM0->CONTROLS[1].CnV = 46875; /* FTM0 通道 1 比较值(~75% 占空比) */ }
View full article
#ftm_pwm_S32K116  Hi,Dear NXP colleague: I'm looking for help about the project of ftm_pwm_s32k116,the fact is that no matter how I try to change the code or configuration.the MCU can't output PWM signal on default channel(FTM0-channel 0,i.e. PTD15). here is my step : 1.import the new project from example; 2.compile it and all PASS,I check the pin mux and flextimer configuration and find no problem(actually it's from NXP example,I think it's totally right); 3.then I flash it  into S32K116; 4.observe the waveform on PTD15 and find nothing,I tried for almost 2days; the zip file of my project is as below,thanks. Re: #ftm_pwm_S32K116 attach my project  Re: #ftm_pwm_S32K116 Hi @Tracy_Lu  First, I noticed that you are using Processor Expert, so it seems that you are working with an older software version. If you are starting your development with S32K1 devices, we would recommend using the latest available software and tools, currently the S32K1_S32M24X Real-Time Drivers AUTOSAR R21-11 Version 3.0.0 (Real-Time Drivers for S32K1) together with S32 Design Studio for S32 Platform (S32 Design Studio | NXP Semiconductors). However, if you would like to continue using the S32K1 SDK, the latest SDK version was provided with S32 Design Studio for S32 Platform 3.4. Additionally, could you please let us know whether you are using an EVB or a custom board? If you would like to remain with your current software setup, it would also be helpful if you could share the exact S32K1 SDK version you are using. BR, VaneB Re: #ftm_pwm_S32K116 Hi,Dear NXP colleague:  thanks  for  the quick and professional reply.I change to another project S32K116_Project_FTM from example and modify the code(with the assistance from gemini AI),I want to share these points to help the engineer like me to solve the problem during compile and debug: 1.I use the FTM function to respond the ESM(error signal monitoring)of my PMIC(TPS650366); 2.at first I use ftm_pwm_S32k116 project and failed to compile and debug,for around 2 days.I can't see any output PWM at the assigned pin.And I'm sure I make the right configuration and debug,with the assistance from Gemini AI; 3.then I find another example named S32K116_Project_FTM,I tried and compile it with no error.and I get the output of the configured pin which is PTD15(FTM0CH0)/16(FTM0CH1),though the initial frequency is 1Hz/5Hz,I know I'm close to the finish line; 4.actually,I need the pwm frequency around 40KHz,so I know the next step is to modify the system frequency prescaler,MOD value,CnV(duty cycle),but I find that I can't change the MOD value(I change the value but I can't write into the root place of MCU),I tried and tried,searching all the info which can help with me; 5.finally I find that if you want to change MOD value,you should satisfy several pre-condition,e.g.you should close the clock,release the write protection...; 6.here is my code after compile and operates normally(output around 48KHz at PTD16); int main(void) { /*! * Initialization: * ======================= */ WDOG_disable(); /* Disable watchdog */ SOSC_init_40MHz(); /* Initialize system oscillator for 40 MHz xtal */ RUN_mode_48MHz(); /* Init clocks: 48 MHz sys, core and bus,                   24 MHz flash. */      FTM0_init();           /* Init FTM0 using 8 MHz SIRCDIV1_CLK */    //FTM0_CH0_OC_init();    /* Init FTM0 CH0, PTD15 */   FTM0_CH1_PWM_init();   /* Init FTM0 CH1, PTD16 */   FTM0_CH6_IC_init();    /* Init FTM0 CH6, PTE8  */   FTM1_Init();   FTM1_CH1_PWM_init();   PORT_init();           /* Configure ports */   start_FTM0_counter();  /* Start FTM0 counter */   /*! * Infinite for: * ======================== */   for(;;)   { //FTM0_CH0_output_compare();/* If output compare match: */   /* Pin toggles (automatically by hardware) */   /* Clear flag 8 */   /* Reload timer */ //FTM0_CH6_input_capture(); /* If input captured: clear flag, read timer */   } } 7.the import code is as below(FTM0_init(),FTM0_CH1_PWM_init())  : void FTM0_init(void) {/** * FTM0 Clocking: * ================================================== */ PCC->PCCn[PCC_FTM0_INDEX] &= ~PCC_PCCn_CGC_MASK; /* Ensure clk disabled for config */ PCC->PCCn[PCC_FTM0_INDEX] |= PCC_PCCn_PCS(0b010) /* Clock src=1, 8 MHz SIRCDIV1_CLK */ | PCC_PCCn_CGC_MASK; /* Enable clock for FTM regs */ /*! * FTM0 Initialization: * =================================================== */ // 1. 第一步:确保 FTM 时钟彻底关闭(CLKS = 0),此时处于完全可配置状态 FTM0->SC = 0x00000000; // 2. 第二步:解除写保护并开启 FTM 完整模式 volatile uint32_t dummy = FTM0->MODE; FTM0->MODE |= FTM_MODE_WPDIS_MASK; /* 禁用写保护 */ FTM0->MODE |= FTM_MODE_FTMEN_MASK; /* 开启 FTM 完整模式 */ // 3. 第三步:在时钟关闭的安全状态下,顺利把 MOD 和比较值写进去 FTM0->CNTIN = 0U; FTM0->MOD = 166 - 1; /* 8MHz / 166 ≈ 48.19 kHz */ // 4. 第四步:配置通道 1 (PTD16) 为边沿对齐 PWM 模式 FTM0->CONTROLS[1].CnSC = FTM_CnSC_MSB_MASK | FTM_CnSC_ELSB_MASK; FTM0->CONTROLS[1].CnV = 83; /* 50% 占空比 (83 < 165) */ // 5. 第五步:极性和组合模式清零 FTM0->COMBINE = 0x00000000; FTM0->POL = 0x00000000; // 6. 最后一步:所有参数已经安稳写入后,才真正开启通道输出和时钟源! FTM0->SC = FTM_SC_PWMEN0_MASK | FTM_SC_PWMEN1_MASK | FTM_SC_PS(0) /* PS = 0 (不分频) */ | FTM_SC_CLKS(1); /* CLKS = 1 (最后启动计数器) */ } void FTM0_CH1_PWM_init(void) { /** * FTM0, Channel 1 in PWM Mode: * ================================================== */ FTM0->CONTROLS[1].CnSC = FTM_CnSC_MSB_MASK |FTM_CnSC_ELSB_MASK;  /* FTM0 ch1: edge-aligned PWM, low true pulses */ /* CHIE (Chan Interrupt Ena) = 0 (default) */ /* MSB:MSA (chan Mode Select)=0b10, Edge Align PWM */ /* ELSB:ELSA (chan Edge/Level Select)=0b10, low true */   FTM0->CONTROLS[1].CnV =  46875; /* FTM0 ch1 compare value (~75% duty cycle) */ }
View full article
S32DS3.5用のIARプラグインマネージャー 私は IAR EWARM FS 8.50.10 を S32 Design Studio 3.5に統合しようとしています。 NXPの統合ガイドによると、推奨される流れはIAR Eclipseのアップデートサイトから IARプラグインマネージャー をインストールし、その後プラグインマネージャーを使って対応するIAR Eclipseプラグインをインストールすることです。 ただし、最新のアップデートサイトから入手可能なIARプラグインマネージャーは Java 17を必要とし、S32DS 3.5は Java 11.0.11で動作しています。その結果、S32DS 3.5ではプラグインマネージャーを解決または起動できません。エラーログには以下が表示されます。 Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))" 誰か確認できますか: どのIARプラグインマネージャーのバージョン/ビルドがS32DS 3.5で検証されましたか? 古いJava 11対応のIARプラグインマネージャーパッケージ/アップデートサイトはどこでダウンロードできますか? IAR EWARM FS 8.50.10の場合、S32DS 3.5 で使用する IAR Eclipse プラグインのバージョン/ビルドはどれですか? もしまだ動作する S32DS 3.5 + IAR 8.50.10 環境を持っている方がいれば、インストールされているIARプラグインマネージャーやプラグインのバージョン番号を共有していただけませんか? よろしくお願いします! Re: IAR Plugin Manager for S32DS3.5 こんにちは、 @LeoYang- さん、 プライベートメッセージを送りました。 よろしくお願いします、 ジュリアン
View full article
从样例中导入的工程报错 IDE版本: S32 Design Studio for S32 Platform 版本:3.6.1 版本 ID:250327 RTD为:SW32ZE_RTD_R21-11_2.0.1_D2505_DesignStudio_updatesite.zip Re: 从样例中导入的工程报错 嗨,zzf 感谢您与我们联系。 你用的是哪个例子?在构建此项目之前,您是否使用过更新代码按钮? BR 乔伊
View full article
例から入った工程报错 IDE バージョン: S32 Design Studio for S32 Platform バージョン: 3.6.1 ビルドID: 250327 RTD は:SW32ZE_RTD_R21-11_2.0.1_D2505_DesignStudio_updatesite.zip Re: 从样例中导入的工程报错 こんにちは、zzf お問い合わせいただきありがとうございます。 どの例を使っていますか?このプロジェクトをビルディングする前にアップデートコードボタンを使ったことはありますか? BR ジョーイ
View full article
i.MX 8M クアッドEvk I2Cインターフェース 私は、I2Cインターフェースを使って、AM/FMチューナーモジュールをNXP i.MX 8M Quad EVKとインターフェースし、チューナーの設定と制御を行う必要があります。 このハードウェアインターフェースの確立方法を教えていただけますか? さらに、i.MX 8M Quad EVKはチューナーモジュールからのデジタルオーディオ出力を受信するために使えるI2S信号を露出していますか?もしそうなら、関連するコネクタの詳細とピンのマッピングを教えていただけますか? Re: i.MX 8M Quad Evk I2C interface こんにちは、 はい、MCIMX8M-EVKにはプロセッサのI2C2にアクセスするためのJ801コネクタがあります。 I2Sインターフェースへのアクセスはアダプターが必要になるため、少し難しいでしょう。これらの信号はM.2 KEY-E J1401コネクタまたはJ1801コネクタにコネクテッドされています。 次のデザインファイルで確認してください: i.MX 8M評価キット(EVKB)のデザインファイル よろしくお願いいたします。
View full article
i.MX 8M 四通道 Evk I2C 接口 我需要使用 I2C 接口将 AM/FM 调谐器模块与 NXP i.MX 8M Quad EVK 连接,以实现调谐器的配置和控制。 请问您能否指导我如何建立这个硬件接口? 此外,i.MX 8M Quad EVK 是否提供可用于接收来自调谐器模块的数字音频输出的 I2S 信号?如果可以,能否请您提供相关的连接器详细信息和引脚映射? Re: i.MX 8M Quad Evk I2C interface 你好, 是的,MCIMX8M-EVK 具有 J801 连接器,可访问处理器的 I2C2。 由于需要适配器,访问 I2S 接口会稍微困难一些。这些信号连接到 M.2 KEY-E J1401 连接器或 J1801 连接器。 请在下一个设计文件中查看: i.MX 8M 评估套件 (EVKB) 的设计文件 顺祝商祺!
View full article
S32K Examples S32K1xx S32K144 Example S32K144 CMP Round-robin S32DS2.0  Example S32K144 Verify Backdoor Access Key S32DS1.3  Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13  Example S32K144 PDB ADC trigger DMA ISR S32DS  Example S32K144 Flash RW simple S32DS  Example S32K144 DMA memory copy test S32DS  Example S32K144 EEEPROM usage Example S32K144 EEEPROM usage - No SDK  Example S32K144 RTC VLPS  Example S32K144 WDOG RCM interrupt  Example S32K144 SRAM ECC Injection  Example S32K144 RAM Retention S32DS.R1 Example S32K144 I2C Master MPL3115A2 S32DSR1_v3  Example S32K144 FlexCAN RXFIFO DMA S32DS.ARM.2018.R1  Example S32K144_printf_implementation - S32DS_1.0  Example S32k144 UART printf/scanf under FreeRTOS - S32DS Example S32K144 SDK Function call on configurable period using LPIT timer.  Example S32K144 .noinit section usage Example S32K144 PDB ADC DMA S32DS.ARM.2018.R1   Example S32K144 RAM selftest simple S32DS 2018.R1  Example S32K144 Position Independent Code  Example S32K144 FlexCAN Pretended Networking STOP mode test S32DS.ARM.2.2  Example S32K144 LPIT DMA LPSPI  Example S32K144 FlexCAN TX/RX/Error ISR test S32DS2.2  Example S32K144 FlexIO Idle Detection S32DS2.2 S32K142 Example_S32K142_LMEN_Cache_v1_0_S32DS3.6_RTD300  Lauterbach_Script_For_MDM_AP_Mass_erase_S32K142  S32K146 Example S32K146 Set_whole_FlexRAM-as_RAM S32DS.ARM.2.2 S32K148 Example S32K148 PDB0-PDB1 ring S32DS3.4 RTM4.0.3  Example S32K148 PDB0-PDB1 ring DMA S32DS3.4 RTM4.0.3  Example S32K148 GPIO Interrupt   S32K116 Example S32K116 WDOG Fast Test  Example S32K116 LPUART LIN Slave TXRX ISR S32DS.ARM.2.2  Example S32K116 FlexCAN PN STOP S32DS.ARM.2.2 Example S32K116 FlexCAN VLPR test S32DS.ARM.2.2 S32K118 Example S32K118-SRAM-keep_data_over_SW_reset v0_1 S32DS.ARM.2.2 S32K3xx S32K312 Example S32K312 ADC_IP Continuous Scan DMA S32DS36 RTD600    S32K344 Example S32K344 PIT BTCU ADC DMA DS3.4 RTD100   Example S32K344 FlexCAN_Ip TX/RX/EnhanceRXFIFO test S32DS3.4 RTD200     Example_C40_Ip_ECC_Fault_Skip_S32K312_DS34_RTD2211_v1     Example Siul2_Port_Ip_Example_S32K344_ITCM_DTCM S32DS3.4 RTD300   Example S32K344 LPUART RX/TX ISR FreeRTOS S32DS36 RTD600    Example_S32K344_MCAL_MCU_ClockMonitor_v1_0_S32DS36_RTD600    Example_S32K314_DTCM1_Backdoor_RTD201_DS34_v3    Example_Reg_Prot_Flash_Controller_S32K344   Example_S32K344_EIM_ERM_DTCM_SRAM_Baremetal_v3_0_S32DS36    Example S32K344 PIT SWtrig ADC ANAMUX S32DS 3.6.0 RTD 6.0.0   Example S32K344 EMAC lwIP FreeRTOS miniEVB S32DS 3.6.1 RTD 6.0.0   Example S32K344 EMAC lwIP FreeRTOS MRCANHUB S32DS 3.6.1 RTD600   Example_S32K344_BIST_eMCEM_SPD106_v2_0_S32DS365_RTD700  Example S32K344EVB_T172 UART_ETH_Gateway HLD S32DS368 RTD701   Example_S32K344_CMU_FM_POR_WDG_v1_0_S32DS369_RTD701    Example_S32K344_FLS_Integrity_Margin_Check_v1_0_S32DS36_RTD701    Example S32K344 LPSPI LCD-PAR-S035 FRDM S32DS 3.6.6 RTD 7.0.1   Example FRDM-A-S32K344 FlexCAN TX_RX FreeRTOS S32DS36 RTD600    Example_S32K344_INFLS_ECC_EDC_eMCEM_SPD106_v1_0_S32DS365_RTD700    Example S32K344 EMAC lwIP FreeRTOS S32K3-T-BOX S32DS 3.6.6 RTD7.0.1   Demo EthernetAnalyzer FRDM-A-S32K344 RTD 7.0.1   Example FRDM-A-S32K344 PIT ADC BTCU_ControlMode FIFO DMA HLD S32DS35 RTD300    Example S32K344EVB_T172 LPUART_EMAC_Gateway IP S32DS368 RTD701    S32K358   S32K358 Multicore Start CM7_2 from CM7_0    Example S32K358 FlexCAN TXRX ISR S32DS35 RTD400/500   Example S32K358 GMAC 100M lwIP FreeRTOS S32DS 3.6.1 RTD600   Example S32K358 GMAC 1G lwIP FreeRTOS S32DS 3.6.1 RTD600   Example S32K358 GMAC lwIP FreeRTOS RDBESS S32DS 3.6.1 RTD600   Example_S32K358_XRDC_SEMA42_Multicore_v1_0_S32DS369_RTD701    S32K388 Example S32K388 GMAC0 lwIP FreeRTOS S32DS 3.6.1 RTD600   S32K389 Example S32K389 GMAC0 lwIP FreeRTOS S32DS 3.6.1 RTD 6.0.0   Example S32K389 GMAC1 SABRE lwIP FreeRTOS S32DS 3.6.1 RTD600  
View full article
S32K 示例 S32K1xx S32K144 示例 S32K144 CMP 轮询 S32DS2.0 示例 S32K144 验证后门访问密钥 S32DS1.3 示例 S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13 示例 S32K144 PDB ADC 触发 DMA ISR S32DS 示例 S32K144 Flash RW simple S32DS 示例 S32K144 DMA 内存复制测试 S32DS S32K144 EEEPROM 使用示例 示例 S32K144 EEEPROM 使用 - 无 SDK 示例 S32K144 RTC VLPS 示例 S32K144 WDOG RCM 中断 示例 S32K144 SRAM ECC 注入  S32K144 RAM 保留示例 S32DS.R1 示例 S32K144 I2C主设备 MPL3115A2 S32DSR1_v3 示例S32K144 FlexCAN RXFIFO DMA S32DS.ARM.2018.R1  示例 S32K144_printf_implementation - S32DS_1.0 示例 S32K144 在 FreeRTOS 下使用 UART printf/scanf - S32DS 示例 使用 LPIT 定时器实现可配置周期函数调用的 S32K144 SDK 示例 S32K144 .noinit章节用法 示例 S32K144 PDB ADC DMA S32DS.ARM.2018.R1 示例 S32K144 RAM 自检简单 S32DS 2018.R1 示例 S32K144 位置无关代码  示例 S32K144 FlexCAN 虚拟网络停止模式测试 S32DS.ARM.2.2 示例 S32K144 LPIT DMA LPSPI 示例 S32K144 FlexCAN TX/RX/Error ISR 测试 S32DS2.2 示例 S32K144 FlexIO 空闲检测 S32DS2.2 S32K146 示例 S32K146 Set_whole_FlexRAM-as_RAM S32DS.ARM.2.2 S32K148 示例 S32K148 PDB0-PDB1 环 S32DS3.4 RTM4.0.3 示例 S32K148 PDB0-PDB1 环 DMA S32DS3.4 RTM4.0.3 示例 S32K148 GPIO 中断 S32K116 示例 S32K116 WDOG 快速测试 示例 S32K116 LPUART LIN 从机 TXRX ISR S32DS.ARM.2.2 示例 S32K116 FlexCAN PN 停止 S32DS.ARM.2.2 示例 S32K116 FlexCAN VLPR 测试 S32DS.ARM.2.2 S32K118 示例 S32K118-SRAM-keep_data_over_SW_reset v0_1 S32DS.ARM.2.2 S32K3xx S32K344 示例 S32K344 PIT BTCU ADC DMA DS3.4 RTD100   示例 S32K344 FlexCAN_Ip TX/RX/EnhanceRXFIFO 测试 S32DS3.4 RTD200   示例 Siul2_Port_Ip_Example_S32K344_ITCM_DTCM S32DS3.4RTD300   示例 S32K358 FlexCAN TXRX ISR S32DS35 RTD400/500    
View full article
S32Kの例 S32K1xx S32K144 例:S32K144 CMPラウンド・ロビンS32DS2.0  例:S32K144バックドア・アクセス・キー検証S32DS1.3  例:S32K144 FlexCAN0 RXFIFO DMA非SDK S32DS13  例:S32K144 PDB ADCトリガDMA ISR S32DS  例:S32K144 Flash RWシンプルS32DS  例:S32K144 DMAメモリ・コピー・テストS32DS  例:S32K144 EEEPROMの使用方法 例:S32K144 EEEPROMの使用方法 - 非SDK  例:S32K144 RTC VLPS  例:S32K144 WDOG RCM割り込み  例:S32K144 SRAM ECC注入  例 S32K144 RAM 保持 S32DS.R1 例:S32K144 I2CマスタMPL3115A2 S32DSR1_v3  例:S32K144 FlexCAN RXFIFO DMA S32DS.ARM.2018.R1  例:S32K144_printf_implementation - S32DS_1.0  例:FreeRTOS環境でのS32k144 UART printf/scanf - S32DS 例:S32K144 LPITタイマを使用した構成可能期間に対するSDK関数の呼び出し  例:S32K144 .noinitセクションの使用方法 例:S32K144 PDB ADC DMA S32DS.ARM.2018.R1   例:S32K144 RAMセルフテスト・シンプルS32DS 2018.R1  例:S32K144ポジショニング独立コード 例:S32K144 FlexCAN疑似ネットワーキングSTOPモードのテストS32DS.ARM.2.2  例:S32K144 LPIT DMA LPSPI  例:S32K144 FlexCAN TX/RX/エラーISRテストS32DS2.2  例:S32K144 FlexIOアイドル検出S32DS2.2 S32K146 S32K146 Set_whole_FlexRAM-as_RAM S32DS.ARM.2.2の例 S32K148 例:S32K148 PDB0-PDB1リングS32DS3.4 RTM4.0.3  例:S32K148 PDB0-PDB1 ring DMA S32DS3.4 RTM4.0.3  例:S32K148 GPIO割り込み  S32K116 例:S32K116 WDOG高速テスト  例:S32K116 LPUART LINスレーブTXRX ISR S32DS.ARM.2.2  例 S32K116 FlexCAN PN STOP S32DS.ARM.2.2 例:S32K116 FlexCAN VLPRテストS32DS.ARM.2.2 S32K118 例 S32K118-SRAM-keep_data_over_SW_reset v0_1 S32DS.ARM.2.2 S32K3XXシリーズ S32K344 例:S32K344 PIT BTCU ADC DMA DS3.4 RTD100   例:S32K344 FlexCAN_Ip TX/RX/EnhanceRXFIFOテストS32DS3.4 RTD200     例Siul2_Port_Ip_Example_S32K344_ITCM_DTCM S32DS3.4RTD300   例:S32K358 FlexCAN TXRX ISR S32DS35 RTD400/500     
View full article
MCX947 如何调试 Trustzone 项目 你好, 我一直在想办法调试修改后的 SDK 信任区域示例。但是我无法调试。它卡在了安全模式下,无法在非安全模式下调试。我原以为它会像从主核心切换到辅助核心一样,从安全核心切换到非安全核心。我读过一份旧的说明文档,其中建议擦除闪存等等。这并没有帮助。 核心与内存 开发板 Re: MCX947 How to debug trustzone projects 你好@embeddedguru 要调试 TrustZone 项目,我建议首先参考 SDK 中的 trustzone_helloworld 演示。 您可以参考MCUXpresso SDK 文档中的“运行 TrustZone 示例应用程序”部分,了解详细步骤。 谢谢! 爱丽丝
View full article
S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi NXP Team, I'm working with the S32K3-T-BOX (S32K344, schematic SCH-50735 Rev C) and trying to get Ethernet working with the S32K344 lwIP example Example_S32K344_EMAC_lwIP_Baremetal_S32K344_v1_0_S32DS36_RTD700. What I did Moved the project from the S32K3X4EVB-T172 setup to the T-Box: package S32K344_172HDQFP, 40 MHz external crystal, RMII. Re-routed the EMAC pins to match the T-Box schematic: TXD0 PTC2, TXD1 PTD7, TX_EN PTD12, TX_CLK/REF_CLK PTD11 (input), RXD0 PTC0, RXD1 PTC1, RX_DV PTC17, RX_ER PTC14. The project builds with 0 errors. I flashed it with the S32 Debug Probe on the S32K344 header. The firmware runs through main() → device_init() → Eth_43_GMAC_Init() and stays in the main loop until the example's test timeout. Problem The RJ45 LINK/activity LEDs never turn on, and Windows shows the adapter as "Disconnected". The same PC port and cable link normally with other devices. Board checks Power LEDs (PF5020 rails) are on. J51, J53 and J55 are on 1-2. S1 is OFF/OFF (boot from SJA1110 flash). U36 (SJA1110 status LED) does not blink green, so I suspect the SJA1110B has no firmware or configuration. Questions The example's description.txt lists only the S32K3X4EVB-T172. Is it intended to work on the S32K3-T-BOX, or only on the EVB? Does the SJA1110B need its own firmware or configuration (for example S32K3_T_BOX_LWIP_for_SJA1110) before the RJ45 link comes up? If so, what is the recommended procedure and debugger for the SJA1110 debug header (J57)? Is a prebuilt image available? Is any SJA1110B-side setting needed so the RMII link to the S32K344 EMAC works (RMII mode, 50 MHz REF_CLK direction)? Thanks! Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Please find the answers to your questions below. 1. The example is intended for the S32K3X4EVB-T172 and will not run on the S32K3-T-BOX without board-specific modifications. Please refer to slide 15 of the https://www.nxp.com/webapp/Download?colCode=TP-S32K3-T-BOX-LWIP-GUIDE  In particular: The S32K3-T-BOX uses a 40 MHz external crystal, while the EVB uses a 16 MHz crystal. The clock configuration must therefore be updated accordingly. The RMII reference clock for the S32K344 EMAC is provided by the SJA1110. A short delay should be added before the S32K344 clock initialization to allow the SJA1110 to start and provide the RMII reference clock. The external PHY initialization in device_init() is not required because the Ethernet PHY and switch initialization is handled by the SJA1110 firmware. 2. Yes, the SJA1110B requires its own firmware and switch configuration. Without running SJA1110 firmware, the RJ45 port and the RMII connection to the S32K344 will not be initialized. I have prepared examples for several SJA1110-based boards, including the S32K3-T-BOX. Please refer to Ethernet Switch SJA1110 Examples. The examples initialize and test the relevant ports and provide LED indication. A prebuilt flash_image.bin is included, so rebuilding the project is not required. Due to distribution restrictions, the complete SJA1110 example projects cannot be attached directly to the Community article. The example may be provided upon request through NXP Technical Support and may require an NDA. Please submit a support case through NXP Technical Support and reference the required S32K3-T-BOX SJA1110 example. 3. Connect a debugger that supports the SJA1110 device to the SJA1110 debug header J57 and program the provided flash image. I use either a PEmicro Multilink debugger or Lauterbach TRACE32. A prebuilt image is available as described in answer 2. 4. Yes. The SJA1110 firmware must configure the switch port connected to the S32K344 for RMII operation and provide the 50 MHz RMII reference clock to the S32K344 EMAC. This is handled by the S32K3-T-BOX-specific SJA1110 example. The inactive U36 LED is therefore a strong indication that the SJA1110 firmware is not currently running or that the device did not boot correctly. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, Thank you for the detailed answers. They confirmed the cause for us. Our status: The SJA1110 is powered (jumpers J51, J53, J55 on 1-2, PF5020 rails on) and S1 is OFF/OFF, but U36 stays dark. We built the public S32K3_T_BOX_LWIP_for_SJA1110 project to app_flash.elf. On the S32K344 side we have applied your three points: the 40 MHz clock configuration, a delay before the clock initialization, and removal of the PHY initialization from device_init(). Two questions: The article "Example SJA1110 FreeRTOS lwIP S32K3-T-BOX" only attaches Example_Availability.txt and no flash_image.bin. Could you share the prebuilt image directly, or tell us which support case to open (and whether an NDA is needed)? In the meantime, is the public S32K3_T_BOX_LWIP_for_SJA1110 project suitable for the T-BOX? Does its switch configuration forward frames between the RJ45 port (P1) and the S32K344 RMII port (P2)? We'd also like to confirm that a PEmicro Multilink is the right probe for J57. Best regards, Divya Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Your DIP switches are inline with my board. Please, check signal level of DEVICE_CFG_N connected to PTA13. If switch accepts the configuration, DEVICE_CFG_N should be low. ad 1. Yes, due to distribution restrictions, the complete SJA1110 example projects cannot be attached directly to the Community article. The example may be provided upon request through NXP Technical Support and may require an NDA. Please submit a support case through NXP Technical Support and reference the required S32K3-T-BOX SJA1110 example.  The main reason is that Automotive Ethernet belongs to export policy control and additional approvals might be required. ad 2. Yes, S32K3_T_BOX_LWIP_for_SJA1110 project is dedicated for the T-BOX. Yes, L2 Forwarding table has default settings - forward to all ports except to source port. Yes, I used PE micro multilink FX. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, Thank you for the clarification. I am working with the Example_S32K344_EMAC_lwIP_Baremetal_S32K344_v1_0_S32DS36_RTD700 example and have modified the EMAC pin configuration to match the S32K3-T-BOX hardware. Could you please confirm whether the pin configuration shown in the attached S32DS ConfigTools screenshot is correct for the T-Box, or if any changes are required? Best regards Divya Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Your pins appear to be correct. MDIO and MDC are not required. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, We have successfully built the SJA1110 lwIP example, but we need clarification on a few points. 1. SJA1110 .mex file fails to open We imported and built the S32K3_T_BOX_LWIP_for_SJA1110 example using S32 Design Studio 3.4.3 and RTD 2.0.0. The project builds successfully with 0 errors, but opening sja1110_t_box.mex produces the following error: Processor SJA1110, s32sdk_sja1110_rtm_100 version is not supported by current version of the tool. Could you please confirm which SJA1110 SDK or Configuration Tools package is required to open this .mex file? Is there a compatible package for S32DS 3.4.3, or do we need to use a different S32DS version? 2. Which firmware image should be programmed onto the SJA1110? After building the S32K3_T_BOX_LWIP_for_SJA1110 example, we obtained the following files: app_flash.elf sja1110_t_box.elf flash_image.bin flash_image_single_bank.bin sja1110_t_box.bin Could you please confirm which file, if any, should be programmed onto the SJA1110 on the T-Box board? Can we use a prebuilt SJA1110 firmware image directly without opening or modifying the .mex file? If so, could you provide the correct image and the recommended programming procedure using a PEmicro Multilink FX debugger through J57? 3. Debugger initialization script for the SJA1110 example We would also like to clarify the debugger configuration for this example. Should we use the following initialization script? ${S32DS_INITIALIZATION_SCRIPTS_DIR}/s32k3xx/s32k3xx_generic_bareboard.py Or is a different initialization script or debugger configuration required for the SJA1110? Please clarify the recommended procedure for programming and debugging the relevant target. 4. TCP/IP middleware is missing from the MCAL configuration For the Example_S32K344_EMAC_lwIP_Baremetal_S32K344_v1_0_S32DS36_RTD700 example, we opened lwip_baremetal_s32k344.mex but could not find the Middleware TCP/IP Stack component in the MCAL configuration tools. Is the TCP/IP stack expected to be configured through the MCAL Configuration Tools, or is lwIP integrated and configured separately at the application level? If additional software or configuration packages are required, could you please specify which ones and how to install them? 5. Recommended procedure for Ethernet bring-up on the T-Box Our T-Box RJ45 link LED remains off. Could you please confirm the recommended sequence for initializing the SJA1110 switch, establishing the RMII connection with the S32K344, and bringing up Ethernet using the T-Box lwIP example? We would appreciate any relevant documentation, compatible software packages, prebuilt firmware images, or example projects that could help us complete this setup. Thank you for your support. Best regards, Divya Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Please find my answers below. 1. SJA1110 .mex file fails to open The sja1110_t_box.mex file was created with S32 SDK for SJA1110 RTM 1.0.0. Therefore, the corresponding SJA1110 development package and SDK integration are required to open and modify it. However, the SJA1110 SDK is now considered a legacy software solution and is no longer available to new customers. Current software development for the SJA1110 is based on the Real-Time Drivers ecosystem. For new projects, the recommended approach is therefore to use the SJA11xx RTD and Ethernet Switch (ETH_SWITCH) driver packages rather than the legacy SDK. Unlike the legacy SDK, which was delivered as a more integrated installation, the RTD software ecosystem is modular. The base RTD, Ethernet PHY and Ethernet Switch drivers, and optional middleware such as FreeRTOS and the TCP/IP stack are provided as separate packages with defined version dependencies. The packages used by my current SJA1110 examples, including the recommended installation order, are listed in the following thread: SJA1110 SDK and RTD package information 2. Which firmware image should be programmed onto the SJA1110? The appropriate file depends on the programming tool: For PEmicro, use app_flash.elf. For Lauterbach TRACE32, use flash_image.bin. Therefore, with a PEmicro Multilink FX connected to the SJA1110 debug header J57, use app_flash.elf.  3. Debugger initialization script for the SJA1110 example Do not use ${S32DS_INITIALIZATION_SCRIPTS_DIR}/s32k3xx/s32k3xx_generic_bareboard.py This initialization script is intended for S32K3 devices, not for the SJA1110. For PEmicro, use the SJA1110-specific debug configuration supplied with the SJA1110 project and program app_flash.elf. The required SJA1110 device support is provided by the corresponding SJA1110 development package or SDK integration. 4. TCP/IP middleware is missing from the MCAL configuration This is expected if only the S32K3 RTD package is installed. The TCP/IP stack is separate middleware and is not part of the base MCAL or RTD installation. For S32K3 RTD 7.0.0, based on the available release information, install these matching packages: SW32K3_FreeRTOS_11.1.0_7.0.0_CD1_D2510_DesignStudio_updatesite.zip SW32K3_TCPIP_STACK_4.0.0_D2512_DesignStudio_updatesite.zip FreeRTOS is a required dependency of the TCP/IP Stack package, including for installation and use of the supplied bare-metal examples. After installing both the matching FreeRTOS and TCP/IP Stack packages in S32 Design Studio, the middleware components and associated examples should become available. You will most likely need to re-import the S32K3 project so that the newly installed components are properly recognized. Please always follow the dependency and compatibility information in the release notes of the selected RTD and TCP/IP Stack versions. 5. Recommended Ethernet bring-up procedure for the T-Box The recommended sequence is: Start with an S32K344 lwIP example supplied with the compatible S32K3 TCP/IP Stack package. Adapt the pin multiplexing and clock configuration to the S32K3-T-BOX schematic, including the 40 MHz FXOSC and the T-BOX RMII pin assignment. Apply the additional T-BOX-specific changes described in the S32K3-T-BOX lwIP Example Guide. Program the SJA1110 firmware through J57. The SJA1110 firmware initializes the switch, the RJ45 port, and the RMII interface toward the S32K344. Confirm that the SJA1110 firmware is running, including the expected indication on U36. Start the S32K344 application after the SJA1110 has had sufficient time to boot and provide the required RMII reference clock. For a new RTD-based SJA1110 project, download the applicable SJA11xx RTD, Ethernet PHY, Ethernet Switch and middleware packages and adapt any existing example to the S32K3-T-BOX. If you already have a valid NDA with NXP, please provide the NDA number in the Technical Support case, you have already created. I can then check whether the existing S32K3-T-BOX SJA1110 example can be shared with you. The relevant documentation and software packages are available from the NXP website. Some files are available only under Secure Files and require an appropriate NDA. Automotive Ethernet software may also be subject to export-control review and additional access approval might be required. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Purchasing the evaluation hardware and obtaining access to controlled-release software and documentation are separate processes. The SJA1110 documentation, RTD packages and complete example projects are not classified as public material. They are distributed through NXP Secure Files, where a valid NDA is required before access can be granted. The NDA is therefore not required simply because you purchased or use the S32K3-T-BOX. It is required because the complete SJA1110 example contains software and configuration information associated with a controlled-release Automotive Ethernet product. In addition, SJA1110 software packages are subject to an access-approval process. Automotive Ethernet software may also be subject to export-control policies, so additional approval may be required even when a valid NDA is already in place. Unfortunately, I cannot provide the complete project or firmware outside this controlled distribution process. The available alternatives are: If your company already has a valid NDA with NXP, please request access to the relevant SJA1110 Secure Files or provide the NDA reference in an NXP Technical Support case. If no NDA is currently in place, please initiate the NXP NDA process and then request Secure Files access. Publicly available S32K3-T-BOX materials may still be used for the S32K344 side, but they do not replace the controlled SJA1110 firmware and configuration required to initialize the switch and its RMII connection. Please note that an NDA enables the access-request process but does not automatically guarantee access to every software package. The applicable product and export-control approvals must also be completed. Once the required access is approved, the SJA1110 RTD packages and the applicable T-BOX example can be provided through the authorized support channel. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel We received a new NXP S32K3 T-Box prototype that was initially working, with the U36 indicator blinking and the Ethernet port LEDs illuminated. We flashed the following example using S32 Design Studio 3.6.10: Example_S32K344_EMAC_lwIP_FreeRTOS_S32K344_v1_0_S32DS36_RTD700 After flashing it, both the U36 indicator and Ethernet port LEDs stopped working. We also tried the following example, but the issue persisted: S32K344EVB_T172_UART_ETH_Gateway In addition, we had previously tried several other Ethernet-related examples on our previous T-Box, including bare-metal lwIP, FreeRTOS lwIP, and Ethernet internal loopback. We have now tried these examples on the new T-Box as well, but we are facing the same issue and have not been able to establish Ethernet connectivity. Could you please help us understand why this issue might be occurring with both T-Box boards? Is there any specific configuration or procedure required when using these examples with the T-Box? Also, is there any other complete, working Ethernet example specifically for the S32K3 T-Box that we can flash and use to verify Ethernet functionality? We would appreciate your guidance on identifying the cause and getting Ethernet communication working. Thank you for your support. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, Thank you for the clarification. Since we have purchased the NXP S32K3 T-Box prototype for our development and evaluation, could you please clarify why an NDA is required to access the complete SJA1110 example and firmware? We understand that some information may be confidential, but we would like to understand whether the NDA is mandatory even for customers who have purchased the hardware and need the firmware to bring up and test its Ethernet functionality. Could you please clarify the reason for this requirement and whether there is any alternative way to obtain the required firmware? Thank you for your support. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , The examples you tested are intended for the S32K3X4EVB-T172 and cannot be used on the S32K3-T-BOX without board-specific modifications. Although the MCU is the same, the T-BOX uses different pin assignments, a 40 MHz external crystal and an RMII connection where the 50 MHz reference clock is provided by the SJA1110. The startup sequence must also allow sufficient time for the SJA1110 to boot before the S32K344 clock and Ethernet initialization.   Flashing an application through the S32K344 debug interface should not affect the SJA1110 external flash. If U36 blinks after this power cycle, the SJA1110 firmware is still present and the issue was caused by the incompatible S32K344 application or its board initialization. If U36 remains inactive, the SJA1110 NVM boot and firmware should be checked separately. I have prepared and validated the following complete example specifically for the S32K3-T-BOX: Example S32K344 EMAC lwIP FreeRTOS S32K3-T-BOX S32DS 3.6.6 RTD7.0.1 - NXP Community S32K3 RTD 7.0.1 was selected as the reference baseline because the S32K3 RTD 7.0.0 release does not provide any basic S32K3 example projects. It has been tested successfully on the S32K3-T-BOX and already includes the required T-BOX-specific pin, clock, RMII and startup-sequence adaptations. See the comments in src/main.c for the complete list of changes made to the original lwip_FreeRTOS_s32k344 project. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, Thank you for your guidance. I have imported and tested the T-Box-specific example project, Example_S32K344_EMAC_lwIP_FreeRTOS_TBOX_v1_0_S32DS36_RTD701, using the following setup: S32 Design Studio 3.6.10 RTD 7.0.1 FreeRTOS 11.1.0 TCP/IP Stack 5.0.0 The project builds successfully with 0 errors and 0 warnings. I flashed the generated ELF to the S32K344 MCU using the NXP S32 Debug Probe connected through the J40 TAG connector. I checked device.c and test.c, including the clock initialization, the delay before clock setup, Eth_43_GMAC_Init(), and the FreeRTOS tasks responsible for lwIP initialization and LED blinking. However, I am still unable to establish Ethernet communication. Current observations: U37's RGB LED continues flashing blue after disconnecting the debugger and power-cycling the board. U36's LED on the SJA1110 appears faintly green. The RJ45 port LEDs remain off. The Windows Ethernet adapter shows Disconnected with a link speed of 0 bps. Pinging 192.168.225.100 results in request timeouts. The SJA1110 S1 DIP switch is set to OFF/OFF for NVM boot. When I subsequently tried to launch the debug configuration again to investigate the initialization sequence, I received the following error: PEmicro GDB Launch Failure: The GDB Server was not able to establish a connection to the target processor (E54431355). The S32 Debug Probe was not connected to the board during this latest attempt. Could you please advise me on the following? Is the blue flashing of U37 expected behavior for this example, or could it indicate that initialization is not completing? Since the RJ45 LEDs are off and Windows reports no physical link, what should I check first to identify the root cause? What would be the recommended next step to debug this issue without unnecessarily changing the existing clock and pin configurations? I would appreciate your guidance on how to proceed. Thank you! Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , As it has been documented in the header of src/main.c, this example uses the static IP address 192.168.0.210, not 192.168.225.100. Therefore, please configure the PC Ethernet adapter to the same subnet, for example 192.168.0.100 with subnet mask 255.255.255.0 and then ping 192.168.0.210. However, since Windows currently reports that the Ethernet cable is disconnected, the physical link issue must be resolved first. 1. U37 should flash white, but it appears as cyan. It indicates that the application is running and, in particular, that the initialization has not ended in a HardFault. However, it does not confirm that the Ethernet initialization completed successfully. 2. The U36 LED controlled by the SJA1110 should be blinking. If it only glows faintly, this may indicate a power-supply problem affecting the SJA1110. This would also explain why the RJ45 link LEDs remain off and Windows detects no physical link. 3. As the first debugging step, please check the SJA1110 power-supply rails on the board and confirm that they are present and stable. Please also inspect the board power configuration, jumper settings and supply connections against the T-BOX documentation. The PEmicro connection error is unrelated to the Ethernet issue. It is expected if the NXP S32 Debug Probe is not connected when the debug configuration is launched.   Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , The images confirm the external connections, but the next step is to measure the SJA1110 supply voltages electrically directly on the board. A visual inspection of the power connections cannot confirm that all required SJA1110 supply rails are present and stable. Please use the S32K3-T-BOX schematic to identify the SJA1110 supply rails and the corresponding decoupling capacitors. The voltages can normally be measured on the accessible capacitor terminals using a multimeter or a fine oscilloscope probe, with respect to board ground. Please take care to avoid shorting adjacent pads. Please check the following: Measure the SJA1110 supply voltages directly at the corresponding decoupling capacitors and report the measured values. Check the SJA1110 RST_N signal and confirm that it is released after power-up and remains stable. If an oscilloscope is available, probe the signal controlling the green channel of U36. This will show whether a blinking signal is generated or whether the signal remains at a constant level. If the supply voltages and reset signal are correct, check whether the SJA1110 provides the expected RMII reference clock to the S32K344. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, I have checked the power supply connections on the T-Box and am sharing images of the connections for your reference. The U36 LED (SJA1110) is glowing solid, faint green and is not blinking. The RJ45 LEDs are still off, and the Ethernet connection shows as disconnected on my PC. Could you please review the attached images and guide me on the next steps to debug this issue? I would like to get the Ethernet link working and successfully test ping connectivity. Please let me know what I should check next. Thank you for your support. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Please use the S32K3-T-BOX schematic to identify the SJA1110 supply rails and the corresponding decoupling capacitors. The voltages can normally be measured on the accessible capacitor terminals using a multimeter or a fine oscilloscope probe, with respect to board ground. Please take care to avoid shorting adjacent pads. Please check the following: Measure the SJA1110 supply voltages directly at the corresponding decoupling capacitors and report the measured values. Check the SJA1110 RST_N signal and confirm that it is released after power-up and remains stable. If an oscilloscope is available, probe the signal controlling the green channel of U36. This will show whether a blinking signal is generated or whether the signal remains at a constant level. If the supply voltages and reset signal are correct, check whether the SJA1110 provides the expected RMII reference clock to the S32K344. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello Pavel, Thank you for the guidance. I would like to share one additional observation. I tested another T-Box with the same power supply connection setup, and on that board, the U36 LED was blinking and the RJ45 Ethernet port LEDs were also illuminating. On my current T-Box, U36 remains solid faint green, and the RJ45 LEDs are off. Since the other T-Box works with the same connection setup, could you please advise whether I should proceed with measuring the SJA1110 supply rails and RST_N signal on the current board, or if there are any other checks I should perform first? I would like to identify the cause and get Ethernet connectivity working. Thank you. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello Pavel, Thank you for the guidance. I have already performed a complete power cycle with S1 set to OFF/OFF, but U36 still glows faint green and the RJ45 LEDs remain off. Could you please guide me on how to identify and check the SJA1110 supply rails and RST_N signal? Please let me know what equipment I should use, the specific measurement points, and the expected voltage levels so I can perform the checks and compare them with the working T-Box. Thank you for your support. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Since the second T-Box operates correctly with the same power-supply setup, please proceed with checking the affected board. First, perform a complete power cycle with S1 set to OFF/OFF. If U36 remains faint green, measure the SJA1110 supply rails and the RST_N signal during power-up, preferably comparing them with the working board. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello Pavel, Thank you for the guidance. I would like to clarify one point regarding the power supply. Before flashing the Ethernet examples and custom image, the T-Box was working normally, with the U36 LED blinking and the RJ45 Ethernet port LEDs illuminating. The issue appeared only after flashing the examples/images. Also, the second T-Box works correctly with the same power-supply setup. Based on these observations, I suspect the issue may not be related to the power supply itself. Could you please share your thoughts on whether the flashed firmware or configuration might have caused this behaviour? Thank you for your support. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , It is not yet clear to me which image was programmed into which device. Could you please provide the exact filename programmed into the SJA1110, the debugger and debug header used and confirm whether the SJA1110 was programmed through J57? The S32K344 Ethernet examples are programmed through the S32K344 debug interface and should not normally overwrite the SJA1110 firmware. This information is therefore needed before we can determine whether the SJA1110 firmware was replaced or whether the S32K344 application is affecting the board initialization. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello Pavel, Thank you for your response. We have flashed the following examples on both T-Box units using the S32K344 debug interface: Example_S32K344_EMAC_lwIP_FreeRTOS_S32K344_v1_0_S32DS36_RTD700  S32K344EVB_T172_UART_ETH_Gateway Bare-metal lwIP example FreeRTOS lwIP example Ethernet internal loopback example However, the issue remains the same on both T-Box units. After flashing these examples, the U36 LED stopped blinking and remained faint green, and the RJ45 Ethernet port LEDs were off. Before trying these examples, the LEDs were working normally. We are unsure whether the required PHY layer support is missing or needs to be configured differently for the T-Box. Could you please guide us on how to add or implement the required PHY layer support to get Ethernet communication working? Is there any additional PHY-related configuration or software support that we need to include? Thank you for your support. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , The missing PHY software is unlikely to explain this behavior. On the S32K3-T-BOX, the S32K344 communicates with the SJA1110 through RMII. The SJA1110 firmware is responsible for initializing the switch ports and the Ethernet PHY connected to the RJ45 interface. The U36 LED is controlled by the SJA1110 firmware. Therefore, a missing PHY configuration in the S32K344 application could prevent Ethernet communication, but it should not by itself cause the SJA1110 heartbeat indication on U36 to stop. At this point, I cannot confirm why programming the S32K344 applications caused U36 to remain faint green on both boards. Programming through the S32K344 debug interface should not normally overwrite the SJA1110 firmware. Please stop testing the generic S32K3X4EVB-T172 examples, as they are not configured for the S32K3-T-BOX hardware. Instead, use the validated T-BOX-specific example: Example S32K344 EMAC lwIP FreeRTOS S32K3-T-BOX, S32DS 3.6.6, RTD 7.0.1 Before testing the example, please perform the following checks: Set S1 to OFF/OFF for SJA1110 NVM boot. Disconnect the debugger and completely remove power from the board. Reapply power and check whether U36 starts blinking before starting a debug session. If U36 remains faint green, check the SJA1110 supply rails and the RST_N signal during power-up. If possible, compare the measurements with a known-working board. If the supply rails and reset sequence are correct, the SJA1110 boot process and firmware should be checked separately. A complete SJA1110 example and the associated controlled software are available through the approved NXP support channel and may require an NDA and additional access approval. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, Thank you for your guidance. Our company has an NDA with NXP, and we need the original factory firmware that the S32K3-T-BOX shipped with, for both the SJA1110 and the S32K344. Could you please share the prebuilt factory image, so that we can program them and restore the board to its original working state, as when it was new? Please also let us know the programming steps and the debugger to use. Could you also tell us the steps to follow to get them? We will provide the NDA reference details. Best regards, Divya Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello Pavel, As you suggested, we checked the RMII clock signal on the T-Box hardware. We probed the signal around resistor R490, which is connected to the "EMAC_RMII_TX_CLK" line. However, we observed a frequency of approximately 7–7.5 kHz on the oscilloscope instead of the expected 50 MHz. Could you please advise whether we are checking the correct point and what could be causing this frequency difference? Please let us know how we can further verify the RMII reference clock on the hardware. Thank you for your support. Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , Thank you for the measurement results. R490 on the EMAC_RMII_TX_CLK line is the correct area for checking the RMII reference clock. However, a measured frequency of approximately 7–7.5 kHz is not a valid RMII clock. It is more likely noise, unrelated periodic activity, or a measurement artifact while the 50 MHz clock is absent. Since U36 is not blinking and the RJ45 LEDs are inactive, please also perform the previously recommended checks: Measure the SJA1110 supply rails and compare them with the working T-Box. Check the SJA1110 RST_N signal during power-up and confirm that reset is released. Set S1 to OFF/OFF, disconnect the debugger, completely remove power, and then power the board again. Check the RMII reference clock before starting an S32K344 debug session. If the SJA1110 supply rails are correct but RST_N remains asserted, the reset circuit or an S32K344-controlled board signal must be investigated. If reset is released but U36 does not blink and no 50 MHz clock is present, the SJA1110 is most likely not booting correctly, and its firmware or boot configuration must be checked separately. Please share the measured SJA1110 supply voltages, the RST_N waveform and oscilloscope captures from both sides of R490. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hello @Divya2904 , I am not directly responsible for handling NDAs, but I can check the current NDA status with the relevant colleagues. For further assistance with the NDA process, please use the chat icon on nxp.com. If the query cannot be resolved online, the support team will create a supporting case on your behalf. Best regards, Pavel Re: S32K3-T-BOX – RJ45 LINK LED stays off with EMAC lwIP baremetal example Hi Pavel, Could you please share your email address. My manager and I would like to discuss the NDA with you over email. Alternatively, you can send me an email regarding this, and I can take it forward from there. Thank you.
View full article
i.MX8QM VPU information needed for developing H.264 decoding software Dear, We would like to develop software to decode H.264 video using the VPU inside the i.MX8QM. However, the reference manual is very brief on the VPU details. Is there more information available regarding its operation; for example, how to interact with these four M0+ cores, how to provide the TS data, how to retrieve the decoded video? Thanks in advance! Best regards. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello @Manuel_Salas Yes, we're doing fine, thanks for asking! Just to be sure we're aligned, we want to develop the software on the A-core, not on the M4 or even directly on the M0+ cores. From what we've seen in the provided document, there should be a driver inside the Linux distribution, right? I think I've found the source code of this. The firmware itself that must be loaded on these M0+ cores, is this also somewhere present inside the Linux distribution? Many thanks again! Best regards, ToarteFretter. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello @ToarteFretter  Hope you are doing very well. Unfortunately, NXP does not publicly share detailed Amphion VPU firmware documentation. The firmware is provided by the IP owner (Amphion), and NXP does not have any driver or SDK examples for controlling the VPU directly from the M core. We just have the i.MX VPU Application Programming Interface Linux Reference Manual available. Best regarsd, Salas. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hi @Manuel_Salas, Can you tell us if the firmware that needs to run on the M0+ cores for the VPU functionality on the i.MX8QM, has to be loaded by the software running on the A-core (e.g.: by Linux), or is this baked into the chip through ROM or maybe part of the SCFW? Quickly looking into the source code of Linux doesn't give us a clear response on this question; also because of the confusing and many flavours of the i.MX8, as well as the VPU types from what it looks. It would be very helpful of you, if you could give some more information on this? Also, if firmware needs to be loaded by us, where that we can find it? Many thanks! Best regards, ToarteFretter. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello @ToarteFretter  For the i.MX8QM Amphion VPU, the decoder firmware is not stored in ROM and is not part of SCFW. It is a separate binary that is loaded at runtime by the A-core host software (by the Linux Amphion kernel driver). Also, you can find the binary with: wget https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.33-7ce4783.bin Inside, you will find the vpu_fw_imx8_dec.bin and vpu_fw_imx8_enc.bin. NOTE: Table from i.MX Linux Release Notes. Best regards, Salas. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello @Manuel_Salas, Can it be that next to the decoder and encoder firmware's, that run respectively on one and two M0+ cores, there is also a third firmware needed for the fourth M0+ core? If yes, could this be ‘vpu_fw_imx8_xuvi.bin’ inside the provided archive? Many thanks! Best regards, Toartefretter. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello. Correct. VPU core Function Firmware M0+ core 0 Malone decoder vpu_fw_imx8_dec.bin M0+ cores 1–2 Windsor encoder vpu_fw_imx8_enc.bin M0+ core 3 XUVI/PPM processing, including TS-related functions vpu_fw_imx8_xuvi.bin Best regards, Salas. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello @Manuel_Salas, Many thanks! Regards, Toartefretter. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello @Manuel_Salas, I have a new question, can the decoder output frames in another format than YUV (e.g. RGBA or BGRA)? If not, how is the conversion "normally" done then? Thanks in advance! Regards, Toartefretter. Re: i.MX8QM VPU information needed for developing H.264 decoding software Hello @Manuel_Salas, I have an additional question... We don't find back where the 'vpu_fw_imx8_xuvi.bin' image gets loaded for the M0+ core 3, is this done by Linux, or uBoot, or by some other means? The encoder and decoder images though we've found back... Many thanks! Kind regards, Toartefretter.
View full article