IMX8DXL PCIe Endpoint enumeration Hello Everyone, It is related to PCIe link training + Enumeration. Our setup: Host: Intel with BIOS + Windows 10/Linux (debian) OS + PCIe Host Device: imx8dxl PCIe Endpoint I have imx8dxl configured as PCIe Endpoint. The link is up. [ 10.037555] pci_epf_test pci_epf_test.0: Failed to get private DMA rx channel. Falling back to generic one [ 10.037569] pci_epf_test pci_epf_test.0: Failed to get DMA channel [ 10.069805] imx6q-pcie 5f010000.pcie_ep: PCIe Gen.1 x1 link up [ 10.069841] imx6q-pcie 5f010000.pcie_ep: PCIe Gen.1 x1 link up [ 10.069855] imx6q-pcie 5f010000.pcie_ep: Link up, Gen1 Problem: imx8dxl PCIe endpoint device is not detected by Windows OS or Linux. Questions: 1. What could be possible cause for not getting detected, inspite Link is Up? 2. As per PCIe Spec, after device power on + stable clock + PERST, we have 20 ms for Link training and 100ms for enumeration, is this correct? if so, how to achieve this with imx8dxl with uboot + Kernel which takes around 5 seconds for complete boot? Re: IMX8DXL PCIe Endpoint enumeration attached the document from the link Re: IMX8DXL PCIe Endpoint enumeration I got the document at the link: https://community.nxp.com/t5/P-Series/Configuring-PCIe-ports-in-endpoint-mode-in-uboot-and-Linux/m-p/223974 Answer: We need to do it in Uboot. Recommended to repartition the PCI Express initialization code and move it ahead of other code blocks irrelevant to PCI Express. Snip: Because a PCI Express endpoint card seated in each PCI Express slot of a x86 PC motherboard is only one of the many components that the entire PC system interoperates with, the system BIOS can not wait forever to discover the PCI Express endpoint card. To synchronize the PCI Express endpoint discovery process between the x86 PC host and the PCI Express endpoint card, the PCI Express CEM Specification defines a 100-msec rule from the de-assertion time of the PERST# (slot reset) to the time that a PCI Express root complex (host) is allowed to probe the connected downstream endpoint. If a PCI Express endpoint card fails to respond the x86 PC host’s configuration cycle correctly at the time when the 100 msec expires, the host assumes it is malfunctioning. The x86 PC host BIOS might not wait for such PCI Express endpoint card to become available even the endpoint card might just need some more time to initialize itself. Such a PCI Express endpoint card would be disabled by the BIOS and become an undiscoverable PCI Express endpoint in the system. .... In general, introducing less than a 10msec delay is fine. However, any delay beyond 10msec reduces the 100msec budget allocated from the slot reset’s deassertion to the configure cycle being responded by PCI Express end point. Therefore, it is recommended to repartition the PCI Express initialization code and move it ahead of other code blocks irrelevant to PCI Express. Re: IMX8DXL PCIe Endpoint enumeration Dear NXP Support team, You expertise in this domain will be valuable direction to the project. Kindly share you solutions. We look forward to your response. Best regards, KK

LPC55s28 DMA通过ADAU1761传输USB数据波形异常 各位前辈好，我正在使用PC音频软件通过USB将音频数据发送到MCU，MCU自动通过DMA将音频数据搭载到I2S，数据通过I2S进入ADAU1761，再通过DAC输出，但是现在的问题是音频数据通过USB传输到ADAU1761后，数据波形不对。前几天一直在测试DMA传输I2S数据，确认DMA传输I2S数据是没有问题的，但是现在可能的问题是USB传输数据的格式与DMA传输的格式不匹配。 我的I2S配置为MCLK为12.288mhz，LRCK为48khz，BCLK为3.072mhz，左对齐，帧长64位，24位有效数据，剩余8位0填充，DMA传输为32位传输，USB部分配置为24位深度，48khz采样率。 请给我你的建议。 谢谢。 最后附上我的代码 回复：LPC55s28 DMA通过ADAU1761传输USB数据波形异常 谢谢您的回复，问题已经解决。 MHY

