Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
Autosar Os 示例 你好 我正在开发一个使用 S32K146 芯片和 Autosar 架构的 ECU 项目。我以前没有接触过 Os 模块的使用,如果您能提供一些与 Os 模块相关的例程,我将不胜感激。 谢谢! Re: Autosar Os Example 能给我一个链接吗? Re: Autosar Os Example 你好 AUTOSAR 操作系统软件包中有一个例子: 您可以在恩智浦 SW 账户中找到它:   S32K_AUTOSAR_OS_4_0_98_RTM_1_0_0.exe_ 它非常直观,你可以通过用户手册 AUTOSAR_OSS32K_UM.pdf 进行配置,它是软件包的一部分。 顺祝商祺! Peter     Re: Autosar Os Example 我正在开发一个使用 S32K146 芯片的 Autosar 项目,配置工具是 EB Tresos。我配置了CAN堆栈并在环回模式下测试了上层的传输和接收过程(从Com层到MCAL),一切正常。 当我将 CAN 控制器配置为正常模式时,CAN 数据被写入寄存器(RAMn),但硬件并未启动传输。Tx 引脚上没有数据,因此,没有触发信号来清除 TX Buff 标志。这也导致前四帧数据成功写入 Buff,但从第五帧开始,数据无法写入,并返回 CAN BUSY 状态。 由于这个问题,我不知道如何解决。因此,我使用了 S32DS 中为 S32K146 提供的 Autosar CAN 示例,做了一些修改,并在相同的硬件上运行。然而,数据仍然无法传输,同样的问题再次出现。 您能帮我分析一下 CAN 传输在我的项目中出现故障的原因吗?谢谢。
View full article
S32K3 BCTUによってトリガーされたADCチャネルの異常な数 こんにちは、NXP EMIOS による ADC 取得のトリガーをテストして BCTU をトリガーし、その結果を FIFO1 に格納するプロセス中に異常を発見しました。私は、RTD バージョン 6.0.0 の S32K344 ハードウェアを使用しています。 ソフトウェアを使用して BCTU のトリガーをテストし、1 つの結果を得ました。これは期待通りの正しい結果です。 PWM で BCTU をトリガーし、次に ADC をトリガーするテストを行いました。ADC チャネルを 3 以上に構成したところ、取得された結果の数も正しくなり、期待どおりになりました。 2 のテストに基づき、チャネル数を 2 に設定したところ、得られた結果の数は 4 となり、期待どおりになりませんでした。 ここに私の設定、テストデータ、設定プロジェクトの一部を示します。 宜しくお願いします、 シアンロン Re: S32K3 Abnormal number of ADC channels triggered by BCTU こんにちは@ wuxianlong 提供されたデモをテストしたところ、問題を再現CAN。 これは、RTD の実装制限が原因である可能性があります。 CH17 の割り込み有効化を無効にすると、問題は解決するはずです。 Re: S32K3 Abnormal number of ADC channels triggered by BCTU こんにちは@ wuxianlong 「でも、原因は何でしょう?確認してみたところ、BCTUのトリガー数は1でした。」 コードにエラーは見当たりません。フラグは変更を保持します。(設定Bctu_Trg にブレークポイントを設定します。 Re: S32K3 Abnormal number of ADC channels triggered by BCTU こんにちは、 @Senlent サポートありがとうございます。あなたの提案によれば、PWM 割り込みを無効にすると、実際にこの問題は解決できることが判明しました。しかし、その理由は何でしょうか?確認したところ、BCTU のトリガー数は 1 です。 よろしくお願いします、 シアンロン Re: S32K3 Abnormal number of ADC channels triggered by BCTU こんにちは@ wuxianlong CH17 の割り込みを有効にすると (FEN がセットされる)、flag0 と flag2 は同じになり、これは予想どおりです。ただし、flag1 は flag2 の 2 倍のサイズ (また flag0 の 2 倍のサイズ) であることがわかります。したがって、BCTU が 2 回トリガーされ、FIFO1 でエラーが発生したと考えられます。 Re: S32K3 Abnormal number of ADC channels triggered by BCTU こんにちは、 @Senlent 申し訳ありませんが、私の表現が十分に明確でない可能性があります。 PWM 割り込みが無効になった後、BCTU が 1 つの ADC チャネルを正しくトリガーできるのはなぜでしょうか?PWM 割り込みを無効にする前は、トリガーされた ADC チャネルが正しくありませんでした。PWM 割り込みを無効にする前に、BCTU のトリガー カウントが正しいこと、および 1 つの PWM が通常 BCTU を 1 回トリガーしていることを確認しました。 私の以前の理解によれば、PWM は BCTU を正しくトリガーし、ADC を誤ってトリガーしたのは BCTU でした。しかし、あなたの説明によると、PWM 信号のルーティングに問題があるようです。これはよく分かりません。さらに詳しい情報を提供してもらえますか? よろしくお願いします、 シアンロン Re: S32K3 Abnormal number of ADC channels triggered by BCTU どうもありがとうございます。
View full article
i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) We designed a custom board based with MIMX8ML8XXXKZ SoC MT53E768M64D4DE-046 WT:C LPDDR4 BD71847 PMIC All SoC and DRAM power lanes seem to be powered properly Based on previous experience with i.MX8MM we attempted to generate timings for the DRAM using the DDR Mtool, but the result we got  Spoiler (Highlight to read) Download is complete Waiting for the target board boot... ===================hardware_init===================== hardware_init exit ************************************************************************* ************************************************************************* ************************************************************************* MX8 DDR Stress Test V3.30 Built on Nov 24 2021 13:52:12 ************************************************************************* Waiting for board configuration from PC-end... --Set up the MMU and enable I and D cache-- - This is the Cortex-A53 core - Check if I cache is enabled - Enabling I cache since it was disabled - Push base address of TTB to TTBR0_EL3 - Config TCR_EL3 - Config MAIR_EL3 - Enable MMU - Data Cache has been enabled - Check system memory register, only for debug - VMCR Check: - ttbr0_el3: 0x97d000 - tcr_el3: 0x2051c - mair_el3: 0x774400 - sctlr_el3: 0xc01815 - id_aa64mmfr0_el1: 0x1122 - MMU and cache setup complete ************************************************************************* ARM clock(CA53) rate: 1800MHz DDR Clock: 2000MHz ============================================ DDR configuration DDR type is LPDDR4 Data width: 32, bank num: 8 Row size: 17, col size: 10 One chip select is used Number of DDR controllers used on the SoC: 1 Density per chip select: 3072MB Density per controller is: 3072MB Total density detected on the board is: 3072MB ============================================ MX8M-plus: Cortex-A53 is found ************************************************************************* ============ Step 1: DDRPHY Training... ============ ---DDR 1D-Training @2000Mhz... PMU: Error: CA Training Failed. PMU: ***** Assertion Error - terminating ***** [Result] FAILED Download is completeWaiting for the target board boot...===================hardware_init=====================hardware_init exit***************************************************************************************************************************************************************************************************************************MX8 DDR Stress Test V3.30Built on Nov 24 2021 13:52:12*************************************************************************Waiting for board configuration from PC-end...--Set up the MMU and enable I and D cache--- This is the Cortex-A53 core- Check if I cache is enabled- Enabling I cache since it was disabled- Push base address of TTB to TTBR0_EL3- Config TCR_EL3- Config MAIR_EL3- Enable MMU- Data Cache has been enabled- Check system memory register, only for debug- VMCR Check:- ttbr0_el3: 0x97d000- tcr_el3: 0x2051c- mair_el3: 0x774400- sctlr_el3: 0xc01815- id_aa64mmfr0_el1: 0x1122- MMU and cache setup complete*************************************************************************ARM clock(CA53) rate: 1800MHzDDR Clock: 2000MHz============================================DDR configurationDDR type is LPDDR4Data width: 32, bank num: 8Row size: 17, col size: 10One chip select is usedNumber of DDR controllers used on the SoC: 1Density per chip select: 3072MBDensity per controller is: 3072MBTotal density detected on the board is: 3072MB============================================MX8M-plus: Cortex-A53 is found*************************************************************************============ Step 1: DDRPHY Training... ============---DDR 1D-Training @2000Mhz...PMU: Error: CA Training Failed.PMU: ***** Assertion Error - terminating *****[Result] FAILED A similar situation was with the Config tool. We tried to use the .ds script both generated by Config tool, as well as the RPA, neither worked Based on the discussion on the forum we attempted to disable the CA training. And calibration for single frequency setpoint started working Spoiler (Highlight to read) Download is complete Waiting for the target board boot... ===================hardware_init===================== hardware_init exit ************************************************************************* ************************************************************************* ************************************************************************* MX8 DDR Stress Test V3.30 Built on Nov 24 2021 13:52:12 ************************************************************************* Waiting for board configuration from PC-end... --Set up the MMU and enable I and D cache-- - This is the Cortex-A53 core - Check if I cache is enabled - Enabling I cache since it was disabled - Push base address of TTB to TTBR0_EL3 - Config TCR_EL3 - Config MAIR_EL3 - Enable MMU - Data Cache has been enabled - Check system memory register, only for debug - VMCR Check: - ttbr0_el3: 0x97d000 - tcr_el3: 0x2051c - mair_el3: 0x774400 - sctlr_el3: 0xc01815 - id_aa64mmfr0_el1: 0x1122 - MMU and cache setup complete ************************************************************************* ARM clock(CA53) rate: 1800MHz DDR Clock: 2000MHz ============================================ DDR configuration DDR type is LPDDR4 Data width: 32, bank num: 8 Row size: 17, col size: 10 Two chip selects are used Number of DDR controllers used on the SoC: 1 Density per chip select: 3072MB Density per controller is: 6144MB Total density detected on the board is: 6144MB ============================================ MX8M-plus: Cortex-A53 is found ************************************************************************* ============ Step 1: DDRPHY Training... ============ ---DDR 1D-Training @2000Mhz... [Process] End of initialization [Process] End of read enable training [Process] End of fine write leveling [Process] End of read DQ deskew training [Process] End of MPR read delay center optimization [Process] End of Write Leveling coarse delay [Process] End of write delay center optimization [Process] End of read delay center optimization [Process] End of max read latency training [Result] PASS ---DDR 2D-Training @2000Mhz... [Process] End of initialization [Process] End of 2D write delay/voltage center optimization [Process] End of 2D write delay/voltage center optimization [Process] End of 2D read delay/voltage center optimization [Process] End of 2D read delay/voltage center optimization [Result] PASS ============ Step 2: DDR memory accessing... ============ Verifying DDR frequency [email protected] [Result] OK ============ Step 3: DDR parameters processing... ============ [Result] Done Success: DDR Calibration completed!!! Download is completeWaiting for the target board boot...===================hardware_init=====================hardware_init exit***************************************************************************************************************************************************************************************************************************MX8 DDR Stress Test V3.30Built on Nov 24 2021 13:52:12*************************************************************************Waiting for board configuration from PC-end...--Set up the MMU and enable I and D cache--- This is the Cortex-A53 core- Check if I cache is enabled- Enabling I cache since it was disabled- Push base address of TTB to TTBR0_EL3- Config TCR_EL3- Config MAIR_EL3- Enable MMU- Data Cache has been enabled- Check system memory register, only for debug- VMCR Check:- ttbr0_el3: 0x97d000- tcr_el3: 0x2051c- mair_el3: 0x774400- sctlr_el3: 0xc01815- id_aa64mmfr0_el1: 0x1122- MMU and cache setup complete*************************************************************************ARM clock(CA53) rate: 1800MHzDDR Clock: 2000MHz============================================DDR configurationDDR type is LPDDR4Data width: 32, bank num: 8Row size: 17, col size: 10Two chip selects are usedNumber of DDR controllers used on the SoC: 1Density per chip select: 3072MBDensity per controller is: 6144MBTotal density detected on the board is: 6144MB============================================MX8M-plus: Cortex-A53 is found*************************************************************************============ Step 1: DDRPHY Training... ============---DDR 1D-Training @2000Mhz...[Process] End of initialization[Process] End of read enable training[Process] End of fine write leveling[Process] End of read DQ deskew training[Process] End of MPR read delay center optimization[Process] End of Write Leveling coarse delay[Process] End of write delay center optimization[Process] End of read delay center optimization[Process] End of max read latency training[Result] PASS---DDR 2D-Training @2000Mhz...[Process] End of initialization[Process] End of 2D write delay/voltage center optimization[Process] End of 2D write delay/voltage center optimization[Process] End of 2D read delay/voltage center optimization[Process] End of 2D read delay/voltage center optimization[Result] PASS============ Step 2: DDR memory accessing... ============Verifying DDR frequency [email protected][Result] OK============ Step 3: DDR parameters processing... ============[Result] DoneSuccess: DDR Calibration completed!!! If multiple frequency setpoints are set, the optimization keeps failing at the second setpoint And the stress test started passing correctly both in the Mtool and in the Config tool. However, the Diag read margin, diag write margin and CA eye tests keep failing One thing to note is that comparing to the IMX8MP-EVK we connected the CA and CB to their respective pins on the CPU (in the EVK they were reversed) Here are the respective lanes lengths and the delay deltas Spoiler (Highlight to read) 1. CAx_B, CKE_A, CK_CS_A - 20mm, <1ps 2. CAx_B, CKE_B, CK_CS_B - 19mm, <1ps 3. DQ07_A - 15mm, <1ps 4. DQ07_B - 14.5mm, <1ps 5. DQ815_A -10mm, <1ps 6. DQ815_B -10mm, <1ps 7. CKA - 21mm, DQS0 - 15mm (-22ps to CKA), DQS1 - 13mm (-55ps to CKA) 8. CKB - 21mm, DQS2 - 14mm (-24ps to CKA), DQS3 - 13mm (-54ps to CKA) 1. CAx_B, CKE_A, CK_CS_A - 20mm, <1ps2. CAx_B, CKE_B, CK_CS_B - 19mm, <1ps3. DQ07_A - 15mm, <1ps4. DQ07_B - 14.5mm, <1ps5. DQ815_A -10mm, <1ps6. DQ815_B -10mm, <1ps7. CKA - 21mm, DQS0 - 15mm (-22ps to CKA), DQS1 - 13mm (-55ps to CKA)8. CKB - 21mm, DQS2 - 14mm (-24ps to CKA), DQS3 - 13mm (-54ps to CKA) Can the CA/CB swap be the reason of the problem? 回复: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) @AlexandrP , @sfatyushkin ,@JorgeCas ,Hi, We designed a custom board based with MIMX8ML4xxxKZ, However, when testing the DDR, even the initial phy init failed, and the error message was as follows: ```txt test-prefix : "C:/nxp/i.MX_CFG_25.12/bin/python3/python" "C:/nxp/i.MX_CFG_25.12/bin/python3/memtool/memtool_entry.py" -t "runtest" -d "C:/ProgramData/NXP/mcu_data_25.12/processors/MIMX8ML4xxxKZ/ksdk2_0/mem_validation/ddrc" -a "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/test_app_phy_test_0_0_.log" -p "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/phy_training_phy_test_0_0_.log" -l INFO "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/connect.json" "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/test.json" "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/phy.json" "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/ddrc_registers.json" "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/ddrc_config.json" "C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/ddrc_config_in.json" INFO memtool.utils.helper *****C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/connect.json INFO memtool.utils.helper *****C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/test.json INFO memtool.utils.helper *****C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/phy.json INFO memtool.utils.helper *****C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/ddrc_registers.json INFO memtool.utils.helper *****C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/ddrc_config.json INFO memtool.utils.helper *****C:/Users/HEJIAN~1.LIG/AppData/Local/Temp/mem_validation/ddrc_config_in.json INFO memtool.processor.imx8m.imx8_processor Xls mapping load time 0.011705 INFO memtool.processor.base_processor Config time 0.008170 INFO memtool.processor.base_processor DS file time 0.256190 INFO memtool.phyinit.phy_init Run phyinit for 2020.06\lpddr4 INFO memtool.comm.serial_channel Using serial: COM23 WARNING memtool.comm.serial_channel Timeout waiting for response "[TARGET IS ALIVE]" ERROR memtool.common.base_test Application is not waiting for input state. WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" ERROR memtool.comm.serial_channel Read symbol failed after 3 tries WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" ERROR memtool.comm.serial_channel Read symbol failed after 3 tries WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" ERROR memtool.comm.serial_channel Read symbol failed after 3 tries WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" ERROR memtool.comm.serial_channel Read symbol failed after 3 tries WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" WARNING memtool.comm.serial_channel Timeout waiting for response "[READ FINISHED]" ERROR memtool.comm.serial_channel Read symbol failed after 3 tries {'app_state': -1, 'num_records': -1, 'records': [], 'debug': -1, 'err_capt_regs': -1, 'debug_regs': -1} ****DONE**** ``` Since this is my first time using IMX8, could you give me some advice? Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Hello, According to constraint manager, the routing is under the recommended values: Best regards. Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) 127 + 50 ps < 191ps Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Hello, 1) A clock frequency reduction, but it is not a warranty that will work.  2) It is under the recommendation, ±50 ps. Best regards. Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Jorge, thanks a lot! This helped us to understand the problem. When laying out the LpDDR lines, we used the same rules as before when laying out iMX8MM, without paying attention to the tightening of the requirements for the CAx lines (within 2 ps in groups), and did not take into account the Pkg delay. So, two questions. 1. Is it possible to configure the CA_x_y lines and run the board with a spread of CA lines times of about 20 ps (possibly at a slow speed), or it is impossible to do without redesigning the board? 2. In the i.MX 8M Plus Hardware Developer’s Guide, all timings seems like in EVK. But the delay on the CK_A lines is indicated to be about 107 ps (145 ps taking into account the Pkg delay). On the EVK board (directly in the project that you provided), I see a delay on the CKa lines of about 89 ps (127 ps taking into account the Pkg delay, and this is outside the 50 ps tolerance for the CA_A_0...4 lines). What is correct? Best regards, Serge Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Hello, The issue you are mentioning could be caused by marginal signal integrity or timing violations. Please take a look in attached file for .alg file. Best regards. Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Based on your response we decided to tackle the ODT parameters once again. We redid the Read/Write ODT and driver matrix in Optimization tab and noticed that some random ODT combinations drop 'Target a connection or exception in the script'. Saying random, I mean that from run to run they are different and don't occur every time. Otherwise, the rest of the combinations succeed, even up to 240 Ohm We also evaluated the "Diag Read/Write Margin tests results more closely. Before, only the fact that test showed "checkmark 100%" was viewed , and noticed that whenever test "passes" it demonstrates not all of the DQ lanes, and the number is different every time. See attached pictures (for some reason the forum doesn't let me attach pictures neither in text, nor as attachments, so adding link to drive folder https://drive.google.com/drive/folders/1U4-G1_Em-73UR1zrtUFAsVCRBpAlchGN?usp=sharing) Trying to investigate this, we observed the 1V1 power lane with the oscilloscope, didn't notice anything extra suspicious, but during that the "Diag Margin" test started to show the Eye diagrams for all of the DQ lanes in more or less okay shape, so we added 9.5pF capacitor (see the attachment with "cond" for reference), and the Margin Test results in all DQ lanes diagrams every time it shows anything CA Bus Signals Margin test as well shows "Checkmark 100%", but in the "Charts" tab it states "Collecting diagnostic data..." and in logs it shows error "CA data is missing!" See full log in spoiler Spoiler (Highlight to read) #################### Result for: ca_bus ###### Run 1 ############################################### Microsoft Windows [Version 10.0.19045.2965] (c) Microsoft Corporation. All rights reserved. C:\nxp\i.MX_CFG_25.03\bin>prompt test-prefix : test-prefix : "C:/nxp/i.MX_CFG_25.03/bin/python3/python" "C:/nxp/i.MX_CFG_25.03/bin/python3/memtool/memtool_entry.py" -t "runtest" -d "C:/ProgramData/NXP/mcu_data_25.03/processors/MIMX8ML8xxxKZ/ksdk2_0/mem_validation/ddrc" -p "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy_training_ca_bus_lpddr4_0_0_.log" -i "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/figure_ca_bus_lpddr4_0_0_.png" -l DEBUG "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.json" INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.json DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.processor.base_processor freq_0 set to 667 INFO memtool.phyinit.phy_init Run phyinit for 2020.06\lpddr4 DEBUG memtool.phyinit.phy_init Shared library C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\phyinit\sharedlib\phyinit_2020.06_lpddr4.dll DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.phyinit.phy_init PHY config file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_config_final.json DEBUG memtool.phyinit.phy_init Phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txt DEBUG memtool.phyinit.phy_init Retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txt DEBUG memtool.phyinit.out_parser Parse phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txt DEBUG memtool.phyinit.out_parser Parse retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txt DEBUG memtool.phyinit.out_parser Parse state A_BRING_UP_POWER DEBUG memtool.phyinit.out_parser Parse state C_PHY_INIT_CONFIG(210) DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x32fb to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.c DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x15d4 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.json DEBUG memtool.phyinit.out_parser Parse state LOAD_IMEM_1(445) DEBUG memtool.phyinit.out_parser Parse state D_LOAD_IMEM_1D(465) DEBUG memtool.phyinit.out_parser Write IMEM 1D as bin size 0x8000 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.bin DEBUG memtool.phyinit.out_parser Write IMEM 1D as txt size 0x6eaf3 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.txt DEBUG memtool.phyinit.out_parser Parse state PHASE.E_SET_DFI_CLOCK(16850) DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1(16869) DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1D(16885) DEBUG memtool.phyinit.out_parser Write DMEM 1D as bin size 0x67c to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.bin DEBUG memtool.phyinit.out_parser Write DMEM 1D as txt size 0x5398 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.txt DEBUG memtool.phyinit.out_parser Parse state PHASE.G_EXEC_FW(17716) DEBUG memtool.phyinit.out_parser Parse state PHASE.PHASE.I_LOAD_PIE(17782) DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x44ff to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.txt DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x933a to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.json DEBUG memtool.phyinit.out_parser Parse state PHASE.H_READ_MSG_BLOCK(18389) DEBUG memtool.phyinit.out_parser Parse retention register list INFO memtool.comm.serial_channel Using serial: COM3 DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.comm.serial_channel Channel is not alive DEBUG spsdk.utils.interfaces.device.usb_device Closing the Interface: SE Blank 865 (0x1FC9, 0x0146)path=b'\\\\?\\hid#vid_1fc9&pid_0146#6&dc7bbf3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' sn='' DEBUG memtool.comm.serial_channel ==================hardware_init======================= DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel [DEBUG]: Clock setup... DEBUG memtool.comm.serial_channel [INFO]: ARM core clock rate is 1800MHz... DEBUG memtool.comm.serial_channel [INFO]: DDR Dram frequency is 666MHz... DEBUG memtool.comm.serial_channel [DEBUG]: Clock setup ended... DEBUG memtool.comm.serial_channel ==================hardware_init exit================== DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read app state WAIT_FOR_INPUT INFO memtool.common.base_test Write app log level DEBUG memtool.comm.serial_channel Executing: Mw92F510,1:0000000a INFO memtool.common.base_test Write app state CONFIG_RECEIVED DEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:55aa55aa DEBUG test_app [DEBUG]: Initialize mailbox... DEBUG test_app [DEBUG]: Apply Init PHY Config... DEBUG test_app [DEBUG]: Execute PHY operation... DEBUG test_app [DEBUG]: Run PHY full init... DEBUG test_app [DEBUG]: Write 1D imem image, offset 0x00050000 size 0x00004000... DEBUG test_app [DEBUG]: End of load 1D imem image... DEBUG test_app [DEBUG]: Set DFI Clock for pstate 0... DEBUG test_app [DEBUG]: Write 1D dmem image, offset 0x00054000 size 0x0000033e... DEBUG test_app [DEBUG]: End of load 1D dmem image... DEBUG test_app [INFO]: Execute Training Firmware for 1D pstate0@667MHz... DEBUG test_app [INFO]: Training Firmware completed for 1D pstate0@667MHz with status 0; Execution ended in 0s.310ms.912us... DEBUG test_app [DEBUG]: PHY operation ended with status 0... DEBUG memtool.comm.serial_channel Executing: mw92F918,1 DEBUG memtool.comm.serial_channel Result: 0x00000000 DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read app state WAIT_FOR_INPUT INFO memtool.common.base_test Read phy status DEBUG memtool.comm.serial_channel Executing: mw92F91C,1 DEBUG memtool.comm.serial_channel Result: 0x00000059 INFO root Number of logged items 0x59 DEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4\lpddr4_pmu_train.strings DEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4_2d\lpddr4_2d_pmu_train.strings DEBUG memtool.comm.serial_channel Executing: mb961000,400 DEBUG memtool.comm.serial_channel Executing: mb961400,400 DEBUG memtool.comm.serial_channel Executing: mb961800,400 DEBUG memtool.comm.serial_channel Executing: mb961C00,400 DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read app state WAIT_FOR_INPUT INFO memtool.common.base_test Write input param test = 200 DEBUG memtool.comm.serial_channel Executing: Mw92EA10,1:000000c8 INFO memtool.common.base_test Write app state INPUT_RECEIVED DEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:77665544 DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read symbol app_state = 0x5588dcfe DEBUG memtool.comm.serial_channel Executing: mw92EABC,1 DEBUG memtool.comm.serial_channel Result: 0x00000001 INFO memtool.common.base_test Read symbol num_records = 0x1 INFO memtool.common.base_test App state WAIT_FOR_INPUT DEBUG memtool.comm.serial_channel Executing: mw92EF40,8 DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read symbol debug = [0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.comm.serial_channel Executing: mw92EF60,A DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read symbol err_capt_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.comm.serial_channel Executing: mw92EF88,20 DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read symbol debug_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.comm.serial_channel Executing: mw92EAC0,1 DEBUG memtool.comm.serial_channel Result: 0x00000001 INFO memtool.common.base_test Read symbol state = 1 DEBUG memtool.comm.serial_channel Executing: mw92EAC4,1 DEBUG memtool.comm.serial_channel Result: 0x000000C8 INFO memtool.common.base_test Read symbol test_id = 200 INFO memtool.common.base_test Record 0 state TestStatus.PASS DEBUG memtool.comm.serial_channel Executing: mw92EAC8,10 DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read test data [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Test 200 finished with state 1 DEBUG memtool.common.base_test App state: WAIT_FOR_INPUT DEBUG memtool.common.base_test Err_caption_registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.common.base_test Debug: [0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.common.base_test Debug registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.common.base_test Results: [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}] DEBUG memtool.common.base_test Number of records: 1 ERROR memtool.memtests.phy_diags_tests CA data is missing! {'app_state': 1435032830, 'num_records': 1, 'records': [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}], 'debug': '[0, 0, 0, 0, 0, 0, 0, 0]', 'err_capt_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0]', 'debug_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'} ****DONE**** #################### Result for: ca_bus ###### Run 1 ###############################################Microsoft Windows [Version 10.0.19045.2965](c) Microsoft Corporation. All rights reserved.C:\nxp\i.MX_CFG_25.03\bin>prompt test-prefix :test-prefix : "C:/nxp/i.MX_CFG_25.03/bin/python3/python" "C:/nxp/i.MX_CFG_25.03/bin/python3/memtool/memtool_entry.py" -t "runtest" -d "C:/ProgramData/NXP/mcu_data_25.03/processors/MIMX8ML8xxxKZ/ksdk2_0/mem_validation/ddrc" -p "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy_training_ca_bus_lpddr4_0_0_.log" -i "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/figure_ca_bus_lpddr4_0_0_.png" -l DEBUG "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.json"INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.jsonDEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.processor.base_processor freq_0 set to 667INFO memtool.phyinit.phy_init Run phyinit for 2020.06\lpddr4DEBUG memtool.phyinit.phy_init Shared library C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\phyinit\sharedlib\phyinit_2020.06_lpddr4.dllDEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.phyinit.phy_init PHY config file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_config_final.jsonDEBUG memtool.phyinit.phy_init Phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txtDEBUG memtool.phyinit.phy_init Retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txtDEBUG memtool.phyinit.out_parser Parse phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txtDEBUG memtool.phyinit.out_parser Parse retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txtDEBUG memtool.phyinit.out_parser Parse state A_BRING_UP_POWERDEBUG memtool.phyinit.out_parser Parse state C_PHY_INIT_CONFIG(210)DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x32fb to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.cDEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x15d4 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.jsonDEBUG memtool.phyinit.out_parser Parse state LOAD_IMEM_1(445)DEBUG memtool.phyinit.out_parser Parse state D_LOAD_IMEM_1D(465)DEBUG memtool.phyinit.out_parser Write IMEM 1D as bin size 0x8000 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.binDEBUG memtool.phyinit.out_parser Write IMEM 1D as txt size 0x6eaf3 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.txtDEBUG memtool.phyinit.out_parser Parse state PHASE.E_SET_DFI_CLOCK(16850)DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1(16869)DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1D(16885)DEBUG memtool.phyinit.out_parser Write DMEM 1D as bin size 0x67c to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.binDEBUG memtool.phyinit.out_parser Write DMEM 1D as txt size 0x5398 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.txtDEBUG memtool.phyinit.out_parser Parse state PHASE.G_EXEC_FW(17716)DEBUG memtool.phyinit.out_parser Parse state PHASE.PHASE.I_LOAD_PIE(17782)DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x44ff to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.txtDEBUG memtool.phyinit.out_parser Write PIE as txt size 0x933a to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.jsonDEBUG memtool.phyinit.out_parser Parse state PHASE.H_READ_MSG_BLOCK(18389)DEBUG memtool.phyinit.out_parser Parse retention register listINFO memtool.comm.serial_channel Using serial: COM3DEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.comm.serial_channel Channel is not aliveDEBUG spsdk.utils.interfaces.device.usb_device Closing the Interface: SE Blank 865 (0x1FC9, 0x0146)path=b'\\\\?\\hid#vid_1fc9&pid_0146#6&dc7bbf3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' sn=''DEBUG memtool.comm.serial_channel ==================hardware_init=======================DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel [DEBUG]: Clock setup...DEBUG memtool.comm.serial_channel [INFO]: ARM core clock rate is 1800MHz...DEBUG memtool.comm.serial_channel [INFO]: DDR Dram frequency is 666MHz...DEBUG memtool.comm.serial_channel [DEBUG]: Clock setup ended...DEBUG memtool.comm.serial_channel ==================hardware_init exit==================DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveDEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read app state WAIT_FOR_INPUTINFO memtool.common.base_test Write app log levelDEBUG memtool.comm.serial_channel Executing: Mw92F510,1:0000000aINFO memtool.common.base_test Write app state CONFIG_RECEIVEDDEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:55aa55aaDEBUG test_app [DEBUG]: Initialize mailbox...DEBUG test_app [DEBUG]: Apply Init PHY Config...DEBUG test_app [DEBUG]: Execute PHY operation...DEBUG test_app [DEBUG]: Run PHY full init...DEBUG test_app [DEBUG]: Write 1D imem image, offset 0x00050000 size 0x00004000...DEBUG test_app [DEBUG]: End of load 1D imem image...DEBUG test_app [DEBUG]: Set DFI Clock for pstate 0...DEBUG test_app [DEBUG]: Write 1D dmem image, offset 0x00054000 size 0x0000033e...DEBUG test_app [DEBUG]: End of load 1D dmem image...DEBUG test_app [INFO]: Execute Training Firmware for 1D [email protected] test_app [INFO]: Training Firmware completed for 1D pstate0@667MHz with status 0; Execution ended in 0s.310ms.912us...DEBUG test_app [DEBUG]: PHY operation ended with status 0...DEBUG memtool.comm.serial_channel Executing: mw92F918,1DEBUG memtool.comm.serial_channel Result: 0x00000000DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveDEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read app state WAIT_FOR_INPUTINFO memtool.common.base_test Read phy statusDEBUG memtool.comm.serial_channel Executing: mw92F91C,1DEBUG memtool.comm.serial_channel Result: 0x00000059INFO root Number of logged items 0x59DEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4\lpddr4_pmu_train.stringsDEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4_2d\lpddr4_2d_pmu_train.stringsDEBUG memtool.comm.serial_channel Executing: mb961000,400DEBUG memtool.comm.serial_channel Executing: mb961400,400DEBUG memtool.comm.serial_channel Executing: mb961800,400DEBUG memtool.comm.serial_channel Executing: mb961C00,400DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveDEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read app state WAIT_FOR_INPUTINFO memtool.common.base_test Write input param test = 200DEBUG memtool.comm.serial_channel Executing: Mw92EA10,1:000000c8INFO memtool.common.base_test Write app state INPUT_RECEIVEDDEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:77665544DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read symbol app_state = 0x5588dcfeDEBUG memtool.comm.serial_channel Executing: mw92EABC,1DEBUG memtool.comm.serial_channel Result: 0x00000001INFO memtool.common.base_test Read symbol num_records = 0x1INFO memtool.common.base_test App state WAIT_FOR_INPUTDEBUG memtool.comm.serial_channel Executing: mw92EF40,8DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read symbol debug = [0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.comm.serial_channel Executing: mw92EF60,ADEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read symbol err_capt_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.comm.serial_channel Executing: mw92EF88,20DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read symbol debug_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.comm.serial_channel Executing: mw92EAC0,1DEBUG memtool.comm.serial_channel Result: 0x00000001INFO memtool.common.base_test Read symbol state = 1DEBUG memtool.comm.serial_channel Executing: mw92EAC4,1DEBUG memtool.comm.serial_channel Result: 0x000000C8INFO memtool.common.base_test Read symbol test_id = 200INFO memtool.common.base_test Record 0 state TestStatus.PASSDEBUG memtool.comm.serial_channel Executing: mw92EAC8,10DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read test data [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Test 200 finished with state 1DEBUG memtool.common.base_test App state: WAIT_FOR_INPUTDEBUG memtool.common.base_test Err_caption_registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.common.base_test Debug: [0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.common.base_test Debug registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.common.base_test Results: [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}]DEBUG memtool.common.base_test Number of records: 1ERROR memtool.memtests.phy_diags_tests CA data is missing!{'app_state': 1435032830, 'num_records': 1, 'records': [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}], 'debug': '[0, 0, 0, 0, 0, 0, 0, 0]', 'err_capt_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0]', 'debug_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}****DONE**** "CA Eye" always runs into timeout, I tried different values for "ATXImpedance" and with value of 20Ohm it's able to run longer for about one cycle, but in the end it still times out. See the full log in the spoiler Spoiler (Highlight to read) #################### Result for: ca_eye ###### Run 1 ###############################################Microsoft Windows [Version 10.0.19045.2965] (c) Microsoft Corporation. All rights reserved. C:\nxp\i.MX_CFG_25.03\bin>prompt test-prefix : test-prefix : "C:/nxp/i.MX_CFG_25.03/bin/python3/python" "C:/nxp/i.MX_CFG_25.03/bin/python3/memtool/memtool_entry.py" -t "runtest" -d "C:/ProgramData/NXP/mcu_data_25.03/processors/MIMX8ML8xxxKZ/ksdk2_0/mem_validation/ddrc" -p "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy_training_ca_eye_lpddr4_0_0_.log" -i "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/figure_ca_eye_lpddr4_0_0_.png" -l DEBUG "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.json" INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.json INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.json DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.processor.base_processor freq_0 set to 667 INFO memtool.phyinit.phy_init Run phyinit for 2020.06\lpddr4 DEBUG memtool.phyinit.phy_init Shared library C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\phyinit\sharedlib\phyinit_2020.06_lpddr4.dll DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.phyinit.phy_init PHY config file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_config_final.json DEBUG memtool.phyinit.phy_init Phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txt DEBUG memtool.phyinit.phy_init Retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txt DEBUG memtool.phyinit.out_parser Parse phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txt DEBUG memtool.phyinit.out_parser Parse retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txt DEBUG memtool.phyinit.out_parser Parse state A_BRING_UP_POWER DEBUG memtool.phyinit.out_parser Parse state C_PHY_INIT_CONFIG(210) DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x32fb to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.c DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x15d4 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.json DEBUG memtool.phyinit.out_parser Parse state LOAD_IMEM_1(445) DEBUG memtool.phyinit.out_parser Parse state D_LOAD_IMEM_1D(465) DEBUG memtool.phyinit.out_parser Write IMEM 1D as bin size 0x8000 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.bin DEBUG memtool.phyinit.out_parser Write IMEM 1D as txt size 0x6eaf3 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.txt DEBUG memtool.phyinit.out_parser Parse state PHASE.E_SET_DFI_CLOCK(16850) DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1(16869) DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1D(16885) DEBUG memtool.phyinit.out_parser Write DMEM 1D as bin size 0x67c to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.bin DEBUG memtool.phyinit.out_parser Write DMEM 1D as txt size 0x5398 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.txt DEBUG memtool.phyinit.out_parser Parse state PHASE.G_EXEC_FW(17716) DEBUG memtool.phyinit.out_parser Parse state PHASE.PHASE.I_LOAD_PIE(17782) DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x44ff to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.txt DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x933a to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.json DEBUG memtool.phyinit.out_parser Parse state PHASE.H_READ_MSG_BLOCK(18389) DEBUG memtool.phyinit.out_parser Parse retention register list INFO memtool.comm.serial_channel Using serial: COM3 DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive INFO memtool.comm.serial_channel Send reset to target DEBUG memtool.comm.serial_channel Executing: R DEBUG spsdk.utils.interfaces.device.usb_device Closing the Interface: SE Blank 865 (0x1FC9, 0x0146)path=b'\\\\?\\hid#vid_1fc9&pid_0146#6&dc7bbf3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' sn='' DEBUG memtool.comm.serial_channel ==================hardware_init======================= DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel [DEBUG]: Clock setup... DEBUG memtool.comm.serial_channel [INFO]: ARM core clock rate is 1800MHz... DEBUG memtool.comm.serial_channel [INFO]: DDR Dram frequency is 666MHz... DEBUG memtool.comm.serial_channel [DEBUG]: Clock setup ended... DEBUG memtool.comm.serial_channel ==================hardware_init exit================== DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read app state WAIT_FOR_INPUT INFO memtool.common.base_test Write app log level DEBUG memtool.comm.serial_channel Executing: Mw92F510,1:0000000a INFO memtool.common.base_test Write app state CONFIG_RECEIVED DEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:55aa55aa DEBUG test_app [DEBUG]: Initialize mailbox... DEBUG test_app [DEBUG]: Apply Init PHY Config... DEBUG test_app [DEBUG]: Execute PHY operation... DEBUG test_app [DEBUG]: Run PHY full init... DEBUG test_app [DEBUG]: Write 1D imem image, offset 0x00050000 size 0x00004000... DEBUG test_app [DEBUG]: End of load 1D imem image... DEBUG test_app [DEBUG]: Set DFI Clock for pstate 0... DEBUG test_app [DEBUG]: Write 1D dmem image, offset 0x00054000 size 0x0000033e... DEBUG test_app [DEBUG]: End of load 1D dmem image... DEBUG test_app [INFO]: Execute Training Firmware for 1D pstate0@667MHz... DEBUG test_app [INFO]: Training Firmware completed for 1D pstate0@667MHz with status 0; Execution ended in 0s.310ms.898us... DEBUG test_app [DEBUG]: PHY operation ended with status 0... DEBUG memtool.comm.serial_channel Executing: mw92F918,1 DEBUG memtool.comm.serial_channel Result: 0x00000000 DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read app state WAIT_FOR_INPUT INFO memtool.common.base_test Read phy status DEBUG memtool.comm.serial_channel Executing: mw92F91C,1 DEBUG memtool.comm.serial_channel Result: 0x00000059 INFO root Number of logged items 0x59 DEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4\lpddr4_pmu_train.strings DEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4_2d\lpddr4_2d_pmu_train.strings DEBUG memtool.comm.serial_channel Executing: mb961000,400 DEBUG memtool.comm.serial_channel Executing: mb961400,400 DEBUG memtool.comm.serial_channel Executing: mb961800,400 DEBUG memtool.comm.serial_channel Executing: mb961C00,400 DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read app state WAIT_FOR_INPUT INFO memtool.common.base_test Write input param test = 200 DEBUG memtool.comm.serial_channel Executing: Mw92EA10,1:000000c8 INFO memtool.common.base_test Write app state INPUT_RECEIVED DEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:77665544 DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1 DEBUG memtool.comm.serial_channel Result: 0x5588DCFE INFO memtool.common.base_test Read symbol app_state = 0x5588dcfe DEBUG memtool.comm.serial_channel Executing: mw92EABC,1 DEBUG memtool.comm.serial_channel Result: 0x00000001 INFO memtool.common.base_test Read symbol num_records = 0x1 INFO memtool.common.base_test App state WAIT_FOR_INPUT DEBUG memtool.comm.serial_channel Executing: mw92EF40,8 DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read symbol debug = [0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.comm.serial_channel Executing: mw92EF60,A DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read symbol err_capt_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.comm.serial_channel Executing: mw92EF88,20 DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read symbol debug_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.comm.serial_channel Executing: mw92EAC0,1 DEBUG memtool.comm.serial_channel Result: 0x00000001 INFO memtool.common.base_test Read symbol state = 1 DEBUG memtool.comm.serial_channel Executing: mw92EAC4,1 DEBUG memtool.comm.serial_channel Result: 0x000000C8 INFO memtool.common.base_test Read symbol test_id = 200 INFO memtool.common.base_test Record 0 state TestStatus.PASS DEBUG memtool.comm.serial_channel Executing: mw92EAC8,10 DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Read test data [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] INFO memtool.common.base_test Test 200 finished with state 1 DEBUG memtool.common.base_test App state: WAIT_FOR_INPUT DEBUG memtool.common.base_test Err_caption_registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.common.base_test Debug: [0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.common.base_test Debug registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] DEBUG memtool.common.base_test Results: [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}] DEBUG memtool.common.base_test Number of records: 1 DEBUG memtool.processor.base_processor freq_0 set to 667 DEBUG memtool.phyinit.phy_init PHY config file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_config_final.json DEBUG memtool.phyinit.phy_init Phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txt DEBUG memtool.phyinit.phy_init Retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txt DEBUG memtool.phyinit.out_parser Parse phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txt DEBUG memtool.phyinit.out_parser Parse retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txt DEBUG memtool.phyinit.out_parser Parse state A_BRING_UP_POWER DEBUG memtool.phyinit.out_parser Parse state C_PHY_INIT_CONFIG(210) DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x32fb to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.c DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x15d4 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.json DEBUG memtool.phyinit.out_parser Parse state LOAD_IMEM_1(445) DEBUG memtool.phyinit.out_parser Parse state D_LOAD_IMEM_1D(465) DEBUG memtool.phyinit.out_parser Write IMEM 1D as bin size 0x8000 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.bin DEBUG memtool.phyinit.out_parser Write IMEM 1D as txt size 0x6eaf3 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.txt DEBUG memtool.phyinit.out_parser Parse state PHASE.E_SET_DFI_CLOCK(16850) DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1(16869) DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1D(16885) DEBUG memtool.phyinit.out_parser Write DMEM 1D as bin size 0x67c to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.bin DEBUG memtool.phyinit.out_parser Write DMEM 1D as txt size 0x5398 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.txt DEBUG memtool.phyinit.out_parser Parse state PHASE.G_EXEC_FW(17716) DEBUG memtool.phyinit.out_parser Parse state PHASE.PHASE.I_LOAD_PIE(17782) DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x44ff to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.txt DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x933a to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.json DEBUG memtool.phyinit.out_parser Parse state PHASE.H_READ_MSG_BLOCK(18389) DEBUG memtool.phyinit.out_parser Parse retention register list DEBUG memtool.common.factories new instance -> {inst} {'app_state': 1435032830, 'num_records': 1, 'records': [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}], 'debug': '[0, 0, 0, 0, 0, 0, 0, 0]', 'err_capt_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0]', 'debug_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'} DEBUG memtool.common.factories new instance -> {inst} DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel DEBUG memtool.comm.serial_channel Channel is alive INFO memtool.comm.serial_channel Send reset to target DEBUG memtool.comm.serial_channel Executing: R ERROR libusbsio.hidapi.dev HID device 'b'\\\\?\\hid#vid_1fc9&pid_0146#6&dc7bbf3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}'' opening failed. ERROR memtool.common.base_test Application load ended with exception: Download incomplete due to configuration error! DEBUG memtool.comm.serial_channel Executing: mw92F918,1 #################### Result for: ca_eye ###### Run 1 ###############################################Microsoft Windows [Version 10.0.19045.2965](c) Microsoft Corporation. All rights reserved.C:\nxp\i.MX_CFG_25.03\bin>prompt test-prefix :test-prefix : "C:/nxp/i.MX_CFG_25.03/bin/python3/python" "C:/nxp/i.MX_CFG_25.03/bin/python3/memtool/memtool_entry.py" -t "runtest" -d "C:/ProgramData/NXP/mcu_data_25.03/processors/MIMX8ML8xxxKZ/ksdk2_0/mem_validation/ddrc" -p "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy_training_ca_eye_lpddr4_0_0_.log" -i "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/figure_ca_eye_lpddr4_0_0_.png" -l DEBUG "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.json" "C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.json"INFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/connect.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/test.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/phy.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_registers.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config.jsonINFO memtool.utils.helper *****C:/Users/vboxuser/AppData/Local/Temp/mem_validation/ddrc_config_in.jsonDEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.processor.base_processor freq_0 set to 667INFO memtool.phyinit.phy_init Run phyinit for 2020.06\lpddr4DEBUG memtool.phyinit.phy_init Shared library C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\phyinit\sharedlib\phyinit_2020.06_lpddr4.dllDEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.phyinit.phy_init PHY config file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_config_final.jsonDEBUG memtool.phyinit.phy_init Phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txtDEBUG memtool.phyinit.phy_init Retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txtDEBUG memtool.phyinit.out_parser Parse phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txtDEBUG memtool.phyinit.out_parser Parse retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txtDEBUG memtool.phyinit.out_parser Parse state A_BRING_UP_POWERDEBUG memtool.phyinit.out_parser Parse state C_PHY_INIT_CONFIG(210)DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x32fb to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.cDEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x15d4 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.jsonDEBUG memtool.phyinit.out_parser Parse state LOAD_IMEM_1(445)DEBUG memtool.phyinit.out_parser Parse state D_LOAD_IMEM_1D(465)DEBUG memtool.phyinit.out_parser Write IMEM 1D as bin size 0x8000 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.binDEBUG memtool.phyinit.out_parser Write IMEM 1D as txt size 0x6eaf3 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.txtDEBUG memtool.phyinit.out_parser Parse state PHASE.E_SET_DFI_CLOCK(16850)DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1(16869)DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1D(16885)DEBUG memtool.phyinit.out_parser Write DMEM 1D as bin size 0x67c to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.binDEBUG memtool.phyinit.out_parser Write DMEM 1D as txt size 0x5398 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.txtDEBUG memtool.phyinit.out_parser Parse state PHASE.G_EXEC_FW(17716)DEBUG memtool.phyinit.out_parser Parse state PHASE.PHASE.I_LOAD_PIE(17782)DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x44ff to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.txtDEBUG memtool.phyinit.out_parser Write PIE as txt size 0x933a to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.jsonDEBUG memtool.phyinit.out_parser Parse state PHASE.H_READ_MSG_BLOCK(18389)DEBUG memtool.phyinit.out_parser Parse retention register listINFO memtool.comm.serial_channel Using serial: COM3DEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveINFO memtool.comm.serial_channel Send reset to targetDEBUG memtool.comm.serial_channel Executing: RDEBUG spsdk.utils.interfaces.device.usb_device Closing the Interface: SE Blank 865 (0x1FC9, 0x0146)path=b'\\\\?\\hid#vid_1fc9&pid_0146#6&dc7bbf3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' sn=''DEBUG memtool.comm.serial_channel ==================hardware_init=======================DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel [DEBUG]: Clock setup...DEBUG memtool.comm.serial_channel [INFO]: ARM core clock rate is 1800MHz...DEBUG memtool.comm.serial_channel [INFO]: DDR Dram frequency is 666MHz...DEBUG memtool.comm.serial_channel [DEBUG]: Clock setup ended...DEBUG memtool.comm.serial_channel ==================hardware_init exit==================DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveDEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read app state WAIT_FOR_INPUTINFO memtool.common.base_test Write app log levelDEBUG memtool.comm.serial_channel Executing: Mw92F510,1:0000000aINFO memtool.common.base_test Write app state CONFIG_RECEIVEDDEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:55aa55aaDEBUG test_app [DEBUG]: Initialize mailbox...DEBUG test_app [DEBUG]: Apply Init PHY Config...DEBUG test_app [DEBUG]: Execute PHY operation...DEBUG test_app [DEBUG]: Run PHY full init...DEBUG test_app [DEBUG]: Write 1D imem image, offset 0x00050000 size 0x00004000...DEBUG test_app [DEBUG]: End of load 1D imem image...DEBUG test_app [DEBUG]: Set DFI Clock for pstate 0...DEBUG test_app [DEBUG]: Write 1D dmem image, offset 0x00054000 size 0x0000033e...DEBUG test_app [DEBUG]: End of load 1D dmem image...DEBUG test_app [INFO]: Execute Training Firmware for 1D [email protected] test_app [INFO]: Training Firmware completed for 1D pstate0@667MHz with status 0; Execution ended in 0s.310ms.898us...DEBUG test_app [DEBUG]: PHY operation ended with status 0...DEBUG memtool.comm.serial_channel Executing: mw92F918,1DEBUG memtool.comm.serial_channel Result: 0x00000000DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveDEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read app state WAIT_FOR_INPUTINFO memtool.common.base_test Read phy statusDEBUG memtool.comm.serial_channel Executing: mw92F91C,1DEBUG memtool.comm.serial_channel Result: 0x00000059INFO root Number of logged items 0x59DEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4\lpddr4_pmu_train.stringsDEBUG memtool.memtests.snps_phy Using messages file C:\ProgramData\NXP\mcu_data_25.03\processors\MIMX8ML8xxxKZ\ksdk2_0\mem_validation\ddrc\firmware\2020.06\lpddr4_2d\lpddr4_2d_pmu_train.stringsDEBUG memtool.comm.serial_channel Executing: mb961000,400DEBUG memtool.comm.serial_channel Executing: mb961400,400DEBUG memtool.comm.serial_channel Executing: mb961800,400DEBUG memtool.comm.serial_channel Executing: mb961C00,400DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveDEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read app state WAIT_FOR_INPUTINFO memtool.common.base_test Write input param test = 200DEBUG memtool.comm.serial_channel Executing: Mw92EA10,1:000000c8INFO memtool.common.base_test Write app state INPUT_RECEIVEDDEBUG memtool.comm.serial_channel Executing: Mw92EAB8,1:77665544DEBUG memtool.comm.serial_channel Executing: mw92EAB8,1DEBUG memtool.comm.serial_channel Result: 0x5588DCFEINFO memtool.common.base_test Read symbol app_state = 0x5588dcfeDEBUG memtool.comm.serial_channel Executing: mw92EABC,1DEBUG memtool.comm.serial_channel Result: 0x00000001INFO memtool.common.base_test Read symbol num_records = 0x1INFO memtool.common.base_test App state WAIT_FOR_INPUTDEBUG memtool.comm.serial_channel Executing: mw92EF40,8DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read symbol debug = [0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.comm.serial_channel Executing: mw92EF60,ADEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read symbol err_capt_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.comm.serial_channel Executing: mw92EF88,20DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read symbol debug_regs = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.comm.serial_channel Executing: mw92EAC0,1DEBUG memtool.comm.serial_channel Result: 0x00000001INFO memtool.common.base_test Read symbol state = 1DEBUG memtool.comm.serial_channel Executing: mw92EAC4,1DEBUG memtool.comm.serial_channel Result: 0x000000C8INFO memtool.common.base_test Read symbol test_id = 200INFO memtool.common.base_test Record 0 state TestStatus.PASSDEBUG memtool.comm.serial_channel Executing: mw92EAC8,10DEBUG memtool.comm.serial_channel Result: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Read test data [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]INFO memtool.common.base_test Test 200 finished with state 1DEBUG memtool.common.base_test App state: WAIT_FOR_INPUTDEBUG memtool.common.base_test Err_caption_registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.common.base_test Debug: [0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.common.base_test Debug registers: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]DEBUG memtool.common.base_test Results: [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}]DEBUG memtool.common.base_test Number of records: 1DEBUG memtool.processor.base_processor freq_0 set to 667DEBUG memtool.phyinit.phy_init PHY config file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_config_final.jsonDEBUG memtool.phyinit.phy_init Phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txtDEBUG memtool.phyinit.phy_init Retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txtDEBUG memtool.phyinit.out_parser Parse phyinit output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d.txtDEBUG memtool.phyinit.out_parser Parse retention output file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_training_out_1d2d_retention.txtDEBUG memtool.phyinit.out_parser Parse state A_BRING_UP_POWERDEBUG memtool.phyinit.out_parser Parse state C_PHY_INIT_CONFIG(210)DEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x32fb to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.cDEBUG memtool.phyinit.out_parser Write PHY CONFIG as txt size 0x15d4 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\phy_init.jsonDEBUG memtool.phyinit.out_parser Parse state LOAD_IMEM_1(445)DEBUG memtool.phyinit.out_parser Parse state D_LOAD_IMEM_1D(465)DEBUG memtool.phyinit.out_parser Write IMEM 1D as bin size 0x8000 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.binDEBUG memtool.phyinit.out_parser Write IMEM 1D as txt size 0x6eaf3 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\imem_1d.txtDEBUG memtool.phyinit.out_parser Parse state PHASE.E_SET_DFI_CLOCK(16850)DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1(16869)DEBUG memtool.phyinit.out_parser Parse state PHASE.F_LOAD_DMEM_1D(16885)DEBUG memtool.phyinit.out_parser Write DMEM 1D as bin size 0x67c to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.binDEBUG memtool.phyinit.out_parser Write DMEM 1D as txt size 0x5398 to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\dmem_1d.txtDEBUG memtool.phyinit.out_parser Parse state PHASE.G_EXEC_FW(17716)DEBUG memtool.phyinit.out_parser Parse state PHASE.PHASE.I_LOAD_PIE(17782)DEBUG memtool.phyinit.out_parser Write PIE as txt size 0x44ff to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.txtDEBUG memtool.phyinit.out_parser Write PIE as txt size 0x933a to file C:\Users\vboxuser\AppData\Local\Temp\mem_validation\pie.jsonDEBUG memtool.phyinit.out_parser Parse state PHASE.H_READ_MSG_BLOCK(18389)DEBUG memtool.phyinit.out_parser Parse retention register listDEBUG memtool.common.factories new instance -> {inst}{'app_state': 1435032830, 'num_records': 1, 'records': [{'state': 1, 'test_id': 200, 'data': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}], 'debug': '[0, 0, 0, 0, 0, 0, 0, 0]', 'err_capt_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0]', 'debug_regs': '[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]'}DEBUG memtool.common.factories new instance -> {inst}DEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channelDEBUG memtool.comm.serial_channel Channel is aliveINFO memtool.comm.serial_channel Send reset to targetDEBUG memtool.comm.serial_channel Executing: RERROR libusbsio.hidapi.dev HID device 'b'\\\\?\\hid#vid_1fc9&pid_0146#6&dc7bbf3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}'' opening failed.ERROR memtool.common.base_test Application load ended with exception: Download incomplete due to configuration error!DEBUG memtool.comm.serial_channel Executing: mw92F918,1 Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Hi Jorge, 1. Could you please provide the data on the chain lengths and propagation delays of LpDDR signals in EVK? 2. Our CAD does not allow importing the EVK pcb file in the format it is posted on your site. Can you provide it in ASCII format? Best regards, Serge Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Hello, Your DDR connection is ok. There is no functional problem in swap CA/CB since dual channel device channels are independent in LPDDR4, just keep in mind that bit swapping within each slice/byte lane is OK. Byte swapping is NOT allowed. If you still having signal integrity tests failed, please look for layout issues and try lower operating frequencies. You could try to change the tunning with different settings and check if helps with your design: ODTImpedance Desired ODT impedance in Ohm. Valid values for DDR4=240,120,80,60,40. Valid values for DDR3L=high-impedance,120,60,40. Valid values for LPDDR4=240,120,80,60,40 TxImpedance Write Driver Impedance for DQ/DQS in ohm (Valid values for all DDR type= 240, 120, 80, 60, 48, 40, 34) ATxImpedance Write Driver Impedance for Address/Command (AC) bus in ohm (Valid values for all DDR type = 120, 60, 40, 30, 24, 20) Best regards. Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Hello @JorgeCas ! I am Alexander's colleague. Attached is the CPU and LPDDR connection diagram. Best regards, Serge Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Hello, Could you please share the connections of memory to i.MX device? Best regards. Re: i.MX8MP LPDDR4 CA Training Failed (without it stress test is ok for single freq point) Dear JorgeCas! Happy New Year! We made a new board and ran the memory at 1600 MHz. It doesn't run at higher speeds—we'll investigate this problem.. I compared the net lengths in the KIT in your picture with our calculations in EDA. 1. In the KIT, when calculating net lengths and delays, you didn't take the via lengths into account. 2. In the KIT, when calculating the CK_x_x signal path lengths, the additional sections to the resistors (R9, R10) were incorrectly added to calculated. Please comment on the KIT chain lengths highlighted in red. Best regards, Serge
View full article
LPSPI3 経由で FS26 を駆動するにはどうすればいいですか? 開発にはS32K3X4EVB-T172を使用しています。 LPSPI3 を使用して FS26 と通信できないことがわかったので、サンプル コードでこの状況を再現しました。 交換したい LPSPI3_PCS0 = 110 = PTB17 <> LPSPI0_PCS0 = 95 = PTB0 LPSPI3_SCK = 7 = PTD1 <> LPSPI3_SCK = 7 = PTD1 LPSPI3_SIN = 111 = PTD20 <> LPSPI0_SIN = 97 = PTC9 LPSPI3_SOUT = 8 = PTD0 <> LPSPI0_SOUT = 94 = PTB1 配線方法は以下の通りです。 LPSPI3_SCK = J37、番号1、LPSPI0_SCK = J2、番号21に接続 LPSPI3_SIN = J39、番号14、LPSPI0_SIN = J2、番号15に接続 LPSPI3_SOUT = J37、番号3、LPSPI0_SOUT = J2、番号18に接続 LPSPI3_PCS0 = J4、番号5、LPSPI0_PCS0 = J2、番号24に接続 既知の障害点は、Sbc_fs26_InitDevice 内の Sbc_fs26_GetDeviceState が FS_STATES_INVALID を返すことです。 ただし、Spi_SyncTransmit を使用すると、CSB が低く引き下げられることがわかります。これは正しいようです。 CSB MOSI 設定を確認しましたが、どこに問題があるのかわかりません。添付ファイルは、LPSPI0 が LPSPI3 に変更されていることを除いて、サンプル コードとほぼ同じです。 Re: How to drive FS26 via LPSPI3? 公式の例では、FS26 と通信するためにどの SPI を使用していますか? Re: How to drive FS26 via LPSPI3? LPSPI0の使用 LPSPI0を削除してから以下のドッキングを実行しました。 LPSPI0_PCS0 = 95 = PTB0 = J2 (上位24) LPSPI3_PCS0 = 110 = PTB17 = J4 (下位5) LPSPI0_SCK = 98 = PTC8 = J2 LPSPI3_SCK = 7 = PTD1 = J37 LPSPI3_SCK = 7 = PTD1 = J37 LPSPI0_SIN = 97 = PTC9 = J2 (上位15) LPSPI3_SIN = 111 = PTD20 = J39 (中間14) LPSPI0_SOUT = 94 = PTB1 = J2 (LPSPI3_SOUT = 8 = PTD0 = J37 に接続) ただし、FS26は通信できません。 Re: How to drive FS26 via LPSPI3? これはコード移植の問題ではありません。非常に大きなコードパッケージがあり、LPSPI3がFS26と通信できないという問題が発生しています。質問しやすいように、FS26のサンプルコードを使用し、FS26との通信をLPSPI0からLPSPI3に変更しました。しかし、LPSPI3がFS26と通信できないという同じ問題が依然として発生しています。Spi_SyncTransmitを呼び出すと、CSBとMOSIに対応する応答が表示されます。そのため、原因がわかりません。 Re: How to drive FS26 via LPSPI3? 使用 LPSPI0 LPSPI0_PCS0 = 95 = PTB0 LPSPI0_SCK = 98 = PTC8 LPSPI0_SIN = 97 = PTC9 LPSPI0_SOUT = 94 = PTB1 Re: How to drive FS26 via LPSPI3? クリスマス休暇期間中は、サポートの応答時間は通常より長くなる場合がありますのでご了承ください。ご理解のほどよろしくお願いいたします。 私が見た説明は、私が行っている RTD 上での SPI 通信転送であり、サポートを超える点があります。
View full article
S32K310 SRAM overflowed S32K3 AUTOMOTIVE-RTD  This week, when I was building the peripherals for an S32K310 project in my IDE, it reported an SRAM overflow error.   But, my project is brand new, and the main function is empty. There is no application code at all; I have only configured the necessary peripherals for my MCU. I checked the demo_310.map file to determine what was causing the excessive memory usage. I found that one of the files within the RTD package is taking up a significant amount of SRAM space. The SRAM address range for K310 is from 0×20400000 to 0×20404000, but the address allocation has now reached 0x20404200. The RTD/src/SchM_Gpt file alone occupies more than 2KB of space. Knowing that the external SRAM space for the S32K310 MCU is only 16KB, I believe there must be some issues within the RTD package. I opened the corresponding file and found the issue shown in the figure below. As shown in the figure, in the file, the length of the variable definition is set to 4 . I understand that this was prepared for multi-core systems. However, in my current project using S32K310, which has only one core, the RTD package still sets the number of cores to 4. This results in the space occupied by variables being expanded by a factor of four. After adjusting the core number configuration and rebuild the project, I can see that the space occupied by RTD/src/SchM_Gpt has decreased from 0x860 to 0x218, which is quite significant. So, please explain why a single-core device like the S32K310 still sets the number of cores to 4. Is this a bug? The version I am using is as follows: S32S32 Design Studio for  S32 Platform 3.6.2 S32K3_RTD_6_0_0_D2506_ASR_REL_4_7_REV_0000_20250610 I have also uploaded my project files in the attachment for your confirmation. I look forward to your reply very much because this is important to me. Thank you. Re: S32K310 SRAM overflowed Hi@khty I have reported this issue to the RTD design team, and it will take some time to get a response. Re: S32K310 SRAM overflowed Hi@khty I received a reply from the design team, and they confirmed that this is a bug. For now, you can manually change the number of cores to 1. I will notify you again when there is an official workaround or version fix.
View full article
在 i.MX7ULP 上使用篡改引脚 我在内核中启用了 SECVIO,以便使用 i.MX7ULP 上的篡改引脚处理篡改事件。 我是否还需要修改设备树 (DTS) 或 U-Boot 中的任何内容才能正确配置和检测篡改引脚? 此外,是否有任何可访问的示例或应用程序来演示如何在用户空间使用篡改处理程序? i.MX 7ULP 安全 Re: Using Tamper Pin on i.MX7ULP 你好 要在 i.MX7ULP 上进行正确的防盗引脚配置和检测:1. 设备树配置:当内核中已启用 SECVIO 时, 您不一定需要专门针对篡改功能修改设备树 (DTS)。篡改引脚通常由 SNVS(安全非易失性存储)模块及其驱动程序处理,而不是通过设备树中的标准 GPIO 配置进行处理。 2. U-Boot 配置: 如果你还打算在 U-Boot 中使用篡改检测,则需要在 U-Boot defconfig 中添加 "CONFIG_IMX_TAMPER=y" 并进行重建。 3. 用户空间中的篡改处理程序: 对于用户空间应用,没有专门针对 i.MX7ULP 的标准化示例应用。不过,您可以调整类似平台(如 i.MX6UL 或 i.MX7D)的实现,因为这些平台的篡改机制基本相似。 有关实施指南,请参阅: -i.MX7 参考手册中的第 3.1.4.2 节(篡改检测) -应用笔记 " i.mx7dsabresd " (AN12210.pdf) 的篡改应用程序 内核中的 SECVIO 驱动程序应处理篡改事件,并且可以配置为在检测到篡改时触发信号相应的网络安全措施。您可以通过 SNVS_LP 状态寄存器 (LPSR) 监测这些事件,并通过 SNVS_LP 防篡改探测器配置寄存器 (LPTDCR) 对其进行管理。 此致
View full article
SCST Lib 测试错误 队员们好 如 所述,在 m7_scst_execute_core_tests 之前调用 MPU_config()。在调试模式下,我发现签名的值不正确(库中的值是 0x2F6AB216U)。但在运行模式下(不使用调试器)是正确的。 我觉得很奇怪。这正常吗? 顺祝商祺! 陈 Re: SCST Lib test error 你好 我认为这是意料之中的行为,因为调试器会影响已测试的部分。 不过,我已经向 SCST 团队提出了这个问题,以确认/解释这种行为。 我会尽快反馈给您。 顺祝商祺! Peter Re: SCST Lib test error 你好 以下是 SCST 团队的反馈意见: 我想这在邮件主题中已经回答过了,最有可能的是在 Trace32 中,它被设置为捕获异常(BusFault、Hardfault),因此需要将其删除,以便 SCST 能正确捕获这些异常。 Trace32 命令"tronchip" 可用于此。 顺祝商祺! Peter
View full article
IMXRT1140-EVK 上の USB ホスト IMXRT1140-EVK に USB ホストが必要です。USB HOST CDC サンプルをインストールしましたが、USB OTG PWR には、コネクテッドデバイスに電力を供給するための 5V がないことに気付きました。何か設定が足りないのでしょうか、アドバイスをお願いします。 私のデバイスは、USB ホストにデータを送信する CDC ACM vcom デバイスです。 Re: USB Host on IMXRT1140-EVK @JACOBTHOMAS_007 この質問については、次の MIMXRT1040-EVKUM を参照してください。 J40(3-4): J48経由の5V_USB_OTG電源 J40(1-2): J45経由の5V_SYS電源 Re: USB Host on IMXRT1140-EVK 迅速な返信ありがとうございます。 ジャンパーを J40 (1-2) と (3-4) にコネクテッドした後、OTG からの出力電圧は 1.2V のみになります。このポートにコネクテッドされたデバイスを駆動するには、出力が 5V になる必要があると予想しました。 参考までに写真をご覧ください   Re: USB Host on IMXRT1140-EVK こんにちは@Sam_Gao、このトピックについて何か更新はありますか?どういうわけか、USB VBUS ピンには 1.2V しか表示されません。 Re: USB Host on IMXRT1140-EVK @JACOBTHOMAS_007 「このポートにコネクテッドされたデバイスを駆動するには、出力が 5V である必要があると予想しました。」 --> USB ポートをマスターとして使用して、スレーブ デバイスに電力を供給したいと考えていましたか? MIMXRT1040-EVKUMの表11を次のように参照してください。 USBコネクタJ48を介した外部ソース(コネクタがホストモードで動作している場合)または電源スイッチU30を介した5V_SYS電源(コネクタがデバイスモードで動作している場合) SO、USBポートをマスター/ホストとして使用する場合は、手順を順に確認してください。 1. 5V_SYSは動作可能です: SW6 + J45 + J40(1-2のみ😞J45 経由の 5V_SYS 電源。 2. ホスト モード (ID = GND) で動作させます。 Re: USB Host on IMXRT1140-EVK サム・ガオ ありがとうございます。USB VBUS を +5V にできるようになりましたが、一方で USB デバイスを EVK otg ポートに接続しても、デバイスを検出できません。また何かが欠けているようです。 Re: USB Host on IMXRT1140-EVK @Sam_Gaoありがとう、うまくいきました!
View full article
后台调试模式驱动代码包 CPU16/32 培训人员/开发人员,你们好、 我和我的学生一起开始了一个项目,用 Arduino IDE 设计一个 BDM 接口 (USB-> BDM),以(简单)监测 Wurz 的 SBC EC376。我们找到了文档 AN1230/D,但找不到第 5 页上叫的 "BDM 软件包" (BDMVx-y.ZIP)。 您能帮助我们吗? 谢谢并致以问候... 维纳德-奈斯 Re: Background Debugging Mode Driver Package 你好@Wijnand、 谢谢您的帖子。AN1230 太旧了,我找不到相关的 BDM 软件包。 虽然我找到了以下链接供你参考,其中提供了 BDM 驱动程序和相关信息。 这不是恩智浦(摩托罗拉)官方版本的私人博客。 BDM Interface for Motorola 683xx MCU\ 使用 GDB 调试器 希望对您有所帮助。 BR 西莱斯特 ----------------------------------------------------------------------------------------------------------------- 注:如果本帖回答了您的问题,请点击"ACCEPT AS SOLUTION" 按钮。Thank you! ----------------------------------------------------------------------------------------------------------------- Re: Background Debugging Mode Driver Package 你好,塞莱斯特、 感谢您的努力。我们将探讨部分资源(BDM 元器件)是否对我们的项目有用。我们的目标是设计一个简单的监控程序,例如用于向目标上传 s 记录。 敬上,Wijnand... Re: Background Debugging Mode Driver Package 你好,塞莱斯特、 感谢您的努力。我们将探讨部分资源(BDM 元器件)是否对我们的项目有用。我们的目标是设计一个简单的监控程序,例如用于向目标上传 s 记录。 敬上,Wijnand... Re: Background Debugging Mode Driver Package 你好 Wijnand, AN1230 文件可以在这里找到: http://archive.retro.co.za/archive/computers/Motorola/freeware.aus.sps.mot.com/mcu332/BDM-V090.ZIP 我在找板附带的软盘上的文件(" ec376 软件包 "/“ec376 SWP”)和其他随附文档。如果有任何问题,请告诉我。 谢谢。
View full article
加载配置和在 CLI 中构建失败 大家好,又是我, 我在使用命令行加载配置和构建项目时遇到了问题。我的电脑是 Windows 11。 以下是我的命令: 加载配置: $env:BASE_PLATFORMSDK_S32K3 = 'C:\NXP\S32DS.3.6.4\S32DS\software\PlatformSDK_S32K3' .\s32dsc.exe -noSplash -application com.nxp.swtools.framework.application --launcher.ini .\s32ds.ini -data 'C:\Users\guest\Desktop\tmp' -sdkPath 'C:\NXP\S32DS.3.6.4\S32DS\software\PlatformSDK_S32K3'.-载入 "C:\Users\guest\Desktop\tmp\my_project\my_project.mex-exportAll 'C:\Users\guest\Desktop\tmp\my_project' 版本 代码包: .\s32dsc.exe -noSplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild--launcher.ini .\s32ds.ini -data 'C:\Users\guest\Desktop\tmp' -cleanBuild my_project 我在构建过程中遇到了错误,致命错误:Stm_Ip.h:No such file or directory. 在检查加载配置过程时,我收到了这样的警告,严重警告:错误的 SDK 安装位置首选项: .使用共享位置! 现在我假设这与我的 SDK 路径有关,但正如你所看到的,我已经使用了 -sdkPath 命令,但仍然出现了错误。 我是不是漏掉了什么?谢谢 Re: Load Config and Building in CLI failed 你好@nairaca04 能否请您分享一下您所遵循的所有步骤,包括执行的任何命令和应用的配置?这将有助于我们更好地了解流程,并确定问题可能出在哪里。 此外,我们建议参考 S32 Design Studio 命令行界面的官方文档,因为其中提供了通过命令行加载配置和构建项目的详细说明和最佳实践。 您可以在以下地点找到这一资源: C:\NXP\S32DS.3.6.4\S32DS\help\resources\howto\HOWTO_S32_Design_Studio_Command_Line_Interface.pdf BR、VaneB Re: Load Config and Building in CLI failed 你好@nairaca04 根据您分享的步骤,您似乎没有使用 S32 配置工具从 .mex 生成代码。文件或更新了代码以及所有元器件依赖关系。有关详细说明和特定命令,请导航至顶部菜单栏并选择帮助 → 帮助内容,然后搜索"命令行执行 - 项目工作" 。 Re: Load Config and Building in CLI failed 你好@VaneB、 感谢您的回复,抱歉这么久才回复。 我查看了 pdf 文件,其中大部分说明都是关于创建项目或构建项目的。我想进一步检查 mex 文件的加载情况。 此外,以下是我按顺序使用的命令: 导入项目: .\s32dsc.exe -noSplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild--launcher.ini.s32ds.ini--data'C:\Users\guest\Desktop\tmp'--import'C:\Users\guest\Desktop\tmp\my_project'。 加载配置 (.mex) 文件: .\s32dsc.exe -noSplash -application com.nxp.swtools.framework.application --launcher.ini .\s32ds.ini -data 'C:\Users\guest\Desktop\tmp' -MCU S32K358 -SDKVersion PlatformSDK_S32K3 -Load 'C:\Users\guest\Desktop\tmp\my_project\my_project.mex'.-ExportAll'C:\Users\guest\Desktop\tmp\my_project'(导出所有项目 编译项目: .\s32dsc.exe -noSplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild--launcher.ini .\s32ds.ini -data 'C:\Users\guest\Desktop\tmp' -cleanBuild my_project/Debug_FLASH 我更新了 "加载配置 ",成功删除了警告信息: 严重:找不到任何 SDK SEVERE:错误的 SDK 安装位置首选项: .使用共享位置! 但是,我在版本中还是遇到了同样的错误:致命错误:stm_ip.h:没有这样的文件或目录。 我注意到的一点是,在 CLI 中,它不会生成 RTD 和堆栈文件夹,而在图形用户界面中,这些文件夹会自动创建。 Re: Load Config and Building in CLI failed 你好@VaneB、 感谢您之前的建议,我已经根据帮助内容更新了我的流程。 现在我又遇到了一个新问题:RTD RTD 可以成功导入,但 堆栈 却无法导入,进程卡在命令行,毫无进展。 信息:Peripherals:源文件已更新: generate\include\Port_PBcfg.h、generate\include\Gmac_Ip_Cfg.h、generate\include\Gmac_Ip_Device_Registers.h、generate\include\Power_Ip_PBcfg.h、generate\include\Power_Ip_Cfg_Defines.h、generate\include\modules.h, generate\src\FlexCAN_Ip_Sa_PBcfg.c、generate\src\Stm_Ip_SA_PBcfg.c、generate\include\Gmac_Ip_Features.h、板\ siul2_port_IP_CFG.H,生成\ include\ mpu_m7_IP_CFG.H,generate\include\Platform_CfgDefines.h、generate\include\FreeRTOSConfig.h、generate\include\DeviceDefinition.h、board\ siul2_port_IP_CFG.C,生成\ src\ port_pbcfg.C,生成\ include\ flexcan_IP_CFGDefines.H,generate\include\Ram_Ip_Cfg_Defines.h、generate\include\Stm_Ip_Cfg_Defines.h、generate\include\Gmac_Ip_PBcfg.h、generate\include\Tspc_Port_Ip_PBcfg.h、generate\src\Mcu_Cfg.c, generate\include\System_Ip_Cfg.h、generate\include\Platform_Cfg.h、generate\src\Platform_Ipw_Cfg.c、generate\include\Power_Ip_Cfg.h、generate\src\Eth_43_GMAC_Ipw_PBcfg.c、generate\include/Clock_Ip_PBcfg.h、生成 Dec 16, 2025 3:14:55 PM com.nxp.swtools.utils.scripting.ScriptDependencyHelper addDependency 警告: [DATA] 依赖源(来自 javascript)包含 .作为分隔符,而不是 :Pins.PortContainer_0_BOARD_InitPeripherals Dec 16, 2025 3:14:56 PM com.nxp.swtools.utils.scripting.ScriptDependencyHelper addDependency 警告: [DATA] 依赖源(来自 javascript)包含 .作为分隔符,而不是 :Pins.PortContainer_0_BOARD_InitPeripherals Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logWarning 警告: [Lcom.nxp.swtools.resourcetables.model.config.IComponentInstanceConfig;@aae360c Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo 信息:构造函数未定义 Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO:类名 BaseToolchainSettings Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO:构造函数 ConfigSet:[编号:BaseNXP] Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO:TypeError: settingsClass.applyToolchainSettings 不是函数 Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo 信息:构造函数未定义 Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO:类名 FreeRtosToolchainSettings Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO:构造函数 ConfigSet:[Id: freertos_driver] Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO: 应用工具链设置 Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo 信息:构造函数未定义 Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO:类名 TcpipToolchainSettings Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO:构造函数 ConfigSet:[标识符:tcpip_cfg] Dec 16, 2025 3:14:57 PM com.nxp.swtools.utils.scripting.internal.ScriptApi logInfo INFO: applyToolchainSettings 这是我更新的序列: 导入项目: .\s32dsc.exe -noSplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild--launcher.ini.s32ds.ini--data'C:\Users\guest\Desktop\tmp'--import'C:\Users\guest\Desktop\tmp\my_project'。 加载配置 (.mex) 文件: .\s32dsc.exe -noSplash -application com.nxp.swtools.framework.application --launcher.ini .\s32ds.ini -data 'C:\Users\guest\Desktop\tmp' -MCU S32K358 -SDKVersion PlatformSDK_S32K3 -Load 'C:\Users\guest\Desktop\tmp\my_project\my_project.mex'.-ExportAll'C:\Users\guest\Desktop\tmp\my_project'(导出所有项目 更新代码: .\s32dsc.exe -noSplash -application com.nxp.swtools.framework.application -launcher.ini .\s32ds.ini -HeadlessTool Peripherals -importProject C:\Users\guest\Desktop\tmp\my_project -sdkPath C:\NXP\S32DS.3.6.4\S32DS\software\PlatformSDK_S32K3 -data 'C:\Users\guest\Desktop\tmp 编译项目: .\s32dsc.exe -noSplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild--launcher.ini .\s32ds.ini -data 'C:\Users\guest\Desktop\tmp' -cleanBuild my_project/Debug_FLASH Re: Load Config and Building in CLI failed 你好@nairaca04 你能分享一下你正在使用的软件包以及版本详细信息吗?另外,你能不能提供你的 .mex文件?我想排除任何与您的设置或配置有关的问题。 如果您不希望在社区中共享此信息,请提交支持票据。 最后,您在建造项目时等待了多久?有时版本过程可能需要一段时间。
View full article
[乱用] 投稿者: @JohnKlug / ボード: imx-プロセッサ / 報告者: ovgfjhx ovgfjhx は、 @JohnKlug が投稿した 「Could not invoke dnf for external kernel module in Yocto kirkstone」という 投稿について、以下の理由で報告しました: 理由:ヌードまたは性行為 詳細: 投稿リンク: https://community.nxp.com/t5/i-MX-Processors/Could-not-invoke-dnf-for-external-kernel-module-in-Yocto/mp/1627964#M203740 投稿者: @JohnKlug |メール著者 報告者: ovgfjhx |メールレポーター 報告された投稿には 2 件の返信があります。
View full article
无法验证 S32M244-CTL 寄存器读取失败时的 GDU 安全状态 在初始化过程中,我们需要将 S32M244 的栅极驱动单元 (GDU) 置于安全状态。我们遵循的顺序是 1. 读取 CTL 寄存器。 2. 3. 再次读取以确认写入。 问题 1: 使用 API 时:Ae_ReadRegister((uint32)(&(IP_GDU_AE->CTL)), AEC_DATAWIDTH_16,&u32RegValGDU_Pre); 读取操作失败,返回状态 0x01。 (注:IP_GDU_AE_BASE 地址为 0x180,IP_GDU_AE->CTL 为 0x186) 问题 2: 在读取失败后,我们尝试使用以下方法进行写入:Aec_Ip_SpiWrite((uint32)(&(IP_GDU_AE->CTL)), AEC_DATAWIDTH_16, 0x0040U); 该写操作返回状态 0x00(成功)。 然而 1.我们无法确认 GDU 是否处于安全状态。 2.随后使用相同 API 的读取仍然失败,无法反映写入的值。 问题 1。在读取/写入 AE/GDU 寄存器之前,是否有任何先决条件(功率域启用、解锁顺序、定时)? 2。我们如何验证 GDU 处于安全状态?是否有需要检查的特定位或状态寄存器? 3. 读操作是否有与写操作不同的 SPI 框架或协议要求? 请求(紧急) 请提供以下方面的指导: 1.解决读取失败问题。 2. 向 CTL 寄存器写入后确认安全状态的建议方法。 Re: Unable to Verify GDU Safe State on S32M244—CTL Register Read Failure 你好 如果要写入 GDU 寄存器,首先需要配置 SPI(可能已经配置)、初始化应用扩展,并在应用扩展 RSTGEN_CFG 寄存器第 4 位启用 GDU。 建议您从我们的电机控制示例中寻找灵感: 在这里,您可以找到应用程序扩展如何与 GDU 一起初始化: 一旦初始化完成,就可以将 GDU 置入或移出安全状态,RTD 中有相关的应用程序接口。 您可以使用该简短代码为例,读取/验证 GDU CTL 寄存器的内容: 如果要手动写入 GDU 的 CTL 寄存器,则必须先读取 CTL 寄存器的内容,然后"OR" 与 0x40 相加,再将结果值写回 CTL 寄存器,因为 CTL 寄存器的某些位只能在 GDU 处于配置模式时更改,否则会出错。 也许测试 GDU 是否安全启动的最简单方法就是配置寄存器 SUPCFG,使低端晶体管在 GDU 安全启动时开启,下面是一个如何配置这种验证的示例: 顺祝商祺! Peter Re: Unable to Verify GDU Safe State on S32M244—CTL Register Read Failure #NXPCommunity, #NXPTechSupport, #GateDriverUnit : 非常感谢您的紧急援助。 Re: Unable to Verify GDU Safe State on S32M244—CTL Register Read Failure 你好 您的电机控制库标头丢失了。这些 three-gflib.h、gmclib.h、和 gdflib.h-aren't它们来自恩智浦的汽车数学& 电机控制库 (AMMCLib)。S32M24x PMSM FOC 示例需要在计算机上安装 AMMCLib,并将其添加到项目的 include/lib 路径中。 为什么会丢失这些文件 示例 S32M24xEVB_PMSM_FOC_1Sh 使用 AMMCLib 块(GFLIB、GMCLIB、GDFLIB 等)。如果没有安装 AMMCLib for S32M24x,或者项目没有配置为指向 AMMCLib,编译器就无法找到这些头文件。 (e.g., C:\NXP\AMMCLIB\S32M24x_AMMCLIB_v1.1.38) 为 S32M24x 安装 AMMCLib 从 NXP 下载/安装用于 S32M24x 的汽车数学和电机控制库 (AMMCLib)。安装完成后,您应该有一个类似的文件夹: C:\NXP\AMMCLIB\S32M24x_AMMCLIB_vX.Y.Z\ 包含头文件和预编译库文件 在 S32 Design Studio 中添加包含路径和库路径。 顺祝商祺! Peter   Re: Unable to Verify GDU Safe State on S32M244—CTL Register Read Failure 你好@petervlna, 通过应用所需的寄存器配置序列,我遇到的问题已成功解决。具体来说,设置 AEC_AE_RSTGEN_CFG_ADDR = 0x0010 可启用 GDU 模块。完成该序列后,系统运行符合预期,未再发现任何错误。 我使用了以下代码,供您参考: /* RSTGEN_CFG = 0x10 */ Retval_GDU_Write = Ae_WriteRegister((uint32)((AEC_AE_RSTGEN_CFG_ADDR)), AE_DATAWIDTH_16, 0x0010U); /* 设置 SSTEN 位之前读取 GDU 控制(CTL)寄存器 */ Retval_GDU_Read = Ae_ReadRegister((uint32)&(IP_GDU_AE->CTL), AE_DATAWIDTH_16,&u32RegValGDU); /* 在 GDU CTL 寄存器中写入/设置 SSTEN 位。*/ Retval_GDU_Write = Ae_WriteRegister((uint32)(&(IP_GDU_AE->CTL)), AE_DATAWIDTH_16, 0x0040U); /* 设置 SSTEN 位后读取 GDU 控制(CTL)寄存器 */ Retval_GDU_Read = Ae_ReadRegister((uint32)&(IP_GDU_AE->CTL), AE_DATAWIDTH_16,&u32RegValGDU); 感谢您的支持。 问候, Mayuresh Re: Unable to Verify GDU Safe State on S32M244—CTL Register Read Failure 我正在使用您建议的示例: Path:C:/NXP/MC_DevKits/S32M24xEVB/sw/S32M24xEVB_PMSM_FOC_1Sh/ 在解压缩项目并尝试编译后,我看到电机控制头文件的致命包含错误: C:/NXP/MC_DevKits/S32M24xEVB/sw/S32M24xEVB_PMSM_FOC_1Sh/src/actuate_s32m.h:48:10: 致命错误:gflib.h:无此文件或目录 报告丢失的文件有: #include"gflib.h" #include"gmclib.h" #include"gdflib.h" 我搜索了整个项目,但在任何地方都找不到这些标头。您能告诉我们如何解决这个问题吗? 具体为: gflib.h. 应放在何处?gmclib.h、和 gdflib.h从何而来? 它们是需要单独安装的恩智浦电机控制库/SDK 的一部分吗? 故障排除 我已经尝试过: * 验证项目的包含路径,并在工作区中搜索丢失的头文件。 * 在典型的恩智浦 SDK 文件夹(如 C:/NXP/.../SDK/、.../MC_DevKits/、.../MotorControlLib/)下查找,但未找到 gflib.h、gmclib.h、gdflib.h. * 确认了示例的提取;没有任何文件被损坏或排除。 如果能提供有关要安装的正确库/软件包以及配置路径的指导,我们将不胜感激。 谢谢, Mayuresh Rangole
View full article
CBTL04083A 用于切换单端 1.8V GPIO/UART 大家好 我知道 CBTL04083A 是专为高速差分信号开关而设计的,而且有很多专门用于 GPIO/UART 开关的好产品。但是,我们目前需要使用 CBTL04083A 版本一个兼容差分信号和单端低速 1.8 V I/O(GPIO 和 UART)的 MUX 模块。差分 PCB 布局将在本模块之外处理。 据我所知,CBTL04083A 的开关基本上是场效应管,因此它应该可以切换单端信号。此外,1.8 V GPIO/UART 电平为 0-1.8V DC,属于设备的输入/共模范围。一个值得关注的问题是推荐的差分摆幅VID ≤ 1.6 V,因为 1.8 V 的 GPIO 可能会超过这个范围。我的假设是,VID 指南针对的是高速信号完整性,因此在这种低速使用情况下可能不是问题。 计划的 UART - CBTL04083A 连接:TX → P,RX → N为同一差分对,开关在一起。 请确认这种用法是否可用于可靠的通信,并分享任何最佳做法建议? Re: CBTL04083A to switch singled-ended 1.8V GPIO/UART 您好__OTL__ 日安 你说得没错,一个简单的直观方法就是把它理解为一个场效应管,不断被激活和失活。 因此,只要是直流和低频信号,它都能通过: -信号的电压范围在设备的 VDD 和绝对最大额定值范围内。 - 共模电压和摆幅不违反电气特性。 对于 1.8 V 逻辑电压(0-1.8V),这通常是安全的,因为该设备支持高达 3.3 V 的电源,而且绝对最大额定值高于 1.8 V。 VID 规格适用于高速差分线对,以确保信号完整性并将失真降至最低。对于低速 GPIO/UART 来说,这一点并不重要,因为..: - 对带宽的要求要低得多。 - 在这种速度下,场效应晶体管开关的行为几乎与短路一样。 因此,在这种情况下,超过 1.6 V 的差分摆幅不是功能问题。 同一差分对的 TX → P 和 RX → N 这在电气上是可以接受的,只是需要注意一些问题: 两条线路将一起切换,这对 UART TX/RX 来说是没有问题的。 确保未使用的差分路由不会引入耦合或噪声。 总之,对于可靠的 UART/GPIO 通信来说,计划中的使用是可以接受的;只是在设计布局时要注意避免任何噪声。 希望这些信息对您有所帮助,如果您还需要其他帮助,请告诉我。 祝你愉快,好运连连。
View full article
ELE KW45 导出公开密钥 我无法导出用于 ECDSA SHA256 校验的公钥。我使用 KW45 进行测试。我使用公开密钥正确验证了摘要。当我尝试导出 blob 时,函数 sss_sscp_key_store_export_key 返回 Fail。我做错了什么? 谢谢 下面是我的 C 代码: status = ELEMU_mu_wait_for_ready(ELEMUA,ELE_MAX_SUBSYSTEM_WAIT); if (status != kStatus_Success) { return kStatus_Fail; } /****************** 开始 ***********************/ status = sscp_mu_init(&sscpContext, (ELEMU_Type *)(uintptr_t)ELEMUA); if (status != kStatus_SSCP_Success) { return kStatus_Fail; } /* 打开特定网络安全子系统的会话 */ status = sss_sscp_open_session (& SSSSESSION、0u、ELE_SUBSYSTEM、& SSCPContext);if (状态! = kstatus_ss_success) {返回 kStatus_Fail;} /* Init keystore */ status = sss_sscp_key_store_init(&keyStore,&sssSession); if (status != kStatus_SSS_Success) { status = sss_sscp_close_session(&sssSession); return kStatus_Fail; } /* Init key object */ status = sss_sscp_key_object_init(&sssKey,&keyStore); if (status != kStatus_SSS_Success) { status = sss_sscp_key_store_free(&keyStore); status = sss_sscp_close_session(&sssSession); return kStatus_Fail; } /* 分配密钥存储句柄 */ status = sss_sscp_key_object_allocate_handle(&sssKey, key_id, /* key id */ kSSS_KeyPart_Public, kSSS_CipherType_EC_NIST_P, 64u, kSSS_KeyProp_CryptoAlgo_AsymSignVerify); if (status != kStatus_SSS_Success) { status = sss_sscp_key_object_free(&sssKey, 1u); status = sss_sscp_key_store_free(&keyStore); status = sss_sscp_close_session(&sssSession); return kStatus_Fail; } status = sss_sscp_key_store_set_key(&keyStore,&sssKey, publicKey, keysize, 256u, kSSS_KeyPart_Public); if (status != kStatus_SSS_Success) { status = sss_sscp_key_object_free(&sssKey, 1u); status = sss_sscp_key_store_free(&keyStore); status = sss_sscp_close_session(&sssSession); return kStatus_Fail; } status = sss_sscp_asymmetric_context_init(&context_verify,&sssSession,&sssKey, kAlgorithm_SSS_ECDSA_SHA256, kMode_SSS_Verify); if (status != kStatus_SSS_Success) { return kStatus_Fail; } status = sss_sscp_asymmetric_verify_digest(&context_verify, digest_used, digest_len, signature_used, 64); if (status != kStatus_SSS_Success) { return kStatus_Fail; } status = sss_sscp_asymmetric_context_free(&context_verify); if (status != kStatus_SSS_Success) { return kStatus_Fail; } size_t blob_size = 64u + 24u; status =sss_sscp_key_store_export_key(&keyStore,&sssKey, key_blob,&blob_size, kSSS_blobType_ELKE_blob); if (status != kStatus_SSS_Success) { status = sss_sscp_key_object_free(&sssKey, 1u); status = sss_sscp_key_store_free(&keyStore); status = sss_sscp_close_session(&sssSession); return kStatus_Fail; } Re: ELE KW45 export public key 你好 您能给我们提供更多关于您的项目和您的目标的细节和信息吗? 您能否帮助我们确认您是否在使用 SDK 示例进行此测试?如果是,您是否进行了修改? 顺祝商祺! 路易斯 Re: ELE KW45 export public key 你好,路易斯、 我已经解决了这个问题。在导出密钥之前,我缺少 RNG 上下文初始值。添加了以下功能调用后,键已正确导出。 sss_sscp_rng_context_init(&sssSession,&ctx_rng, 1u); status = sss_sscp_rng_get_random(&ctx_rng,NULL,0u); 总之,我使用的是输出对称密钥的 SDK 示例;在我的示例中,唯一的区别是我使用了非对称密钥,只有公开部分,用于 ECC Nist-p 曲线。 谢谢! 亚历山德罗
View full article
ubloxとlwipでビルディングするときにwifi_nxpに2つの問題が見つかりました https://github.com/NXP/wifi_nxp/issues に 2 つの問題を追加しました。SO誰かがこれを見て欲しい 問題1 LWIP_IGMP を 0 に設定するとビルドできません 問題2 MCUX_COMPONENT_utility.debug_console_rttでビルドできません Re: I have found 2 problems in wifi_nxp when building with ublox and lwip 新しい問題が 1 つ追加されました。SO 3 つの問題が未解決になりました。 Re: I have found 2 problems in wifi_nxp when building with ublox and lwip こんにちは、 教えてくれてありがとう。 担当チームに通知いたしました。 ちなみに、どのu-bloxモジュールを使用していますか? よろしくお願いいたします。 ダニエル。 Re: I have found 2 problems in wifi_nxp when building with ublox and lwip よろしくお願いします。 どの SDKs バージョンを使用していますか? どのような例を使っていますか? それぞれのCASEの再現手順を共有してCANいただけますか? よろしくお願いいたします。 ダニエル。 Re: I have found 2 problems in wifi_nxp when building with ublox and lwip LWIP_IGMP が無効になっている場合のビルドの問題について · 問題 #7 · NXP/wifi_nxp 。 LWIP_IGMPを0に設定してLWIPを使用する場合は、wifi_netif.cファイル内の以下のコードを保護してください。 #もし LWIP_IGMP では以下のようにエラーが発生します。 #if LWIP_IGMP netif_set_igmp_mac_filter(netif, igmp_mac_filter); netif->flags |= NETIF_FLAG_IGMP; #endif よろしくお願いいたします。 ダニエル。 Re: I have found 2 problems in wifi_nxp when building with ublox and lwip AP をオフにするとビルドできないことについて · 問題 #9 · NXP/wifi_nxp 。 WPL_Start_APとWPL_Stop_APというAPIは、wifi_webconfigサンプルの一部です。このサンプルはuAPを起動するために設計されており、プロビジョニングに特化しています。そのため、SDKsではuAPの機能を保護できません。 #もし。 コードをカスタマイズし、wifi_webconfig の例をベースとして使用する場合は、次のコマンドを使用してガード機能を追加できます。 #if UAP_SUPPORT ... #endif   これにより、必要に応じて AP 機能を無効にできるようになります。
View full article
Spice 原理图和 mex 原理图有什么区别? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你们好 我正在使用 BFU730F 设计一个低噪声放大器,我下载了设计工具包,但我看到有两种类型的晶体管,一种是 spice 原理图,另一种是 mex 原理图。我在 ADS 上都试过了,但得到的结果却不一样。 我想知道是否有人知道这两种型号有什么区别,为什么我得不到相同的结果? 提前谢谢您。 Re: What is the difference between a spice schematic and a mex shematic 请再次附上 PDF 文件,我也遇到了同样的问题。 Re: What is the difference between a spice schematic and a mex shematic <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 请参阅以下文件,了解 Mextram 与 Spice 模型的异同: https://www.nxp.com/files-static/nxp/other_type/nlur2002823.pdf https://www.nxp.com/files-static/nxp/other_type/bctm89graaff.pdf 祝您愉快, Pavel ----------------------------------------------------------------------------------------------------------------------- 注:如果本帖回答了您的问题,请点击正确答案按钮。Thank you! -----------------------------------------------------------------------------------------------------------------------
View full article
实时时钟 PCF85043A 运行速度过快 +55ppm 你好、 我们发现,我们在几种产品中使用的 PCF85043A 实时时钟的 +55 ppm 运行速度过快。 对于老产品,我们在生产过程中会进行频率校准,因此偏移会被抵消。但在较新的产品中,我们放弃了校准,现在发现 RTC 总是运行得太快。 我们使用的晶体是 ECS-.327-7-34B-C-TR、指定为 7pF 负载。 因此,我们将 PCF85063 的负载上限寄存器设置为 7pF。 我们在现场应用以及实验室测量中使用三种不同精度的 TCXO 作为参考,观察了由此产生的时间偏移。 我们还检查了演示板 OM11059A,它给出了相同的结果! 将负载上限寄存器设置为 12.5pF 可在一定程度上提高精度,但仍然不够精确,而且不令人满意,因为这种现象肯定有更深层次的原因。 PCF85063 有 55ppm 的频率偏移,这是已知的问题吗? 如果是,恩智浦的 "建议解决方案 "是什么? 感谢您的提示。 Re: Real-time clock PCF85043A is running too fast by +55ppm 好的,谢谢你的发言。 不过,我们有几款 10'000 产品,它们显示出明显的 +55ppm 平均频率偏移。很少达到正确的频率,甚至出现负偏移。 (当然,我知道核实频率是我们自己的责任,是我们的错,我们直到现在才注意到)。 不过...... 根据 UM10301 用户手册中的图表(见附图),这意味着几乎所有实时时钟芯片的负载上限都在约 4.5pF 的最小范围内,但很少或几乎从未达到 7pF 或更高。 我想,在>数年的 30,000 件产品中,这显然不是由于某批晶圆电容过低造成的。 因此,这与我们从数据表中看到的结果大相径庭。 好吧,我们可以变通,没问题。我很高兴知道,我没有测量错,这实际上是一种非理想行为。 对于未来的设计:我想,额外的外部电容(具有更精确的值)可以更准确地确定频率。 Re: Real-time clock PCF85043A is running too fast by +55ppm 嗨,比特、 还是说,这实际上是芯片的一种非理想行为,可以通过偏移寄存器来解决? 最后一句是正确的。请参阅PCF85063A 数据表中的表 40。内部晶体电容具有容差。7pF 电容可能从 4.2pF 到 9.8pF 不等。因此,晶体频率也可能根据内部电容的变化而变化。 是的,应该用偏移寄存器来解决这个问题。 致以最崇高的敬意 约瑟夫 Re: Real-time clock PCF85043A is running too fast by +55ppm 你好,Jozef, 感谢您的答复。 我们已经知道偏移寄存器,我们用它来补偿偏移和晶体的温度曲线。 当然,这也算是解决了问题。然而,这只是一种变通办法,并不能从根本上解决问题。 问题是: 使用 +/-10ppm 晶体,为什么在室温下会产生 +55ppm 偏移? 在室温下,不需要对软件进行微调,只需要对硬件的负载能力进行微调。根据数据手册,负载上限由实时时钟芯片提供,无需外部负载上限。那么,为什么会有如此大的频率偏差(使用几种晶体、多个参考和包括演示板在内的几个 PCB)? 我错过了什么吗? 还是说,这实际上是芯片的一种非理想行为,可以通过偏移寄存器来解决? Re: Real-time clock PCF85043A is running too fast by +55ppm 嗨,比特、 PCF85063A 的精度可在偏移寄存器中进行微调。请参阅PCF85063A 数据手册中的第 7.2.3 节。 校准工作流程请参见图 11 和图 12。 致以最崇高的敬意 约瑟夫
View full article
大きく異なる こんにちは、 生成されたコードのハードウェア上でのリアルタイム実行が、シミュレーション結果と大きく異なっていました。根本的な原因は何でしたか? また、この実際のパフォーマンス問題を解決するために、モデルまたはターゲット構成をどのように変更しましたか?
View full article
使用 S32K314 DFlash 模拟 EEPROM 大家好目前,项目中使用 C40_ip 元器件的 API 进行 dFlash 擦除操作。不过,我从手册中发现,S32K314 的 DFlash 和 PFlash 的扇区擦除寿命只有 1000 次。因此,我很想知道如何使用恩智浦认可的 EEEPROM 驱动程序。 最重要的是,该项目中使用的所有元器件都属于 “驱动程序”,而不是 “MCAL”。我想知道目前有哪些解决方案可以提高项目中对 DFlaser 擦除和写入周期的寿命要求。 期待得到社会各界的回应。 Re: use S32K314 DFlash to simulate EEPROM 您的问题的解决方案是使用我们的 EEPROM 仿真驱动程序,它们是 RTD 驱动程序代码包的一部分。 Re: use S32K314 DFlash to simulate EEPROM 非常感谢你的答复! 目前,我只能在 " MCAL " 元器件中找到 FEE 元器件,但是所有现有的项目都是基于 " Driver " 元器件开发的,这主要是由于这个矛盾。 Re: use S32K314 DFlash to simulate EEPROM 当前 RTD 版本为 6.0.0。 示例和二手驱动程序如下: Re: use S32K314 DFlash to simulate EEPROM 非常感谢你的回答! 我成功地在 IDE 中找到了这个演示,我想知道 " MCAL " 和 " D river " 的元器件能否混合在一起? 如果可能的话,使用 " MCAL " 中的三个费用元器件,而不是演示中显示的 " Driver " 中的 " c40_ip " 元器件是否可行?会有兼容性问题吗? Re: use S32K314 DFlash to simulate EEPROM 感谢您的答复! 那么,要使用 EEEPROM 的功能,目前是否建议充分使用 " MCAL " 元器件来实现?对于已经开发了大部分功能并充分使用 " Driver " 元器件的项目来说,移植的工作量有点繁重... Re: use S32K314 DFlash to simulate EEPROM 不推荐,你可以选择其中一个层。 Re: use S32K314 DFlash to simulate EEPROM 我认为这基本上取决于你。费用元器件将在定义的闪存部分上方运行,因此你可以使用带有 IP 层的其他部分,但要由你来保证一致性。
View full article
S32K312 Wkup 恩智浦的支持者们,你们好。我使用基于 LLD 的 S32K312 配置了一组代码。现在我想内置 WKUP 功能,但我遇到了一些问题。如果我不在代码中添加以下代码: Power_Ip_Init(&Power_Ip_HwIPsConfigPB); Power_Ip_GetResetReason(); Power_Ip_SetMode(&Power_Ip_aModeConfigPB[0]);   程序将进入待机模式,但唤醒后会异常运行。如果我添加以下代码 Power_Ip_Init(&Power_Ip_HwIPsConfigPB); Power_Ip_GetResetReason(); Power_Ip_SetMode(&Power_Ip_aModeConfigPB[0]);   调用 ADC、PWM 等其他外设接口获取数据时,会出现硬件错误,如 Adc_Sar_Ip_GetConvData、Emios_Icu_Ip_StartSignalMeasurement 等。 如果我不调用外围接口,程序通常可以进入待机模式并唤醒。原因何在?故障排除的方向是什么?很抱歉,我的代码不能共享。 Re: S32K312 Wkup 你好@ZZZZJH、 是的,有一些区别,正常待机退出将同时执行 HSE& sBAF 初始化代码和 HSE_FW 校验,而快速待机退出将绕过以节省时间。此外,快速待机退出将启动到用户定义的地址,在调用 Reset_Handler 和完全初始化 MCU 之前,用户可以在该地址执行一些关键任务。 您可以从 S32K3 参考手册第 41.2 章中找到完整的详细信息。 致以最诚挚的问候, Julián Re: S32K312 Wkup 谢谢,朱利安!出现上述问题是因为我的电源中的MCU外设元器件未启用。这导致了硬件错误。问题已经解决。我目前使用的是正常的待机模式。请问 "快速 "和 "正常 "之间有什么区别吗? Re: S32K312 Wkup 你好@ZZZZJH、 我不确定第一段代码和第二段代码之间有什么区别,但听起来你好像缺少了 POWER 驱动程序中的某些配置。如果未启用元器件,则尝试初始化或使用它会导致硬故障。 例如,在运行模式下,在 MCUPersederAppertional 选项卡中确认是否启用了 ADC 和 PWM 实例: 另外,您使用的是快速待机还是普通待机退出?如果使用 fast,则必须在唤醒后跳转到 “RESET 处理器” 才能正确初始化 MCU。 下面的社区帖子中还有一些低功耗配置示例: [RTD400 & 500 MCAL & IP] S32K3 电源管理单元 AN 和演示-恩智浦社区 S32K3 电源管理单元 AN 和演示-恩智浦社区 致以最诚挚的问候, Julián
View full article