Linux IMXRT595コマンドラインを介したEVKのデバッグの問題 コマンドラインユーティリティを使用してLinuxでIMXRT595 EVKをデバッグすることはできません。 JP1 を開いたままにしてデバッグ プローブを USB に接続すると、dmesg に次のようなメッセージが表示されます。 [175902.334295] usb 3-4: new high-speed USB device number 127 using xhci_hcd [175902.487414] usb 3-4: New USB device found, idVendor=1fc9, idProduct=0090, bcdDevice= 1.00 [175902.487422] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [175902.487425] usb 3-4: Product: LPC-Link-II CMSIS-DAP [175902.487427] usb 3-4: Manufacturer: NXP [175902.487429] usb 3-4: SerialNumber: A000000001 [175902.491334] hid-generic 0003:1FC9:0090.0025: hiddev1,hidraw8: USB HID v1.00 Device [NXP LPC-Link-II CMSIS-DAP] on usb-0000:00:14.0-4/input0 [175902.491984] cdc_acm 3-4:1.1: ttyACM0: USB ACM device [175902.492975] hid-generic 0003:1FC9:0090.0026: hiddev3,hidraw9: USB HID v1.11 Device [NXP LPC-Link-II CMSIS-DAP] on usb-0000:00:14.0-4/input3 JLinkExe V7.96hを起動したところ、USBデバッグプローブが見つかりませんでした。 それから私は「MIMXRT595-EVK入門」の「LPCScrypt」セクションに従っていました。 JP1をショートし、J40を接続してから、dmesgが表示します。 [176483.914804] usb 3-4: new high-speed USB device number 2 using xhci_hcd [176484.063377] usb 3-4: New USB device found, idVendor=1fc9, idProduct=000c, bcdDevice= 1.00 [176484.063384] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [176484.063386] usb 3-4: Product: LPC [176484.063388] usb 3-4: Manufacturer: NXP [176484.063390] usb 3-4: SerialNumber: ABCD その後、program_JLink実行しますが、失敗しました。 LPCScrypt - J-Link firmware programming script v2.1.2 Nov 2020. Connect an LPC-Link2 or LPCXpresso V2/V3 Board via USB then press Space. Booting LPCScrypt No bootable LPCScrypt target found dfu-util 0.11 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Found DFU: [1fc9:000c] ver=0100, devnum=2, cfg=1, intf=0, path="3-4", alt=0, name="DFU", serial="ABCD" (Grepping for 0x1fc9:0x000c) Boot Failed! Ensure One Debug Probe is configured to DFU-Boot and connected via USB. - For LPC-Link2: remove link JP1 (nearest USB) and power cycle - For LPCXpresso V2/V3: make DFU link and power cycle ここで何が問題なのかわかりません。 回复: LinuxでのコマンドラインによるEVK IMXRT595デバッグの問題 感謝！LinkServerをインストールした後、使用できます west debug -r linkserver をクリックして、今すぐデバッグを開始します。

About S32K312 MPU Background Region Hi all, I have a question about S32K312 MPU Background Region: For example, setting permissions for a certain address: region1：permissions are readable and executable in privileged mode and readable and executable in user mode; So the permissions within the address area of region 1 are readable and executable in privileged mode and readable and executable in user mode; The access permissions for address segments other than region 1 are: 1.If the Background Region is enabled, the permissions for other address segments are: readable , writable, and executable under privileged mode, and not readable , writable, and executable under user mode? 2. If the Background Region is not enabled, what are the permissions for other address segments: not readable, not writable, and not executable under privileged mode and user mode? Best regards. S32 SDK for S32K1 Re: About S32K312 MPU Background Region Hi @sunyy, As per the description, default memory map has read/write in both privileged and not-privileged modes. The background region has read/write in privileged mode only. Please contact ARM support if you need more datails. Regrads, Daniel Re: About S32K312 MPU Background Region Thank you for your answer. But I couldn't find a specific description of read and write permissions, so I would like to ask if the permissions for the background region are read and write in privileged mode and not read and write in user mode, right? Re: About S32K312 MPU Background Region Hello @sunyy, This is specified in the documentation I linked here. The background region has the same memory access attributes as the default memory map, but is accessible from privileged software only. Please contact ARM support if you need more details. Regards, Daniel Re: About S32K312 MPU Background Region Hello，What are the read and write access permissions for the background region? Re: About S32K312 MPU Background Region Hi @sunyy, https://developer.arm.com/documentation/dui0646/c/Cortex-M7-Peripherals/Optional-Memory-Protection-Unit/MPU-Control-Register?lang=en https://developer.arm.com/documentation/dui0646/c/Cortex-M7-Peripherals/Optional-Memory-Protection-Unit Regards, Daniel