What's the difference between SpiDataWidth and SpiEEMaxLenght Hi NXP Team, i'm developing a project using MBDT on S32K358 board. I was wondering waht's the difference between SpiDataWidth and SpiEbMaxLenght when configuring the Spi peripheral. Thanks, Simon Re: What's the difference between SpiDataWidth and SpiEEMaxLenght Hi @simon98  In the transmission I made, I set SpiDataWidth to 8 bits, which matches the size of each data element I am transmitting. I also defined SpiEbMaxLength as 100, which represents the maximum number of data elements that can be transmitted in a single operation. Although I transmitted an array of 10 data elements, each 8 bits wide, since SpiEbMaxLength was set to 100, I have the capacity to transmit up to that limit. In this case, since I only sent 10 data elements, we did not reach the maximum allowed, but if necessary, I could transmit up to 100 data elements in a single operation without any issues. Re: What's the difference between SpiDataWidth and SpiEEMaxLenght Hi VaneB, I've tried to send a 3 byte data buffer setting up a data store memory of 3 elements uint8 on MBDT. I've configured the SpiDataWidth = 8 and SpiEbMaxLength = 1000 (as the MBDT spi example): I've found out that it transmit corrrectly a frame with 3 bytes... So i'm a bit confused over the real purpose of these two configuration parameters... For example if i need to send a frame with 3 byte of data, a possible configurations that would come to mind could be SpiDataWidth = 24 SpiEbMaxLength = 3 but i don't understand why it works even with the example configuration. Could you explane me with a practical example how these works? Thanks, Simon Re: What's the difference between SpiDataWidth and SpiEEMaxLenght Hi @simon98  The SpiDataWidth parameter represents the frame size in terms of the number of bits. For MCAL, the maximum frame size is 64 bits, as it is designed to be compliant with AUTOSAR 4.7, according to the "Specification of SPI Handler/Driver" documentation provided by AUTOSAR. The SpiEbMaxLength refers to the maximum number of data elements that can be stored in the external buffer. BR, VaneB

More MC9S12C64 flash burner questions I thought I had the flash burner routine solved but when I inserted my working test code into my main program it wouldn't work. So, I went back to my test program and found that it was limited in what I could burn back. I wrote another test program that uses the same number of configurable constants as my main program. I found that it would erase the sector just fine, but I couldn't get it to burn any more than 256 bytes. I'm kind of at a loss to explain why. Any suggestions would be greatly appreciated. Regards, Robert Re: More MC9S12C64 flash burner questions Follow up: Thanks to Ladislav's suggestions and code examples I was finally able to solve this coding problem I've been working with on several projects for well over a year now. I was able to get, out of his latest example, the portions I needed and convert them to absolute assembler. Then I was able to integrate them into my main program. The erase and burn routines work perfectly. No matter how much I studied the reference manual and code examples from a couple of books,  I just could not get it right. Now I have it and owe Ladislav a great debt of thanks. I couldn't have done it without him. Regards, Robert Re: More MC9S12C64 flash burner questions Hi Ladislav, Thanks very much for the attachment. I was able to load it into my controller and run it. I believe I understand what it does. Excellent work! I notice that the program was written in relocatable assembler. I'm not familiar with that and my programs are written in absolute assembler. I'll have to see how I can integrate the parts of your program that I need into my absolute assembler program. Regards, Robert Re: More MC9S12C64 flash burner questions Hi, look into attached code. 1) label "<<<<<<<<<<<<<<<<<" is asking you for your code regarding error processing. 2) read the code carefully to understand also notes. The flash is written once and then in loop...just as an example. You can add more command for processing if you want. 3) When debugging you should set:   4) Do not visualize written part of memory in memory window while E/W because debugger is reading the memory and reading while writing is not allowed. 5) Tested, working.....Now, you must be able to do it!!! Best regrads Ladislav Re: More MC9S12C64 flash burner questions Hi Ladislav, Thanks again for taking the time to answer my question. Yes, I can fit what I need into near Flash. (Unpaged Flash?) My code is from $C000 to $D8F2, 6,226 bytes by my reckoning. It may expand in future but not much. The only time this code is changed is when I do a code revision, it never gets changed on the fly. My configurable constants are from $4000 to $424C (588 bytes) They may expand in future but certainly never anywhere near $4FFF. (4,095 bytes maximum available, I think.) In my program the configurable constants from $4000 to $424 C are copied to RAM at start up where the program accesses them. They can be modified there and burnt back to Flash in the program if necessary. Does that answer your question? Regards, Robert Reqards, Robert Re: More MC9S12C64 flash burner questions Hi, my fault, I mixed answers. I would like to ask which part of the flash you want to E/W. If you need only small part then I suggest to select some part of near flash. (4000-4FFF, C000-FFFF) It will solve issue with paging. Easier for me is to create example than fight with each issue. I will remove incorrect part of our communication from this thread. So, what is exactly your task. Best regards, Ladislav Re: More MC9S12C64 flash burner questions Hi Ladislav, Now I am really confused. I am using the free version of Code Warrior. CW 5.9.0 build 5294. From the link you sent it says it will accept unrestricted assembler. I see no restrictions on flash burning. When I created the project that I attached last time I went to: New project -> Select derivative (MC9S12C64) -> connection (USBDM) -> Language (absolute assembly) -> Add existing files (BurnerTestv4.asm) ->Rapid Application (none). In the Select derivative I see no mention of S12ZVMC. Just in case, I followed the same path to created a new project which I am attaching the zip file for. I couldn't open your attachment because I couldn't find an MCP file for it. Also, as I mentioned, I am not fluent in C so if you can help me with this it pretty well has to be in assembler only. Thanks  Robert  Re: More MC9S12C64 flash burner questions Hi, the Sw you attached is S12ZVMC. The device you mention is S12C .... absolutely different families. BTW, I created a simple project (attached) and it works without any issues. I am not able to make your project alive. Please check also your license and limitations here.... https://www.nxp.com/design/design-center/software/development-software/codewarrior-development-tools/codewarrior-legacy/codewarrior-for-mcus-eclipse-ide-coldfire-56800-e-dsc-qorivva-56xx-rs08-s08-s12z-11-1:CW-MCU10?tab=Buy_Parametric_Tab     Best regards, Ladislav    

