How to use QSPI for M7 on i.MX 8M Plus EVK Hi all, I'm having trouble getting started using the i.MX 8M Plus EVK with QSPI NOR. I've found instructions on how to flash the 8M Mini using "uuu -b qspi firmware.bin", but this doesn't appear to work on  My EVK seems to have come with a boot image loaded into the NOR flash: u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> sf read $loadaddr 0 0x100 device 0 offset 0x0, size 0x100 SF: 256 bytes @ 0x0 Read: OK u-boot=> md $loadaddr 40400000: 412000d1 007e1000 0005fc00 00000000 .. A..~......... 40400010: 007e0fe0 007e0fc0 0080b7c0 00000000 ..~...~......... 40400020: 007e0bc0 0002cc00 00000000 00000000 ..~............. 40400030: 00000000 00000000 00000000 00000000 ................ 40400040: 1400000a d503201f 40200000 00000000 ..... .... @.... Is there an app note regarding how to flash and start the M7 with code in QSPI? Re: How to use QSPI for M7 on i.MX 8M Plus EVK I programmed the flash with flash_debug/hello_world.bin at offset 0. u-boot=> load mmc 1 $loadaddr hello_world.bin 18664 bytes read in 4 ms (4.4 MiB/s) u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> sf erase 0 0x5000 SF: 20480 bytes @ 0x0 Erased: OK u-boot=> sf write $loadaddr 0 $filesize device 0 offset 0x0, size 0x48e8 SF: 18664 bytes @ 0x0 Written: OK Re: How to use QSPI for M7 on i.MX 8M Plus EVK I figured it out... After programming the .bin file to the flash, issuing these commands in U-Boot allow the M7 hello_world app to run: u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> bootaux 0x08000000 ## No elf image at address 0x08000000 ## Starting auxiliary core stack = 0x20020000, pc = 0x0800048D... And I see "hello world." on UART4 (/dev/ttyUSB3).

Debugging app deployed to nor flash Hello  I'm using 1189EVK and loaded freertos hello world cm33 app to vscode.  I want to build, deploy and debug that app. But when deploying vscode shows an error  "Error: ENOENT: no such file or directory, open 'C:\NXP\MCUX_Provi_v9\bin\deviceInfo.json'" and indeed that file is not in that directory (provisioning tool version is 9.0.1). Is that vscode doen't support debugging on flash? Thanks Re: Debugging app deployed to nor flash Hi, Indeed you can have this problem if no rights, the issue is logged and will be addressed soon. In the mean time, please find attached the deviceInfo file. Remove the txt extension, copy it in the location and let me know if the problem is fixed. Regards, Melania.

Can't install S32K3xx Development Package and FreeMASTER Serial Communication Driver version 1.3.0 I have received the S32K3X4EVB-T172.  Question 1: When I tried install the S32DS 3.5.9, I could't  install the S32K3xx Development Package by SW32_S32DS_3.5.9_D2312.zip only showed S32 Design Studio Platform Package and S32 Design Studio Platform Tools Package.  2. Get Software: 2.2 Install the S32K3xx Development Package  Open About S32 Design Studio for S32 Platforms dialog (menu → Help → About S32 Design Studio for S32 Platforms) shows the following as: S32 Design Studio for S32 Platform Version: 3.5 Build id: 231219 (Update 9) Question 2: I have already installed the FreeMASTER 1.3.0 RTM (FMASTERSW32.exe) in Step "2.4 Get the Run-Time Debugging Tool", but I can't install "FreeMASTER Serial Communication Driver version 1.3.0" on S32DS Extensions and Updates dialog (menu → Help → S32DS Extensions and Updates).  The error message shows as following as: Operation details Software being installed: com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400 Missing requirement: com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400 requires 'org.eclipse.equinox.p2.iu; com.nxp.s32ds.s32k3.dev.feature.feature.group 1.0.0' but it could not be found. The installation Details: Package: GDB Client for Arm Embedded Processors 12.1 Build 1702; Version: 1702; Build id: 202309251304 Package: S32 Design Studio Platform package; Version: 3.5.9; Build id: 202312191958 Package: S32K3 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202303311831 Package: S32K3.P01 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202304031555 Package: GNU ARM PEMicro Interface Debugging Support; Version: 5.1.7; Build id: 202112141853 Package: S32 Design Studio Platform Tools package; Version: 3.5.9; Build id: 202312191958 Package: NXP GCC for Arm Embedded Processors Build 1620; Version: 1620; Build id: 202005201521 Package: S32 Design Studio Debugger Core; Version: 3.5.9; Build id: 202312191723 Re: Can't install S32K3xx Development Package and FreeMASTER Serial Communication Driver version 1.3 I have install the FreeMASTER 1.3.0 RTM (FMASTERSW32.exe) after that i had installed the S32K3xx Development Package from SW32K3xx_S32DS_3.5.0_D2303.zip (Upload from previous version S32DS 3.5.3).

部署到 Nor Flash 的调试应用程序 你好 我正在使用 1189EVK 并将 freertos hello world cm33 应用程序加载到 vscode。 我想构建、部署和调试该应用程序。但是部署vscode时显示错误 “错误：ENOENT：没有此文件或目录，打开‘C:\NXP\MCUX_Provi_v9\bin\deviceInfo.json’”，但该文件确实不在该目录中（配置工具版本为 9.0.1）。vscode 不支持在 flash 上调试吗？ 谢谢！