fatal error: status.h Hi NXP team, We are using S32K144 EVK board and S32 design studio v3.5. We created a simple application project and configured the LPSPI peripheral and generated the code. However, when I build the project I am getting the following error: fatal error: status.h: No such file or directory Please assist me to resolve this issue. Best regards, Hareesh Re: fatal error: status.h Can we ever expect an actual solution to this??  At my company it takes an act of God to get IT to approve and install a software package.  Now I have to get them to downgrade me... Re: fatal error: status.h Hi @Hareesh  I am afraid other customers have reported some irregularities about the support of S32K1 SDK with S32DS v3.5. We recommend using S32DS3.4 for these devices if you are using SDK.  B.R. VaneB

Storing linker file within project directory rather than S32DS S32k144 shared directory I am developing a project for a S32K144-based system using S32DS 3.4 on Windows. When creating a new project, the linker file used for the project is stored within the following directory: "C:\NXP\S32DS.3.4\S32DS\software\S32SDK_S32K1XX_RTM_4.0.3\platform\devices\S32K144\linker\gcc"  I will refer to this directory as the "Shared Linker Directory" going forward.  I can see the linker file within the " /Project_Settings/Linker_Files/" directory in the IDE, however it is just a shortcut to the file in the "Shared Linker Directory" and it does not actually exist in the project. Here is an example using the flexcan_encrypted_s32k144 demo. I would like to store the linker file within the project itself so that changes may be reflected on GitHub, and I have a few questions related to this: 1. I have found that the path in Properties → C/C++Build → Settings → Standard S32DS C Linker → General -> "Script file (-T)" to be: "${workspace_loc:/${ProjName}/Project_Settings/Linker_Files/S32K144_64_flash.ld}"  It seems to me that this should refer to the internal project directory and not the "Shared Linker Directory". Why is that not the case?  2. I manually changed the directory in question 1  to "../Project_Settings/Linker_Files/S32K144_64_flash.ld", and put a modified linker file in the " /Project_Settings/Linker_Files/" directory. This allows the project to use the modified linker file rather than the default one, and for the file to be pushed to GitHub, as desired. However, the files listed under " /Project_Settings/Linker_Files/" when viewed using the IDE are still the linker files located at the "Shared Linker Directory" directory rather than the linker files located within the project. (I.e., if I open one of the files listed here, it opens the file that is stored at "Shared Linker Directory".) How can I update the project so that the files listed under the " /Project_Settings/Linker_Files/" directory within the IDE are actually the files that are located within my project? 3. Is there a way when creating a new project or loading in an example project to have all of its project settings files (linker, startup, etc.) be independent immediately and not from the shared s32ds directory? In other words, not have to manually change the directories each time? Let me know. Thanks in advance! Compiler | Assembler | Linker General New Project Wizard - Project Management and Settings Re: Storing linker file within project directory rather than S32DS S32k144 shared directory Hi @aipers, I'm not sure how to modify the direct script when importing an example, since (again) this goes out of scope of support modifying the .xml or script files for eclipse functionality. My recommendation is to either create new projects and copy over the configuration or simply creating a new linker file inside the project settings. I apologize for the inconveniences. Best regards, Julián Re: Storing linker file within project directory rather than S32DS S32k144 shared directory Hi @Julián_AragónM, Yes this works. When I look for the linker file for the new application project it is properly in the project's directory. Thanks for your help! However, I am hoping to make changes to the linker file of an example projects, but I don't want it to carry across to other example projects, as they will get it from the shared linker directory at the moment. Any solution to that?  I noticed that the linker path in the project settings is different for the new application project: "${ProjDirPath}/Project_Settings/Linker_Files/S32K144_64_flash.ld" This clearly represents the project's internal directory, but it is still odd to me that the example project settings do not point to the internal project directory as you mentioned they should with their path in you previous reply. Putting it again here for reference: "${workspace_loc:/${ProjName}/Project_Settings/Linker_Files/S32K144_64_flash.ld}" Any ideas? Thanks, again. Re: Storing linker file within project directory rather than S32DS S32k144 shared directory Hi @aipers, I see, I think the issue may lie in importing a project, rather than creating a new one to configure. Could you try creating one and copying over the configuration? "File -> New -> S32DS Application Project" Best regards, Julián Re: Storing linker file within project directory rather than S32DS S32k144 shared directory Hi @Julián_AragónM , thank you for the fast response! 1. I am unfortunately unable to emulate the behavior you are showing with your linker file. When I click "Show In -> System Explorer", I am taken to the shared linker filer directory and not the workspace directory, as shown below. I have not changed anything in the settings and the script files -T is still set to  " "${workspace_loc:/${ProjName}/Project_Settings/Linker_Files/S32K144_64_flash.ld}". 2. When I open the project in VSCode, the linker file does not appear/exist because it is a shortcut and not actually saved in the workspace as mentioned above. Please let me know if there was anything you did on your side or if you changed any settings to have the linker file saved in the workspace.  3. That makes sense, I won't touch project setup config for now.  Thanks again! Re: Storing linker file within project directory rather than S32DS S32k144 shared directory Hi @aipers, 1. I am not sure how you have concluded that the linker file shown in the workspace is actually a shortcut. You can actually look for the file by using the "Show in file explorer" option: This shows the files under the workspace directory. The shared linker directory is used but only as reference for creating the project. Not when editing the file. "${workspace_loc:/${ProjName}/Project_Settings/Linker_Files/S32K144_64_flash.ld}" does refer to the internal project directory, not the shared one. "workspace_loc" simply returns the workspace directory (e.g. C:\Users\user\workspaceS32DS.3.5) and "project_name" returns the name of the current project, giving a full directory to the current project. 2. I have opened this file from VS Code and edited just to see the changes reflected in S32DS.  Are you unable to edit the linker file in your project?  3. Currently it is not supported to change the configurations for project creation, but I suppose you could edit the tpl.sdk.s32k1xx.4_0_3.xml file which is the template file. I would not recommend doing this since S32DS has all the configurations for the S32K families to work correctly. Editing any wrong parameter may lead to undesirable behavior out of our scope of support. Best regards, Julián