Build Error for Sai_47478A_440_100 Example in S32DS 3.4 (S32K344) Hello, all I'm trying to build the Sai_47478A_440_100 example in S32DS 3.4 for S32K344, but I am encountering the following issues. 1. .mex File Load Error in Peripheral Mode When I select the project from the Peripheral tab, I get the following error: "error during opening configuration sai_~.mex processor s32k344, platformsdk_s32k3 version is not supported by current version of the tool" I'm using S32DS 3.4 and have installed SW32K3_RTD_4.4_1.0.0. How can I properly load the .mex file in Peripheral Mode? The goal is to integrate this code into RTD 5.0.0 in S32DS 3.5 If anyone has faced a similar issue, I would appreciate any guidance on resolving this. Thank you! Re: Build Error for Sai_47478A_440_100 Example in S32DS 3.4 (S32K344) The Sai_47478A_440_100 project is configured by EBTresos instead of S32 Configuration Tool(S32DS). You need to import the C:\NXP\S32K344_Whiteboard_Example_RTM_1.0.0\S32K344_Whiteboard_Example_RTM_1.0.0\SAI\Sai_47478A_440_100\Tresos_Project\Sai_47478A_440_100 by using EBTresos. Here is the configuration of LPI2C0: Sorry, I'm afraid you need to refer to EBTresos Project to migrate the project to RTD 5.0.0 in S32DS. Best Regards, Robin ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------

IOMUXC_GPR_GPR14 available information discrepancy Hi I have a question about register IOMUXC_GPR_GPR14 on RT1062 MCU In the reference manual (latest, rev.3) this register should be responsible for ACMP configuration. While when i search examples of FlexRAM configuration i find some info and code examples mentioning that register is responsible for some FlexRAM settings. For example this post https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexRAM-configuration-for-OCRAM-0/m-p/1078440 and also AN12077 application note mentions it, and the Teensy 4.1 code do some strange setting on this register right after setting GRP17 and GPR16 so they used it for sure for FlexRAM not the analog comparators. In the SDK however (at least in version 2.16.100) all the code for IOMUXC_GPR_GPR14 is dedicated to ACMP1-4 I'm puzzled. Please bring some light on it Re: IOMUXC_GPR_GPR14 available information discrepancy That makes sense. Thanks, now i understand why the old code is that way but new code just ignores this register and only uses GPR17 and GPR16 for FlexRAM configuration Re: IOMUXC_GPR_GPR14 available information discrepancy Hi @Pencioner , Thanks for your interest in NXP MIMXRT series! This is not a bug, but the two FEATURES use different bit fields. About FlexRAM, in the previous version, IOMUXC_GPR_GPR14 provided 16-20bit for configuring the size of ITCM/DTCM, then it was found out that it works even if you don't configure these two bitfields, so the new version of RM about these two bitfields has been hidden.   And the configuration of ACMP uses the other bitfields of IOMUXC_GPR_GPR14, and the FlexRAM function does not affect each other. Best regards, Gavin

