在多台计算机上使用 S32DS 许可 你好，我正试图在两台不同的计算机上安装 S32DS，两台计算机都是我自己使用的。 原来 S32DS 许可证只能使用一次，所以我不能使用我的许可证在第二台计算机上安装。我可以为我的账户再申请一个 S32DS 3.5 许可证吗？预先表示感谢。 激活 | 安装 | 许可 | 安装程序下载

IMX8mp 上の GPU から NPU へのゼロコピー こんにちは、 私は i.MX 8M Plus のパイプラインに取り組んでいますが、GPU (OpenCL) から NPU へのゼロコピー データ転送を実現する方法があるかどうか疑問に思っています。 DMA-BUF を使用したゼロコピーをサポートしていると思われる NNStreamer に遭遇しましたが、パイプラインに GPU プロセッシングステップ (OpenCL など) を挿入して NPU までゼロコピーを維持できるかどうかに関する明確なドキュメントや例は見つかりませんでした。 私の質問: GPU プロセッシング (OpenCL 経由) を実行し、その結果をコピーせずに NPU に直接渡すことは可能ですか? NNStreamer はゼロコピーを維持しながらこのフローをサポートできますか? はいの場合、GPU と NPU の両方のアクセスに対して DMA-BUF (または互換メモリ) を設定する方法の例や推奨されるプラクティスはありますか? ドキュメント、例、または関連するカーネル/ユーザー空間コンポーネントへのポインタがあれば、大変ありがたく思います。 よろしくお願いします！ Re: GPU zero-copy to NPU on IMX8mp こんにちは、 opencl での dmabuf 機能のサポートについては、このThreadを参照してください。 https://community.nxp.com/t5/i-MX-Graphics/IMX8MP-OpenCL-extension-cl-khr-external-memory-dma-buf-missing/mp/2147914 しかし、nnstreamerやvxデリゲートにはimport dmabufのようなデモコードは存在しない。 よろしくお願いします、 志明

[TJA1043] Occasional Failure to Transmit or Receive CAN Messages Dear NXP Technical Team, We have encountered an occasional issue where TJA1043T is unable to transmit or receive messages properly during use. Could you please confirm whether the following CAN bus environment might affect the normal operation of TJA1043T: Source voltage: 13.72V CAN_H voltage: 2.8V CAN_L voltage: 2.2V Thanks for your support. Alex Re: [TJA1043] Occasional Failure to Transmit or Receive CAN Messages Dear Tomas, Thank you for your detailed response and insights. As you suggested, we have captured the actual CAN bus waveforms during operation on the vehicle using the oscilloscope. Please refer to the attached screenshot for the waveform details. Measurement points: CAN_H and CAN_L at the TJA1043 transceiver side Could you please help us analyze the quality of the bus signals based on the waveform? Specifically, we would like to know: (1) Whether there are any noticeable ringing, overshoot, or signal integrity issues. (2)If the signal shape and level meet the requirements for reliable CAN communication. (3)Whether any observed anomalies might contribute to occasional communication errors or error frames. Your further guidance would be greatly appreciated. Best regards, Alex Re: [TJA1043] Occasional Failure to Transmit or Receive CAN Messages Dear Alex, If I understood correctly, the differential voltage between CAN_H and CAN_L in your setup is: V_diff = CAN_H - CAN_L = 2.8V - 2.2V = 0.6V This value is below the typical threshold for a dominant state, which is usually between 1.5V and 3V in Normal mode (see datasheet Table 8). In recessive state, the bus voltages should be approximately equal and centered around 0.5 × VCC. So differential voltage of 0.6V may not be reliably interpreted as either dominant or recessive, potentially leading to communication errors. To ensure proper operation: - Confirm correct bus termination. - Ensure consistent ground potential across all nodes. - Verify that the transceiver is in Normal mode and not in Standby or Sleep mode. - Check for any external biasing or leakage affecting the bus lines. If the issue persists, capturing bus waveforms during failure events and monitoring the ERR_N pin for diagnostic flags may help identify the root cause. BRs, Tomas

S32G3 BSP44.0: fsl-image-ubuntu looking for virtual/x86_64-fslbsp-linux-gcc-crosssdk I'm trying to build an ubuntu image for the s32g399ardb3 using the S32G3 Linux BSP44.0. I have the machine set to s32g399ardb3ubuntu and running bitbake fsl-image-ubuntu gives an error: ERROR: Nothing PROVIDES 'virtual/x86_64-fslbsp-linux-gcc-crosssdk' (but /newhome/arthur/fsl-auto-yocto-bsp44.0_s32g/sources/meta-alb/meta-alb-sdk/recipes-devtools/binutils2.34/binutils-cross-canadian_2.34.bb DEPENDS on or otherwise requires it). Close matches: virtual/x86_64-fslbsp-linux-g++ virtual/x86_64-fslbsp-linux-gcc virtual/x86_64-fslbsp-linux-go I can build the fsl-image-auto image in BSP44.0 for s32g399ardb3. I can also build the fsl-image-ubuntu image in BSP43.0 for s32g399ardb3ubuntu. The machine I am building on is: SB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal Kernel version is 5.4.0-204-generic and ldd (Ubuntu GLIBC 2.31-0ubuntu9.18) 2.31 There are log warnings qabout the preferred version of 2.35 of glibc not available. Am I missing a package? Regards, Arthur. Full log: arthur@nmgPowerEdgeT630:~/fsl-auto-yocto-bsp44.0_s32g/build_s32g399ardb3ubuntu$ bitbake fsl-image-ubuntu Loading cache: 100% |##############################################################################################################| Time: 0:00:02 Loaded 5800 entries from dependency cache. Parsing recipes: 100% |############################################################################################################| Time: 0:00:01 Parsing of 3692 .bb files complete (3691 cached, 1 parsed). 5803 targets, 615 skipped, 2 masked, 0 errors. NOTE: Resolving any missing task queue dependencies WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-aarch64 not available (for item virtual/aarch64-fsl-linux-binutils) WARNING: versions of binutils-cross-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.35 of cross-localedef-native not available (for item cross-localedef-native-dev) WARNING: versions of cross-localedef-native available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-crosssdk-x86_64-fslbsp-linux not available (for item virtual/x86_64-fslbsp-linux-binutils) WARNING: versions of binutils-crosssdk-x86_64-fslbsp-linux available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item virtual/libc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-native not available (for item binutils-native) WARNING: versions of binutils-native available: 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libintl) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item virtual/nativesdk-libiconv) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-utils) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dbg) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-dev) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-localedata-i18n) WARNING: versions of glibc-locale available: 2.31 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc-thread-db) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.38 of binutils-cross-canadian-aarch64 not available (for item binutils-cross-canadian-aarch64) WARNING: versions of binutils-cross-canadian-aarch64 available: 2.34 2.42 WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-ldconfig) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-dev) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of nativesdk-glibc not available (for item nativesdk-glibc-utils) WARNING: versions of nativesdk-glibc available: 2.39+git WARNING: preferred version 2.35 of glibc not available (for item glibc) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc not available (for item ldconfig) WARNING: versions of glibc available: 2.31+git 2.39+git WARNING: preferred version 2.35 of glibc-locale not available (for item glibc-locale) WARNING: versions of glibc-locale available: 2.31 2.39+git WARNING: preferred version 2.35 of glibc not available (for item virtual/libintl) WARNING: versions of glibc available: 2.31+git 2.39+git ERROR: Nothing PROVIDES 'virtual/x86_64-fslbsp-linux-gcc-crosssdk' (but /newhome/arthur/fsl-auto-yocto-bsp44.0_s32g/sources/meta-alb/meta-alb-sdk/recipes-devtools/binutils2.34/binutils-cross-canadian_2.34.bb DEPENDS on or otherwise requires it). Close matches: virtual/x86_64-fslbsp-linux-g++ virtual/x86_64-fslbsp-linux-gcc virtual/x86_64-fslbsp-linux-go NOTE: Runtime target 'binutils-cross-canadian-aarch64' is unbuildable, removing... Missing or unbuildable dependency chain was: ['binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] NOTE: Runtime target 'packagegroup-cross-canadian-s32g399ardb3' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-cross-canadian-s32g399ardb3', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] ERROR: Required build target 'fsl-image-ubuntu' has no buildable providers. Missing or unbuildable dependency chain was: ['fsl-image-ubuntu', 'packagegroup-cross-canadian-s32g399ardb3', 'binutils-cross-canadian-aarch64', 'virtual/x86_64-fslbsp-linux-gcc-crosssdk'] Summary: There were 48 WARNING messages. Summary: There were 2 ERROR messages, returning a non-zero exit code. Linux BSP Re: S32G3 BSP44.0: fsl-image-ubuntu looking for virtual/x86_64-fslbsp-linux-gcc-crosssdk Linux BSP support no longer includes the Ubuntu rootfs following the migration to Poky 5.0. This limitation is also documented in the Linux BSP Release Notes for BSP version 44. Re: S32G3 BSP44.0: fsl-image-ubuntu looking for virtual/x86_64-fslbsp-linux-gcc-crosssdk Apologies this is a duplicate of https://community.nxp.com/t5/AP-Software-Support/Linux-BSP-44-build-errors/td-p/2164327 with possibly a bit more information. Regards, Arthur.