Problem debugging IMXRT595 EVK via command line under Linux I cannot debug IMXRT595 EVK under linux with command line utilities: When I left JP1 Open and connect debug probe to USB, dmesg shows following: [175902.334295] usb 3-4: new high-speed USB device number 127 using xhci_hcd [175902.487414] usb 3-4: New USB device found, idVendor=1fc9, idProduct=0090, bcdDevice= 1.00 [175902.487422] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [175902.487425] usb 3-4: Product: LPC-Link-II CMSIS-DAP [175902.487427] usb 3-4: Manufacturer: NXP [175902.487429] usb 3-4: SerialNumber: A000000001 [175902.491334] hid-generic 0003:1FC9:0090.0025: hiddev1,hidraw8: USB HID v1.00 Device [NXP LPC-Link-II CMSIS-DAP] on usb-0000:00:14.0-4/input0 [175902.491984] cdc_acm 3-4:1.1: ttyACM0: USB ACM device [175902.492975] hid-generic 0003:1FC9:0090.0026: hiddev3,hidraw9: USB HID v1.11 Device [NXP LPC-Link-II CMSIS-DAP] on usb-0000:00:14.0-4/input3 When I started JLinkExe V7.96h, it cannot find USB debug probe. Then I was following "Getting Started with the MIMXRT595-EVK",  Section "LPCScrypt" . I shorted JP1, and connected J40, then dmesg shows: [176483.914804] usb 3-4: new high-speed USB device number 2 using xhci_hcd [176484.063377] usb 3-4: New USB device found, idVendor=1fc9, idProduct=000c, bcdDevice= 1.00 [176484.063384] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [176484.063386] usb 3-4: Product: LPC [176484.063388] usb 3-4: Manufacturer: NXP [176484.063390] usb 3-4: SerialNumber: ABCD Then runs program_JLink, it failed: LPCScrypt - J-Link firmware programming script v2.1.2 Nov 2020. Connect an LPC-Link2 or LPCXpresso V2/V3 Board via USB then press Space. Booting LPCScrypt No bootable LPCScrypt target found dfu-util 0.11 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Found DFU: [1fc9:000c] ver=0100, devnum=2, cfg=1, intf=0, path="3-4", alt=0, name="DFU", serial="ABCD" (Grepping for 0x1fc9:0x000c) Boot Failed! Ensure One Debug Probe is configured to DFU-Boot and connected via USB. - For LPC-Link2: remove link JP1 (nearest USB) and power cycle - For LPCXpresso V2/V3: make DFU link and power cycle Not sure what's wrong here. 回复： Problem debugging IMXRT595 EVK via command line under Linux Thanks! I installed LinkServer, then I can use west debug -r linkserver to start debug now. 回复： Problem debugging IMXRT595 EVK via command line under Linux Hi @sprhawk , Thanks for your interest in NXP MIMXRT series! You are doing everything correctly, if you want to use JLink instead of DAPLink, you need to re-flash the firmware. Since I don't have a Linux host on my side, I did the same in Win10PC and was able to successfully burn the JLink firmware. The latest LPCScrypt has been integrated into Linkserver, please try it. If it still doesn't work, we recommend that you try burning the firmware using a Windows host.  https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKERSERVER Best regards, Gavin  