1170EVKBのMCU-Linkファームウェアを更新 1170EVK-BボードでMCUXpressoを使用しています。プロジェクトをデバッグしようとすると、次のようなファームウェア更新の警告が表示されます。 Firmware update requiredファームウェアのアップデートが必要です LinkServerと最新のファームウェアを https://www.nxp.com/design/design-center/software/sensor-toolbox/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#MIMXRT1170-EVK からダウンロードしました LinkServerを使用して自動的に更新しようとしましたが、成功しませんでした。 ./LinkServerプローブ「#1」更新自動情報:MCU-Linkファームウェア更新自動:サポートされていません-ファームウェア(V3.122以降)は、選択したプローブで手動でプログラムする必要があります（[TQYQNHWCAQPZC][MCU-LINKオンボード(r0E2)CMSIS-DAP V2.250])ファームウェア更新自動:サポートされていません。 次に、ボードをブートローダーモードにして、次のようなさまざまな指示に基づいてファームウェアを更新できるようにしようとしました。 ※https://www.nxp.com/design/design-center/software/sensor-toolbox/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#MIMXRT1170-EVK ※ https://community.nxp.com/t5/i-MX-RT/Put-RT1170-EVK-in-quot-ISP-USB-quot-mode-for-MCU-Link-installer/m-p/1426988 ※ https://community.nxp.com/t5/i-MX-RT/Facing-issue-with-LPC-Link-2-with-iMX-RT-1170-Evk/m-p/1407341 ※https://community.nxp.com/t5/i-MX-RT/i-MX-RT1170-with-MCU-Boot-Utility/td-p/1303418 ...しかし、失敗しました。私の問題は1170EVKと1170EVK-Bの違いから生じているのでしょうか、それとも何か明らかなものが欠けているのでしょうか? どうもありがとう Nick Re:1170EVKBのMCU-Linkファームウェアの更新 お知らせいただきありがとうございます! ディエゴ Re:1170EVKBのMCU-Linkファームウェアの更新 おかげで助かりました。 この記事は「JP3にジャンパを取り付けて、MCU-LinkをISPモードに強制する」に役立ちました - https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/Using-J-Link-with-MIMXRT1170-EVKB/ta-p/1715138 そうしたら： $ cd /Applications/LinkServer_1.5.30/MCU-LINK_installer/scripts J-Link firmware for MCU-Link programming script v1.0.8 March 2023. NOTE: J-Link firmware supports MCU-Link Pro and MCU-Link on-board systems that use an LPC55S69 in LQFP100 or BGA98 package. Although the firmware can be programmed in to MCU-Link and MCU-Link on-board systems that use LQFP64 package, the firmware will not run. Place the board in ISP USB mode using the appropriate jumper on your MCU-Link. Refer to the board documentation for more information. Connect board via USB then press Space. Programming Firmware_J-Link-MCU-Link_230502.s19 Programmed successfully. - To use: remove ISP jumper and reboot. 私はまだ問題を抱えていましたが、この投稿は役に立ちました:https://community.nxp.com/t5/i-MX-RT/Failed-to-power-up-DAP-ERROR-Could-not-connect-to-target/m-p/1503062#M20946 そして、ついにオンボードデバッガーが動作するようになりました。 Re:1170EVKBのMCU-Linkファームウェアの更新 こんにちは@nickager  お元気にお会いできることを願っています。 i.MX RT1170-EVKはLPC43xxをオンボードデバッガとして実装し、i.MX RT1170-EVKBはLPC55s69(MCU-Link)を実装しています。もしかしたら、それが問題があった理由かもしれません。 ここからLinkserverをダウンロードしてください Windows用Linkserver 1.5.30インストーラー 。SWをインストールした後、C:\nxp\LinkServer_1.5.30\MCU-LINK_installer\scriptsでアップデートスクリプトを実行します(デフォルトのインストールパスを使用)。 MCU-Link FWは、上記LinkServer for Microcontrollersのページで配布しています。 これがお役に立てれば幸いです。 ディエゴ

MK64 FlexBus FB_RW 我用的是MK64，写操作完成后FB_RW一直为低，读操作完成后FB_RW又恢复为高，好像是6800模式，我需要8080模式