MPC5744p CANモジュールの再初期化 こんにちは、みんな、 私の名前はアブデルラーマン ハビブです。MPC5744p 用の NXP ツールボックスを使用しています。私の質問は、SIMULINK NXP ツールボックス全体の実行中に CAN モジュールをリセットして再起動したいということです。SOどうやってそれをするのでしょうか? 言い換えれば、マイクロコントローラ自体をリセットするのと同じ動作を、ECU モジュール全体ではなく CAN モジュールに対してのみ実行したいのです。 よろしくお願いいたします。

S32G-VNP-RDB3 enable LLCE flexcan   Where exactly is J166 (CAN2_SEL) located on the S32G-VNP-RDB3 board and how should it be configured? Which physical connector does LLCE CAN0 and LLCE CAN14 map to? Is additional Device Tree / pinmux / transceiver enable configuration required, or is the jumper sufficient? Is there an official mapping table for LLCE instances → FlexCAN → transceiver → board connector? What does LLCE FW error 53 mean in this context (is it related to missing ACK)? in the picture is the connected with llcecan14(device tree) with FlexCan0 port ?   Re: S32G-VNP-RDB3 enable LLCE flexcan Hello, @Scidem  Thanks for your post. 1. Would you mind share more information regarding to J166, in which document/chart it was mentioned? 2. When the cable shown is plugged to the board, the LLCECAN0/CAN14 could be directly used with the cable, there is mark on each pair of the wire, 3. For actually using it under BSP, you may reference the chapter12 "LLCE support" of BSP44 UM for S32G3, the detailed configurations, building prerequisite are provided. 4. The LLCE_CAN and FlexCAN are different IPs on S32G3, connections on RDB3 is shown below: 5. The error mentioned may be the LLCE_ERROR_COMMAND_NOTSUPPORTED,  For the detailed error code description, I suggest referencing the Llce_Fw_ReturnType in  Llce_InterfaceFwMgr.h directly 6. No, as mentioned, LLCE_CAN14 and FlexCAN0 are different. they could be used separately. BR Chenyin

MPC5746CRM 你好 你能提供从最旧到最新的 MPC5746C 参考手册吗？ 即 Rev_1、Rev_2、......，直到 Rev_6.1 维护该产品已超过 7 年，因此希望了解所有变化。 谢谢！ Re: MPC5746CRM 你好 遗憾的是，我们做不到。所有更改都会在最新版本中进行跟踪。 只需参考附录：版本说明： 始终坚持使用最新版本。 顺祝商祺！ Peter Re: MPC5746CRM 你好，彼得、 我已收到所有 RM。 您现在可以关闭该票。 谢谢！