Firmware for SJA1105 Tool on LS1021ATSN-PA platform is missing Hi out there, currently im working on the LS10121ATSN-PA platform - installed with OpenIL. But after first steps with SJA1105 Tool to change switch configuration i get the error "could not open /lib/firmware/sja1105.bin for write". Where can i get the firmware? Greetings Frank Re: Firmware for SJA1105 Tool on LS1021ATSN-PA platform is missing I found a solution by myself. I used the offical Image OpenIL which contains the firmware for the SJA1105.

应用程序引发异常错误：ValueError 您好，我正在尝试使用安全配置工具的 V8 连接到我们的 MIMXRT1160-EVK，当我选择菜单目标/调试探针下的调试探针时，它会立即引发异常而不显示子菜单。 有办法解决这个问题吗？ 此致敬礼 伊恩·诺曼 回复：应用程序引发异常错误：ValueError 感谢您的快速回复。 伊恩

IMX8MP turn off LVDS differentials during standby Hello NXP I am working with "network standby" mode on our new product. I managed to control all our supplies and also GPIOs except then LVDS differential pairs of LVDS0. This result in the fact that they are still supplied with approximately 1.8 Volt and this pulls one of the other supplies up a bit through the LVDS attached display. -------------------- I did a "rmmod panel_lvds". But is there any simple way to turn off differential signals during standby? The signals LVDS pairs are not MUXable and cannot be controlled with IOMUXC like SPI, I2C or similar signals that can be reconfigured to GPIOs. ...maybe making the ldb or phy a loadable module as well? Thanks in advance Flemming Graphics & Display Re: IMX8MP turn off LVDS differentials during standby This seems to be working for me. Thank you:-) Re: IMX8MP turn off LVDS differentials during standby Hi @robot1  You can try to unregister drm master node driver drivers/gpu/drm/imx/imx-drm-core.c which will disable all interface's output. And another way is reloading the ldb driver.

FS65 machine state What the "External RST" mean? Re: FS65 machine state Hi, The RSTB pin acts as as output/input. Its main function is to reset the MCU, but input voltage is monitored in order to detect external reset (external RST) and fault condition. BRs, Tomas

pn5180，AN11802（rev 1.8）respberry pi 5，NfcrdlibEx1_DiscoveryLoop......不起作用 按照AN11802 rev1.8说明，将sw369328.zip应用到raspberry pi 5，但是出现以下错误。 DiscoveryLoop示例： 行：133 错误 - 发生（0xF181）：0xCCEE CC-组件 ID，EE-错误代码。参考-ph_Status.h 行：142 错误 - (0xF181) 发生在 NFCLIB 中 无论如何，这不是 KERNEL SPI CFG DIR 问题吗？还是SPI设置有问题？ 回复：pn5180，AN11802（rev 1.8）respberry pi 5，NfcrdlibEx1_DiscoveryLoop……无法正常工作 谢谢你的分享。 回复：pn5180，AN11802（rev 1.8）respberry pi 5，NfcrdlibEx1_DiscoveryLoop……无法正常工作 我解决了。 主板_PiPn5180.h #定义PHDRIVER_LINUX_USER_SPI /*#定义PHDRIVER_LINUX_KERNEL_SPI*/