无法安装S32K3xx开发包和FreeMASTER串行通信驱动程序版本1.3.0 我已经收到了S32K3X4EVB-T172。 问题 1 ：当我尝试安装 S32DS 3.5.9 时，我无法通过SW32_S32DS_3.5.9_D2312.zip安装S32K3xx 开发包，仅显示S32 Design Studio 平台包和S32 Design Studio 平台工具包。 2.获取软件：2.2 安装S32K3xx开发包 打开关于 S32 平台的 S32 设计工作室对话框（菜单 → 帮助 → 关于 S32 平台的 S32 设计工作室）显示以下内容： 面向 S32 平台的 S32 设计工作室 版本：3.5 版本号：231219（更新 9） 问题 2 ：我已经在步骤“2.4获取运行时调试工具”，但我无法在S32DS 扩展和更新对话框（菜单 → 帮助 → S32DS 扩展和更新）上安装“FreeMASTER 串行通信驱动程序版本 1.3.0”。 错误信息如下： 操作详情 正在安装的软件：com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400缺少要求：com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400 需要“org.eclipse.equinox.p2.iu；com.nxp.s32ds.s32k3.dev.feature.feature.group 1.0.0”但找不到。 安装详情： 软件包：适用于 Arm 嵌入式处理器 12.1 Build 1702 的 GDB 客户端；版本：1702；构建 ID：202309251304 软件包：S32 Design Studio 平台软件包；版本：3.5.9；版本号：202312191958 软件包：S32K3 RTD AUTOSAR R21-11 版本 3.0.0；版本：3.0.0；版本号：202303311831 软件包：S32K3.P01 RTD AUTOSAR R21-11 版本 3.0.0；版本：3.0.0；版本号：202304031555 软件包：GNU ARM PEMicro 接口调试支持；版本：5.1.7；版本号：202112141853 软件包：S32 Design Studio 平台工具包；版本：3.5.9；版本号：202312191958 软件包：NXP GCC for Arm Embedded Processors Build 1620；版本：1620；版本号：202005201521 软件包：S32 Design Studio Debugger Core；版本：3.5.9；版本号：202312191723 回复：无法安装S32K3xx开发包和FreeMASTER串行通信驱动程序版本1.3 我已经安装了FreeMASTER 1.3.0 RTM (FMASTERSW32.exe)，之后我从 SW32K3xx_S32DS_3.5.0_D2303.zip 安装了 S32K3xx 开发包（从以前的版本 S32DS 3.5.3 上传）。

