我对 MM9ZJ638 的睡眠唤醒功能有疑问 各位大佬好，我遇到一个关于MM9ZJ638的Sleep唤醒的问题，主要跟can模块的Sleep有关。通过手册发现，CAN Sleep模块在写入CANCTL0的SLPRQ位并等待CAN模块检查发送和接收完成之后，可以自动进入睡眠模式。可以通过读取 CANCTL1 的 SLPAK 位来确认 CANCTL1 的 SLPAK 位。在测试中发现我的控制板在Busoff状态时，设置CANCTL0的SLPRQ位后，CAN模块的CANCTL1的SLPAK位一直处于0状态，并没有更新到睡眠状态。我应该检查哪些寄存器配置以确保我可以在 Busoff 状态下睡眠？请帮帮我，谢谢！ 回复：我有一个关于 MM9ZJ638 睡眠唤醒的问题 按照你的想法，我解决了问题，谢谢

如何将 MM9Z1I638 设置为安全模式，我需要帮助，谢谢 我对使用MM9Z1I638打开安全模式有疑问。看了手册，知道了FSEC寄存器是用来打开安全模式的，但是这个寄存器好像不支持直接写，需要通过FLASH编程来写入。写入的地址段为P_FLASH块的0xFF_FE0F字节，支持的最小扇区大小 P_FLASH为512字节。我按照擦除扇区、校验扇区、写入扇区的流程写入字节，但是发现每次擦除扇区之后软件都会运行到非法的地方。检查后发现，这个扇区存储的所有信息都是地址 电池传感器 Re: HOW CAN set MM9Z1I638 to safe mode ,i need help,THANKS 这个是一个流程我建议您看下面的帖子： I have a question about using MM9Z1I638 to open the safe mode - NXP Community Re: HOW CAN set MM9Z1I638 to safe mode ,i need help,THANKS 我看了6.14.5里面的安全字节描述，上面写的是在下一次复位以后，会使用0xFF_FE0F地址的值来初始化FSEC寄存器，我现在的问题是如何对0XFF_FE0F这个地址写入值，我之前用上面描述的方法进行扇区擦除后，值通过单步调试的方法能检测到0XFF_FE0F地址的值进行了更改，但是随后运行，通过调试器的数据分析，软件就跳转到了非法的位置，所以我想问问正常的编写这个地址的流程是怎么样的，谢谢 Re: HOW CAN set MM9Z1I638 to safe mode ,i need help,THANKS Hi SHAOWEN 您说的是security吧？ 如果是的话请仔细阅读datasheet page 403：6.14.5 Security，里面有详细的介绍

IMX8QXP jpeg decoder Hi, We are experiencing an issue with the JPEG encoder on our IMX8QXP (var-som) system. We are using Yocto Scarthgap and require the encoder to convert JPEG images to raw NV12 or BGR24 formats. Currently, we are only receiving YUV444 (YUV3) output. Previously, with Yocto Sumo, we were able to obtain NV12 output successfully. The mxc-jpeg device driver appears to support multiple output formats, including BGR24, NV12, and NV12M. Furthermore, the command #v4l2-ctl --list-formats-ext -d /dev/video2 lists 13 compatible output types. We would appreciate assistance in understanding the specific requirements necessary to achieve NV12 or BGR24 output from the driver. A simplified version of our C code is attached for your reference. Sincerely, //Saber Re: IMX8QXP jpeg decoder "8QXP JPEG decoder only support such case of RGB format, for example if the input jpeg is encoding use RGB color space, then JPEG decoder output is RGB fmt; But if input jpeg is encoding use YUV color space, then output still is YUV fmt.If customer must use input YUV JPEG , but output need RGB fmt, suggest customer use hardware video convert, such as imxvideoconvert, other than software video convert." Re: IMX8QXP jpeg decoder Hi, Would you please try RGB or BGR? Regards, Saber Re: IMX8QXP jpeg decoder couldn't reproduce this on nxp board with official bsp I didnot reproduce any issue, below is cmd for make v4l2jpegdec plugin output fmt is NV12. root@imx8qxpc0mek:~# cat /proc/version Linux version 6.6.23-lts-next-06236-gb586a521770e (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 13.2.0, GNU ld (GNU Binutils) 2.42.0.20240216) #1 SMP PREEMPT Fri Jun 7 13:15:57 UTC 2024 root@imx8qxpc0mek:~# gst-launch-1.0 filesrc location=/root/thumbnail_image004.jpg ! jpegparse ! v4l2jpegdec ! "video/x-raw,format=NV12" ! filesink location=dmp.nv12 Setting pipeline to PAUSED ... ====== V4L2DEC: 1.24.0 build on May 6 2024 08:51:28. ====== Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... Redistribute latency... New clock: GstSystemClock Got EOS from element "pipeline0". Execution ended after 0:00:00.007471000 Setting pipeline to NULL ... Freeing pipeline . Re: IMX8QXP jpeg decoder My main question is, how do we get RGB (or BGR) out of decoder! Re: IMX8QXP jpeg decoder Yes, you are correct. Our product has Sumo right now and it can convert JPEG to NV12. However, with Scarthgap (kernel 6.6.23) the only output we get is YUV444, despite of whatever we configure the decoder. I have attached two images we are using for test.  Re: IMX8QXP jpeg decoder what format of your jpg source is? do you mean you can output nv12 on Yocto Sumo using the same command, right? if yes pls send your jpg file to me, and I checked the source code, it seems can support different format as output linux-imx/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c at lf-6.6.y · nxp-imx/linux-imx Re: IMX8QXP jpeg decoder Hi, Thanks for your replay. I have attached the output from gstreamer. I used the command below, as you can see in the logs, gstreamer uses HW JPEG coder to convert the input image to V308 (YUV444) and then converts YUV444 to RGB using software. # GST_DEBUG=3 gst-launch-1.0 -v filesrc location=/ANPR/DPRGremlin1080p.jpg ! jpegparse ! v4l2jpegdec capture-io-mode=dmabuf ! videoconvert ! video/x-raw,format=RGB ! filesink location=output.rgb I have also used the example code from https://github.com/nxp-imx/imx-test/tree/lf-6.6.23_2.0.0/test/mxc_jpeg_test It seems like, when we want to use ioctl and VIDIOC_STREAMON, then the output format changes to YUV444. Re: IMX8QXP jpeg decoder did you test the gstreamer with jpeg encoder on the imx8qxp? do you have any log or print information to share?