Unable to detect IMXRT1160 EVK with provisioning tool Hi, is there a guide for how to connect the IMXRT1160 EVK with the secure provisioning tool (V8) as I'm getting connection failed when trying to use the USB port. I've tried both USB1 & USB2 on the EVK but get the same result. Also does a specific example program need to be run when trying to connect?  Any suggestions greatly appreciated. Kind regards Ian Re: Unable to detect IMXRT1160 EVK with provisioning tool That's great thanks for the help, it was SW1 I needed to change to 0010 Re: Unable to detect IMXRT1160 EVK with provisioning tool Hi Ian, 1. check the power supply,  J38 should be set to 3-4 for power from USB 2. check the switches to set the board to ISP mode: SW1: 0001  (to run the application, change the switch to 0010) Here is the photo of RT1170-EVK, where the jumpers are located and where the cable should be connected. RT1160-EVK should be similar.

NXP level translating and I2C Bus repeater to replace TCA9509(TI) Hi Team, We are currently searching for alternative solution for TI's level translator TCA9509, can you help to advise which NXP chip can be the best option? Thanks. Regards Boler Re: NXP level translating and I2C Bus repeater to replace TCA9509(TI) Hi Guowei, Got it, thank you. Re: NXP level translating and I2C Bus repeater to replace TCA9509(TI) HI Boler Connect the EN pin to VCCA via a 10k resistor should be OK. Thanks! Re: NXP level translating and I2C Bus repeater to replace TCA9509(TI) Hi Guowei, Thanks a lot for your quick update. PCA9509 should be the best option for our application. By the way,  can you help to advise if any design consideration for the EN pin of PCA9509? Can I just connect the EN pin to VCCA via a 10k resistor? Or it also can be connected to VCCB?   Regards Boler Re: NXP level translating and I2C Bus repeater to replace TCA9509(TI) HI Boler Please see below picture circled parts for replace TI part!

LS1021ATSN-PA 平台上的 SJA1105 工具固件缺失 大家好， 目前我正在使用安装了 OpenIL 的 LS10121ATSN-PA 平台。但是在使用 SJA1105 工具更改交换机配置的第一步之后，我收到错误“无法打开 /lib/firmware/sja1105.bin 进行写入”。我可以在哪里获得固件？ 问候弗兰克 回复：LS1021ATSN-PA 平台上的 SJA1105 工具固件缺失 我自己找到了解决办法。我使用了包含 SJA1105 固件的官方 Image OpenIL。