Another imx8mp 4GB LPDDR uboot question Hello, We have board based on the imx8mp evk that has 4GB LPDDR4 instead of 6G, and I'm trying to understand the correct settings for PHYS_SDRAM_SIZE and the memory devicetree node. The memory module (MT53E1G32D2FW) datasheet lists 32Gb/package, 16Gb dual-channel die. Listed are 2 die, 2 channels per die, and 8 banks per channel. Density: 8Gb per channel, 16Gb per die. I ran the DDR tool and got the timings for the board to boot. Now I need to do the uboot configuration. It seems I have 2 primary options for uboot configuration 3GB/1GB or 2GB/2GB splits. 3GB/1GB split Board header: #define PHYS_SDRAM_SIZE 0xc0000000 /* 3 GB */ #define PHYS_SDRAM_2_SIZE 0x40000000 /* 1 GB */ Device tree: reg = <0x0 0x40000000 0 0xc0000000>, <0x1 0x00000000 0 0x40000000>; or 2GB/2GB split Board header: #define PHYS_SDRAM_SIZE 0x80000000 /* 2 GB */ #define PHYS_SDRAM_2_SIZE 0x80000000 /* 2 GB */ Device tree: reg = <0x0 0x40000000 0 0x80000000>, <0x1 0x00000000 0 0x80000000>; They both seem to boot ok, but I'm not sure which is correct (if any). In this post, there was this was the suggestion: #define PHYS_SDRAM_SIZE 0xC0000000 /* 3 GB */ //This value is the size that you will need for your first die on your memory. In this case 3GB. Since the density of each die on this DDR is 16Gb (2GB), that would indicate that I should use a 2G/2G split. However, in this post, the suggestion was: .xlsx seems as correct. For imx8mp_evk.h suggest to leave "PHYS_SDRAM_SIZE" in default value, This suggestion would indicate that I should use the 3GB/1GB split. Here is another post where the person tried both ways, although their issue was not running the DDR tool first. I've seen both approaches in various board headers in the uboot source tree, which only adds confusion. So my question is whether PHYS_SDRAM_SIZE should be based on the die density (16Gb) value or set  to the size of the imx8mp's first DDR memory map region (3GB)? In other words, is the 3GB/1GB split or 2GB/2GB split correct? i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Another imx8mp 4GB LPDDR uboot question I haven't found anyone yet, but do you have this tool? https://www.nxp.com/design/design-center/development-boards-and-designs/i-mx-evaluation-and-development-boards/config-tools-for-i-mx-applications-processors:CONFIG-TOOLS-IMX I'm pretty sure all we did was generate the initial file by filling in the device info on the DDR screen. After you choose the part number when creating a new project, you go to the DDR screen using the menu at the top. It will load a table that you fill in the module info. This will update the tabs on the right with the .ds and the timing.c files. You can see the tabs I'm talking about in the second screenshot on the tool's main page (see below). I believe these are the settings from the datasheet that go in the table. 8 2 2 32 16 10 3 8 32 2000 0.5 200 5 50 20 Without the pins to run the tool, though, you won't be able to tune the settings or run the validation tests. From experience, you may end up with some very tricky bugs down the road without doing those steps. Re: Another imx8mp 4GB LPDDR uboot question Thanks for your quick response.  Well in theory, the ddr tool can communicate with a board that doesn't have OTG as long as the circuit is configured as USB-Device. The issue is we don't have all the USB pins exposed on our board to make it work like that. That's why I'm searching for the file lpddr4_timing.c obtained for the RAM MT53E1G32D2FW. Re: Another imx8mp 4GB LPDDR uboot question Hi rcossdev, One of our hardware guys was able to generate the details for the config tool by filling in the device info table in the DDR configuration spreadsheet. He used the one from here. From what I remember, we copied the data from the last tab to the config tool to actually generate the c code. Requirements changed and we actually moved over to the mx8mq. I had to clear that workspace to make room due to the size of yocto, so I'll have to see if anyone still has a copy. The caveat is that we never got that board to actually pass all of the config tool's DDR validation tests before switching boards. I know the docs say that OTG is required, but I used the config tool on the board we were working on and the hardware guys later assured me that it did not have OTG. I do remember having to connect both the USB cable and separate usb-serial adapter without any SD cards to get the tools to communicate with the board and load the validation code. I'm not sure why that worked, but it did pass the lower frequency tests for what it's worth. Re: Another imx8mp 4GB LPDDR uboot question Hello jmp, Did you manage to generate the lpddr4_timing.c file? We designed a board based also on the imx8mp using the same RAM (MT53E1G32D2FW) But since we didn't include the OTG circuitry we're unable to run the ddr tool and we're struggling to do the bring-up of the board. I'd really appreciate if you could share your timing file. Thanks! Re: Another imx8mp 4GB LPDDR uboot question Perfect, thank you for the clarification. Re: Another imx8mp 4GB LPDDR uboot question yes, we suggest customer to use 3G+1G, you also can find the definition for DDR4(4G) in the uboot https://github.com/varigit/uboot-imx/blob/imx_v2020.04_5.4.70_2.3.2_var01/include/configs/imx8mp_evk.h but I think if you use 2G should be fine, if 3G+1G works for you why do you struggle with this? just use this, it's fine, you can find imx8mp memory map from reference manual

nor flash にデプロイされたアプリのデバッグ こんにちは 私は1189EVKを使用しており、freertos hello world cm33アプリをvscodeにロードしました。 そのアプリをビルド、デプロイ、デバッグしたいと思います。しかし、vscodeをデプロイするとエラーが表示されます 「エラー:ENOENT:そのようなファイルまたはディレクトリはありません。'C:\NXP\MCUX_Provi_v9\bin\deviceInfo.json'を開いてください」と、実際にはそのファイルがそのディレクトリにありません(プロビジョニングツールのバージョンは9.0.1です)。それはvscodeがフラッシュでのデバッグをサポートしていないのですか? ありがとうございます

S32K3 RTD5.0.0 lpi2c hello! Recently, I updated RTD4.0.0 to 5.0.0, then got problem. In Lpi2c configure page, "I2C Clock Source" don't contains any value.(in RTD4.0.0 it works ok) the RTD error is : Source clock is not enabled in Clock component is that a bug ? or something I didn't configure? 回复： S32K3 RTD5.0.0 lpi2c Hi@Vandarkholme Please add"Clock_Ip_ReferencePoints" and then try again. 回复： S32K3 RTD5.0.0 lpi2c oh, I add clockReference then it worked! In RTD5.0.0 clockReference is key component? RTD4.0.0 not need to configure that component