Update MCU-Link firmware on 1170EVKB I am using MCUXpresso with an 1170EVK-B board. When I try to debug the project I receive the firmware update warning below: Firmware update requiredFirmware update required I have downloaded LinkServer and latest firmware from: https://www.nxp.com/design/design-center/software/sensor-toolbox/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#MIMXRT1170-EVK I've tried using LinkServer to automatically update without success: ./LinkServer probe '#1' update auto INFO: MCU-Link firmware update auto: not supported - the firmware (V3.122 or later) should manually programmed on the selected probe ([TQYQNHWCAQPZC] [MCU-LINK on-board (r0E2) CMSIS-DAP V2.250]) Firmware update auto: not supported and then tried to put the board into a boot loader mode where I can update the firmware based on various instructions such as: * https://www.nxp.com/design/design-center/software/sensor-toolbox/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#MIMXRT1170-EVK * https://community.nxp.com/t5/i-MX-RT/Put-RT1170-EVK-in-quot-ISP-USB-quot-mode-for-MCU-Link-installer/m-p/1426988 * https://community.nxp.com/t5/i-MX-RT/Facing-issue-with-LPC-Link-2-with-iMX-RT-1170-Evk/m-p/1407341 * https://community.nxp.com/t5/i-MX-RT/i-MX-RT1170-with-MCU-Boot-Utility/td-p/1303418  ... but have failed. Could my problems stem from the difference between 1170EVK and 1170EVK-B or am I missing something obvious? Many thanks Nick Re: Update MCU-Link firmware on 1170EVKB Thanks for letting us know! Diego Re: Update MCU-Link firmware on 1170EVKB Thanks that helped.  I found this post helpful for "Install a jumper at JP3 to force the MCU-Link in ISP mode" - https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/Using-J-Link-with-MIMXRT1170-EVKB/ta-p/1715138 Then: $ cd /Applications/LinkServer_1.5.30/MCU-LINK_installer/scripts J-Link firmware for MCU-Link programming script v1.0.8 March 2023. NOTE: J-Link firmware supports MCU-Link Pro and MCU-Link on-board systems that use an LPC55S69 in LQFP100 or BGA98 package. Although the firmware can be programmed in to MCU-Link and MCU-Link on-board systems that use LQFP64 package, the firmware will not run. Place the board in ISP USB mode using the appropriate jumper on your MCU-Link. Refer to the board documentation for more information. Connect board via USB then press Space. Programming Firmware_J-Link-MCU-Link_230502.s19 Programmed successfully. - To use: remove ISP jumper and reboot. I still had problems but this post helped: https://community.nxp.com/t5/i-MX-RT/Failed-to-power-up-DAP-ERROR-Could-not-connect-to-target/m-p/1503062#M20946 and I finally have working onboard debugger. Re: Update MCU-Link firmware on 1170EVKB Hi @nickager  I hope to find you well.  The i.MX RT1170-EVK implements LPC43xx as the on-board debugger, and the i.MX RT1170-EVKB the LPC55s69, ( MCU-Link). Maybe that is the reason why you had issues.  Please make sure to download Linkserver from here  Linkserver 1.5.30 installer for Windows  . After installing the SW execute the update script at C:\nxp\LinkServer_1.5.30\MCU-LINK_installer\scripts (using default installation path) The MCU-Link FW is now being distributed at LinkServer for Microcontrollers page referecenced above.  I hope this could help you! Diego

MK64 FlexBus FB_RW I'm using MK64, the FB_RW keeps being low after the write operation is finished, and the FB_RW returns high after the read operation, which seems to be 6800 mode, I need 8080 mode Re: MK64 FlexBus FB_RW Hi, From the attached  FlexBus timing, it is incorrect, at least, the data bus should be valid until the rising edge of /CS signal. Pls try different parameter in the FB_CSCRn register, especially, WRAH and WS bits, do not use burst mode, set AA bit in 1. Pls have  a try. BR XiangJun Rong Re: MK64 FlexBus FB_RW The DM9000 write timing is shown in the figure, how does the MK64 FlexBUS implement it? Re: MK64 FlexBus FB_RW As you can see from the graph, the FB_RW stays low after the data is written Re: MK64 FlexBus FB_RW Hi, The Flex_Bus of K64 is in 8086 mode instead of 68K mode. This is the reading timing: This is writing timing: Compare the two timing, you can see that the /FB_OE  low and the FB_RW high are observed in reading timing, the /FB_OE  high and the FB_RW low are observed in writing timing. If the timing is 68K mode, the /FB_OE is always low no matter whether it is reading or writing. Hope it can help you BR XiangJun Rong