Installing Windows 11 IoT Enterprise on iMX93 Hi, I'm following the IMXWQSG.pdf i.MX Windows IoT Quick Start Guide Rev. 1.5.1 — 24 May 2024 to the letter. Step 5 results in an error: C:\W21H2-1-5-1-imx-windows-bsp-binaries\IoTEntOnNXP>.\make-winpe-enterprise.cmd /disable_updates /test_signing /no_patch Selected: "install.wim" OPTIONS SUMMARY: Source image: install.wim Test signing: yes Windows debug over ethernet: no, IP: Windows PE debug over ethernet: no, IP: KD_NET file (for debug over net): no Windows debug over serial: no Windows PE debug over serial: no Unattended install answer file: no Disable updates: yes Disable transparency: yes Split wim: no Cumulative update: no, path: Skip updates to Windows Enterprise: yes Skip updates to Windows PE: yes ********************************************************************************************************************************************************* +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ *** Step 1 Creating i.MX Windows IoT Enterprise image: out\imx_win_iot_install.wim ********************************************************************************************************************************************************* +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --------------------------------------------------------------------------------------------------------------------------------------------------------- *** Step 1.1 Copying Windows Enterprise image install.wim to out\imx_win_iot_install.wim --------------------------------------------------------------------------------------------------------------------------------------------------------- A subdirectory or file out already exists. copy "install.wim" "out\imx_win_iot_install.wim" 1 file(s) copied. "Cannot identify Windows image version" This comes from the command "dism /Get-WimInfo /WimFile:!IMX_WIN_ENTERPRISE_IMAGE! /index:2" in the make-winpe-enterprise.cmd batch file (which results in the command "dism /Get-WimInfo /WimFile:out\imx_win_iot_install.wim /index:2" being executed). The dism.log file shows: 2024-11-27 15:23:09, Info DISM PID=2060 TID=13108 Scratch directory set to 'C:\Users\vboxuser\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir 2024-11-27 15:23:09, Info DISM PID=2060 TID=13108 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct 2024-11-27 15:23:09, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2024-11-27 15:23:09, Info DISM PID=2060 TID=13108 Successfully loaded the ImageSession at "C:\Windows\system32\Dism" - CDISMManager::LoadLocalImageSession 2024-11-27 15:23:09, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2024-11-27 15:23:09, Info DISM DISM Provider Store: PID=2060 TID=13108 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2024-11-27 15:23:09, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2024-11-27 15:23:09, Info DISM DISM Manager: PID=2060 TID=13108 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2024-11-27 15:23:09, Info DISM DISM.EXE: 2024-11-27 15:23:09, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2024-11-27 15:23:09, Info DISM DISM.EXE: 2024-11-27 15:23:09, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22621, Running architecture=amd64, Number of processors=4 2024-11-27 15:23:09, Info DISM DISM.EXE: Dism.exe version: 10.0.22621.2792 2024-11-27 15:23:09, Info DISM DISM.EXE: Executing command line: dism /Get-WimInfo /WimFile:out\imx_win_iot_install.wim /index:2 2024-11-27 15:23:09, Error DISM DISM WIM Provider: PID=2060 TID=13108 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:3487 - CWimManager::InternalOpGetImages(hr:0x80070057) 2024-11-27 15:23:09, Error DISM DISM WIM Provider: PID=2060 TID=13108 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4274 - CWimManager::InternalCmdGetImages(hr:0x80070057) 2024-11-27 15:23:09, Error DISM DISM WIM Provider: PID=2060 TID=13108 "Error executing command" - CWimManager::InternalExecuteCmd(hr:0x80070057) 2024-11-27 15:23:09, Error DISM DISM WIM Provider: PID=2060 TID=13108 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2128 - CWimManager::ExecuteCmdLine(hr:0x80070057) 2024-11-27 15:23:09, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070057 2024-11-27 15:23:09, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2024-11-27 15:23:09, Info DISM DISM.EXE: 2024-11-27 15:23:09, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2024-11-27 15:23:09, Info DISM DISM.EXE: The install.wim file is copied from the ISO "26100.1.240331-1435.ge_release_CLIENT_IOT_LTSC_EVAL_A64FRE_en-us.iso". I've also tried the /iso option (and copying the iso file in IoTEntOnNXP, and the result is always the same. What could be the problem? Re: Installing Windows 11 IoT Enterprise on iMX93 The previous reply was missing one more required change in the make-winpe-enterprise.cmd file (of release W21H2-1-5-1), so here is the complete solution: The Windows 11 IoT Enterprise evaluation ISO WIM file is using index 1, not 2. So, you need to change the batch commands in make-winpe-enterprise.cmd from line 425 as follows (this will then work for Windows 10 and Windows 11, no matter which ISO you use): @REM Identify Windows version from .wim image set wimindex=2 :TryWimIndexAgain for /f "tokens=1,* delims=: " %%a in ('dism /Get-WimInfo /WimFile:!IMX_WIN_ENTERPRISE_IMAGE! /index:%wimindex% ^| findstr /i "name"') do ( set WINNAME=%%b for /f "tokens=1,2 delims= " %%c in ("!WINNAME!") do ( set WINVER=%%d ) ) if not "!WINVER!" == "10" ( if not "!WINVER!" == "11" ( if "%wimindex%" == "2" ( echo "Cannot identify Windows image version using index 2, trying index 1" set wimindex=1 goto TryWimIndexAgain ) else ( echo "Cannot identify Windows image version!" goto ErrExit ) ) ) echo "Identified Windows !WINVER! from .wim file" echo: echo --------------------------------------------------------------------------------------------------------------------------------------------------------- echo *** Step 1.2 Mounting i.MX Windows IoT Enterprise image at %IMX_WIN_ENTRPRISE_MOUNT_DIR% echo --------------------------------------------------------------------------------------------------------------------------------------------------------- mkdir "%IMX_WIN_ENTRPRISE_MOUNT_DIR%" echo dism /mount-wim /wimfile:"%IMX_WIN_ENTERPRISE_IMAGE%" /mountdir:"%IMX_WIN_ENTRPRISE_MOUNT_DIR%" /index:%wimindex% dism /mount-wim /wimfile:"%IMX_WIN_ENTERPRISE_IMAGE%" /mountdir:"%IMX_WIN_ENTRPRISE_MOUNT_DIR%" /index:%wimindex% || goto ErrExit And from line 713 (after changing the batch file at line 425 as per above): if "!SPLIT_WIM!" == "yes" ( echo dism /Apply-Image /ImageFile:"%WINPE_DRIVE_LETTER%:\install.swm" /SWMFile:"%WINPE_DRIVE_LETTER%:\install*.swm" /index:%wimindex% /ApplyDir:W:\ /Compact >> "%WIN_ENTERPRISE_INSTALL_CMD%" ) else ( echo dism /Apply-Image /ImageFile:"%WINPE_DRIVE_LETTER%:\%IMX_WIN_ENTERPRISE_IMAGE_FILE_NAME%" /index:%wimindex% /ApplyDir:W:\ /Compact >> "%WIN_ENTERPRISE_INSTALL_CMD%" ) Now Windows 11 will install successfully on the iMX93 EVK. Hopefully these fixes make it into the next release so others don't have to waste time trying to find out why it all doesn't work... Re: Installing Windows 11 IoT Enterprise on iMX93 Glad you were able to figure this out yourself. Additional tip: The Windows 11 IoT Enterprise LTSC Evaluation .ISO only has a single index... which contains Windows 11 IoT Enterprise LTSC The OEM .ISO files have two indices. Index 1 contains Windows Enterprise LTSC and Index 2 contains Windows IoT Enterprise LTSC. Re: Installing Windows 11 IoT Enterprise on iMX93 Ok, so the problem is with the batch file itself. The Windows 11 WIM file is using index 1, not 2. So, for anybody running into this same issue, change the batch commands from line 425 as follows (this will then work for Windows 10 and Windows 11): @REM Identify Windows version from .wim image set wimindex=2 :TryWimIndexAgain for /f "tokens=1,* delims=: " %%a in ('dism /Get-WimInfo /WimFile:!IMX_WIN_ENTERPRISE_IMAGE! /index:%wimindex% ^| findstr /i "name"') do ( set WINNAME=%%b for /f "tokens=1,2 delims= " %%c in ("!WINNAME!") do ( set WINVER=%%d ) ) if not "!WINVER!" == "10" ( if not "!WINVER!" == "11" ( if "%wimindex%" == "2" ( echo "Cannot identify Windows image version using index 2, trying index 1" set wimindex=1 goto TryWimIndexAgain ) else ( echo "Cannot identify Windows image version!" goto ErrExit ) ) ) echo "Identified Windows !WINVER! from .wim file" echo: echo --------------------------------------------------------------------------------------------------------------------------------------------------------- echo *** Step 1.2 Mounting i.MX Windows IoT Enterprise image at %IMX_WIN_ENTRPRISE_MOUNT_DIR% echo --------------------------------------------------------------------------------------------------------------------------------------------------------- mkdir "%IMX_WIN_ENTRPRISE_MOUNT_DIR%" echo dism /mount-wim /wimfile:"%IMX_WIN_ENTERPRISE_IMAGE%" /mountdir:"%IMX_WIN_ENTRPRISE_MOUNT_DIR%" /index:%wimindex% dism /mount-wim /wimfile:"%IMX_WIN_ENTERPRISE_IMAGE%" /mountdir:"%IMX_WIN_ENTRPRISE_MOUNT_DIR%" /index:%wimindex% || goto ErrExit