Difference between EIM and FCCU NCFF Hello, I'm currently learning on how to work with some safety concepts on the S32K344-Q257EVB, namely the FCCU, and i wanted to test it and see how it reacts to faults (in terms of changing states in the Finite State Machine (FSM) and checking the FCCU1/FCCU2 signals with an oscilloscope to see if they get asserted or not). My question is, how should i do that? On the reference manual i have read that the FCCU has some Non-Critical Fault Fake (NCFF) that could be used to achieve that, but there is also an Error Injection Module (EIM) and that is where my confusion begins. What is the difference between both? In which cases should i use one and/instead of the other? Thanks in advance! Best regards, JRodrigues Re: Difference between EIM and FCCU NCFF Hello Peter, Thanks for the clarification. Have a good rest of your day! Best Regards, JRodrigues Re: Difference between EIM and FCCU NCFF Hello, the NCFF referring to "All SRAM ECC uncorrectable error ERM_SRAM or ECC cache memory error.." can act as a fault that "happened in the memory and was then reported to the FCCU"? NCFF will inject the fault only to FCCU fail state machine (FSM). So you can verify the reaction of device in case such fault will come to FCCU. But NCFF will not inject the ECC error physically to ECC mechanism nor to the memory. For such purpose you will you EIM. So if you want to verify the reaction of ECC and reaction path on error in ECC mechanism to FCCU NCFSx, you will need to use EIM. Best regards, Peter Re: Difference between EIM and FCCU NCFF Hi Peter, So, in the S32K3xx_fault_map excel file that comes with the reference manual, the NCFF referring to "All SRAM ECC uncorrectable error ERM_SRAM or ECC cache memory error.." can act as a fault that "happened in the memory and was then reported to the FCCU"? Best Regards, JRodrigues Re: Difference between EIM and FCCU NCFF Hello, You can use for EOUT tests NCFF which can inject the faults to the FCCU. Usually you use it when you want to verify the FCCU reaction on incoming fault. It however cant physically inject fault to peripherals/ memories. In some cases there is inejction dirrectly on tested peripheral or FCCU can inject fault only to the status register like STCU_ERR and not in the test itself. However EIM: The Error Injection Module (EIM) is mainly used for diagnostic purposes. It provides a method for diagnostic coverage of internal memories (for example, system RAM, cache RAMs, and peripheral memories). EIM enables you to induce artificial errors on error-checking mechanisms of a system, such as ECC for RAM read data and parity bits. So EIM will create a physical fault on memory and memory then reports fault to FCCU. This way you can test for example if your ECC mechanism is working correctly, etc... Best regards, Peter

i.MX7 Solo LCD信号とピン配置 ご列席の皆様、 私はここのような同様の問題を抱えています: https://community.nxp.com/t5/i-MX-Processors/i-MX7-LCD-Pinout/m-p/1599101 しかし、私の質問は24ビット幅のLCDインターフェースです。 データシート ( IMX7SCEC Rev. 7, 09/2023 ) にもリファレンス マニュアル ( IMX7SRM Rev. 0.1, 08/2016 ) にも、どのピンが信号 R[0], R[1] に属しているかがわかりません。G[0]、G[1]、....B[0]、...[7]。 この情報は、HW回路を設計するために不可欠です。 ここでは、信号は次のようになります。 LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7] ? つまり、LCD_DATA[00] = B0, LCD_DATA[01]= B1, ....そしてLCD_DATA[22]=R6、LCD_DATA23=R7、それぞれです。私は正しいですか? これらの信号とそのピン配置の具体的な宣言は、ドキュメントのどこで確認できますか。   日時:i.MX7ソロLCD信号とピン配置 こんにちは はい、その通りです。 LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7]  これについては、i.MX7D Sabreの回路図を参照してください。 よろしくお願いします/サルドス、 アルド。

EB：如何在EB中设置优先级分组？ 当我在平台模块中使能Isr的时候，发现最大优先级只能到15，如果优先级设置的大于15的话，EB就会报优先级超出范围的错误。我怎样才能将优先级设置为大于 15？我想知道是否可以在EB中设置优先级组。 这里我使用s32k344和RTD 4.0.0.0

EB 生成コード: modules.h の Marco use_Gpt_moduleSTD_ONに変更することはできません EBにGPT、basenxp、platform、resource、その他のモジュールを追加し、コードを生成した後、Marcoがmodules.hをuse_Gpt_moduleしていることがわかりました。STD_ONに変更することはできません。このマルコをSTD_ONに変更する方法は? 回复: EB 生成コード: Marco use_Gpt_module of modules.hSTD_ONに変更することはできません ここではs32k344を使用しています。

