What is the purpose of imx8mn-evk-u-boot.dtsi? According to imx8mn_evk_defconf, the boot dts file is imx8mn-elk.dts which includes imx8mn-elk.dtsi then imx8mn.dtsi. I don't see imx8mn-evk-u-boot.dtsi included, and I am not sure how and when this file is used. We are having a boot-up issue and wondering if this file is the issue. Do we need it if we are basing our board on imx8mn-evk with some modifications? Thank you. i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: What is the purpose of imx8mn-evk-u-boot.dtsi? The short answer is u-boot build system automatically includes -u-boot.dtsi in addition to the defined board file. In this example, the final u-boot device tree is imx8mn-evk.dts + imx8mn-evk-u-boot.dtsi. I found this description to be helpful. Not knowing this, we only created a custom device tree file for our board based on imx8mn-evk.dts and did not create -u-boot.dtsi version. @sinanakman this was causing SPL not to boot at all ( the common uuu USB cannot connect error). The underlying issue is inside imx8mn-evk-u-boot.dtsi, many nodes were decleraded with the property 'u-boot,dm-spl'. Apparently, this needed to select which node SPL would drive so you are not including the whole tree that u-boot uses. Obviously, without it, SPL did not have access to many key nodes such as pmic and uart, and it is no wonder we were not booting with zero output messages. I found this description to be useful. @hustdage I do not believe Binman is in play here, but I could be wrong as I am new to all this. You are correct that binman node is described within *-u-boot.dtsi file, but I don't believe it is used in the imx8mn-evk board since CONFIG_BINMAN is not set. I see boards that specifically select it, such as IMX8MN_BEACON, but not the IMX8MN_EVK target. It may be there as an optional feature, but I think the imx8mn_evk board still uses ad-hoc scripts included within the imx-boot to support the imx-mkimage tool in building the final image (flash.bin). Please correct me if I am wrong. Re: What is the purpose of imx8mn-evk-u-boot.dtsi? Moose' question  is "I don't see imx8mn-evk-u-boot.dtsi included".  And I have answered  " It is called binman node in u-boot. You can check the u-boot document. And learn this u-boot knowledge. “ It is not overlay, it is Automatic .dtsi includesion. https://github.com/nxp-imx/uboot-imx/blob/lf-6.1.36-2.1.0/tools/binman/binman.rst Automatic .dtsi inclusion It is sometimes inconvenient to add a 'binman' node to the .dts file for each board. This can be done by using #include to bring in a common file. Another approach supported by the U-Boot build system is to automatically include a common header. You can then put the binman node (and anything else that is specific to U-Boot, such as u-boot,dm-pre-reloc properies) in that header file. Binman will search for the following files in arch/ /dts: -u-boot.dtsi where is the base name of the .dts file -u-boot.dtsi -u-boot.dtsi -u-boot.dtsi u-boot.dtsi Re: What is the purpose of imx8mn-evk-u-boot.dtsi? The imx8mn-evk-u-boot.dtsi will overlay  imx8mn-evk.dts, so the final dtb will contain properties in imx8mn-evk-u-boot.dtsi . Of course, you need modify imx8mn-evk-u-boot.dtsi. Re: What is the purpose of imx8mn-evk-u-boot.dtsi? Hi Moose If you can show us what boot up issues you are having we might be able to help you a bit better. Please describe your custom board how it deviates from the eval board you might have based it and how you generate your images that you are having issues with. Best regards Sinan Akman Re: What is the purpose of imx8mn-evk-u-boot.dtsi? It is called binman node in u-boot. You can check the u-boot document. And learn this u-boot knowledge.

与S32K146的单线通信 您好， 只是想让你知道我使用 S32k14x EAR SDK v08.6 进行编码 我有一个模块（转向锁）。它采用单线通信协议运行。 所以，我很难弄清楚如何启用模块和我的 S32k146 之间的通信。以下是我的疑问。 1.接线： 以上是模块的接线细节。因此，我可以将信号反馈线（绿色）连接到 S32k146 的哪个引脚，以及如何根据电流在嵌入式术语中启用该信号。 2.建立沟通。 fowwling 是锁供应商提供的示例。我怎样才能实现这个 例子： 主机：控制器 从属：转向锁 锁定：从机收到数据后，主机发送数据：0xAAAA（两个字节） 推荐，它将伸出锁舌来锁定转向锁，然后回复其 当前状态。 打开：主机发送数据：0x5555（两个字节）当从机收到 赞扬，它会拉动锁舌打开转向锁，然后回复其 当前状态。 如果从属进程收到其他命令，它将忽略它并且不会做任何事情。 有人可以帮我吗？这对我来说会有很大的帮助。提前致谢 回复：与S32K146的单线通信 感谢您的意见。我忽略了那个错误。

