Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
IMX8MP linux uboot need to be set up with the default environment + extra variables IMX8MP linux uboot need to set up the default environmnet + few more variables after the flashing the bootloader via uuu. Use case: The IMX8MP SoM comes with default uboot from vendor. So for the first time writing need to flash the new uboot image, we set it to the default environment and set few more board specific environment variables on the factory process. So when I'm using the command, uuu -b emmc_all bl-imx8mp.bin image.wic.zst its using the builtin script uuu_version 1.4.149 # @_flash.bin | bootloader, which can extract from wic image # @_image [_flash.bin] | wic image burn to emmc. # This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ SDP: boot -f bl-imx8mp.bin -scanlimited 0x800000 # This command will be run when ROM support stream mode # i.MX8QXP, i.MX8QM SDPS: boot -scanterm -f bl-imx8mp.bin -scanlimited 0x800000 # These commands will be run when use SPL and will be skipped if no spl # SDPU will be deprecated. please use SDPV instead of SDPU # { SDPU: delay 1000 SDPU: write -f bl-imx8mp.bin -offset 0x57c00 SDPU: jump -scanlimited 0x800000 # } # These commands will be run when use SPL and will be skipped if no spl # if (SPL support SDPV) # { SDPV: delay 1000 SDPV: write -f bl-raptor-imx8mp.bin -skipspl -scanterm -scanlimited 0x800000 SDPV: jump -scanlimited 0x800000 # } FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: ucmd mmc dev ${emmc_dev} FB: flash -raw2sparse all image.wic.zst/* FB: flash -scanterm -scanlimited 0x800000 bootloader bl-imx8mp.bin FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi; FB: ucmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0 FB: done So my requirement is Flash the bootloader + rootfs / image Reset to defaults. Add new variables. Reboot with proper working new bootloader with expected env. But now its first flashing the rootfs and then the new bootloader. So when I executed env default -f -a, after it, it causes the default of environment of old bootloader in the SoM board. When it resetted, it starts then with new bootloader but with old defaults from old bootloader. Is there any suggestion to solve this issue? Re: IMX8MP linux uboot need to be set up with the default environment + extra variables Hello @jake4  Hope you are doing very well. You can try making your own custom script and add the below: FB: ucmd env default -f -a Example of complete script: uuu_version 1.4.149 SDP: boot -f bl-imx8mp.bin -scanlimited 0x800000 SDPS: boot -scanterm -f bl-imx8mp.bin -scanlimited 0x800000 SDPU: delay 1000 SDPU: write -f bl-imx8mp.bin -offset 0x57c00 SDPU: jump -scanlimited 0x800000 SDPV: delay 1000 SDPV: write -f bl-imx8mp.bin -skipspl -scanterm -scanlimited 0x800000 SDPV: jump -scanlimited 0x800000 FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: ucmd mmc dev ${emmc_dev} FB: flash -raw2sparse all image.wic.zst/* FB: flash -scanterm -scanlimited 0x800000 bootloader bl-imx8mp.bin FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi; FB: ucmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0 FB: ucmd env default -f -a FB: ucmd setenv board_version "1.0" FB: ucmd setenv my_custom_var "value" FB: ucmd saveenv FB: ucmd reset FB: done Best regards, Salas. Re: IMX8MP linux uboot need to be set up with the default environment + extra variables Hi @Manuel_Salas , We would have only eth fastboot enabled in the uboot , so we cant use the boot switch of SDP. Can you please let me know if there is a option with only the fastboot command. Thanks
View full article
How use adjust SOI -EOI with use MC33 PT2000 IC just as topic, we need the help which can esstablished whole process , which use PT2000 to apply fule injection SOI -EOI measurement  H-Bridge Driver Small Engine Driver Solenoid Controller Re: How use adjust SOI -EOI with use MC33 PT2000 IC appreciated! Re: How use adjust SOI -EOI with use MC33 PT2000 IC Dear Kaijinbin,  there is an PT2000 end of injection detection application note available to download from the PT2000 product page, with a valid NDA.  If you don't have an NDA yet and you would like to sign one, please create a new ticket here and our representative for NDA matters will help you with the process.  Additionally please download the PT2000SWUG and PT2000-IDEUG from the FRDMPKPT2000EVM product page. You can download the PT2000 Developer Studio IDE and Software Files for Peak and Hold and DCDC software from the same page. You can then test the software example on the FRDMPKPT2000EVM Evaluation Board.  With Best Regards, Jozef
View full article
Detail about S32K338 Good morning, I need to know if the S32K388 microcontroller has three independent cores, like the K324 (which has two), and if two of these cores can also be used in Lockstep. If I want one single core + one Lockstep core, should I use the K358? Thanks Re: Detail about S32K338 Hello @gianpiero_lenta , Lockstep operation is not a software-configurable feature that can be enabled between two independent cores. Instead, Lockstep is a dedicated hardware configuration implemented in specific S32K3 derivatives. Therefore, if your application requires one independent Cortex-M7 core together with a Lockstep Cortex-M7 pair, I recommend using the S32K358, which is designed with this hardware configuration. Best regards, Pavel
View full article
rt1189 Boot Flow 1. As shown in the figure, does the "Authenticate Image" process verify the hash value during the SHA-512 hashing stage?  2. If I set the hash value, will the BootROM verify the image integrity? And if the BootROM verification fails, will it enter recovery mode? Re: rt1189 Boot Flow 1. Is hash verification enabled only when the signature authentication feature is enabled? How can hash verification be enabled independently? How can the device be transitioned into the OEM_CLOSED lifecycle state? 2. I will enable the Recovery Boot fuse. 3. My goal is to use an unencrypted image. The Boot ROM should calculate and verify the image hash. If the hash verification fails, the Boot ROM should enter the recovery boot flow and boot the recovery image from the LPSPI NOR Flash. Re: rt1189 Boot Flow Hi @yanyanwang , A1: Yes. RT1180 uses AHAB with two authentication layers: Signature layer: ECDSA (SHA-256 / SHA-384) verifies the Container header and image array entry (which stores each image's Hash). Hash layer: The ROM re-computes the digest of the loaded image body and compares it against the Hash stored in the image array entry. The SHA hashing stage in your figure is exactly this mandatory integrity check, which does verify the hash value. A2:The ROM always computes and compares the hash, but whether a failure is enforced depends on the device life cycle: the out-of-fab default is the Open configuration, where authentication runs but all authentication errors are ignored and the image still executes. Only after the device is moved to OEM_CLOSED will a hash mismatch actually block boot. Whether it enters recovery depends on the Recovery Boot fuse. if enabled, a primary-boot authentication failure triggers a re-load and re-authentication from the recovery device; if not enabled, the flow falls through to Serial Downloader / Fatal Mode / reset loop. Best regards, Gavin Re: rt1189 Boot Flow As shown in the figure above, if I only sign the image and do not encrypt it, will it be able to go through the bootrom verification flow? Additionally, with oem_close enabled, will it still be able to enter the bootrom verification flow?     Re: rt1189 Boot Flow Please find answers to your two questions below: 1. Can a signed-only (non-encrypted) image go through the BootROM verification flow? Yes. In the RT1180 AHAB, signing (authentication) is the mandatory part of secure boot, ensuring image authenticity and integrity, while encryption (OTFAD/IEE) is an independent, optional anti-cloning feature and is NOT a prerequisite for verification. Therefore, a signed-only image will go through the full AHAB signature verification flow normally, this is also the standard approach in NXP's official SPSDK rt118x_secure_boot example. 2. With oem_close (OEM_CLOSED) enabled, will it still enter the verification flow? Yes, and verification becomes mandatory. Recommendation: Before performing oem_close, please program the signed image in the OEM_OPEN state first and confirm it boots successfully with no ELE events, then close the device (SRKH is irreversible once fused) to avoid bricking the part. (Please refer to: i.MX RT1180 Security Reference Manual. After signing the NDA through your company account, submit a request to the online technic sales representative.) Re: rt1189 Boot Flow Using the two demos, multicore_trigger and cm7_helloworld, I did not enable ECC for the CM7 ITCM. I used the SPT tool to merge the CM33 image and the CM7 image, which is intended to run from memory, into a single image, and then programmed the merged image into NOR Flash through UART. However, the boot process failed. According to the manual, a container can contain up to 8 OEM image entries. In my test, I only included two images: one CM33 image and one CM7 image. CM7 ITCM ECC was not enabled. Neither the CM33 nor the CM7 image started. However, when I checked the container header, I found that only the CM33 image was present. The CM33 image itself can boot normally without any issues when used alone. I would like to understand why the CM7 image was not included or processed as expected, and whether the lack of CM7 ITCM ECC configuration affects how Boot ROM processes the CM7 image. Question 2: If I merge 8 CM7 images and 1 CM33 image into a single container, what will the Boot ROM do during the startup process? Since there is only one CM7 core, how does Boot ROM determine which CM7 image should be booted? If all 8 image entries are CM7 images, will Boot ROM load all 8 images, select only one image, or leave the selection to the CM33 application? How does Boot ROM identify and process multiple CM7 image entries in the same container? Is there a priority, image index, Core ID, load address, entry point, or another mechanism used to determine which CM7 image is executed? I would also like to understand the exact Boot ROM behavior when CM7 ITCM ECC is enabled and when it is not enabled. When CM7 ITCM ECC is enabled, does Boot ROM initialize the CM7 ITCM ECC memory, copy the CM7 image from NOR Flash into CM7 ITCM, and then release CM7 from reset? Or does Boot ROM only load the CM7 image, while the CM33 application is responsible for releasing CM7 from reset and starting it? When CM7 ITCM ECC is not enabled, what does Boot ROM do when it encounters a CM7 image whose load address is in CM7 ITCM? Does Boot ROM skip the CM7 image, fail to load it, leave CM7 in reset, or cause the entire container boot process to fail? In particular, I would like to clarify whether the following container is supported: Image 0: CM33 Image 1: CM7 Image 2: CM7 Image 3: CM7 Image 4: CM7 Image 5: CM7 Image 6: CM7 Image 7: CM7 Image 8: CM7 If it is supported, what exactly happens to these 8 CM7 images during Boot ROM startup, and which component is responsible for selecting the CM7 image that will actually execute? Finally, I would like to clarify whether the maximum of 8 OEM image entries means that the container can simply store 8 different images, or whether Boot ROM also provides a mechanism to select and boot a specific image for a given core.
View full article
关于FS2613芯片的选型 FS2613系列芯片功能是比较强大的,各个电源轨的数值和时序是可以编辑的。但我们没有太多软件开发的精力,也尽量不想自行OTP。请问有没有哪个型号,出厂的默认配置就是适配S32K358的?比如下图? Rio_Lee_0-1786090969347.pngRio_Lee_0-1786090969347.png Re: 关于FS2613芯片的选型 看附件 Re: 关于FS2613芯片的选型 嗯嗯,请问对于MFS2633AMDB2AD型号,默认上电后,以下各通道的输出电压分别是多少? VCORE、LDO1、LDO2、VREF、VBST;TRK1与TRK2跟随来源是哪里? Re: 关于FS2613芯片的选型 MFS2633AMDB2AD Search | NXP Semiconductors 你可以选择这个! Re: 关于FS2613芯片的选型 MFS2633AMDB2AD已停产,同等参数,我应该替换成:MFS2633HMDB2AD,对吧? Re: 关于FS2613芯片的选型 是的! Re: 关于FS2613芯片的选型 请问该芯片的PIN.17 FCCU1与PIN.18 FCCU2是如何使用的?两个Pin脚的输入值会构成真值表,引发芯片的不同保护措施? Re: 关于FS2613芯片的选型 新的问题请提交新的ticket多谢! Re: 关于FS2613芯片的选型 请问出厂的默认配置在适配S32K358的基础上,LDO1、LDO2、TRK1、TRK2都是3.3V的型号? Re: 关于FS2613芯片的选型 guoweisun_0-1787644183604.png 有两个适配K35X的都不是您想要的LDO1、LDO2、TRK1、TRK2都是3.3V 新问题可以提交新的ticket最好用公司的邮箱
View full article
iMX8 Nano Kernel updation from 5.15 to 6.18 Hi  While porting the kernel from 5.15 to 6.18 for the A53 core. facing an issue with rpmsg.  # dmesg -T | grep -Ei 'rpmsg|rproc' [Tue Oct 8 15:42:28 2024] imx rpmsg driver is registered. [Tue Oct 8 15:42:29 2024] imx-rproc imx8mn-cm7: error -ENOENT: Failed to enable clock [Tue Oct 8 15:42:29 2024] imx-rproc imx8mn-cm7: probe with driver imx-rproc failed with error -2 [Tue Oct 8 15:42:29 2024] remoteproc remoteproc0: releasing imx-rproc I am getting this error.When i searched this error online i was asked to add dummy clock in the dts as below  imx8mn-cm7 {     compatible = "fsl,imx8mn-cm7";     rsc-da = <0xb8000000>;     clocks = <&clk IMX8MN_CLK_DUMMY>;     mbox-names = "tx", "rx", "rxdb";     mboxes = <μ 0 1                                    μ 1 1                                    μ 3 1>;     memory-region = <&vdevbuffer>, <&vdev0vring0>, <&vdev0vring1>, <&rsc_table>;     status = "okay";   } Could u please let me is this the only the change required. What is the reason for this change. Regards Yadunath R Re: iMX8 Nano Kernel updation from 5.15 to 6.18 No — I would not treat clocks = <&clk IMX8MN_CLK_DUMMY>; as the only required change. It may be enough to get past the immediate -ENOENT: Failed to enable clock probe failure, but for i.MX8M Nano the important requirement is that the Cortex-M7 root clock must remain enabled when Linux loads/starts the M7 firmware. Reason: The imx-rproc node is expected to have a clock entry; AN5317 shows the i.MX8M remoteproc DTS node with compatible = "fsl,imx8mn-cm7" and a clocks = <...> property, plus mailbox and memory-region entries. Your error means the kernel 6.18 imx-rproc driver tried to get/enable the clock from that node and the clock lookup failed with -ENOENT , so probe aborted before remoteproc0 stayed registered. NXP’s AMP guidance says: “For i.MX 8M platforms, the root clock for M7/M4 must be kept always enabled by Linux to load the firmware code and start Cortex M7/M4.” It also says NXP Linux BSP keeps this root clock enabled when the M core is started from U-Boot; otherwise, if the M core is first started from Linux boot, drivers/clk/imx/clk-composite-8m.c must be updated to skip gate registration for the M core clock. So the change has two possible meanings: Dummy clock as compatibility workaround If kernel 6.18 imx-rproc requires a clocks property but the real M7 clock is intentionally not controlled through common clock framework, adding IMX8MN_CLK_DUMMY can satisfy the driver’s clock handle requirement and avoid -ENOENT . Real clock-control fix If Linux is actually responsible for loading/starting the M7, a dummy clock alone may hide the probe error but not guarantee the M7 clock is enabled. In that case you must ensure the M7/M4 root clock is kept on, either by the NXP BSP clock-driver handling or by the clk-composite-8m.c change described in AN5317. Also verify the rest of the remoteproc/rpmsg DTS, not only the clock line: imx8mn-cm7 {         compatible = "fsl,imx8mn-cm7";         rsc-da = <...>;         clocks = <&clk IMX8MN_CLK_DUMMY>;   /* or the correct M7 clock used by your BSP */         mbox-names = "tx", "rx", "rxdb";         mboxes = <μ 0 1>, <μ 1 1>, <μ 3 1>;         memory-region = <&vdevbuffer>, <&vdev0vring0>, <&vdev0vring1>, <&rsc_table>;         status = "okay"; }; The memory-region list is important because AN5317 states that this property must contain the memory sections used by the firmware ELF so remoteproc can reload it from sysfs. Recommended check path: If you start M7 from U-Boot , use the NXP flow such as prepare_mcore / bootaux , then boot Linux; AN5317 says this is the path where the BSP keeps the M core root clock enabled. If you start M7 from Linux remoteproc , confirm your 6.18 clock driver includes the NXP handling to keep the M core root clock always enabled; otherwise the dummy clock may only fix probe, not runtime start/load. Compare your DTS against the NXP imx8mn-*-rpmsg.dts for the same BSP release, especially clocks , mboxes , rsc-da , and reserved-memory layout. The dummy clock explains the immediate -ENOENT probe failure, but the real design requirement is to keep the i.MX8MN M7 root clock enabled; whether DTS alone is sufficient depends on whether your 6.18 BSP clock driver already preserves that clock.
View full article
External Data Abort when calling Clock_Ip_Init() Hi there, I'm attempting to initialise some peripheral clocks using the RTD and S32 DS mex tool. (Note im generating the code in a M7 project, but actually building and running for a A53 project) However, an external data abort occurs inside Clock_Ip_Init(). Specifically, the call stack looks like this: Clock_Ip_Init -> Clock_Ip_InitClock() -> Clock_Ip_DisableCmuFcFceRefCntLfrefHfref(). This appears to be the first attempt to actually write to the CMU peripheral memory. The fault occurs on a LDR instruction on memory 0x4005'C028 which according the S32G3 memory map correctly resides within the CMU memory area. At this stage, the MMU is not enabled, but my understanding is an external data abort occurs outside the CPU/MMU and is probably linked to secure access or a "locked" peripheral. Am i right in saying the CMU needs to be made "accessible" from the A53 core in some manner prior calling Clock_Ip_Init()? If so, could you advise on the steps to do so? Best regards, Jonny Device = S32G399A Compiler = S32DS_GCC _11_4 Core = Cortex A53 Re: External Data Abort when calling Clock_Ip_Init() Hi,jonnyWHIS Thank you for contacting us. Do you intend to create bare-metal code running on the S32G A53 core in the S32DS IDE? BR Joey
View full article
Unable to access MT29F64G08AECAB 8GB NAND Flash from T2081 processor Hi, I have a T2081 NXP processor connected to an external NAND Flash MT29F64G08AECAB via IFC. My goal is to run diagnostic test on this NAND Flash on code warrior or simply read the device and manufacturer ID of this device on Code Warrior (for which I have written the code). To achieve this goal, I have done the following already: 1. Configured LAW for the NAND IFC in the generated T2081QDS_init_core.tcl starting from 0xFF800000 and of size 1MB.  ## LAW3 to IFC - NAND   # LAWBARH   mem [CCSR_ADDR 0x000C30] = 0x00000000   # LAWBARL   mem [CCSR_ADDR 0x000C34] = 0xFF800000   # LAWAR   mem [CCSR_ADDR 0x000C38] = 0x81F00013 2. Also have configured the CSPR and FTIM registers corresponding to NAND like below : set NAND_CS   5 # NAND Flash, addr 0xFF800000, 1MB size, 8-bit NAND, ECC disable   # CSPR_EXT   mem [CCSR_ADDR [expr 0x12400C + $NAND_CS * 0x0C]] = 0x00000000   # CSPR   mem [CCSR_ADDR [expr 0x124010 + $NAND_CS * 0x0C]] = 0xFF800103   # AMASK   mem [CCSR_ADDR [expr 0x1240A0 + $NAND_CS * 0x0C]] = 0xFFFF0000   # CSOR   mem [CCSR_ADDR [expr 0x124130 + $NAND_CS * 0x0C]] = 0x01082100   # IFC_FTIM0   mem [CCSR_ADDR [expr 0x1241C0 + $NAND_CS * 0x30]] = 0x1E0B0507   # IFC_FTIM1   mem [CCSR_ADDR [expr 0x1241C4 + $NAND_CS * 0x30]] = 0x2929090B   # IFC_FTIM2   mem [CCSR_ADDR [expr 0x1241C8 + $NAND_CS * 0x30]] = 0x01203819   # IFC_FTIM3   mem [CCSR_ADDR [expr 0x1241CC + $NAND_CS * 0x30]] = 0x15000000 Note that there are 2 chip selects (CS5 and CS6) going from the processor to NAND and for the time being I am trying to access the first 4GB and hence configuring CS5 only. 3. Configured TLB: fine   1M TLB entry  5 : 0xFF800000 - 0xFF8FFFFF for NAND   cache-inhibited, guarded   reg ${CAM_GROUP}L2MMU_CAM5  = 0x5000000A1C08000000000000FF80000000000000FF800001 4. And since the device support for this MT29F64G08AECAB could not be found in the installed directory, I followed the manual and created a .xml for this device (for 4GB) which I have attached here. After doing all of this, when I run the diagnostic test for the NAND device on code warrior, I get the below error: Nisarga_R_0-1786096350786.pngNisarga_R_0-1786096350786.pngNisarga_R_0-1786096350786.pngNisarga_R_0-1786096350786.png As an alternative I tried to write a simple C code to read back the device id from this device. So I wrote the below code in code warrior and I have attached it here. And as a result when I read back the IFC_NAND_MDR register I get back 0x124E0000 which is not matching with the Device ID. I would like to know if I am doing something wrong or missing out something because I am unable to run the diagnostic test or read back the device id. I have attached the respective T2081QDS_init_core.tcl and also the respective schematics for reference. Regards, Nisarga R   QorIQ T2 Devices Re: Unable to access MT29F64G08AECAB 8GB NAND Flash from T2081 processor I am discussing with the internal team now. Thanks Re: Unable to access MT29F64G08AECAB 8GB NAND Flash from T2081 processor Your NAND flash hardware connections appear to be aligned with the recommended design guidelines, assuming RCW[IFC_GRP_E2_BASE] = 0 and the NAND device is not being used as the boot source. Having said that, what Device ID value are you expecting to read back from the IFC_NAND_MDR register? We have never tried and tested with dual-die NAND devices and are not sure about its operation.  Based on our experience with the single die NAND flash devices, please check the following and share the results with us for further investigation. 1) Share the complete IFC register dump if possbile 2) Share the IFC interface pin-mux configuration. 3) If there is any update of the Codewarrior debug, please also let me know. 4) Please refer the below sections of RM and verify if your NAND flash implementation aligns with the information documented therein:  a) 13.2 External signal descriptions b) 13.5 NAND flash control machine c) 13.9 Initialization/Application information Thanks Re: Unable to access MT29F64G08AECAB 8GB NAND Flash from T2081 processor Any update? Thanks Re: Unable to access MT29F64G08AECAB 8GB NAND Flash from T2081 processor it seems CE and CE2 is connected seperately while the rest pin is connected together like ALE etc. Not sure it is right for dual layer NAND device. Please check the schematics for NAND device
View full article
SPD 1.0.3 — eMcem.xdm XDM Schema Bug at Line 717 (EB Tresos Import Failure) I am reporting a bug in S32K3 Safety Peripheral Drivers (SPD) version 1.0.3, specifically in the eMcem module's XDM configuration file which prevents it from being imported into Elektrobit (EB) Tresos Studio. Environment ┌───────────────────┬─────────────────────────────────────────┐ │ Item │ Version / Path │ ├───────────────────┼─────────────────────────────────────────┤ │ MCU │ S32K344 (S32K3XX) │ ├───────────────────┼─────────────────────────────────────────┤ │ SPD │ S32K3_SPD 1.0.3 (S32K3_SAF_1.0.3_D2306) │ ├───────────────────┼─────────────────────────────────────────┤ │ RTD │ SW32K3_RTD 4.4 R21-11 3.0.0 P01 │ ├───────────────────┼─────────────────────────────────────────┤ │ EB Tresos │ 29.0.0 (installed at C:\EB\tresos) │ ├───────────────────┼─────────────────────────────────────────┤ │ S32 Design Studio │ 3.6.0 │ └───────────────────┴─────────────────────────────────────────┘ Issue Description When attempting to import the eMcem module (eMcem_TS_T40D34M10I3R0) into an EB Tresos project, the XDM parser throws the following error: ▎ "Invalid Attribute 'a' for tag 'a'" at line 717 of config/eMcem.xdm This prevents the eMcem module from being imported into any EB Tresos project entirely. Root Cause Analysis The file C:\NXP\S32K3_SPD_1.0.3\eclipse\plugins\eMcem_TS_T40D34M10I3R0\config\eMcem.xdm contains an invalid XDM schema structure at lines 715–718,in the RecoveryTimeoutEnabled parameter block: Buggy code (lines 715–718): VariantPreCompile The problem is the nested inside the element. According to the XDM schema (http://www.tresos.de/_projects/DataModel2/08/attribute.xsd), an element cannot contain another element as a child. The correct structure used by all other occurrences in the same file (e.g., the ReactionType parameter at lines 684–687)is: Correct code: VariantPreCompile This is the only occurrence of this malformed nesting in the entire eMcem.xdm file (20+ other IMPLEMENTATIONCONFIGCLASS blocks are correctly formed). It is clearly a copy-paste error during the SPD packaging process. Verification - The Bist module (Bist_TS_T40D34M10I3R0) and SafetyBase module (SafetyBase_TS_T40D34M10I3R0) from the same SPD 1.0.3 package do not have this bug —their .xdm files are correctly structured and import into EB Tresos without any errors. - I confirmed that the Bist.xdm file has zero occurrences of nested inside . Why This Is a Deadlock The META-INF/CRYPTOMANIFEST.MF and META-INF/CRYPTOMANIFESTSIG.MF files in the eMcem plugin contain DSA cryptographic signatures (Key ID: Freescale, Provider: dreisoft.tresos.launcher2.CryptoKeyProvider) for key plugin files including config/eMcem.xdm. Any modification to the .xdm file —even a single-line fix —breaks the DSA signature verification, causing EB Tresos to reject the module with a license/integrity error. This creates an irrecoverable deadlock: - Cannot import with the bug —XDM schema validation fails - Cannot fix the bug —DSA signature verification fails →license error - Cannot remove the signatures —EB Tresos fails to start (plugin integrity check) Request Please provide one of the following: 1. A hotfix release of SPD (or at minimum, a corrected eMcem.xdm file with updated CRYPTOMANIFEST signatures) compatible with our environment 2. An updated SPD version (e.g., 1.0.4 or newer) that includes this fix 3. A license re-activation or workaround that allows us to apply the necessary one-line fix to eMcem.xdm without triggering the DSA signature validation failure 4. Confirmation of whether a newer SPD version exists that resolves this issue, along with download/upgrade instructions This issue is blocking our S32K344 safety software integration, specifically the eMcem (Extended Microcontroller Error Manager) module configuration in EB Tresos. Additional Note The SPD 1.0.3 Release Notes state compatibility with RTD 3.0.0 / 3.0.0 P07. We are using RTD 4.4 (SW32K3_RTD_4.4_R21-11_3.0.0_P01). Could you also confirm the compatibility status between SPD 1.0.3 and RTD 4.4, and advise if a newer SPD version is required for RTD 4.x integration? --- Thank you for your assistance. Please let me know if you need any additional information or logs. Best regards. Re: SPD 1.0.3 — eMcem.xdm XDM Schema Bug at Line 717 (EB Tresos Import Failure) Hello @WuDiDi, The issue is also present in SPD 1.0.4. I can see that it has been fixed in SPD 1.0.5 and SPD 1.0.6: SPD version 1.0.5 is compatible with S32K3_S32M27x Real-Time Drivers ASR R21-11 Version 5.0.0 and 4.0.0. Version 4.0.0 is supported for all derivatives except S32K3E ones (S32K39x and S32K36x). SPD version 1.0.6 is compatible with S32K3 Real-Time Drivers Version 7.0.0 + 6.0.0. Could you update to a newer RTD/SPD version? Many RTD, SPD bug has been fixed since version 1.0.3. Please note that NXP does not provide hotfixes for outdated software versions. Regarding SPD 1.0.3 compatibility, we can only guarantee functionality with the RTD version explicitly specified in the release notes. Compatibility with other RTD versions is not guaranteed. Regards, Daniel Re: SPD 1.0.3 — eMcem.xdm XDM Schema Bug at Line 717 (EB Tresos Import Failure) Hi Daniel, Thank you for the clarification. I am already using SPD 1.0.5 (D2503) with RTD 4.0.0 P01 for S32K342, so the version compatibility should be fine. I have a specific question about implementation scope: the SPD 1.0.5 Demo project (S32_SPD_Demo) only provides TresosProject configurations for S32K344/S32K358/S32K388/S32K396, not S32K342. I am adapting it to S32K342. Could you confirm the following for S32K342: 1. Lockstep fault injection: Does S32K342 support lockstep fault injection via the DCM/EIM mechanism? The S32K342 is a single-core lockstep device —I see EMCEM_DCM_NCF_3_LC_ERR and EMCEM_DCM_NCF_0_PLTFRM_CM7_0_LUP in the DCM fault list. Are those the correct injection points? 2. LBIST/MBIST: The Bist_TS_T40D34M10I5R0 plugin has S32K342 EPD variants. Are the LBIST MISR golden signatures and MBIST partition tables in Bist_SpecificTables_S32K3XX.c already correct for S32K342 silicon? Do we need any S32K342-specific adjustments? 3. Is there an application note or reference manual specifically for S32K342 safety verification (LBIST/MBIST/lockstep FI) that you can share? Re: SPD 1.0.3 — eMcem.xdm XDM Schema Bug at Line 717 (EB Tresos Import Failure) Hi @WuDiDi, The follow-up questions are not related to the original topic. Could you please create a new thread for them? Thank you. BR, Daniel
View full article
GUI Guider 2.0 图片存储类型选择Flash,无法显示 Re: GUI Guider 2.0 图片存储类型选择Flash,无法显示 嗨@sk-l 请 您 提供 更 详细 的 问题 描述 ?It would be very helpful if you could also attach screenshots or relevant pictures for 参考,引用.   谢谢。   BR 哈里 Re: GUI Guider 2.0 图片存储类型选择Flash,无法显示 图片/动画图片 颜色格式 I4,存储类型 Flash,模拟期间不显示; 颜色格式 I4,存储类型 C 数组,图像显示正常;
View full article
需要S32DS的激活码 s32ds 安装的激活码 需要签署NDA 需要用到公司邮箱 没有公司邮箱 请确认下 怎么申请 Re: 需要S32DS的激活码 你好, 你喜欢用哪个版本的S32DS?
View full article
FS32K144UAT0VLLT哪个Time具备Input capture功能? 经理: 请教问题: (1)FS32K144UAT0VLLT规格书显示具备8个独立TIME,只看到FTM0,FTM1,FTM2,还有哪些也是TIME? (2)FS32K144UAT0VLLT的哪个TIME具备Input capture功能? 谢谢! Re: FS32K144UAT0VLLT哪个Time具备Input capture功能? Robin_Shen 你好,补充问题: 1. S32K-RM Rev14.2的Table 47-1. FTM instances and features 表格里,“Fault inputs"是什么参数? 2. S32K-RM Rev14.2手册多少页显示每个FTM都具备input capture功能? 谢谢! Re: FS32K144UAT0VLLT哪个Time具备Input capture功能? A1. 就是支持几路外部Fault输入,以S32K144为例Table 47-1写了支持4路,你可以在左侧表格看到FTM0_FLT0\1\2\3 这4路。 A2. 每个FTM都支持的功能,通常不会特地写出来。你按照Table 47-5. Channel Modes Selection配置寄存器就能实现47.5.5 Input Capture Mode 提到的input capture 模式了。
View full article
PCA9615 I am writing to ask for help with the circuits at either end of dI2C communication - between two PCBs across a twisted wire bundle (DSDAP & DSDAM; DSCLP &  DSCLM; two GND; and two 5V lines). Leading up to this I decided to test Gemini so I regretably relied on AI to generate the parts of the two PCBs that related to the dI2C comms. Attached are the parts of the schematics associated with the dI2C. Unsuprisingly there is no comms between the boards, but my laziness and I have to say stupidity (leason learnt) has cost me a lot of time. I finally referred to the datasheet and the user manual for the demo board and one obvious difference is that there are 600 Ohm resistors between the positive lines (DSCLP and DSDAP) and VDD(B), the same from the negative lines (DSCLM and DSDAM) and VSS, and 120 Ohms between the respective positive and negative lines which apparently result in 100 Ohms between the positive and negative lines (I know that 1/600 + 1/120 = 1/600 + 5/600 = 100, but I can't see it electrically- maybe because I'm a mechanical engineer ??). Is the error (maybe one of a number of errors) caused by not having what may be considered a 600 Ohm pull up resistor, a 600 Ohm pull down resistor and a 120 Ohm resistor between the respective pair of wries (characteristic impedance of a 28 AWG twisted wire pair is about 100 Ohms cabling used in internal data links and USB/Ethernet configurations and 78 Ω to 95 Ω for standard spacing configurations using PVC or FEP insulated wires), but instead a simplified and likely erroneous version of just a single 100 Ohm resitor at either end of the connecting wire on the dI2C side of the PCA9615?  That is one significant difference between what AI gave me and what I see in Figs 1, 7, 8 and 9 of the datasheet. Another difference is that AI suggested different capacitor arrangements for the two PCBs whereas there's only one type of arrangement on the demo board (which I assume gets used on both sides of the dI2C connecting line). Further, there appears to be two capacitors for each of the VDDA pin and the VDDB pin - both ceramic capacitors (although my first thought was that the two yellow capacitors would have been tantalum type). Can I use the capacitor arrangement provided in the demo user manual and ignore what AI provided and shown in the attached? Another issue is that on the master side (on which I am using a 3.3V microcontroller) originally Ai instructed that the enable pin be conencted to the 5V line, but after having had the boards made, the lack of any function across the two boards in part prompted the AI to determined that the enable pin on the master side should have been connected to the 3.3V line (VDD(A) on the master board was connected to the 3.3V line). It then requested that all all supply to the enable pin on the master PCB be cut completely as a test. Can you please advise what supply, if any all, should be channeled to the EN pin? I will not be hot swapping any electrical hardware during test or final operation. I am considering implementing the above changes, but would really appreciate your help before I proceed further with costly boards. Re: PCA9615 Just a further thing regarding the capacitors, only decoupling capacitors were suggested for both VDDA and VDDB pins on the master PCB. Decoupling capacitors were also suggested for the slave PCB, but two additional capacitors were also suggested for the VDDB pin on slave PCB.  Re: PCA9615 Hello! Thank you for the detailed explanation. Please note that NXP provides an evaluation board for the PCA9615 family that can be used as a reference design for your implementation. We strongly recommend comparing your schematic against the PCA9615 evaluation board and its associated user manual, as the design includes the recommended differential I²C termination network, biasing resistors, decoupling capacitors, and EN pin connections that have been validated by NXP. Using the evaluation board schematic as a baseline is often the best approach when designing a custom PCA9615-based system, as it minimizes the risk of configuration or layout issues and follows the recommendations provided in the datasheet and application documentation. We suggest reviewing the evaluation board schematic and updating your design accordingly before committing to another PCB revision. https://www.nxp.com/products/interfaces/ic-spi-i3c-interface-devices/ic-i3c-bus-repeaters-buffers-and-extenders/pca9616pw-demo-board:OM13523UL Hope this helps!
View full article
Reinstalling the S32DS environment and SDK package has caused previous projects to fail to compile Reinstalling the S32DS environment and SDK package has caused previous projects to fail to compile. In the past, my project used S32DS V2.2 and SDK RTM 2.0.0. Now, after reinstallation, I am using S32DS.ARM.2018.R1 and have also installed SDK RTM 2.0.0. But now I can't compile the project. It seems that it can't recognize the project itself. You can see the details in the picture. Re: Reinstalling the S32DS environment and SDK package has caused previous projects to fail to compi Hi @yangcao1234  Please note that S32K1 SDK RTM 2.0.0 was released specifically for S32DS for ARM 2018.R1 Update 6. It was not intended to be used with S32DS for ARM 2.2, and compatibility with that version is not guaranteed. BR, VaneB
View full article
SL3S1206FUD2/HA Request for Good Die identification documentation / Wafer Map Dear Supplier, We would like to confirm whether you have provided any documentation or markings that distinguish “Good Die” from “NG Die” on the wafer. Specifically, we are looking for: A wafer map (indicating which die passed/failed testing), A test result report, or Physical markings on the wafer surface (e.g., ink dots, laser marks) that clearly identify usable die. After inspecting the wafer under our microscope, we could not find any visible physical markings. This raises concerns that we may not be able to reliably differentiate good die from defective die. Could you please help check whether such information was included with the shipment, or assist us in obtaining these materials from the manufacturer? We need this data for our subsequent processing steps. Thank you for your kind assistance. We look forward to your reply.
View full article
EasyEVSE 1060 to sigbrd2x interface issues This is a follow up to this post: https://community.nxp.com/t5/Power-Energy/EasyEVSE-signal-board-compatibility-and-availability/m-p/2384517 Short synopsis: I have a RT1060EVKB/Sigbrd2x EVSE, and a RT1064/Sigbrd2x EV running v5.0.8 software that I’m trying to stand up.  This was originally posted as a response to the question above, but I wasn’t sure whether the tech reps followed up on the thread responses. Thank you for your response.  I'm back working on this and am having issues getting EVSE code v5.0.8 that I got from NXP’s Git to work.  It builds fine and displays the GUI, but when I try to use its debug interface and request the version information, I get a correct response for the 1060 code of 5.0.8, but the version of the sigbrd2x shows as hw: v 255, and sw: v255.255.0.  I seem to recall reading a post somewhere that said there was some issue with a communications conflict with the LCD display on the 1060 board.  I can program the sigbrd2x and step code, so I'm pretty confident that that side is executing.  I'm using the EVSE-RT106X-CBL rather than the arduino headers.  My primary symptoms (besides the EV and EVSE sides not talking to each other) are the version reporting above that seems suspect, and I can't get past the "firmware download" status on the EVSE LCD, and the EVSE code on the 1060 won't start if the sigbrd2x is powered up (I'm powering them separately).  It feels like a communications issue.  Is there a patch / workaround for this?  If so, can you point me to documentation on how to resolve it? Best Regards, Chris Edwards Re: EasyEVSE 1060 to sigbrd2x interface issues Hi @chrisedwards , Thanks for your interest in NXP MIMXRT series! It seems the RT1060 is reading an idle/pulled-up SPI bus and getting no valid data back. This means the RT1060 ↔ Sigbrd2x SPI link never established — which also explains why the EVSE stays at "firmware download" and why the two sides don't talk. Suggested steps: - Scope the SPI lines (SCK/MOSI/MISO/CS). If MISO stays high, the board isn't responding → confirms the 0xFF. - Check the EVSE-RT106X-CBL wiring against the connector pinout in the signal-board manual — verify all SPI lines + GPIO are connected correctly. - LCD vs. SPI pin conflict: Temporarily disable the LCD and re-read the version to isolate it. - Follow the power-up order in the user guide, or power the host first. Best regards, Gavin Re: EasyEVSE 1060 to sigbrd2x interface issues Hi Gavin, Check sigboard’s qspi flash:               Powering the boards separately, I don’t see any traffic on the SPI pins of U17 (which is where I believe the switch gets its firmware).  I do see traffic on these pins on U17 of my EV setup (physically different board).  Check sigboard’s host interface SPI:               I don’t see any traffic on the spi pins of the host connector (19,21,23,24) when I have the 1060 powered and then apply power to the sigbrd2x (with the 1060 and sigbrd powered separately), nor when I power the sigbrd via the cable that goes to J32, with J2&J3 appropriately set). From digging into the User Guide (UG10140): I noticed that LEDs D18, D21, and D33 never illuminate.  They do on the sigbrd2x I have in my EV setup.  D24 does not illuminate on either setup.  D19 blinks. End state of debugging steps, after disabling the GUI: Ok with the LCD disabled by setting ENABLE_EVSE_UI to 0 in EVSE_config.h, the 1060 boots while connected to the sigbrd2x, using the cable that powers the sigbrd from J32 on the 1060, I can get a version number for the sigboard hw ( v2), and the sigboard sw v1.2.0.  Still no traffic on sigboard’s U17 nor illumination on LEDs D18, D21, 24, or D33.  D19 blinks.  Still no activity on the SPI pins on the sigboard’s host connector. So… progress, but it feels like the switch is not coming up at all. The user’s guide implies that the LEDs indicate that the switch isn’t working. Thanks and Best Regards,               Chris
View full article
In standby mode, the pins of the S32K328 cannot output a high level I followed the configuration steps in the operation manual to configure some GPIO pins of the S32K328 to maintain a high level in standby mode, but it failed. Below is my configuration process. I did not perform the fourth step recommended in the manual. Does this have an impact? I have performed similar configurations on the S32K312 before without any errors. My understanding is that, since I did not disable the pin keep function after reset, even if I configure the GPIO pins to output a low level after wake‑up, the output pin level should still maintain the high level that was set before entering standby mode. Currently, in actual measurements, the several GPIO pins configured in both standby mode and run mode have remained at a low level. Re: In standby mode, the pins of the S32K328 cannot output a high level Hi @hhggll23, I did not perform the fourth step recommended in the manual. Does this have an impact? Yes, it does. If you enable Pad Keeping before going to standby mode (write DCM_GPR->DCMRWF1[STANDBY_IO_CONFIG] = 0. Which is default register value no matter PKE of SIUL2 is set or not), but you did not disable it after wakeup, the SIUL2 module cannot be initialized again. If you don’t need the Pad Keeping function while the MCU needs to go to standby mode and wakeup, you need to write 1 to this bit anywhere and leave it alone. This is done through the Power_Ip_Init() API: Now, I/O pins retain their last set states in run mode during standby mode, regardless of Pad Keeping configuration. Since S32K3 will always perform a reset sequence after waking up, and since SIUL2 module resets the GPIO pads to its default state on a functional reset, pad keeping ensures that the pin can retain its state from wakeup until user unlock it. Are you trying to set all of the pins shown in the image to HIGH on Standby? Are all of them going LOW upon entering Standby? Or when exiting?  Best regards, Julián Re: In standby mode, the pins of the S32K328 cannot output a high level Thank you very much for your reply. I rechecked the program and found that after pulling the pins high before standby, an unintended routine ran that re‑initialized all GPIO pins, which caused the pins to remain at a low level during standby. After the modification, the GPIO pin levels have been successfully pulled high in standby mode. Now a new issue has arisen: after the GPIO pins are pulled high in standby mode, the standby current seems to have increased. Currently, under standby conditions, the quiescent current of the controller is about 3 mA with a 24 V supply. After troubleshooting other circuits, I suspect that the S32K328 consumes most of this current. At 24 V, 3 mA corresponds to about 14.4 mA when converted to the controller's 5 V supply. I have pulled high 8 GPIO pins in standby mode. Is this standby current normal? To address this issue, can I configure the GPIO pins of the S32K328 as high‑impedance in standby mode, so that an external pull‑up resistor can maintain the high level on the pins during standby?
View full article
GPIO Based on the S32K324 MCU, how to configure a GPIO to high‑impedance state using S32DS. Re: GPIO Hi Please refer to previous similar discussions: S32K3 GPIO HIGH-Z If the pin may have previously enabled internal pull, in order to satisfy the tristate definition in S32K3XXRM, Siul2_Port_Ip_SetPullSel(..., PORT_INTERNAL_PULL_NOT_ENABLED) should be called to ensure PUE=0; Best Regards, Robin
View full article
Query Regarding PCA9450CHN Voltage Configuration Through I2C We are using the PCA9450CHN PMIC and understand that it powers up with default regulator voltages, which can be modified through I2C programming. Could you please explain the complete sequence for changing these voltages after power-on, including when the SoC starts communicating with the PMIC? Also, please let us know the recommended debugger or tools to monitor and verify the PMIC register programming and voltage changes. Board Design HW-Open-Source Re: Query Regarding PCA9450CHN Voltage Configuration Through I2C You can refer to above after the POR_B signal pull high and the PCA9450C enter into RUN mode you can change its power rails output value.
View full article
S32K566 LPUART Communication Issue Hi, I am using the Uart_Example_S32K566_M7 module on the S32K566 microcontroller with an LPUART module clock of 50 MHz. I configured the baud rate to 115200 and am sending 0xAA data to the PC using a UART-to-USB converter. However, the received data is incorrect (0x00 0x80 0x80). When I configure the baud rate to 115200/8 = 14400, the data is received correctly. I also tried different baud rates such as 9600 and 19200. I am using S32DS 3.6.6 and SDK 0.8.0. Uart_Example_S32K566_M7 source code also attached here please find.  I have attached the configuration and received data screenshots for reference. Receiver terminal window baud rate is 115200: Receiver terminal window baud rate is 14400: Re: S32K566 LPUART Communication Issue Hello @Manikandan_Aruchamy , I hope this email finds you well. I am writing to you in regard to a product currently in your possession – an NPI (New Product Introduction) which has not been officially launched yet. Please be advised that customers who have been granted early access to such products have assigned their field engineers. Your designated field engineer should serve as your primary support channel for any issues, concerns or queries you may have about this product. Our online support team will be opening a wider range of support for this product once it has been officially released. Until then, we will not be equipped to provide the desired assistance. Thank you for your understanding. Best regards, Pavel
View full article