Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
Profinet porting on iMX95EVK Hi, I am trying to port NXP-Port GMBH provided profinet stack on my iMX95 EVK on linux core I have found access to below link where it is tested on i.MX-RT1180 and also on iMX94. Profinet stack link  My queries are: 1. Please confirm imx95 supports this and this stack can be ported for evaluation purpose. 2. Please also share any documents that I can refer to port this stack on linux. Please let me know if you need any other information from my end. Thanks Gaurav  Re: Profinet porting on iMX95EVK I hope his email finds you well,  At this moment, i.mx95 doesn't support the PROFINET Industrial Ethernet Protocol Software. Only the mentioned devices:  Oswalag_0-1786397230469.png Re: Profinet porting on iMX95EVK Hi @Oswalag , Thanks for the reply. I have checked that imx94 and imx95 are quite similar and if the stack is working on imx94 then with some efforts it should be portable on imx95. I have few queries: 1. Please confirm whether profinet stack is ported on M7 core or linux core  on IMX94. 2. Are there any documents available that can help with porting on IMX94? Thanks, Gaurav Re: Profinet porting on iMX95EVK Hi, Any update on this query. Re: Profinet porting on iMX95EVK Hello,  Please check the following fact-sheet, there is information about the core's roles  https://www.nxp.com/docs/en/fact-sheet/PROFINETFS.pdf All the available documentation is in https://www.nxp.com/design/design-center/software/development-software/software-for-industrial-networking/profinet-industrial-ethernet-protocol-software:PROFINET-INDUSTRIAL-COMMUNICATIONS-SOFTWARE For more information you can contact NXP Pro Support services 
View full article
关于RAM空间分配的问题 各位NXP官方的技术人员你们好 我在使用S32K144的过程中遇到了一些问题 在这个地址分配表中 System RAM 空间SRAM_L (extends downwards)和SRAM_U (extends upwards)的大小 对于 S32K144芯片是不是支持用户自定义 对于全局变量地址的分配问题 初值不为零的全局变量存放在SRAM_L  中 初值为零的变量存放在SRAM_U 中 这是为什么  而且  SRAM_L  SRAM_U 如果支持自定义大小的话  他们两个地址段的起始地址和结束地址有规定吗 为什么 全局变量有无初值  芯片分配的地址段不同 我很想了解关于这个芯片的flash分配的相关问题  如果有这方面的教学资料  可以让我知道在哪下载吗? 衷心期待得到您的回复 万分感谢! Re: 关于RAM空间分配的问题 嗨@Ni_ 有应用笔记可供参考。虽然它是为 S32K3 设备设计的,但 RTD 中使用的连接器概念对于 S32K1 设备来说本质上是相同的。因此,它应该可以作为理解和配置链接器的有用参考。 AN14893 :S32K3xx 链接器文件和启动代码
View full article
Memory error occurs during flashing in TRACE32 When flashing via TRACE32 scripts, memory cannot be accessed. What could be the root cause? Re: Memory error occurs during flashing in TRACE32 As shown in the attached script, Lauterbach occasionally fails to access RAM. This issue can be resolved by re‑flashing the software via PE. Re: Memory error occurs during flashing in TRACE32 Hello @代码织梦师, Could you share which device you are using? Also verify the flash algorithm path in the .cmm script matches the device derivative.  From the image, I assume you are reading SRAM in S32K3, which does need ECC initialization, can you confirm you, or the startup file is correctly initializing SRAM ECC after POR? Best regards, Julián  Re: Memory error occurs during flashing in TRACE32 Hello @代码织梦师, It could be SRAM ECC initialization, although both the debugger as well as the startup code should initialize the SRAM ECC, if enabled. You can try the init_sram.cmm from demo scripts in T32: Best regards, Julián
View full article
lwip_FreeRTOS_s32k396 example project for MCSPTR2AK396 Development Kit Hello! I am working with the 3-Phase Permanent Magnet Synchronous Motor Control Development Kit with S32K396 MCSPTR2AK396. To test the base firmware, I installed the following stack: S32DS_3.6.5_RFP_win32 S32K3_ETPU_SW_4.9_2.0.1_D2512 SW32K3_S32M27x_RTD_R23-11_7.0.0_QLP03_D2512 SW32K3_FreeMASTER_Driver_1.5.0_D2512 S32K3xx_AMMCLIB_RTM_1_1_45_BIN MCSPTR2AK396_SW GCC version 10.2 After several unsuccessful attempts to synchronize all software versions, it finally worked, and the base firmware started functioning. However, I wanted to test the Ethernet communication functionality next, and that’s where I encountered unresolved issues at the moment. I additionally installed: SW32K3_FreeRTOS_11.1.0_0.8.0_CD1_D2603 SW32K3_TCPIP_STACK_4.0.0_D2512 And I took the test project lwip_FreeRTOS_s32k396, but it never compiled without errors; there were always conflicts in descriptions and other issues. I tried using the latest version of SW32K3_TCPIP_STACK_5.0.0_CD01_D2605, and I had to apply a file replacement during the update code process. In the end, the firmware compiled with warnings but no errors. After that, I moved on to testing. I set up the system as follows: personal computer -> GeekStore 100BT1-PRO2 Automotive Converter (http://pinzhi-tech.com.cn/en/home_eng/product_list_100base-t1_eng/100bt1-pro2_eng/) -> MCSPTR2AK396. I aligned the IP addresses of the Ethernet connection on the computer and the one specified in the firmware so they would be in the same subnet. However, attempting to ping the motor's assigned IP from the computer was unsuccessful, although it seems the network polling is ongoing, as indicated by the converter. What could be the issue? Could it be that I shouldn’t have used the latest version of TCPIP_STACK? Are there possible issues with the board itself? On the controller board stickers, revisions B1 and B are indicated. Is it possible to obtain additional documentation specifically for these revisions (on the website, I only saw documentation for revision A)? I would appreciate any advice or clarifying questions. Re: lwip_FreeRTOS_s32k396 example project for MCSPTR2AK396 Development Kit Hello @Anna_Anna, Firstly, I am not sure what errors were present with TCPIP v4.0.0, since it is also compatible with RTD 7.0.0 & FreeRTOS 7.0.0 CD01 packages, however, latest TCPIP stack (v5.0.0) is OK. Can you share what was the file modification? I was able to import, generate and compile the project without problem. My environment: S32DS v3.6.0, RTD v7.0.1, FreeRTOS v7.0.0 CD 01 and TCPIP Stack version 5.0.0 CD 01. It seems that MCSPTR2AK396 has a design oversight. EMAC_MII_RMII_RX_DV (PTD14) is not connected to RX_CTL - CONFIG6: MCSPTR2AK396 EVB ethernet connectivity, CRS_DV signal clarification. That said, is the task and OS is running?  xTickCount — this should be incrementing continuously if the RTOS tick interrupt is active. xSchedulerRunning — this should be set to 1 if the scheduler is running. Best regards, Julián    Re: lwip_FreeRTOS_s32k396 example project for MCSPTR2AK396 Development Kit Hello  Regarding the design files, I can see that the HW Design Package for MCSPTR2AK396 includes revision B2: Julin_AragnM_3-1786576291659.png Best regards, Julián Re: lwip_FreeRTOS_s32k396 example project for MCSPTR2AK396 Development Kit Hello @Anna_Anna, Yes, the fsdata.c and EthIf.c in previous release was reported and fixed; EthIf.c file from RTD is just a stub. We provide our own minimal implementation for EthIf, so the file from RTD can be safely excluded from the project. Secondly, yes, from your description, it seems that the example works properly. The connection is needed and should be done as mentioned (routing/soldering CRS_DV to PTD14).  Best regards, Julián Re: lwip_FreeRTOS_s32k396 example project for MCSPTR2AK396 Development Kit Hello @Julián_AragónM! The issue with building the test project using TCPIP v4.0.0 was resolved by excluding two files, fsdata.c and EthIf.c, from the build. This conflict seems to have been automatically resolved in version 5.0.0. I also checked the values of the variables xSchedulerRunning and xTickCount through the Expressions window in the S32DS debugger. xSchedulerRunning indeed takes the value 1, and the second one increases sequentially (1, 5001, 10001...), leading me to conclude that FreeRTOS is functioning correctly on the board, and the problem is not in the software. If I understand correctly, the only remaining cause is a hardware issue—the absence of a connection between CRS_DV (CONFIG6) on the TJA1103A and pin PTD14? To resolve this, do I need to solder these two contacts together? Please confirm. Best regards, Anna  Re: lwip_FreeRTOS_s32k396 example project for MCSPTR2AK396 Development Kit Thanks, I'll try this approach a little later and report back on the results. Re: lwip_FreeRTOS_s32k396 example project for MCSPTR2AK396 Development Kit Hello. After I soldered pin 41 (PTD 14) of the MCU and pin 25 (RX_CTL/CONFIG6) of the TJA1103A, the ping really started working. Thanks!
View full article
mc9s08qg8 drivers device manager: Jungo connectivity WinDriver:      Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)   pemicrowindvr:    This device is working properly.   These r the drivers i have in jungo!!!   ur input:   In USB Multilink Universal and USB Multilink Universal FX Technical Summary [USBMLUNIVERSALFX] documentation Chapter 6 Driver Installation mention that a copy of the driver installation program may be downloaded from P&E page "Support Center">Downloads. if you need an updated driver.   Best Regards,   What do u mean by this. Is this where i can get my BDM driver for my Wiztronics.com P&E interface board? Re: mc9s08qg8 drivers Hello, From the other post, I was referring that, as you are using P&E USB multilink Universal, the support page could redirect you to download a patch or an upgrade to your driver, I found these resources that could maybe help you if you have an incorrectly driver. In these page, its mentioned some patches for CodeWarrior v10.2 or higher and v6.3, to add support for PE hardware if is not detected by the operating system. PEmicro FAQ ID 211 Another option USB Multilink Resources Install Is a resource package for USB Multilink Universal, for when running older software. Also could you help us share which exact version of USB multilink Universal are you using? I could not guarantee this will work, since it’s a partner page, but it could redirect you in how to look for a driver correction for your issue, hope this information was helpful and let me know if that work for you Best Regards.
View full article
MC3377ASP1 AFE is Burning Hi Everyone, I am using MC33774SP1 AFE for my BMS application. I am using it for cell voltage measurement, cell balancing [external+internal] on my board. I am using it for 15s battery pack though i have designed it for 18 cells. I am shorting the last three terminals to make it as 15s. I am facing AFE burning issues in which Vbat and ground pins are getting short and fire is getting observed on IC. I am attaching my schematic for your reference as well. Could you please guide me related to this. Also, I am using a wakeup circuitry for my BMS in between VBAT and VSTACK pins. Re: MC3377ASP1 AFE is Burning Hi, Using the MC33774ASP1 in a 15s configuration is possible, but the unused upper channels must be connected correctly. For a 15s stack, the active cell connections should use CT0 to CT15 and CB0 to CB15. The unused upper pins should be connected to the highest used cell node, meaning CT16, CT17 and CT18 should be tied to CT15, and CB16, CB17 and CB18 should be tied to CB15. One important concern from the schematic is the VBAT/VSTACK connection. It appears that VBAT is supplied from VSTACK through diode circuitry. Please note that VBAT must closely track the highest CT/CB cell node. In particular, the voltage difference between VBAT and the highest CB node must remain within the datasheet limits. If the diode path or wake-up circuitry creates a voltage drop or transient difference between VSTACK/highest CT/CB and VBAT, this could overstress the device. Please check the following points before continuing powered tests: 1. Confirm that CT16, CT17 and CT18 are tied locally to CT15, and CB16, CB17 and CB18 are tied locally to CB15 for the 15s configuration. 2. Confirm that VBAT is connected to the actual top-of-stack node through the recommended VBAT filter and that the wake-up circuit does not introduce a diode drop or transient offset between VBAT and the highest CT/CB node. 3. Measure VBAT, VSTACK, CT15 to CT18, and CB15 to CB18 during pack connection, wake-up and power-up. The transient behavior is important, not only the steady-state voltage. 4. Confirm that balancing and measurement are disabled for the unused upper channels. 5. Confirm that the external balancing MOSFET circuitry for the unused channels cannot create any unintended current path. 6. Please also verify the capacitor values on the CT/CB sensing lines. If large capacitors are used on each cell tap, the inrush current during pack connection may cause transient overstress. Based on the destructive nature of the failure, with VBAT and ground becoming shorted and visible IC damage, this should be treated as a possible hardware overstress condition. I recommend stopping further powered tests until the VBAT/VSTACK relationship and the unused-cell connections are verified with measurements. BRs, Tomas Re: MC3377ASP1 AFE is Burning Hi Tomas. Thanks for the prompt reply. One issue I found that the difference between my VBAT and CB18 was around 1.6V, which was more than the recommended value of 0.4V . I am suspecting it might be causing my AFE burning. I am checking it further and will post my results. Thanks and Regards, Abhishek
View full article
ECSPI1 does not generate expected SPI clock on custom board Hi Team, We are working with an i.MX8MP custom board based on the i.MX8MP EVK configuration. On the i.MX8MP EVK, we have an SPI device connected through ECSPI2. With the existing EVK Device Tree configuration, SPI communication is working correctly, and we can observe the expected SCLK waveform on the oscilloscope. On our custom board, the SPI interface is connected to ECSPI1 instead of ECSPI2. We therefore modified the Device Tree configuration to use ECSPI1. However, with ECSPI1, we are not able to observe the expected/correct SPI clock pulses on the SCLK pin. We have tried several different Device Tree configurations, but the issue remains. 1. ECSPI1 configured similar to the existing ECSPI2 configuration We changed the controller from ECSPI2 to ECSPI1 and created the corresponding ECSPI1 pinctrl group, including SCLK, MOSI, MISO and CS. 2. Separate CS pinctrl group We also tried defining a separate pinctrl_ecspi1_cs and using it along with the ECSPI1 pinctrl group. 3. Explicit ECSPI1 pinmux configuration We also tried explicitly defining the ECSPI1 pins. However, with ECSPI1, we are still unable to observe the expected SPI clock pulses. We would like to know when configuring ECSPI1 on i.MX8MP, are there any additional Device Tree or pinctrl changes required apart from enabling &ecspi1 and configuring the ECSPI1 SCLK/MOSI/MISO/CS pins? In particular, is there any ECSPI1-specific pinctrl, clock, IOMUX, or other Device Tree configuration that needs to be added for ECSPI1 to operate correctly? The same SPI setup works on ECSPI2, so we would like to understand whether there is any additional configuration required when moving the interface from ECSPI2 to ECSPI1. Thanks in advance for your guidance. Re: ECSPI1 does not generate expected SPI clock on custom board Hi ,  Please find the dts file attached Re: ECSPI1 does not generate expected SPI clock on custom board Hi @SWETHA1  Please share your dts file about ECSPI1.  B.R Re: ECSPI1 does not generate expected SPI clock on custom board Hi @SWETHA1  I have checked your dts file, I found the following errors: 1. ECSPI pins have been reused, causing a pin usage conflict. Please remove this part or use other pins for reuse.     pinctrl_ecspi1: ecspi1grp {         fsl,pins = <             MX8MP_IOMUXC_ECSPI1_SCLK__ECSPI1_SCLK       0x48             MX8MP_IOMUXC_ECSPI1_MOSI__ECSPI1_MOSI       0x48             MX8MP_IOMUXC_ECSPI1_MISO__ECSPI1_MISO       0x48         >;     };     pinctrl_uart3: uart3grp {         fsl,pins = <             MX8MP_IOMUXC_ECSPI1_SCLK__UART3_DCE_RX      0x140             MX8MP_IOMUXC_ECSPI1_MOSI__UART3_DCE_TX      0x140             MX8MP_IOMUXC_ECSPI1_SS0__UART3_DCE_RTS      0x140             MX8MP_IOMUXC_ECSPI1_MISO__UART3_DCE_CTS     0x140         >;     }; 2. The ECSPI1 chip select (CS) configuration is contradictory. Please change it to the following code.     pinctrl_ecspi1_cs: ecspi1cs {         fsl,pins = <             MX8MP_IOMUXC_ECSPI1_SS0__GPIO5_IO09     0x40000         >;     }; B.R Re: ECSPI1 does not generate expected SPI clock on custom board Hi @pengyong_zhang, Please find the below observations 1. Logic analayser result when used the suggested changes SWETHA1_1-1786532293061.pngSWETHA1_1-1786532293061.png 2. Another observation when used the below patch on top of the previously attached dts SWETHA1_0-1786532274946.pngSWETHA1_0-1786532274946.png the above graph observed with this changes pinctrl_ecspi1: ecspi1grp { fsl,pins = < MX8MP_IOMUXC_ECSPI1_SCLK__ECSPI1_SCLK 0x80 MX8MP_IOMUXC_ECSPI1_MOSI__ECSPI1_MOSI 0x80 MX8MP_IOMUXC_ECSPI1_MISO__ECSPI1_MISO 0x80 >; }; With the suggested changes, we could see the clock is not as expected.  Re: ECSPI1 does not generate expected SPI clock on custom board Adding a few more details for the last response Observation 1: The result obtained after applying the suggested DTS changes. However, the SPI clock waveform is still not as expected, and the overall SPI signal behavior does not match the expected result. Observation 2: When MISO is left floating, CS shows two unwanted spikes, which is not the desired behavior. CS is initially driven low. Even when CS is configured to be driven high through the DTS, it is initially driven high as expected; however, after a transaction, CS appears to go low again. Could you please share your insights on this and guide to proceed further Re: ECSPI1 does not generate expected SPI clock on custom board Hi @SWETHA1  1. Please share your latest dts file. 2. How did you test the SPI device? You can use the `spidev_test` tool to run SPI tests. Please share the output of your `ls /dev/` command. B.R Re: ECSPI1 does not generate expected SPI clock on custom board Hi  Please find the attached dts files correspoding to shared observations 1 and 2.  The output of ls /dev shows /dev/spidev1.0 As for testing the spidevice , I have used the attached c file , which is verified working in  evk board where the spi is connected to ecspi2 and used the existing pinctrl groups. Now the validation results are taken and shared under the custom board based on evk where spi is connected in ecspi1.
View full article
Project [Rename] , 造成 整個 Project 丟失 餓死抬頭  S32DS 3.5  面對 相似 新Project  對 舊Project 做 [Rename] 動作  新Project 沒有生出來 就算了  將我 原有的 舊Project 也刪除了 !!  Explorer 已找不到原Project Folder  chkdsk 表示 無錯誤 !   請問,我該如何 救回 原有 舊Project !??  另,為什麼 [數字開頭的 Project Name] 不合法? ??   Spoiler (Highlight to read) S32DS-ARM S32DS-S32PLATFORM #rename    #rename  Re: Project [Rename] , 造成 整個 Project 丟失 你好@CY9 , 我不认为这是由于子文件夹数量造成的。从日志元数据中可以看到,在“2026-08-10”执行的重命名操作失败了: !ENTRY com.nxp.s32ds.ext.ide.core 4 0 2026-08-10 08:50:24.109 !MESSAGE Unexpected error during rename !STACK 1 我推断您要重命名的项目是“202503021_App_118”,您尝试将其重命名为“ADB22pxAPP_VR”,对吗?我看到以下错误: org.eclipse.core.internal.resources.ResourceException(/ADB22pxAPP_VR)[374]: java.lang.Exception: Resource '/ADB22pxAPP_VR' already exists. 但是,我不确定这是否是根本原因,因为我尝试将一个项目重命名为一个已存在的项目,但却失败了: 所以,仅凭这些信息,我真的无法得出结论。我唯一能建议的操作是使用 Recuva 扫描整个磁盘,查找 202503021_App_118 和 ADB22pxAPP_VR。如果项目无法恢复,我不确定是否还有其他可行的解决方案。 此致, 朱利安 Re: Project [Rename] , 造成 整個 Project 丟失 是的, 我确信 ` ADB22pxAPP_VR` 不存在。 它确实存在,而且你的程序也找到了它。 是否应该停止重命名功能!? 实际上,它删除了整个目录。 我完全不知道发生了什么事。 Recuva找不到任何文件夹。 我正在尽快抢救一些文件。 谢谢你的关心。
View full article
Inquiry on Alternative Parts for MW6S010GNR1 Dear  support team  Part number MW6S010GNR1 has been discontinued. Could you please recommend equivalent alternative models? Our application is industrial wideband RF equipment. thanks so much Re: Inquiry on Alternative Parts for MW6S010GNR1 **MW6S010GNR1 Status & Recommended Alternatives** ### Part Overview **MW6S010GNR1** (NXP / former Freescale) is a **10 W, 28 V LDMOS** RF power transistor designed for broadband applications. | Parameter | Value | |------------------------|--------------------------------| | Frequency range | 450 – 1500 MHz | | Output power | 10 W | | Supply voltage | 28 V (qualified up to 32 V) | | Typical gain | ~18 dB @ 960 MHz | | Package | TO-270-2 Gull Wing (GNR1) | | Application | Class A / AB, base station, broadband industrial RF | **Status**: Discontinued / End of Life (part of NXP Radio Power product line ramp-down). Last Time Buy is expected around **30 September 2026**, with final shipments targeted for **2027**. --- ### Recommended Equivalent / Alternative Models There is **no exact pin-to-pin drop-in replacement** from NXP. Below are the closest practical alternatives for industrial wideband RF equipment. All will require matching network re-optimization. | Priority | Part Number | Manufacturer | Key Specs | Package | Notes / Compatibility | |----------|----------------------|--------------|----------------------------------------|--------------|-----------------------| | 1 | **MW6S010NR1** | NXP | Same electrical specs as GNR1 | TO-270-2 | Non-Gull Wing version of the same die. Also discontinued, but may still have residual stock. | | 2 | **BLP15H9S10G** or **BLP15H9S10** | Ampleon | 10 W, 50 V, very wideband (1–2000 MHz) | TO-270 | Excellent wideband industrial alternative. Higher voltage, needs matching redesign. | | 3 | **BLP15M9S30G** / related 28–32 V devices | Ampleon | 30 W class, 1–1500 MHz, 32 V | TO-270 | Higher power option if headroom is acceptable. | | 4 | **AFT27S010N** | NXP | ~10 W, 28 V, broader frequency coverage | Plastic | Newer generation, but different package and matching required. Check current availability. | | 5 | Other 10 W / 28 V LDMOS | Ampleon / Infineon | Various | TO-270 or similar | Search for unmatched wideband LDMOS in 10 W class. | --- ### Practical Recommendations for Industrial Wideband Use 1. **Short-term** - Check remaining stock of **MW6S010GNR1** and **MW6S010NR1** for Last Time Buy. - If pin-out compatibility is critical, prioritize the NR1 version if available. 2. **Medium / Long-term (Recommended)** - Migrate to **Ampleon BLP15H9S10(G)** series. These are modern, wideband, rugged LDMOS devices commonly used in industrial, ISM, and broadband RF applications. - They offer better long-term availability and support. 3. **Design Notes** - Expect to redesign the input/output matching networks. - Verify thermal performance, bias point (IDQ), and VSWR ruggedness in your specific industrial environment. - Confirm package footprint and soldering profile compatibility. --- **Would you like me to:** - Compare detailed electrical parameters (gain, efficiency, capacitances) between MW6S010GNR1 and a specific alternative (e.g. BLP15H9S10G)? - Help search for current stock/pricing of the recommended parts? - Suggest matching circuit references or evaluation boards? Please share your exact frequency band, power requirement, and preferred supply voltage if you need a more targeted recommendation. Email: [email protected] Re: Inquiry on Alternative Parts for MW6S010GNR1 Hi lotu, the BLP15H9S10 above is a 50 V part, so that's a new supply rail, not just a rematch. Ampleon's BLP0427M9S20GZ keeps you at 28 V, it's the same TO-270-2 gull wing, and it covers 400 to 2700 MHz, so your whole band. DigiKey had 145 in stock today. I found it on https://parter.ai/alternatives/nxp-usa-inc/mw6s010gnr1?utm_source=nxp_community along with a few others. Raz, Parter (AI Supply chain app)
View full article
[FRDM-IMXRT1186] Question about ADC Power Sequencing (VDDA_1P8 vs 3P3) I am reviewing the FRDM-IMXRT1186 (SCH-95302 Rev.A4) and the RT1180 Data Sheet Rev.9. The datasheet requires VDDA_ADC_1P8 to be powered prior to VDDA_ADC_3P3. However, on the FRDM board, VDDA_ADC_1P8 comes from an AMS1117-1.8 regulator tied to VDD_3V3, meaning it follows the 3.3V rail's soft-start. Additionally, VDDA_ADC_3P3 is left floating by default (R337=DNP). My questions: 1.Is the FRDM board considered compliant with the datasheet sequence given this implementation? 2.For a production design, is it mandatory to use a PMIC or an LDO with an EN pin to strictly meet the "prior-to" requirement? 3.I have attached a screenshot of the relevant schematic section. I will post my detailed analysis in the comments below to keep this initial post clear. FRDM-Training i.MXRT 106x Re: [FRDM-IMXRT1186] Question about ADC Power Sequencing (VDDA_1P8 vs 3P3) Hi @rejust , Thank you so much for your interest in our products and for using our community. Yes, from the default FRDM-IMXRT1186 schematic, the design is intended to meet this sequencing requirement. R337 is DNP by default, so VDDA_ADC_3P3 is not directly tied to VDD_3V3 through the 0 Ω bypass path. Instead, VDDA_ADC_3P3 is supplied through the U17 MOSFET sequencing circuit. This circuit is controlled by the VDDA_ADC_1P8 / ADC_1V8_IN rail, so VDDA_ADC_3P3 is enabled only after VDDA_ADC_1P8 is established. For production design, a PMIC is not mandatory. Any reliable sequencing method is acceptable, such as a PMIC, LDO/load switch with EN control, or a MOSFET sequencing circuit, as long as the timing at the SoC pins meets the datasheet requirement. Wish it helps you Best Regards May
View full article
HSE AB Swap works from bare metal but fails after MCAL clock setup on S32K312 Hi, I am working on HSE-B AB Swap on an S32K312 MINI-EVB with HSE firmware version 0.2.55.0 (ab_swap variant). The board is in OEM_PROD lifecycle and Bank A is currently active. Both banks hold the same HSE firmware version. I have a working reference where a bare-metal main function polls HSE INIT_OK and then submits the activate passive block service. That call returns success and the swap applies on the next reset. Bank B contains a valid IVT with pointers compiled for the lower address space per section 11.3 of RM00286. The same MU submission code, moved into a bootloader after MCAL clock initialization, returns HSE response 55A5A26A (invalid address). HSE INIT_OK stays set. Other HSE services (AES, RSA, SHA) work correctly in this state. The only difference between the working and failing runs is that the bootloader path writes the MC_CGM MUX 0 divider registers during clock initialization, keeping the source on FIRC but changing the AIPS_SLOW to HSE_CLK ratio from 1:1 (SBAF default) to 1:4. My main question: what does the invalid address response refer to for the activate passive block service, since the service takes no data structure? Is there a documented sequence for reconfiguring MC_CGM dividers after HSE has reached INIT_OK, that keeps this specific service usable? I can share the failing binary, register dumps, and clock config on request. Thanks Re: HSE AB Swap works from bare metal but fails after MCAL clock setup on S32K312 Hi David, Thank you for the guidance about the DCF client. To make sure I set this up correctly on the first attempt, could you please clarify a few things: 1. Point 5 in your list says the MC_CGM MUX 0 source must be PLL_PHI0. Is this a hard requirement — does the activate passive block service require the system clock to be on PLL, or can it also work with the system running on FIRC (48 MHz)? 2. Could you share the earlier points 1 to 4 from the same list? We only have points 5 and 6 in the image and suspect we are missing prerequisites. 3. Point 6 gives the DCF value for a 120 MHz HSE clock scenario. For a 48 MHz FIRC configuration with AIPS slow clock at 12 MHz (1:4 ratio), what value should be programmed into the UTEST_MISC DCF record's clock mode and gasket control bit field? 4. What is the exact UTEST address on S32K312 for this record, and is there a sample or a Design Studio / Cyclone algorithm file we can use to program it safely? Since UTEST is one-time programmable, we want to be certain before writing. 5. Are there any other DCF records required for AB Swap beyond UTEST_MISC — such as an OTA enable marker in UTEST, or OTA indicators inside the active and passive blocks? If yes, please share those as well. Board context: HSE firmware 0.2.55.0 ab_swap variant, OEM_PROD lifecycle, INIT_OK and OEM SU rights bits set. Thanks a lot, Re: HSE AB Swap works from bare metal but fails after MCAL clock setup on S32K312 I guess you don't have setup DCF client what is necessary for use as you described. Re: HSE AB Swap works from bare metal but fails after MCAL clock setup on S32K312 1) I didn't want to take a screenshot of point 5, but point 6. 2) It is taken from RM: 3) The key point is ratio 1:4. Also it is described in RM embedded attachment (S32K3xx_DCF_clients.xlsx) 4) DCF record address to be programmed you will have to find out yourself (to find first location with 0xFFFF_FFFF). Specifically is should be around address 0x1B000780, but double check it before programming. See following document to understand DCF records: https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/MPC57xx-DCF-records/ta-p/1114884 Also DCF calculator exists: https://community.nxp.com/t5/S32K-Knowledge-Base/S32K344-DCF-Configurator/ta-p/1986243 I have been using TRACE32 script as follows: ; Program UTEST do ~~\demo\arm\flash\s32k3.cmm prepareonly flash.Program 3. /OTP ;put lines generated by S32K344 DCF configurator data.set 0x1B000780 %QUAD 0x0010000460000101 ;dcf_client_utest_misc flash.Program off Mentioned DCF calculator also allows you to create S-records that may be programmed by any programmer/debugger. 5) OTA flag is programmed automatically when AB_SWAP HSE FW is being installed, user don’t need to care of it. I am not aware of other DCF configurations needed. Re: HSE AB Swap works from bare metal but fails after MCAL clock setup on S32K312 Hello, Follow-up: I have prepared the DCF record for dcf_client_utest_misc per your instruction (value 0x0010000460000101, target address 0x1B000768 — first free QUAD on my board, verified). However, S32DS + PEmicro Multilink debug configuration silently skips the UTEST write — bytes at 0x1B000768 remain FFFFFFFFFFFFFFFF after the flash session. What is the correct tool/procedure to program a single DCF record into UTEST OTP on S32K312 using PEmicro Multilink (or any tool that ships with S32DS 3.6.4)? Do I need a specific flash algorithm file, a different debug configuration, or the standalone S32 Flash Tool?
View full article
Building NXP Android 16 BSP in AWS or GCP Cloud – Experience, Setup and Build Times Hi everyone, I am currently working on setting up Android 16 for an NXP i.MX 95 and would like to build the NXP BSP in a cloud environment. The release I am using is: Android 16.0.0_2.0.0 (L6.18.20_2.0.0 BSP) I am currently looking into using AWS or Google Cloud Platform (GCP) as the build environment instead of a local workstation. I would therefore like to ask the community: Is there any official NXP documentation or recommendation for building the Android BSP in AWS or GCP? Has anyone already successfully built this Android BSP in AWS or GCP? Which instance/VM configuration did you use (CPU, RAM, storage, etc.)? Approximately how long does a complete BSP build take in your setup? What were the approximate cloud costs per build? Are there any specific issues or limitations to be aware of when building the BSP in a cloud environment? I am especially interested in practical experience, for example which cloud instance type worked well and whether there are any important considerations regarding RAM, disk space, CPU cores, storage performance or build parallelization. Any recommendations, example configurations or lessons learned would be greatly appreciated. Thanks in advance for sharing your experience! Best regards Fb Re: Building NXP Android 16 BSP in AWS or GCP Cloud – Experience, Setup and Build Times Hello @Feevlic  Hope you are doing very well. We do not have documentation for that specific scenario for compiling Android. The process should be the same as a physical machine. Please try following the steps of the UG10156 Android User's Guide. Best regards, Salas.
View full article
MIMXRT1160 XIP fails randomly I have multiple boards running XIP from octal flash at 166 MHz. One of them fails occasionally  with "undefined instruction" error.  I've suspected signal integrity issues but I do not have test points on the PCB, so the only way to check that has been reducing speed from 166 MHz to 133 MHz, which appears to "fix" the problem with that particular board.  It's probably telling that the error appears most often when chainloading the application from mcuboot. It is more rare during application runtime. I can't find a reliable way to trigger it too - need to power-cycle the board several times until the fault appears.  Is there a way I can diagnose this XIP failure with more precision? Re: MIMXRT1160 XIP fails randomly Hi @tbonkers , The behavior you describe is most likely caused by insufficient read-sampling margin (setup/hold) at 166 MHz, due to tight PCB-routing/signal-integrity headroom on the Flash data lines. This also explains both symptoms: dropping to 133 MHz widens the sampling window so the issue "disappears"; and the mcuboot chainload is the first, dense, cache-cold instruction fetch right after a cold reset, where margin is tightest — hence it fails most often there, while runtime fetches mostly hit cache and rarely trigger it. We suggest the following checks, all software-side and requiring no PCB test points: Start with dummy cycles. Verify that the dummy-cycle count in the read LUT strictly matches your Octal Flash datasheet spec at 166 MHz. If an auto-generated FCB (e.g., from the provisioning tool) uses a lower value, set it to the datasheet-specified value, and you may add 1–2 extra dummy cycles to widen the data-valid window and increase sampling margin. Insufficient dummy cycles place the first data beat in the turnaround/not-yet-settled region — a classic source of intermittent errors. Verify the read sample-clock source . 166 MHz is only in-spec when readSampleClksrc=3 (kFlexSPIReadSampleClk_ExternalInputFromDqsPad: read strobe/DQS provided by the Flash device). If it is currently 0 or 1, 166 MHz is out of spec, which is fully consistent with "133 MHz fixes it." Please confirm a real DQS trace exists on the PCB and use this mode. If intermittent faults persist after these adjustments, you can run at 133 MHz as a safe baseline while isolating the 166 MHz margin bottleneck via steps 1–3 above. And this post may also help: https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Octal-flash-IS25WX256-dummy-cycles/m-p/2178828   Best wishes, Gavin Re: MIMXRT1160 XIP fails randomly Error log or schematics sharing could be helpful, how about the failing rate till now? Re: MIMXRT1160 XIP fails randomly Hi @Gavin_Jia , I've tested the read command with different dummy cycles count, and the failure is still there. I've set the number of dummy cycles in the flash volatile register to 20 so that it can support 166 Mhz. According to the flash datasheet it should support up to 200 MHz with 20 dummy cycles. readSampleClksrc=3 is set by the bootROM, confirmed with debugger connected. The DQS trace does exist.  Sometimes the fault happens while application is running, after the first major flash read. Re: MIMXRT1160 XIP fails randomly Hi @tbonkers , Thanks for the detailed testing. Based on your findings, this is most consistent with the 166 MHz Octal DDR XIP read path operating at the edge of its sampling / signal-integrity margin. readSampleClksrc=3 and the DQS trace are necessary but not sufficient conditions: in DDR DQS mode, the RT1160 side still requires the DQS-to-SIO relative skew to stay within ~±1 ns, and 166 MHz is the interface's upper limit, so margin is minimal.  I’ve looked into more resources, and the following solutions may help you resolve the current issue without modifying the PCB: Apply DLL errata ERR011377. The RT1160 errata states that after the DLL lock-status bit is set, an immediate read/write to the external flash may still return wrong data due to a timing issue; the workaround is to wait at least 512 FlexSPI root-clock cycles after the lock bit is set before accessing flash. Please ensure this delay is applied in every path in the bootloader and application that reconfigures FlexSPI/DLL/clock — this fits well with "most frequent at chainload, intermittent at runtime." Run a quantifiable RAM-resident stress test (more effective than repeated power-cycling). Place the test code and fault handler in ITCM/OCRAM, repeatedly read large flash blocks from the AHB memory map with CRC comparison, sweeping 166/133/120 MHz. If the error rate drops sharply as frequency decreases, it confirms a timing/SI-margin issue. For the mcuboot case:  if the bootloader ever erased/programmed the external NOR, you must invalidate I/D-cache before jumping to the application; also confirm the application does not re-initialize FlexSPI with different clock/DLL/LUT/pad settings. If in the end only 166 MHz fails while 133 MHz is stable, we recommend 133 MHz as the safe operating frequency for the current board; if 166 MHz is mandatory for production, the PCB DQS/SCLK/SIO length-matching, impedance, crosstalk, and pad drive strength should be reviewed, with test points added for these signals in the next revision. Best regards, Gavin
View full article
FAQs – NAFEB43388 and NAFEBx3388 Evaluation Board Introduction The NAFEB43388 is a highly configurable, industrial-grade, 8-input universal analog front-end designed for high-precision measurement applications such as PLCs, DCS I/O modules, remote/distributed I/O, data acquisition systems, instrumentation, and industrial automation. It integrates a 24-bit sigma-delta ADC, 13-bit DAC, high-voltage multiplexers, programmable gain amplifiers, precision references, diagnostics, and an integrated sense resistor with protection switch for current measurements. The NAFEBx3388-EVB evaluation board supports evaluation of pin-compatible NAFEB43388/NAFEB73388 family devices and is intended to demonstrate high-precision industrial measurements using the FRDM-MCXN947 MCU platform and a Windows-based GUI. For detailed register settings, timing diagrams, electrical limits, and calibration procedures, please refer to the latest NAFEB43388 product data sheet and the NAFEBx3388-EVB user manual available on nxp.com.  1. What is the NAFEB43388? The NAFEB43388 is a highly configurable multichannel universal-input Analog Front-End intended for precision industrial measurements. It integrates a 24-bit sigma-delta ADC, 13-bit DAC, low-leakage high-voltage multiplexers, low-offset and low-drift PGA stages, internal voltage references, diagnostics, and an integrated current-sense resistor protected by a smart e-fuse circuit. 2. What applications is the NAFEB43388 designed for? Typical applications include PLC and DCS I/O modules, remote and distributed I/O modules, sensor and data acquisition systems, instrumentation, and industrial automation or process-control equipment. 3. How many analog inputs does the NAFEB43388 support? The device provides eight high-voltage analog inputs plus one common input. These inputs can be configured for single-ended, differential, or pseudo-differential measurements depending on the measurement topology and register configuration. 4. What types of signals can the NAFEB43388 measure? The NAFEB43388 supports software-configurable measurement of voltage, current, resistance, RTD, and thermocouple-type sensor signals. The supported input ranges include voltage up to ±12.5 V, current up to ±25 mA, and resistance measurement capability from 1 mΩ to 1 MΩ according to the fact sheet, while the datasheet describes programmable current excitation for resistance and RTD measurements. 5. What is the ADC resolution and data-rate range? The NAFEB43388 integrates a 24-bit sigma-delta ADC. For the low-power NAFEB43388 variant, the ADC data rate is configurable from 7.5 samples per second up to 288k samples per second, depending on the selected data-rate code, SINC filter configuration, and settling mode. 6. What is the DAC resolution and output capability? The integrated DAC has 13-bit resolution and can be configured for voltage output or current output. The DAC supports voltage output up to approximately ±12.5 V full-scale and current output up to approximately ±2.5 mA full-scale, with a DAC data rate up to 100 ksps. 7. What is the difference between NAFEB43388, NAFEB43188, NAFEB73388, and NAFEH73388? The NAFE family includes low-power and high-speed variants, with or without factory calibration and HART modem support. The NAFEB43388 is a low-power, 24-bit, 8-input device with factory calibration and no HART modem. The NAFEB43188 is similar but without factory calibration. The NAFEB73388 is a high-speed 24-bit, 8-input variant with factory calibration, and the NAFEH73388 adds HART modem support. 8. What is the NAFEBx3388-EVB? The NAFEBx3388-EVB is an evaluation board designed to evaluate pin-compatible NAFEB43388 and NAFEB73388 AFE devices. It enables high-precision industrial measurements using the FRDM-MCXN947 MCU platform and includes a GUI for configuring and testing the device. 9. What hardware is included in the NAFEBx3388 evaluation kit? The evaluation kit includes the NAFEBx3388 evaluation board, an FRDM-MCX947 evaluation board with custom firmware, and a USB cable. The EVB is connected to the FRDM-MCX947 board through Arduino-compatible connectors. 10. How is the NAFEBx3388-EVB powered? The EVB can be powered using the supplied 24 V AC-DC adapter connected to J307, with jumpers J308, J309, and J310 set to the 2-3 position. Alternatively, external supplies can be applied: AVDD/DVDD = 3.75 V on J300, HVDD = +15.4 V on J301, and HVSS = -15.4 V on J302, accounting for the voltage drop across the protection diode in the supply path. 11. How does the NAFEB43388 support voltage measurements? The AFE can measure differential, pseudo-differential, and single-ended voltage signals. Single-ended measurements are performed by connecting the positive signal to AIxP or AIxN and the negative signal to AICOM, while differential measurements use the corresponding AIxP and AIxN pair. 12. What voltage input ranges are available? The input range depends on the total programmed channel gain. For single-ended input, the nominal linear ranges include ±10 V at gain 1, ±5 V at gain 2, ±2.5 V at gain 4, ±0.625 V at gain 16, ±0.313 V at gain 32, and ±0.156 V at gain 64. For differential input, the corresponding nominal linear ranges are ±20 V, ±10 V, ±5 V, ±1.25 V, ±0.625 V, and ±0.313 V. 13. How does the NAFEB43388 support current input measurements? The AI1P pin can measure current using the integrated 25 Ω sense resistor and the configurable current-input protection switch, CISW. This supports common industrial current ranges such as ±20 mA, 0 mA to 20 mA, and 4 mA to 20 mA. 14. What protection is available for current input mode? When current input mode is selected on AI1P, the integrated CISW protection switch supports fault handling. The datasheet describes three current levels: approximately 50 mA short-circuit or overcurrent threshold, 30 mA overload threshold, and 12 mA current-limiter level. The overcurrent deglitch time, overcurrent limit time, and limiter delay can be configured. 15. What is the purpose of the programmable gain amplifiers? The NAFEB43388 includes two PGA stages. PGA1 operates in the high-voltage domain and supports gains of 1 and 16, while PGA2 operates in the low-voltage domain and supports gains of 1, 2, and 4. Combining both stages provides total gains from 1 to 64, allowing the input range to be matched to the signal amplitude. 16. What are the available ADC reading modes? The NAFEB43388 supports five conversion modes: Single-Channel Single-Reading, Single-Channel Continuous-Reading, Multichannel Single-Reading, Multichannel Multireading, and Multichannel Continuous-Reading. These modes allow the host to choose between one-shot, continuous, host-driven, semi-autonomous, or autonomous multichannel acquisition. 17. When should normal settling or single-cycle settling be used? Normal settling is better suited for single-channel reading where maximum data rate is preferred, while single-cycle settling is recommended for multichannel systems to avoid settling-time error after switching channels. In normal settling, the ADC output stabilizes after four samples, while in single-cycle settling the output is stable in one cycle, but the effective data rate is four times slower. 18. What factors affect noise performance? Noise performance depends mainly on the selected data rate, PGA gain, digital filter order, and settling mode. Lowering the data rate reduces the equivalent noise bandwidth and therefore reduces noise. Increasing PGA gain can reduce input-referred noise because the PGA contributes less noise than the ADC. Higher-order digital filtering can also reduce noise by narrowing the effective bandwidth. 19. What calibration options are available? The NAFEB43388 includes user-accessible calibration coefficient registers for analog input gain, analog input offset, extra calibration coefficients, and DAC output calibration. Factory-calibrated options load coefficients from nonvolatile memory during power-up or reset, and users can also perform application-specific calibration using the available registers and GUI procedures. 20. What accuracy can be achieved with calibration? For voltage input with user calibration, the datasheet specifies typical room-temperature TUE of 0.002 %FS and maximum ±0.005 %FS under the stated conditions. Across temperature, typical TUE is listed as 0.05 %FS with maximum ±0.1 %FS. For current input using the internal sense resistor and user calibration, the listed typical room-temperature TUE is 0.00125 %FS with maximum ±0.005 %FS. 21. How is an external 4-wire PT100 connected and measured? For the external 4-wire PT100 demo, one red RTD wire is connected to AI2P and one white wire to AI3P to provide the current forcing path, while the other red and white wires are connected to AI3N and AICM for differential voltage sensing. The default GUI configuration uses AI3P-AI3N as the measured input, -2 mA DAC current excitation on AI2P, normal settling, PGA1 = 16x, PGA2 = 4x, 200 SPS, and SINC4_4 filtering. 22. What diagnostics are integrated in the NAFEB43388? The NAFEB43388 includes advanced diagnostics for fault and anomaly detection, including power-supply monitoring, under-/over-range detection on the signal path, redundant voltage-reference monitoring, temperature monitoring, CRC error detection, global alarm functionality, clock-deviation detection, and input/output overcurrent-related status flags. 23. How can multiple NAFEB43388 devices be synchronized? The device supports synchronization through the SYNCADC pin. A host-generated SYNC pulse can be connected to multiple NAFE devices so that conversions start simultaneously on the rising edge of the SYNCADC pulse. The device can also synchronize to the host using SYNCADC, synchronize the host to the NAFE data rate using DRDY, or share an external 18.432 MHz clock with the host for coherent measurements. SPI
View full article
MCX C15/C16 Product Training: Essential MCUs built for cost effective, low-end applications Picture1.png Welcome to MCX C15 and MCX C16 Product Training! This page provides access to training materials, presentations, demos, recordings, and supporting resources related to the MCX C15 and MCX C16 MCU family. While live Q&A support will be available during the training period, all content will remain accessible for future reference and self-paced learning.  Instructions  To get started with the MCX C15/C16 training, you will need to have your FRDM-MCXC162 in hand and perform the set-up operations according to the FRDM-MCXC162 Getting Started Page which is a pre-requisite.   Step 1. Mandatory pre-work before starting with the labs:  Getting Started with FRDM-MCXC162 Step 2. After completing the pre-work, download the lab guides. Each lab has its own guide document and a video guide you can use as support material in case you have any question at any step:  Lab0: Introduction to MCX C15/C16 and FRDM-MCXC162 Lab1: Low Power is a Superpower Objectives Download and run your first project from VS Code on the FRDM-MCXC16 Explore the basics of low-power modes Description Load the SDK low-power example, walk through the code flow, and review the available wake-up options. You'll also learn how to connect a current meter to the FRDM board to measure power consumption. Lab2: Low-Power Sensing Demo Objectives Download and run your first ACH example from VS Code on the FRDM-MCXC16 Explore a low-power sensing application Description Access and download examples directly from ACH in VS Code, then run a real-world low-power sensor use case. Lab3: PWM Lighting Demo Objectives Learn how to load firmware using LinkServer/LinkFlash and simple production-style scripts Explore the timer and PWM capabilities of the MCXC family Description Use a provided binary and step-by-step instructions to program the board. The demo controls the onboard RGB LED using PWM. Source code will also be available in ACH. Lab4: Connecting Expansion Boards to FRDM-MCXC162 Objectives Download an ACH example from VS Code Connect and use expansion boards with the FRDM-MCXC16 Description Connect an expansion board, download the example from ACH, and try a low-power sensing application using an external sensor. Additional requirements as below:  MikroE OLED B/W Click display in I2C mode SparkFun Qwiic dToF Imager (TMF8820) Qwiic board cable Step 3. Review the support material and useful links to get you up to speed with some product information, FRDM board information and Getting started. Below also includes additional reading material.   MCX C15/C16 Product Page  FRDM-MCXC162 Tool Summary Page  FRDM-MCXC162 Getting Started Page  MCX C1 Family Factsheet  MCX C15/C16 Datasheet   MCX C15/C16 Reference Manual  Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here  FRDM-Training Hands-On Training MCXC
View full article
MCX C Knowledge Hub The MCX C series MCUs, powered by Arm® Cortex®-M23 up to 72 MHz or Arm® Cortex®-M0+ up to 48 MHz, are designed for cost effectiveness and efficiency, making them ideal for low-end Industrial and IoT applications. Featuring precision analog peripherals as well as USB and segment LCD options, these MCUs cater to diverse needs. The MCX C Series extends the classical IPs within NXP MCUs, providing flexible and scalable memory and packages. MCX C MCUs offer features like USB and segment LCD support, making them ideal for a wide range of general-purpose applications. With a focus on versatility, these MCUs provide the performance and scalability needed for today’s evolving technology demands. Documents: MCX C Series  MCX C Fact Sheet MCX C Series Products MCX C04x:  The MCX C04x microcontrollers, featuring an Arm® Cortex®-M0+ core, offer 32 KB Flash, 2 KB SRAM, and 8 KB boot ROM. Designed as entry-level MCUs, they prioritize simplicity and ease of use for a variety of applications. Key peripherals include a 12-bit ADC, comparator and multiple-channel timer/PWM modules. The enhanced low-power architecture ensures efficiency, with static power consumption as low as 2.2 μA and a 7.5 μs wake-up time for full retention. In deep sleep, static mode power consumption drops to just 77 nA. This series supports scalable memory options and flexible packaging, accommodating diverse application needs. Documents: MCX C041 Sub-Family Reference Manual Data Sheet - MCX C04X Errata: MCXC041 Mask Set MCX C14x/C24x/C44x: The MCX C14x/24x/44x microcontrollers, featuring an Arm® Cortex®-M0+ core, offer a range of memory configurations, from 32KB to 256KB Flash and up to 32KB SRAM, with 16KB Boot ROM. These entry-level MCUs are optimized for cost-sensitive and battery-powered applications requiring low-power USB connectivity and segment LCD support. The FlexIO technology enables customization for various serial peripheral emulation needs. They feature optimized low-power modes, achieving efficiency down to 54uA/MHz in very low-power run mode and 1.96 uA in deep sleep mode with retained RAM and RTC. Documents: Data Sheet - MCX C24x/C14x Data Sheet - MCX C44x Errata:  MCXC - x41 x42  Errata: MCXC - x43 x44 MCX C44x Sub-Family Reference Manual MCX C24x Sub-Family Reference Manual MCX C15/C16: The MCX C15 and MCX C16 microcontrollers (MCUs) are low‑cost, entry‑level devices featuring an Arm® Cortex®‑M23 core running at up to 72 MHz, with memory configurations offering up to 64 KB of flash memory and 16 KB of static random‑access memory (SRAM). These devices bring precision analog and control peripherals into the low‑cost, entry‑level MCU class, making advanced features—such as a 16‑bit analog‑to‑digital converter (ADC), comparator with digital‑to‑analog converter (DAC) and flexible pulse‑width modulation (FlexPWM) for motor control—accessible to cost‑sensitive IoT applications. Designed as an upgrade path from legacy 8‑bit and 16‑bit MCUs, as well as devices based on Arm Cortex‑M0+ cores, this entry‑level 32‑bit MCU series delivers higher performance and greater scalability without increasing costs. Documents: Data Sheet -MCX C151/C161/C162  Fact Sheet - MCX C1 Family Reference Manual - MCX C15/C16  Boards: FRDM MCX C444: FRDM-MCXC444 is a compact and scalable development board for rapid prototyping of MCX C444 MCU. It offers industry-standard headers for easy access to the MCU's I/Os, integrated open-standard serial interfaces and onboard MCU-Link debugger.  FRDM-MCXC444 QSG Getting Started with FRDM-MCXC444 FRDM-MCXC444 Board User Manual FRDM MCX C242: FRDM-MCXC242 is a compact and scalable development board for rapid prototyping of MCX C242 MCU. It offers industry standard headers for easy access to the MCU’s I/Os, integrated open-standard serial interfaces and on-board MCU-Link debugger. FRDM-MCXC242 QSG Getting Started with MCXC242  FRDM-MCXC242 Board User Manual  FRDM-MCX C041:  is a compact and scalable development board for rapid prototyping of MCX C041 MCU. It offers industry-standard headers for easy access to the MCU’s I/Os, integrated open-standard serial interfaces and onboard MCU-Link debugger. FRDM-MCXC041 QSG Getting Started with FRDM-MCXC041 FRDM-MCXC041 Board User Manual MCX C to FRDM Board Mapping Supported MCU(s) Recommended Board Best fit for  Key Differentiators MCXC041 (16QFN, 24QFN) FRDM-MCXC041 Ultra-Low-cost entry-level designs  32KB flash - 2KB SRAM- 48MHz Cortex M0+ - LPUART - SPI - I2C - ADC MCX C141/ C142/ C241/ C242 /C441 /C442 / C444 FRDM-MCXC444 General-purpose USB and Segment LCD application Industrial / Consumer Up to 256KB Flash - 32KB SRAM - 48MHz Cortex-M0+ - USB FS 2.0 - SLCD - FlexIO - DMA 0 CAN-FD - Multiple UART/SPI/I2C MCX C151/ C152/ C161/ C162 FRDM-MCXC162 Motor Control Precision analog Power tools    medical devices Up to 64KB flash - 16KB SRAM - 72MHz Cortex-M23 - 16-bit ADC 2.4MSPS - FlexPWM - 4xUART - 45 GPIO   Application Notes: Software, Hardware and Peripherals: AN14321 Using Segment Liquid Crystal Displays (SLCD) Controller on MCX C444 MCU: This document describes the usage of the on-chip SLCD controller by enabling an SLCD device called S401M16KR. The S401M16KR is a four-digit 0.17-inch seven-segment LCD panel. AN14590 Running RT-Thread on MCUXpresso IDE: This document is intended for the users who are familiar with RT-Thread and want to port it to MCUXpressoIDE. It provides steps to streamline the porting process. The porting steps are applicable to other NXP chips also. This document uses FRDM-MCXC444 as an example. AN14319 FlexIO Emulating UART with IRDA: This application note introduces how to use the universal peripheral module FlexIO for emulating the UART bus with IRDA. The FlexIO peripheral, initially introduced on the MCXC242 and MCXC444 family, is a highly configurable module capable of emulating a wide range of different communication protocols. These communication protocols include UART, I2C, SPI, I2S, and so on. AN14322 USB to multi VCOM on MCX C444 Series MCU: This document describes how to implement a USB to functions of multiple VCOMs on MCX C444 series FRDM boards. AN14349 Emulating I2C Bus Controller by using FlexIO on MCX C: This application note lists the steps to use the FlexIO module for emulating the I2C bus controller Power Management:  AN14811 Estimated Power-on Hours for the MCX C04x, MCX C14x, MCX C24x and MCX C44x: This document describes the estimated product power-on hours (PoH) for the MCX C04x, MCX C14x, MCX C24x, and MCX C44x industrial MCUs. It uses the criteria from the qualification process. AN14332 MCX C444 Power Mode Switch Application: This application note focuses on the power management controller (PMC), system mode controller (SMC), Multipurpose Clock Generator Lite (MCG-Lite), and Low-Leakage Wakeup Unit (LLWU). Training: Design without Bounds FRDM Training and Resources FRDM Training Hub MCX C15/C16 Product Training Useful Links: FRDM Boards Enclosures (3D Print) MCX C:  How to Enter the ROM Bootloader to Update the firmware MCUXPresso for Visual Studio Code - MCX MCUXpresso Config Tool for MCUXpresso IDE MCUXpresso Config Tool for 3rd party IDE Download Firmware to MCX microcontrollers over USB, I2Cm UART, SPI, CAN Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here    MCXC
View full article
i.MXRT1052和FPGA通讯用SRAM AADM模式,有些信号没有输出 i.MXRT1052和FPGA通讯用SRAM AADM模式,有些信号没有输出。 我现在用的AADM模式。但是在实际配置的时候没有看到WE#,OE#。还是配置的SEMC_ADDR11/SEMC_ADDR12。现在这两个信号在FPGA端没有变化。但是数据和地址是有变化的,ADV#也是有变化的。SEMC_CS0没有变化。 这是为什么?我看到手册上的SEMC Pin Mux。SEMC_ADDR11是WE#,SEMC_ADDR12是OE#,但是在MCUXpresso Config Tools 26.06里面配置的时候没有OE#和WE#。 还是其他什么原因导致没有信号。 Re: i.MXRT1052和FPGA通讯用SRAM AADM模式,有些信号没有输出 Hi @SDFDSFSF ,    请注意,不要用SEMC_CS0做FPGA SRAM的片选。SEMC_CS0是SDRAM CS0, SRAM应该使用SEMC_CSX[3:0], 并在SEMC->IOCR里把对应的MUX_CSXx配置成SRAM CE#。      另外,确认外设初始化后,寄存器SRAMCR0.AM= 01 (AADM)。当SRAM工作在AADM模式下,SEMC会自动将SEMC_ADDR11定义为WE#,SEMC_ADDR12定义为OE#。 Best Regards, Shelly
View full article
Himiway: Mid-Drive vs Hub Motor: Pros and Cons If you're shopping for an electric bike, one of the biggest decisions is choosing between a mid-drive motor and a hub motor. Neither design is automatically better. Mid-drive motors are especially good at using the bike's gears to handle steep hills and technical terrain, while hub motors are simpler, usually more affordable, and require less drivetrain maintenance. For many everyday riders, a good hub motor provides more than enough performance. Riders dealing with serious hills, mountain trails, or demanding cargo use may benefit more from a mid-drive system. Here's a practical comparison. Mid-Drive vs Hub Motor at a Glance Feature Mid-Drive Motor Hub Motor Motor Location Around the crank/pedals Front or rear wheel hub Best For Hills, trails, technical riding Commuting, leisure, mixed everyday riding Hill Performance Excellent Good to excellent depending on torque Weight Distribution Very balanced More weight at one wheel Drivetrain Wear Higher Lower Maintenance More involved Generally simpler Flat Tire Repair Usually easier Motor-wheel removal can be harder Pedaling Feel Often very natural Depends heavily on sensor tuning Price Usually higher Usually more affordable What Is a Mid-Drive Motor? A mid-drive motor is positioned near the bottom bracket, where the pedals and crankset meet the frame. Instead of directly turning a wheel, the motor sends power through the bicycle's drivetrain. That means the motor can take advantage of the bike's gears in much the same way the rider does. Shift into a lower gear for a steep climb, for example, and the motor can operate at a more favorable speed while producing strong climbing assistance. This is the biggest reason mid-drive systems are popular on performance-oriented electric mountain bikes and other bikes designed for demanding terrain. Pros of Mid-Drive Motors 1. Excellent Hill-Climbing Performance This is probably the strongest argument for a mid-drive. Because motor power passes through the bicycle's gears, you can select a lower gear when climbing. This helps the motor operate efficiently instead of forcing it to pull the bike uphill at very low motor RPM. For riders living in extremely hilly areas, this can make a noticeable difference. However, don't assume that every mid-drive automatically climbs better than every hub motor. Motor torque, controller tuning, rider weight, gearing, tire size, and total bike weight all matter. A strong 750W geared hub motor with high torque can still be an excellent hill climber for normal roads and moderate trails. 2. Better Weight Distribution A mid-drive motor places its weight low and near the center of the bicycle. That generally gives the bike more neutral handling because there isn't a large motor concentrated inside the front or rear wheel. The advantage becomes especially noticeable during technical mountain biking, quick direction changes, and riding over uneven terrain. 3. Efficient Use of Motor Power Because the motor can use the bicycle's gears, a mid-drive system can keep the motor operating in a more efficient RPM range. This can improve efficiency on routes involving frequent elevation changes. It doesn't necessarily mean a mid-drive will always have longer range, though. Battery capacity, speed, tire pressure, rider weight, temperature, elevation, wind, and assist level can easily have a larger effect on real-world range. 4. Natural Pedaling Experience Many higher-end mid-drive systems are paired with torque sensors. A torque sensor measures how hard you're pushing on the pedals and adjusts motor assistance accordingly. Push harder and you receive more assistance. Pedal gently and the motor responds more gently. The result can feel surprisingly similar to riding a normal bicycle—except that you suddenly have much stronger legs. Cons of Mid-Drive Motors 1. More Drivetrain Wear The same feature that gives a mid-drive its climbing advantage also creates one of its biggest disadvantages. Both the rider and motor are sending power through components such as the: Chain Chainring Cassette Derailleur system High motor torque combined with poor shifting habits can accelerate drivetrain wear. If you regularly shift gears while the motor is delivering maximum power, chains and cassette teeth may wear substantially faster. 2. More Expensive Mid-drive systems generally cost more. The motor must be integrated around the crank area, and the frame often needs to be designed specifically around that drive unit. For riders who mainly travel on pavement or relatively gentle terrain, paying the premium may not provide enough practical benefit. 3. Shifting Technique Matters Mid-drive riders need to think more carefully about gears. Starting a steep hill in a very high gear and then shifting under heavy motor load isn't ideal. Good riding technique involves selecting an appropriate gear before the drivetrain becomes heavily loaded. For experienced cyclists, this quickly becomes natural. For beginners, there can be a learning curve. 4. A Broken Chain Can Become a Bigger Problem Because a mid-drive transfers motor power through the chain, drivetrain failure can potentially leave you unable to use the motor to drive the rear wheel. A throttle-equipped hub-drive bike can have an advantage here because its motor operates independently from the bicycle chain. What Is a Hub Motor? A hub motor is built directly into the center of the front or rear wheel. Rear hub motors are particularly common on modern electric bikes. Instead of sending power through the chain and cassette, the motor directly rotates the wheel. This makes the system mechanically straightforward and separates motor power from the traditional bicycle drivetrain. Several Himiway models use powerful hub-drive configurations. Bikes such as the Himiway D5 2.0 Series demonstrate why hub motors remain popular on practical fat-tire e-bikes: they can combine substantial torque with relatively straightforward operation. Pros of Hub Motors 1. Simple and Low-Maintenance Design One of the biggest advantages is simplicity. The motor doesn't normally send its power through the bicycle chain or cassette. Your drivetrain therefore only has to handle your pedaling force rather than your pedaling force plus motor output. For riders who want an e-bike for commuting, weekend rides, errands, or recreation, this simplicity is valuable. 2. Strong Everyday Performance It's outdated to think that hub motors are only suitable for flat roads. Modern geared hub motors can produce substantial torque. For example, the Himiway D5 2.0 uses a 750W geared hub motor rated at 90 Nm of torque. That's the kind of specification designed to provide strong acceleration and useful climbing assistance rather than simply cruising along perfectly flat bike paths. The D5 2.0 20" combines the same general idea with 20-inch fat tires and full suspension, giving riders a compact platform designed around comfort and maneuverability. For normal hills, neighborhood streets, gravel roads, and recreational trails, a well-designed hub motor can be more than capable. 3. Lower Purchase Cost Hub motors are generally less complicated and less expensive for manufacturers to integrate into an e-bike. That can allow more of the bike's budget to go toward other features such as: Larger batteries Hydraulic brakes Better suspension Integrated lighting Fat tires Higher payload capacity This is one reason hub-drive bikes can offer very attractive specifications for the money. 4. Less Stress on the Chain and Cassette Since motor power goes directly to the wheel, the chain doesn't have to transmit the motor's full torque. That can mean longer drivetrain component life compared with a powerful mid-drive bike, assuming both bikes are maintained properly. 5. Throttle Operation Can Be Useful On compatible hub-drive e-bikes equipped with a throttle, motor operation doesn't necessarily depend on the bicycle drivetrain. This can be convenient when starting from a stop, briefly moving through an intersection, or getting the bike moving when carrying a load. It also provides an important mechanical advantage: a broken chain doesn't necessarily prevent the motor from moving the bicycle. Cons of Hub Motors 1. Less Efficient on Extreme Climbs A conventional hub motor can't take advantage of the bicycle's cassette in the same way a mid-drive can. On a long and very steep climb, the motor may be forced to operate at low speed under heavy load. That can increase heat generation and energy consumption. For occasional hills this might not matter much. For riders climbing steep mountain roads every day, it becomes much more important. 2. Heavier Rear or Front Wheel The motor adds substantial mass to whichever wheel contains it. Most powerful e-bikes use rear hub motors, so the rear of the bicycle can feel heavier when lifting or servicing it. You may notice this more when carrying the bike upstairs than when actually riding it. 3. Flat Tire Repairs Can Be More Complicated A hub-motor wheel isn't quite as easy to remove as an ordinary bicycle wheel. You may need to disconnect the motor cable and deal with a significantly heavier wheel. For that reason, maintaining correct tire pressure and using puncture-resistant tires can be particularly worthwhile on hub-drive e-bikes. What About Himiway eBikes? Himiway ebikes is a useful example because many of its bikes emphasize powerful hub-drive systems rather than automatically using a mid-drive simply because it sounds more premium. Models such as the Himiway D5, D5 Pro, D5 2.0, D5 2.0 ST, D5 2.0 Camo, D5 2.0 20", C3, A7, A7 Pro, D7, and D7 Pro target different types of riding, so the important point is to look at the complete bike rather than judging it solely by motor location. For example, a rider considering a D5 2.0 may care about strong torque, fat-tire traction, suspension comfort, range, and everyday reliability more than achieving the lightest possible drivetrain. The D5 2.0 20" is particularly interesting for riders who value easier maneuverability and comfort. Its smaller 20-inch wheels, 4-inch tires, full suspension, and low center of gravity create a very different riding experience from a traditional large-wheel mountain e-bike. The A7 and A7 Pro, meanwhile, are more relevant to riders prioritizing urban transportation and everyday usability. And the C1 Kids belongs in a completely different category. For younger riders, controllability, appropriate sizing, speed management, braking, and adult supervision are far more important than chasing maximum motor torque. This highlights an important lesson: Don't choose an e-bike based on the motor alone. What Riders Actually Notice Specifications are useful, but everyday riding tends to make the differences much simpler. A well-tuned hub-drive bike often feels effortless during normal commuting. You pedal, assistance arrives, and you keep moving without constantly thinking about gears. A good mid-drive tends to reward riders who actively use their gears. When approaching a hill, shifting down allows the motor and rider to work together efficiently. On technical terrain, the centered weight can also make the bicycle feel more balanced. The difference becomes much less dramatic when you're cruising at moderate speeds on a flat bike path. That's why paying substantially more for a mid-drive isn't automatically worthwhile for every rider. Which Motor Is Better for Hills? Mid-drive wins for serious climbing. If your normal rides include long, steep mountain climbs, a mid-drive's ability to use the bike's gearing is a major advantage. But there's an important distinction between "hills" and "extreme hills." Most people aren't climbing mountain passes every morning. A high-torque geared hub motor can handle typical neighborhood hills, rolling countryside, gravel roads, and moderate trail climbs very well. That's why bikes such as the Himiway D5 2.0 can make sense for riders who want climbing ability without moving to a more expensive mid-drive platform. Which Is Better for Commuting? For typical commuting, I'd give the advantage to the hub motor. It's simple, relatively inexpensive, puts less motor-related stress on the bicycle drivetrain, and provides plenty of assistance for normal urban riding. If your commute involves extremely steep terrain, however, a mid-drive becomes more attractive. Which Is Better for Mountain Biking? For serious technical mountain biking, I'd choose a mid-drive. The centered motor position improves weight distribution, while access to the bike's gearing helps during steep and technical climbs. For gravel roads, forest paths, dirt roads, camping trips, and relatively moderate recreational trails, a powerful fat-tire hub-drive bike can still be an excellent choice. Which Is Better for Beginners? For many beginners, a hub-drive e-bike makes more sense. There's less need to think about keeping the motor in the correct gear, drivetrain maintenance is straightforward, and prices are often more approachable. However, motor type isn't the only factor affecting ease of use. Frame geometry, wheel size, bike weight, standover height, throttle behavior, torque or cadence sensing, brakes, and suspension can make an even bigger difference to rider confidence. Mid-Drive vs Hub Motor: Final Verdict There isn't a universal winner. Choose a mid-drive motor if you: Regularly climb very steep hills Ride technical mountain trails Want balanced weight distribution Prefer a natural, performance-oriented riding feel Don't mind additional drivetrain maintenance Are comfortable paying more Choose a hub motor if you: Commute or ride recreationally Mostly encounter flat to moderately hilly terrain Want lower maintenance Want better value for your budget Prefer a mechanically simpler system Want motor operation independent of the bicycle drivetrain For many everyday riders, a quality geared hub motor offers the better balance of power, simplicity, reliability, and price. A properly designed 750W, high-torque hub-drive e-bike can handle far more than just flat city streets. Mid-drives become particularly valuable when terrain gets genuinely demanding. So instead of asking, "Which motor is better?", ask: "Where will I actually ride this bike?" If the answer is steep mountain trails and demanding climbs, look closely at mid-drives. If it's commuting, weekend rides, gravel roads, errands, and moderate hills, a good hub-drive e-bike—such as several models in Himiway's lineup—may give you everything you need without paying for complexity you won't use.
View full article
BDM driver cw v6.3 my P&E USB multilink Universal Interface MC908JB8 chip needs a BDM driver to download my code to my MCS08QG8 chip. Otherwise I need a P&E USB multilink Universal board to load my MC9S08QG8 chip. And the board runs about $200. I would prefer to get a BDM driver for my Lenovo USB port. U say the BDM driver is in the CW v6.3 dvelopment software code! I loaded the CW v6.3 code but it will not install, because the "OS is wrong". the orginal OS was for my xp computer, but i am running windows 11 now and the cw v6.3 will not install on that OS. HELPPPPPPPPP!!!!!!!!! Re: BDM driver cw v6.3 你好,   CodeWarrior v6.3 与 Windows 11 不兼容;要在 Windows 11 中使用 CodeWarrior,请更新到 v11.1,这就是您无法在 Windows 11 中安装 CW v6.3 的原因。   能否分享一下您的 P&E USB Multilink 连接在设备管理器 > Jungo Connectivity 中显示的内容? 它在其他地方出现过吗?或者有警告标志吗? 例如,我的 P&E USB 多链路设置如下:   luis_maravilla_1-1786386142957.png 在USB Multilink Universal 和 USB Multilink Universal FX 技术概要 [USBMLUNIVERSALFX]文档的第 6 章“驱动程序安装”中提到,如果需要更新驱动程序,可以从 P&E 页面“支持中心”>“下载”下载驱动程序安装程序的副本。   顺祝商祺! Re: BDM driver cw v6.3 我需要MC9s08qg8芯片的BDM接口。我正在尝试在 Windows 11 系统上使用 BDM USB 驱动程序。我能否创建一个虚拟机来完成这项任务,还是说这条路也行不通?
View full article
MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi Team, I am working with the MIMXRT1040-EVK and using MCUXpresso IDE with LinkServer/SWD. I am facing an issue where my application works correctly when linked and executed from RAM, but when configured to execute from external FlexSPI NOR Flash, the debugger does not reach main(). Current behavior RAM build: "Link application to RAM" enabled Application downloads successfully Application executes correctly Debugger reaches main() I can debug the application normally Flash/XIP build: "Link application to RAM" disabled Application is linked to external Flash starting at 0x60000000 Build completes successfully .axf is generated When I start debugging, the debugger does not reach main() The CPU does not appear to execute from the expected 0x600xxxxx XIP address range Linker/map information The generated .map file shows the expected XIP layout: .boot_hdr 0x60000000 .boot_hdr.conf 0x60000000 .boot_hdr.ivt 0x60001000 .boot_hdr.boot_data 0x60001020 .text 0x60002000 .isr_vector 0x60002000 ResetISR 0x6000231C main 0x60004EF4 So the application appears to contain the expected FlexSPI NOR boot header, IVT, boot data, vector table, ResetISR, and application code. I also have: XIP_EXTERNAL_FLASH = 1 XIP_BOOT_HEADER_ENABLE = 1 Important observation After attempting to debug/program the Flash image, I checked the memory at: 0x60000000 0x60001000 0x60002000 and the memory window shows 0x00000000/empty data rather than the expected application contents. For example, at: 0x60002000 I expected the application vector table, but the memory appears to contain zeros. The CPU registers after the failed debug attempt also showed: PC = 0x0020E368 SP = 0x20200F70 LR = 0x0020ED49 rather than a PC in the expected 0x600xxxxx XIP region. Debug configuration I am using: Debug Connection: SWD Connect script: RT1040_connect.scp The Debug configuration has: Load image: enabled Use project binary: igpio_led_output.axf Load symbols: enabled Use project binary: igpio_led_output.axf Set breakpoint at: main Request hardware breakpoint: enabled The LinkServer Debug configuration is being used. Project contents The project contains the standard XIP-related files: xip/ ├── evkmimxrt1040_flexspi_nor_config.c ├── evkmimxrt1040_flexspi_nor_config.h ├── fsl_flexspi_nor_boot.c └── fsl_flexspi_nor_boot.h The generated linker script also places the boot header and application into the BOARD_FLASH region beginning at 0x60000000. My question Could someone please help me determine why the external FlexSPI NOR Flash is not being programmed with the generated XIP image when launching the LinkServer debug session? Specifically: Does the MIMXRT1040-EVK + LinkServer require a specific FlexSPI NOR Flash driver/configuration for debugging XIP applications? Is RT1040_connect.scp sufficient for both connecting and programming the external NOR Flash? Is there any additional Flash programming configuration required in the MCUXpresso Debug Configuration? Should the Debug configuration use a specific flexspi_nor Flash driver or Flash Tool configuration? Is there a known issue with LinkServer + MIMXRT1040 + external FlexSPI NOR + XIP debugging where the .axf is loaded as symbols but the external Flash is not actually programmed? Is there a recommended NXP example project/configuration that I can compare against for a working MIMXRT1040-EVK FlexSPI NOR XIP debug session? I would appreciate any guidance on what I should check next. Thank you. Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Thank you for the response. I checked the MCU Settings → Memory details as you suggested. I have attached the screenshot. The BOARD_FLASH memory is configured as: Location: 0x60000000 Size: 0x800000 Flash Driver: MIMXRT1040_SFDP_QSPI.cfx So, it appears that the specific external Flash driver is already configured for BOARD_FLASH. I also tried the Serial Download Mode + MCU Provisioning Tool procedure. I was able to successfully Build Image and Write Image using the MCU Provisioning Tool. However, after that, I was still unable to get the application programmed/debugged from Flash through the normal MCUXpresso + LinkServer debug flow. Interestingly, when I tried flashing/debugging the code one more time later, it suddenly worked and the application was successfully running from Flash. I did not intentionally change the project configuration, Flash driver, linker configuration, or boot settings between the failed and successful attempts. So, at this point, I suspect there may be some intermittent issue related to the Flash programming/initialization/reset sequence rather than the application/linker configuration itself. Could you please advise what could cause this behavior on the MIMXRT1040-EVK? In particular: Is MIMXRT1040_SFDP_QSPI.cfx the correct Flash driver for the EVK's external FlexSPI NOR? Is the fact that the Default LinkServer Flash Driver field is blank significant, even though BOARD_FLASH has MIMXRT1040_SFDP_QSPI.cfx assigned in the Driver column? Could the external Flash remain in an unexpected state after a previous failed programming/debug attempt, requiring a specific reset or power cycle? Could RT1040_connect.scp or the LinkServer reset/connection sequence cause intermittent Flash programming behavior? Is there any known issue with the MIMXRT1040-EVK, LinkServer and MIMXRT1040_SFDP_QSPI.cfx where Flash programming may fail intermittently? Since the same configuration eventually worked without any intentional change, I would like to understand what could have caused the previous failure so that we can make the Flash debugging/programming reliable. Thank you. Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi @Prashanth1 , Based on the screenshot you provided, the Flash driver configuration appears to be fine. Could you first try putting the board into serial download mode and using the MCUXpresso Secure Provisioning Tool to download the image to Flash by usb/uart? This method isolates the influence of the debugger and can be used to check whether the board has any flash hardware issues. Additionally, please provide me with the log of the failed download attempt using the debugger. On my end, I’ll arrange for an RT1040-EVK as soon as possible and try to reproduce the issue using the project package you previously attached. Best regards, Gavin Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi Gavin Sir, Thank you for the response. I checked the MCU Settings → Memory details as you suggested. I have attached a screenshot. In my project, the BOARD_FLASH memory is configured as: Location: 0x60000000 Size: 0x800000 Driver: MIMXRT1040_SFDP_QSPI.cfx So, it appears that the FlexSPI NOR Flash driver is already associated with the BOARD_FLASH memory region. However, I noticed that the “Default LinkServer Flash Driver” field at the top of the MCU Settings is blank, while the driver column for BOARD_FLASH shows MIMXRT1040_SFDP_QSPI.cfx. Could you please confirm: Is this configuration correct for the MIMXRT1040-EVK? Should I also select MIMXRT1040_SFDP_QSPI.cfx in the Default LinkServer Flash Driver field? Or is the driver shown in the BOARD_FLASH row sufficient for LinkServer to program the external FlexSPI NOR? My main issue is that the application is correctly linked for XIP at 0x60000000, but after launching the LinkServer debug session, I don't see the application contents at 0x60000000 / 0x60002000 in the Memory window. RAM debugging works correctly with the same application. I have attached the MCU Settings screenshot for reference. Thank you.     Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi @Prashanth1 , Thanks for your interest in NXP MIMXRT series! When using an external Flash, a specific Flash driver is required. Please check whether the Flash driver has been loaded correctly in the IDE: (My screenshot uses the RT1170 as an example; the process is similar for the RT1040.) Best regards, Gavin Re: MIMXRT1040-EVK: Debug works from RAM, but it's not working for FLASH Hi @Prashanth1 , Based on the described phenomenon, the most likely cause is that there was dirty data/image in the Flash memory previously. Whether it is an incorrect FCB header or an image that causes the MCU to enter an error state upon execution, such issues can lead to failure when attempting to re-flash the image. The standard recovery method in this scenario is to enter serial download mode. You may want to consult this article: https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/RT-board-recovery-for-debugger-connect-issues/ta-p/1635260 Regarding the selection of the flash loader, you simply need to select the appropriate flash driver in the "Flash" row within the IDE. The *.scp file is provided with the SDK and is used for pre-configuring the link server; You can go into the file to learn more about each line of command. Best regards, Gavin
View full article