Unsecure for mc9s12xd64? Hello, I'm trying to write the mc9s12xd64 with the PEMicro USB Multilink Rev.D and CodeWarrior 5.1. When I try to unsecure the micro, the program shows me this message. "Derivative could NOT be unsecured!!!! The Unsecure command file might be missing or disabled. Make sure the command file defined in the Unsecure panel of the Command File dialog contains the correct commands to unsecure the current connected derivative and the board oscillator frequency." I also use CodeWarrior 5.2 for other micros and this haven't happened in version 5.2. Could you help me? Do I need a driver or a package for this? Thank you for the help.  Re: Unsecure for mc9s12xd64? HI JesusCordoba， If your problem is because of unsecure, you have to do the following: once the Hi-Wave is open, click on "P&E Multilink/Cyclone Pro" and then click on the "Unsecure" option. This will execute the command file designed to unsecure the microcontroller. All the flash of the device will be erased and the security byte will be set to the Unsecure status (1:0 in the security bits). If this does not work, I suggest you checking P&E tools. Click on the support link and then Downloads and Documentation. Select “Utility” as the Download Type and HC(S)12 as the Product Family. On the available downloads( http://www.pemicro.com/support/download_processor.cfm ) look for the Unsecure12 Utility, download it and install it. This software will allow you to unsecure the S12 derivatives we have. Hope this helps, Jun Zhang

请问GUI-Guider自带的Meter控件的刻度数字颜色是否单独可调？ 请问GUI-Guider自带的Meter控件的刻度数字颜色是否单独可调？我把表盘的背景改为白色，刻度改为红色，但刻度的数字颜色无法改变。这种情况下无法显示刻度数字。

MM9ZJ638のスリープウェイクアップについて問題があります こんにちは、大物、私は主に缶モジュールのスリープに関連するMM9ZJ638のスリープウェイクアップについて問題があります。マニュアルを通じて、CAN Sleepモジュールは、SLPRQビットのCANCTL0を書き込んでCANモジュールが送受信の完了を確認するのを待った後、自動的にスリープモードに入ることができることがわかりました。CANCTL1のSLPAKビットは、CANCTL1のSLPAKビットを読み取ることで確認できます。テストでは、コントロールボードがBusoff状態のとき、SLPRQビットのCANCTL0を設定した後、CANモジュールのSLPAKビットのCANCTL1が常に0状態になり、スリープ状態に更新されないことがわかりました。Busoff 状態でスリープできることを確認するには、どのレジスタ コンフィギュレーションを確認する必要がありますか。私を助けてください、ありがとう! Re:MM9ZJ638の睡眠の目覚めについて問題があります あなたの考えによると、私は問題を解決しました、ありがとう

コード内のエラーまたはある種の非互換性? HvBms400_775_722_TPL_Bring_Upの例を開くときにエラーが表示されました。 Automotive Package Managerバージョン2024.01がダウンロードされ、開発パッケージがダウンロードされ、そこにあるはずのものすべてがそこにありました。

Error : undefined identifier 'class' I'm starting a new project in CodeWarrior IDE version 5.7.0 Build 2264. I keep getting this message upon trying to build with make. It doesn't recognize my c++ code. How do I resolve this? Re: Error : undefined identifier 'class' I discovered that my license is supposed to give me all the c++ features and that my license needed to be upgraded. I consider this issue to be resolved and closed. Thank you for replying. Re: Error : undefined identifier 'class' I discovered that my problem is that my license is supposed to give me all the c++ features and my license needed to be upgraded. Thank you for replying. I consider this issue resolved and closed. Re: Error : undefined identifier 'class' Hi ShannonMt  What's your chip part number? Jun Zhang

GoldVIP-S32G 添加 eth 模块后 memmap 问题 使用 eb tresos 29.2.0 打开 GoldVIP-S32G3-1.11.0，添加模块配置中的 Eth 模块。然后配置tsn相关的功能并生成项目。 这时编译代码时总是提示缺少头文件“Eth_MemMap.h”。 我知道我需要为 Eth 模块配置 memmap。但我不知道该怎么做。 回复：在 GoldVIP-S32G 中添加 eth 模块后出现 memmap 问题 非常感谢您的回复！ 问题已解决。具体操作如下： 1.添加Eth模块并配置相关配置。 2. 构建项目 -> generate_swcd 3. Im-and 导出器 -> Imp_Swcd -> 运行导入器 4. EcuExtractCreator 5. SvcAs_Trigger 6. 生成项目 回复：在 GoldVIP-S32G 中添加 eth 模块后出现 memmap 问题 非常感谢您的回复。 一.根据文档（ Eth_TS_T40D11M40I2R0\doc\RTD_ETH_IM.pdf）的解释，添加Eth模块后，并没有说明Eth_Memmap.h是如何生成的。我觉得这个不是手动写的，应该是编译生成的。 二.添加Eth模块后，我根据这个文档GoldVIP-S32G3-1.11.0\documentation\GoldVIP-User-Manual.pdf \14.4 Building the M7 Application编译了GoldVIP-S32G3-1.11.0\realtime\s32g399ardb3\can-gw。不知道我的编译方法是否有问题。

[iMX8QM-MEK] Unable to change firmware on M4 core - remote core state attached Hey, I am attempting to change the firmware that is running on one of the M4 cores of the iMX8QM-MEK by using an .elf file compiled using MCUXpresso IDE. I have copied both the .elf file and the .bin file to the boot SD and configured U-boot to load the .bin image to the M4 core by changing: => print m4_0_image m4_0_image=hello_world_m40.bin I am running into some peculiar issues regarding the remote core in both U-boot and the kernel. First of all, it seems that this power mode switching task runs before U-boot prints its first lines to the console, which might indicate that something is happening in SFCW. In U-boot, when I Interrupt auto-boot and run the booting script, I get the following: => print m4boot_0 m4boot_0=run loadm4image_0; dcache flush; bootaux ${loadaddr} 0 => print loadm4image_0 loadm4image_0=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${m4_0_image} => run m4boot_0 14800 bytes read in 10 ms (1.4 MiB/s) ## Auxiliary core is already up  And when I boot into the kernel and read the state of remoteproc0 I get the following state, which disallows me from loading any firmware to the core, or stopping the core: root@imx8qmmek:~# cat /sys/class/remoteproc/remoteproc0/state attached root@imx8qmmek:~# echo stop > /sys/class/remoteproc/remoteproc0/state [ 84.896858] imx-rproc imx8qm-cm4-0: Failed to stop remote core [ 84.902759] remoteproc remoteproc0: can't stop rproc: -13 -sh: echo: write error: Permission denied Looking at dmesg yields: root@imx8qmmek:~# dmesg | grep rproc [ 3.022630] remoteproc remoteproc0: imx-rproc is available [ 3.031813] remoteproc remoteproc0: attaching to imx-rproc [ 3.043022] rproc-virtio rproc-virtio.1.auto: assigned reserved memory node vdevbuffer@90400000 [ 3.057679] rproc-virtio rproc-virtio.1.auto: registered virtio0 (type 7) [ 3.064485] rproc-virtio rproc-virtio.2.auto: assigned reserved memory node vdevbuffer@90400000 [ 3.085832] rproc-virtio rproc-virtio.2.auto: registered virtio1 (type 7) [ 3.092648] remoteproc remoteproc0: remote processor imx-rproc is now attached [ 3.101451] remoteproc remoteproc1: imx-rproc is available [ 3.107032] remoteproc remoteproc1: attaching to imx-rproc [ 3.113075] rproc-virtio rproc-virtio.3.auto: assigned reserved memory node vdevbuffer@90400000 [ 3.127700] rproc-virtio rproc-virtio.3.auto: registered virtio2 (type 7) [ 3.141984] rproc-virtio rproc-virtio.4.auto: assigned reserved memory node vdevbuffer@90400000 [ 3.163620] rproc-virtio rproc-virtio.4.auto: registered virtio3 (type 7) [ 3.177037] remoteproc remoteproc1: remote processor imx-rproc is now attached  I'm not sure how to stop the remote core so that I can swap the firmware in the linux kernel instead of via U-boot, and I cannot find any information on the attached state for remoteproc. If it's not possible to stop the core in U-boot, and only start it, how can I prevent whatever process runs before U-boot from starting the core, so that I can start it in U-boot or in the kernel? I built my bootable .wic file using Yocto poky 5.0.4 scarthgap. --- U-Boot info --- U-Boot SPL 2024.04-lf_v2024.04+g6c4545203d1+p0 (Nov 15 2024 - 04:02:13 +0000) Normal Boot Trying to boot from MMC2_2 Primary set selected Load image from MMC/SD 0x7c800 U-Boot 2024.04-lf_v2024.04+g6c4545203d1+p0 (Nov 15 2024 - 04:02:13 +0000) CPU: NXP i.MX8QM RevB A53 at 1200 MHz at 26C Model: NXP i.MX8QM MEK Board: iMX8QM MEK Boot: SD1 Reset cause: POR DRAM: 5.8 GiB TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x51] Core: 188 devices, 32 uclasses, devicetree: separate MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from MMC... OK [*]-Video Link 0it6263_i2c_reg_read, read err 3 faill to read from it6263 revision, ret 3 (1280 x 720) [0] dpu@56180000, video [1] lvds-channel@0, display [2] lvds-to-hdmi-bridge@4c, video_bridge In: serial Out: serial Err: serial BuildInfo: - SCFW 83624b99, SECO-FW 7d5462e6, IMX-MKIMAGE 71b8c18a, ATF android - U-Boot 2024.04-lf_v2024.04+g6c4545203d1+p0 switch to partitions #0, OK mmc1 is current device flash target is MMC:1 Net: eth0: ethernet@5b040000 [PRIME]Could not get PHY for FEC1: addr 1 Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 => bdinfo boot_params = 0x0000000000000000 DRAM bank = 0x0000000000000000 -> start = 0x0000000080200000 -> size = 0x0000000007e00000 DRAM bank = 0x0000000000000001 -> start = 0x0000000092000000 -> size = 0x000000006c000000 DRAM bank = 0x0000000000000002 -> start = 0x0000000880000000 -> size = 0x0000000100000000 flashstart = 0x0000000000000000 flashsize = 0x0000000000000000 flashoffset = 0x0000000000000000 baudrate = 115200 bps relocaddr = 0x0000000087627000 reloc off = 0x0000000007607000 Build = 64-bit current eth = ethernet@5b040000 ethaddr = 00:04:9f:06:5e:76 IP addr = fdt_blob = 0x0000000085215210 new_fdt = 0x0000000085215210 fdt_size = 0x0000000000011b20 Video = dpu@56180000 active FB base = 0x0000000087700000 FB size = 1280x720x32 lmb_dump_all: memory.cnt = 0x3 / max = 0x10 memory[0] [0x80200000-0x87ffffff], 0x07e00000 bytes flags: 0 memory[1] [0x92000000-0xfdffffff], 0x6c000000 bytes flags: 0 memory[2] [0x880000000-0x97fffffff], 0x100000000 bytes flags: 0 reserved.cnt = 0x2 / max = 0x10 reserved[0] [0x85210ba0-0x87ffffff], 0x02def460 bytes flags: 0 reserved[1] [0x90000000-0x91ffffff], 0x02000000 bytes flags: 4 devicetree = separate arch_number = 0x0000000000000000 TLB addr = 0x0000000087f50000 irq_sp = 0x0000000085215200 sp start = 0x0000000085215200 Early malloc usage: 28e0 / 8000 --- Kernel info --- root@imx8qmmek:~# uname -a Linux imx8qmmek 6.6.52-lts-next-ge0f9e2afd4cf #1 SMP PREEMPT Tue Nov 19 23:01:49 UTC 2024 aarch64 GNU/Linux i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Linux Re: [iMX8QM-MEK] Unable to change firmware on M4 core - remote core state attached Okay, I found a solution which works for me. (assume root folder is the cloned git repo - so the parent folder of build- ) I modified the following 3 files to force Yocto to build the image using "flash_spl" instead of "flash_linux_m4", as defined in soc.mak in both the imx-mkimage tool and in ./build- /tmp/deploy/images/ /imx-boot-tools/soc.mak: in ./sources/meta-freescale/recipes-bsp/imx-mkimage/imx-boot_1.0.bb - change line 230 from flash_linux_m4 to flash_spl in ./sources/meta-imx/meta-imx-bsp/recipes-bsp/imx-mkimage/imx-boot_1.0.bb - change line 230 from flash_linux_m4 to flash_spl in ./sources/meta-imx/meta-imx-bsp/conf/layer.conf - change line 308 from flash_linux_m4 to flash_spl After rebuilding the image in bitbake, flash the newly generated .wic file to an SD card. Verify if the boot-imx symlink in ./build- /deploy/images/ points to a file ending in flash_spl. Then, in U-boot, make sure that the environment variable fdt_file= .dtb so not -rpmesg.dtb, since this causes strange bootloops. After booting in the kernel, check whether rpmsg_char and rpmsg_ctrl are loaded using $ lsmod If they are not loaded, you can either load them manually using insmod or modprobe, or you can load them on boot using files like /etc/rc.local As a final check, you can call $ cat /sys/class/remoteproc/remoteproc?/state to verify if the remote cores are offline. Following these steps allowed me to finally load my own .elf files to the remote cores, without shutting off the device. Re: [iMX8QM-MEK] Unable to change firmware on M4 core - remote core state attached Hello @Chavira  After a more thorough investigation it seems like my Yocto build automatically bakes the "Power mode task" into the final boot-imx binary after running bitbake imx-image-core, which is then eventually flashed to an SD card. This pretty much exhibits the same behaviour as if I were to use imx-mkimage tool to make a flash.bin containing the firmware for an M4 core and flash this bin to the SD card (following the instructions mentioned in MCUXpresso ch 6.1). Perhaps the better question on my end is to ask how I can let the M4 cores boot without also flashing firmware to them before U-boot is loaded, so hopefully the kernel can take ownership of the cores instead of attaching to them. Anyway, I tried again with exactly the same results. As far as I know, I am compiling for TCM and not for DDR or anything of the sorts. I am using Yocto 5.0 (scarthgap) to create a .wic image that is flashed to an SD card, from which the board boots. To build the bootable image, I did the following steps: 1. Cloned the following repo and synced it repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml 2. Set up the build environment as follows: MACHINE=imx8qmmek DISTRO=fsl-imx-wayland source ./imx-setup-release.sh -b build-imx8qmmek 3. built core image bitbake imx-image-core 4. built SDK for this core image bitbake -c populate_sdk imx-image-core The .wic image is too large to attach however I will attach the project that I intend to load to the cores instead. Re: [iMX8QM-MEK] Unable to change firmware on M4 core - remote core state attached Hi @ChrisC05! Thank you for contacting NXP Support! I am not having the same issues by my side! That are my log file. root@imx8qmmek:~# cat /sys/class/remoteproc/remoteproc0/state offline root@imx8qmmek:~# echo -n /lib/firmware/imx8qx_m4_TCM_hello_world.elf > /sys/class/remoteproc/remoteproc0/firmware root@imx8qmmek:~# echo start > /sys/class/remoteproc/remoteproc0/state [ 48.826504] remoteproc remoteproc0: powering up imx-rproc [ 48.832113] remoteproc remoteproc0: Direct firmware load for /lib/firmware/imx8qx_m4_TCM_hello_world.elf failed with error -2 [ 48.843484] remoteproc remoteproc0: Falling back to sysfs fallback for: /lib/firmware/imx8qx_m4_TCM_hello_world.elf [ 48.857911] remoteproc remoteproc0: Booting fw image /lib/firmware/imx8qx_m4_TCM_hello_world.elf, size 170108 [ 48.868149] remoteproc remoteproc0: remote processor imx-rproc is now up root@imx8qmmek:~# echo stop > /sys/class/remoteproc/remoteproc0/state [ 55.686720] remoteproc remoteproc0: stopped remote processor imx-rproc root@imx8qmmek:~# echo start > /sys/class/remoteproc/remoteproc0/state [ 57.262522] remoteproc remoteproc0: powering up imx-rproc [ 57.268094] remoteproc remoteproc0: Direct firmware load for /lib/firmware/imx8qx_m4_TCM_hello_world.elf failed with error -2 [ 57.279475] remoteproc remoteproc0: Falling back to sysfs fallback for: /lib/firmware/imx8qx_m4_TCM_hello_world.elf [ 57.291340] remoteproc remoteproc0: Booting fw image /lib/firmware/imx8qx_m4_TCM_hello_world.elf, size 170108 [ 57.301833] remoteproc remoteproc0: remote processor imx-rproc is now up root@imx8qmmek:~# echo stop > /sys/class/remoteproc/remoteproc0/state [ 58.654715] remoteproc remoteproc0: stopped remote processor imx-rproc root@imx8qmmek:~# echo start > /sys/class/remoteproc/remoteproc0/state [ 62.362524] remoteproc remoteproc0: powering up imx-rproc [ 62.368089] remoteproc remoteproc0: Direct firmware load for /lib/firmware/imx8qx_m4_TCM_hello_world.elf failed with error -2 [ 62.380199] remoteproc remoteproc0: Falling back to sysfs fallback for: /lib/firmware/imx8qx_m4_TCM_hello_world.elf [ 62.391978] remoteproc remoteproc0: Booting fw image /lib/firmware/imx8qx_m4_TCM_hello_world.elf, size 170108 [ 62.402415] remoteproc remoteproc0: remote processor imx-rproc is now up root@imx8qmmek:~# echo stop > /sys/class/remoteproc/remoteproc0/state [ 63.854715] remoteproc remoteproc0: stopped remote processor imx-rproc root@imx8qmmek:~# echo start > /sys/class/remoteproc/remoteproc0/state [ 71.054540] remoteproc remoteproc0: powering up imx-rproc [ 71.060119] remoteproc remoteproc0: Direct firmware load for /lib/firmware/imx8qx_m4_TCM_hello_world.elf failed with error -2 [ 71.071486] remoteproc remoteproc0: Falling back to sysfs fallback for: /lib/firmware/imx8qx_m4_TCM_hello_world.elf [ 71.083307] remoteproc remoteproc0: Booting fw image /lib/firmware/imx8qx_m4_TCM_hello_world.elf, size 170108 [ 71.093741] remoteproc remoteproc0: remote processor imx-rproc is now up root@imx8qmmek:~# echo stop > /sys/class/remoteproc/remoteproc0/state [ 72.106732] remoteproc remoteproc0: stopped remote processor imx-rproc root@imx8qmmek:~# dmesg | grep rproc [ 3.138247] remoteproc remoteproc0: imx-rproc is available [ 13.009374] remoteproc remoteproc1: imx-dsp-rproc is available [ 48.826504] remoteproc remoteproc0: powering up imx-rproc [ 48.868149] remoteproc remoteproc0: remote processor imx-rproc is now up [ 55.686720] remoteproc remoteproc0: stopped remote processor imx-rproc [ 57.262522] remoteproc remoteproc0: powering up imx-rproc [ 57.301833] remoteproc remoteproc0: remote processor imx-rproc is now up [ 58.654715] remoteproc remoteproc0: stopped remote processor imx-rproc [ 62.362524] remoteproc remoteproc0: powering up imx-rproc [ 62.402415] remoteproc remoteproc0: remote processor imx-rproc is now up [ 63.854715] remoteproc remoteproc0: stopped remote processor imx-rproc [ 71.054540] remoteproc remoteproc0: powering up imx-rproc [ 71.093741] remoteproc remoteproc0: remote processor imx-rproc is now up [ 72.106732] remoteproc remoteproc0: stopped remote processor imx-rproc root@imx8qmmek:~# uname -a Linux imx8qmmek 6.6.52-lts-next-ge0f9e2afd4cf #1 SMP PREEMPT Tue Nov 19 23:01:49 UTC 2024 aarch64 GNU/Linux root@imx8qmmek:~# I am using the hello_world.bin in u-boot and using the hello_world.elf in Linux. Can you try again? Are you compiling for TCM? Can you share your project/binary that are you using? Best Regards! Chavira

S32K344 MRCANHUBK344 QSPI Example Timeout Hello, I’m currently testing the Qspi_Ip_Example_S32K344 on the MRCANHUBK344 developer board. The example project uses an MX25L6433FM2R-08G flash device, whereas the CANHUB board is equipped with an MX25L6433FM2I-08G. I believe there isn’t any major difference in configuration between these two flash models, and the QSPI pin definitions in the example also seem to match the MRCANHUBK344 QSPI interface. However, I’m running into an issue where Qspi_Ip_Init returns STATUS_QSPI_IP_BUSY. Everything appears normal until Qspi_Ip_InitProtection is called inside Qspi_Ip_Init, at which point Qspi_Ip_WaitCommandComplete also returns STATUS_QSPI_IP_BUSY (as shown in the attached image). I’ve come across a similar issue in this forum post: initial QSPI will be timeout on S32K344 EVB  I’m using S32 Design Studio 3.6 and RTD R21-11 Version 5.0.0. Could anyone advise me on the steps to resolve or further diagnose this issue? Thank you in advance for your help Re: S32K344 MRCANHUBK344 QSPI Example Timeout Hi, I tried the configurations you mentioned and successfully ran the example. Thank you. Re: S32K344 MRCANHUBK344 QSPI Example Timeout Hi, I was able to pass init and run code when lowering QSPI_SFCK Also slowing down signal edges helps with example default SFCK (80MHz) Most probably there is some issue with HW design or similar. BR, Petr   Re: S32K344 MRCANHUBK344 QSPI Example Timeout Hi, devices are the same, there is just temp range difference. Pins setting looks correct and matches with schematic, as you wrote. You can check in debugger if respective SIUL registers are written that way. Let me check this RTD demo in MRCANHUBK344 as well. BR, Petr

Question about running hello world in CM7 on imx8mp-evk Ok, so that question might seem very basic, I'm wracking my brain as to why it doesn't work, but here it goes: I'm trying to run the basic hello world in the CM7 on a imx8mp-evk. Release 6.6.52. In u-boot: u-boot=> setenv fdtfile 'imx8mp-evk-rpmsg.dtb'; u-boot=>boot [device boots, I enter login] imx8mpevk login: root root@imx8mpevk:~# echo -n /lib/firmware/ > /sys/module/firmware_class/parameters/path root@imx8mpevk:~# echo -n imx8mp_m7_TCM_hello_world.elf > /sys/devices/platform/imx8mp-cm7/remoteproc/remoteproc0/firmware root@imx8mpevk:~# echo start > /sys/devices/platform/imx8mp-cm7/remoteproc/remoteproc0/state And then, Linux hangs. No "hello world" in any console (should be in console 4, which is COM8 for me, but I got all 4 open just to make sure). What am I doing wrong here? i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Question about running hello world in CM7 on imx8mp-evk It works! Thank you! Re: Question about running hello world in CM7 on imx8mp-evk Hello, Need more command in u-boot: u-boot=> setenv fdtfile 'imx8mp-evk-rpmsg.dtb'; run prepare_mcore u-boot=>boot Best Regards, Zhiming

GoldVIP-S32Gにethモジュールを追加した後のmemmapの問題 EB tresos 32.2.0を使用してGoldVIP-S32G29.2.0を開き、追加しますモジュール構成の Eth モジュール。次に、tsnに関連する関数を設定し、プロジェクトを生成します。 このとき、コードをコンパイルすると、ヘッダー ファイル "Eth_MemMap.h" が見つからないことが常に確認されます。 私はEthモジュールのmemmapを設定する必要があることを知っています。しかし、私はそれを行う方法を知りません。 Re:GoldVIP-S32Gにethモジュールを追加した後のmemmapの問題 お返事ありがとうございます! 問題は解決しました。方法は次のとおりです。 1. Eth モジュールを追加し、設定を行います。 2. プロジェクトのビルド -> generate_swcd 3. IMおよび輸出業者-> Imp_Swcd -> Run Importer 4.エクエキスクリエーター 5. SvcAs_Trigger 6. プロジェクトの生成 Re:GoldVIP-S32Gにethモジュールを追加した後のmemmapの問題 この度はお返事をいただき、誠にありがとうございました。 一.ドキュメント(Eth_TS_T40D11M40I2R0\doc\RTD_ETH_IM.pdf)に従って説明すると、Ethモジュールを追加した後、Eth_Memmap.hがどのように生成されるかの説明はありません。これは手動で書かれているのではなく、コンパイルして生成する必要があると思います。 二.Ethモジュールを追加した後、このドキュメントに基づいてGoldVIP-S32G3-1.11.0\realtime\s32g399ardb3\can-gwをコンパイルします。GoldVIP-S32G3-1.11.0\documentation\GoldVIP-User-Manual.pdf \14.4 M7アプリケーションのビルド。コンパイル方法に何か問題があるかどうかわかりません。

PF5020 OTP Settings for S32G3 EVK & Goldbox Are the settings for the PF5020 OTP used on the S32G3 EVK and Goldbox available? What about the other PMICs on the board? Re: PF5020 OTP Settings for S32G3 EVK & Goldbox Hi, Overall, all configuration reports should be available under the product specific page (i.e. VR5510: VR5510 | Multi-Channel PMIC for Automotive Applications | NXP Semiconductors), either under the public or Secure Files option. On regards of the PF5020 P/N under the S32G3 Reference Boards, we are not seeing any information. For this, we can recommend opening a ticket under the NXP online services for further support. We do apologize. Please, let us know.

error within code or some kind of incompatibility? I received an error when opening the HvBms400_775_722_TPL_Bring_Up example.  Automotive package manager version 2024.01 was downloaded, the development package was downloaded, everything that should have been there was there.  Re: error within code or some kind of incompatibility? Hi Please install SW32K3_RTD_4.4_R21-11_3.0.0_D2303 by refer to HOWTO: offline install S32K3 RTD 3.0.0 in S32DS v3.5 Best Regards, Robin ------------------------------------------------------------------------------- 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. -------------------------------------------------------------------------------

S32K344 Flash Memory Erase Cycles life   #define FLS_MASTER_ID                0U #define FLS_BUF_SIZE                 80U #define FLS_SECTOR_ADDR              0x00600000U #define FLS_SECTOR_TEST              C40_CODE_ARRAY_0_BLOCK_2_S256    void FlashWrite()  {      /* Unlock sector if needed */     if (STATUS_C40_IP_SECTOR_PROTECTED == C40_Ip_GetLock(FLS_SECTOR_TEST))     {         C40_Ip_ClearLock(FLS_SECTOR_TEST, FLS_MASTER_ID);     }       /* Erase sector */     C40_Ip_MainInterfaceSectorErase(FLS_SECTOR_TEST, FLS_MASTER_ID);     do     {         C40Status = C40_Ip_MainInterfaceSectorEraseStatus();     }     while (STATUS_C40_IP_BUSY == C40Status);     /* Check job result */     Fls_ExampleAssert(STATUS_C40_IP_SUCCESS == C40Status);       /* Write data */     C40_Ip_MainInterfaceWrite(FLS_SECTOR_ADDR, FLS_BUF_SIZE, TxBuffer, FLS_MASTER_ID);     do     {         C40Status = C40_Ip_MainInterfaceWriteStatus();     }     while (STATUS_C40_IP_BUSY == C40Status);     /* Check job result */     Fls_ExampleAssert(STATUS_C40_IP_SUCCESS == C40Status);       /* Compare the data in memory with TxBuffer */     C40Status = C40_Ip_Compare(FLS_SECTOR_ADDR, FLS_BUF_SIZE, TxBuffer);     /* Check job result */     Fls_ExampleAssert(STATUS_C40_IP_SUCCESS == C40Status);      }   I am Calling this function FlashWrite() for every 1 Minute and MCU is working 24HRs so considering that how much flash memory life i'll get. Also let me know how to calculate it?   S32K344-WB   Re: S32K344 Flash Memory Erase Cycles life Dear  @lukaszadrapa and @narsimh_kamath  Thanks for the detailed information and calculations. This is what i was looking for. Re: S32K344 Flash Memory Erase Cycles life Thank you @lukaszadrapa  The simplified calculation & insight you offer is very helpful! It does look like if the interval for writing 32B data were increased from 'every 1 min' to ' every 2 min' , then certainly the desired EEPROM emulation can be achieved with a 15 year lifetime. Would you agree? Re: S32K344 Flash Memory Erase Cycles life There's 128KB of data flash. Even if I do not consider any overhead caused by Emulated EEPROM mechanism: "data flash size" / "user data" = 128KB / 2KB = 64 updates So, the data flash will be full just after 64 updates. We can perform 100,000 cycles on data flash, so it will gives us 6,400,000 updates. Doing this every 1 minute for 24 hours a day for 15 years: 6,400,000 / 60 / 24 / 365 = 12 years But that's ideal situation without any EEE overhead. Fee needs additional data in flash, so it will be less than 12 years. If you add additional 1MB from code flash: 1024KB / 2KB = 512 updates We can perform 1000 cycles on code flash: 512,000 updates 512,000 / 60 / 24 / 365 = 1 year So, this also does not make a difference. If you want to know the endurance exactly (with EEE overhead), you can find section "3.6.9 Endurance calculation" in Fee user manual. c:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32K3\RTD\Fee_TS_T40D34M50I0R0\doc\RTD_FEE_UM.pdf But you are not able to reach 15 years in this use-case. Regards, Lukas Re: S32K344 Flash Memory Erase Cycles life Hi @lukaszadrapa , thanks. I notice we now support FEE in the latest MBDT for S32K3 (V1.6.0) . Could you help share some insight to the calculation involved for estimating if a certain use-case is feasible or not (in terms of Flash / emulated EEPROM specifications for S32K3). E.g. , if I need to write 2KB of data every 1 minute for 24 hours a day for 15 years , can this be supported assuming I am able to use FEE & can implement a round-robin sector scheme? Re: S32K344 Flash Memory Erase Cycles life Hi @jerryrig  This is 1MB block on S32K344, so this specification applies:   I can see you are erasing still the same sector in a loop. And because one sector erase == one P/E cycle, you have only 1000 cycles available. So, if you erase the same sector each minute, you have less than 17 hours. To achieve much better numbers, I would consider to use data flash block which provides  100,000 cycles and I would use EEPROM Emulation feature. There's Autosar Fee driver in RTD for this (notice that it's not available in non-Autosar Ip layer). Regards, Lukas

PF5020 OTP 设置（适用于 S32G3 EVK 和 Goldbox） S32G3 EVK 和 Goldbox 上使用的 PF5020 OTP 设置是否可用？ 电路板上的其他 PMIC 怎么样？

PF5020 S32G3 EVK & Goldbox の OTP 設定 S32G3 EVKやGoldboxで使用されているPF5020 OTPの設定は可能ですか? ボード上の他のPMICはどうですか?

Can the color of the scale numbers of the Meter control that comes with GUI-Guider be adjusted individually? Can I ask if the color of the scale numbers of the Meter control that comes with GUI-Guider can be adjusted separately? I changed the background of the dial to white and the scale to red, but the color of the scale numbers cannot be changed. In this case, the scale numbers cannot be displayed. Re: 请问GUI-Guider自带的Meter控件的刻度数字颜色是否单独可调？ Hi @alen-liao, Please refer the screenshot attached to adjust Digit Part: Best Regards， Wenbin

the memmap issue after adding eth module to GoldVIP-S32G Opening the GoldVIP-S32G3-1.11.0 with eb tresos 29.2.0，add Eth module in the module configurations. Then configure functions related to tsn and generate project. At this time, when compiling the code, it always prompts that the header file “Eth_MemMap.h” is missing. I know I need to configure memmap for Eth module. But i don't know how to do it. Re: the memmap issue after adding eth module to GoldVIP-S32G Thank you very much for your reply！ The problem has been solved. Here's how to do it: 1. Add the Eth module and configure configurations. 2. Build Project -> generate_swcd 3. Im-and exporters -> Imp_Swcd -> Run Importer 4. EcuExtractCreator 5. SvcAs_Trigger 6. Generate Project Re: the memmap issue after adding eth module to GoldVIP-S32G Hi, Thanks for your feedback. For the following comment: "...there is no explanation of how Eth_Memmap.h is generated" We understand that you are expecting for the file to be generated by your Configuration Tool, for which this might not happen. The "*_Memmap.h" files are already provided under the RTD package, for which this seems to be a linkage problem, not that the file is not being generated. Please, let us know. Re: the memmap issue after adding eth module to GoldVIP-S32G Thank you very much for your reply. 一.Explaining according to the documentation (Eth_TS_T40D11M40I2R0\doc\RTD_ETH_IM.pdf), after adding the Eth module, there is no explanation of how Eth_Memmap.h is generated.I think this is not written manually, it should be compiled and generated. 二. After adding the Eth module, I Compile GoldVIP-S32G3-1.11.0\realtime\s32g399ardb3\can-gw based on this document GoldVIP-S32G3-1.11.0\documentation\GoldVIP-User-Manual.pdf \14.4 Building the M7 Application.I don't know if there is something wrong with my compilation method。 Re: the memmap issue after adding eth module to GoldVIP-S32G Hi, For the log that you are showing, it seems that the makefile is not able to find the related "Eth_MemMap.h" file. We understand that you have modified the project, have you also modified the makefile itself? As for the overall MemMap usage, we recommend looking into the Integration Manual of the respective driver (i.e. Eth_TS_T40D11M40I2R0\doc\RTD_ETH_IM.pdf) for more information. Please, let us know.