How to display video capture by OS08A20 camera via HDMI(LT8912)? Hello, Could you please tell me how to display video captured by the OS08A20 camera via HDMI(LT8912)? ■ Environment Board: i.MX95 Verdin Camera: OS08A20 HDMI: LT8912 BSP: Official NXP BSP (NXP’s Full Reference Image) https://www.nxp.com/webapp/Download?colCode=L6.6.23_2.0.0_MX95&appType=license DTB:imx95-19x19-verdin.dtb+imx95-19x19-verdin-lt8912.dtbo+imx95-19x19-verdin-os08a20.dtbo Command used: GST_DEBUG=3 gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,width=1920,height=1080,format=YUYV" ! videoconvert ! autovideosink ■ Result 0:00:00.083718541 916 0xaaaaf3247f20 ERROR GST_PIPELINE grammar.y:1138:gst_parse_perform_link: could not link v4l2src0 to videoconvert0, neither element can handle caps video/x-raw, width=(int)1920, height=(int)1080, format=(string)YUYV WARNING: erroneous pipeline: could not link v4l2src0 to videoconvert0, neither element can handle caps video/x-raw, width=(int)1920, height=(int)1080, format=(string)YUYV If any additional information is needed, please let me know. Thank you in advance! Graphics & Display Multimedia Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi @kazuhito_morita , Dtb file I use this one: fdtfile=imx95-19x19-evk-os08a20-isp-it6263-lvds0.dtb For the  The console output of the media-ctl -p command executed on your board The console output of the zcat /proc/config.gz command executed on your board You need I add them to the attachment. By the way,  if still not work in your side. You can use the support way I share you last time. We do not have your board in hand, so can not debug it for, I confirmed in our side, for the in iMX95 Verdin board support you can contact the Toradex Toradex - Customer Support Hope this can do help for you Wish you have a nice day Best Regads Rita Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi @Rita_Wang  Thank you for your reply despite being busy. The BSP version is the same as my environment. I’m also using 6.12.34_2.1.0 now. However, the issue has not been resolved yet. I’m looking forward to receiving the other two pieces of information. best regards Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? I am using the newest version BSP in our website: For the others  The console output of the media-ctl -p command executed on your board The console output of the zcat /proc/config.gz command executed on your board I will test on our board later and then give you reply, so sorry for late test on it, too many task in hand. Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? I am on the new prodcut training this week, I will try again next week when I go to office, then test for you. Thanks. Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi, @Rita_Wang  Could you please share the following information about your environment? The version of the NSP-BSP you are using The console output of the media-ctl -p command executed on your board The console output of the zcat /proc/config.gz command executed on your board The DTS file you are using Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Good news it work now. I will send you next week I go to office and then share it to you. Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? hi, @Rita_Wang  Thank you very much for all your support so far. You were able to output the input image from the OS08A20 camera via HDMI, and I would like to refer to your implementation. Would it be possible for you to share the following information? The version of NSP-BSP you are using The console output of the media-ctl -p command executed on your board The console output of the zcat /proc/config.gz command executed on your board The DTS file you are using Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi @kazuhito_morita , We do not have your board in hand, so can not debug it for, I confirmed in our side, for the in iMX95 Verdin board support you can contact the Toradex Toradex - Customer Support Hope this can do help for you Wish you have a nice day Best Regards Rita Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? @Rita_Wang  Thank you for your advice. However, I still cannot display the camera image. Here are the steps I executed: export LIBCAMERA_PIPELINES_MATCH_LIST='nxp/neo,imx8-isi,uvcvideo' GST_DEBUG=3 gst-launch-1.0 libcamerasrc ! queue ! autovideosink RESULT The following debug messages appear in the console:   Setting pipeline to PAUSED ... export LIBCAMERA_PIPELINES_MATCH_LIST='nxp/neo,imx8 [0:01:38.381866712] [780] INFO Camera camera_manager.cpp:326 libcamera v0.0.0+5937-lf-6.12.34-2.1.0 [0:01:38.507243420] [784] INFO NxpNeoIPA neo_ipa.cpp:131 nxpneo: IPANxpNeo NXPNEO_IPA_v0.0.0+5937-lf-6.12.34-2.1.0 Pipeline is live and does not need PREROLL ... 0:00:00.611470375 780 0xffff84000b70 FIXME default gstutils.c:4169:gst_element_decorate_stream_id_internal: Creating random stream-id, consider implementing a deterministic way of creating a stream-id Pipeline is PREROLLED ... Setting pipeline to PLAYING ... 0:00:00.612225292 780 0xffff84000b70 WARN default gstlibcamera-utils.cpp:345:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R10 New clock: GstSystemClock 0:00:00.612294792 780 0xffff84000b70 WARN default gstlibcamera-utils.cpp:345:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R12 0:00:00.612571875 780 0xffff84000b70 WARN default gstlibcamera-utils.cpp:345:gst_libcamera_stream_formats_to_caps: Unsupported DRM format XVUY [0:01:38.925148004] [785] INFO Camera camera.cpp:1205 configuring streams: (0) 3840x2160-NV21/sYCC 0:00:00.0 / 99:99:99.:99.   The counter remains at 0:00:00.0 and does not count up. When I boot the NXP BSP, Weston seems to start automatically. A gray background and some application icons are displayed — could this be affecting the camera display? Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi @kazuhito_morita , Thank you, I am back and discussed with my colleague，you also need to run the following commend : export LIBCAMERA_PIPELINES_MATCH_LIST='nxp/neo,imx8-isi,uvcvideo' You can try it, I will wait for your test result.  If still not work tell me. Wish you have a nice day Best Regards Rita Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? @Rita_Wang  Thank you very much for your support. Wishing you a wonderful holiday! Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi @kazuhito_morita , I see the board you are using, it is not our EVK board, here I will test the OS08A20 camera via HDMI on our EVK board and then tell you the result. By the way, in China we will have the China National days leave from today and I will test i for you when I back to office on the Oct 9th. Thanks for kindly understandings. Wish you have a nice day Best Regards Rita Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi, @Rita_Wang  Thank you for your cheking. I’m attaching a photo of the board. Please take a look and let me know what you think. best regards. Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi @kazuhito_morita ， Can you share the board picture to me? I do not know the verison Board in your side, B0 or A1 version, thanks. Wish you have a nice day Best Regards Rita Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? @Rita_Wang  Thank you for checking. I tried the GStreamer pipeline you suggested, but I encountered an error. I will investigate the details of the error. root@imx95evk:~# gst-launch-1.0 libcamerasrc ! queue ! autovideosink Setting pipeline to PAUSED ... [0:01:47.980555800] [624] INFO Camera camera_manager.cpp:315 libcamera v0.0.0+4594-lf-6.6.23-2.0.0-dirty (2025-09-05T01:32:47+00:00) [0:01:48.031624883] [629] INFO NxpNeo neo_utils.cpp:629 Parsing pipeline config file /usr/share/libcamera/pipeline/nxp/neo/config.yaml [0:01:48.033805175] [629] WARN CameraSensor camera_sensor.cpp:248 'os08a20 2-0036': Recommended V4L2 control 0x009a0922 not supported [0:01:48.033880508] [629] WARN CameraSensor camera_sensor.cpp:315 'os08a20 2-0036': The sensor kernel driver needs to be fixed [0:01:48.033911467] [629] WARN CameraSensor camera_sensor.cpp:317 'os08a20 2-0036': See Documentation/sensor_driver_requirements.rst in the libcamera sources for more information [0:01:48.034876550] [629] WARN CameraSensorProperties camera_sensor_properties.cpp:262 No static properties available for 'os08a20' [0:01:48.034923050] [629] WARN CameraSensorProperties camera_sensor_properties.cpp:264 Please consider updating the camera sensor properties database [0:01:48.034952592] [629] WARN CameraSensor camera_sensor.cpp:461 'os08a20 2-0036': Failed to retrieve the camera location [0:01:48.034980800] [629] WARN CameraSensor camera_sensor.cpp:483 'os08a20 2-0036': Rotation control not available, default to 0 degrees Pipeline is live and does not need PREROLL ... ERROR: from element /GstPipeline:pipeline0/GstLibcameraSrc:libcamerasrc0: Internal data stream error. Pipeline is PREROLLED ... Additional debug info: /usr/src/debug/libcamera/0.2.0.imx/src/gstreamer/gstlibcamerasrc.cpp(645): gst_libcamera_src_task_enter (): /GstPipeline:pipeline0/GstLibcameraSrc:libcamerasrc0: streaming stopped, reason not-negotiated (-4) Setting pipeline to PLAYING ... ERROR: pipeline doesn't want to preroll. I would appreciate it if you could advise me on anything else I should try or check. Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? I have tried  on the i.MX 95 EVK running 6.12.20_2.0.0 BSP, it can run well. Run the example Gstreamer pipeline to verify camera stream root@imx95evk:~# gst-launch-1.0 libcamerasrc ! queue ! autovideosink Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Can you share the board picture to me? Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? @Rita_Wang  Thank you for your response. The box is labeled as follows: iMX95 Verdin EVK V1.1D PN: 05241103 SN: 36204509 The board itself is labeled as follows: iMX95 Verdin EVK CB V1.3A PN：05211300 SN：35873003 best regards Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? @Rita_Wang  Thank you for your response. The box is labeled as follows: iMX95 Verdin EVK V1.1D PN: 05241103 SN: 36204509 The board itself is labeled as follows: iMX95 Verdin EVK CB V1.3A PN：05211300 SN：35873003 best regards Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? For the i.MX95 19x19 EVK boar which version are you using, B0 or others？ Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? I tried to capture an image using v4l2-ctl, then the kernel crashed. ■ System Configuration SoC / Board: NXP i.MX95 19x19 EVK (Verdin variant) Linux Kernel: 6.6.23-lts-next-06236-gb586a521770e NXP Yocto BSP: Official NXP BSP (NXP’s Full Reference Image) Camera: OS08A20_MIPI Used device: /dev/video0 Device Tree: imx95-19x19-verdin.dtb + imx95-19x19-verdin-lt8912.dtbo + imx95-19x19-verdin-os08a20.dtbo(overlayed) media-ctl version: 6.6.23 ■ Problem Description When I try to start a video capture using the following command, the kernel crashes (Oops) every time.   v4l2-ctl -d /dev/video0 --stream-mmap=1 --stream-count=1 ■ Example Oops/Crash Log Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP CPU: 1 PID: 691 Comm: v4l2-ctl Not tainted 6.6.23-lts-next-06236-gb586a521770e #1 Hardware name: NXP i.MX95 19X19 board (DT) pc : formatter_subdev_enable_streams+0xb0/0x22c ... Call trace: formatter_subdev_enable_streams+0xb0/0x22c v4l2_subdev_enable_streams+0xe4/0x268 mxc_isi_crossbar_enable_streams+0x12c/0x1d0 v4l2_subdev_enable_streams+0xe4/0x268 mxc_isi_pipe_enable+0x204/0x2ac mxc_isi_vb2_start_streaming+0xa0/0xe4 vb2_start_streaming+0x68/0x15c vb2_core_streamon+0xf8/0x1bc vb2_streamon+0x18/0x64 mxc_isi_video_streamon+0x28c/0x314 v4l_streamon+0x24/0x30 __video_do_ioctl+0x32c/0x3f8 ■ media-ctl device topology (excerpt) The media graph is active with crossbar/csi/formatter/ISI routing. (See attached details below. media-ctl.txt) ... ■ Reproduction Details The media graph, Device Tree, and v4l2/fmt settings are configured according to the official NXP documentation. Even when restricting to just one ISI channel (/dev/video0), the Oops always occurs. ■ Questions Is this Oops in formatter_subdev_enable_streams() a known issue in recent NXP BSP or kernel 6.6.x? Is there any BSP update or kernel patch available to address this problem? If so, where can I find it? Are there any recommended workarounds or hints to resolve this and enable video capture? Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi , I am also facing the same issue in my iMX95 Verdin EVK kit. The following are the details. I have recently bought the X-IMX-OS08A20 camera module from https://www.nxp.com/design/design-center/development-boards-and-designs/4K-MIPI-CMOS-CAMERA-MODULE. I have connected it to the iMX95 Verdin EVK kit and the camera gets detected properly and probes successfully. I am using the following dtb-  imx95-19x19-verdin-os08a20-isp-lt8912.dtb I am running the following v4l2 commands and I could get the v4l2 stream with stream-mmap command. The following is the commands which I use media-ctl -d /dev/media0 -l "'os08a20 2-0036':0 -> 'csidev-4ad30000.csi':0[1]" media-ctl -d /dev/media0 -l "'csidev-4ad30000.csi':1 -> '4ac10000.syscon:formatter@20':0[1]" media-ctl -d /dev/media0 -l "'4ac10000.syscon:formatter@20':1 -> 'crossbar':2[1]" media-ctl -d /dev/media0 -l "'crossbar':5 -> 'mxc_isi.0':0[1]" media-ctl -d /dev/media0 -l "'mxc_isi.0':1 -> 'mxc_isi.0.capture':0[1]" echo "media setting" media-ctl -d /dev/media0 -R "'os08a20 2-0036' [1/0->0/0[1]]" media-ctl -d /dev/media0 -R "'csidev-4ad30000.csi' [0/0->1/0[1]]" media-ctl -d /dev/media0 -R "'4ac10000.syscon:formatter@20' [0/0->1/0[1]]" media-ctl -d /dev/media0 -R "'crossbar' [2/0->5/0[1]]" echo "routing done" media-ctl -d /dev/media0 -V "'os08a20 2-0036':0/0 [fmt:SBGGR10/3840x2160 field:none]" media-ctl -d /dev/media0 -V "'csidev-4ad30000.csi':0/0 [fmt:SBGGR10/3840x2160 field:none]" media-ctl -d /dev/media0 -V "'4ac10000.syscon:formatter@20':0/0 [fmt:SBGGR10/3840x2160 field:none]" media-ctl -d /dev/media0 -V "'crossbar':2/0 [fmt:SBGGR10/3840x2160 field:none]" media-ctl -d /dev/media0 -V "'mxc_isi.0':0/0 [fmt:SBGGR10/3840x2160 field:none]" echo "linking Completed " I run the following command to get the frames with v4l2 and I am able to get the expected 30 fps. v4l2-ctl -d /dev/video0 --set-fmt-video=width=3840,height=2160,pixelformat=BG10 --stream-mmap <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.04 fps <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.04 fps <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.04 fps I am trying to push it  to the display and i face this issue.  root@imx95-19x19-verdin:~# gst-launch-1.0 libcamerasrc ! video/x-raw,format=BGRx,width=3840,height=2160 ! videoconvert ! fpsdisplaysink video-sink=autovideosink text-overlay=true Setting pipeline to PAUSED ... [0:01:33.994814097] [774] INFO Camera camera_manager.cpp:326 libcamera v0.5.0+330-7fce0333-dirty (2025-06-04T12:23:54UTC) Pipeline is live and does not need PREROLL ... [0:01:34.098980249] [780] WARN ISI imx8-isi.cpp:353 Cannot find a supported YUV/RGB format Pipeline is PREROLLED ... Setting pipeline to PLAYING ... ERROR: from element /GstPipeline:pipeline0/GstLibcameraSrc:libcamerasrc0: Internal data stream error. Additional debug info: /usr/src/debug/libcamera/0.5.0.imx/src/gstreamer/gstlibcamerasrc.cpp(682): gst_libcamera_src_task_enter (): /GstPipeline:pipeline0/GstLibcameraSrc:libcamerasrc0: streaming stopped, reason not-negotiated (-4) ERROR: pipeline doesn't want to preroll. Execution ended after 0:00:00.000314034 Setting pipeline to NULL ... [0:01:34.099615025] [780] WARN ISI imx8-isi.cpp:353 Cannot find a supported YUV/RGB format ERROR: from element /GstPipeline:pipeline0/GstLibcameraSrc:libcamerasrc0: Internal data stream error. Additional debug info: /usr/src/debug/libcamera/0.5.0.imx/src/gstreamer/gstlibcamerasrc.cpp(682): gst_libcamera_src_task_enter (): /GstPipeline:pipeline0/GstLibcameraSrc:libcamerasrc0: streaming stopped, reason not-negotiated (-4) Freeing pipeline ... cam -c 1 --info [0:01:09.047021603] [772] INFO Camera camera_manager.cpp:326 libcamera v0.5.0+330-7fce0333-dirty (2025-06-04T12:23:54UTC) [0:01:09.152506530] [772] WARN ISI imx8-isi.cpp:353 Cannot find a supported YUV/RGB format Using camera /base/soc/bus@42000000/i2c@42530000/os08a20_mipi@36 as cam0 0: 3840x2160-SBGGR10 * Pixelformat: SBGGR10 (3840x2160)-(3840x2160)/(+1,+1) - 3840x2160 * Pixelformat: SBGGR12 (3840x2160)-(3840x2160)/(+1,+1) - 3840x2160 Till now I have not exported MATCH_LIST regarding the libcamera and the above are those logs. After this I export export LIBCAMERA_PIPELINES_MATCH_LIST='nxp/neo,imx8-isi' root@imx95-19x19-verdin:~# cam -c 1 --info [0:01:46.524765885] [782] INFO Camera camera_manager.cpp:326 libcamera v0.5.0+330-7fce0333-dirty (2025-06-04T12:23:54UTC) [0:01:46.642824790] [783] INFO NxpNeoIPA neo_ipa.cpp:128 nxpneo: IPANxpNeo NXPNEO_IPA_v0.5.0+330-7fce0333-dirty (2025-06-04T12:23:54UTC) Using camera /base/soc/bus@42000000/i2c@42530000/os08a20_mipi@36 as cam0 0: 3840x2160-BGR888 * Pixelformat: R8 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: R10 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: R12 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: R16 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: NV21 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: NV61 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: NV12 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: XBGR8888 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: BGR888 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: RGB888 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: XRGB8888 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: NV16 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: YUYV (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: XVUY8888 (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 * Pixelformat: UYVY (1920x1080)-(3840x2160)/(+0,+0) - 1920x1080 - 3840x2160 After this when I run the following gstreamer command the stream does not begin. There is no response for this process until it gets killed.  root@imx95-19x19-verdin:~# GST_DEBUG=3 gst-launch-1.0 libcamerasrc ! videoconvert ! autovideosink Setting pipeline to PAUSED ... [0:04:17.443233635] [794] INFO Camera camera_manager.cpp:326 libcamera v0.5.0+330-7fce0333-dirty (2025-06-04T12:23:54UTC) [0:04:17.562332552] [798] INFO NxpNeoIPA neo_ipa.cpp:128 nxpneo: IPANxpNeo NXPNEO_IPA_v0.5.0+330-7fce0333-dirty (2025-06-04T12:23:54UTC) Pipeline is live and does not need PREROLL ... 0:00:00.203418021 794 0xffffa4000b70 FIXME default gstutils.c:4169:gst_element_decorate_stream_id_internal: Creating random stream-id, consider implementing a deterministic way of creating a stream-id Pipeline is PREROLLED ... Setting pipeline to PLAYING ... 0:00:00.203987701 794 0xffffa4000b70 WARN default gstlibcamera-utils.cpp:345:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R10 0:00:00.204038448 794 0xffffa4000b70 WARN default gstlibcamera-utils.cpp:345:gst_libcamera_stream_formats_to_caps: Unsupported DRM format R12 New clock: GstSystemClock 0:00:00.204228106 794 0xffffa4000b70 WARN default gstlibcamera-utils.cpp:345:gst_libcamera_stream_formats_to_caps: Unsupported DRM format XVUY [0:04:17.578186764] [799] INFO Camera camera.cpp:1205 configuring streams: (0) 3840x2160-NV21 0:00:00.0 / 99:99:99. How to overcome this issue. Can you please guide me on this. Can you please provide a solution for this. Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? Hi, was this issue resolved ? Re: How to display video capture by OS08A20 camera via HDMI(LT8912)? No, it has not been resolved yet.