更新 1170EVKB 上的 MCU-Link 固件 我正在使用带有 1170EVK-B 板的 MCUXpresso。当我尝试调试项目时，我收到以下固件更新警告： Firmware update required需要固件更新 我已经从以下网址下载了 LinkServer 和最新固件： https://www.nxp.com/design/design-center/software/sensor-toolbox/opensda-serial-and-debug-adapter :OPENSDA?tid=vanOpenSDA#MIMXRT1170-EVK 我尝试使用 LinkServer 自动更新，但没有成功： ./LinkServer 探针‘#1’自动更新信息：MCU-Link 固件自动更新：不支持 - 固件（V3.122 或更高版本）应在所选探针上手动编程（[TQYQNHWCAQPZC] [MCU-LINK 板载（r0E2）CMSIS-DAP V2.250]）固件自动更新：不支持 然后尝试将主板置于引导加载程序模式，我可以根据各种指令更新固件，例如： * https://www.nxp.com/design/design-center/software/sensor-toolbox/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#MIMXRT1170-EVK * https://community.nxp.com/t5/i-MX-RT/Put-RT1170-EVK-in-quot-ISP-USB-quot-mode-for-MCU-Link-installer/mp/1426988 * https://community.nxp.com/t5/i-MX-RT/Facing-issue-with-LPC-Link-2-with-iMX-RT-1170-Evk/mp/1407341 * https://community.nxp.com/t5/i-MX-RT/i-MX-RT1170-with-MCU-Boot-Utility/td-p/1303418 ...但失败了。我的问题是否源于 1170EVK 和 1170EVK -B之间的差异，或者我是否忽略了一些明显的东西？ 非常感谢 Nick 回复：更新 1170EVKB 上的 MCU-Link 固件 感谢您告知我们！ 迭戈 回复：更新 1170EVKB 上的 MCU-Link 固件 谢谢，有帮助。 我发现这篇文章对“在 JP3 处安装跳线以强制 MCU-Link 处于 ISP 模式”很有帮助 - https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/Using-J-Link-with-MIMXRT1170-EVKB/ta-p/1715138 然后： $ cd /Applications/LinkServer_1.5.30/MCU-LINK_installer/scripts J-Link firmware for MCU-Link programming script v1.0.8 March 2023. NOTE: J-Link firmware supports MCU-Link Pro and MCU-Link on-board systems that use an LPC55S69 in LQFP100 or BGA98 package. Although the firmware can be programmed in to MCU-Link and MCU-Link on-board systems that use LQFP64 package, the firmware will not run. Place the board in ISP USB mode using the appropriate jumper on your MCU-Link. Refer to the board documentation for more information. Connect board via USB then press Space. Programming Firmware_J-Link-MCU-Link_230502.s19 Programmed successfully. - To use: remove ISP jumper and reboot. 我仍然遇到问题，但这篇文章很有帮助： https://community.nxp.com/t5/i-MX-RT/Failed-to-power-up-DAP-ERROR-Could-not-connect-to-target/mp/1503062#M20946 我终于有了可以运行的板载调试器。 回复：更新 1170EVKB 上的 MCU-Link 固件 你好@nickager 我希望你一切都好。 i.MX RT1170-EVK 将 LPC43xx 实现为板载调试器，i.MX RT1170-EVKB 将 LPC55s69（MCU-Link）实现为板载调试器。也许这就是您遇到问题的原因。 请确保从此处下载适用于 Windows 的 Linkserver 1.5.30 安装程序。安装 SW 后，执行位于 C:\nxp\LinkServer_1.5.30\MCU-LINK_installer\scripts 的更新脚本（使用默认安装路径） MCU-Link FW 目前正在上述微控制器 LinkServer 页面上分发。 我希望这能对你有帮助！ 迭戈

MK64 フレックスバスFB_RW MK64を使用していますが、書き込み操作が終了した後もFB_RWが低くなり続け、読み取り操作後にFB_RWがハイに戻り、6800モードのようですが、8080モードが必要です

Should the RT1021 use the FreeRTOS port ARM_CM4F or ARM_CM7? Hi, Which FreeRTOS port should the RT1021 be using? The SDK demo projects use ARM_CM4F, but there are comments in there that say that CM7 r0p1 versions should use the ARM_CM7 port. (Also I think the original SDK demos used the CM7 one a few years ago?) The RT1021 reference manual talks about the ETM Arm CoreSight™ ETM-M7 Revision: r0p1 Technical Reference Manual. Please clarify which port to use. Many thanks and kind regards. Re: Should the RT1021 use the FreeRTOS port ARM_CM4F or ARM_CM7? Thanks @MultipleMonomials @rshipman for providing this method. Yes, it is ARM_CM4F. Re: Should the RT1021 use the FreeRTOS port ARM_CM4F or ARM_CM7? Hmm, in the past I used the debugger to inspect the registers of my MIMXRT1050 and it came back as a Cortex-M7 r1p1, even though the manual for this one also references "Arm CoreSight™ ETM-M7 Revision: r0p1".  So, I think that using the Cortex-M4F port is correct. You can check it yourself by reading the CPUID register in the debugger (J-Link prints its value when connecting to the core, or you could read it manually).  Per here, the rightmost hex digit is the revision, and the sixth-from-the-right hex digit is the variant number.  For example, mine comes back as 0x411FC271, which would mean that it is r1p1.

S32K341EHT0MPAST Pinout I am wanting to use the S32K341EHT0MPAST and can't find a list of the functions associated with the pin to the 100 pins. Do you know where I can find the pinout information? Re: S32K341EHT0MPAST Pinout Hi @Capray986  Attached to the S32K3xx Reference Manual, Rev. 8 you can find the S32K342_S32K341_S32K322_IOMUX file, which contains the pins specifications of this device. B.R. VaneB

