Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
The SPI duty cycle of S32K322 is not 50% for 8MHz Dear NXP team,           We are working on an improvement activity where we need to have the 8MHz SPI SCLK to be periodic within SPI transactions. We measured the SPI SCLK for 8MHz (which is driven by the SPI peripheral driver in S32K322) and found that 50% duty is not maintained. When we lower the frequency to 1/2/4 MHz we see 50% duty being maintained for those SCLK frequencies.  Question - Is this any Hardware limitation of the Peripheral driver or by changing the driver settings, desired 50% duty can be obtained for 8MHz? PFA the screenshots where duty is maintained for 1MHz and not for 8MHz Note: We have connected Logic Analyzer from Saleae that has higher sampling resolution (250MS/s) to measure the SPI signals Re: The SPI duty cycle of S32K322 is not 50% for 8MHz Hi, the LPSPI clock duty cycle is determined by the SCKSET and SCKHLD timing parameters. A 50/50 duty cycle is only obtained when these fields are programmed to equal values. Depending on the selected LPSPI functional clock and the divider values required to generate 8 MHz, an exact 50/50 duty cycle may not be achievable due to the timing resolution of the clock generator. The observed 76 ns / 48 ns high-low times appear consistent with such divider quantization effects. So, try to calculate the expected duty cycle from your LPSPI functional clock frequency, TCR[PRESCALE], and the contents of the CCR/CCR1 registers (SCKSET, SCKHLD, SCKDIV), and determine whether a different clock source or divider configuration could achieve a duty cycle closer to 50/50.   BR, Petr
View full article
MIMXRT1170-EVK FreeRTOS Hello Example Issue Hi Team, I imported the evkbmimxrt1170_freertos_hello_cm7 example project from the MCUXpresso SDK into MCUXpresso IDE without making any significant modifications. The project builds successfully without any errors or warnings and downloads to the MIMXRT1170-EVK(MIMXRT1176DVMAA) board successfully. The task created successfully and executes only once and then stops at address 0xDEADBEEE. This behavior occurs every time. LED Toggle Task: To verify whether the problem was related to vTaskSuspend(), I've created another task with a simple LED blinking task. Expected behavior: LED should toggle every 100 ms continuously. Actual behavior: LED toggles only once. After the first execution, debugger again stops at: 0xDEADBEEE Kindly clarify the following queries, What does address 0xDEADBEEE indicate in the MCUXpresso SDK for i.MX RT1170? Why does the task execute only once instead of running periodically? Is there any additional configuration required to work correctly on the MIMXRT1170-EVK? What changes are required to make the task execute periodically as expected? Re: MIMXRT1170-EVK FreeRTOS Hello Example Issue Hello @Rosh, I understand that you are currently using the MIMXRT1170-EVK. Please note that the SDK for the MIMXRT1170-EVK is different from the SDK provided for the MIMXRT1170-EVKB. Could you please download and test with the SDK specifically generated for the RT1170-EVK using the MCUXpresso SDK Builder? I understand your point. The SDK examples are intended to provide a common use cases for each peripheral functionality. The 0xDEADBEE value is typically associated with a HardFault condition. Could you please run the example without any modifications and let me know the results using the latest available SDK version? BR Habib Re: MIMXRT1170-EVK FreeRTOS Hello Example Issue Hi @Habib_MS  I've downloaded the SDK specifically generated for the RT1170-EVK using the MCUXpresso SDK Builder and tested it. It is working fine now. Thank you for your support.
View full article
FRDM-MCXA156: SWO Trace (Data, Profile & Interrupts) Not Working in MCUXpresso IDE Hello Everyone, I am currently working with the FRDM-MCXA156 development board and have been facing an issue with SWO (Serial Wire Output) while debugging. Although the application debugs successfully, I am unable to receive any data in the SWO Trace windows, including: SWO Data SWO Profile SWO Interrupt Trace SWO ITM Console To troubleshoot the issue, I have already verified the following: The SWO pin has been correctly configured using Config Tools. The TRACE clock is enabled and configured to 96 MHz, matching the MCU core clock (MCXA156 runs at 96 MHz). The project is being debugged using LinkServer with the on-board MCU-Link probe. Despite these configurations, all the SWO trace windows remain empty during debugging. For reference, I have attached screenshots of the SWO Trace Configuration, SWO Data, SWO Profile, and other windows, along with the relevant project configuration. I would greatly appreciate any guidance or suggestions on what might be causing this issue or if there are any additional configuration steps required to enable SWO trace on the FRDM-MCXA156. Thank you for your time and assistance. #swo #frdm-mcxa156  Development Board MCXA Re: FRDM-MCXA156: SWO Trace (Data, Profile & Interrupts) Not Working in MCUXpresso IDE With respect to previous thread, The screenshot of SWO enable configuration and clocks are attached below. Thanks Re: FRDM-MCXA156: SWO Trace (Data, Profile & Interrupts) Not Working in MCUXpresso IDE Hello @sidsal  For the FRDM-MCXA156 board, resistor R36, which connects the SWO signal to the onboard debugger, is DNP (not populated) by default. Could you please populate R36 and test again? Thank you. BR Alice Re: FRDM-MCXA156: SWO Trace (Data, Profile & Interrupts) Not Working in MCUXpresso IDE Thank you for pointing this out @Alice_Yang . I checked the FRDM-MCXA156 schematic and confirmed that R36, which connects the P0_2/SWO signal to the onboard MCU-Link debugger, is marked as DNP. I also noticed that on the FRDM-MCXN947, the equivalent SWO connection (R130) is populated with a 0 Ω resistor. Could you please confirm whether R36 on the FRDM-MCXA156 should also be populated with a 0 Ω resistor to enable SWO tracing through the onboard MCU-Link debugger? Additionally, could you please clarify why R36 is left unpopulated (DNP) by default on the FRDM-MCXA156? Is there a specific board-design reason or limitation that requires it to remain unpopulated? So I cannot use SWO feature?  Thank you for your help. Re: FRDM-MCXA156: SWO Trace (Data, Profile & Interrupts) Not Working in MCUXpresso IDE Hello @sidsal  " Could you please confirm whether R36 on the FRDM-MCXA156 should also be populated with a 0 Ω resistor to enable SWO tracing through the onboard MCU-Link debugger?" ->>Yes. If you want to use the SWO function, you need to install a 0 Ω resistor or solder the connection accordingly. “Additionally, could you please clarify why R36 is left unpopulated (DNP) by default on the FRDM-MCXA156? ” ->>I think this is because not all users require the SWO function, so the 0 Ω resistor is not populated by default. Thank you. BR Alice Re: FRDM-MCXA156: SWO Trace (Data, Profile & Interrupts) Not Working in MCUXpresso IDE Thank you for your support @Alice_Yang .
View full article
S32K356 RTD选择 我们计划使用S32K356,发现只有7.0.0和7.0.1可以用,但是对应autosar R23,如果使用autosar R21,哪个版本可以推荐? Re: S32K356 RTD选择 SW32K3_S32M27x_RTD_R21-11_6.0.0_P05_D2510,我也尝试了,但是尝试了很多次都失败了,猜测跟S32Ds版本有关系,3.6.7也试过了,还是S32D32用哪个版本呢? Re: S32K356 RTD选择 从6.0.0的描述看,并不支持S32K356. Re: S32K356 RTD选择  如上图,6.0.0 QLP01也无法安装,还有另一个问题,通过RTD release note,只需要S32DS3.6.2即可满足安装要求,为什么我用3.6.7,还提示要更新组件,这个跟release note 不符合,是什么原因。 Re: S32K356 RTD选择 这是安装RTD7.0.1的错误信息,看起来是版本限制吗?另外,RTD release描述的对应的S32DS的版本,按理解说,应该是直接可以安装,不再需要更新S32DS组件,如果还需要更新组件,还不如推荐更新的安装版本,更便于使用。 Re: S32K356 RTD选择 S32DS版本不符合的问题怎么解决的,为什么我在S32DS3.6.7中安装RTD7.0.1,还是装不上,提示更新。 Re: S32K356 RTD选择 你好@wenming , 问题可能与 S32DS 版本有关。 但是,请务必先安装 QLP01,正如 SW32K3_S32M27x_RTD_R21-11_6.0.0_P05_D2510_ReleaseNotes.txt 中所述:“此版本基于 S32K3_S32M27x 实时驱动程序 AUTOSAR R21-11 版本 6.0.0 QLP01。” 顺祝商祺! 帕维尔 Re: S32K356 RTD选择 你好@wenming , 我还有一些补充发现。 好消息是,我能够在 S32DS 3.6.2 中安装 RTD 6.0.0 QLP01 和 P05。然而,尽管发行说明中如此描述,RTD 6.0.0 QLP01 必须先安装在干净/基础的 RTD 6.0.0 安装之上。之后,P05 也能成功安装。 遗憾的是,即使按照上述安装步骤操作后,SDK 仍然无法附加到 S32DS 中的 S32K356 项目。 我了解到您正在寻找旧版本的 AUTOSAR。然而,根据观察到的行为,我无法确认 S32DS 中 RTD 6.0.0 的 S32K356 设置是否正常工作。对于 S32K356,较新的 RTD 7.0.0 版本似乎提供了实用的 S32DS 支持。/ 7.0.1 版本。 顺祝商祺! 帕维尔 Re: S32K356 RTD选择 你好@wenming , 问题1:如何解决S32DS版本不兼容问题? 请您更具体地描述一下您看到的兼容性错误信息?   Q2:为什么我无法在 S32DS3.6.7 中安装 RTD7.0.1,并且它一直提示我更新? 更新提示本身并不是错误。当所选 RTD 软件包依赖于更新或附加的元器件时,S32DS 可能会要求更新相关的平台/工具软件包。   另外,请确保 S32 Design Studio 中已安装 S32K3 RTD 软件包所需的 GCC 10.2 工具链。   顺祝商祺! 帕维尔 Re: S32K356 RTD选择 你好@wenming , 谢谢你提供的截图。 从错误信息来看,这似乎不是 S32DS 版本限制。S32DS 在收集/下载待安装项目时发生错误,关键信息为: ZLIB 输入流意外终止 失败的项目是与 S32DS 平台/调试相关的工件,例如: com.nxp.s32ds.doc.platform.resources com.nxp.s32ds.lrc.gdb.arm64.linux.win32 这通常表明其中一个文件没有完全下载,或者在下载/提取过程中损坏了。因此,这个问题看起来更像是更新站点/下载/缓存问题,而不是 RTD 7.0.1 与 S32DS 3.6.7 之间的直接兼容性限制。 关于发行说明:所列出的 S32DS 版本应理解为该 RTD 版本的基准/测试 S32DS 版本。然而,S32DS 是模块化的,如果当前安装中缺少或过时了相关的平台、工具、调试器、编译器或文档组件,则 RTD 安装可能仍然需要更新或安装这些组件。 请尝试以下步骤: 重启S32DS,然后再次尝试安装。 请确保与 NXP 更新站点的网络连接稳定。 如果可能,请在安装过程中使用官方离线更新站点的 ZIP/软件包,而不要仅依赖在线下载。 检查 S32DS 中是否已安装所需的 GCC 10.2 工具链。 如果问题仍然存在,请尝试全新安装 S32DS 3.6.x 版本。安装时,请先安装 RTD 7.0.1 基本软件包,然后再应用任何其他补丁/更新软件包。 因此,根据目前的截图,我不会得出 RTD 7.0.1 不能与 S32DS 3.6.7 一起使用的结论。当前错误指向的是所需 S32DS 更新文件的下载不完整/已损坏。 作为参考,我已成功在 S32DS 3.6.6 中安装了 SW32K3_S32M27x_RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite.zip。在我的配置中,我只需要额外安装 S32K3 RTD 软件包所需的 GCC 10.2 工具链。   顺祝商祺! 帕维尔 Re: S32K356 RTD选择 我将S32DS版本改为3.6.10了,这个版本可以安装RTD7.0.1,不需要额外安装其他组件。我们现在先使用S32DS3.6.10+RTD7.0.1开发。如果后续autosar R21的版本有更新的消息,麻烦告知一下,谢谢了。
View full article
IW612 working on IMX95-19x19 EVK board based on Android 16 In default, IMX95-19x19 EVK board enables the PCIe M.2 interface for Wi-Fi modules. But for SDIO interface M.2 Wi-Fi module, we could not use it directly. This doc is a step by step guide about how to make IW612 SDIO M.2 module(Murata 2EL) working on IMX95-19x19 EVK board based on Android 16. 1.Download I.MX Android BSP package, copy with scp to VMSIS. 16.0.0_1.4.0_ANDROID_SOURCE 2.Decompressing android bsp tar -xzf imx-android-16.0.0_1.4.0.tar.gz 3. source ./imx_android_setup.sh to download Android source code. 4.Prepare cross compiler GCC cross compiler: Download the tool chain for the AArch32 and AArch64 on: Arm GNU Toolchain I download the latest version: Arm GNU Toolchain 15.3.rel1 Need to pay attention, for I.MX95, need both 64 bit and 32 bit GCC compile tool. 64bit: arm-gnu-toolchain-15.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz 32 bit: arm-gnu-toolchain-15.3.rel1-x86_64-arm-none-eabi.tar.xz For AArch64 toolchain nxf93258@lsv051430:~/GCC_cross_compile_toolchain$sudo tar -xvJf arm-gnu-toolchain-15.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz -C /opt/ nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$export AARCH64_GCC_CROSS_COMPILE=/opt/arm-gnu-toolchain-15.3.rel1-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- For 32bit toolchain: nxf93258@lsv051430:~/GCC_cross_compile_toolchain$sudo tar -xvJf arm-gnu-toolchain-15.3.rel1-x86_64-arm-none-eabi.tar.xz -C /opt/ nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$ export AARCH32_GCC_CROSS_COMPILE=/opt/arm-gnu-toolchain-15.3.rel1-x86_64-arm-none-eabi/bin/arm-none-eabi- 5.Set the external clang, kernel-build-tools, rust, and clang-tools tools for kernel building: nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$ sudo ./device/nxp/common/tools/setup_android_kernel_prebuilts.sh 6.Set up the environment for building. This only configures the current terminal, if change to another terminal need to re-run the configurations. nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$ source build/envsetup.sh 7.Execute the Android lunch command for i.MX95-EVK. nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$lunch evk_95-nxp_stable-userdebug 8.Optional Steps: Execute the imx-make.sh script to finish the whole images compiling. Or you can follow below steps to only build required images. nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$ ./imx-make.sh -j4 2>&1 | tee build-log.txt 9.Modify the device tree to disable pcie0 and enable usdhc3 like below: ~/Android/imx-android-16.0.0_1.4.0/android_build/vendor/nxp-opensource/kernel_imx/arch/arm64/boot/dts/freescale$ git diff diff --git a/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts b/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts index 69508a66f1c8..dfa1d3d51a9c 100644 --- a/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts +++ b/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts @@ -26,10 +26,19 @@ / { aliases { mmc0 = &usdhc1; mmc1 = &usdhc2; + mmc2 = &usdhc3; serial0 = &lpuart1; ethernet0 = &enetc_port0; ethernet1 = &enetc_port2; }; + + usdhc3_pwrseq: usdhc3_pwrseq { + compatible = "mmc-pwrseq-simple"; + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_usdhc3_pwrseq>; + post-power-on-delay-ms = <100>; + }; + bt_sco_codec: audio-codec-bt-sco { #sound-dai-cells = <1>; @@ -651,7 +660,7 @@ &pcie0 { reset-gpio = <&i2c7_pcal6524 5 GPIO_ACTIVE_LOW>; vpcie-supply = <&reg_pcie0>; supports-clkreq; - status = "okay"; + status = "disable"; }; &pcie1 { @@ -733,6 +742,22 @@ &usdhc2 { status = "okay"; }; +&usdhc3 { + pinctrl-names = "default", "state_100mhz", "state_200mhz", "sleep"; + pinctrl-0 = <&pinctrl_usdhc3>; + pinctrl-1 = <&pinctrl_usdhc3_100mhz>; + pinctrl-2 = <&pinctrl_usdhc3_200mhz>; + pinctrl-3 = <&pinctrl_usdhc3>; + mmc-pwrseq = <&usdhc3_pwrseq>; + vmmc-supply = <&reg_pcie0>; //Both PCIE0 and USDHC3 use same power supply. + bus-width = <4>; + keep-power-in-suspend; + non-removable; + wakeup-source; + status = "okay"; +}; + + &enetc_port0 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_enetc0>; @@ -1225,6 +1250,45 @@ IMX95_PAD_SD2_DATA3__USDHC2_DATA3 0x138e IMX95_PAD_SD2_VSELECT__USDHC2_VSELECT 0x51e >; }; + + pinctrl_usdhc3_pwrseq: usdhc3pwrseq { + fsl,pins = < + IMX95_PAD_XSPI1_SCLK__GPIO5_IO_BIT9 0x31e + >; + }; + + pinctrl_usdhc3: usdhc3grp { + fsl,pins = < + IMX95_PAD_SD3_CLK__USDHC3_CLK 0x158e + IMX95_PAD_SD3_CMD__USDHC3_CMD 0x138e + IMX95_PAD_SD3_DATA0__USDHC3_DATA0 0x138e + IMX95_PAD_SD3_DATA1__USDHC3_DATA1 0x138e + IMX95_PAD_SD3_DATA2__USDHC3_DATA2 0x138e + IMX95_PAD_SD3_DATA3__USDHC3_DATA3 0x138e + >; + }; + + pinctrl_usdhc3_100mhz: usdhc3-100mhzgrp { + fsl,pins = < + IMX95_PAD_SD3_CLK__USDHC3_CLK 0x158e + IMX95_PAD_SD3_CMD__USDHC3_CMD 0x138e + IMX95_PAD_SD3_DATA0__USDHC3_DATA0 0x138e + IMX95_PAD_SD3_DATA1__USDHC3_DATA1 0x138e + IMX95_PAD_SD3_DATA2__USDHC3_DATA2 0x138e + IMX95_PAD_SD3_DATA3__USDHC3_DATA3 0x138e + >; + }; + + pinctrl_usdhc3_200mhz: usdhc3-200mhzgrp { + fsl,pins = < + IMX95_PAD_SD3_CLK__USDHC3_CLK 0x15fe + IMX95_PAD_SD3_CMD__USDHC3_CMD 0x13fe + IMX95_PAD_SD3_DATA0__USDHC3_DATA0 0x13fe + IMX95_PAD_SD3_DATA1__USDHC3_DATA1 0x13fe + IMX95_PAD_SD3_DATA2__USDHC3_DATA2 0x13fe + IMX95_PAD_SD3_DATA3__USDHC3_DATA3 0x13fe + >; + }; }; &thermal_zones { 10.Build dtbo image. Need about 40 minutes. DTBO image holds the device tree binary of the board. nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$ source build/envsetup.sh nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$ lunch evk_95-nxp_stable-userdebug nxf93258@lsv051430:~/Android/imx-android-16.0.0_1.4.0/android_build$./imx-make.sh dtboimage -j4 Then you will see that the dtbo images time stamp are updated as below: Below info is for your reference. ~/Android/imx-android-16.0.0_1.4.0/android_build/device/nxp/common/build/dtbo.mk This makefile includes the logic how to pack dtbo image. ~/Android/imx-android-16.0.0_1.4.0/android_build/device/nxp/imx9/evk_95/SharedBoardConfig.mk  This Macro: SUPPORT_GBL is not enabled in default, so still use dtbo image for the device tree. ~/Android/imx-android-16.0.0_1.4.0/android_build/device/nxp/imx9/evk_95/BoardConfig.mk  Wi-Fi/Bluetooth FW located here:  Wi-Fi/Bluetooth driver located here: Can modify the Makefile accordingly if needed. After compiled, the Wi-Fi driver and cfg80211.ko is located here: 11.Download prebuilt Image and decompress it. 16.0.0_1.4.0_DEMO_95//Pay attention to the version, need to match with our Android Source code download version. 12.Replace dtbo image. Rename the original dtbo-imx95.img to dtbo-imx95_original.img in the prebuilt image directory to be a backup. Then copy the dtbo-imx95.img from the remote android source code compiled directory: ~/Android/imx-android-16.0.0_1.4.0/android_build/out/target/product/evk_95/dtbo-imx95.img to the prebuilt image directory. Like below: 13.Flash images into board. Change the I.MX95-19*19-EVK board's SW7 to 1001 (from 1-4 bit) to enter serial download mode, then connect the board's USB1 port with type C cable to Windows PC. Download the UUU binary file from GitHub: Releases · nxp-imx/mfgtools Open the cmd interface in administrator mode, and enter to the prebuilt image directory. Flash the images into I.MX95-19*19-EVK board with below command: uuu_imx_android_flash.bat -f imx95 -a -e -u trusty-dual For the details of each parameter, can refer to: Android Quick Start Guide 14.Verify Wi-Fi and Bluetooth functions. After flash finished successfully, power off the board and change the board's SW7 to switch the board back to 1010 (form 1-4 bit) to enter eMMC boot mode. Check dmesg logs to confirm IW612 Wi-Fi driver is loaded successfully:   Check Wi-fi and Bluetooth work as expected in UI.  Can use this application: scrcpy on windows instead of connecting a LCD. This guide can also be a reference for other M.2 Wi-Fi modules with SDIO interface working on I.MX95 19*19-EVK board with Android or Linux OS. Reference: Android Quick Start Guide Android User's Guide Linux-Kernel Archive: [PATCH V3 2/3] arm64: dts: imx95-15x15-evk: Disable PCIe bus in the default dts Finished by Christine.Li. Aug 5 2026.
View full article
A2DP test on IW612+I.MX8MPlus-EVK L6.6.52 This doc is a brief step by step introduction for how to play music through A2DP on IW612 + I.MX8MPlus-EVK based on L6.6.52. Step 1: Load WiFi/Bluetooth Driver • NXP i.MX Release Distro 6.6-scarthgap imx8mpevk ttymxc1 imx8mpevk login: root root@imx8mpevk:~# modprobe moal mod_para=nxp/wifi_mod_para.conf root@imx8mpevk:~# root@imx8mpevk:~# dmesg | grep wlan [ 562.728200] wlan: Loading MWLAN driver [ 562.728788] wlan: Register to Bus Driver... [ 562.730460] wlan: Enable TX SG mode [ 562.730464] wlan: Enable RX SG mode [ 563.554778] wlan: uap%d set max_mtu 2000 [ 563.622367] wlan: version = SDIW612---18.99.3.p21.10-MM6X18505.p4-GPL-(FP92) [ 563.625611] wlan: Register to Bus Driver Done [ 563.625622] wlan: Driver loaded successfully root@imx8mpevk:~#modprobe btnxpuart root@imx8mpevk:~# hciconfig -a hci0: Type: Primary Bus: UART BD Address: D0:17:69:EE:71:4F ACL MTU: 1021:7 SCO MTU: 120:6 DOWN RX bytes:774 acl:0 sco:0 events:48 errors:0 TX bytes:496 acl:0 sco:0 commands:47 errors:0 Features: 0xbf 0xfe 0x8f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: PERIPHERAL ACCEPT • Step 2: Up BT interface and enable the power save feature root@imx8mpevk:~# hciconfig hci0 up root@imx8mpevk:~# hciconfig hci0 piscan root@imx8mpevk:~#hciconfig hci0 noencrypt root@imx8mpevk:~# hciconfig -a hci0: Type: Primary Bus: UART BD Address: D0:17:69:EE:71:4F ACL MTU: 1021:7 SCO MTU: 120:6 UP RUNNINGPSCAN ISCAN RX bytes:1900 acl:0 sco:0 events:109 errors:0 TX bytes:1365 acl:0 sco:0 commands:108 errors:0 Features: 0xbf 0xfe 0x8f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: PERIPHERAL ACCEPT Name: 'imx8mpevk' Class: 0x200000 Service Classes: Audio Device Class: Miscellaneous, CI Version: 5.4 (0xd) Revision: 0x8300 LMP Version: 5.4 (0xd) Subversion: 0x1015 Manufacturer: NXP Semiconductors (formerly Philips Semiconductors) (37) • Step 3: Scan, Pair and Connect to Headset root@imx8mpevk:~# bluetoothctl hci0 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn cis-central cis-peripheral Agent registered [CHG] Controller D0:17:69:EE:71:4F Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# default-agent Default agent request successful [bluetooth]# agent on Agent is already registered [bluetooth]# scan on [NEW] Device B1:96:11:68:9C:09 联想thinkplus-HE05X II代 [bluetooth]# scan off [bluetooth]# pair B1:96:11:68:9C:09 Attempting to pair with B1:96:11:68:9C:09 hci0 device_flags_changed: B1:96:11:68:9C:09 (BR/EDR) supp: 0x00000000 curr: 0x00000000 [DEL] Device 67:02:B9:7C:ED:B5 67-02-B9-7C-ED-B5 [DEL] Device 80:F4:16:4C:48:F2 HI-Apiyoo-12MIQ001981 hci0 B1:96:11:68:9C:09 type BR/EDR connected eir_len 34 [CHG] Device B1:96:11:68:9C:09 Connected: yes hci0 new_link_key B1:96:11:68:9C:09 type 0x04 pin_len 0 store_hint 1 [CHG] Device B1:96:11:68:9C:09 Bonded: yes [DEL] Device 6A:98:7A:08:0F:B8 6A-98-7A-08-0F-B8 [CHG] Device B1:96:11:68:9C:09 ServicesResolved: yes [CHG] Device B1:96:11:68:9C:09 Paired: yes Pairing successful5X II代]# [DEL] Device 6C:59:25:E5:66:77 6C-59-25-E5-66-77 [DEL] Device 61:CC:7D:CE:20:4E 61-CC-7D-CE-20-4E [DEL] Device 64:C1:4B:76:C1:80 64-C1-4B-76-C1-80 [DEL] Device 72:50:16:14:52:A6 72-50-16-14-52-A6 hci0 B1:96:11:68:9C:09 type BR/EDR disconnected with reason 2 [CHG] Device B1:96:11:68:9C:09 ServicesResolved: no [CHG] Device B1:96:11:68:9C:09 Connected: no [bluetooth]#trust B1:96:11:68:9C:09 [CHG] Device B1:96:11:68:9C:09 Trusted: yes Changing B1:96:11:68:9C:09 trust succeeded [bluetooth]#connect B1:96:11:68:9C:09 Attempting to connect to B1:96:11:68:9C:09 hci0 B1:96:11:68:9C:09 type BR/EDR connected eir_len 34 [CHG] Device B1:96:11:68:9C:09 Connected: yes [NEW] Endpoint /org/bluez/hci0/dev_B1_96_11_68_9C_09/sep1 [NEW] Endpoint /org/bluez/hci0/dev_B1_96_11_68_9C_09/sep2 [NEW] Transport /org/bluez/hci0/dev_B1_96_11_68_9C_09/sep1/fd0 [CHG] Transport /org/bluez/hci0/dev_B1_96_11_68_9C_09/sep1/fd0 Delay: 0x05dc (1500) Connection successfulII代]# [CHG] Device B1:96:11:68:9C:09 ServicesResolved: yes [联想thinkplus-HE05X II代]#quit • Step 4: Start pipewire and wireplumber Service then list and choose default Audio Source/Sink Card root@imx8mpevk:~#systemctl --user start pipewire wireplumber root@imx8mpevk:~#wpctl status PipeWire 'pipewire-0' [1.0.5, root@imx8mpevk, cookie:831282980] Clients: 32. WirePlumber [1.0.5, root@imx8mpevk, pid:1528] 40. WirePlumber [export] [1.0.5, root@imx8mpevk, pid:1528] 87. wpctl [1.0.5, root@imx8mpevk, pid:1552] Audio -Devices: 41. Built-in Audio [alsa] 42. Built-in Audio [alsa] 43. Built-in Audio [alsa] 44. Built-in Audio [alsa] 45. Built-in Audio [alsa] 81. 联想thinkplus-HE05X II代 [bluez5] -Sinks: 47. Built-in Audio Mono [vol: 0.40] 48. Built-in Audio Stereo [vol: 0.40] 50. Built-in Audio Stereo [vol: 0.40] 58. Built-in Audio Digital Stereo (IEC958) [vol: 0.40] * 82. 联想thinkplus-HE05X II代 [vol: 0.40] -Sources: 46. Built-in Audio Mono [vol: 1.00] 49. Built-in Audio Stereo [vol: 1.00] 51. Built-in Audio Stereo [vol: 1.00] * 59. Built-in Audio Digital Stereo (IEC958) [vol: 1.00] -Filters: -Streams: Video -Devices: 52. mxc-isi-m2m_v1 [v4l2] 53. vsi_v4l2enc [v4l2] 54. vsi_v4l2dec [v4l2] Streams: Settings Default Configured Devices: root@imx8mpevk:~#wpctl set-default 82 root@imx8mpevk:~#wpctl set-default 59 root@imx8mpevk:~# wpctl status PipeWire 'pipewire-0' [1.0.5, root@imx8mpevk, cookie:831282980] Clients: 32. WirePlumber [1.0.5, root@imx8mpevk, pid:1528] 40. WirePlumber [export] [1.0.5, root@imx8mpevk, pid:1528] 87. wpctl [1.0.5, root@imx8mpevk, pid:1572] Audio 41. Built-in Audio [alsa] 42. Built-in Audio [alsa] 43. Built-in Audio [alsa] 44. Built-in Audio [alsa] 45. Built-in Audio [alsa] 81. 联想thinkplus-HE05X II代 [bluez5] 47. Built-in Audio Mono [vol: 0.40] 48. Built-in Audio Stereo [vol: 0.40] 50. Built-in Audio Stereo [vol: 0.40] 58. Built-in Audio Digital Stereo (IEC958) [vol: 0.40] * 82. 联想thinkplus-HE05X II代 [vol: 0.40] 46. Built-in Audio Mono [vol: 1.00] 49. Built-in Audio Stereo [vol: 1.00] 51. Built-in Audio Stereo [vol: 1.00] * 59. Built-in Audio Digital Stereo (IEC958) [vol: 1.00] 分区Bluetooth 的第4 页 * 59. Built-in Audio Digital Stereo (IEC958) [vol: 1.00] Streams: Video 52. mxc-isi-m2m_v1 [v4l2] 53. vsi_v4l2enc [v4l2] 54. vsi_v4l2dec [v4l2] Streams: Settings Default Configured Devices: 0. Audio/Sink bluez_output.B1_96_11_68_9C_09.1 1. Audio/Source alsa_input.platform-sound-xcvr.iec958-stereo Step 5: Copy、Play and Enjoy Music Drag the music file yesterday-once-more.wavto I.MX8MP-EVK board by connecting Windows PC and I.MX8MP-EVK board into one local area network. root@imx8mpevk:~# pw-play -v ./yesterday-once-more.wav sndfile: opened file "yesterday-once-more.wav" format 00010002 channels:2 rate:44100 sndfile: using default channel map: FL,FR PCM: fmt:s16 rate:44100 channels:2 width:2 rate:44100 latency:4410 (0.100s) connecting playback stream; target=(null) stream state changed unconnected -> connecting stream param change: Spa:Enum:ParamId:Latency stream param change: Spa:Enum:ParamId:Tag stream param change: Spa:Enum:ParamId:Props stream properties: application.name = "pw-play" node.name = "pw-play" media.software = "Lavf58.29.100" media.format = "WAV (Microsoft)" node.rate = "1/44100" node.latency = "4410/44100" media.type = "Audio" media.category = "Playback" media.role media.filename = "yesterday-once-more.wav" media.name = "yesterday-once-more.wav" stream.is-live = "true" node.want-driver = "true" node.autoconnect = "true" media.class = "Stream/Output/Audio" remote 0 is named "pipewire-0" stream state changed connecting -> paused stream param change: Spa:Enum:ParamId:Props stream param change: Spa:Enum:ParamId:Latency stream param change: Spa:Enum:ParamId:Latency stream param change: Spa:Enum:ParamId:Format stream state changed paused -> streaming stream set volume to 1.000 -success stream node 88 stream time: now:0 rate:1/48000 ticks:0 delay:9248 queued:0 buffered:0 buffers:0 avail:2 size:0 stream time: now:4821374572568 rate:1/48000 ticks:49152 delay:9248 queued:1882 buffered:32 buffers:1 avail:1 size:1882 stream time: now:4822355905886 rate:1/48000 ticks:96256 delay:9248 queued:1882 buffered:32 buffers:1 avail:1 size:1882 stream time: now:4823379905870 rate:1/48000 ticks:145408 delay:9248 queued:1881 buffered:32 buffers:1 avail:1 size:1881 Finished By Christine.Li Jul 22th,2026.
View full article
Example SJA1110 FreeRTOS lwIP SJA1110-EVM S32DS 3.5 RTD 1.0.2 ********************************************************************************* * Detailed Description: * Updated the example lwip_FreeRTOS_SJA1110 for board SJA1110-EVM * to enable ping from the command window, from all applicable ports * *ping 192.168.0.200 * *Pinging 192.168.0.200 with 32 bytes of data: *Reply from 192.168.0.200: bytes=32 time=2ms TTL=255 *Reply from 192.168.0.200: bytes=32 time=1ms TTL=255 *Reply from 192.168.0.200: bytes=32 time=1ms TTL=255 *Reply from 192.168.0.200: bytes=32 time=1ms TTL=255 * *Ping statistics for 192.168.0.200: * Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), *Approximate round trip times in milli-seconds: * Minimum = 1ms, Maximum = 2ms, Average = 1ms * * Installed packages to S32DS 3.5 update 14: * SW32SJA11xx_S32DS_3.5.0_RFP_D2206.zip * SJA11XX_RTD_4.4_1.0.1_P02_HF01_D2510_DesignStudio_updatesite.zip * SW32SJA1110_XJA11XX_ETH_PHY_4.4_1.0.8_CD01_D2509_DesignStudio_updatesite.zip * SJA11XX_ETH_SWITCH_4.4_1.0.2_CD01_D2509_DesignStudio_updatesite.zip * SW32SJA11xx_FreeRTOS_11.1.0_0.8.0_CD2_D2411_DesignStudio_updatesite.zip * SJA11XX_TCPIP_2.0.0_CD01_D2510_DesignStudio_updatesite.zip * * EVB: * - Except SW15, All DIP switches accordingly to um575112-AH1901 SJA1110 - EVM User Manual(1.2).pdf * - TJA1101 needs to be in Managed Operation, RMII mode (50 MHz output on REF_CLK) * SW15.1-8: ON OFF ON OFF ON OFF OFF ON * * Configuration: * - Updated switch configuration * - Updated phy configuration * - Fixed Mcu/McuModuleConfiguration/McuPowerControlUnit - 1V8 and 2V5 * - Fixed Eth configuration * * * * - TCPIP stack: enabled UDP_ECHO, etc. * - Added Gpio_Dio * - Added nvm_metadata * - MAC learning is disabled * - Added LED control via I2C GPIO expander * (adopted & fixed from SJA1110_gptp_ds example - SW32SJA11xx_M7_gPTP_1_0_0_D2411_DesignStudio_updatesite.zip) * * main.c * - Updated only the header * device.c/h * - adopted from SJA1110_gptp_ds example * test.c * - Removed the code that shuts down the TCP/IP stack after its predefined timeout * - Added LED ALIVE * - Added debug stuff * /board + /pca950x + /swi2c * - adopted from SJA1110_gptp_ds example * * ----------------------------------------------------------------------------- * Test HW: SJA1110-EVM SCH REV B2 * MCU: SJA1110 * Debugger: Lauterbach TRACE32 * Target: RAM or external FLASH (flash_image.bin generated) * EVB connection: any port (excluding SFP cages) <-> RDDRONE T1ADAPT (on ports where applicable) <-> USB-to-Ethernet adapter <-> Laptop DELL, Windows 11
View full article
S32G-VNP-RDB3: Onchip debugging support Hello, I want to debug my AUTOSAR Operating System based application on following environment. 1) Board Name: S32G-VNP-RDB3 2) Microcontroller Variant: S32G399 3) Cortex-M7 Cores 4) Host: Windows Is there any on-chip debugging support enabled in the mentioned board where I can connect without any external debugger or probe. If on-chip debugging support is not available on this board then can I debug with S32 debug probe (H/W) and s32 design studio IDE (S/W) ? With Regards, Madhusudan Gupta Re: S32G-VNP-RDB3: Onchip debugging support Hello, @madhusudangupta007  Thanks for your post. 1. There is no onchip debugger on RDB3, so it is not supported to directly debug the RDB3 via the USB port. 2. Commonly, the Lauterbach TRACE32 Debug is used for debugging the S32G products, besides, the S32 Debug Probe which is provisioned by NXP(S32 Debug Probe | NXP Semiconductors) is also used. 3. Yes, as mentioned before, the S32 debug probe(HW) and S32 Design Studio(IDE) could be used together for debugging the RDB3 board.    BR Chenyin
View full article
i2c problems during wakeup frum suspend A question for the experts out there. I have a circuit in which several push-button switches are connected to a GPIO expander. My current system is based on an IMX8MP, to which this GPIO expander is connected via I²C. This expander has an interrupt line to the IMX8MP. Often, when I put the system into suspend mode and press one of the push buttons (the expander is also marked as a wake-up source in the device tree), I receive this message hundreds or even thousands of times as soon as the system comes out of suspend: [ 117.113106] pca953x 3-0076: failed reading register. I know there was already a patch for a similar issue in the i2c-imx.c driver, and I’ve applied it. However, it isn’t having the desired effect. What can I do about this? P.S. It doesn’t happen all the time, but it can be reproduced relatively quickly. Best regards R. Re: i2c problems during wakeup frum suspend I use Kernel Version 6.6.23 Re: i2c problems during wakeup frum suspend Hi @RRD101  Based on your description, it seems like you could try this commit. Also, which kernel version are you using? Best Regards, Zhiming
View full article
ADT7420 temperature sensor can't work with frdm_mcxw72 board Hi, i tried to run the adt7420 sample demo with frdm_mcxw board, but the print message is "sensor: device not ready.“ after i flashed the image into the target . the hardware setup like below picture for reference  i think the hardware wiring is ok which i followed below description. and you can find the overlay file which i added the board folder like below i also attached the build log file which can help get more information from it.  can you check it and help solve the issue Re: ADT7420 temperature sensor can't work with frdm_mcxw72 board Hello, hope you are doing well.   From the image you shared, it looks like you are working with a KW47-LOC board, could you please confirm this is the right device? Which Zephyr repo and version you are working with? As you may know, the KW47-LOC board is not directly supported on Zephyr, only the frdm-mcxw72 is. That said, since the chips are compatible, you can work with the frdm-mcxw72 examples and modify the overlay file to adapt it to the KW47-LOC board pins. Checking your overlay configuration, the KW47-LOC board only supports the LPI2C1 module, so you will have to enable the lpi2c1 node in your overlay instead. For the SCL and SDA pins, these are defined in frdm_mcxw72-pinctrl.dtsi as PTB4 and PTB5 for I2C1, I would recommend keeping those since they match the KW47-LOC pins. In order for J2 pin 6 to connect to the target MCU pin PTB4, place J24 2-3 shorted.   Refer to UM12114 for the MikroBUS I2C pinout: Pin 2: INT (Hardware interrupt) on WUU0_P12/PTC7 Pin 5: SCL (I2C clock) on I2C1_SCL Pin 6: SDA (I2C data) on I2C1_SDA   Please also confirm that you have the following configurations enabled in your prj.conf file: CONFIG_I2C=y CONFIG_SENSOR=y CONFIG_ADT7420=y   Best regards, Ana Sofia. Re: ADT7420 temperature sensor can't work with frdm_mcxw72 board Hi Ana Thanks for your support.  Yes, I did work with a KW47-LOC board and try to run the frdm-mcxw72 examples on this board, the Zephyr repo version is v4.4.1. After change the overlay file from I2C0 into I2C1,  it looks the ADT7420 device initialize is ok, but this sensor is still can't read out the right temperature , you can see  below print message from the serial monitor.  here is the latest overlay file and prj.conf file content. Best regards Liu Wei
View full article
S32K312 HSE Secure Boot: Can pInstAuthTag Point to a Signature Stored in the UTEST DCF Record Area? Hello NXP Support Team, We are implementing HSE-based Secure Boot with SMR on the S32K312 and would like to confirm whether an SMR signature can be permanently stored in the UTEST DCF record area. Our current implementation is as follows: We store a 512-byte RSA-4096 signature in UTEST, starting at address: 0x1B001A00U The occupied address range is: 0x1B001A00 to 0x1B001BFF This region belongs to the UTEST DCF record area. Our project does not require any DCF configuration in this area. Therefore, we are currently considering using the unused DCF record space to store permanent security data, including the public key and the SMR signature. Since the software image and its signature are fixed in our use case, the signature is not expected to change during the product lifetime. In the SMR Entry, we configure the signature reference as follows: smrEntry.pInstAuthTag[0] = 0x1B001A00U; smrEntry.pInstAuthTag[1] = 0U; Our expectation is that, during subsequent Secure Boot verification, HSE will read the 512-byte signature directly from the UTEST address specified by pInstAuthTag[0]. When installing the SMR Entry through HSE_SRV_ID_SMR_ENTRY_INSTALL, we initially configured the installation service authentication tag to reference the same UTEST address: pSmrEntryInstall->pAuthTag[0] = 0x1B000A00U; However, the SMR installation service returned HSE_SRV_RSP_INVALID_PARAM, apparently because the UTEST address was rejected as an invalid input address for the service. As a workaround, before calling the SMR installation service, we copy the 512-byte signature from UTEST into a shared RAM buffer: UTEST 0x1B000A00 | | Copy 512 bytes v Shared RAM buffer We then configure the installation request as follows: pSmrEntryInstall->pAuthTag[0] = PTR_TO_HOST_ADDR(signatureRamBuffer);   pSmrEntryInstall->authTagLength[0] = 512U; The SMR Entry itself still contains: smrEntry.pInstAuthTag[0] = 0x1B000A00U; With this configuration, HSE_SRV_ID_SMR_ENTRY_INSTALL returns success and the SMR Entry is installed successfully. Could you please clarify the following questions? Is 0x1B001A00U a valid address for hseSmrEntry_t.pInstAuthTag[0] on the S32K312? During a subsequent Secure Boot, can HSE_B directly access the UTEST DCF record area and read the signature referenced by pInstAuthTag[0]? Does a successful HSE_SRV_ID_SMR_ENTRY_INSTALL response confirm that the persistent pInstAuthTag[0] address is valid for later boot-time SMR verification, or does the installation service only verify the signature supplied through hseSmrEntryInstallSrv_t.pAuthTag[0]? Is there a difference between the memory regions accepted for: hseSmrEntryInstallSrv_t.pAuthTag[0] and: hseSmrEntry_t.pInstAuthTag[0] In our test, the UTEST address is rejected when used directly as pAuthTag[0], but the SMR installation succeeds when the same signature is copied to RAM while pInstAuthTag[0] still points to UTEST. Could this configuration pass SMR installation but fail during the next reset or Secure Boot because HSE cannot access the UTEST address at boot time? Is the unused UTEST DCF record area allowed to store customer application data such as a public key or an SMR signature when no DCF records are required by the project? Could using this DCF record area cause any conflict with HSE firmware, ROM boot code, future DCF processing, lifecycle transitions, debug configuration, or device configuration scanning? Are there any alignment, record-format, ECC, programming, locking, or access restrictions for storing a raw 512-byte signature in this UTEST area? If UTEST is not supported for pInstAuthTag[0], should the persistent SMR signature always be stored in normal application Code Flash or Data Flash? The main point we would like to confirm is whether the following configuration is officially supported and safe for production: /* Persistent signature location used during Secure Boot / smrEntry.pInstAuthTag[0] = 0x1B000A00U;   / Temporary RAM copy used only during SMR installation */ pSmrEntryInstall->pAuthTag[0] = PTR_TO_HOST_ADDR(signatureRamBuffer);   pSmrEntryInstall->authTagLength[0] = 512U; MCU: S32K312 HSE type: HSE_B Signature algorithm: RSASSA-PSS with RSA-4096 Signature length: 512 bytes Persistent signature address: 0x1B001A00U Thank you. Re: S32K312 HSE Secure Boot: Can pInstAuthTag Point to a Signature Stored in the UTEST DCF Record Ar sorry the Signature location is not 0x1B000A00U. it is 0x1B001A00U. Re: S32K312 HSE Secure Boot: Can pInstAuthTag Point to a Signature Stored in the UTEST DCF Record Ar Hi @Yiming2  I tested it on my board because it is not explicitly mentioned in the documentation if UTEST can be used or not. And I got similar results. If pAuthTag = pInstAuthTag = 0x1B001A00, I got HSE_ SRV_ RSP_ INVALID_ ADDR response. Then I placed pAuthTag into RAM memory while pInstAuthTag was pointing still to UTEST and this works. Once secure boot is enabled by BOOT_SEQ bit, secure boot is successful, application is working. HSE is able to read the signature in UTEST DCF area. Based on the test results, HSE firmware obviously checks if address pAuthTag falls within RAM or code/data flash memory while pInstAuthTag in UTEST is accepted. It’s not documented but it works. But if you do not plan to update the signature, an option is to keep HSE_SMR_CFG_FLAG_INSTALL_AUTH zero, so internal verification scheme (internal hash) would be used for verification. Your signature would be used only for installation and pInstAuthTag would be ignored. In my opinion, this setup makes more sense if you do not plan to update the image. Also the verification would be much faster (hash vs. RSA algorithm). This is probably the best way to keep it simple and to get better performance. If HSE_SMR_CFG_FLAG_INSTALL_AUTH is set and pInstAuthTag is used, this targets mainly a use-case when you want to easily update an application: application and authentication tag is updated and you do not need to modify or reinstall that SMR. DCF is scanned up to stop record (all 0xFF’s), the rest is ignored. Normally the DCF area is not supposed to be used for user data but I can’t see a problem here. The only restriction for UTEST is that it is OTP area. And the same ECC limitations apply (like for code or data flash) – once an aligned double word is programmed, you should not program the same double word again because it would cause ECC error. Regards, Lukas
View full article
IMX95 failed to reparent can1 I tried to enable can1 my device tree pin is follow imx95 evk, and disable  &micfil IMX95_PAD_PDM_CLK__AONMIX_TOP_CAN1_TX  0x39e IMX95_PAD_PDM_BIT_STREAM0__AONMIX_TOP_CAN1_RX  0x39e , but the following error occurred.  [ 9.968941] CAN device driver interface [ 9.976800] scmi-pinctrl-imx scmi_dev.8: Error set config -13 [ 9.976814] scmi-pinctrl-imx scmi_dev.8: pin_config_set op failed for pin 121 [ 9.976893] clk: failed to reparent can1 to syspll1_pfd1_di: -1 [ 9.978973] Internal error: synchronous external abort: 0000000096000010 [#1] SMP [ 9.978986] Modules linked in: flexcan(+) can_dev neoisp(+) at24 rpmsg_ctrl rpmsg_char pwm_fan enetc4_uio(O) fsl_ecat_enetc4 fsl_ecat_enetc_core moal(O) mlan(O) fuse [ 9.979017] CPU: 5 UID: 0 PID: 357 Comm: (udev-worker) Tainted: G M O 6.18.2-rt3-1.0.0-1.0.0 #1 PREEMPT_RT [ 9.979026] Tainted: [M]=MACHINE_CHECK, [O]=OOT_MODULE [ 9.979028] Hardware name: Axiomtek i.MX95 scm136 board (DT) [ 9.979031] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 9.979035] pc : flexcan_read_le+0x0/0x20 [flexcan] [ 9.979060] lr : flexcan_probe+0x454/0x834 [flexcan] [ 9.979067] sp : ffff800086133820 [ 9.979069] x29: ffff800086133850 x28: ffff8000862b0000 x27: ffff000085a182a0 Does anyone know how to fix this? Re: IMX95 failed to reparent can1 Hi,Zhiming_Liu Thank you for the reply. you are right ,I need to change system manager config. Re: IMX95 failed to reparent can1 Hi @HenryHsu  Here is my previous test on i.MX95 EVK, please check your dts with below modifications.   dts modification:     diff --git a/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts b/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts index ab7bd4fdaadf..5eb3011f0894 100644 --- a/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts +++ b/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts @@ -380,7 +380,7 @@ &flexcan1 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_flexcan1>; xceiver-supply = <&reg_can1_stby>; - status = "disabled"; + status = "okay"; }; &flexcan2 { @@ -623,23 +623,23 @@ spidev0: spi@0 { }; }; -&micfil { - #sound-dai-cells = <0>; - pinctrl-names = "default", "sleep"; - pinctrl-0 = <&pinctrl_pdm>; - pinctrl-1 = <&pinctrl_pdm_sleep>; - assigned-clocks = <&scmi_clk IMX95_CLK_AUDIOPLL1_VCO>, - <&scmi_clk IMX95_CLK_AUDIOPLL2_VCO>, - <&scmi_clk IMX95_CLK_AUDIOPLL1>, - <&scmi_clk IMX95_CLK_AUDIOPLL2>, - <&scmi_clk IMX95_CLK_PDM>; - assigned-clock-parents = <0>, <0>, <0>, <0>, - <&scmi_clk IMX95_CLK_AUDIOPLL1>; - assigned-clock-rates = <3932160000>, - <3612672000>, <393216000>, - <361267200>, <49152000>; - status = "okay"; -}; +// &micfil { +// #sound-dai-cells = <0>; +// pinctrl-names = "default", "sleep"; +// pinctrl-0 = <&pinctrl_pdm>; +// pinctrl-1 = <&pinctrl_pdm_sleep>; +// assigned-clocks = <&scmi_clk IMX95_CLK_AUDIOPLL1_VCO>, +// <&scmi_clk IMX95_CLK_AUDIOPLL2_VCO>, +// <&scmi_clk IMX95_CLK_AUDIOPLL1>, +// <&scmi_clk IMX95_CLK_AUDIOPLL2>, +// <&scmi_clk IMX95_CLK_PDM>; +// assigned-clock-parents = <0>, <0>, <0>, <0>, +// <&scmi_clk IMX95_CLK_AUDIOPLL1>; +// assigned-clock-rates = <3932160000>, +// <3612672000>, <393216000>, +// <361267200>, <49152000>; +// status = "okay"; +// }; &mu7 { status = "okay"; @@ -960,19 +960,19 @@ IMX95_PAD_GPIO_IO35__HSIOMIX_TOP_PCIE2_CLKREQ_B 0x4000031e >; }; - pinctrl_pdm: pdmgrp { - fsl,pins = < - IMX95_PAD_PDM_CLK__AONMIX_TOP_PDM_CLK 0x31e - IMX95_PAD_PDM_BIT_STREAM0__AONMIX_TOP_PDM_BIT_STREAM_BIT0 0x31e - >; - }; + // pinctrl_pdm: pdmgrp { + // fsl,pins = < + // IMX95_PAD_PDM_CLK__AONMIX_TOP_PDM_CLK 0x31e + // IMX95_PAD_PDM_BIT_STREAM0__AONMIX_TOP_PDM_BIT_STREAM_BIT0 0x31e + // >; + // }; - pinctrl_pdm_sleep: pdmsleepgrp { - fsl,pins = < - IMX95_PAD_PDM_CLK__AONMIX_TOP_GPIO1_IO_BIT8 0x51e - IMX95_PAD_PDM_BIT_STREAM0__AONMIX_TOP_GPIO1_IO_BIT9 0x51e - >; - }; + // pinctrl_pdm_sleep: pdmsleepgrp { + // fsl,pins = < + // IMX95_PAD_PDM_CLK__AONMIX_TOP_GPIO1_IO_BIT8 0x51e + // IMX95_PAD_PDM_BIT_STREAM0__AONMIX_TOP_GPIO1_IO_BIT9 0x51e + // >; + // }; pinctrl_ptn5110: ptn5110grp { fsl,pins = <     system manager modification: diff --git a/configs/mx95evk.cfg b/configs/mx95evk.cfg index 9250d02..6722097 100755 --- a/configs/mx95evk.cfg +++ b/configs/mx95evk.cfg @@ -389,7 +389,7 @@ SYS ALL # Resources M7P OWNER # CPUs must be first -CAN_FD1 OWNER +// CAN_FD1 OWNER FSB READONLY IRQSTEER_M7 OWNER LPIT1 OWNER @@ -612,6 +612,7 @@ CAMERA5 OWNER CAMERA6 OWNER CAMERA7 OWNER CAMERA8 OWNER +CAN_FD1 OWNER CAN_FD2 OWNER CAN_FD3 OWNER CAN_FD4 OWNER   Result:  
View full article
关于安装IDE和RTD遇到的问题 你好,我安装了S32DSIDE 3.6.6软件 然后我又安装了RTD包 但是我在新建application project时找不到SDK,如下图 这个问题困扰我很久了,期待回复,谢谢,我的电脑配置如下 电脑上装了JDK 8和JDK17, Python 13 14 15   Re: 关于安装IDE和RTD遇到的问题 谢谢,我发现了这个问题,然后我就想装gcc-10.2,我找到了关于编译器的网页 我不知道使用哪一个,所以我下载了这两个EXE文件进行安装 但是安装完成之后,在S32DS软件中新建工程发现还是没有gcc-10.2 然后我就想在扩展包管理器中下载,但是我试了很多次下载过程中总是报错,无法下载成功,请指导我下一步该怎么做,谢谢~~~ Re: 关于安装IDE和RTD遇到的问题 抱歉,过去两天是周末,这是我今天早上又试着装了一次报的错 Re: 关于安装IDE和RTD遇到的问题 你好@YangLuYao , 抱歉回复晚了。从图片来看,您似乎正在尝试安装 NXP GCC 6.3.1(版本 1620),但实际上您应该安装 v10.2(版本 1728): 如果这仍然不起作用,我想你可以尝试从外部安装它:在 S32 设计工作室中安装软件。 我会检查以下几点: 安装过程中网络不稳定。 工作场所的代理/防火墙。 防病毒/网络安全检查。 磁盘空间。 除此之外,我就不确定根本原因是什么了。您可以尝试重新安装 S32DS,然后再次尝试安装 NXP GCC 10.2。 此致, 朱利安 Re: 关于安装IDE和RTD遇到的问题 嗨@YangLuYao , 无需下载独立组网 (SA) 工具链。S32DS 已提供 NXP GCC 10.2: 选择工具链后,点击“安装/更新 1 个项目”,点击“下一步”,S32DS 将提示您重新启动。重启后,您应该可以看到它已安装: 如果发现任何错误,能否告知一下? 此致, 朱利安 Re: 关于安装IDE和RTD遇到的问题 我已经解决了这个问题,谢谢~~
View full article
S32K1 Complementary PWM Hi,NXP experts We used the S32K142 chip in the air conditioning compressor project of Nissan. However, Nissan requested to know how the FTM of the chip ensures the achievement of complementary PWM output. Therefore, they would like to ask for assistance in providing explanations and supporting materials, or test reports for the verification of this function. Thank you. Re: S32K1 Complementary PWM Hi@Chenxu1 the chip-level protection is mainly architectural: one channel defines the PWM timing, the companion channel is produced by internal complement logic, and optional dead-time/synchronized-update hardware preserves non-overlap and coherent updates. S32K-RM Rev14.1: Re: S32K1 Complementary PWM Hi, Senlent, Tkx for your reply. We are clear about how FTM outputs complementary PWM. At the chip level, how does it ensure that the complementary waveforms are not out of position? This is what our customers are interested in knowing. Re: S32K1 Complementary PWM Hi@Chenxu1 It can read and test AN5303 and its provided bare-metal code. https://www.nxp.com/docs/en/application-note/AN5303.pdf These are some steps I recorded during my previous testing, for your reference. I set up complementary PWM mode and inserted a 2µs dead time (I forgot to save the complete project, but the modification is very simple).
View full article
i.MX RT1170 SDRAM Configuration from SDK Example: Auto-Refresh Disabled? Hello NXP Team, we created the SDRAM configuration for our custom i.MX RT1170 based hardware using the MCUXpresso SDK example as a reference: https://github.com/nxp-mcuxpresso/mcuxsdk-examples/blob/main/_boards/evkbmimxrt1170/demo_apps/shell/shell.mex Our design uses an ISSI IS42S16320F SDRAM connected to the SEMC interface. Unfortunately, we are experiencing occasional system instabilities with this configuration. While reviewing the SDRAM settings in detail, we noticed that Auto-Refresh appears to be disabled in the example configuration: This surprised us, because according to our understanding the IS42S16320F requires periodic refresh cycles to maintain data integrity, and therefore we would expect Auto-Refresh to be enabled. Could you please clarify the following points? Is it correct that Auto-Refresh is intentionally disabled in the provided SDK example? If so, what is the rationale behind this configuration? Are SDRAM refresh cycles handled elsewhere by the SEMC controller or software initialization code? For an ISSI IS42S16320F on a custom hardware design, would you recommend enabling Auto-Refresh explicitly? Thank you for your support. Best regards, i.MXRT 101x Re: i.MX RT1170 SDRAM Configuration from SDK Example: Auto-Refresh Disabled? Hello @Masmiseim, The DCD configuration provided in the example is implemented for the SDRAM used on the RT1170-EVKB. As you may know, each SDRAM device has its own timing requirements and initialization parameters, so the SEMC configuration included in the example may not be fully compatible with your specific SDRAM. In this example, the Auto Refresh feature is enabled as part of the final SDRAM initialization sequence. However, during the initialization process itself, the Auto Refresh bit remains disabled and the required refresh operations are performed through SEMC IP commands, as shown in the images below: If you would like to customize these settings for your SDRAM, the DCD can be generated using the MCUXpresso Config Tools. This allows you to configure the SDRAM parameters according to your device requirements, as illustrated in the following image:   On the other hand, there is available an SDK (version 26.06) example called "semc_cm7" which demonstrates how use the SEMC peripheral with an external SDRAM. Finally, in this community post Omar provides an example for configure the SEMC registers that could be useful. BR Habib Re: i.MX RT1170 SDRAM Configuration from SDK Example: Auto-Refresh Disabled? It's always wise to treat anything you attempt to use from the SDK as just an example and therefore you should check & verify everything.
View full article
Unable to Configure Tasks and ISRs in AUTOSAR OS for S32K144 Hi, I am currently integrating the AUTOSAR OS on the S32K144 MCU and have installed the S32K_AUTOSAR_OS_4_0_98_RTM_1_0_0 DTM package. After importing the OS module into EB tresos, I can only see the OSCounter container in the configuration editor. However, the OS User Manual describes additional configuration elements such as Tasks, ISRs, and other OS objects. Could you please clarify: Why are only OSCounter configurations visible in EB tresos? Is there any additional plugin, license, or configuration step required to enable Task and ISR configuration? What is the correct procedure for creating and configuring Tasks and ISRs for the S32K144 AUTOSAR OS? Also I want to configure task, ISR and OS related configuration. Any guidance or example project would be greatly appreciated. Thanks Re: Unable to Configure Tasks and ISRs in AUTOSAR OS for S32K144 Hi @Julián_AragónM , Thank you for your response. Currently I'm using v29.0.0 version of EB Tresos Could you please suggest the appropriate RTD version that is compatible with this EB tresos release? Thank you for your support. Best Regards, Devi Re: Unable to Configure Tasks and ISRs in AUTOSAR OS for S32K144 Hi @Devi_55, SW32K14-OS401-RTM-1.0.0 b4.0.98 is legacy SW and no longer maintained. It is strongly recommended to transition to the newer RTDs (Real-Time Drivers for S32K1). For any further assistance or support, please reach out to your NXP representative.  After installing SW32K14-OS401-RTM-1.0.0 b4.0.98 RTM, I can see all of the included ones below. The release notes for this SW package mentions EB Tresos v21.0.0, pelase confirm you are using this build.   EB tresos Studio 21.0.0 b160607-0933  Best regards, Julián Re: Unable to Configure Tasks and ISRs in AUTOSAR OS for S32K144 Hi @Devi_55, Latest release of RTD for S32K1 (S32K1_S32M24x Real-Time Drivers AUTOSAR R21-11 Version 3.0.0 QLP07) uses EB Tresos v29.0.0: Best regards, Julián Re: Unable to Configure Tasks and ISRs in AUTOSAR OS for S32K144 Hello  I apologize; this was an oversight by my part.  RTD 3.0.0 QLP07 is the crypto release for the RTD drivers, QLP06 contains all of the base drivers (Adc, Can, Os, etc.): Best regards, Julián Re: Unable to Configure Tasks and ISRs in AUTOSAR OS for S32K144 Hello @Julián_AragónM , I have installed the S32K1_S32M24x Real-Time Drivers AUTOSAR R21-11 Version 3.0.0 QLP07 package, which is compatible with EB tresos v29.0.0. However, after reviewing the available plugins, I could not find several expected modules such as OS, ADC, Port, Dio, Spi, Can, Mcu, and other MCAL components. Could you please suggest which RTD/AUTOSAR package I should use if I need access to the complete set of MCAL drivers along with an AUTOSAR OS? If a different version of EB tresos is required for compatibility, I am willing to install and use the recommended version. I would appreciate your guidance on the appropriate package and toolchain for the S32K144. Thank you. Best Regards, Devi Re: Unable to Configure Tasks and ISRs in AUTOSAR OS for S32K144 Hello @Julián_AragónM  Thank you for your response. I will verify this with the mentioned RTD version. Thanks Best Regards, Devi 
View full article
can we do V/f control of a PMSM? I am making a simulink model for PMSM control by V/f method. This model works for an induction motor but the speed output for PMSM coming oscillating, i think the fields are not synchronizing. Am i missing something? Re: can we do V/f control of a PMSM? Hello, Indeed the fields may not be synchronizing properly. With an induction motor, the rotor slip induces currents in the rotor windings which produce a natural electro-magentic damping effect. Within a PMSM there is no slip, no induced rotor current like in an induction motor, therefore no inherent damping. The rotor PMs must lock exactly to the rotating stator field. The angle between rotor and stator fields behaves like an undamped pendulum resulting in any disturbance causes the rotor to oscillate around sync position. Options to address this: 1. Add an active damping to your V/f model - you can inject the missing damping by modulating the output voltage or frequency based on estimated speed error: estimate rotor speed using a sensor or a sensorless technique feed d(w_error)/dt back to modulate the V/f output amplitude This is the simplest fix if you want to stay with V/f method. 2. Other option would be to move to I/f control where you control the stator current magnitude at a commanded frequency. More information about I/f control on the following page I-F Controller Hope this helps! Best regards, Stefan.
View full article
How to Debug Multi Core with TRACE32 on S32K312? Dear NXP Support, I am currently using TRACE32 to debug an S32K312 device. The S32K312 is configured with two cores (Core 0 and Core 1). I can debug Core 0 without any issues, but I am unable to debug code running on Core 1. As shown in the attached screenshot, I set a breakpoint in the source code executed by Core 1. I also added a counter variable, and I can see that its value keeps increasing, which indicates that the code is indeed running. However, the breakpoint is never hit. Could you please advise how to properly configure TRACE32 to debug both Core 0 and Core 1? If there are any additional settings or initialization steps required for multi-core debugging on the S32K312, I would appreciate your guidance. Here is my file cmm  ; -------------------------------------------------------------------------------- ; @Title: Demo script for S32K312-M7 on S32KXXCVB-176 (FLASH) ; @Description: ; Programs the sieve demo application into the processor internal flash and ; sets up a demo debug scenario. ; This script can be used as a template for flashing an application. ; Prerequisites: ; * Connect Debug Cable to J205 ; or ; Connect Combiprobe/uTrace to J10 ; @Keywords: ARM, Cortex-M7, Flash ; @Author: STK ; @Board: S32KXXCVB-176 ; @Chip: S32K312-M7 ; @Copyright: (C) 1989-2021 Lauterbach GmbH, licensed for use with TRACE32(R) only ; -------------------------------------------------------------------------------- ; $Id: s32k312_sieve_flash.cmm 17943 2021-07-12 15:34:31Z skrausse $ ;WinCLEAR ; -------------------------------------------------------------------------------- ; initialize and start the debugger RESet SYStem.RESet SYStem.CPU S32K312-M7 ;SYStem.CPU MWCT2016S-M7 SYStem.CONFIG.DEBUGPORTTYPE JTAG IF COMBIPROBE()||UTRACE() ( SYStem.CONFIG.CONNECTOR MIPI20T ) SYStem.Option DUALPORT ON SYStem.MemAccess DAP SYStem.JtagClock 10MHz Trace.DISable SYStem.Up ; ECC init for the internal SRAM DO C:\T32\demo\arm\hardware\s32k3\scripts\init_sram.cmm ; -------------------------------------------------------------------------------- ; Flash programming ; prepare flash programming (declarations) DO ~~/demo/arm/flash/s32k3.cmm PREPAREONLY FLASH.ChangeType 0x10016000--0x1003FFFF NOP flash.erase.all FLASH.ReProgram ALL ( Data.LOAD.intelhex "project.hex" ;Data.LOAD.auto * ;Data.LOAD.s1record ; Adding IVT header ;Data.Set 0x00400000++0xF0 %Long 0x0 ; Init table with 0 ;Data.Set 0x00400000 %Long 0x5aa55aa5 ; Magic number ;Data.Set 0x00400004 %Long 0x00000001 ; Boot configuration word (enable M7-0) ;Data.Set 0x0040000C %Long ADDRESS.OFFSET(__nvic_base) ; M7-0 application core start adddress ;Data.Set 0x00400024 %Long 0x00000000 ; LC configuration address ) FLASH.ReProgram OFF ; -------------------------------------------------------------------------------- SYStem.Up Break Data.LOAD.Elf "project.elf" /nocode Go.direct main SYStem.Mode Attach TrOnchip.Set CORERESET OFF ; -------------------------------------------------------------------------------- ; open some windows Mode.Hll Thank you for your support. Re: How to Debug Multi Core with TRACE32 on S32K312? Hi @NghiaLX308  Are we really talking about S32K312? Because this is single core device: Regards, Lukas Re: How to Debug Multi Core with TRACE32 on S32K312? Hello Mr @lukaszadrapa  I’m sorry, that was my mistake. The MCU is S32K322. Re: How to Debug Multi Core with TRACE32 on S32K312? I have two versions in my repository - one for S32K324 which opens two instances of Trace32 and second very simple for S32K396 which uses one instance of Trace32 only and then there are two scripts which can be used to switch between the cores. You can use these scripts as a reference to develop own solution.  Regards, Lukas Re: How to Debug Multi Core with TRACE32 on S32K312? I got it. Thank you Mr @lukaszadrapa . 
View full article
need alternative part number for MRF101AN. I would appreciate if anyone could provide me the alternative part number for MRF101AN.?? And idea on availability for the same for next few years. thank you! Re: need alternative part number for MRF101AN. **MRF101AN Status & Alternatives** ### Current Status **MRF101AN** (NXP) is now in **End-of-Life / Last Time Buy**. | Item | Details | |----------------------------|--------------------------------------| | **Lifecycle** | End of Life (EOL) / Last Time Buy | | **Last Time Buy (LTB)** | **30 September 2026** | | **Last Time Delivery (LTD)** | **30 September 2027** | | **Reason** | NXP is ramping down the Radio Power product line | After September 2026 you will no longer be able to place new orders with NXP. Remaining stock will be allocated on a first-come, first-served basis until the final shipment date in 2027. --- ### Closest Alternatives | Part Number | Manufacturer | Key Differences | Compatibility | Recommendation | |------------------|--------------|------------------------------------------|--------------------------------|--------------| | **MRF101BN** | NXP | Mirror pin-out version of MRF101AN | Same package (TO-220), electrical performance almost identical | Best short-term option if pin-out can be flipped | | **MRF300AN / MRF300BN** | NXP | 300 W version (higher power) | Different package (TO-247) | Only if you need higher power and can redesign | | No official drop-in | — | NXP has **not** released a pin-compatible successor | — | — | **Note**: NXP has not published an official pin-to-pin replacement for the MRF101AN. The **MRF101BN** is the closest device (same electrical characteristics, mirrored pin-out). --- ### Third-party / Competitive Alternatives (not pin-compatible) These require board redesign but are still in active production: - Ampleon BLF188XR / BLF189XRG (higher power, different package) - STMicroelectronics STAC2932B or similar LDMOS devices - Other 50 V LDMOS devices in the 100 W class from Infineon or MACOM (need matching for frequency and power) --- ### Availability Outlook (Next Few Years) | Period | Availability Expectation | |---------------------|----------------------------------------------| | Now – Sep 2026 | Still orderable (Last Time Buy window) | | Oct 2026 – Sep 2027 | Only remaining stock / residual shipments | | After Sep 2027 | No new supply from NXP | **Recommendation**: 1. Place a **Last Time Buy** as soon as possible if you still need this exact part. 2. Start evaluating **MRF101BN** (if pin-out change is acceptable) or begin a redesign to a currently active 50 V LDMOS device. 3. Contact : [email protected]. Would you like me to help compare specific electrical parameters of MRF101AN vs MRF101BN, or suggest possible redesign candidates based on your frequency and power requirements? Re: need alternative part number for MRF101AN. Hi Mingel, MRF101BN won't buy you anything. It's on the same discontinuance notice as the AN, PCN 202603037DN, same 30 September last order date, and so are MRF300AN and BN. After that it's leftover stock, and NXP names no replacement. The one I'd look at is Ampleon's BLP15H9S100Z, 100 W at 50 V, still shows active. Surface mount though, so the board changes. Others we mapped here: https://parter.ai/alternatives/nxp-usa-inc/mrf101an?utm_source=nxp_community Raz, Parter (AI Supply chain app)
View full article
The 30 Second Cherry Trick for Better Sleep I've been seeing a lot of people talking about the 30 Second Cherry Trick for Better Sleep, so I decided to look into what it's actually about. From what I found, it isn't presented as a medication or a quick fix. The idea revolves around a simple nighttime habit involving tart cherries and natural sleep support. Some people like it because it's easy to add to an evening routine and doesn't require making major lifestyle changes. Of course, everyone's sleep challenges are different, and what works for one person may not work for another. Good sleep habits, reducing caffeine late in the day, and maintaining a consistent bedtime are still important. If you're curious about what the 30 Second Cherry Trick actually is and why so many people have been discussing it recently, I found a page that explains the concept in more detail. Learn more here: https://health.smartdiscoveryhub.com/ys1/
View full article