Firmware/Software inside MPC8533? I have read the documentations of MPC8533. But I am still not sure that MPC8533 can store firmware/software inside it? (for example: boot software). It is an integrated processor, not a traditional processor. Can you help to confirm that it can store firmware/software inside it or not? Re: Firmware/Software inside MPC8533? Thank you very much for your help. Re: Firmware/Software inside MPC8533? firmware/software cannot be stored in MPC8533 processor, it should be deployed on the boot media device integrated on the target board, for example eLBC NOR flash or SD card.

MPC8533 内部的固件/软件？ 我已经阅读了MPC8533的文档。但我仍然不确定 MPC8533 是否可以在其中存储固件/软件？（例如：启动软件）。它是一个集成处理器，而不是传统的处理器。 您能否帮助确认它是否可以存储固件/软件？ 回复：MPC8533 内部的固件/软件？ 非常感谢您的帮助。 回复：MPC8533 内部的固件/软件？ 固件/软件不能存储在MPC8533处理器中，而应该部署在目标板上集成的启动媒体设备上，例如eLBC NOR闪存或SD卡。

MCUXPRESSO IDE draw data series In the MCUXpresso IDE, is there a way to draw in a window a data series ? For example draw the content of an array graphically. Luigi Re: MCUXPRESSO IDE draw data series You can also use FreeMASTER to plot data very easily. It has built in data plotting. Re: MCUXPRESSO IDE draw data series Yes, in MCUXpresso IDE, you can visualize a data series using the Peripherals+ view, Data Watchpoints and Tracing (DWT), or the FreeRTOS plugin for monitoring runtime data. For plotting, you can export Official Site data to a CSV file and use external tools like Excel or Python (with Matplotlib) to create the plot. This allows for flexible visualization of your data.