IMXRT685-AUD-EVK debugging issue with JLink it is the first time i use IMXRT685-AUD-EVK, i meet two issues blocking in setup stage by following the Tutorial steps. First Issue: when debugging the example, error message popups as followng snapshot: Spoiler (Highlight to read) the logs from output is captured in attached text file: MCUxpresso_err.txt the logs from output is captured in attached text file: MCUxpresso_err.txt The environment and versions of IDE is as following list: MCUXpressoIDE: 24.9.25 JLink: V810 (installed with MCUXpressoIDE) Windows 10 Pro x64 22H2 Second Issue: failed when use xt-ocd to connect EVB through JLink, "Error: SWD Wait time-out expired!" printed. the template topology.xml is from here , and the modified version (with my serial number) is in attached whole log is as following: Ubuntu 22.04: edmond@ed-ubuntu:/opt/Tensilica/xocd-14.11$ ./xt-ocd -c ./topology.xml XOCD 14.11 2023-04-06 14:43:30 (c) 1999-2024 Cadence Design Systems Inc. All rights reserved. [Debug Log 2024-10-31 10:12:33] Loading module "gdbstub" v2.0.0.12 Loading module "jlink" v2.0.2.0 Using JLINK lib v.69600 Jlink USB Serial Number: 722949484 Connected to Jlink Device: Name:'J-Link LPCXpresso V2 compiled May 2 2023 17:39:56' S/N:722949484 Firmware: J-Link LPCXpresso V2 compiled May 2 2023 17:39:56 Requested/Set TCK: 1000kHz/65534kHz Jlink: Select pipelined SWD SWD-DP with ID 0x6BA02477 Loading module "jtag" v2.0.0.20 Loading module "xtensa" v2.0.0.48 Starting thread 'GDBStub' Listening for GDB connection on port 20000 Initialize XDM driver Error: SWD Wait time-out expired! SWD-DP with ID 0x6BA02477 SWD-DP with ID 0x6BA02477 SWD-DP with ID 0x6BA02477 SWD-DP with ID 0x6BA02477 Error: XDM initialization failed ERROR: Couldn't initialize, exit... other logs from Win11: PS C:\Program Files (x86)\Tensilica\Xtensa OCD Daemon 14.07> .\xt-ocd.exe -c .\topology.xml XOCD 14.07 2021-06-01 19:00:49 (c) 1999-2024 Cadence Design Systems Inc. All rights reserved. [Debug Log 2024-10-30 16:35:38] Loading module "gdbstub" v2.0.0.12 Loading module "jlink" v2.0.2.0 Using JLINK lib v.69600 Jlink USB Serial Number: 722949484 Connected to Jlink Device: Name:'J-Link LPCXpresso V2 compiled May 2 2023 17:39:56' S/N:722949484 Firmware: J-Link LPCXpresso V2 compiled May 2 2023 17:39:56 Requested/Set TCK: 1000kHz/65534kHz Jlink: Select SWD SWD-DP with ID 0x6BA02477 Loading module "jtag" v2.0.0.20 Loading module "xtensa" v2.0.0.48 Starting thread 'GDBStub' Opened GDB socket at port 20000 Initialize XDM driver Error: SWD Wait time-out expired! SWD-DP with ID 0x6BA02477 SWD-DP with ID 0x6BA02477 SWD-DP with ID 0x6BA02477 SWD-DP with ID 0x6BA02477 Error: XDM initialization failed ERROR: Couldn't initialize, exit... Have tried different combination with OS, xtensa ocd versions and JLink versions: Win10, Win11 and Ubuntu 22.04 xtensa ocd version: 14.07, 14.08, 14.11 JLink version: V810, V810C, V696(in another topic, this version fixed similar error, but not mine) Also checked the jumps as default: i.MXRT 600 Re: IMXRT685-AUD-EVK debugging issue with JLink Thanks! @mayliu1  It can work after i upload a hello world demo with DSP enabled through IDE (mimxrt685audevk_dsp_hello_world_usart_cm33) The xt-ocd can connect to DSP now. So I guess that because i bought a new board which was burned with the factory default image (without DSP enabled), but I want to debug DSP directly and ignore running IDE demo in toturial video, then it causes the communication failure. Just an advice to add a tip in guide document that to run hello world with DSP first then to try debugging DSP. Thank you again for your kindly support and your time! That's really helpful to me. Re: IMXRT685-AUD-EVK debugging issue with JLink Hi @e_matthews , Hi , I 'm glade that your project " hello world example" from SDK is well debugging through JLink. Question1: Does it mean JLink connecting to CPU is OK on IDE? Answer: Yes,  If you can debugging, It means CPU is OK on IDE. Question2: But JLink connection from xt-ocd still doen't work, it always show "Error: SWD Wait time-out expired!". Does it mean DSP still not work? Answer:  To reduce power consumption, The DSP core will do not power on  when the RT600 boots. If you want debug a DSP code, the RT600 Arm kernel need execute some code . For the detail description, you can refer to the guide sheet. Wish it helps you. If you still have question about it, please kindly let me know. If your question is solved, please tell me to close this case, thanks. Best Regards mayliu Re: IMXRT685-AUD-EVK debugging issue with JLink Dear @mayliu1  Thank you for advices. For 1, JLink firmware is updated with guide, log as: For 2, JLink commander connection is verified: For 3, hello world example from SDK is well debugging through JLink: Does it mean JLink connecting to CPU is OK on IDE? But JLink connection from xt-ocd still doen't work, it always show "Error: SWD Wait time-out expired!". Does it mean DSP still not work? Best Regards! Edmond Re: IMXRT685-AUD-EVK debugging issue with JLink Hi @e_matthews ， Hi, I have consulted with a RT600 series expert. He give some advices. 1: Please pay attention to the "Getting Started with Xplorer for EVK-MIMXRT685". The path of the "Getting Started with Xplorer for EVK-MIMXRT685" file is in XXX\SDK_2_16_000_EVK-MIMXRT685\docs. Especially, check  chapter 2.6 "2.6 Program LPC-Link2 with SEGGER J-Link", and update JLINK firmware. 2: Try to use J-link-commander to connect the board, whether It can connected. 3: Try to use MCUXpresso IDE create a simple project "mimxrt685audevk_hello_world" , using JLINK to debug, whether the project can run normally. Wish it helps you. If you still have question about it, please kindly let me know. Best Regards mayliu Re: IMXRT685-AUD-EVK debugging issue with JLink Thanks! @mayliu For 1, the "./" means the current path, just inditate where's the topology exist. It should be the same if without it. For 2, i double checked the usbser ID which I used, it was correct and was retrieved from JLink log print as tortuial: 722949484 if I typed the wrong ID, the log was like the following instead of what i've got: Re: IMXRT685-AUD-EVK debugging issue with JLink Dear @e_matthews , I use MIMXRT685-EVK debug, It is similar to  MIMXRT685-AUD-EVK. 1: Please make sure that modify usbser ID in  topology.xml file according to your JLINK. 2: the command is xt-ocd.exe -c topology.xml,  but I see your command is xt-ocd.exe -c .\topology.xml.   Wish it helps you. If you still have question about it, please kindly let me know. Best Regards mayliu Re: IMXRT685-AUD-EVK debugging issue with JLink Dear @mayliu, Thank you for your kindly advice, I will follow your guide to check the toturial from the correct link. On the other hand, I double checked the wrong link that I jumped in: https://www.nxp.com.cn/document/guide/getting-started-with-imxrt685-aud-evk-development-platform:GS-MIMXRT685-AUD-EVK?section=plug-it-in  the only difference between two links: mine is "www.nxp.com.cn" and the video content in the first section are different: And then checking for the SDK version, what i used was for MIMXRT685-AUD-EVK as following: I also rebuild the SDK from the new link. The new downloaded SDK package are identical with my old one: Thank you again for replying! But there is still issue No.2 blocking, and it is not related with SDK. Only Jlink and xt-ocd are involved. Re: IMXRT685-AUD-EVK debugging issue with JLink Dear @e_matthews , Thank you for your interest in the NXP MIMXRT product, I would  like to provide service for you. Please tell me your SDK information, It must be consistent to your Board. From image you post I know your board is MIMXRT685-AUD EVK board , so you should import MIMXRT685-AUD-EVK SDK, not MIMXRT685-EVK SDK, It is very import. Also, I suggest you can refer to this link https://www.nxp.com/document/guide/getting-started-with-imxrt685-aud-evk-development-platform:GS-MIMXRT685-AUD-EVK Wish it helps you. If you still have question about it, please kindly let me know. Best Regards mayliu