S32K324 M7コアの起動中に発生したハードフォールト 説明: S32K324 Cortex-M7コアの起動フェーズでHardFaultが発生しています。FEEデモに基づいてドライバを設定した後、 startup_cm7.s 内の _INIT_DATA_BSS() でプログラムが停止します 。 詳細： MCU: S32K324、デュアルCortex-M7 開発環境: S32DS + Segger J-Link コールスタックには次の内容が表示されます: HardFault_Handler() at exceptions.c:97 memset() at 0x40a66c init_data_bss() at startup.c:144 _INIT_DATA_BSS() at startup_cm7.s:565 リンカーセクション: .sram_bss (NOLOAD) : { *(.bss) *(.bss*) *(.mcal_bss) } > int_sram_c0 .bss_tcm_data (NOLOAD) : { *(.dtcm_bss*) } > int_dtcm HardFault は.bss_tcm_data の memset() 中に発生します 。 スタートアップ初期化のようです #S32K324 Re: HardFault during startup on S32K324 M7 core こんにちは@Changyukeさん 遅れて申し訳ありません。数日間オフィスを離れていました。 ldr r3, [pc, #12] str r0, [r3, #32] このコードは、まず PC + 12 のメモリ アドレスから 32 ビットの値を読み取り、それをレジスタ R3 にロードします。この値は通常、データ構造またはメモリ領域へのポインターを表します。 次に、直接ストア命令は、R0 の内容を R3 + 32 として計算されたメモリ アドレスに書き込みます。このCASE、0x20440020 に解決されます。 この障害は MPU または XRDC の構成が原因ではないため、その場所の SRAM が適切に初期化されていないことが原因であると考えられます。初期化は、32 ビット書き込みではなく、64 ビット整列書き込みを使用して実行する必要があります。初期化されていない領域に 32 ビット書き込みを試みると、不正確なバス障害が発生します。 main() の始めで、メモリを初期化CAN。 volatile uint64* ptr = (uint64*)0x20440000; *ptr = 0ULL; // Write 64-bit zero 逆アセンブリでは、STRD 命令が表示されます。 プロジェクトは Mem_43_INFLS_eJobRuntimeInfo を CAN 更新しますか? よろしくお願いいたします。 ダニエル Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applications or product design.  Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction. Re: HardFault during startup on S32K324 M7 core こんにちは@danielmartynek RTD を搭載した S32K324のデバッグ中に、アプリケーションが次の割り当てで常に HardFault に入ることを観察しました。 Mem_43_INFLS_eJobRuntimeInfo[インスタンスインデックス].JobResult = ジョブ結果;   デバッガーの観察: 変数 Mem_43_INFLS_eJobRuntimeInfo は 0x20440000 (サイズ: 40 バイト) にあります。 障害指示:   文字列 r0, [r3, #32] 例外レジスタ: CFSR = 0x00000400 (IMPRECISERR = 1) HFSR = 0x40000000 (強制 = 1) BFARVALID = 0 BFAR = 0x00000000 この現象は、上記の行が実行されるたびに再現されます。 アドバイスをお願いします: Mem_43_INFLS_eJobRuntimeInfo の正しい配置と構成については、どのドキュメントまたはアプリケーション ノートを参照すればよいですか? メモリ領域 (0x20440000) が有効であり、この変数に対して適切に初期化されているかどうかを確認するための推奨されるデバッグ方法はありますか? ありがとう、 チャンユケ Re: HardFault during startup on S32K324 M7 core こんにちは、ダニエル。 ご提案ありがとうございます。障害ステータス レジスタをチェックした結果は次のとおりです。 CFSR = 0x00000400 不正確さ = 1 精度 = 0 BFARVALID = 0 HFSR = 0x40000000 (強制 = 1) BFAR = 0x00000000 私も: MPU を無効にしました (プリプロセッサから MPU_ENABLE を削除しました)。 RM にリストされているオプション (オプション B core clk @120Mhz) に従ってシステム クロックを厳密に構成しましたが、システムは依然として HardFault 状態になります。 スタックから正確な障害命令をキャプチャする方法がよくわかりません。実際にこれをどのように行うのか明確にしていただけますか? 根本原因を絞り込む方法について、さらに何か提案はありますか? ありがとう、 チャンユケ Re: HardFault during startup on S32K324 M7 core こんにちは@Changyukeさん BFAR を使用した PRECISERR はまだ無効ですか? いずれにせよ、スタック中に障害が発生しない限り、スタック上に障害命令が表示されるはずです。https://community.nxp.com/t5/S32K-Knowledge-Base/S32K14x の障害処理/ta-p/1114447 POR 後、起動コードの先頭でそれをキャッチし、デバッガーをアタッチしてコードをステップ実行します。 Start: mov r0, #1 cmp r0, 0 /* change r0 to 0 in register view */ bne Start /* Capture after power-on reset */ MPU は system.c で無効に CAN します。MPU 領域が領域のサイズに揃っていない場合、予期しない動作が発生するCANがあります。 RMにリストされているクロックオプションの1つだけを使用してください。例：表158.オプション B - 低速モード (CORE_CLK @ 120 MHz)、その他の構成では予期しない動作が発生するCANがあります。 よろしくお願いいたします。 ダニエル Re: HardFault during startup on S32K324 M7 core こんにちは、ダニエル。 申し訳ありませんが、当初は問題は解決したと思っていましたが、さらにテストを行ったところ、特定の条件下では問題がまだ残っています。 S32K344 FEE デモを参照して、S32K324 で FEE 機能をテストしています。システムは、main() に到達する前に、起動フェーズ中に HardFault に入ります。リンカー ファイルおよびその他の構成は変更されていません。 観察された動作: 最初に NXP S32K344 FEE デモをフラッシュし、次に S32K324 プロジェクトをフラッシュすると、プログラムは正常に起動します。 S32K324 プロジェクトを直接フラッシュすると、電源投入時にシステムが常に HardFaults になります。 試みと観察: CPU 周波数を 80 MHz に下げても問題は解決しません。 FEE/Flash 初期化 (つまり、MemAcc_Init と Fee_Init) をコメント アウトしても、HardFault が発生します。 Core0 と Core1 のフラッシュ順序は現象に影響しません。 短い電源サイクルでは一貫して動作しますが、長期間の電源オフ (数日間) の後、電源オン時にシステムが再び HardFaults になります。 この問題は、起動メモリ、MPU/キャッシュ/TCM 構成、または電源投入時のフラッシュの準備状況に関連している可能性があると思われます。 S32K3xx デバイスで同様の動作に遭遇した方はいらっしゃいますか? また、推奨されるトラブルシューティング手順は何でしょうか? ご指導いただければ幸いです。 よろしくお願いいたします。 チャンユケ 回复： HardFault during startup on S32K324 M7 core こんにちは、ダニエル。 MEMACC 設定を更新し、FEE メイン関数の期間を調整したところ、すべて正常に動作するようになりました。助けてくれてありがとう！ Re: HardFault during startup on S32K324 M7 core こんにちは、ダニエル。 早速のご返信ありがとうございます。 HardFault 中に障害ステータス レジスタをチェックしました。 CFSR = 0x00000400 (PRECISERR、正確なデータバスエラー) HFSR = 0x40000000 (強制) MMFAR = 0 外径 = 0 コンテキスト: FEE モジュールを統合する前は、プログラムは HardFault なしで正常に実行されます。この障害は、デモに従って FEE を設定および統合した後にのみ発生するため、問題は FEE 初期化シーケンスに関連していると考えられます。 また、デフォルトのリンカー ファイルやスタートアップ コードは変更していません。これらは SDKs の元のコードのままです。 よろしくお願いいたします。 チャンユケ Re: HardFault during startup on S32K324 M7 core こんにちは@Changyukeさん それはどのような障害例外ですか? CAN 構成可能障害ステータス レジスタ (CFSR) を読み取りますか? https://developer.arm.com/documentation/ddi0403/d/System-Level-Architecture/System-Address-Map/System-Control-Space--SCS-/Configurable-Fault-Status-Register--CFSR デフォルトのリンカー ファイルとスタートアップ コードを変更しましたか? もしSOなら、ファイルを共有してください。 よろしくお願いいたします。 ダニエル