How to change 32Mhz crystal Xtaltrim value in HWparemeter Hi NXP,     Now we are developing bluetooth board with KW45. And we meet a problem is that the frequency error of our dut is about 50 Khz, it is out of the limit (-20, 20)ppm. So now we want to change the internal capacitor to tune the frequency and to get more presice one. Here is our default Frequency error=57.6 Khz.       And we want to change the interal capacitor value to get more presice Frequency. We found HWParameter in HCI_black box project can change this value and it can be store in NBU, which will not be change even if we change FW in dut.        and this is the defalut code in HWParameter.h, Please help us to change the value, we really need your help, thanks!       Please help us to change the value, we really need your help, thanks! Re: How to change 32Mhz crystal Xtaltrim value in HWparemeter Hi Annie, It would depend on the XTAL you are using. For example, it has to be compliant with the +/-50ppm. But, for your question about the trim, you could use the PLATFORM_SetXtal32MhzTrim. You could take as a base the ShellCalibration_SetXtal32MHzTrim from the ble_shell example. Hope this helps. Regards, Ricardo Re: How to change 32Mhz crystal Xtaltrim value in HWparemeter Hi Ricardo,     We are using 32MHZ crytal from TXC, load capcitor is 8pF in the datasheet, which is the same as NDK NX1612SA (EXS00A-CS14160) that NXP recommended. That would be ok?     So we hope to discuss with you the viability of changing Xtaltrim to get more ideal Frequency accuracy and how to do?          Best Regards,     Annie Re: How to change 32Mhz crystal Xtaltrim value in HWparemeter Hello, Could you please confirm that you are using a NXP recommended 32MHz crystal? Also, maybe this community post might be helpful: KW45/K32W1 32MHz & 32kHz Oscilllation margins - NXP Community Regards, Ricardo

how to build fmc tool for arm64 Hi I want to use fmc on my ls1046a board which running a tiny yocto on it. I tried to build fmc with this: flex-builder -c fmc -a arm64 -r yocto:tiny   the log is like    flex-builder -c fmc -a arm64 -r yocto:tiny COMPONENT: fmc DISTRO TYPE: yocto DISTRO SCALE: tiny make: Entering directory '/home/LSDK' make[1]: Entering directory '/home/LSDK/packages/apps' make[1]: Leaving directory '/home/LSDK/packages/apps' make: Leaving directory '/home/LSDK'   and I found nothing got built.   Am I doing right? I am using LSDK21.048 Re: how to build fmc tool for arm64 Thanks, it works. Re: how to build fmc tool for arm64 Please don't add fmc in local_arm64_tiny.conf, just use the default local_arm64_tiny.conf provided in LSDK 21.08. Re: how to build fmc tool for arm64 I tried your commands, but it failed the same as before. If I add fmc to IMAGE_INSTALL_append of local_arm64_tiny.conf it failed with :  ERROR: Nothing RPROVIDES 'fmc' (but /home/yu/flexbuild_lsdk2108_github/components/rfs/yocto-poky/meta/recipes-core/images/core-image-minimal.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'fmc' is unbuildable, removing... Missing or unbuildable dependency chain was: ['fmc'] ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'fmc'] even after yocto:devel rfs built up. Do I need some change in the yocto:devel config?  Re: how to build fmc tool for arm64 Yes The prebuild image works well. But I need to build image for my own board. I confirmed again fmc won't be built in the yocot:tiny.  Here's what I have done: clone flexbuild_lsdk2108 repo build one time to fetch the resource flex-builder -m ls1046ardb -b sd clean the rfs and rebuild the rfs and itb flex-builder -i clean-rfs -r yocto:tiny flex-builder -i mkrfs -r yocto:tiny flex-builder -i mkitb -r yocto:tiny load the image and boot as ls1046ardb tftp $load_addr lsdk2108_yocto_tiny_LS_arm64_240412.itb bootm $load_addr#ls1046ardb there is no fmc tool NXP LSDK tiny 2108 (based on Yocto) TinyLinux login: root root@TinyLinux:~# fmc -sh: fmc: command not found If I add fmc to IMAGE_INSTALL_append of local_arm64_tiny.conf build rfs will get an error :  Loading cache: 100% | | ETA: --:--:-- Loaded 0 entries from dependency cache. Parsing recipes: 100% |###############################################################################################################################################################################################################################################| Time: 0:00:03 Parsing of 818 .bb files complete (0 cached, 818 parsed). 1443 targets, 56 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'fmc' (but /home/yu/flexbuild_lsdk2108_github/components/rfs/yocto-poky/meta/recipes-core/images/core-image-minimal.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'fmc' is unbuildable, removing... Missing or unbuildable dependency chain was: ['fmc'] ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'fmc'] Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. Could you try to build it once? Re: how to build fmc tool for arm64 Please try the pre-built image $ wget https://www.nxp.com/lgfiles/sdk/lsdk2108/lsdk2108_yocto_tiny_LS_arm64.itb Re: how to build fmc tool for arm64 Here's what I got on my yocto:tiny root@TinyLinux:~# fmc -sh: fmc: command not found root@TinyLinux:~# Re: how to build fmc tool for arm64 fmc is in yocto:tiny, you can use it directly. Re: how to build fmc tool for arm64 In my case if I add fmc to local_arm64_tiny.conf, I can not build rfs. Can you build with that? I used command you wrote above and here is my log. Re: how to build fmc tool for arm64 fmc tool has already been included in yocto:tiny filesystem, please refer to the following. root@TinyLinux:~# fmc ERR : PCD file is required root@TinyLinux:~# Re: how to build fmc tool for arm64 Thanks, but I have tried this. It seems there is not dependency for fmc yocto build. Could you try this in your environment ? I'm using LSDK21.04 19:09:47 NOTE: Runtime target 'fmc' is unbuildable, removing... 19:09:47 Missing or unbuildable dependency chain was: ['fmc'] 19:09:47 ERROR: Required build target 'core-image-minimal' has no buildable providers. 19:09:47 Missing or unbuildable dependency chain was: ['core-image-minimal', 'fmc'] Re: how to build fmc tool for arm64 Please add "fmc" in IMAGE_INSTALL_append in configs/yocto/local_arm64_tiny.conf $ flex-builder  -i clean-rfs -r yocto:tiny  $ flex-builder  -i mkrfs -r yocto:tiny Re: how to build fmc tool for arm64 Hi Team Could you please check this? Thanks!