HSE FW install for S32K310 i want to install HSE FW to S32K310, based on HSE install demo downloaded from the website, can i just modify the flash configuration in the link command file according to the S32K310? and also want to confirm, is S32K310 using the same HSE FW as S32K311? please provide some detailed guidance about how to modify the reference demo Re: HSE FW install for S32K310 Hi Lukas     you are right , some variables is defined in DTCM    we managed to move them to Sram no cacheable and it works now    Thanks!  Re: HSE FW install for S32K310 Hi Leo, one more thing - it may be caused by DTCM. If data objects used for communication with HSE are located in DTCM, make sure that this switch is turned on: It ensures that DTCM address is translated to DTCM Backdoor address by Crypto driver. That's because HSE cannot see normal DTCM address. Regards, Lukas Re: HSE FW install for S32K310 Hi Leo, 1. What is the frequency of HSE_CLK? If it is configured to 120MHz, try to decrease it to 60MHz. https://community.nxp.com/t5/S32K/HSE-provides-RSP-NOT-SUPPORTED-response/m-p/1712323/highlight/true#M26508 2. Try to disable data cache memory. All the data objects used for communication with HSE must be forced to non-cacheable memory. 3. The S32K3 reference manual says: "Before configuring HSE_CLK, you must wait for the SBAF to enter WFI by reading core status register of HSE CPU (PRTN0_CORE2_STAT)." So, it’s necessary to wait for WFI bit before running clock initialization. I found out that current RTD drivers do not check WFI bit. This was a few months time ago and I can see that this should be included in the drivers in RTD version 5.0.0 and higher. 4. What is the content of HSE GPR register at 0x4039_C028? What is the content of FSR and GSR registers in MU_0? Regards, Lukas Re: HSE FW install for S32K310 Hi Lukas      thank you very much for your reply!     indeed i can read the HSE FW version after i download the project     and the HSE_STATUS_INIT_OK flag is set every time when initialize the HW     however when try to use the Crypto driver    and HSE is not responding to the request, what could be the potential cause of it? Re: HSE FW install for S32K310 Hi @LeoYang-  I usually recommend to create new project directly for used derivative and then port the code. However, I believe that this project will work just with the changes you did. Used features are the same on both derivatives. Yes, the firmware support both S32K310 and S32K311: Regards, Lukas

カスタム RT1170 B で XIP ブート モードを FLEXSPI1 から FLEXSPI2 に変更した後のデバッグ モードの問題 NXPサポートチームの皆さん、こんにちは。 RT1170をベースにしたカスタムボードを使用しており、XIPブートモードをFLEXSPI1からFLEXSPI2に切り替えました。この変更を行った後、次のような必要なすべての変更が適用されたことを確認しました。 ピン配置の調整: FLEXSPI2に関連するすべてのピン構成を更新しました。 周波数設定: XIP の適切なクロック周波数で FLEXSPI2 を設定します。 追加の周辺機器構成:リファレンスマニュアルに記載されているすべての周辺機器とメモリの構成を確認。 問題点: リリース・モードではシステムは正常に動作しますが、 デバッグ・モードを使用できません。FLEXSPI2 からブートすると、デバッグが期待どおりに初期化されません。 FLEXSPI2 に切り替えた後にこのモードに影響を与える可能性のある、デバッグに固有の追加の構成または設定はありますか? この変更の影響を受ける可能性のあるメモリ マップ、クロック セットアップ、またはデバッグ インターフェイスの追加の設定、構成、または特定の領域についてアドバイスをいただけますか。デバッグ機能を適応させるために何が必要かについてのガイダンスをいただければ幸いです。 ご支援いただきありがとうございます i.MXRT 106倍

