RT1170 support QSPI Flash (MX25L51245G ) Hi, Can RT1170 support MX25L51245G for QSPI flash? Do it need to modify the configuration file “evkmimxrt1170_flexspi_nor_config.c” to meet this chip? If so, how to modify it? Which parameters should be modified? Thanks for your support! Best regards, WJC Re: RT1170 support QSPI Flash (MX25L51245G ) Hello @jeremyzhou  We are using the MX25L51245G external flash and RT1176 and have implemented the configuration shown below. It works flawlessly in XIP mode, but I would like to get a validation from you as well. However, when running a multicore application in "Link application mode", the system hits a hardfault. Specifically, it triggers an assert due to the value read from the FlexCAN MCR register. I am attaching some screenshots and my lookup table below for your reference. M7 flash init(RAM): M4 flash init(RAM): hardfault for multicore(RAM): Here is the lookup table configuration designed to support the software running seamlessly in both RAM and XIP (Execute-in-Place) modes:   #define FLASH_DUMMY_CYCLES 0x08 const flexspi_nor_config_t qspiflash_config = { .memConfig = { .tag = FLEXSPI_CFG_BLK_TAG, .version = FLEXSPI_CFG_BLK_VERSION, .readSampleClksrc=kFlexSPIReadSampleClk_LoopbackFromDqsPad, .csHoldTime = 3u, .csSetupTime = 3u, .controllerMiscOption = 0x10, .deviceType = kFlexSpiDeviceType_SerialNOR, .sflashPadType = kSerialFlash_4Pads, .serialClkFreq = kFlexSpiSerialClk_133MHz, //okuma hatasi olursa kFlexSpiSerialClk_120MHz .sflashA1Size = 64u * 1024u * 1024u, //64MB //Her acilista QE = 1. ROM once WREN'i (seq 3) kendisi gonderir, sonra 4*12'yi 0x40 ile calistirir. //NXP RT1170 EVK'daki configCmd kalibinin aynisi .configCmdEnable = 1u, .configModeType[0] = kDeviceConfigCmdType_Generic, .configCmdSeqs[0] = {.seqNum = 1u, .seqId = 12u, .reserved = 0u}, //1 tane sequence calistir: 4*12 //asagiyi 0x20 yapinca calismadi dogrudan memory hatasinda patladi main'e gelmeden .configCmdArgs[0] = 0x40u, //WRITE_SDR'nin gonderecegi byte: SR = 0x40 .lookupTable = { [0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x6C, RADDR_SDR, FLEXSPI_1PAD, 0x20),//6Ch QREAD4B: komut ve 4 byte adres tek hattan (1-1-4) [1] = FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, FLASH_DUMMY_CYCLES, READ_SDR, FLEXSPI_4PAD, 0x04),//8 dummy bekle, data 4 hattan [4 * 1 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x05, READ_SDR, FLEXSPI_1PAD, 0x04),//status regini 0x05'den okuyacam (WIP = bit0) [4 * 3 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x06, STOP, FLEXSPI_1PAD, 0x0),//write en ettim //asagidakini yoruma alinca gercekten silmedi [4 * 5 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x21, RADDR_SDR, FLEXSPI_1PAD, 0x20),//4 byte adress alarak 4 kb sector silecem [4 * 8 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xDC, RADDR_SDR, FLEXSPI_1PAD, 0x20),//64 kb block silecem(app'de kullanmiyoruz) [4 * 9 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x12, RADDR_SDR, FLEXSPI_1PAD, 0x20),//4 byte 1 page yazacam [4 * 9 + 1] = FLEXSPI_LUT_SEQ(WRITE_SDR, FLEXSPI_1PAD, 0x04, STOP, FLEXSPI_1PAD, 0x0),//datayi gonder ve bitir (WEL'i flash program bitince kendisi temizler) [4 * 11 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xC7, STOP, FLEXSPI_1PAD, 0x0),//tum flashi silecem(app'de kullanmiyoruz) [4 * 12 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x01, WRITE_SDR, FLEXSPI_1PAD, 0x01),//WRSR + tam 1 byte (configCmdArgs[0]): sadece SR yazilir, CR'ye dokunmaz //seq 6/7 bos: ROM API suspend/resume kullanmiyor }, }, .pageSize = 256u, .sectorSize = 4u * 1024u, .ipcmdSerialClkFreq = 0x1, .blockSize = 64u * 1024u, .isUniformBlockSize = true, }; Re: RT1170 support QSPI Flash (MX25L51245G ) Hi, Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you. 1) Can RT1170 support MX25L51245G for QSPI flash? -- Yes. 2) Do it need to modify the configuration file “evkmimxrt1170_flexspi_nor_config.c” to meet this chip? -- Yes, please refer to the below code. const flexspi_nor_config_t qspiflash_config = { .memConfig = { .tag = FLEXSPI_CFG_BLK_TAG, .version = FLEXSPI_CFG_BLK_VERSION, .readSampleClksrc=kFlexSPIReadSampleClk_LoopbackFromDqsPad, .csHoldTime = 3u, .csSetupTime = 3u, // Enable DDR mode, Wordaddassable, Safe configuration, Differential clock .sflashPadType = kSerialFlash_4Pads, .serialClkFreq = kFlexSpiSerialClk_100MHz, .sflashA1Size = 64u * 1024u * 1024u, .lookupTable = { // Read LUTs FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xEB, RADDR_SDR, FLEXSPI_4PAD, 0x20), FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, 0x06, READ_SDR, FLEXSPI_4PAD, 0x04), }, }, .pageSize = 256u, .sectorSize = 4u * 1024u, .blockSize = 256u * 1024u, .isUniformBlockSize = false, }; Have a great day, TIC ------------------------------------------------------------------------------- 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. -------------------------------------------------------------------------------

