Jlink fails to debug imx93 When using JLink to debug the M33 core of i.MX93, after setting breakpoints, it seems only the PC pointer is halted, while various internal counters continue counting, preventing normal debugging. What are the solutions for this issue?Thank you for ansering! Re: Jlink fails to debug imx93 Yes, and I tried on single M33 core, the system counter can't be halted as before. I can't find the reason. Best Regards. Re: Jlink fails to debug imx93 Hi @leoX  My test is based on single M33 and Jlink, did you boot M33 with remoteproc? Best Regards, Zhiming Re: Jlink fails to debug imx93 Thank you for your response! I am reading tstmr in a task to calculate the task's execution cycle, but if I add a breakpoint, the calculated cycle increases, indicating that the system counter continues to count when I add a breakpoint. Also, I am starting the M core through the A core. Does setting the download mode for M33 help? Best Regards Re: Jlink fails to debug imx93 Hi, Can you share the screenshot of  various internal counters?  Did you set the m33 download mode? Best Regards, Zhiming

Required Boot animation shows in multiple display Hi all,   Currently, we are working on the NXP MX8MP platform with Android 14 OS "enabling the Multiple-Display" feature, where we are using one DSI MIPI display, which is the primary display, and another one is an LVDS display. We have successfully implemented the Multiple-Display function, but at the time of booting, the Android boot animation is coming only on the DSI MIPI display, and this Android boot animation is not coming on the LVDS display. Here I need to get the Android boot animation in both displays. How can I get the solution for this? Graphics & Display i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Multimedia Re: Required Boot animation shows in multiple display Hello @Bio_TICFSL  Kindly provide a solution for this issue at your earliest convenience. We have been awaiting your response for quite some time. Best regards, Manoj kumar Re: Required Boot animation shows in multiple display Hi @Bio_TICFSL  Can you please help us to solve this problem? Re: Required Boot animation shows in multiple display Hi @Bio_TICFSL  Thanks for your support but the issue is different. We are working on "enabling the Multiple-Display" and we have implemented this feature successfully. The problem here is that we are getting Android boot animation in main display (DSI MIPI) but in LVDS display Android boot animation is not coming and directly home screen is appearing after booting completion.  Here I need to get the Android boot animation in both displays. How can I get the solution for this? Re: Required Boot animation shows in multiple display Hello, To have a boot image display on both monitors for an Android MX8 system, you'll need to configure both the U-Boot bootloader and the Linux kernel to support dual displays. This involves modifying device tree files (DTB/DTBO) and potentially adjusting boot arguments in U-Boot. Additionally, ensuring the kernel is compiled with the correct display drivers and configurations for both monitors is crucial.  1. U-Boot Configuration: Device Tree: The device tree (DTB or DTBO) needs to be updated to reflect the presence of both displays. This includes enabling the appropriate display controllers (e.g., LVDS, HDMI, MIPI-DSI) and configuring their settings for each display.      Boot Arguments: In U-Boot, you might need to modify the bootargs to specify the correct display configuration and potentially load the correct DTB/DTBO file for the dual display setup.        2. Kernel Configuration: Device Tree: The kernel's device tree (often found under arch/arm64/boot/dts/ ) should also be updated to reflect the dual display setup, similar to the U-Boot changes.      Display Selection: The kernel needs to know which display controller to use for each display, and this is often done through the device tree.        3. Android-Specific Steps: Boot Image: The Android boot image (boot.img) needs to be rebuilt after making the necessary changes to the kernel and device tree. This image contains the kernel, ramdisk, and potentially other binaries.      Display Initialization: The Android system will need to initialize both displays during boot, which might involve specific calls to the display drivers and configuration settings.        4. Testing: Initial Boot: After flashing the new boot image, start the system and observe the boot process. You should see the boot logo and any other boot messages on both displays.      Display Functionality: Verify that both displays are working correctly after the system boots into Android, and that you can interact with the system on both.      Regards          