i.MX7 Solo LCD signals and pinout Ladies and Gentlemen, I have a similar problem like the one here: https://community.nxp.com/t5/i-MX-Processors/i-MX7-LCD-Pinout/m-p/1599101 But, my question is with 24 bit wide LCD interface. I cannot find neither in the datasheet ( IMX7SCEC Rev. 7, 09/2023 ), nor in the reference manual ( IMX7SRM Rev. 0.1, 08/2016 ), which pins belongs to signals R[0], R[1], .... G[0], G[1], .... B[0], ... B[7]. This information is essential to design a HW circuit. Shall I estimate, that the signals are as follows here: LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7] ? I mean LCD_DATA[00] = B0, LCD_DATA[01]= B1, .... and LCD_DATA[22]=R6, LCD_DATA23=R7, correspondingly. Am I correct? Where can I find a concrete declaration of these signals and their pinout in the documentation?   Re: i.MX7 Solo LCD signals and pinout Hello, Yes, it is correct that way: LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7]  You may refer to the i.MX7D Sabre schematic for this. Best regards/Saludos, Aldo.

i.MX7 Solo LCD 信号和引脚排列 女士们，先生们， 我有一个类似的问题，例如： https://community.nxp.com/t5/i-MX-Processors/i-MX7-LCD-Pinout/mp/1599101 但是，我的问题是关于 24 位宽的 LCD 接口。 我在数据表（ IMX7SCEC Rev. 7, 09/2023 ）和参考手册（ IMX7SRM Rev. 0.1, 08/2016 ）中都找不到哪些引脚属于信号 R[0]、R[1]、.... G[0]、G[1]、.... B[0]、... B[7]。 这些信息对于设计硬件电路至关重要。 我估计这里的信号如下： LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7]？ 我的意思是 LCD_DATA[00] = B0，LCD_DATA[01]= B1，.... 并且 LCD_DATA[22]=R6，LCD_DATA23=R7，分别对应。我说得对吗？ 在文档中哪里可以找到这些信号及其引脚排列的具体声明？   回复：i.MX7 Solo LCD 信号和引脚排列 你好， 是的，这样是正确的： LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7] 您可以参考 i.MX7D Sabre 示意图。 致以最诚挚的问候/问候， 阿尔多。

在定制 RT1170 B 上将 XIP 启动模式从 FLEXSPI1 更改为 FLEXSPI2 后，调试模式出现问题 您好，NXP 支持团队， 我正在使用基于 RT1170 的定制板，并进行了以下修改：我将 XIP 启动模式从 FLEXSPI1 切换到 FLEXSPI2。做出此更改后，我确保应用了所有必要的修改，包括： 引脚排列调整：更新了 FLEXSPI2 的所有相关引脚配置。 频率设置：使用适合 XIP 的时钟频率设置 FLEXSPI2。 附加外围设备配置：验证参考手册中概述的所有外围设备和内存配置。 问题： 虽然系统在发布模式下运行正常，但我无法使用调试模式。从 FLEXSPI2 启动时，调试未按预期初始化。 切换到 FLEXSPI2 后，是否有任何特定于调试的附加配置或设置可能会影响此模式？ 您能否就可能受此更改影响的内存映射、时钟设置或调试接口中的任何其他设置、配置或特定区域提供建议？我们将非常感激任何有关调整调试功能所需的指导。 感谢您的支持 i.MXRT 106x

NX3DV221 I/O Hello, Could you confirm if the NX3DV221 analog mux can handle both single-ended and differential signals? The datasheet doesn’t seem to specify this detail. Thank you! Re: NX3DV221 I/O Hello Antonino, Yes, the NX3DV221 may handle both single-ended and differential signals. BRs, Tomas