S32DS-S32K3xx SMP示例编译错误 我正在尝试编译 FreeRTOS_Toggle_Led_Example_S32K358_SMP 项目，它产生了以下错误： C:/NXP/workspaceS32DS.3.6.0/FreeRTOS_Toggle_Led_Example_S32K358_SMP/generate/include/FreeRTOSConfig.h:64:66:错误：函数“taskDISABLE_INTERRUPTS”的隐式声明[-Werror=implicit-function-declaration] arm-none-eabi-gcc“@RTD/src/Clock_Ip.args”-MMD-MP-MF“RTD/src/Clock_Ip_Monitor.d”-MT“RTD/src/Clock_Ip_Monitor.o”-o“RTD/src/Clock_Ip_Monitor.o”“../RTD/src/Clock_Ip_Monitor.c” 64 | #定义 configASSERT（x）if（（x）==0）{ taskDISABLE_INTERRUPTS（）; 对于（;; ）; } | ^~~~~~~~~~~~~~~~~~~~~~ ../FreeRTOS/Source/portable/GCC/ARM_CM7/r0p1/portmacro.h:184:17: 注意：在宏“configASSERT”的扩展中 184 | configASSERT（Get_64（&ucRecursionCountByLock[ulLockNum]）！= 255u）； | ^~~~~~~~~~~~~~ 缺少#include？ 有没有快速修复此问题的方法？ 我正在使用 DS 3.6.0以及“适用于 S32K3XX 版本 5.0.0 的 FreeRTOS”包裹。示例取自“SW32K3 FreeRTOS 11.1.05.0.0上述包中的 CD1 D2409 示例项目部分。 谢谢 回复：S32DS-S32K3xx SMP示例编译错误 谢谢朱利安。成功了！

S32 Design Studio for ARM expires soon Hello support team, could you please extend my S32 Design Studio for ARM 2.2 license, it will expire in 15 days. My license details as follows: S32 Design Studio for ARM ActivationId: 0E6E-4188-1B59-C966 Evaluation Days: 15 Feature Version: 2.2 Feature Status: Evaluation (15 days) Thanks in advance. Kind regards, Andreas Re: S32 Design Studio for ARM expires soon Thanks for the quick help, I was able to re-register the extended license. Thank you and have a good time. Re: S32 Design Studio for ARM expires soon Hi Andreas,  your S32DS license has been extended. You can left your current license to expire or return it - on main menu bar click on Help -> NXP Licenses -> Open -> Return License and activate S32DS again with your old code. 

S32DS - S32K3xx SMP サンプルのコンパイル エラー プロジェクトをコンパイルしようとするとFreeRTOS_Toggle_Led_Example_S32K358_SMP次のエラーが発生します。 C:/ NXP / workspaceS32DS.3.6.0 / FreeRTOS_Toggle_Led_Example_S32K358_SMP / generate / include / FreeRTOSConfig.h:64:66:エラー:関数 'taskDISABLE_INTERRUPTS'の暗黙宣言[-Werror =暗黙の機能宣言] arm-none-eabi-gcc "@RTD/src/Clock_Ip.args" -MMD -MP -MF "RTD/src/Clock_Ip_Monitor.d"-MT「RTD/src/Clock_Ip_Monitor.o」-o "RTD/src/Clock_Ip_Monitor.o""../RTD/src/Clock_Ip_Monitor.c" 64 |#define configASSERT(x) if((x)==0) { taskDISABLE_INTERRUPTS(); for( ;; ); } |^~~~~~~~~~~~~~~~~~~~~~ ../FreeRTOS/Source/portable/GCC/ARM_CM7/r0p1/portmacro.h:184:17: ノート: マクロ 'configASSERT' の拡張中 184 |configASSERT( Get_64(&ucRecursionCountByLock[ulLockNum]) != 255u); |^~~~~~~~~~~~ #include がありませんか? これを修正する簡単な方法はありますか? DS 3.6.0 を使用していますおよび「FreeRTOS for S32K3XX バージョン 5.0.0」パッケージ。「SW32K3 FreeRTOS 11.1.0」から取得した例5.0.0上記パッケージのCD1 D2409 Example Projects」セクション。 感謝 Re: S32DS - S32K3xx SMP サンプルコンパイルエラー ありがとうジュリアン。うまく行きました！