VSCode failed to build with error - could not determine build directory.. Hello, When building imported sample app rtos version of hello world cm33 vscode fails to build with error  "Error: Could not determine the build directory for project mimxrt1180evk_hello_world_demo_cm33". SDk is 2.15, board is 1180 rev B, The build does not even start.  Is there any logs to see what is happening? When I tried a clean command (from vscode context menu) the log is  clean task started.... "C:\Program Files\CMake\bin\cmake.EXE" --build --config Debug --target clean -- Error: could not load cache clean finished with error(s). It seems that cmake tool does not get the path of project.  .vscode dir is attached. cmake is 3.28.1 Re: VSCode failed to build with error - could not determine build directory.. Hi @arunkumar_g ,   Thanks so much for your updated information.   I glad to hear you already make it works.   From your newest information, really like what you mentioned, should still the plugin install abnormal cause this issues.   Anyway, final working is important!   If you still have question about it, please kindly let me know. If your question is solved, please help to mark the correct answer, just to close this case. Any new issues, welcome to create the new question post, thanks. Best Regards, Kerry Re: VSCode failed to build with error - could not determine build directory.. The mcuxpresso tool is the one vscode plugin initiates. For me it is 1.2 b142 -and i install mcuxpresso sdk developer kit Finally I was able to build vscode project, But for that I did multiple things - Uninstall vscode, mcuxpresso tool app, mcuxpresso ide - Delete vscode plugin directories and mcuxpresso cache and tool download dirs (from folder as well as folders -Reinstalled back.  I still believe the issue was cause by mangled configuration of mcuxpresso vscode plugin. Re: VSCode failed to build with error - could not determine build directory.. Hi @arunkumar_g ,   Thanks for your updated information.   Which MCUXpresso Installer you are using now?   I will also try your version, my current version is V1.0, I may try all the Installer, Vscode, cmake version totally the same as you again. Just to kick out the tool issues. Best Regards, Kerry Re: VSCode failed to build with error - could not determine build directory.. Cmake installed was from mcuxpresso installer. I uninstalled that and installed 3.21 and no change in behavior. Have installed the sdk mutiple times in different paths and has same observations. I dont think this is related to cmake as mentioned in first post, somehow cmake does not get the build directory path. Is there a chance the plugin is passing empty path to cmake? From where the plugin gets the build path and how does it pass it to cmake? Re: VSCode failed to build with error - could not determine build directory.. Hi @arunkumar_g ,   Path should not the issue on your side, as I also use the same deep path: Can you try to use the low cmake version, which is the same as my:3.21.0: I think the vscode version should also not the issues. BTW, if you still have issues, do you also try to import the SDK again, whether any improvement or not? Any updated information, please kindly let me know. My windows system is win10. Best Regards, Kerry Re: VSCode failed to build with error - could not determine build directory.. @kerryzhou  i'm using vscode 1.88, cmake is 3.28.1. Yes all toolchains are enabled when i dowloaded (default selections for gcc toolchain)  @DragosMiloiu  No file paths are not long "C:\code\mcuexpresso\code\demo\mimxrt1180evk_freertos_hello_cm33" and long paths setting are enabled in pc. Re: VSCode failed to build with error - could not determine build directory.. Hi @arunkumar_g,  I noticed from your files that you are using Windows. Windows has a limit for the length of the path (260 characters). So, if the path to where you created the project is long could you try to create it in a shorter path (like C:/work) and see if it helps? Thanks, Dragos. Re: VSCode failed to build with error - could not determine build directory.. Hi @arunkumar_g ,  I also test it on my side, I can build it.  This is my test result: Which VScode version you are using? I am using 1.87.0. my cmake version is:cmake version 3.21.0 Your situation should caused by the repository import, which method you import the SDK? I am also using the SDK2.15.0, do you use all Toolchians: You can delete your vscode SDK, and import it again with the local method, whether it have improvement or not? Any updated information, please kindly let me know. Best Regards, Kerry Re: VSCode failed to build with error - could not determine build directory.. Yes mcuxpresso works ok. VScode is the one that shows this error.  Note: both are in different machines. Re: VSCode failed to build with error - could not determine build directory.. Hi @arunkumar_g ,   Thanks so much for your question.   If not use the vscode, use the IDE, eg, mcuxpresso, whether it works on your side?   Just the Vscode version meet issues, right?   I am also testing this code on my side, will give you updated information later. Best Regards, Kerry

i.MX93 Multicore flexio Hello experts, I am working on i.mx93 in which cortex-a55 is running Linux, here at cortex-m33 side I want to use flexio moules as felxio-pin (as gpio to toggle one pin), so for that I am using flexio_pin_led_output example code from this SDK_2_14_2_MIMX9352xxxxM. But after reading readme.txt file I found below things. Note Please run the application in Low Power boot mode (without Linux BSP). The IP module resource of the application is also used by Linux BSP. Or, run with Single Boot mode by changing Linux BSP to avoid resource conflict. 1. In Linux dts file I have not enabled any flexio related node, so my query is that is it safe to access flexio at cortex-m33 side? 2. Here I am worrying because readme.txt file denotes that The IP module resource of the application is also used by Linux BSP. but I am not able to find where it is. 3. In nutshell my task is to safely access flexio from cortex-m33 side. PS: I am referring imx93-11x11-evk.dts file that I have attached below. Re: i.MX93 Multicore flexio Hi, 1. I do. 2. It is. Regards Re: i.MX93 Multicore flexio Hi josephlinares Thanks for your comments, 1. Here do you mean to say that I should take care about the flexio-gpio pin which must not be used in cortex-A55 Linux dts file right? 2. And if not present in dts file than it is safe to access flexio-gpio pin from cortex-M33 core, is it true? Re: i.MX93 Multicore flexio Hi, Thank you for your interest in NXP Semiconductor products, Confirmed, could not find any usage of MX93_PAD_GPIO_IO04__X in imx93-11x11-evk.dts. But it's found under lpuart and aud-hat demos, consider looking at any DTS before using the flexio_pin_led_output.c demo. Regards

OV5640 image quality in Android 11 imx8mm , Horizontal RGB Lines Hi NXP  I am using custom imx8mm board with Android 11 , kernel 5.4.70  booting properly. OV5640 camera driver is intigreted and Display driver is integreted  everything works fine. Display works fine , When I open the camera app horizontal RGB lines are coming , after capturing the picture  also its same .  whole picture is coming blue colour. How to solve the RGB lines and it should auto focus? Does anyone have any solution or any referance link, pdf that will be helpfull. clock for the camera is 24 MHz. Camera is MIPI-CSI2 and Display is MIPI-DSI . I have attached the sample captured images and logcat of camera open, then captured a picture,then closed the camera application . Thanks and Regards Deepak Kumar Beniya Android Graphics & Display i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: OV5640 image quality in Android 11 imx8mm , Horizontal RGB Lines The issue is solved The problem was with camera power supply section . It was having noise in analog and digital power section . we have given external power supply to camera the lines were dissapeared. Re: OV5640 image quality in Android 11 imx8mm , Horizontal RGB Lines Then, for the camera configuration in Android, please read the Chapter 8.1 in Android User's Guide. https://www.nxp.com/docs/en/user-guide/ANDROID_USERS_GUIDE.pdf Re: OV5640 image quality in Android 11 imx8mm , Horizontal RGB Lines I have done Camera Test Pattern  Pattern testing is perfect . I have register values   {0x503d, 0x80, 0, 0},{0x4741, 0x00, 0, 0} Re: OV5640 image quality in Android 11 imx8mm , Horizontal RGB Lines https://www.nxp.com.cn/docs/en/reference-manual/IMX_REFERENCE_MANUAL.pdf There are different ov564 driver in the kernel. Please double check the driver you are using is proper or not. Please check the above manual Chapter 6.1.2. For i.MX 8M, select > OmniVision ov5640 camera support (MXC_CAMERA_OV5640_V2) and OmniVision ov5640 camera support using MIPI (MXC_CAMERA_OV5640_MIPI_V2). You may try to run Linux to test the camera first. make sure the camera is working well on the board. Re: OV5640 image quality in Android 11 imx8mm , Horizontal RGB Lines Connection is proper. It have AXT connectors. Is there any other solution for this.  So, I could solve this Problem Thanks Deepak Beniya Re: OV5640 image quality in Android 11 imx8mm , Horizontal RGB Lines It seems is like the hardware connection between camera and the board is not good. Please double check the connection.

MPC5777C MCAN stuck on TX buffer request pending Hello, What i'm trying to do is to use a M_CAN interface on our custom board. I tired to use the source code snippets from one of the examples available from this forum: https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/Example-MPC5777C-MCAN-simpleTXRX-GHS616/ta-p/1109280 I'm just using M_CAN1 to send the messages instead of M_CAN0 and the receiver is just a Kvaser interface. I have configured the pins 195 and 196 as alternate function (0x3) to use them as M_CAN1 interface. The external oscillator is used as interface clock. The problem that i'm facing is that when i try to send any message from dedicated buffer then i can see that the bit for buffer 0 is set in TXBRP but the message is never sent and the state of the TX pin also never changes, it stays constantly high. I can see the message RAM is updated with a frame data and i also tested that when using TEST register i can set and reset the TX pin state. I can't really see any errors in the registers (see attached screen). Any ideas why the interface never sends the message? In case more info is needed please don't hesitate to ask. Best regards Re: MPC5777C MCAN stuck on TX buffer request pending Hello, Yes, it looks like there was a bug in the software resulting in IMUX registers being overwritten with wrong values resulting in selecting incorrect input for M_CAN1 RX pin. Thank you for help. Best regards Re: MPC5777C MCAN stuck on TX buffer request pending Hi, another hint from register values; after leaving init mode the PSR[ACT] is still 0, it indicated the module is not synchronized to the bus, so cannot start transmission. It can be due to wrong pin configuration or the RX pin is seen low. You can try to disconnect transceiver and connect TX/RX pins together. Did you set respective IMUX register as well to select pin you are using? For 3N45H example you can refer to  https://community.nxp.com/docs/DOC-342013  BR, Petr Re: MPC5777C MCAN stuck on TX buffer request pending Hello, It is 3N45H. Best regards Re: MPC5777C MCAN stuck on TX buffer request pending Hi, I see ACK error is detected, from register view, but in this case I expect error counters set as well and TX signal should be visible. What is MCU mask set used in fact, there is little difference between 2N45H and 3N45H. BR, Petr

コンパレータCMP0_OUTパッド/ピン出力なし FRDM-KV10評価ボードでは、入力の構成とコンパレータの動作を検証するCMP0_SCR_COUTビットをスキャン(FRDM-KV10の赤色LEDのスイッチング)することで、CMP0コンパレータの動作を確認できます。 しかし、コンパレータ出力をPTC5ピンに取得できません(外部抵抗でヒステリシスを設定したい場合はイライラします)。 この3つの命令は、PTC5で出力するのに十分ですか。 ldr r0,=0x4004B014 //ピン制御レジスタ n (PORTC_PCR5) ldr r1,=0x00000640 //PTC5 alt6 CMP0_OUT str r1,[r0] 「非常に小さな」アセンブラ添付ソースファイルを参照してください(私は.添付するファイルの拡張子)。 Re:コンパレータCMP0_OUTパッド/ピン出力なし はい、出力をPAD / PINにリダイレクトするには、CMP0_CR1_OPE = 1も設定する必要があります。今ではうまくいきます。ご清聴ありがとうございました。

[Security] CSEC secureboot verify Dear NXPs： S32K146 P-Flash 1M(2 Block) D-Flash 32K background: CMD_BOOT_DEFINE→BootManager 6KB Use CSEC's secureboot mechanism for verification. The secondary verification area is Flex NVM Bootloader; The area of third-level verification is Application; A. Sequential Boot Mode Q1: (void)CSEC_DRV_BootDefine(BOOT_SIZE, CSEC_BOOT_SERIAL) After enabling secureboot, power on again to enter Secureboot. Since the selected mode is A. Sequential Boot Mode, even if the on-chip ROM fails to verify the Bootmanager image, the Bootmanager code will still be executed, so I It cannot be judged whether the first level verification is successful. I use the CSEC_DRV_GetStatus() interface in Bootmanager to determine the result of the first-level verification. If the (1 == (CSEC_STATUS_BOOT_OK & CSEC_DRV_GetStatus())) condition is met, the first-level verification is considered successful. Is my understanding correct? Q2: Is there any way I can get the BOOT_MAC value calculated by CSEC? Because I want to know what is the difference between this and the BOOT_MAC I calculated on my PC Re: [Security] CSEC secureboot verify Hi @Gideon  Even if sequential or parallel secure boot mode fails, the application code is executed. The only effect of the failure is that boot protected keys cannot be used. Only if strict sequential boot mode is used, the device will stay in reset forever if secure boot fails. But notice that there's no way to recover - the device needs to be replaced. Yes, use CSEC_STATUS_BOOT_OK to check the result. There's no way to read BOOT_MAC. This would violate the SHE specification. Regards, Lukas

Comparator CMP0_OUT no pad/pin output With the FRDM-KV10 evaluation board I am able to check the operation of the CMP0 comparator by scanning the CMP0_SCR_COUT bit (switching of the FRDM-KV10 red LED) which validates the configuration of the inputs and the operation of the comparator. BUT I can't get the comparator output to the PTC5 pin (which is frustrating when you want to have hysteresis set by external resistors). Is this 3 instructions enough to have the output on PTC5 :   ldr r0,=0x4004B014 //Pin Control Register n (PORTC_PCR5)   ldr r1,=0x00000640 //PTC5 alt6 CMP0_OUT   str r1,[r0] Please see the "very little" assembler attached source file (I had to change the .S extension of the file for it to be attached). Re: Comparator CMP0_OUT no pad/pin output Yes, you must also put CMP0_CR1_OPE=1 to have the output redirected to a PAD/PIN. Now it works. Thank you for your attention. Re: Comparator CMP0_OUT no pad/pin output Hi, Thank you so much for your interest in our products and for using our community. Unfortunately we do not have an SDK example that shows how to use the Comparator Output (CMPO), there is just the cmp_interrupt and cmp_polling examples. However to set the CMPO you just need to use the following registers: Hope it helps you. Have a nice day!

比较器 CMP0_OUT 无焊盘/引脚输出 使用 FRDM-KV10 评估板，我可以通过扫描 CMP0_SCR_COUT 位（FRDM-KV10 红色 LED 的切换）来检查 CMP0 比较器的运行，从而验证输入的配置和比较器的运行。 但是我无法将比较器输出送到 PTC5 引脚（当您想通过外部电阻设置滞后时，这是令人沮丧的）。 这 3 条指令是否足以在 PTC5 上获得输出： ldr r0,=0x4004B014 //引脚控制寄存器n (PORTC_PCR5) ldr r1，=0x00000640 //PTC5 alt6 CMP0_OUT 字符串 r1,[r0] 请参阅“非常少”的汇编程序附加源文件（我必须更改文件的 .S 扩展名才能将其附加）。 回复：比较器 CMP0_OUT 无焊盘/引脚输出 是的，您还必须将 CMP0_CR1_OPE=1 设置为将输出重定向到 PAD/PIN。现在它可以工作了。感谢您的关注。

Breakpoint FreeRtos debugging Hello ,  I can 't have an enabled breakpoint , also FreeRtos tasks (threads) I can't see them however. I create 4 tasks. Maybe it's not well configured. I am based on the Freertos s32k344 example. maybe my debugger doesnt support FreeRtos, my debugger is : Re: Breakpoint FreeRtos debugging Hi, I am using S32 DS V3.4 , using Free RTOS with 2 task. When i try to debug, breakpoint are hitting at very first time, but after triggering Resume option, breakpoints are not hitting.  Anyone please give me some suggestion to resolve this error. Re: Breakpoint FreeRtos debugging Thank you. If the breakpoints are resolved, the FreeRTOS debugging features will work. Re: Breakpoint FreeRtos debugging Hi @AchrafOukheir  According to the shared images, looks like you have selected the Skip All Breakpoints. This command marks all breakpoints in the current view as skipped. Breakpoints marked as skipped will not suspend execution.  B.R. VaneB

EVS application for recording video? Hello, I am using i.MX 8QuadMax MEK. I know i.MX 8QuadMax MEK supports multi-camera EVS on Android Automotive image. I'd like to know if there exist any EVS application that record video from (multi) camera. I know there exist evs_app under $MY_ANDROID/vendor/nxp-opensource/imx/evs/evs_app But I didn't find it to do the video record too. 1. Is there any EVS application that record video (H/W accelerated and h.265 format)? 2. And I'd like to find APIs to record video (H/W accelerated and h.265 format) in EVS application programming. What API can I use in the Android Automotive EVS programming environment in i.MX 8QuadMax MEK? F.Y.I. I am reading this page already. So please don't recommend me find this page. Thank you in advance. Re: EVS application for recording video? Thank you! At least you provided NXP training Content Pages and answer to my question that there is no example I need. Re: EVS application for recording video? Hello, Sorry NXP don't have an example similar what you are trying to do. https://community.nxp.com/t5/NXP-Training-Content/Working-With-Multiple-Cameras-in-i-MX8/ta-p/1532258 Regards

imx6ull cpu frequency failed using 1588 time synchronization when operating at 792000 Hi I am using the ptp4l tool for time synchronization on imxlinux version 4.1.15, when I increase the cpu frequency to 792000, it skips time, but it doesn't happen when I am using linux 5.15, I would like to ask what changes have been made in the higher version. Here is the printout of the time skip root@imx6ull:~# ptp4l -A -4 -H -m -i eth0 ptp4l[182.571]: selected /dev/ptp0 as PTP clock ptp4l[182.577]: driver changed our HWTSTAMP options ptp4l[182.578]: tx_type 1 not 1 ptp4l[182.578]: rx_filter 1 not 12 ptp4l[182.579]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[182.581]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[190.319]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[190.319]: selected best master clock e67809.fffe.3d93fe ptp4l[190.320]: assuming the grand master role ptp4l[194.325]: port 1: new foreign master ce96f5.fffe.4c2be7-1 ptp4l[198.325]: selected best master clock ce96f5.fffe.4c2be7 ptp4l[198.326]: port 1: MASTER to UNCALIBRATED on RS_SLAVE ptp4l[200.324]: master offset -2434 s0 freq -2876 path delay 1723 ptp4l[201.324]: master offset -2516 s2 freq -2958 path delay 1721 ptp4l[201.325]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[202.324]: master offset -2598 s2 freq -5556 path delay 1721 ptp4l[203.324]: master offset -7 s2 freq -3744 path delay 1720 ptp4l[204.325]: master offset 781 s2 freq -2958 path delay 1720 ptp4l[205.324]: master offset 789 s2 freq -2716 path delay 1712 ptp4l[206.325]: master offset 2147484114 s2 freq +32767999 path delay 1712 ptp4l[207.325]: master offset -24954283 s2 freq -24957551 path delay 1716 ptp4l[208.325]: master offset -12526340 s2 freq -20015893 path delay 1069 ptp4l[209.325]: master offset -28330 s2 freq -11275785 path delay 1069 ptp4l[210.325]: master offset 14538505 s2 freq +3282551 path delay -2068315 ptp4l[211.325]: master offset 2158479308 s2 freq +32767999 path delay -2068315 ptp4l[212.325]: master offset -13968519 s2 freq -20862922 path delay -2068315 ptp4l[213.325]: master offset 2145937382 s2 freq +32767999 path delay -2068315 ptp4l[214.325]: master offset 2121002525 s2 freq +32767999 path delay -2068315 ptp4l[215.325]: master offset -53833606 s2 freq -32767999 path delay 279566 ptp4l[216.325]: master offset -28931120 s2 freq -32767999 path delay 279566 ptp4l[217.325]: master offset -3931906 s2 freq -15016865 path delay 279566 ptp4l[218.325]: master offset 8588962 s2 freq -3675568 path delay 279566 ptp4l[219.325]: master offset 13242000 s2 freq +3554158 path delay -193292 Re: imx6ull cpu frequency failed using 1588 time synchronization when operating at 792000 Problem solved because the fec controller in linux 4.1.15 imx6ul did not add this configuration FEC_QUIRK_BUG_CAPTURE Re: imx6ull cpu frequency failed using 1588 time synchronization when operating at 792000 Hi, Thank you for your interest in NXP Semiconductor products, There are going to be changes in the kernel as well as the driver itself, probably, You could go through the release notes for every release and look for the code improvements. You are advised to move to latest BSP which features fixes to issues like this one. Regards

A Question on I2C Device in a Mixed I3C Bus Hi, NXP Experts, Recently, we are investigating if NXP-RT600 MCU with I3C HDR support could meet our system requirement. We now have a following question, and hope get support from you. In our system, there will be not only I3C devices but also I2C legacy devices which can work at 400Kbps or 1Mbps modes. As for legacy I2C protocol, multi-master feature is supported so that any of the I2C device can start a communication transaction when a bus is in an idle state. Is this still true for an I2C device working in a mixed I3C bus i.e. the I2C device (target in I3C specification term) can start a communication transaction when the mixed I3C bus is in Bus Availiable State? Will NXP-RT600 MCU support such a use senario? Thanks and Regards! // JC1985 Re: A Question on I2C Device in a Mixed I3C Bus Thanks Omar for your help, it is very clear! Re: A Question on I2C Device in a Mixed I3C Bus I3C is compatible with I2C but with some limitations: – Does not support clock stretching by other devices on the bus. – Does not support multi-master systems I2C. – Does not support extended addressing (10-bit). – Supports standard mode, fast mode, and fast more plus, not high-speed mode. Best regards, Omar

バックドア方式は、どのようなシナリオでITCMおよびDTCMのS32K312にアクセスするために使用されますか? 1.私は現在、シングルコアプロセッサであるS32K312のTCMを使用しています。 ただし、メモリ マップには、ITCM_0 Backdoor と DTCM_0 Backdoor のアドレスが用意されています。そのユースケースは何ですか?S32K312には直接法で十分だと思います。   2. ITCM_0 Backdoor と DTCM_0 Backdoor を使用する場合、linker_flash_s32k312.ld の MEMORY セクションと SECTION セクションに定義を追加する必要がありますか? バックドア方式を使用してITCMとDTCMにアクセスするためのデモをどこで入手できるか知っている人はいますか? どうもありがとうございます。

mbedTLS サポート v3.6 NXPチームの皆さん、こんにちは。 短期的にmbedTLS v3.5のバージョンをサポートする予定があるかどうか知りたいです 私の組織では、現在のv2.28.5のいくつかの脆弱性を認識し、心配しています お時間をいただきありがとうございます、そしてよろしくお願いします。 ロベルト・ロドリゲス 回复: mbedTLSサポート v3.6 ご支援いただき、誠にありがとうございました。 回复: mbedTLSサポート v3.6 ご回答ありがとうございます。 私が使用しているデバイスはMIMXRT1051xxxxBです。これは古いデバイスですか?これを支援する予定はありますか?

在什么情况下会使用后门方法访问S32K312的ITCM和DTCM？ 1.我目前使用的是S32K312的TCM，它是一个单核处理器。 但是，内存映射提供了 ITCM_0 后门和 DTCM_0 后门的地址。它们的用例是什么？我认为直接方法对于S32K312来说已经足够了。   2.如果我使用ITCM_0 Backdoor和DTCM_0 Backdoor，是否需要在linker_flash_s32k312.ld的MEMORY和SECTION部分添加定义？ 有人知道我可以在哪里获得使用后门方法访问 ITCM 和 DTCM 的演示吗？ 非常感谢您。

In what scenarios would the backdoor method be used to access ITCM and DTCM for S32K312? 1. I am currently using the TCM of S32K312, which is a single-core processor. However, the memory map provides addresses for ITCM_0 Backdoor and DTCM_0 Backdoor. What are their use cases? I think Direct method is sufficient for S32K312.   2. If I use ITCM_0 Backdoor and DTCM_0 Backdoor, do I need to add definitions in the MEMORY and SECTION sections of linker_flash_s32k312.ld? Does anyone know where I can obtain a demo for accessing ITCM and DTCM using the Backdoor method? Thanks a lot. Re: In what scenarios would the backdoor method be used to access ITCM and DTCM for S32K312? Hi @petervlna  Thank you for your response to my post. Your response resolved my confusion.   Best regards, Chris Re: In what scenarios would the backdoor method be used to access ITCM and DTCM for S32K312? Hello, 1. I am currently using the TCM of S32K312, The reason is that only core has direct access as master. Other masters like DMA need to access the TCM memory via backdoor. 2. If I use ITCM_0 Backdoor and DTCM_0 Backdoor, do I need to add definitions in the MEMORY and SECTION sections of linker_flash_s32k312.ld? Does anyone know where I can obtain a demo for accessing ITCM and DTCM using the Backdoor method? You can have a look at the example here. https://community.nxp.com/t5/S32K/DTCM-ITCM-example/m-p/1606827#M21008 Best regards, Peter