MCX-Nx4x EEPROM type memory Looking for something similar to the EEPROM memory block on the LPC546xx parts. The MCX parts seem to have a flash ROMAPI but its really poorly documented and lacks clear examples. CFPA vs. CMPA? Incrementing fields? Lots of pre-assigned locations? Unclear block size restrictions? Factory vs. infield vs keystore? Plus its in ROM so its not even possible to follow the code. Reminds me of the LPC546xx USB functions which were likewise difficult to understand due to the poor documentation. Oh and I have read AN14259 which helps a little but not enough. All I want is a persistent but not OTP memory area that I can store application specific constants in. I'm probably missing something so please point me in the right direction. Thanks in advance for any help! Boot ROM|Booting | Flash Core and Memory Re: MCX-Nx4x EEPROM type memory Hi Pablo, Thank you for your continued support with this. I think I have finally achieved a solution to this and I can now place my data into the free area in the CMPA page. It all hinges on understanding the MBC and unfortunately the reference manual is not very clear about how it is used. However the Security Reference Manual chapter 21 is more helpful and once I configuring the MBC the ROM flash APIs started working as I expected. I really think some better examples in this area would have saved me a lot of time. The flash hiding one is probably the nearest to what is required but without a good explaination of what it is actually going on is just too unclear to be useful. Best wishes and thank you once again for your help, Andy Re: MCX-Nx4x EEPROM type memory Hi @andyjackson, To program and read the CMPA region, you can use the FLASH APIs. Typically, the function used to write CMPA data is ffr_cust_factory_page_write. You can find more information about this function in section 13.2.2.10 of the reference manual. Additionally, the following community post may be helpful for understanding how to use the FLASH API to update the CMPA flash region. MCXN5 CMPA Write Fails - NXP Community Best Regards, Pablo Re: MCX-Nx4x EEPROM type memory Hello again Pablo, Thanks for your last reply. I've been digging into this further and according to the MCXNx4x_IFR.xlsx spreadsheet in the Reference Manual 0x01004200 to 0x01005FFF of the CMPA is customer defined which seems perfect. However, I have yet to find a way of accessing this area. FFR_GetCustomerData() will let me read up to byte 0x1FF of the CMPA 8Kbyte page and the standard flash functions FLASH_Read/Program/Erase etc only seem to work within the main program flash. How can I access the rest of the CMPA page? I've seen examples where the first 512 bytes of the CMPA page can be updated but nothing that accesses the rest of the page. Any ideas? Best wishes, Andy Re: MCX-Nx4x EEPROM type memory Hi @andyjackson I understand that Reference Manuals may be overwhelming. The following community post may be helpful for more information on the ROM API. Re: Using MCX N ROM API for Internal Flash Erase/Programming - NXP Community Also, example mcxromapi_flash_hiding_cm33_core0 may be helpful since it show how MBC provides read, write, and execute access control per block to internal flash memory. Best Regards, Pablo Re: MCX-Nx4x EEPROM type memory Hi Pablo, Thank you for your reply. I want to be able to read and save persistent application data at runtime so the Secure Provisioning Tool is not an option. The main flash banks might be reflashed during firmware updates so using that doesn't seem to be an option either. Also, a reboot after updating is likewise not possible as this would disrupt execution so this seems to rule out the CFPA which leaves the CMPA. Looking at AN14259 almost all locations in the CFPA and CMPA appear to have predefined usage so I'm not sure where I can safely write to anyway. I tried playing with FFR_GetCustKeystoreData/FFR_CustKeystoreWrite and FFR_GetCustomerData/FFR_CustFactoryPageWrite and whilst reads appeared to work, writes seemed to always generate hard faults. Plus I'm guessing at how to use them properly as I'm not aware of an code example for them. I can't help feeling that I'm missing something as a small user EEPROM like area seems essential for most microcontroller applications. Unfortunately with a nearly 4000 page reference manual its hard to digest all the information. Best wishes, Andy Re: MCX-Nx4x EEPROM type memory Hi @andyjackson, The MCXN features a Protected Flash Region (PFR), which includes two configurable pages: CFPA (Customer In-field Programmable Area) and CMPA (Customer Manufacturing/Factory Programmable Area). Both of these areas can be written to multiple times. As you mentioned, Application Note AN14259 provides examples of how to modify the CFPA bit fields using the ROM APIs. You can also use the MCUXpresso Secure Provisioning Tool for this purpose. The tool’s User Guide includes Section 5.2.8: OTP/PFR/IFR/BCA/FCF Configuration, which explains how to use the GUI to modify the CFPA bit fields. The GUI also provides detailed descriptions of each field. Additionally, Application Note AN14178 may be helpful, as it demonstrates how to perform flash read and write operations using the Flash Command Controller instead of the ROM API. Also, there is an example on the MCXN947 SDK called mcxromapi_flash_hiding_cm33_core0 that you may be interest in, this example demonstrates a program showing flash hiding. Best Regards, Pablo Re: MCX-Nx4x EEPROM type memory Hello, Unfortunately I can't release the code but the key parts are: 1. Read and understand the Security Reference Manual chapter 21 on the functioning of the MBC 2. You will need something like this in your initialisation code (running on CPU0): // For RW access to the CMPA page the MBC needs to be configured // See chap 21 of the MCX Nx4x Security Reference Manual TRDC->MBC_INDEX[0].MBC_MEMN_GLBAC[5] = 0x7700; TRDC->MBC_INDEX[0].MBC_DOM0_MEM1_BLK_CFG_W[0] |= 0x500; after which the FLASH_xxxxx functions should have RW access to the CMP block. See the NXP examples for using these functions. Hope that helps, Andy Re: MCX-Nx4x EEPROM type memory @andyjackson could you please provide a code sample or any further detail on how you got this working? I am also trying to store data in the customer defined region of CFPA but have had no luck so far. Re: MCX-Nx4x EEPROM type memory Thanks Andy, After reviewing your comment and the reference manual again I was still having issues with the CFPA however, I now have a small example working with the CMPA which will be a good starting point. I've attached a small example snippet in case its helpful for someone stumbling across this in the future. Thanks for your help Re: MCX-Nx4x EEPROM type memory Hi, A nice little example! Only thing I would add is that if you want to preserve the NXP defined data in the first 512 bytes of the block, I think you will need to copy it prior to erasing and rewrite it after. As a final comment for NXP - this really should be one of the SDK examples as I suspect a lot of people want a mechanism to store dynamic application specific data. Its a shame that there isn't a dedicated user flash area with no NXP defined data requirements. Andy

Api Reference/JavaDoc for TapLinx Android SDK Where can I find api reference/JavaDoc for TapLinx Android SDK? Getting Started Re: Api Reference/JavaDoc for TapLinx Android SDK Dear why_sto, JavaDocs are available on below link, under "Downloads" (hint: press "Show all" button): https://www.nxp.com/design/design-center/software/rfid-developer-resources/taplinx-software-development-kit-sdk:TAPLINX Best regards, TapLinx team Re: Api Reference/JavaDoc for TapLinx Android SDK Hello, I can't seem to find the mentioned JavaDoc, it seems only release notes and the getting started guides are available.