ファームウェア/ソフトウェアがMPC8533内部にありますか? 私はMPC8533のドキュメントを読みました。しかし、私はまだMPC8533ファームウェア/ソフトウェアをその中に保存できるかどうか確信が持てませんか?(例: ブートソフトウェア)。これは統合プロセッサであり、従来のプロセッサではありません。 ファームウェア/ソフトウェアを内部に保存できるかどうかを確認できますか? Re:ファームウェア/ソフトウェア内部MPC8533? ご協力いただき、誠にありがとうございました。 Re:ファームウェア/ソフトウェア内部MPC8533? ファームウェア/ソフトウェアはMPC8533プロセッサに保存できないため、eLBC NORフラッシュやSDカードなど、ターゲットボードに統合されたブートメディアデバイスに展開する必要があります。

pn5180, AN11802(rev 1.8) respberry pi 5, NfcrdlibEx1_DiscoveryLoop ... doesn's work As per AN11802 rev1.8 instructions, sw369328.zip was applied to raspberry pi 5, but the following error occurs.  DiscoveryLoop Example: Line: 133    Error - (0xF181) has occurred : 0xCCEE CC-Component ID, EE-Error code. Refer-ph_Status.h Line: 142   Error - (0xF181) has occurred in NFCLIB By any chance, isn't it a KERNEL SPI CFG DIR problem? Or is there a problem with SPI setting? Re: pn5180, AN11802(rev 1.8) respberry pi 5, NfcrdlibEx1_DiscoveryLoop ... doesn's work Thanks for your sharing. Re: pn5180, AN11802(rev 1.8) respberry pi 5, NfcrdlibEx1_DiscoveryLoop ... doesn's work I solved it. Board_PiPn5180.h  #define PHDRIVER_LINUX_USER_SPI /*#define PHDRIVER_LINUX_KERNEL_SPI*/

S32K344 での HSE - 対称暗号化は不可 こんにちは皆さん 現在、私はHSE-BとS32K344に取り組んでいます。フラッシュメモリ内のデータのAES-CTR暗号化/復号化を行うために、「HSE_SRV_ID_SYM_CIPHER」 サービスを利用したいです。対応するHSEサービスに電話をかけると、いつも エラーコード「HSE_SRV_RSP_NOT_ALLOWED」が表示されます。問題を特定するためにHSEファームウェアリファレンスマニュアルをすでに読んでいますが、理解できません。 次のものを添付しました。 NVM キー属性 (対称キーを含む) の定義 対応するHSEサービスの定義 対応するHSEサービスの関数呼び出し あなたがこの問題を解決するのを手伝ってくれることを願っています。 ありがとうございます！