Error in building imx-boot image for iMX93 11x11 EVK using imx-mkimage Hello everyone, I'm tryng to build the imx-boot image by using imx-mkimage, following the steps I found for i.MX 93 A1 in Linux Users Guide (from 39/166 to 40/166): https://www.nxp.com/doc/IMX_LINUX_USERS_GUIDE I succesfully build u-boot.bin and u-boot-spl.bin (GitHub - nxp-imx/uboot-imx at lf_v2023.04) and I and I copied them in imx-mkimage/iMX93 (source: GitHub - nxp-imx/imx-mkimage: i.MX Mkimage Bootloader Tool 6.6.3_1.0.0). In the same folder I put bl31.bin, generated from  GitHub - nxp-imx/imx-atf: i.MX ARM Trusted firmware together with mx93a1-ahab-container.img (u-boot/doc/board/nxp/imx93_11x11_evk.rst at master · u-boot/u-boot · GitHub) . So the final content of the folder is this: When it comes to run the command: make SOC=iMX93 flash_singleboot The output gives the following error: Can anyone help me with this issue? I can't figure out what is going on. Thanks, in advance, Bob Re: Error in building imx-boot image for iMX93 11x11 EVK using imx-mkimage Thank you, now it works! Regards, Bob Re: Error in building imx-boot image for iMX93 11x11 EVK using imx-mkimage Hi, This is another issue missing DDR firmware. Follow the steps as below. wget https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-imx-8.23.bin chmod +x firmware-imx-8.23.bin ./firmware-imx-8.23.bin copy missing ddr firmware from -> firmware-imx-8.23/firmware/ddr/synopsys/ Regards Harvey Re: Error in building imx-boot image for iMX93 11x11 EVK using imx-mkimage Hello, I tried to do the gitclone command as you suggested: git clone https://github.com/nxp-imx/imx-mkimage.git The download terminated succesfully, then I moved all the necessary files into iMX93 folder. Then I execute:  make SOC=iMX93 flash_singleboot this command returns: How can i go ahead? Regards, Bob     Re: Error in building imx-boot image for iMX93 11x11 EVK using imx-mkimage This seems to be a problem with your git. or did you download the imx-mkimage in git clone? Regards Harvey Re: Error in building imx-boot image for iMX93 11x11 EVK using imx-mkimage Hello @Harvey021 , Thanks for responding, I tried the command you suggested and this is the output:   Can you tell me what I have to do next? Thanks, Bob Re: Error in building imx-boot image for iMX93 11x11 EVK using imx-mkimage Hi @Bob_NXP_user  It seems that the commit number has not been generated. please make sure your download. Have a run "git rev-parse --short=8 HEAD >> src/build_info.h" to see what it is. Regards Harvey

S32DS - S32K3xx SMP example compilation error I'm trying to compile FreeRTOS_Toggle_Led_Example_S32K358_SMP project and it produces the following error: C:/NXP/workspaceS32DS.3.6.0/FreeRTOS_Toggle_Led_Example_S32K358_SMP/generate/include/FreeRTOSConfig.h:64:66: error: implicit declaration of function 'taskDISABLE_INTERRUPTS' [-Werror=implicit-function-declaration] arm-none-eabi-gcc "@RTD/src/Clock_Ip.args" -MMD -MP -MF"RTD/src/Clock_Ip_Monitor.d" -MT"RTD/src/Clock_Ip_Monitor.o" -o "RTD/src/Clock_Ip_Monitor.o" "../RTD/src/Clock_Ip_Monitor.c" 64 | #define configASSERT(x) if((x)==0) { taskDISABLE_INTERRUPTS(); for( ;; ); } | ^~~~~~~~~~~~~~~~~~~~~~ ../FreeRTOS/Source/portable/GCC/ARM_CM7/r0p1/portmacro.h:184:17: note: in expansion of macro 'configASSERT' 184 | configASSERT( Get_64(&ucRecursionCountByLock[ulLockNum]) != 255u); | ^~~~~~~~~~~~ Missing #include? Is there a quick way to fix this? I'm using DS 3.6.0 and 'FreeRTOS for S32K3XX version 5.0.0' package. Example taken from 'SW32K3 FreeRTOS 11.1.0 5.0.0 CD1 D2409 Example Projects' section of the above package. thanks Re: S32DS - S32K3xx SMP example compilation error Thanks Julian. It worked! Re: S32DS - S32K3xx SMP example compilation error Hi @ogai, This issue has already been reported to the SW team. The provided example is incomplete, and some workarounds are needed for it to work correctly:  1. Configuration .mex needs to be updated to include SMP support: 2. Calls to vPortGET_CORE_ID need to be replace with calls to portGET_CORE_ID.  3. In ASSERT(), change macro definition to "if((x)==0) {__asm volatile ( " cpsid i " ::: "memory" ); for( ;;); } Best regards, Julián

BLDC 电机控制 如何使用 NXP S32K3 微控制器控制 BLDC 电机 回复：BLDC电机控制 @Senlent 谢谢 回复：BLDC电机控制 有没有使用 s32k 微控制器控制无刷直流电机的源代码或参考代码 回复：BLDC电机控制 你好@Kalase 这就是我针对您的问题所找到的答案： S32K344-六步换向控制 https://community.nxp.com/t5/S32K-Knowledge-Base/S32K344-Six-step-commutation-control/ta-p/1804572