imx93 lvds with kernel 6.12 I'm trying to make an LVDS display work on an imx93 custom board. I'm struggling with this error : imx-lcdif 4ae30000.lcd-controller: probe with driver imx-lcdif failed with error -2 After adding some traces, this comes from this line in the driver (in function lcdif_load) lcdif->clk_axi = devm_clk_get(drm->dev, "axi"); if (IS_ERR(lcdif->clk_axi)) return PTR_ERR(lcdif->clk_axi); So, it seems it cannot find the "axi" clock. I'm using the device tree from the kernel, imx93.dtsi, as the base, which includes the following lines: clock-names = "pix", "disp-axi", "disp-apb"; assigned-clocks = <&clk IMX93_CLK_VIDEO_PLL>, <&clk IMX93_CLK_MEDIA_DISP_PIX>, <&clk IMX93_CLK_MEDIA_AXI>, <&clk IMX93_CLK_MEDIA_APB>; So there's some inconsistency here between the device tree and the driver here. Problem is that i don't know if the clocks are correct, which ones i should use. I tried to have a look to what is in the 6.18 branch, but this part (lcdif controller) has completely disappeared from the imx93.dtsi file. Any hints? Re: imx93 lvds with kernel 6.12 Ok, found one cause, this was using the wrong driver. Now, with the lcdif_v3 driver, no clock issues. On the other hand, i still get this problem imx93-ldb ldb-display-controller: Failed to create device link (0x180) with 4ae30000.lcd-controller Any hints ? Re: imx93 lvds with kernel 6.12 Hello @julienblanc  Hope you are doing very well. Are you still having the issue? Best regards, Salas. Re: imx93 lvds with kernel 6.12 Unfortunately, no. I keep having the same error. Here's how i tried to configure things : backlight_lvds: backlight-lvds { compatible = "pwm-backlight"; status = "okay"; power-supply = <&display_power_12v>; brightness-levels = < 0 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100>; default-brightness-level = <30>; pwms = <&pwm_backlight 0 1000000 0>; }; pwm_backlight: pwm_gpio { compatible = "pwm-gpio"; #pwm-cells = <3>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_clko4_gpio>; gpios = <&gpio4 29 GPIO_ACTIVE_HIGH>; // gpio controller &gpio4, pin 29 status = "okay"; }; panel { compatible = "panel-lvds"; width-mm = <224>; height-mm = <126>; backlight = <&backlight_lvds>; status = "okay"; port { panel_in: endpoint { remote-endpoint = <&lvds_ldb_out>; }; }; panel-timing { clock-frequency = <72400000>; hactive = <1280>; vactive = <800>; hfront-porch = <72>; hback-porch = <88>; hsync-len = <20>; vfront-porch = <15>; vback-porch = <23>; vsync-len = <10>; de-active = <1>; pixelclk-active = <1>; }; }; &ldb { status = "okay"; lvds-channel@0 { #address-cells = <1>; #size-cells = <0>; status = "okay"; port@1 { reg = <1>; lvds_ldb_out: endpoint { remote-endpoint = <&panel_in>; }; }; }; &ldb_phy { status = "okay"; }; display_power is a gpio-hog on an exander : display_power_12v: gpio_regulator { gpio-hog; gpios = <12 GPIO_ACTIVE_HIGH>; output-high; label = "DISPLAY12V"; }; This is mostly taken from some examples in the device-trees. I can't get what's wrong, or why it won't bring the display up, even not the backlight. I know i should use a TPM instead of a software gpio, but that need a hardware fix, currently i have to deal with it and i don't think that's the problem. Thanks for your support, Regards, Julien Re: imx93 lvds with kernel 6.12 For anyone interested, i finally got it working, even with the soft pwm. Causes were : * missing modules in kernel compilation (CONFIG_BACKLIGHT_CLASS_DEVICE=y , CONFIG_BACKLIGHT_PWM=y ,CONFIG_DRM_PANEL_LVDS=y ) * backlight must use a regulator for power supply

RT1160 扩频器崩溃了…… 我正在寻求帮助，我已经查看了所有其他论坛帖子，并按照我能找到的所有方法操作，但在尝试在 RT1160 MCU 上启用扩频时仍然会崩溃。 从截图中可以看到，我已经移动了 fsl_clock.o到 RAM 以及 *flexspi.o写入内存。 使用 Segger Ozone，您可以准确地看到崩溃发生的位置，以及生成的异常和异常寄存器设置。 知道这里出了什么问题吗？ Re: RT1160 Spread Spectrum crashing... 嗨@application_ninja ， 虽然你已经移动了 fsl_clock.o向 RAM 传输数据时，函数 SDK_DelayAtLeastUs() 位于 fsl_common_arm.o 文件中。它仍然驻留在闪存中。至少，所有用于更改时钟的调用链都应该位于内部 RAM 中。这就是为什么在 AN12879（如何为 RT 系列启用扩频）中，所有代码都加载在 ITCM 或 DTCM 上的原因。 Re: RT1160 Spread Spectrum crashing... 感谢您的回复，但是需要移动 fsl_common_arm.o仍然会导致设备崩溃。但这一次它确实通过了“SDK_DelayAtLeastUs”，但崩溃非常严重，调试器不会停下来记录崩溃发生的位置。 该程序非常庞大，我无法在 ITCM / DTCM 中全部运行。

RT1170はQSPIフラッシュ(MX25L51245G)をサポートしています こんにちは、 RT1170はQSPIフラッシュのMX25L51245Gをサポートしていますか? このチップに対応するために、設定ファイル「evkmimxrt1170_flexspi_nor_config.c」を変更する必要がありますか？ もしSOなら、どうやって修正すればいいのでしょうか?どのパラメータを変更すべきでしょうか？ ごサポートありがとうございます! よろしくお願いいたします。 世界ジュニア会議 Re: RT1170 support QSPI Flash (MX25L51245G ) こんにちは、 @jeremyzhou 弊社では、MX25L51245G外部フラッシュメモリとRT1176を使用しており、以下の構成を実装しています。XIPモードでは問題なく動作しますが、念のため貴社からも確認をいただきたいです。 しかし、「リンクアプリケーションモード」でマルチコアアプリケーションを実行すると、システムはハードフォールトに遭遇します。具体的には、FlexCAN MCRレジスタから読み取った値によってアサートがトリガーされます。 参考までに、スクリーンショットとルックアップテーブルを以下に添付します。 M7フラッシュ初期化（RAM）： M4フラッシュ初期化（RAM）： マルチコア(RAM)のハードフォルト: こちらはRAMモードとXIP(Execute-in-Place)モードの両方でシームレスに動作するソフトウェアをサポートするために設計されたルックアップテーブルの構成です:   #define FLASH_DUMMY_CYCLES 0x08 const flexspi_nor_config_t qspiflash_config = { .memConfig = { .tag = FLEXSPI_CFG_BLK_TAG 、 .version = FLEXSPI_CFG_BLK_VERSION、 .readSampleClksrc= kFlexSPIReadSampleClk_LoopbackFromDqsPad 、 .csHoldTime = 3u、 .csSetupTime = 3u、 .controllerMiscOption = 0x10、 .deviceType = kFlexSpiDeviceType_SerialNOR 、 .sflashPadType = kSerialFlash_4Pads、 .serialClkFreq = kFlexSpiSerialClk_133MHz , //オクマハタシオルルサkFlexSpiSerialClk_120MHz .sflashA1Size = 64u * 1024u * 1024u, //64MB //彼女のアシリスタQE = 1. ROM 1 回 WREN'i ( seq 3) kendisi gonderir 、 sonra 4*12' yi 0x40 ile calistirr 。 //NXP RT1170 EVK'daki configCmd kalibin aynisi .configCmdEnable = 1u、 .configModeType[0] = kDeviceConfigCmdType_Generic、 .configCmdSeqs[0] = {.seqNum = 1u, .seqId = 12u, .reserved = 0u}, //1 taneシーケンスcalistir : 4*12 // asagiyi 0x20ヤピンカカリスマディドグルダンメモリハタシンダパトラディメインエゲルメデン .configCmdArgs[0] = 0x40u, //WRITE_SDR'nin gonderecegi byte: SR = 0x40 .lookupTable = { [0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x6C, RADDR_SDR, FLEXSPI_1PAD, 0x20), //6Ch QREAD4B: komut ve 4 byte adres tek hattan (1-1-4) [1] = FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, FLASH_DUMMY_CYCLES, READ_SDR, FLEXSPI_4PAD, 0x04), //8 ダミーベール、データ 4ハットン [4 * 1 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x05, READ_SDR, FLEXSPI_1PAD, 0x04), //ステータスregini 0x05'den okuyacam (WIP = bit0) [4 * 3 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x06, STOP, FLEXSPI_1PAD, 0x0), //書き込み完了 //アサギダキニヨルマアリンカゲルツェクテンシルメディ [4 * 5 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x21, RADDR_SDR, FLEXSPI_1PAD, 0x20), //4 バイトアドレスalarak 4 kbセクターsilecem [4 * 8 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xDC, RADDR_SDR, FLEXSPI_1PAD, 0x20)、 //64 kbブロック サイセム(アプリ デkullanmiyoruz ) [4 * 9 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x12, RADDR_SDR, FLEXSPI_1PAD, 0x20), //4バイト1ページyazacam [4 * 9 + 1] = FLEXSPI_LUT_SEQ(WRITE_SDR, FLEXSPI_1PAD, 0x04, STOP, FLEXSPI_1PAD, 0x0), // datayi gonder ve bitir (WEL'i フラッシュ プログラム ビットインスkendisi temizler ) [4 * 11 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xC7, STOP, FLEXSPI_1PAD, 0x0), // tum flashi silecem (app'de kullanmiyoruz ) [4 * 12 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x01, WRITE_SDR, FLEXSPI_1PAD, 0x01), //WRSR + tam 1 バイト (configCmdArgs[0]): sacece SR yazilir , CR'ye dokunmaz // seq 6/7 bos : ROM API サスペンド/レジュームkullanmiyor }、 }、 .pageSize = 256u、 .sectorSize = 4u * 1024u、 .ipcmdSerialClkFreq = 0x1、 .blockSize = 64u * 1024u、 .isUniformBlockSize = true、 }; Re: RT1170 support QSPI Flash (MX25L51245G ) こんにちは、 NXP Semiconductors製品へのご関心と、皆様にお仕えできる機会をいただき、ありがとうございます。 1) RT1170はQSPIフラッシュのMX25L51245Gをサポートしていますか? ――はい。 2) このチップに合わせて設定ファイル「evkmimxrt1170_flexspi_nor_config.c」を変更する必要がありますか? はい、下記のコードをご参照ください。 const flexspi_nor_config_t qspiflash_config = { .memConfig = { .tag = FLEXSPI_CFG_BLK_TAG, .version = FLEXSPI_CFG_BLK_VERSION, .readSampleClksrc=kFlexSPIReadSampleClk_LoopbackFromDqsPad, .csHoldTime = 3u, .csSetupTime = 3u, // Enable DDR mode, Wordaddassable, Safe configuration, Differential clock .sflashPadType = kSerialFlash_4Pads, .serialClkFreq = kFlexSpiSerialClk_100MHz, .sflashA1Size = 64u * 1024u * 1024u, .lookupTable = { // Read LUTs FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xEB, RADDR_SDR, FLEXSPI_4PAD, 0x20), FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, 0x06, READ_SDR, FLEXSPI_4PAD, 0x04), }, }, .pageSize = 256u, .sectorSize = 4u * 1024u, .blockSize = 256u * 1024u, .isUniformBlockSize = false, }; 良い一日をお過ごしください。 TIC ------------------------------------------------------------------------------- 注記： この投稿があなたの質問への回答になっている場合は、「正解としてマーク」ボタンをクリックしてください。ありがとう！ - 前回の投稿から7週間Threadをフォローしており、その後の返信は無視しています もし後で関連する質問があれば、新しいThreadを開き、閉じたThreadを参照してください。 -------------------------------------------------------------------------------

imx95とvfio_pciパススルー こんにちは、 IMX95 SoC上でPCIパススルー機能を備えた仮想マシンを使用したいと考えています。しかし、SMMUはキャッシュコヒーレントではなく、vfio_pciドライバーがそれを必要としているため、これは全く不可能のようです。関連項目： https://community.nxp.com/t5/i-MX-Processors/i-MX95-19x19-EVK-SMMU-coherent-table-walks-IDR0-COHACC-and-vfio/mp/2410515 そして https://github.com/NXP/dpdk/blob/25.11-qoriq/nxp/README_imx95_enetc_vf_vfio#L32 IOMMUを無効にすることはできません。また、カーネルパラメータが次のように書かれているので、役に立つとは思えません。 MODULE_PARM_DESC(enable_unsafe_noiommu_mode, "安全でない、IOMMUなしモードを有効にします。このモードはデバイス隔離を提供せず、DMA変換もホストカーネル保護も提供せず、 仮想マシンへのデバイス割り当てには使用できず、RAWIO権限が必要で、カーネルを汚染します。これが何のためにあるのか分からない場合は、離れてください。（デフォルト：false）""); IMX95 SoCを(安全な)PCIパススルーで使うのは本当に不可能なのでしょうか?そうでないなら、私が何か見落としているのでしょうか？ よろしくお願いします、 マイケル Re: imx95 and vfio_pci passthrough こんにちは、 迅速なご回答ありがとうございます。でも、完全に理解できているかどうか自信がありません。念のため確認ですが、DPDKは使用せず、PCIデバイスをパススルーする汎用的なqemu/kvm仮想マシンを使用したいと考えています。これはuio-pci-genericフレームワークとどのように関連しているのでしょうか？ ありがとう、 マイケル Re: imx95 and vfio_pci passthrough こんにちは、 NXP Semiconductors製品にご関心いただきありがとうございます。 この場合、DPDKチームの同僚の回答に従う必要があります。唯一の選択肢は、回答で述べられているものです。 「顧客が他の用途でSMMUを使いたいが、DPDKではバイパスしても許容される場合(bootargsでiommu.passthrough=1を使いたくない、DTSでSMMUノードを無効にしたくない場合)。 その後、uio-pci-genericフレームワークのバインドを試み、VSI-PSIメッセージングを無効にすることができます(エクスポートENETC4_VSI_MSG_DISABLE=1)。しかしVSI-PSIメッセージを無効にすると、ユーザーはpromisc、VLAN MACフィルタリング、リンク情報などのENETC機能の一部を使えなくなります。」 よろしくお願いします。 Re: imx95 and vfio_pci passthrough こんにちは、 この話題に関して何かニュースはありますか? よろしくお願いします、 マイケル

Ara Vision Examples Multi-Stream YOLOv8 Object Detection  This post shows a walkthrough of the ARA2 Vision Examples demo and its multi-stream YOLOv8 object detection application. The ara2-vision-examples demo provides vision AI examples for NXP i.MX platforms using Ara240 DNPU acceleration. It demonstrates real-time video processing with AI/ML inference capabilities such as object detection, classification, pose estimation, and semantic segmentation. This walkthrough focuses on the Go Point launch of the application, which uses GStreamer to process up to eight simultaneous video streams, run YOLOv8 object detection on each stream, and display the results in a single mosaic view.   Key Features Multi-stream video processing from 1 to 8 streams YOLOv8 object detection accelerated by Ara240 DNPU Support for YOLOv8n, YOLOv8s, YOLOv8m, YOLOv8l, and YOLOv8x models GStreamer-based video pipeline Mosaic display output with bounding boxes Runtime options for stream count, model selection, synchronization, and endpoint selection FPS and IPS performance overlay per stream   Running the Demo Run the application with the default settings: multistream_yolov8 Run with a specific number of streams: multistream_yolov8 -s 4 Select a different YOLOv8 model: multistream_yolov8 -s 4 --model yolov8s Run eight streams for maximum throughput: multistream_yolov8 -s 8 --sync false Enable synchronized playback: multistream_yolov8 -s 4 --sync true   Walkthrough Video In the attached video, it is shown how to launch the application from GoPoint, configure the number of streams, select different YOLOv8 models, and view the object detection results in the mosaic display.  (function() { var wrapper = document.getElementById('lia-vid-6405447139112w960h540r991'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (view in My Videos) Summary Ara-Vision-Examples is the reference application showcasing edge vision AI on the Ara240 Discrete NPU (DNPU). It runs real-time object detection, classification, pose estimation and semantic segmentation over single or multiple (up to eight) video streams, rendering bounding boxes, labels and confidence scores. Links ARA2 Vision Examples repository: https://github.com/nxp-imx-support/ara2-vision-examples Multi-stream YOLOv8 README: ara2-vision-examples/tasks/object-detection/yolo/multistream-gstreamer/README.md at main · nxp-imx-support/ara2-vision-examples · GitHub ARA2-M2-16G-GT ARA240 Hands-On Training

S32K3X8EVB-Q289 Boundary Scan test based on Lauterbach μTrace and Trace32. 1. Abstract/Introduction Boundary scan is a method for testing interconnects (wire lines) on printed circuit boards or sub-blocks inside an integrated circuit (IC). Boundary scan is also widely used as a debugging method to watch integrated circuit pin states, measure voltage, or analyze sub-blocks inside an integrated circuit. The Joint Test Action Group (JTAG) developed a specification for boundary scan testing that was standardized in 1990 as the IEEE Std. 1149.1-1990. In 1994, a supplement that contains a description of the boundary scan description language (BSDL) was added which describes the boundary-scan logic content of IEEE Std 1149.1 compliant devices. Since then, this standard has been adopted by electronic device companies all over the world. Boundary scan is now mostly synonymous with JTAG. This test is based on existing application notes for LPC55(S)xx, i.MX RT and MCXA (See references). The procedure follows how to do both a BYPASS, IDCODE and SAMPLE test, as well as an EXTEST. Following boundary scan instructions are defined in the IEEE standard: BYPASS (mandatory): TDI is connected to TDO via a single shift register. IDCODE (optional): Reads the device identification register. SAMPLE (mandatory): Takes a snapshot of the normal operation of the IC. EXTEST (mandatory): Apply preloaded data of the boundary scan register to the ports. 2. Hardware platform Lauterbach: LA-3505 POWER-DEBUG-PRO S32K3: S32K3X8EVB-Q289 There are no hardware modifications needed for connecting JTAG interface, as the S32K3 family includes the standard Arm debug port, supporting both the JTAG and SWD interfaces. S32K3XX derivatives can directly use the JTAG interface. Ensure S32K3X8EVB-Q289's jumpers are set as in the Quick Start Guide for S32K3X8EVB Board: Default Jumper settings.Default Jumper settings. Ensure a valid connection between the EVB's JTAG ARM 20-pin Standard Port (On board: J365), and the Debug Cable for Lauterbach interface. 3. Software platform This test uses Lauterbach's TRACE32 Software Package. Download the TRACE32_202509.7z to the computer and install it: Because the installation package is relatively large, you can install software components according to the target processor to save hard disk space. You can find installed driver at C:\T32\bin\windows64\drivers. 4. BSDL file validation using Lauterbach JTAG debugger. Confirm that Lauterbach probe is detected in 'Device Manager': Device Manager Trace32 device enumeration.Device Manager Trace32 device enumeration. Note: Lauterbach debugger used is LA-3500, with Probe LA-3000 + LA-7844A Debug License. Related information can be found on the Lauterbach's page. Open TRACE32 Arm interface: Type in the following commands: SYStem.Down BSDL.RESet BSDL.ParkState Select-DR-Scan BSDL.state  BSDL.state window should now appear. Select 'FILE' and load BSDL from S32K3 HW Design Package. S32K3X8EVB-Q289 should use S32K358_bga289_customer_1995E01D.bsdl. BSDL.state window.BSDL.state window.  After loading the file, type the following command: BSDL.SOFTRESET​ Switch to the Check tab of the BSDL.state window. Click BYPASSall and IDCODEall button to see if both results pass. Both should change from 'No result' to 'Test PASS': BYPASS and IDCODE check.BYPASS and IDCODE check. BYPASS: PASS means the bypass scan completed correctly for all configured devices. This indicates that the JTAG chain connectivity, chain order/length, and basic BSDL configuration are probably correct. IDCODE: PASS means the received device ID matches the expected BSDL description. This is evidence that the correct device and BSDL file are being used, but it still does not validate the boundary-register pin definitions. Next, click the SAMPLEall button, 'No result' should become Test done. Double-click the entity name, and the BSDL.SET window will pop-up: BYPASS and IDCODE check, BSDL.SET window appears.BYPASS and IDCODE check, BSDL.SET window appears. SAMPLE: PASS indicates that the pin can be observed through the boundary-scan cell, the BSDL input/observe mapping is likely correct, and that the captured value corresponds to the actual pad level. In the BSDL.SET window, uncheck Intern option to filter out the internal registers. The remaining contents are the sampled value on each signal pins. Use a multimeter to measure voltage of at least three signal pins and see if the logic state matches the sampled value. BSDL.SET window, SAMPLE check.BSDL.SET window, SAMPLE check. Next, in the Instructions field, click EXTEST and in the DR mode field, choose Set Write. Then switch to the BSDL.state window and check SetAndRun and TwoStepDR. BSDL.SET & BSDL.STATE windows EXTEST set up.BSDL.SET & BSDL.STATE windows EXTEST set up. Switch back to BSDL.SET window, click 'ENABLE' in Init BSR to enable output of corresponding signal pins, and click the buttons in “Reg.” column to toggle their output logic state 0 or 1. Use a multimeter to measure if the logic state really toggles on those signal pins. At least three signal pins need to be verified. BSDL.SET window enable and toggle signal levelBSDL.SET window enable and toggle signal level Note: PTG29/30/31 (User LED indicators Red/Green/Blue) for simplicity reasons, however, as a diagnostic recommendation, use an unloaded or lightly loaded pad if possible. 5. Conclusion This procedure provides a practical method for validating the S32K3X8EVB JTAG boundary-scan chain using TRACE32 and the appropriate S32K358 BSDL file. BYPASSall and IDCODEall verify JTAG-chain connectivity and device identification, SAMPLEall confirms pin-state observation, and EXTEST verifies pin control through the boundary-scan register. While these checks confirm basic boundary-scan operation, additional pin-level testing is recommended to validate board connectivity and application-specific signals. Any reset observed during EXTEST should be investigated before concluding a BSDL-related issue. The final report should capture the BSDL file used, JTAG-chain results, validated pins, measured logic levels, and any reset behavior observed during EXTEST. 6. References How to Perform Boundary Scan for LPC55(S)xx based on μTrace AN12919: Introduction to Boundary Scan of i.MX RT Series – Application Note How To Perform Boundary Scan On MCXA Series Using μTrace And Trace32 Boundary Scan User's Guide S32K3 Auto General-Purpose MCUs | NXP Semiconductors Software Download | Lauterbach TRACE32

LF6.18.20-2.0.0におけるimx6qの起動に関する問題 こんにちは、 いくつか質問があります。 1. CMAについて:以前はU-Boot環境で「cma=256M」を設定していましたが、今はそれを行うとシステムが起動できません。「カーネルを起動...」で停止します。」 2. DTS のオーバーライドについて: カスタムの `.dtsi` ファイルで CMA 設定を定義しましたが、システムは起動中に「start kernel...」でハングアップします。なぜこのようなことが起きているのか？ 3. 変更を加えずデフォルト値を使用すると、システムは起動時に `cma = 0` と表示されます。なぜ？ 4. `busfreq`が有効になっている場合、省電力のためにクロック周波数を下げるとシステムがクラッシュします。これを説明してもらえますか? ありがとう、 Re: LF6.18.20-2.0.0 about imx6q boot issue こんにちは、 次のリンクをご覧ください。 CM用に予約されているメモリサイズを変更する CMAはDMA操作に必要であり、アプリケーションによって異なります。 これは、複数の問題が重複していることが原因である可能性があります。 よろしくお願いいたします。

DDRストレス i.mx9392 チームの皆さん、こんにちは。 以前NXPから最新のツールを使用するように勧められたのですが、私のデバイスでDDRストレステストを実行できません。しかし、最新バージョンのConfigツールv26.09でもこの問題は依然として発生しています。問題は、私のデバイスでセキュアブートイメージを使用していることに起因しています。DDRストレステストツールや他の方法でDDRをテストする方法について教えていただけませんか? ありがとうございます マヘシュ ソレノイドコントローラ Re: DDR stress i.mx9392 こんにちは、 DDRストレステストが失敗したときに見ているログを共有してもらえますか? ボードでSDPを無効にしましたか？ よろしくお願いいたします。

Showing a short looping product video on a GUI Guider screen (i.MX RT) I would like to show a short looping product demo clip (about 10 seconds) on the idle screen of a GUI Guider project running on an i.MX RT board. The clips are short marketing videos made with an AI video tool such as Nereo (https://www.nereo.io/), so the source is a normal H.264 MP4. Questions: Is converting the MP4 to an image sequence and using an animated image widget the recommended approach in GUI Guider, or is there a better supported path (for example an MJPEG/AVI player)? What frame rate and resolution are realistic on i.MX RT1170 / RT1060 without affecting touch responsiveness? Any guidance on storing the frames in external flash versus SD card for this use case? Thanks for any pointers to examples or app notes. Re: Showing a short looping product video on a GUI Guider screen (i.MX RT) Hi @nereostudio, 1. That would be the recommended approach for an application like this one, yes. 2. The expected FPS and resolution will depend on many variables, including display interface bandwidth and color depth, chosen MCU core and frequency, whether accelerators are being used on the graphics pipeline, number of extra widgets displayed and widget complexity, etc. That said, the RT1170 would clearly perform better than the RT1060, so if you intend to maintain steady 30fps, I suggest going for the RT1170. Additionally, there are many ways of ensuring performance if you are not reaching the desired spec, which are described on the following section of the User Guide: Performance optimization — GUI Guider Documentation 3. GUI Guider by default converts images to .c files that are built alongside the rest of the GUI into a single binary file to be stored in flash, so there is not much to worry about here.

ARA2-M2-16G-GT 在 ARA2-M2-16G-GT 板用户手册中，引脚 40 为 I2C_SDA，引脚 42 为 I2C_SCL。 在 FRDM-IMX8MPLUS 原理图中，引脚 40 为 I2C_SCL，引脚 42 为 I2C_SDA。 正确的引脚排列是什么？ 谢谢  电路板设计 Re: ARA2-M2-16G-GT 你好， 根据两款设备的原理图，引脚 42 为 I2C_SDA，引脚 40 为 I2C_SCL： 顺祝商祺！

imx8qxp H265 サンプルビデオ再生 h265形式の動画ファイルを再生しようとしているのですが、再生できません。 IMX8QXP - スカースギャップ - L 6.6.52 h265の動画サンプルファイルを再生するための正しいコマンドやパッケージ/ライブラリをご確認いただけますか? GSTローンチ1.0-v filesrc location=/root/sample.h265 !h265parse !v4l2h265dec !imxvideoconvert_g2d !fpsdisplaysink video-sink=waylandsink text-overlay=false sync=false & i.MX 8ファミリ | i.MX 8QuadMax (8QM) | 8QuadPlus Re: imx8qxp H265 sample video play こんにちは、 更新情報はこちらです。 root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# gst-launch-1.0 -v filesrc location=/navigation/aa_video_dump.h265 ! h265parse ! v4l2h265dec ! imxvideoconvert_g2d ! fpsdisplaysink video-sink=waylandsink text-overlay=false sync=false パイプラインを一時停止状態に設定しています... ====== V4L2DEC: 1.24.7 ビルド、2024 年 10 月 23 日 09:43:13。====== パイプラインはプリロール中... /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0/GstWaylandSink:waylandsink0: sync = false レイテンシを再分配... /GstPipeline:pipeline0/GstH265Parse:h265parse0。GstPad:src: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0。GstPad:sink: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0。GstPad:src: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0。GstPad:src: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0。GstGhostPad:sink。GstProxyPad:proxypad0: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0/GstWaylandSink:waylandsink0。GstPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flipped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0。GstGhostPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flipped/left-flopped/right-flipped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0。GstPad:sink: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flopped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 レイテンシを再分配... root@imx8qxpc0mek:~# gst-inspect-1.0 | grep -i h265 codectimestamper: h265timestamper: H.265タイムスタンプ rtp: rtph265depay: RTP H265 デペイローダー rtp: rtph265pay: RTP H265ペイローダー typefindfunctions: video/x-h265: h265, x265, 265 video4linux2: v4l2h265dec: V4L2 H265デコーダー videoparsersbad: h265parse: H.265パーサー root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# gst-inspect-1.0 | grep -i v4l2 video4linux2: v4l2deviceprovider (GstDeviceProviderFactory) video4linux2: v4l2h263dec: V4L2 H263デコーダー video4linux2: v4l2h264dec: V4L2 H264デコーダー video4linux2: v4l2h264enc: V4L2 H.264エンコーダー video4linux2: v4l2h265dec: V4L2 H265デコーダー video4linux2: v4l2mpeg2dec: V4L2 MPEG2デコーダー video4linux2: v4l2mpeg4dec: V4L2 MPEG4デコーダー video4linux2: v4l2radio: ラジオ (video4linux2) チューナー video4linux2: v4l2sink: ビデオ (video4linux2) シンク video4linux2: v4l2spkdec: V4L2 SPKデコーダー video4linux2: v4l2src: ビデオ (video4linux2) ソース video4linux2: v4l2vc1dec: V4L2 VC1デコーダー video4linux2: v4l2vp8dec: V4L2 VP8デコーダー video4linux2: v4l2xviddec: V4L2 XVIDデコーダー root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# Re: imx8qxp H265 sample video play こんにちは、 Scarthgap(6.6.52)を使っている場合、問題は以下の通りかもしれません: 画像にv4l2h265decが存在しません。 H.265ファイルは、生の基本的なストリームではありません。 VPUのファームウェア/ドライバーが読み込まれていません。 BSPは、パイプラインで指定されたものとは異なるデコーダー要素を使用します。 以下の出力結果を提供してください。 シェル gst-inspect-1.0 | grep -i h265 gst-inspect-1.0 | grep -i v4l2 「 そして、これら4つのケースのいずれかが発生しているかどうかを特定するためのGST-Launch-1.0からの正確なエラーメッセージも示しています。 Re: imx8qxp H265 sample video play こんにちは、 ログには、H.265デコードとGStreamerネゴシエーションが正常に動作していることが示されています。 h265parseは有効な1280×720 H.265メインストリームを検出しました。 v4l2h265decは、デコードされたNV12_8L128フレームを生成しました。 imxvideoconvert_g2d がそれらを YUY2 に変換しました。 waylandsinkはキャップを受け取った。 これはH.265パッケージの欠損問題ではありません。 以下のコマンドを試して、エラーやパイプラインの状態がターミナルに表示されることなく実行できるようにします。 gst-launch-1.0-v filesrc location=/root/sample.h265 !h265parse !\ v4l2h265dec !imxvideoconvert_g2d !waylandsink sync=false Re: imx8qxp H265 sample video play こんにちは、 最新情報のご提供ありがとうございます。 以下のコマンドを実行しましたが、動作しませんでした。 root@imx8qxpc0mek:~# gst-launch-1.0 -v filesrc location=/root/sample.h265 ! h265parse ! v4l2h265dec ! imxvideoconvert_g2d ! waylandsink sync=false パイプラインを一時停止状態に設定しています... ====== V4L2DEC: 1.24.7 ビルド、2024 年 10 月 23 日 09:43:13。====== パイプラインはプリロール中... レイテンシを再分配... /GstPipeline:pipeline0/GstH265Parse:h265parse0。GstPad:src: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0。GstPad:sink: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0。GstPad:src: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0。GstPad:src: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstWaylandSink:waylandsink0。GstPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0。GstPad:sink: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flipped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 レイテンシを再分配... また、もう1つのコマンドは正常に動作しますが、ビデオの再生が非常に遅いです。 root@imx8qxpc0mek:~# gst-launch-1.0 filerc location=/root/sample.h265 ! h265 parse ! avdec_h265 max-threads=4 ! videoconvert ! video/x-raw,format=I420 ! waylandsink sync=false パイプラインを一時停止に設定中... パイプラインはプリロール中... レイテンシを再分配... レイテンシを再分配... パイプラインはプリロールされています... パイプラインを「プレイ」に設定... レイテンシを再分配... 新しい時計:GstSystemClock 0:00:00.0 / 99:99:99. 0:00:00.0/ 99:99:99。 0:00:00.0/ 99:99:99。 0:00:00.0/ 99:99:99。 0:00:00.0/ 99:99:99。 動画再生の遅さについて、フィードバックや修正点を確認していただけませんか ありがとうございます、そして敬具 VKS Re: imx8qxp H265 sample video play こんにちは、 最新のBSPで試してみてはどうですか? H.265デコーダパッケージは欠けていません。ソフトウェアデコーダー(avdec_h265)は動作しますが、Cortex-A35 CPUでデコードが行われているため遅いです。あなたの設定はハードウェアのH.265デコーダをバイパスするため、パフォーマンスが悪いのです。 Re: imx8qxp H265 sample video play @Oswalagさん、最新情報ありがとうございます。 H.265デコーダーを正しく使うために、他に追加すべきカーネルやパッケージ構成はありますか? ありがとうございます。 VKS

imx8qxp H265 示例视频播放 我尝试播放h265视频文件，但无法播放。 IMX8QXP - 斯卡思间隙 - L 6.6.52 请您检查并提供播放h265视频示例文件的正确命令或软件包/库。 gst-launch-1.0-v filesrc location=/root/sample.h265 !h265解析！v4l2h265dec！imxvideoconvert_g2d！fpsdisplaysink video-sink=waylandsink text-overlay=false sync=false & i.MX 8 系列 | i.MX 8QuadMax (8QM) | 8QuadPlus Re: imx8qxp H265 sample video play 你好， 请查收更新内容。 root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# gst-launch-1.0 -v filesrc location=/navigation/aa_video_dump.h265 ! h265parse ! v4l2h265dec ! imxvideoconvert_g2d ! fpsdisplaysink video-sink=waylandsink text-overlay=false sync=false 将管道设置为暂停状态... ====== V4L2DEC: 1.24.7 版本，构建于 2024 年 10 月 23 日 09:43:13。====== 管道正在预滚动…… /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0/GstWaylandSink:waylandsink0: sync = false 重新分配延迟…… /GstPipeline:pipeline0/GstH265Parse:h265parse0.GstPad:src: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:sink: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:src: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:src: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0.GstGhostPad:sink.GstProxyPad:proxypad0: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0/GstWaylandSink:waylandsink0.GstPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0.GstGhostPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:sink: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 重新分配延迟…… root@imx8qxpc0mek:~# gst-inspect-1.0 | grep -i h265 codectimestamper: h265timestamper: H.265 timestamper rtp: rtph265depay: RTP H265 解压加载器 rtp：rtph265pay：RTP H265 有效载荷 typefindfunctions: video/x-h265: h265, x265, 265 video4linux2：v4l2h265dec：V4L2 H265解码器 videoparsersbad: h265parse: H.265 解析器 root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# gst-inspect-1.0 | grep -i v4l2 video4linux2：v4l2deviceprovider（GstDeviceProviderFactory） video4linux2：v4l2h263dec：V4L2 H263解码器 video4linux2：v4l2h264dec：V4L2 H264解码器 video4linux2：v4l2h264enc：V4L2 H.264 编码器 video4linux2：v4l2h265dec：V4L2 H265解码器 video4linux2：v4l2mpeg2dec：V4L2 MPEG2 解码器 video4linux2：v4l2mpeg4dec：V4L2 MPEG4 解码器 video4linux2: v4l2radio: 收音机 (video4linux2) 调谐器 video4linux2：v4l2sink：视频（video4linux2）接收器 video4linux2：v4l2spkdec：V4L2 SPK解码器 video4linux2：v4l2src：视频（video4linux2）源 video4linux2：v4l2vc1dec：V4L2 VC1解码器 video4linux2：v4l2vp8dec：V4L2 VP8 解码器 video4linux2：v4l2xviddec：V4L2 XVID解码器 root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# Re: imx8qxp H265 sample video play 你好， 由于您使用的是 Scarthgap (6.6.52) 版本，问题可能出在以下方面： 图像中不存在 v4l2h265dec。 H.265 文件不是原始基本流。 VPU固件/驱动程序未加载。 BSP 使用的解码器元件与流水线中指定的解码器元件不同。 请提供以下命令的输出结果： 壳 gst-inspect-1.0 | grep -i h265 gst-inspect-1.0 | grep -i v4l2 `` 并获取 gst-launch-1.0 的确切错误消息，以尝试确定是否发生了以下四种情况之一。 Re: imx8qxp H265 sample video play 你好， 日志显示 H.265 解码和 GStreamer 协商功能正常： h265parse 检测到有效的 1280×720 H.265 主码流。 v4l2h265dec 生成解码后的 NV12_8L128 帧。 imxvideoconvert_g2d 将它们转换为 YUY2 格式。 waylandsink 接受了这些盖子。 这不是 H.265 软件包缺失的问题。 尝试运行以下命令，并允许其不带 & 参数运行，以便错误和管道状态在终端中可见： gst-launch-1.0-v filesrc location=/root/sample.h265 !h265解析！\ v4l2h265dec！imxvideoconvert_g2d！waylandsink 同步=false Re: imx8qxp H265 sample video play 你好， 谢谢你的更新。 我执行了以下命令，但没有效果。 root@imx8qxpc0mek:~# gst-launch-1.0 -v filesrc location=/root/sample.h265 ! h265parse ! v4l2h265dec ! imxvideoconvert_g2d ! waylandsink sync=false 将管道设置为暂停状态... ====== V4L2DEC: 1.24.7 版本，构建于 2024 年 10 月 23 日 09:43:13。====== 管道正在预滚动…… 重新分配延迟…… /GstPipeline:pipeline0/GstH265Parse:h265parse0.GstPad:src: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)字节-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, 我的=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:sink: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)字节-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, 我的=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:src: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:src: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstWaylandSink:waylandsink0.GstPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:sink: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 重新分配延迟…… 此外，另一个命令运行正常，但是视频播放速度非常慢。 root@imx8qxpc0mek:~# gst-launch-1.0 filesrc location=/root/sample.h265 ! h265parse ! avdec_h265 max-threads=4 ! videoconvert ! video/x-raw,format=I420 ! waylandsink sync=false 将管道设置为暂停状态... 管道正在预滚动…… 重新分配延迟…… 重新分配延迟…… 管道已预卷…… 将管道设置为播放状态... 重新分配延迟…… 新时钟：GstSystemClock 0:00:00.0 / 99:99:99。 0:00:00.0/ 99:99:99。 0:00:00.0/ 99:99:99。 0:00:00.0/ 99:99:99。 0:00:00.0/ 99:99:99。 请您检查一下视频播放缓慢的问题，并提供反馈/解决方法。 谢谢，此致敬礼！ VKS Re: imx8qxp H265 sample video play 感谢@Oswalag提供的最新消息。 要正确使用 H.265 解码器，是否还需要在版本过程中添加其他内核或软件包配置？ 谢谢，此致敬礼！ VKS Re: imx8qxp H265 sample video play 你好， 您能否尝试使用最新的电路板支持包版本？ H.265 解码器代码包，软件包没有缺失，软件解码器 (avdec_h265) 可以工作，但是速度很慢，因为解码是在 Cortex-A35 CPU 上完成的，你的配置绕过了硬件 H.265 解码器，这就是性能差的原因。

ARA2-M2-16G-GT In the ARA2-M2-16G-GT Board User Manual Pin 40 is I2C_SDA and Pin 42 is I2C_SCL. in the FRDM-IMX8MPLUS schematic Pin 40 is I2C_SCL and Pin 42 is I2C_SDA. what the correct pinout? thanks  Board Design Re: ARA2-M2-16G-GT Hello, According the the schematic of both devices, pin 42 is I2C_SDA and pin 40 I2C_SCL: Best regards.

imx8qxp H265 sample video play I am trying to play the h265 video file and it is not playing.  IMX8QXP - Scarthgap  - L 6.6.52 Can you please check and provide the right command or packages/lib to play h265 video sample files, gst-launch-1.0 -v filesrc location=/root/sample.h265 ! h265parse ! v4l2h265dec ! imxvideoconvert_g2d ! fpsdisplaysink video-sink=waylandsink text-overlay=false sync=false & i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Re: imx8qxp H265 sample video play Hi, Please find the update, root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# gst-launch-1.0 -v filesrc location=/navigation/aa_video_dump.h265 ! h265parse ! v4l2h265dec ! imxvideoconvert_g2d ! fpsdisplaysink video-sink=waylandsink text-overlay=false sync=false Setting pipeline to PAUSED ... ====== V4L2DEC: 1.24.7 build on Oct 23 2024 09:43:13. ====== Pipeline is PREROLLING ... /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0/GstWaylandSink:waylandsink0: sync = false Redistribute latency... /GstPipeline:pipeline0/GstH265Parse:h265parse0.GstPad:src: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:sink: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:src: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:src: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0.GstGhostPad:sink.GstProxyPad:proxypad0: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0/GstWaylandSink:waylandsink0.GstPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstFPSDisplaySink:fpsdisplaysink0.GstGhostPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:sink: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 Redistribute latency... root@imx8qxpc0mek:~# gst-inspect-1.0 | grep -i h265 codectimestamper: h265timestamper: H.265 timestamper rtp: rtph265depay: RTP H265 depayloader rtp: rtph265pay: RTP H265 payloader typefindfunctions: video/x-h265: h265, x265, 265 video4linux2: v4l2h265dec: V4L2 H265 Decoder videoparsersbad: h265parse: H.265 parser root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# gst-inspect-1.0 | grep -i v4l2 video4linux2: v4l2deviceprovider (GstDeviceProviderFactory) video4linux2: v4l2h263dec: V4L2 H263 Decoder video4linux2: v4l2h264dec: V4L2 H264 Decoder video4linux2: v4l2h264enc: V4L2 H.264 Encoder video4linux2: v4l2h265dec: V4L2 H265 Decoder video4linux2: v4l2mpeg2dec: V4L2 MPEG2 Decoder video4linux2: v4l2mpeg4dec: V4L2 MPEG4 Decoder video4linux2: v4l2radio: Radio (video4linux2) Tuner video4linux2: v4l2sink: Video (video4linux2) Sink video4linux2: v4l2spkdec: V4L2 SPK Decoder video4linux2: v4l2src: Video (video4linux2) Source video4linux2: v4l2vc1dec: V4L2 VC1 Decoder video4linux2: v4l2vp8dec: V4L2 VP8 Decoder video4linux2: v4l2xviddec: V4L2 XVID Decoder root@imx8qxpc0mek:~# root@imx8qxpc0mek:~# Re: imx8qxp H265 sample video play Hello,  Since you are using Scarthgap (6.6.52), the issues could be: v4l2h265dec not present in the image. The H.265 file is not a raw elementary stream. VPU firmware/driver not loaded. The BSP uses a different decoder element than the one specified in the pipeline. Please provide the output of: Shell gst-inspect-1.0 | grep -i h265 gst-inspect-1.0 | grep -i v4l2 `` and the exact error message from gst-launch-1.0 to try to identify if one of these four cases is occurring. Re: imx8qxp H265 sample video play Hello,  The log shows that H.265 decoding and GStreamer negotiation are working: h265parse detected a valid 1280×720 H.265 Main stream. v4l2h265dec produced decoded NV12_8L128 frames. imxvideoconvert_g2d converted them to YUY2. waylandsink accepted the caps. This is not a missing H.265 package issue. Try the following command and allow it to run without & so errors and pipeline state remain visible in the terminal: gst-launch-1.0  -v filesrc location=/root/sample.h265 ! h265parse ! \ v4l2h265dec ! imxvideoconvert_g2d ! waylandsink sync=false Re: imx8qxp H265 sample video play Hi, Thank you for update. I executed following command but not working root@imx8qxpc0mek:~# gst-launch-1.0 -v filesrc location=/root/sample.h265 ! h265parse ! v4l2h265dec ! imxvideoconvert_g2d ! waylandsink sync=false Setting pipeline to PAUSED ... ====== V4L2DEC: 1.24.7 build on Oct 23 2024 09:43:13. ====== Pipeline is PREROLLING ... Redistribute latency... /GstPipeline:pipeline0/GstH265Parse:h265parse0.GstPad:src: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:sink: caps = video/x-h265, width=(int)1280, height=(int)720, framerate=(fraction)30/1, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, pixel-aspect-ratio=(fraction)1/1, profile=(string)main, tier=(string)high, level=(string)4 /GstPipeline:pipeline0/v4l2h265dec:v4l2h265dec0.GstPad:src: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:src: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/GstWaylandSink:waylandsink0.GstPad:sink: caps = video/x-raw, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1, format=(string)YUY2 /GstPipeline:pipeline0/imxvideoconvert_g2d:imxvideoconvert_g2d0.GstPad:sink: caps = video/x-raw, format=(string)NV12_8L128, width=(int)1280, height=(int)720, interlace-mode=(string)progressive, multiview-mode=(string)mono, multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono, pixel-aspect-ratio=(fraction)1/1, colorimetry=(string)bt709, framerate=(fraction)30/1 Redistribute latency... As well as one more command is working fine but, video playing is very slow. root@imx8qxpc0mek:~# gst-launch-1.0 filesrc location=/root/sample.h265 ! h265parse ! avdec_h265 max-threads=4 ! videoconvert ! video/x-raw,format=I420 ! waylandsink sync=false Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Redistribute latency... Redistribute latency... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... Redistribute latency... New clock: GstSystemClock 0:00:00.0 / 99:99:99. 0:00:00.0 / 99:99:99. 0:00:00.0 / 99:99:99. 0:00:00.0 / 99:99:99. 0:00:00.0 / 99:99:99. Can you please check and provide your feedback/ fix for slowness in video playing Thanks & regards, VKS Re: imx8qxp H265 sample video play Hello,  Could you try with the latest BSP?  The H.265 decoder package is not missing, the software decoder (avdec_h265) works but is slow because decoding is being done on the Cortex-A35 CPUs, your configuration bypasses the hardware H.265 decoder, that's why you have poor performance. Re: imx8qxp H265 sample video play Thank You @Oswalag  for the update. Is there any other kernel or package configuration required to be added to the build to use the H.265 decoder in proper way? Thanks & regards, VKS

DDR stress i.mx9392 Hi Team, I am not able to run DDR stress test on my device previously NXP sujjested to use latest tool but still I am facing this issue with the latest version of the Config tool v26.09 as well. The issue is due to I am using secure boot image on my device. Can you please assist how to use DDR stress test tool or any other method to test the DDR. Thanks, Mahesh Solenoid Controller Re: DDR stress i.mx9392 Hello, Could you please share the log you are seeing when the DDR stress test fails? Did you disable SDP in your board? Best regards.

ARA2-M2-16G-GT ARA2-M2-16G-GTボードのユーザーマニュアルでは、ピン40はI2C_SDA、ピン42はI2C_SCLされています。 FRDM-IMX8MPLUSの回路図では、ピン40はI2C_SCL、ピン42はI2C_SDAです。 正しいピン配置は何ですか？ よろしくお願いします。 ボード設計 Re: ARA2-M2-16G-GT こんにちは、 両デバイスの回路図によると、ピン42はI2C_SDA、ピン40はI2C_SCLです。 よろしくお願いいたします。

DDR压力 i.mx9392 大家好， 我无法在我的设备上运行 DDR 压力测试，之前 NXP 建议使用最新工具，但我仍然在使用最新版本的 Config 工具 v26.09 时遇到此问题。问题在于我的设备上使用了安全启动映像。请问如何使用DDR压力测试工具或其他方法来测试DDR内存？ 谢谢！ 马赫什 电磁阀控制器 Re: DDR stress i.mx9392 你好， 能否请您分享一下DDR压力测试失败时您看到的日志？ 你是否在板上禁用了SDP？ 顺祝商祺！

LF6.18.20-2.0.0 关于 imx6q 启动问题 你好， 我有几个问题： 1. 关于 CMA：之前我在 U-Boot 环境中设置了 `cma=256M`，但现在这样做会导致系统无法启动；它卡在“start kernel...”处。 2. 关于 DTS 覆盖：我在自定义的 `.dtsi` 文件中定义了 CMA 设置，但系统在启动时仍然卡在“启动内核...”处。为什么会发生这种情况？ 3. 如果我不做任何更改并使用默认值，系统在启动时显示“cma = 0”。为什么？ 4. 如果启用了 `busfreq`，则在为了省电而降低频率后，系统会崩溃。请问您能解释一下吗？ 谢谢， Re: LF6.18.20-2.0.0 about imx6q boot issue 你好， 我建议您看看以下链接： 更改为 CMA 保留的内存大小 DMA 操作需要 CMA，并且 CMA 取决于应用程序。 这可能是由于多个问题重叠造成的。 顺祝商祺！

LF6.18.20-2.0.0 about imx6q boot issue Hello, I have a few questions: 1. Regarding CMA: Previously, I set `cma=256M` in the U-Boot environment, but now doing so prevents the system from booting; it hangs at "start kernel..." 2. Regarding DTS overrides: I defined CMA settings in my custom `.dtsi` file, but the system still hangs at "start kernel..." during boot. Why is this happening? 3. If I make no changes and use the default values, the system shows `cma = 0` at boot. Why? 4. If `busfreq` is enabled, the system crashes after downclocking for power saving. Could you please explain this? Thanks,  Re: LF6.18.20-2.0.0 about imx6q boot issue Hello, I suggest you take a look in the next link: Changing memory size reserved for CMA CMA is required for DMA operations and it is application dependent. This may be caused by overlapping issues. Best regards.