SNVS Mode RT1176 Hello, we've an RT1176 on custom hardware and use the internal RTC in SNVS domain. I've managed to get current consumption to 3,8uA when putting MCU in SNVS mode. So the system will go into SNVS mode by setting TOP bit in LPCR register when power fail occurs. But afterwards the system won't power on due to PMIC_ON_REQ is held low. Actual I keep all but instead of setting TOP bit the systen stuck in while loop until power supply shut down. In this state the current consumption from coin cell is 3,8uA and all is fine. But without setting TOP bit in LPCR I'm not sure if the MCU is in SNVS mode so I'm not sure if there will be any unwanted behavior and my system will drain my coin cell. Can someone clarify in which state the MCU will be? I'm not configure any setpoint or another energy mode. just power down all except VDD_SNVS_IN. Another hint just for anyone trying to mesaure RTC consumption. When debugger is connected (we're using Segger JLink) the current will increase to ~60uA.  Best Regards Re: SNVS Mode RT1176 SNVS mode is the state where all power domains are off with the exception of SNVS. To access SNVS either you press the ON/OFF for more than five seconds or set the TOP bit. If you don’t do any of these then the system will not be on SNVS. If you don't set TOP and everything is off except SNVS mode, it still is SNVS mode. BR, Omar

S32K144 UART problem Hello everyone, I have a prolblem when using the UART example code. I just plugged and flashed the example code but nothing happend. The IDE is S32DS version 3.6.3, the board I use is S32K144 EVB Q100, the RTD I use is version 4.4 and Hercules for display data (baurate in both side is 19200) Thanks for reading. Re: S32K144 UART problem Hi @Andrew101, S32K144 UART example from RTD uses UART0 and FlexIO to test communication: You can scope these pins to see the transmission. Or you can wait for the example to compare verify the transmissions. From the description.txt file: - The first welcome message is sent via UART: "Hello, This message is sent via Uart!" - The second welcome message is sent via UART: "Have a nice day!" - User need to check return status of Send_Data() function for verifying example.   It uses Lpuart instance 0, comunicates with Flexio instance 0 channel 0 for Rx and channel 1 for Tx (connect PTC3 (J4.16) - PTD2(D6)(J6.3) and PTB0 (J4.5) - PTE5(D7)(J6.18)).   Best regards, Julián

ROS2 on i.MX93 SOM EVK Has anyone tried using the ROS2 on i.MX93 in the M33 cortex with FreeRTOS? I am trying to integrate the microros in the freeRTOS provided in the SDK for the imx93. How to add the required files to the sdk project, or any other alternative way to run micro-ros as well as SDK examples. Anything remotely close to the answers are also welcome, that might open a new perspective. Thank You. Re: ROS2 on i.MX93 SOM EVK Thank you @Daniel for the reply , Missed quite a few details on the query posted at first, that i will mention now: Hardware Environment：     I.MX93 EVB Software Environment:     Ubuntu 22.04     IDE：VSCode with MCUXpresso IDE      SDK：SDK Builder | MCUXpresso SDK Builder (nxp.com) Requirement: to use the microros in the m33 core of the IMX93 EVB and use RPmsg instead of UART communication to the processor. By following the steps mentioned in the "Porting Micro-ROS on Frdm-MCXN947" , i was able to create the static library "libmicroros.a" and the header files. how can i integrate this in the firmware ? how to combine this with the freeRTOS example codes provided in the SDK example. since we cannot use direct mcuxpresso ide for the imx93, using  the extension on the VSCode, in this how can i link the generated static libraries as well as the header files for this one. Does VSCode provides this linking section anywhere?  Only in the cmakelist.txt has the details regarding the libraries, but how can i link the static library and the header files that i have generated by following the link you have provided.  cmakelist & main files are attached. Re: ROS2 on i.MX93 SOM EVK Hi I would suggest you refer to below article, porting Micro-ROS on Frdm-MCXN947.    The MCXN947 is an M33 core.  Porting Micro-ROS on Frdm-MCXN947 - NXP Community Regards Daniel Re: ROS2 on i.MX93 SOM EVK Can i get an update on this please?

S32G399a-rdb3 PFE2 ping doesn't work I'm trying to bring up QNX 8 io-sock on S32G399a-rdb3 board bsp 44.0 PFE Driver 1.9.0 PFE FW 1.8.0 Here's what I do to call io-sock process io_sock.cfg content :  ( if I added hw.pfe.2.phy_address="4" as mentioned in the Release notes of the driver I get no phy at loc:4 phy failed to attach ) from inside QNX : I still can't ping the ECU from the laptop or vice versa I tried to configure pfe from uboot ( since it's working there if configured ) then make qnx act as a slave but I got undefined reference  What am I missing? GoldVIP Re: S32G399a-rdb3 PFE2 ping doesn't work Hi Hesham, PFE driver for QNX 8.0 is only in Proof of Concept level and might have some problems which are not resolved yet. The configuration for PFE use in QNX is a little bit tricky, you need to configure HW and clocks in u-boot before starting QNX, as we don't have SerDes implementation in QNX driver. APP FSM timeouts means, that FSM clocks are not configured correctly. I recommend to use u-boot BSP 39.0 with DTB and ATF. Inside this u-boot, there is PFE driver which will configure all the settings before booting QNX. Please follow PFE QNX Integration Manual from Release package doc/qnx_drv_im/PFE_QNX_DRV_IntegrationManual.pdf Regards Milan Re: S32G399a-rdb3 PFE2 ping doesn't work Hello @Hesham_Gharabawy, Thanks for reaching out to us. Reading your problem, in this community we cannot support QNX software, since it is not an NXP product, we do not have the knowledge to helpyou, I would recommend contacting QNX support directly https://blackberry.qnx.com/en/company/contact. With that said, I am aware that QNX uses the same boot flow and it is an unix-like OS, just as Linux. Therefore sections 7.3 Ethernet Software support on S32G3 and 7.2.2 SerDes configuration for SGMII in U-Boot may help you with your problem. If you need support testing the ping command in u-boot alone, please let me know which port of the RDB3 you are trying to use and I can guide you. Best regards

Flexbuild を使用して、i.MX8M Plus EVK 上の eMMC に Debian イメージをフラッシュする方法を教えてください。 こんにちは、皆さん。 私は i.MX8M Plus EVK を使用して、NXP の Flexbuild システムを使用して Debian イメージを生成しています。 これまでのところ、flex-installer を使用してイメージをビルド、カスタマイズし、SD カードにフラッシュすることができ、正常に起動します。 ここで、SD から起動するのではなく、同じ Debian イメージをオンボード eMMC に展開したいと思います。 Flexbuild ユーザーガイドから、flex-installer が「SD/eMMC カードまたは USB/SATA ディスク」へのインストールをサポートしていることに気付きましたが、i.MX8M Plus EVK での eMMC の明確な例や手順は見つかりませんでした。 Flexbuild ツールを使用して Debian イメージを eMMC にフラッシュするための公式ワークフローはありますか? rootfs を準備した後、U-Boot (mmc dev、mmc write) を使用してブートローダー + パーティション分割を手動で処理する必要がありますか、それともこのための既製のスクリプトがありますか? Yocto BSP では通常、uuu/imx-uuc を使用して eMMC にフラッシュしますが、Debian Flexbuild では同様のフローは見当たりません。あるんですか？ 詳細な手順や参考資料があれば幸いです。 ありがとうございます。 Re: How to use Flexbuild to flash Debian image into eMMC on i.MX8M Plus EVK? ここに解決策を投稿していただけますか?私はimx8mp-evkの新しい開発者です。同じ問題が発生します。 Re: How to use Flexbuild to flash Debian image into eMMC on i.MX8M Plus EVK? flex-installer は、これらのイメージを eMMC に展開するために使用されます。 Re: How to use Flexbuild to flash Debian image into eMMC on i.MX8M Plus EVK? 私はそれを解決します

SJA1110B こんにちは、 2 つの 4 線式イーサネット (ETH1、ETH2) 10/100 Mbps があります。 PHY から ETH1 を MII2 に、ETH2 を MII3 にCAN接続しますか。RMII のみを使用しています。 お知らせください。 敬具 ジョシュア Re: SJA1110B こんにちは@joshHeavyEquipさん、 はい、CAN。SJA1110B は、ポート 2 とポート 3 に 2 つの MII/RMII/RGMII インターフェースを提供します。当然、MII/RMII/RGMII は設定可能です。 よろしくお願いいたします。 パベル

IMX8M PLUS 的 SDK 你好， 我正在开始使用 i.MX 8M Plus 处理器进行开发，我需要指导如何使用哪个 SDK/工具链来版本我的项目和生成将在处理器上运行的二进制文件。 对于 CORTEX A53（Linux/Android 端）： -我应该使用恩智浦的电路板支持包来构建 Linux 镜像和应用程序吗？ -对于应用程序开发（例如Qt GUI、多媒体），我是否使用从（交叉编译环境）生成的SDK/工具链，还是有单独的SDK代码包？ Re: SDK for IMX8M PLUS 您好@parvathitp， 感谢您联系恩智浦支持中心！ 对于 Linux 开发，你可以使用 ARM 工具链；但是，我建议生成 Yocto SDK 以获得完全兼容的工具链来交叉编译应用程序。 您可以从以下链接找到 Yocto SDK 的部署说明： https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/How-to-compile-Linux-Kernel-Image-and-device-tree-using-Yocto/ta-p/2022759 致以最崇高的敬意， Chavira

KW45 / MCXW71 Differences and Software Configurations Dear Team, Thank youf or your support. We are currently using your NXP KW45 series MCU for a BLE Specific application which does not require CAN. I came across another MCU from NXP - MCX-W71.  As of what I can see there is not much difference apart from support of CAN Protocol. Can you let me know if there are any other major differences ? Regarding SW -  We have nearly developed your KW45 SW and would like to Migrate to MCXW71 willl it be possible ? If we directly flash our SW, will it work ? BR, Tomaru KW45B41Z-EVK KW45 MCX-W71X MCX-W72X  Re: KW45 / MCXW71 Differences and Software Configurations Hi， @tomaru  Thanks for creating case to us and choosing our products. KW45 and MCXW71 are software compatible. The difference is mainly from production process which following different manufacture rules . KW45 is used for automotive, and MCXW71‘s aim area is for IOT industry. So, back to your question,  We have nearly developed your KW45 SW and would like to Migrate to MCXW71 willl it be possible ? If we directly flash our SW, will it work ? ==>Yes, you can migrate from KW45 to MCXW71.  Before directly flash SW, please double confirm whether have any special macro defined for KW45 in your SW. If has, please remember to change them to adapt for MCXW71. Please let me know whether have any other concerns on this case. If no, please help to mark my answer as a solution for this case, so that we can close it. And do not hesitate to create new case to us if you meet any other issue when using our product. Best regards, Christine.

通过 FPGA 的 QSPI 接口对 MIMX8ML8CVNKZAB 进行 DMA 访问 我们正计划通过 QSPI 接口访问 I.MX8M 加 (MASTER) DMA，FPGA 作为从站。 我们无法找到足够的信息来访问 DMA。请分享访问 DMA i.MX8M plus 芯片的程序/算法。 还要提供 i.MX8M 和 DMA 访问权限是否有任何参考可用。 期待您的回音。 在此先表示感谢......！ Re: DMA access of MIMX8ML8CVNKZAB over QSPI interface with FPGA 另请参阅以下链接、 通过 FlexSPI 扩展 i.MX8M/93 连接 FPGA/CPLD 的能力 - NXP Community Re: DMA access of MIMX8ML8CVNKZAB over QSPI interface with FPGA 你好 mk： Linux 手册》第 3.5 节介绍了 QSPI 驱动程序。 i.MX Linux 参考手册 此致 丹尼尔

エラーメッセージ「ダンプファイルを開けませんでした」 統合ブートローダ デモ v2.1 ソフトウェア パッケージの S32k344 の例を使用したところ、コンパイル プロセスでエラーが報告されました。 Re: Error message "could not open dump file" こんにちは、VaneB インストール環境をCドライブに変更したら問題はなくなりました。ソフトウェアのバージョンはまったく変更されていません。 ありがとうございます。 Re: Error message "could not open dump file" こんにちは@Aurora_J 前述のとおり、互換性の問題や予期しない動作を防ぐために、S32 Design Studio バージョン 3.4 を使用することをお勧めします。 Re: Error message "could not open dump file" プロジェクトの設定を変更しておらず、RTD 2.0 はすでにインストールされています。 Re: Error message "could not open dump file" こんにちは@Aurora_J プロジェクトに何か変更を加えましたか?また、RTD バージョン 2.0.0 をインストールしましたか? このプロジェクトは S32 Design Studio バージョン 3.4 を使用して開発されたSO、問題を回避するために、一致するソフトウェアとツールのバージョンを使用していることを確認してください。 BR、ヴェインB

S32K3xx Config Rx Mailbox Hello team, We are trying to configure Global mask for FlexCAN RX mailbox. But it is going in hardfault condition.  Kindly need your support in above issue. Is it possible configure Global mask and receive CAN Msg for any CAN Id?  Currently we are configuring every RX CAN Mailbox ID using configRxMB() api. But configuring RX mailbox ID's there is a limitation of 32 Id only. If it is possible to set Global Mask for RX Mailbox, it would be possible to receive for any CAN Id. Thanks, Vinay Re: S32K3xx Config Rx Mailbox Thank you Julián_AragónM. This solved my issue.  Re: S32K3xx Config Rx Mailbox Hi @vinaykl, In order to receive all CAN IDs, you can configure the global mask for "don't care" (0b): For example: FlexCAN_Ip_SetRxMbGlobalMask(INST_FLEXCAN_0, 0U); Best regards, Julián