S32G2 LINUX-BSP and SJA1110 Hello,         I can‘t clearly understand the  SPI communication between S32G274A and SJA1110：         1、What is the DSA driver? If I enable it, then SJA1110 is an external module, it is the driver outof DTS tree for SJA1110?         2、where is the source code of DSA driver?  Is it here: https://github.com/nxp-archive/autoivnsw_sja1110_linux/tree/master , if it is not, what is this code in github for SJA1110?            then in this code, I find that it check if the sja1110's devtype is SJA1110_SWITCH, where to set this devtype, in the DTS file? /** * Write a given value to a given register of the switch * sja1110->devtype needs to be SJA1110_SWITCH */ static u32 sja1110_write_reg(struct sja1110_priv *sja1110, u32 reg_addr, u32 val) {        3、There is only sja1110.ko in Linux bsp as default, I want to visit the interface "sja1110_write_reg" provided by  https://github.com/nxp-archive/autoivnsw_sja1110_linux/tree/master/sja1110_init.c  to config sja1110 ,   what should I do? GoldVIP Re: S32G2 LINUX-BSP and SJA1110 Hello,         Thank you for your reply, I don't have question now. Re: S32G2 LINUX-BSP and SJA1110 Hello @yangjinzhuang Perfect, let me know if you have any other question from the S32G side. Best regards, Alejandro Re: S32G2 LINUX-BSP and SJA1110 Hello,        Thank you for your reply, I will go to the  Other-NXP-Products forum, I had the NDA. Re: S32G2 LINUX-BSP and SJA1110 Hello @yangjinzhuang, All your questions are specific to the SJA1110 chip, this is outside of my scope and the S32G forum scope. Please post your questions in the Other-NXP-Products forum. On it, one of my collogues should be able to help you with everything related to the SJA1110. Please be aware that the documentation related to the SJA1110 and its SDK requires signing a NDA, for this you can contact your FAE/NXP representative. Let me know if you have more questions related to the S32G products. Best regards, Alejandro Re: S32G2 LINUX-BSP and SJA1110 Hello,        1、can you give me the command to config SJA1110's port mode after DSA driver is loaded?       2、I see that SJA1110 has SPI_HOST and SPI_AP host access point,  I also see there are SWITCH_CONTROL_INTERNAL and SWITCH_CONTROL_SPI mode in SDK. In my understand that now, the DSA driver has no relationship with SJA1110's SPI mode and access point, is it right?       3、what is the relationship with SPI_HOST/SPI_AP and SWITCH_CONTROL_INTERNAL/SWITCH_CONTROL_SPI? Does it set SPI_HOST with  SWITCH_CONTROL_INTERNAL  at the same time?Does it set SPI_AP with  SWITCH_CONTROL_SPI at the same time?       4、If I set SPI_AP, the external host controller must be other SJA1110? Can the external controller be S32G274A? The design is S32G274A----SPI----SJA1110 in GLDBOX hardware. I am not sure if S32G274A can access SJA1110 through SPI on SPI_AP interface as an external host controller. Re: S32G2 LINUX-BSP and SJA1110 Hello,         Thanks for your reply, I still want to know how to config SJA1110 and SPI commands here: https://community.nxp.com/t5/Other-NXP-Products/bd-p/other  Re: S32G2 LINUX-BSP and SJA1110 Hello @yangjinzhuang, Here are my answers to your questions: 1 - Yes, that is the aim of the DSA driver. 2 - Yes, you can check the compatibility in https://docs.kernel.org/networking/dsa/sja1105.html  3 - Sorry, I made a mistake. The .c, .o and .ko you mention, refer the out of tree driver mentioned before, this is loaded at boot time. This is the driver that handles the configuration loading while the DSA driver handles the switch functionality. The information for BSP35 is the following [page 60, Linux BSP 35.0 User Manual for S32G2 platforms, 19-Jan-2023]: Please also check section 7.7 Setting up SJA1110 switch. If you have specific questions about the SJA1110 configuration and SPI commands, please post it here: https://community.nxp.com/t5/Other-NXP-Products/bd-p/other  Let me know if this information answers your questions. Re: S32G2 LINUX-BSP and SJA1110 Hello,         The sja1110_init.c and build result in Linux-BSP project path is as follows: AUTO_YOCTO_BSP/build_s32g274ardb2/tmp/work/s32g274ardb2-linux/sha1110/1.0-r0/git/sja1110_init.c  AUTO_YOCTO_BSP/build_s32g274ardb2/tmp/work/s32g274ardb2-linux/sha1110/1.0-r0/git/sja1110.o AUTO_YOCTO_BSP/build_s32g274ardb2/tmp/work/s32g274ardb2-linux/sha1110/1.0-r0/git/sja1110.ko   Re: S32G2 LINUX-BSP and SJA1110 Hello,          Thanks for your reply, my Linux-bsp version is 35.0 and switch chip is SJA1110.          1、Does DSA driver support config switch's port mode(ingress/egress)?          2、Does SJA1110's DSA driver provide same functions with SJA1105 in Linux-bsp UM?          3、I build Linux-bsp 35.0 on Ubuntu，I can find the source code as follows in the 35.0 project https://github.com/nxp-archive/autoivnsw_sja1110_linux/tree/master/sja1110_init.c, then I can also see the build result of sja1110.o and sj1110.ko in the same path, they are built from sja1110_init.c, which is as same as  https://github.com/nxp-archive/autoivnsw_sja1110_linux/tree/master/sja1110_init.c, I can't understand this with your answer before. Re: S32G2 LINUX-BSP and SJA1110 Hello @yangjinzhuang  here are my answers to your questions: 1 - There might be a small confusion on the term "out-of-tree Linux kernel module", it does not refer to the device tree, instead it means the following [article]: the behavior is the following  [page 62, Linux BSP 41.0 User Manual for S32G2 platforms]: the description above is related to a simple configuration loader, not the DSA driver. The DSA (Distributed Switch Architecture) driver behaves as described below [page 62]: 2 - You can find the code in: https://github.com/nxp-auto-linux/linux/tree/release/bsp41.0-5.15.153-rt/drivers/net/dsa/sja1105 3 - the code you shared, as you can see in the name of the repo, is archived, it is no longer supported as you can see in the compatible linux versions: Furthermore I was not able to find any reference to S32G chip family in the repo. I used the BSP41 as an example, if you need details about another version let me know and also let me know if you have more questions about this topic. Re: S32G2 LINUX-BSP and SJA1110 Hello @yangjinzhuang, I will start to analyze your questions and come back to you when I have a relevant update. I appreciate your patience.  Best regards, Alejandro