After rt1052 turns on HAB, using nxp mcu bootutility serial boot cannot connect flashloader Looking at the console messages, it feels like the flashloader has signed successfully and downloaded and jumped to the chip, I don't know why it won't connect. I'm using a combination of core and backplane boards, and switching to a core board that doesn't have HAB turned on, it downloads fine, which means there's nothing wrong with the flashloader itself. Opening the automatically generated bd file signed for the flashloader, I don't see any problems, so I'm looking for help. The console information is as follows: executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- error-status toolStatus: 0 commandOutput: { "command" : "error-status", "response" : [ 4042322160 ], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1075790864 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1075790880 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1074757636 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1074757660 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1074757660 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\elftosb4\win>"D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\elftosb4\win\elftosb.exe" -f imx -V -c "D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\gen\bd_file\imx_flashloader_gen.bd" -o "D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\gen\bootable_image\ivt_flashloader_signed.bin" "D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\src\targets\MIMXRT1052\flashloader.srec" CSF Processed successfully and signed data available in csf.bin Section: 0x14 Section: 0x15 Section: 0x16 Section: 0x18 Section: 0x19 Section: 0x1a Section: 0x1f Section: 0x21 iMX bootable image generated successfully Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- write-file 539001344 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\gen\bootable_image\ivt_flashloader_signed.bin toolStatus: 0 commandOutput: { "command" : "write-file", "response" : [ 3351091 ], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } The automatically generated bd file is as follows options { flags = 0x08; startAddress = 0x20208200; ivtOffset = 0x0; initialLoadSize = 0x200; entryPointAddress = 0x2021b26d; } sources { elfFile = extern(0); } constants { SEC_CSF_HEADER = 20; SEC_CSF_INSTALL_SRK = 21; SEC_CSF_INSTALL_CSFK = 22; SEC_CSF_INSTALL_NOCAK = 23; SEC_CSF_AUTHENTICATE_CSF = 24; SEC_CSF_INSTALL_KEY = 25; SEC_CSF_AUTHENTICATE_DATA = 26; SEC_CSF_INSTALL_SECRET_KEY = 27; SEC_CSF_DECRYPT_DATA = 28; SEC_NOP = 29; SEC_SET_MID = 30; SEC_SET_ENGINE = 31; SEC_INIT = 32; SEC_UNLOCK = 33; } section (SEC_CSF_HEADER; Header_Version="4.2", Header_HashAlgorithm="sha256", Header_Engine="DCP", Header_EngineConfiguration=0, Header_CertificateFormat="x509", Header_SignatureFormat="CMS" ) { } section (SEC_CSF_INSTALL_SRK; InstallSRK_Table="../../../gen/hab_cert/SRK_1_2_3_4_table.bin", InstallSRK_SourceIndex=0 ) { } section (SEC_CSF_INSTALL_CSFK; InstallCSFK_File="../../cst/crts/CSF1_1_sha256_2048_65537_v3_usr_crt.pem", InstallCSFK_CertificateFormat="x509" ) { } section (SEC_CSF_AUTHENTICATE_CSF) { } section (SEC_CSF_INSTALL_KEY; InstallKey_File="../../cst/crts/IMG1_1_sha256_2048_65537_v3_usr_crt.pem", InstallKey_VerificationIndex=0, InstallKey_TargetIndex=2) { } section (SEC_CSF_AUTHENTICATE_DATA; AuthenticateData_VerificationIndex=2, AuthenticateData_Engine="DCP", AuthenticateData_EngineConfiguration=0) { } section (SEC_SET_ENGINE; SetEngine_HashAlgorithm = "sha256", SetEngine_Engine = "DCP", SetEngine_EngineConfiguration = "0") { } section (SEC_UNLOCK; Unlock_Engine = "SNVS", Unlock_features = "ZMK WRITE" ) { } A screenshot of the nxp-mcu bootutility error report is shown below: But in reality, the keys are configured with BMOD[1:0]=2'b01 (serial downloader) More often than not, the boot mode is recognized as BMOD[1:0]=2'b00 (boot from fuse) Rarely will it be BMOD[1:0]=2'b10 (internal boot) And then the recognized UUIDs look out of whack as well Very strange, never recognizes the boot mode as BMOD[1:0]=2'b01 (serial downloader) ps: switching to a core board with no HAB configured recognizes it properly every time as BMOD[1:0]=2'b01 (serial downloader) i.MXRT 105x Re: rt1052开启HAB后，使用nxp mcu bootutility串口启动无法连接flashloader Now, can you only replace the master chip? Re: rt1052开启HAB后，使用nxp mcu bootutility串口启动无法连接flashloader I have the same problem, can you help me out? I would like to mail the development board to you. 回复： rt1052开启HAB后，使用nxp mcu bootutility串口启动无法连接flashloader Now, this development board doesn't work. I'll mail it to you to help me adjust it. Is it okay? I'm in Shanghai. 回复： rt1052开启HAB后，使用nxp mcu bootutility串口启动无法连接flashloader NXP Technical Support: Hello! I am experiencing the same problem. Now, downloading the program with KEIL is OK, but, it won't run. The development board model number is: MIMXRT1064-EVK. the console information is as follows: Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- error- status toolStatus: 0 commandOutput: { " command ": "error-status ", " response ": [ 4042322160 ], " status ": { " description ": " 305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- read-register 1075790864 32 4 D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command ": "read-register ", " response ": [], " status ": { " description ": "305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- read-register 1075790880 32 4 D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command ": "read-register ", " response ": [], " status ": { " description ": "305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- read-register 1074757636 32 4 D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command ": "read-register ", " response ": [], " status ": { " description ": "305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- read-register 1074757660 32 4 D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command ": "read-register ", " response ": [], " status ": { " description ": "305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- read-register 1074757660 32 4 D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command ": "read-register ", " response ": [], " status ": { " description ": "305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\elftosb4\win >" D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\ elftosb4\win\elftosb.exe " -f imx -V -c "D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\gen\bd_file\imx_flashloader_gen.bd " -o "D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\gen\bootable_image\ivt_flashloader_signed.bin " "D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\src\targets\MIMXRT1064\flashloader.srec " CSF Processed successfully and signed data available in csf.bin Section: 0x14 Section: 0x15 Section: 0x16 Section: 0x18 Section: 0x19 Section: 0x1a Section: 0x1f Section: 0x21 iMX bootable image generated successfully Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- write-file 539001344 D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\gen\bootable_image\ivt_flashloader_signed.bin toolStatus: 0 commandOutput: { "command ": "write-file ", " response ": [ 2290649224 ], " status ": { " description ": "305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\sdphost\win\sdphost -t 50000 -p COM8,115200 -j -- jump-address 539001344 toolStatus: 0 commandOutput: { " command ": "jump-address ", " response ": [], " status ": { " description ": " 305411090 (0x12343412) HAB enabled. ", "value ": 305411090 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\blhost2_3\win\blhost -t 50000 -p COM8,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { " command ": "ping ", " response ": [], " status ": { " description ": "10501 (0x2905) Invalid packet type. ", "value ": 10501 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\blhost2_3\win\blhost -t 50000 -p COM8,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { " command ": "ping ", " response ": [], " status ": { " description ": "10501 (0x2905) Invalid packet type. ", "value ": 10501 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\blhost2_3\win\blhost -t 50000 -p COM8,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { " command ": "ping ", " response ": [], " status ": { " description ": "10501 (0x2905) Invalid packet type. ", "value ": 10501 } } Executing: D:\TP161PCB\MCUBootUtility\NXP-MCUBootUtility-3.5.0\tools\blhost2_3\win\blhost -t 50000 -p COM8,115200 -j -- get-property 1 0 Re: rt1052开启HAB后，使用nxp mcu bootutility串口启动无法连接flashloader Can you help me see what it is again? Re: rt1052开启HAB后，使用nxp mcu bootutility串口启动无法连接flashloader The full screenshot of the console and its contents are below: xecuting: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- error-status toolStatus: 0 commandOutput: { "command" : "error-status", "response" : [ 4042322160 ], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1075790864 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1075790880 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1074757636 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1074757660 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- read-register 1074757660 32 4 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\vectors\readReg.dat toolStatus: 0 commandOutput: { "command" : "read-register", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\elftosb4\win>"D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\elftosb4\win\elftosb.exe" -f imx -V -c "D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\gen\bd_file\imx_flashloader_gen.bd" -o "D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\gen\bootable_image\ivt_flashloader_signed.bin" "D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\src\targets\MIMXRT1052\flashloader.srec" CSF Processed successfully and signed data available in csf.bin Section: 0x14 Section: 0x15 Section: 0x16 Section: 0x18 Section: 0x19 Section: 0x1a Section: 0x1f Section: 0x21 iMX bootable image generated successfully Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- write-file 539001344 D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\gen\bootable_image\ivt_flashloader_signed.bin toolStatus: 0 commandOutput: { "command" : "write-file", "response" : [ 2290649224 ], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\sdphost\win\sdphost -t 50000 -p COM22,115200 -j -- jump-address 539001344 toolStatus: 0 commandOutput: { "command" : "jump-address", "response" : [], "status" : { "description" : "305411090 (0x12343412) HAB enabled.", "value" : 305411090 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\blhost2_3\win\blhost -t 50000 -p COM22,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { "command" : "ping", "response" : [], "status" : { "description" : "10501 (0x2905) Invalid packet type.", "value" : 10501 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\blhost2_3\win\blhost -t 50000 -p COM22,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { "command" : "ping", "response" : [], "status" : { "description" : "10501 (0x2905) Invalid packet type.", "value" : 10501 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\blhost2_3\win\blhost -t 50000 -p COM22,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { "command" : "ping", "response" : [], "status" : { "description" : "10501 (0x2905) Invalid packet type.", "value" : 10501 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\blhost2_3\win\blhost -t 50000 -p COM22,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { "command" : "ping", "response" : [], "status" : { "description" : "10501 (0x2905) Invalid packet type.", "value" : 10501 } } Executing: D:\AEMBED\rt1052\soft\NXP-MCUBootUtility-master\tools\blhost2_3\win\blhost -t 50000 -p COM22,115200 -j -- get-property 1 0 toolStatus: 1 commandOutput: { "command" : "ping", "response" : [], "status" : { "description" : "10501 (0x2905) Invalid packet type.", "value" : 10501 } } Re: rt1052开启HAB后，使用nxp mcu bootutility串口启动无法连接flashloader 控制台命令截图不太完整，write-file 后面没有命令了吗？

新製品 SPC5675KFK0MMS2R と代替製品 SPC5675KFF0VMS2R のパラメータの違いを教えてください。 旧製品SPC5675KFF0VMS2Rは販売終了となりました。代替製品SPC5675KFK0MMS2R（公式サイトに掲載）と旧製品の違いについて教えていただけますか？よろしくお願いいたします。 Re: 求新产品SPC5675KFK0MMS2R与替代原产品SPC5675KFF0VMS2R的参数区别 こんにちは、 古いSPC5675KFF0VMS2Rは製造中止になりました。公式サイトに記載されている交換モデル SPC5675KFK0MMS2R と元のモデルの違いについて詳しく説明していただければ幸いです。ありがとう。 新しい SPC5675KFK0MMS2R とオリジナルの SPC5675KFF0VMS2R のパラメータの違いを知りたいです。 違いは次のとおりです。 K0 vs F0 - 工場は異なるが同じデバイスカット（リビジョン） M vs V - 異なる温度範囲 これらの情報はデータシート rev 9 に記載されています。 よろしくお願いいたします。 ピーター

S32 Debug Probe Support for S32K3 Hi team, The "S32 Debugger for S32 Platform" mentions that S32K3 also supports the S32 Debug Probe. But when I check the "S32DS Extensions and Updates" in the S32DS IDE 3.5, I found that the S32Z2/E2/G/R development package all support the S32 Debug Probe, but for S32K3 development package, it seems not supporting this feature. Could you please check whether S32K3xx can support the S32 Debugger? If supported, please share the environment (S32DE IDE version and corresponding development package download link) for integrating this feature. Best Regards, Zheng Lin Priority: MEDIUM S32DS Re: S32 Debug Probe Support for S32K3 Hi Alexandra, Got it, thanks for your update. Best Regards, Zheng Lin Re: S32 Debug Probe Support for S32K3 Hi @ZhengLin , The S32 Debugger support for S32K3 devices is available with S32DS3.6. In S32DS3.5 such support does not exist. Please install S32DS3.6.3, the most recent release; is a new installer that will have default also the S32K3 dev packages (actually all the public NPIs will be default installed with the S32DS3.6.x installer). Regards, Alexandra

将 imx93 的 MIPI_CSI& LVDS 线路配置为 GPIO 引脚 您好， 我们能否将 imx93 的 MIPI_CSI& LVDS 线路配置为 GPIO 引脚？ Re: configure MIPI_CSI & LVDS lines of imx93 as GPIO pins 您可以参考 imx93 数据表，mipi csi 和 lvds 焊盘没有复用功能，因此不能用作 gpio 引脚。

Dual-Purpose Pin Usage on MIMXRT1024 for UART and Boot We are currently working with the i.MX RT1024 processor and plan to repurpose the BOOT_CFG[4] and BOOT_CFG[5] pins (corresponding to GPIO_EMC_22 and GPIO_EMC_23) for UART RX and TX functionality, in addition to their role in boot configuration.  To facilitate this dual-purpose usage, we have implemented a 6.2 ms delay circuit using the TPS3840DL30DBVRQ1 voltage supervisor and the SN74LVC1G125DCKR buffer. This setup is intended to control the enabling/disabling of the UART interface, ensuring that the boot configuration is correctly latched during power-up before the pins are repurposed for UART communication. Given our requirement to use these pins for both boot configuration and UART, we would like to confirm whether this implementation is robust and reliable. Are there any recommended modifications or considerations to improve the design or ensure consistent behavior? Re: Dual-Purpose Pin Usage on MIMXRT1024 for UART and Boot Hi @Ash7, This delay circuit of 6.2ms should provide enough time for the RT1024 to finish its booting process while probing the BOOT_CFG pins without any interference of the UART. Remember you could also spare this circuit by configuring the BOOT_CFG fuses instead of relying on the BOOT_CFG pins. But this is only recommended for production, and if the BOOT_CFG pins are meant to remain with the same values. BR, Edwin.

I2c in s32k2358 Hello nxp community, I'm using s332k358 controller and trying to communicate to slave on I2c bus , i used MCAL I2c driver LPI2C . I'm unable to communnicate with the slave devices, i tried to check the signals in oscilloscope , i didnt observe I2C SCLK , function returned error. Is there any example project for I2C sync transmit and async transmit using MCAL driver Re: I2c in s32k2358 Hi @Shivanand  Please refer to the following thread as an example of LPI2C0 configured as Master and LPI2C1 as Slave, using DMA. Example S32K324 I2C Transmit & Receive Using DMA DS3.5 RTD300 It is not specifically designed for your device, but the functionality is similar and may serve as a useful reference. Re: I2c in s32k2358 Hi @VaneB  The Example projects  i found in RTD's are flexio I2c as master and I2c as slave . Is there any projects which involves I2c as master ? Re: I2c in s32k2358 Hi @Shivanand  Yes, example codes for I2C are included with the RTDs. You can find them under the following names: I2c_Example_S32K358 – for MCAL drivers I2c_Ip_Example_S32K358 – for IP drivers Additionally, I recommend reviewing the S32K3_S32M27x I2C Driver Integration Manual and the User Manual included with the RTDs. These documents provide detailed information about the driver, including its limitations, hardware and software requirements, usage instructions, and configuration guidelines.  You can typically find these documents at the following location: C:\NXP\S32DS.3.6.2\S32DS\software\PlatformSDK_S32K3\RTD\I2c_TS_T40D34M60I0R0\doc BR, VaneB

S32K3 向け S32 デバッグ プローブ サポート こんにちは、チームの皆さん 「 S32 プラットフォーム用 S32 デバッガー」には、 S32K3もS32 デバッグ プローブをサポートしていることが記載されています。 しかし、S32DS IDE 3.5 の「S32DS 拡張機能と更新」を確認すると、 S32Z2/E2/G/R開発パッケージはすべてのサポートS32 デバッグ プローブをサポートしていますが、 S32K3開発パッケージではこの機能はサポートされていないようです。 S32K3xx が S32 デバッガをサポートできるかどうか確認していただけますか?サポートされている場合は、この機能を統合するための環境(S32DE IDE バージョンと対応する開発パッケージのダウンロード リンク) を共有してください。 よろしくお願いいたします。 ジェン・LIN 優先度: 中 S32DS Re: S32 Debug Probe Support for S32K3 こんにちは、アレクサンドラさん。 了解しました。更新ありがとうございます。 よろしくお願いいたします。 ジェン・LIN Re: S32 Debug Probe Support for S32K3 こんにちは@ZhengLinさん S32K3 デバイス用の S32 デバッガー サポートは、S32DS3.6 で利用できます。S32DS3.5 ではそのようなサポートは存在しません。最新リリースの S32DS3.6.3 をインストールしてください。これは、S32K3 開発パッケージもデフォルトで含まれる新しいインストーラです (実際には、すべてのパブリック NPI は S32DS3.6.x でデフォルトでインストールされます)。インストーラ）。 よろしくお願いいたします。 アレクサンドラ

Subject: S32K1XX CANFD Tx arbitration start delay Hello   We're developing CAN FD on S32K146 board, I have come confusions about the Tx arbitration start delay  which do need your kind support. 1. Is it mandatory to configure the  TASD bit in FlexCAN CTRL2 registor using non-zero value? 2. If it is mandatory, how to choose the TASD value? I review the Ref manual, but it does confuzed me. I will put my configuration here: a. CAN_CLK is the same with SYS_CLK(80MHZ); b. EPRESDIV = 1; EPROPSEG = 46; EPSEG1 = 15; EPSEG2 = 15; ERJW = 15; (NBT in arbitration phase is 80) c. FPRESDIV = 1;FPROPSEG = 7; FPSEG1 = 7; FPSEG2 = 3; FRJW = 3; (NBT in data phase is 20) according to the formula in ref manual(page 1933), I get the below value: CPCBN = (fSYS/BITRATEN) = 80 * 2 = 160; NMBEND = [(9 * 160) - 4]/2 = 718; That's so big!!! And TASD = 31 - [2 * (12+1) + 4]/160 = 31 that is unreasonable.  So could some one please tell me whether my understanding is right? or how to set the TASD value? Thanks a lot. Re: Subject: S32K1XX CANFD Tx arbitration start delay TDC is Transceiver delay compensation. but anyway, forget my question, I misunderstood the manual Re: Subject: S32K1XX CANFD Tx arbitration start delay Hi@fan1234 No, it depends on the following factors. If set to the maximum, when multiple mailboxes or nodes compete for the bus, setting a larger TASD will artificially reduce the sending priority of the mailbox. • Peripheral-to-oscillator clock ratio • CAN bit timing variables that determine the CAN bit rate • Number of message buffers (MBs) in use by the matching and arbitration processes For TDC question: if S32K1xx has no auto TDC but only fixed TDC I don't understand what you mean about TDC, could you explain it in more detail? Re: Subject: S32K1XX CANFD Tx arbitration start delay Thank you for your reply. so, that means for CANFD frames, even the max TASD will be OK, right? And as you mentioned TDC before, i want to confirm if S32K1xx has no auto TDC but only fixed TDC? Re: Subject: S32K1XX CANFD Tx arbitration start delay Hi@fan1234 I checked and found that this value is not mandatory to be configured as non-zero value, but it is recommended that users configure the register because it is very necessary in some working conditions, such as high bus load, timing constraints I created an Excel spreadsheet for the calculation, which seems to be more convenient. First, I want to point out that your calculation is correct, but you need to check whether you are using CAN FD or not. If you are using non-FD frames, the result should be 24.8125. For reference, Re: Subject: S32K1XX CANFD Tx arbitration start delay sorry, the question is about "CTRL2[TASD] (Tx Arbitration Start Delay)", not TDC, please check it . Re: Subject: S32K1XX CANFD Tx arbitration start delay Hi@fan1234 Sorry for the misunderstanding, let me take time check your question again.

imx93のMIPI_CSIとLVDSラインをGPIOピンとして設定する こんにちは、 imx93 の MIPI_CSI および LVDS ラインを GPIO ピンとして設定CANますか? Re: configure MIPI_CSI & LVDS lines of imx93 as GPIO pins imx93のデータシートを参照してください。mipi csiとlvdsパッドには多重化機能がないため、GPIOピンとして使用することはできません。

nxp-openwrt 24.10，支持 iw611/iw612 的版本指令 我正试图将 nxp openwrt 端口用于 imx93 evk 衍生工具。 到目前为止，大多数事情看起来都不错，我可以启动到主机，而且大多数东西似乎都能正常工作。但要让 mwiflex 驱动程序与 iw612 芯片配合使用却遇到了问题。 有没有关于如何启动的说明？ 到目前为止，我已经发现你必须下载 nxp-linux 仓库（我用的是 6.6.y）然后在 openwrt 菜单配置中手动指向它。缺少这一步会导致某些补丁失效。 有人能指点我一些关于这个的教程/更新的版本说明吗？ 我发现：https://www.nxp.com.cn/docs/zh/training-reference-material/TIP-5G-IOT-OPENWRT-2.pdf 但这似乎已经过时了... Re: nxp-openwrt 24.10, build instructions with iw611/iw612 support 使用 6.12.y（今天的最新 git），并尝试了 tags/lf-6.12.3-1.0.0我遇到了另一个错误： /home/johan/nxp/openwrt-feeds-6.12/imx_openwrt/版本_dir/target-aarch64_cortex-a53_musl/linux_cortexa53/mac80211-regula r/backports-6.11.2/backport-include/asm/unaligned.h: 3:15：致命错误：asm/unaligned.h：没有这样的文件或目录 3 | #include_next < asm/unaligned.h > | ^~~~~~~~~~~~~~~~~~~~~~~ ~~~~ 编译终止。 make [8]: *** [scripts/makefile.build: 229: /home/johan/nxp/openwrt-feeds-6.12/imx_openwrt/版本_dir/target-aarch64_cortex-a5 3_musl/linux-imx_cortexa53/mac80211-re 重现步骤：启用 kmod-batman-adv，它会拉入 package_kmod-adv cfg80211 和向后移植。 提供一些详细的 版本 说明确实会有所帮助， 谢谢 Re: nxp-openwrt 24.10, build instructions with iw611/iw612 support Hello 试试最新的： https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applications-processors:IMXLINUX 此致 Re: nxp-openwrt 24.10, build instructions with iw611/iw612 support 感谢 Sandra720Ben 的回复！虽然我已经找到了 iw612 可能存在的问题。 我还想为openwrt端口提供某种 " 推荐的 " 版本说明。 建议使用哪个内核版本？ 现在的版本相当 " 脆弱 "，它可以运行 70% 的次数，然后偶尔它会拉出一个不正确/新的 " 向移植代码包 " https://github.com/nxp-imx/imx_openwrt/blob/imx-openwrt-24.10/package/kernel/mac80211/Makefile 它在 6.6.y 上失败了内核 nxp/openwrt-feeds/imx_openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-imx_cortexa53/mac80211.regular/backports-6.11.2/net/wireless/nl80211.c：18771:9：错误：函数 “genlmsg_multic ast_allns” 的参数太少 | genlmsg_multicast_allns (& nl80211_fam，msg，0，| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~。 /include/net/genetlink.h: 485:5：注意：这里声明 485 | int genlmsg_multicast_allns (const struct genl_系列 *系列，| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ 例如，最初是用哪个内核分支开发的，内核 lf-6.6.y、lf-6.12.y 还是 lf-6.XX.XX ? 是否有任何默认设置需要更改，最好能提供 imx93 的 defconfig。 我还必须在内核配置中添加"edma_v3" 内核驱动程序。 如蒙指点，不胜感激。 谢谢 Re: nxp-openwrt 24.10, build instructions with iw611/iw612 support 您好！ 根据你的描述，i.MX93 EVK上的mwiflex驱动程序问题几乎可以肯定是由于缺少固件或设备树配置错误造成的，而不仅仅是内核源代码。虽然你正确地发现指向 NXP Linux 仓库是必要的，但该驱动程序还需要 IW612 芯片的特定固件文件，这些文件通常位于单独的仓库中，如 imx-firmware。没有针对这种特定硬件的简单教程是正常的；通常可以通过检查内核日志（dmesg）来查找驱动程序故障的确切原因，并在恩智浦社区论坛上搜索类似问题，从而找到解决方案。这些论坛是发现所需的确切固件文件和设备树绑定的重要资源。

QSPIフラッシュサイズMIMXRT1062 こんにちは、皆さん i.MXRT1062を使った製品を開発しています。 128Mb を超えるサイズの QSPI フラッシュを使用できますか?EVKは128MBのQSPIフラッシュメモリを使用する 表3-1を見てみましょう。i.MX RT1060X プロセッサリファレンスマニュアルのシステムメモリマップ (CM7) によると、FlexSPI2/FlexSPI2 暗号文は最大 240MB、FlexSPI/FlexSPI 暗号文は最大 256MB を使用できるようです。 Q: i.MX RT1062 のブート デバイスとして NOR フラッシュを使用する場合、利用できる最大容量はどれくらいですか? よろしくお願い申し上げます。 Re: QSPI Flash Size MIMXRT1062 @アンドリュー・チョイ i.MX RT1060 のシステム メモリ マップに基づくと、あなたの観察は正しいです。FlexSPI インターフェースは、256 MB のアドレス指定可能な領域にマップされます。 Q1: 128Mb を超えるサイズの QSPI フラッシュを使用できますか?RT1060-EVK ボードにはどのサイズがありますか? A: 128Mb (16 MB) を超える QSPI NOR フラッシュをCAN使用します。プロセッサのメモリマップは、プライマリFlexSPIインターフェース[2]に256MBのアドレス空間（0x6000_0000から0x6FFF_FFFF）を割り当てており、そのサイズまでのフラッシュデバイスを接続して直接アドレス指定することができます。MIMXRT1060-EVKBボードには、64Mビット（8MB）QSPI NORフラッシュ（部品番号IS25WP064AJBLE [1]）が搭載されています。 Q2: i.MX RT1062 のブート デバイスとして NOR フラッシュを使用する場合、利用できる最大容量はどれくらいですか? A: i.MX RT1062 でブート デバイスとして使用される単一の NOR フラッシュの最大容量は 256 MB です。この制限は、FlexSPI コントローラの 256 MB のアドレス指定可能な空間によって定義されます。内部ブート ROM は、このインターフェースにコネクテッドされたシリアル NOR フラッシュ デバイスからブートするように設計されており、フラッシュからの Execute-In-Place (XIP) をサポートします。 参考文献： [1] MIMXRT1060EVKBUM [2] IMXRT1060RM

Convert Raw File to Jpeg( in i.MX8MP). My purpose is to convert Raw File to Jpeg in i.MX8MP. I am using encoder_test in imx-test-lf-5.15.32_2.0.0. There is no JPEG in mxc_isi_out_format(in kernel isi), so the following error occurs. "isi-m2m 32e00000.isi:m2m_device: mxc_isi_m2m_s_fmt_vid_cap, format is not support!" Is it possible to fix the problem? Or should I use another method? Re: Convert Raw File to Jpeg( in i.MX8MP). current imx8mp HW doesn't have such convert function, customer needs do it by their own SW

How to test se05x-4.3.1-r0 package on imx8m_mini board Hi, we integrated se05x-4.3.1 recipe into mickledore yocto source code(6.1.55 Linux Kernel) for imx8mm-lpddr4-evk target board. I have downloaded "se05x_mw_v04.05.00.zip" from below link and compiled package using  se05x_4.3.1.bb file. https://www.nxp.com/webapp/sps/download/license.jsp?colCode=SE05x-PLUG-TRUST-MW&appType=file1&DOWNLOAD_ID=null&_gl=1*7zr8ng*_ga*MTI5MzE5MjUxNi4xNzEyMjMyMTky*_ga_WM5LE0KMSH*MTcxMjIzMjE5Mi4xLjEuMTcxMjIzMjk4Ny4wLjAuMA..  We are compile SE05x package using above recipe but  I have following queries regarding SE05x package.  1) On imx8mm-lpddr4-evk board, which i2c header is connected for SE05x chip ? what are i2c pin number and i2c header number of schematics ? 2) Any driver changes required for SE05x packages. If yes, what is driver is used for configuring se05x and please share driver path and require changes ? 3) how to test SE05x on imx8mm-lpddr4-evk target board ? please share testing steps.   Thanks, Mallikarjuna Reddy Ambati. Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @mallikarjuna , Yes, I have played SE050ARD with iMX8M kev board, and double confirmed the connection you made between SE050ARD and IMX8M_MINI MPU target board is correct, the root cause should be on the jumpers configurations. Please kindly pay attention to the following two jumpers: J6 should be 1-2 shorten as well as J14. Hope that helps, Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" 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. ------------------------------------------------------------------------------- Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @Kan_Li  On target board, we know which pins should use, but my question is which I2C pins of SE05x should use? please find attached images for SE05x hardware pins overview, In that 4-5 I2C related pins are available. Have you ever tested SE05x module on IMX8M_MINI MPU target board?   Q1) which I2C pins of SE05x should use to connect with IMX8M_MINI MPU ? Thanks, Mallikarjuna Reddy Ambati Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @mallikarjuna , I believe pin3 of J1004 is SCL and pin5 of J1004 is SDA indeed, please make sure you connect them to the same signals on SE050ARD board. Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" 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. ------------------------------------------------------------------------------- Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @Kan_Li , I have used J1004 I2C_CN header to connect with SE050 module as shown below.    Pin connections:- VDD 3V: - 4th Pin of J8 header of SE050 module with 1st pin of J1004 on IMX8M_MINI MPU. GND: - 7th Pin of J8 header of SE050 module with 7th pin of J1004 on IMX8M_MINI MPU.  SDA: - 9th Pin of J2 header of SE050 module with 3rd pin of J1004 on IMX8M_MINI MPU.  SCL: - 10th Pin of J2 header of SE050 module with 5th pin of J1004 on IMX8M_MINI MPU. I modified SE05x source code in simw-top\hostlib\hostLib\platform\linux\i2c_a7.c file i2c interface as  default_axSmDevice_name = "/dev/i2c-2" as we are using i2c3 (J1004 I2C_CN) which is configured as /dev/i2c-2 on target board and build image. I tried to detect SE050 module on i2c bus 2 using command "i2cdetect -y -r 2" but i'm not able to detect SE05x module on i2c-2 bus. Q1) which i2c pins of SE050 module should use to connect with IMX8M_MINI MPU?? Please provide your inputs here to debug these and inform me if I am missing anything?  Thanks, Mallikarjuna Reddy Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @mallikarjuna , Please kindly refer to the following snapshot for details regarding J1004 and yes, 0x48 is always the default address for se05x, no other changes needed. You may firstly use the i2cdetect command to check the hardware connection and then build the MW on IMX8M_MINI MPU Board to test se050 with the demos out of building. Please kindly let me know if there are any further questions. Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" 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. ------------------------------------------------------------------------------- Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi, Please find below fig 1: - OM-SE050ARD module and fig 2: IMX8M_MINI MPU Board that we are using. Fig 1:-  OM-SE050ARD module Fig 2: IMX8M_MINI MPU Board We want to test above SE05x module on Imx8mmini MPU board. On target board, I want to use J1004 I2C_CN (i2c3) header for connections which is configured as /dev/i2c-2 on target board. So, we modified same on simw-top\hostlib\hostLib\platform\linux\i2c_a7.c as default_axSmDevice_name = "/dev/i2c-2";  Now, how SE05x module to be connected with imx8m mini board. Q1) Please provide which I2C pins/I2C header should use on SE050 for connection purpose with imx8m board MPU board. Q2) we modified i2c interface on i2c_a7.c as mentioned above, those changes are enough?  Any DTS changes are required for i2c node? Q3) Is SE050 module slave address is 0x48? Any i2c bus, SE050 is connected on 0x48 slave address? slave addr is mentioned in i2c_a7.c as shown below fig. Please help us, how to test with SE050 on imx8m_mini target board with all required connections and changes. Thanks, Mallikarjuna Reddy. Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @mallikarjuna , Yes, you have to connect OM-SE050ARD-E with the EVK to test SE050, and the connection is something like below: You may refer to simw-top/doc/dev-platforms/platform_imx8_linux.html for more details. Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" 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. ------------------------------------------------------------------------------- Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @Kan_Li , Thank you for the reply. 1) you may firstly use the following command to probe the se05x device on board for verifying the i2c port. "i2cdetect -y -a -q 1", and check if the i2c port should be changed.    - To do that, I think SE05x chip needs to connect with imx8mm-lpddr4-evk target board externally, right?  or Se05x chip comes as built in chip for imx8mm board? Q-1) If needs to connect externally, which I2C pins needs to use for connections? Need to use below J1004 I2C CN header to connect Se05x chip?  Is my understanding correct?  Q-2) If available, please share any link/documents for SE05x connections with i2c header and testing steps?   Thanks, Mallikarjuna Reddy  Re: How to test se05x-4.3.1-r0 package on imx8m_mini board Hi @mallikarjuna , Please kindly have my comments as below: 1) On imx8mm-lpddr4-evk board, which i2c header is connected for SE05x chip ? what are i2c pin number and i2c header number of schematics ? - The default I2C interface is /dev/i2c-1, if another port is used , please modify the definition in "simw-top\hostlib\hostLib\platform\linux\i2c_a7.c" 2) Any driver changes required for SE05x packages. If yes, what is driver is used for configuring se05x and please share driver path and require changes ? - Not needed at all. 3) how to test SE05x on imx8mm-lpddr4-evk target board ? please share testing steps.   - you may firstly use the following command to probe the se05x device on board for verifying the i2c port. "i2cdetect -y -a -q 1", and check if the i2c port should be changed. then you may run any se05x demo in /usr/local/bin for test. Hope that makes sense, Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" 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. -------------------------------------------------------------------------------

I want to speed up jpeg decoding in i.MX RT Hi community. I need faster JPEG decoding on i.MX RT1170 EVK. I measured the jpeg decoding time of the sample software sd_jpeg_cm7. It uses 23msec to decode a 480x272 jpeg image, but I would like to speed this up. The request requires about a 3x speedup. Do you have any ideas? Best regards. Re: I want to speed up jpeg decoding in i.MX RT Hi @Ryo_Aoki ,   Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.   About the decoding, you can refer to this application note: https://www.nxp.com/docs/en/application-note/AN12562.pdf It contains some performance information.   So,if you want to speed up, I think, you can copy the code to the internal TCM or OCRAM, it will faster than the external flash running result. Wish it helps you! If you still have question about it, please kindly let me know. Best Regards, Kerry

RT1176远程升级遇到的问题 当我按照论坛中的另一个帖子（帖子链接在最后），进行远程升级时，我遇到了一个问题，在SBL文件的配置和生成过程是很顺利的，随后我使用MCUXpresso IDE生成了一个HELLO_WORLD APP，并且为这个APP生成了与SBL相匹配的头，按照教程我将APP通过NXP-MCUBootUtility烧写到0x30100000地址下，对板卡进行复位，SBL成功启动，并且能够引导APP程序，串口可以打印出HELLO信息 随后我尝试使用Keil生成一个HELLO_WORLD APP，并对这个APP配置了与上面相同的SBL头，并也将APP通过通过NXP-MCUBootUtility烧写到0x30100000地址下，对板卡进行复位，SBL成功启动，并且能够引导APP程序，但串口无任何打印信息 我认为这样的现象是SBL正常、且对于APP配置的头也正常，这样才能对APP进行正确的引导，但是APP内容或配置不正常，导致的无法正常输出打印信息 我对比了我用MCUXpresso编译APP时和用keil编译APP时的操作 对于MCUXpresso来说，我去掉了FCB头，并且配置了FLASH地址偏移到了0x30100400 对于Keil来说，我同样去掉了FCB头，并且配置了FLASH地址偏移到了0x30100400 但最后，keil生成出的bin加上引导头后，经过SBL引导，并不能成功打印出，但MCUXpresso的却可以成功打印，请帮忙看看是哪里出了问题，谢谢 PS：帖子链接如下 https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/RT1170-SBL-ISP-download-SDRAM-APP/ta-p/1767982 i.MX-RT1170  Re: RT1176远程升级遇到的问题 非常感谢您的答复，按照您所说的，我修改了分散加载文件后，目前已经可以成功引导了，感谢！

sCheck 之后需要再次进行哪些初始化 你好，我发现在 s32k312 上执行 sCheck 之后必须再次调用 Platform_Init()，否则 intm 可能无法工作。我认为 sCheck 可能会更改检查的一些设置并保持不变。我是否应该调用所有初始化函数来重置外围设备？如Mcu_Init()、Mcl_Init()、Rm_Init()。