Multi Source Translation Content

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Multi Source Translation Content

ディスカッション

ソート順:
S32K344 停机 你好,团队、 我们正在使用 S32K344 构建定制的 MCU 板。在开发部分,我们使用 freeRTOS 作为操作系统。我们在初期运行中没有遇到任何问题。但当我们长时间运行时,比如超过 15 分钟,它就会挂起。请告诉我可能出了什么问题。 谢谢! 维奈 Re: S32K344 Halts 你好,@vinaykl、 您需要提供更多详细信息,以缩小问题范围。 你说的 "挂起 "到底是什么意思? 系统是陷入了循环,还是出现了故障异常? 是否有任务仍在运行,还是一切都冻结了? 这种行为可能是由堆栈溢出、堆耗尽、中断行为不当或任务饥饿等内存相关问题引起的。 S32DS IDE 包含有助于分析 FreeRTOS 应用程序的工具,如堆使用视图、任务列表视图等。 此致, 丹尼尔
記事全体を表示
S32DS 和 S32 调试探针 - 在 S32R47 上调试 KQ8 的奇怪行为 我使用的是 S32DS 3.6.3使用 S32 调试探针在 S32R47 硬件目标上调试 KQ8 DSP 内核。在对 KQ8 应用程序进行单步调试(C HLL 步进,而非汇编指令步进)时,调试器会进入汇编代码的意外部分,最终卡住,系统挂起,需要重新启动。 我附上了一些奇怪行为的截图,似乎调试器开始步进 Xtensa C-runtime 设置或库代码,这在 HLL 步进模式下是不应该发生的。 我还附上了一段屏幕录制视频,显示了具体发生的情况。 客户(Hella/Forvia)报告了这一问题,他们正在寻求恩智浦的指导,请解释这一行为并建议如何避免。 提前感谢! Gary 优先级:高 S32DS 资料来源直接客户 Re: S32DS and S32 Debug Probe - Strange Behaviour Debugging KQ8 on S32R47 你好@GaryRK、 这确实是一个 S32 调试器问题,是由调试器内部设计的源步进和调试模块中的 KQ8 架构特性造成的。更确切地说,S32 调试器在源步进时是指令步进和运行到内部 bp 的混合。从设计上讲,KQ8 上的 Asm 步骤正在触发一个由调试模块处理的异常,但是如果同时触发另一个异常,则该异常将保持未处理状态,这就是这里发生的情况。我们也可以在劳特巴赫调试器上重现该错误,但使用的是指令步进模式。我们将想办法解决这个问题。在此之前,解决办法是尽可能在函数中使用 SW 断点。 此致, 亚历山德拉 Re: S32DS and S32 Debug Probe - Strange Behaviour Debugging KQ8 on S32R47 附上用于重现问题的 S32DS 项目 Re: S32DS and S32 Debug Probe - Strange Behaviour Debugging KQ8 on S32R47 你好,丹妮拉、 在使用具有正确 SRAM 区域定义的修改/自定义 gdbio-stacklocal LSP 时,问题仍然存在。我从我的同事马克那里拿到了改良版,我想这是你们团队做的。无论如何我都附上了它以供参考。 我认为这个问题是 S32 调试探针而不是 KQ8 可执行文件特有的。它似乎无法只执行 C/HLL 步进,并在 Xtensa 操作系统派生的汇编代码中卡住/丢失,这些代码看起来像函数序幕/前导和堆栈管理。 我所附的截图显示了一个例子:我正在步进程序,当输入一个常规的 C 函数时,调试器在一个奇怪的、意想不到的地方停止了 KQ8 的运行。 顺祝商祺! Gary Re: S32DS and S32 Debug Probe - Strange Behaviour Debugging KQ8 on S32R47 嗨,加里、 你遇到的问题很可能与 LSP 有关,S32DS 从 KQ8 核心配置中重复使用 LSP,其定义的 SRAM 大小为 64M 而不是 8M。为了防止这种行为,你可以手动编辑 LSP,也可以使用专用的代码包工具(例如 Xtensa Explorer)生成这样的 LSP。 顺祝商祺! 达妮埃拉 Re: S32DS and S32 Debug Probe - Strange Behaviour Debugging KQ8 on S32R47 如果有人见过这种情况,能否请您承认这里确实存在问题,以便我向海拉/福维亚提供一些初步反馈?我们每天都要与客户开会,他们要求我们提供最新信息。 谢谢! Gary Re: S32DS and S32 Debug Probe - Strange Behaviour Debugging KQ8 on S32R47 由于没有收到客户的反馈,因此关闭此问题。
記事全体を表示
射频高功率模块套件 & 晶体管模型 RF High 功率模块 Kit 2025 修订版 3.1(适用于 ADS2016、ADS2017、ADS2019、ADS2020、ADS2022、ADS2023、2024 和 2025) 需要安装 RF 功率模块套件才能运行所有 RF 高功率 ADS 模型。 安装说明包含在相应的射频功率模块套件中。 该套件没有安装说明。你能帮我安装这个套件吗?我使用的是 64 位 Windows。ADS2022. 我什么都试过了。更改地点。解压缩并保存在 ADS 的相应目录中。没有任何效果。每当我使用任何模型时,都会出现模拟错误 模拟信息 在网表解析期间,hpeesofsim 在动态设备加载中检测到警告。 加载此文件的共享库失败:"c:\users\syed musawir ali\myworkspace6_wrk\rf_power_ads_designkit_ads2025_3p1\bin\ads_2022_win32_64_vs2019/RF_LDMOS_ADS_DesignKit.dll"(c:\users\syed musawir ali\myworkspace6_wrk\rf_power_ads_designkit_ads2025_3p1\bin\ads_2022_win32_64_vs2019/RF_LDMOS_ADS_DesignKit.dll).musawir ali\myworkspace6_wrk\rf_power_ads_designkit_ads2025_3p1\bin\ads_2022_win32_64_vs2019/RF_LDMOS_ADS_DesignKit) Dynamic linker gave reasons: " The specified module could not be found." 造成这种情况的原因可能是缺少依赖库、 或试图加载错误架构的库。 例如,不能在 Solaris 中使用 Linux 库,也不能在 64 位 应用程序中使用 32 位库(反之亦然)。 网表解析过程中,hpeesofsim 检测到警告。 模型 'FSL_MRFE6VP100H_FET2.FET2M1'(在文件 'C: /Users/Syed Musawir Ali/myworkspace6_wrk/mrfe6vp100H_lev0_dk//Circuit/mordels/fest2.FET2M1' 中定义):`fslrfepk_fet2_dk//circuit/mordels/fest2VP100H_fet2M1'左右定义):`fslrfpk_FET2_FET2 _v1' 是一个未定义的原始设备。 hpeesofsim 在网表扁平化过程中检测到错误。 FSL_MRFE6VP100H_FET2.FSL1 "是未定义模型 "FET2M1 "的实例。 现状/摘要 hpeesofsim (*) 550.shp 2021 年 7 月 24 日,MINT 版本 5 (64 位 Windows 构建时间:2021 年 7 月 24 日星期六 16:09:49 +0000) ***** Simulation started at Thu Sep 18 09:53:26 2025 Running on host:"DESKTOP-6G6MK1Q" In Directory:"C:\Users\Syed Musawir Ali\MyWorkspace6_wrk\data" 进程 ID:11828 -------------------- 仿真因错误而终止。 -------------------- Re: RF high power model kit & transistor models 您好! 请使用以下链接和信息获取设计工具包的解压缩、安装和设置说明。 http://edadocs.software.keysight.com/display/support/Knowledge+Center?cmpid=zzfindeesof-knowledgecenter 然后转到高级设计系统 (ADS),转到文档,就可以找到 Unix、Linux Windows 安装指南。 请注意,这需要登录。 希望这能帮到您。
記事全体を表示
S32N55:对多功能域的 gPTP 支持 队员们好 我想询问当前的GpTP堆栈是否支持多功能域?如果是这样,我怎样才能获得不同功能域的时间? 谢谢。 顺祝商祺! 布里奇特 GPTP_STACK Re: S32N55: gPTP support for multi-domains 是的,没错。默认情况下,gPTP 无法知道哪个功能域适合你,也无法知道你想如何处理在其他功能域上收到的时间。因此,应用程序可以自由实施(决定)如何处理时间信息。 关于第二个问题。这取决于执行情况。gPTP 从 NETC 获取时间戳。在某些情况下(NPI),netc 支持 2 个计时器。如果支持 2 个定时器,则时间戳可以基于自由运行定时器,该定时器不受 SW.... 的管理,只是从 0 运行到无穷大(2^64)。在另一种情况下,如果只有经过校正的定时器,NETC 将使用该定时器生成时间戳。该计时器既由 gPTP 协议栈管理,也用于生成时间戳。这取决于你如何处理从特定功能域收到的时间。在默认情况下,在功能域 0 上收到的时间用于计时器校正。你可以将其关闭,然后计时器就会像自由运行一样运行... 或者你可以使用不同的功能域来管理计时器。但时间戳始终由 NETC HW 提供。 Re: S32N55: gPTP support for multi-domains 嗨,团队, 请回答本回复中提出的问题。谢谢。 Re: S32N55: gPTP support for multi-domains 如果自由运行计时器不支持 gPTP 堆栈的管理,这是否意味着该计时器只能由特定的功能域中的大师使用?根据 gPTP 协议栈逻辑,所有用于发送、接收和计算的时间戳都直接来自硬件,无需使用 Stbm 等方法将中间时间戳转换为软件时间戳。换句话说,不能调整的计时器只能由大总管使用,因为大总管不需要修改自己的时钟。 总体而言,我们的 NETC 通常只支持一个定时器,该定时器可根据 gPTP 协议在硬件层面进行同步。而 gPTP 协议栈软件完全依赖于硬件时间戳。因此,在这种情况下,gPTP 堆栈本质上只支持一个功能域。 我的理解正确吗? Re: S32N55: gPTP support for multi-domains 这个问题要复杂得多。 在网络中,有些设备必须(仅有感知)同步其计时器。然后,您的设备不必同步其计时器。而这并不是他们的角色所赋予的。 Grandmaster 可以同步本地计时器,例如与 GPS 同步......也可以使用自由运行计时器。但是,网络只提供了指针为 "大师 "启动时间的时间。对于某些应用来说,这就足够了,而对于某些应用来说则不然。 网桥可以更新或不必更新其本地时间。这意味着时间戳可以基于自由运行计时器或校正计时器。为保证桥接正常运行,当地时间并不重要。一旦网桥为其他 TSN 功能提供服务,就必须对网桥进行本地时间同步。因此,具体情况具体分析。 终端节点通常会将其本地定时器与主节点同步。最典型的使用案例。但是,它也可以在自由运行时运行,而无需同步。至于是让终端节点管理校正后的定时器,还是让它以自由运行的方式运行(如果有的话,甚至可以使用自由运行的定时器来记录时间戳),这取决于应用程序。在这种情况下,可以采用与多域环境相同的方式处理来自 "大师 "的时间。 在这种情况下,堆栈可以提供时间戳计时器和 Grandmaster 时间之间的软件参考(当前偏移量),而不是使用接收到的时间信息进行本地计时器更新。它可以作为 1 个功能域或 n 个功能域的软件参考。Stack 只需提供当地时间与全球机制时间之间的当前时差。适用于所有功能域。而且,如果更正后的计时器可用(始终可用),则可以使用所选功能域的时间进行本地更新。 理论上,如果 10 个经过更正的计时器可用,那么 10 个功能域时间可以由硬件在本地维护... 但这并不常见,也不知道会有什么好处。对于大多数应用程序来说,只需要一个时基,精度极高,而其他功能域可能在不需要高精度时提供不同的时间。因此,所提供的 SW 偏移已经足够。 在 gPTP 中,我们讨论的精度范围是低纳秒,最高可达 10 纳秒。这对 TSN 很有用......但对于系统或其他应用来说,时间精度并不是必需的。 Re: S32N55: gPTP support for multi-domains 非常感谢你的解释。 我想我现在明白了。关键在于,gPTP 协议侧重于提供当前设备与 GM 之间的时间偏移,而设备的时钟是否需要与 GM 同步则取决于具体的应用程序。 再次感谢您耐心细致的解释!
記事全体を表示
New SDK Generator Docs New SDK generator docs have been released. You can get it from: 1. SDK generator repo: https://bitbucket.sw.nxp.com/projects/MCUCORE/repos/mcu-sdk-generator/browse/doc  2. Gitbook: http://10.193.108.154:4000/ Here is a snapshot Getting Started With SDK Generator.md Getting Starts. It illustrates why we need sdk generator, how to install and use it. Basic concepts and working scenarios are introduced. Yaml Data Record Guide.md Illustrate yaml data record rule, syntax, concepts. It covers every aspect of the SDK data. Yaml Data Record For Project Settings.md Illustrate yaml data record syntax for project settings. Yaml Data Record Component Naming Conventions.md Illustrate SDK component naming conversation. Yaml Example Reference.md The reference index for yml/batch set demos. Release Actions Of SDK Generator.md Illustrate the release actions of SDK. SDK Docs Generation Flow.md Illustrate how to integrate SDK docs generation into sdk generator. How To Configure Release_config File.md Illustrate how to config release config yml. Frequently Asked Questions.md Frequently asked questions, still on-going, we will add more.  
記事全体を表示
Thread tech days.pdf
記事全体を表示
AUT-N1800 レーダーセンシング付きの専用短距離通信DSRCを使用して、交通渋滞を解消します <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自動車を購入する個人が増え、都市人口が増加すると、道路の渋滞は年々悪化しています。交通渋滞は数十億ドルの生産性の損失をもたらします:個人はストップゴー条件で何時間も単調な車両操作に制限されています。解決策:NXPのADASレーダー、ビジョン、およびV2Xテクノロジーの進歩により、渋滞を緩和し、失われた生産性を取り戻すことができます-1)個人的なストレスの軽減、2)通勤者の生産性の向上、3)交通事故の削減。このセッションでは、ドライバーの応答のばらつきを制御する方法を示します(例:加速、減速、最小安全走行距離を一定にする)、渋滞渋滞を緩和します。セッションは、ADAS DSRC機能とNXPデバイスのマッピングで終了します。 ビデオプレゼンテーションを見る <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自動車を購入する個人が増え、都市人口が増加すると、道路の渋滞は年々悪化しています。交通渋滞は数十億ドルの生産性の損失をもたらします:個人はストップゴー条件で何時間も単調な車両操作に制限されています。解決策:NXPのADASレーダー、ビジョン、およびV2Xテクノロジーの進歩により、渋滞を緩和し、失われた生産性を取り戻すことができます-1)個人的なストレスの軽減、2)通勤者の生産性の向上、3)交通事故の削減。このセッションでは、ドライバーの応答のばらつきを制御する方法を示します(例:加速、減速、最小安全走行距離を一定にする)、渋滞渋滞を緩和します。セッションは、ADAS DSRC機能とNXPデバイスのマッピングで終了します。 ビデオプレゼンテーションを見る セキュアなコネクテッド&自動運転車
記事全体を表示
CSCI E-251,2012 年秋季 - 最终项目展示 - 简介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 哈佛大学继续教育学院 CSCI E-251,2012 年秋季:操作系统原理 最终项目展示 James L. Frankel 教授作介绍 (在 “我的视频” 中查看) 学生项目 回复:CSCI E-251,2012 年秋季 - 最终项目演示 - 简介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> jamiefrankel——好东西!谢谢上传!!
記事全体を表示
Automotive Ethernet AVB Demo: ADAS System and a complete Infotainment Solution Demo This demo shows an infotainment and ADAS system based on NXP Ethernet components and is divided in three main parts: Infotainment, Network and ADAS. In the infotainment part, a “Head Unit” ECU plays locally an MPEG movie and also streams it over Ethernet to the second “Rear Seat Unit” ECU. Both ECUs also execute in the backroad the NXP AVB SW stack. This enables the two ECUs to be perfectly synchronized with each other. Therefore the two ECUs can playback the very same video (and audio) frame at the same time on their local displays. In the network part the new Automotive Ethernet Switch (SJA1105EL) and PHYs (TJA1100HN) implement the Ethernet connectivity of the system. The switch executes the AVB “gPTP” synchronization SW that enables the infotainment application described above to operate. In the ADAS part a surround view camera captures a video stream and streams it to a “Cluster” ECU also connected via the automotive Ethernet network. The camera is based on the NXP “MPC5604E ” Salsa processor and on a competitor’s BroadR-Reach PHY. This also shows the interoperability of the TJA1100HN PHY with competitor’s products. Features: All displays are implemented with NXP i.MX6 processor, and a full implementation of the NXP Ethernet AVB Stack running on Linux. The camera is based on an NXP Salsa processor (MPC5304EKIT) . The Switch board that connects all displays and the camera uses the NXP SJA1105EL Automotive Ethernet switch and the TJA1100HN BroadR-Reach Ethernet PHY ______________________________________________________________________________________________________________ Featured NXP Products: Product Link IEEE 100BASE-T1 compliant Automotive Ethernet PHY Transceiver TJA1100HN | Automotive Ethernet PHY Transceiver | NXP  i.MX 6 Series i.MX 6 Series Applications Processors | Multicore Arm Cortex-A7/A9/M4 | NXP  Audio Video Bridging Software https://www.nxp.com/design/design-services/audio-video-bridging-software:AVB-SOFTWARE?&fsrch=1&sr=4&pageNum=1 Development Kit Enabling Video Over Ethernet with NXP® MPC5604E MCU NXP® MPC5604EKIT:Development Kit | NXP  ___________________________________________________________________________________________________________ Automotive
記事全体を表示
Example MPC5777C-SDADC_simple GHS614 ******************************************************************************** * Detailed Description: * Example configures Sigma_Delta ADC and periodically converts ANA0_SDA0 input * (EVB's potentiometer can be connected i.e. J53-1 --> PO15) and displays * results in the terminal window (USBtoUART bridge J21). Terminal settings is * 19200-8-no parity-1 stop bit-no flow control on eSCI_A. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A *                  eSCI_A is USBtoUART bridge (connector J21) * EVB connection:  For ADC: J53-1 (EVB pot's wiper) --> PO15 (header P22) * ******************************************************************************** ******************************************************************************** * Detailed Description: * Example configures Sigma_Delta ADC and periodically converts ANA0_SDA0 input * (EVB's potentiometer can be connected i.e. J53-1 --> PO15) and displays * results in the terminal window (USBtoUART bridge J21). Terminal settings is * 19200-8-no parity-1 stop bit-no flow control on eSCI_A. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A *                  eSCI_A is USBtoUART bridge (connector J21) * EVB connection:  For ADC: J53-1 (EVB pot's wiper) --> PO15 (header P22) * ******************************************************************************** General
記事全体を表示
HMB-N1905 Low Cost Radar to Create Secure and Smart Homes Advancing technology has brought down the cost of 24 GHz radar system significantly bringing a whole range of new applications into reach. Historically radar was a pure military and industrial application due to high application costs. With the latest generation of NXP BiCMOS technology this has changed. A 24 GHz radar frontend can now be fully integrated into a single IC bringing the costs and power dissipation down to consumer levels. This opens up a whole range of applications which were previously not possible. This lecture will show the possibilities of radar in different applications such as presence detection and consumer drone collision avoidance. A live demonstration based on first test chips in combination with ARM processors will be given. Advancing technology has brought down the cost of 24 GHz radar system significantly bringing a whole range of new applications into reach. Historically radar was a pure military and industrial application due to high application costs. With the latest generation of NXP BiCMOS technology this has changed. A 24 GHz radar frontend can now be fully integrated into a single IC bringing the costs and power dissipation down to consumer levels. This opens up a whole range of applications which were previously not possible. This lecture will show the possibilities of radar in different applications such as presence detection and consumer drone collision avoidance. A live demonstration based on first test chips in combination with ARM processors will be given. Smart Home & Buildings
記事全体を表示
Patch to Support BT656 and BT1120 Output For i.MX6 BSP Here are two patches to support BT656 and BT1120 output for i.MX6 ipuv3. With this patch, the i.MX6 can support the CVBS output on TV encoder. It is useful for a TV box. "L3.0.35_1.1.0_GA_bt656_output_patch.zip" is the patch for Freescale L3.0.35_1.1.0_GA_iMX6DQ BSP. "r13.4.1_bt656_output_patch.zip" is the patch for Freescale Android R13.4.1 BSP. 1. Features supported:     1) Support BT656(8 bits) and BT1120 (16 bits)interlaced output on display port.     2) Support both RGB and YUV frame buffer for BT656/BT1120 output.     3) Support PAL and NTSC mode.     4) Support on the fly switch between PAL and NTSC mode.     5) Support CVBS output based on adv7391 TV encoder. 2. Hardware link between iMX6 and adv7391 TV encoder chip.     IPU1_DI0_DISP_CLK connected to adv7391 CLKIN pin.     IPU1_DISP0_DAT_23~DISP0_DAT_16 connected to adv7391 P7~P0 pins.     IPU1_DI0_PIN2 connected to adv7391 HSYNC pin. (option)     IPU1_DI0_PIN4 connected to adv7391 VSYNC pin. (option)   - Android R13.4.1 kernel. 3. How to use -- Copy the two patch files to kernel folder.     $ git apply ./0001-Support-BT656-and-BT1120-output-for-iMX6-ipuv3.patch     $ git apply ./0002-Support-adv739x-TV-encoder-for-BT656-output.patch -- Select them in kernel config and build the new kernel image:                     Device Drivers  --->                       Graphics support  --->                           [*]   MXC BT656 and BT1120 output                           [*]   ADV7390/7391 TV Output Encoder -- Uboot parameters for video mode    Output BT656 NTSC data to display port with UVYV frame buffer mode:       "video=mxcfb0:dev=bt656,BT656-NTSC,if=BT656,fbpix=UYVY16"    Output BT656 NTSC data to display port with RGB565 frame buffer mode:       "video=mxcfb0:dev=bt656,BT656-NTSC,if=BT656,fbpix=RGB565"    Output BT656 PAL data to display port with RGB24 frame buffer mode:       "video=mxcfb0:dev=bt656,BT656-PAL,if=BT656,fbpix=RGB24"    Output CVBS NTSC signal on adv7391 with UYVY frame buffer mode:       "video=mxcfb0:dev=adv739x,BT656-NTSC,if=BT656,fbpix=UYVY16"    Output CVBS PAL signal on adv7391 with RGB565 frame buffer mode:       "video=mxcfb0:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565" -- Switch between PAL and NTSC    $ echo D:720x480i-60 > /sys/class/graphics/fb0/mode    $ echo D:720x576i-50 > /sys/class/graphics/fb0/mode 4. Note     1) For 8 bits BT656 interface, the default data pins are "DISP0_DAT_23~DISP0_DAT_16", it can also        be any other continued display data pins, for example if "DISP0_DAT_7~DISP0_DAT_0" are used, the        macro "BT656_IF_DI_MSB" in "kernel_imx/drivers/mxc/ipu3/ipu_disp.c" should be changed from "23"        to "7".     2) For 16 bits BT1120 interface, the default data pins are "DISP0_DAT_23~DISP0_DAT_8", it can also        be any other continued display data pins, the macro "BT656_IF_DI_MSB" should be modified if the        hardware pins are changed.     3) When bt656 interface is the second display for each IPU,1-layer-fb (it can be checked with command        "$ cat /sys/class/graphics/fbx/fsl_disp_propperty"), the frame buffer can only be YUV format. In this        case, the IPU DC channel was used for BT656 display, it has no CSC function, so RGB frame buffer was        not supported. 2013-08-09 updated: The new release package "L3.0.35_1.1.0_GA_bt656_output_patch_2013-08-09.zip" had fixed the BT656 dual display issue on iMX6S/DL. Removed the old release package. 2013-09-04 updated: The new release package "r13.4.1_bt656_output_patch_2013-09-04.zip" had fixed the BT656 dual display issue on iMX6S/DL. For default, the dual display was tested with HDMI + CVBS, HDMI is the main display and adv739x CVBS output is the second display. For iMX6DQ which has two IPUs, please assign dual display to two IPUs, for example adv739x is on IPU1 DI0, it is fixed, because hardware pins used for it is fixed. Then we can assign HDMI or LVDS to another IPU (IPU2). For iMX6S/DL which has only one IPU, since adv739x had used IPU1 DI0, another display should be IPU1 DI1. 2013-09-30 updated: Added patch for L3.0.35_4.1.0_GA BSP, the file is "L3.0.35_4.1.0_GA_bt656_output_patch_2013-09-30.zip". 2014-07-21 updated: Added patch for L3.10.17_1.0.0_GA BSP, the file is "L3.10.17_1.0.0_GA_bt656_output_patch_2014-07-21.zip". 2015-01-26 updated: Updated the IPU microcode for 1080i50 and 1080i60 BT1120 output, the parameters "N" for command BMA is a 8 bits parameters, so its max value is 255, but for 1080i50 and 1080i60 output, it needs more blank data in each line, the "N" will be bigger than 255, the updated IPU microcode can fix this limitation. The updated file is "IPU_Microcode_Update_for_BT1120_1080i_20150126.zip". You can update the macro "DC_MCODE_BT656_xxx"  and function _ipu_dc_setup_bt656_interlaced() to the old patch if you used BT1120 mode to support 1080i display. The verified 1080i display mode is: {    /* 1080I60 Interlaced output */   "BT1120-1080I60", 30, 1920, 1080, 13468,   20, 3,   20, 2,   280, 1,   FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,   FB_VMODE_INTERLACED,   FB_MODE_IS_DETAILED,}, {   /* 1080I50 Interlaced output */   "BT1120-1080I50", 25, 1920, 1080, 13468,   20, 3,   20, 2,   720, 1,   FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,   FB_VMODE_INTERLACED,   FB_MODE_IS_DETAILED,}, 2016-01-28 updated: Updated IPU microcode to align with BT656.4 specification for NTSC output. For other BSP version with NTSC format support, please reference to ipu_disp_update.c for the final microcode. File "L3.0.35_4.1.0_GA_bt656_output_patch_20160128.zip"., Details, please reference to the readme.txt file in the package. 2016-06-24 update: Added BT656 and BT1120 progressive mode support. File "L3.0.35_4.1.0_GA_bt656_output_patch_20160624.zip". Details, please reference to the readme.txt file in the package. The patch for 3.14.52 GA1.1.0 BSP will be released in next week. 2016-06-27 update: Add BT656 and BT1120 display patch for 3.14.52 BSP. File "L3.14.52_1.1.0_GA_bt656_output_patch_2016-06-27.zip", details, please reference to the readme.txt in the package. 2017-03-10 update: Fixed a hard coding DC macro issue for progressive mode. Added patch "0008-Fixed-a-hard-coding-DC-macro-issue-for-progressive-m.patch" in L3.0.35_4.1.0_GA_bt656_output_patch_2017-03-10.zip. The code in patch "L3.14.52_1.1.0_GA_bt656_output_patch_2016-06-27" is correct. Android Graphics & Display i.MX6DL i.MX6Dual i.MX6Quad i.MX6S Linux Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP You can remove the other displays from device tree: &mxcfb3 {  status = "disabled"; }; &mxcfb4 {  status = "disabled"; }; Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP No patch is needed, if you are using iMX6DQ, which has two IPU, you just need assign the two BT656 displays to two IPUs. Then in kernel command line, add two video mode for them: video=mxcfb0:dev=bt656,BT656-NTSC,if=BT656,fbpix=RGB32 video=mxcfb1:dev=bt656,BT656-NTSC,if=BT656,fbpix=RGB32 If it is iMX6S/DL which has only one IPU, it can't support such use case, because there is no enough space in CPMEM to run two BT656 microcode in one IPU. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Qiang_FSL‌ Dear Qiang,do we have a patch to support dual BT656 display? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi, Somebody already ported the patch to kernel 4.9.123? I tried to port this but got stuck. At boot I got a kernel panic saying "Failed set parent clk" After comparing the source I found out there are some things changed to the clk initialization in the new kernel, compared to 4.1.15. Clint Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP If you need HDMI to support different resolutions, then it has to use PLL5 alone. If your HDMI just need support some special resolution, then you can set PLL5 to a fixed frequency, and let BT1120 and HDMI to generate pixel clock from it. For example, if PLL5 is 594MHz, it can support 1080P HDMI (148.5MHz pixel clock) + BT1120 (74.25MHz pixel clock)  together. Except the programable PLL5, the IPU_DI clock source can be followed:       mmdc_ch0_axi 528MHz       pll3_usb_otg 480MHz       pll2_pfd0_352m       pll2_pfd2_396m       pll3_pfd1_540m Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP HI . Qiang Li-Mpu se Thank you very much for your reply. I will test the IIC signal strength according to your ideas. 26/5000 Thank you very much for your reply. I will test the IIC signal strength according to your ideas. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi yan zhang The I2C interface is the only interface iMX6 will read from adv7391, so I think you need check the I2C signal in -40 degree case, maybe the drive stregth for the I2C pins need be increased. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP yes, I think so, if you need to use mxcfb1, thy to set in the uboot command. for restriction, ipu can support up to 240M. for pixel clock set, you can refer to the patch and source code in the bsp cleanmaster. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang ,        Where can  I get  the patch for the IPU output the parallel video  format YUV422 8bit  with Hsync Vsync DE Pclk signals ? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hello All,                I too need this patch for L4.1.15. Has anybody got this? Ian Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hello everyone. I would like to try this patch. Where can I obtain the original source file to which patches can be applied? I tried two source files, but I get an error. https://github.com/embeddedarm/linux-3.0.35-imx6-android https://github.com/ADVANTECH-Corp/linux-imx6 Thank you for your support. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Any news on the availability of the patch for L4.1.15? If I have to port it on my own, what would be the best starting point? L3.14.52_1.1.0_GA_bt656_output_patch_2016-06-27.zip? Best regards  Martin Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP We also use 4.1.15 and need the patch for this version. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Qiang_FSL Hi, Qiang We're using Linux 4.1.15 on IMX6Q platform, and do you have patch for Linux 4.1.15? Or some patch here for Linux 3.x can also be used for Linux 4.1.15? Thanks for your help. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For that interlaced display patch, you can use such kind of double clock mode. I had tested on parallel LCD, for a 800*480 display, I can set the framebuffer to 400*480, and use that kind of double clock mode, the display can work fine. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Mm.... strange, if you check the link you gave me,  Patch for iMX6 BSP to support interlaced display on HDMI and LCD interface  in 4th comment you've mentioned DI_SYNC_CLK * 2, /* run_resolution */ should work. That's why I asked about it. Anuradha Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For BT656 mode, it is already two pixel clock to send out one pixel data. And this patch will not work with your "DI_SYNC_CLK * 2, /* run_resolution */" modification. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi, what is your idea about dual clock mode. Can I achieve this using DI_SYNC_CLK * 2, /* run_resolution */ ? Thanks Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Just simply doing this, can we get 2 clocks per pixel :   /* Active Pixel */     _ipu_di_sync_config(ipu,       disp,   /* display */       DI_SYNC_APIXEL,   /* counter */       0,   /* run count  */       DI_SYNC_CLK * 2, /* run_resolution */       h_start_width + h_sync_width,  /* offset  */       DI_SYNC_CLK,  /* offset resolution */       width,   /* repeat count  */       DI_SYNC_ALINE,   /* CNT_CLR_SEL  */       0,   /* CNT_POLARITY_GEN_EN  */       DI_SYNC_NONE,  /* CNT_POLARITY_CLR_SEL */       DI_SYNC_NONE,  /* CNT_POLARITY_TRIGGER_SEL  */       0,   /* COUNT UP  */       0  /* COUNT DOWN */       ); Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hello Qiang,  So in this TV encoder, 16-bit mode requires 2 clock cycles per pixel. Is it available under BT1120 mode in ipu_disp.c ? How to set the number of clock cycles required for pixel in ipu files ? Thanks Anuradha Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Display interface and framebuffer format can be different, just like the BT656 output, on display interface, it is 8 bits UYVY data, but in framebuffer, it can be RGB565, RGB32 ... ... Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi thanks for your reply. Can fbpix be RGB in UYVY16 interface mode ? I noticed in mxc_ipuv3_fb.c, always the fb pixel format is YUYV or UYVY for UYVY16 interface !! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Anuradha, For 16-bit YCbCr with HSYNC and HSYNC, you can reference to this patch: https://community.nxp.com/docs/DOC-100657 video=mxcfb0:dev=lcd,LCD-1080i50,if=UYVY16,fbpix=RGB32 "if=UYVY16" means 16-bit YCbCr with HSYNC and HSYNC output mode. You can add your own timing mode to replace the "LCD-1080i50" mode, the default BSP can't support UYVY16 mode output, it is enabled in that patch. For "RGB pixel format for BT656 8-bit mode", it can be supported too, you can use the DC for display, then no CSC, and the RGB data in framebuffer can be sent to 8 bit LCD interface directly. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang-Li, I use ADV7342 chip as a TV encoder which can also accept 16 bit pixel bus (16-bit YCbCr input). Anyway it does not support EAV/SAV, so I plan to use external VSYNC and HSYNC for that. Can I use BT1120 mode for this ? If yes what would be the pixel format for the frame buffer ?  fb_lcd{      if_fmt = BT1120;      if_pixel_fmt = ? } Moreover can we use an RGB pixel format for BT656 8-bit mode ? Thanks in Advance Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP You can use the BT656 progressive mode to output the 720P display, then use the followed patch to generate VSYNC on DI_PIN3 and HSYNC on DI_PIN2. In the patch, the VSYNC width is hardcoding as 10 HSYNC (2*10  /* COUNT DOWN */), and the HSYNC width is hardcoding as 80 pixel clocks (2*80  /* COUNT DOWN */), you can modify them as you wanted: diff --git a/arch/arm/mach-mx6/clock.c b/arch/arm/mach-mx6/clock.c index 2d5b497..d2d9556 100644 --- a/arch/arm/mach-mx6/clock.c +++ b/arch/arm/mach-mx6/clock.c @@ -5556,7 +5556,8 @@ int __init mx6_clocks_init(unsigned long ckil, unsigned long osc,   clk_set_rate(&pll4_audio_main_clk, 176000000);   clk_set_rate(&pll5_video_main_clk, 650000000);   - clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  /* For CVBS 27MHz clock */ +// clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  /* For CVBS 27MHz clock */ + clk_set_parent(&ipu1_di_clk[0], &pll5_video_main_clk);   clk_set_parent(&ipu1_di_clk[1], &pll5_video_main_clk);   clk_set_parent(&ipu2_di_clk[0], &pll5_video_main_clk);   clk_set_parent(&ipu2_di_clk[1], &pll5_video_main_clk); diff --git a/drivers/mxc/ipu3/ipu_disp.c b/drivers/mxc/ipu3/ipu_disp.c index 4dfb194..1d71447 100644 --- a/drivers/mxc/ipu3/ipu_disp.c +++ b/drivers/mxc/ipu3/ipu_disp.c @@ -2600,13 +2600,13 @@ int32_t ipu_init_sync_panel(struct ipu_soc *ipu, int disp, uint32_t pixel_clk,   } else if ((pixel_fmt == IPU_PIX_FMT_BT656) || (pixel_fmt == IPU_PIX_FMT_BT1120)) {    pixel_clk = pixel_clk / 10000;    pixel_clk = pixel_clk * 10000; -  if (pixel_clk < 74000000) { -   rounded_pixel_clk = 108000000; /* For PAL and NTSC */ - -   clk_set_rate(di_parent, 540000000); -   clk_set_rate(ipu->di_clk[disp], rounded_pixel_clk); -   clk_set_parent(&ipu->pixel_clk[disp], ipu->di_clk[disp]); -  } else { +//  if (pixel_clk < 74000000) { +//   rounded_pixel_clk = 108000000; /* For PAL and NTSC */ +// +//   clk_set_rate(di_parent, 540000000); +//   clk_set_rate(ipu->di_clk[disp], rounded_pixel_clk); +//   clk_set_parent(&ipu->pixel_clk[disp], ipu->di_clk[disp]); +//  } else {     rounded_pixel_clk = pixel_clk * 2;     rounded_parent_clk = clk_round_rate(di_parent,        rounded_pixel_clk); @@ -2622,7 +2622,7 @@ int32_t ipu_init_sync_panel(struct ipu_soc *ipu, int disp, uint32_t pixel_clk,      clk_round_rate(ipu->di_clk[disp], pixel_clk);     clk_set_rate(ipu->di_clk[disp], rounded_pixel_clk);     clk_set_parent(&ipu->pixel_clk[disp], ipu->di_clk[disp]); -  } +//  }   } else {    /* try ipu clk first*/    dev_dbg(ipu->dev, "try ipu internal clk\n"); @@ -3123,11 +3123,11 @@ int32_t ipu_init_sync_panel(struct ipu_soc *ipu, int disp, uint32_t pixel_clk,       DI_SYNC_NONE,  /* offset resolution */       0,   /* repeat count */       DI_SYNC_NONE,  /* CNT_CLR_SEL */ -     0,   /* CNT_POLARITY_GEN_EN */ +     1,   /* CNT_POLARITY_GEN_EN */       DI_SYNC_NONE,  /* CNT_POLARITY_CLR_SEL */ -     DI_SYNC_NONE,  /* CNT_POLARITY_TRIGGER_SEL */ +     DI_BT656_SYNC_BASECLK,  /* CNT_POLARITY_TRIGGER_SEL */       0,   /* COUNT UP */ -     0  /* COUNT DOWN */ +     2*80  /* COUNT DOWN */       );       vsync_cnt = DI_BT656_SYNC_IVSYNC; @@ -3142,11 +3142,11 @@ int32_t ipu_init_sync_panel(struct ipu_soc *ipu, int disp, uint32_t pixel_clk,       DI_SYNC_NONE,  /* offset resolution */       0,   /* repeat count */       DI_SYNC_NONE,  /* CNT_CLR_SEL */ -     0,   /* CNT_POLARITY_GEN_EN */ +     1,   /* CNT_POLARITY_GEN_EN */       DI_SYNC_NONE,  /* CNT_POLARITY_CLR_SEL */ -     DI_SYNC_NONE,  /* CNT_POLARITY_TRIGGER_SEL */ +     DI_BT656_SYNC_HSYNC,  /* CNT_POLARITY_TRIGGER_SEL */       0,   /* COUNT UP */ -     0  /* COUNT DOWN */ +     2*10  /* COUNT DOWN */       );       /* COUNTER_5: first active line */ diff --git a/drivers/video/mxc/mxc_bt656if.c b/drivers/video/mxc/mxc_bt656if.c index 0ad5dee..800ac42 100644 --- a/drivers/video/mxc/mxc_bt656if.c +++ b/drivers/video/mxc/mxc_bt656if.c @@ -44,6 +44,7 @@ struct mxc_bt656if_data {   * vsync_len: not used, set to 1   */  static struct fb_videomode bt656if_modedb[] = { +#if 0   {    /* NTSC Interlaced output */    "BT656-4-NTSC", 60, 720, 487, 37037, @@ -161,6 +162,52 @@ static struct fb_videomode bt656if_modedb[] = {    FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,    FB_VMODE_NONINTERLACED,    FB_MODE_IS_DETAILED,}, +#endif + { +  /* NTSC Progressive output */ +  "BT656-480P", 60, 720, 480, 20833, +  36, 9, +  0, 0, +  276, 1, +  0, +  FB_VMODE_NONINTERLACED, +  FB_MODE_IS_DETAILED,}, + { +  /* PAL Progressive output */ +  "BT656-576P", 50, 720, 576, 20833, +  44, 5, +  0, 0, +  288, 1, +  0, +  FB_VMODE_NONINTERLACED, +  FB_MODE_IS_DETAILED,}, + { +  /* 1280x720 Progressive output */ +  "BT656-720P", 60, 1280, 720, 20833, +  25, 5, +  0, 0, +  732, 1, +  0, +  FB_VMODE_NONINTERLACED, +  FB_MODE_IS_DETAILED,},  };  static int bt656if_modedb_sz = ARRAY_SIZE(bt656if_modedb); Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP 嗨,Hi Qiang 感谢你的工作,我们按照这个文章打了L3.14.52_1.1.0_GA_bt656_output_patch_2016-06-27这个补丁,BT656交错模式下工作正常。 目前我们有新的需求,想通过8位数据线+CLK+VSYNC+HSYNC输出720P的UYVY数据,拟使用引脚如下: pinctrl_ipu1_bt656: ipu1grp-3 { fsl,pins = < MX6QDL_PAD_DI0_DISP_CLK__IPU1_DI0_DISP_CLK 0x10 MX6QDL_PAD_DI0_PIN15__IPU1_DI0_PIN15 0x10 MX6QDL_PAD_DI0_PIN2__IPU1_DI0_PIN02 0x10 MX6QDL_PAD_DI0_PIN3__IPU1_DI0_PIN03 0x10 MX6QDL_PAD_DI0_PIN4__IPU1_DI0_PIN04 0x80000000 MX6QDL_PAD_DISP0_DAT16__IPU1_DISP0_DATA16 0x10 MX6QDL_PAD_DISP0_DAT17__IPU1_DISP0_DATA17 0x10 MX6QDL_PAD_DISP0_DAT18__IPU1_DISP0_DATA18 0x10 MX6QDL_PAD_DISP0_DAT19__IPU1_DISP0_DATA19 0x10 MX6QDL_PAD_DISP0_DAT20__IPU1_DISP0_DATA20 0x10 MX6QDL_PAD_DISP0_DAT21__IPU1_DISP0_DATA21 0x10 MX6QDL_PAD_DISP0_DAT22__IPU1_DISP0_DATA22 0x10 MX6QDL_PAD_DISP0_DAT23__IPU1_DISP0_DATA23 0x10 >; }; 我们的疑问是,在本文补丁下,是否可以支持这么操作,我们该如何配置相关资源?可以给出一些指导意见,谢谢! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes, it can.  1) For 8 bits BT656 interface, the default data pins are "DISP0_DAT_23~DISP0_DAT_16", it can also        be any other continued display data pins, for example if "DISP0_DAT_7~DISP0_DAT_0" are used, the        macro "BT656_IF_DI_MSB" in "kernel_imx/drivers/mxc/ipu3/ipu_disp.c" should be changed from "23"        to "7". Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Sir, customer ask about hardware connect pads between i.MX6 and ADV7391. Could use IPU1_DISP0_DAT_23~DISP0_DAT_16 connected to adv7391 P7~P0 pins? Please help confirm it. Thanks a lot, We checked NXP TV box reference design .i.MX6 OTT TVBox HW/SW Reference Design Release (ICS4.0.4_1.0.0-alpha)  P7~P0 pins of ADV7390 is connect i.MX6 IPU_DISP_Data0~7. We checked the patch in https://community.nxp.com/docs/DOC-94019 Meanwhile find some code about setting DISP_DAT23 ~ DISP_DAT16 or DISP_DAT7 ~ DISP_DAT0 to output “8 bits BT656” Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi all, Did anyone try to get PAL out of an ADV7393 chip? NTSC works perfectly, thanks for the effort. However, PAL seems to be harder on me. I modified the kernel video= boot argument to show PAL. When starting gstreamer test pattern generator, i do get graphics on my PAL monitor. It does, however, seem confused wjth tining somehow. The image seems to flicker, sometimes some grey raster seems to be under the color bars and from the second half, i get the impression that a new frame starts overlapping. The behavior is equally unstable but presents itself somewhat differently on another PAL television I have. Would this ring a bell for someone? Thanks a lot  Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi llinguo, you can apply the patch "L3.14.52_1.1.0_GA_bt656_output_patch_2016-06-27", then porting the adv739x driver from L3.0.35_4.1.0. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang    Our BSP version is 3.4.52.I want to download the patch "L3.14.52_1.1.0_GA_bt656_output_patch_2016-06-27",but i don't find the driver of adv7393. Can I download the patch "L3.0.35_4.1.0_GA_bt656_output_patch_2017-03-10",then add this patch in  the BSP 3.14.52? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear @qiang Li,  I have a question on xserver settings, for the below mode : /* NTSC Interlaced output */ + "BT656-NTSC", 60, 720, 480, 37037, + 19, 3, + 20, 3, + 276, 1, + FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT, + FB_VMODE_INTERLACED, + FB_MODE_IS_DETAILED,}, what should be the correct xserver mode settings ? The issue is I cannot get the accelerated frame buffer output to fb0 !!!  Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP The 20833 is just a reference setting for pixel clock, you can adjust it. With the 20833, pixel clock frequency = 10^12 / 20833 = 48MHz, for 60fps setting, the pixel clock should be 148.5MHz, so 20833 should be 6734. How many pixel clocks for one frame: (1280*2 + 732) * (720 + 25 + 5) = 2469000; so the display refresh rate = 148.5M / 2469000 = 60fps. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang,         How to calculate the pclk in 720p mode?         10^12 /((1280*2+25+5+732)*(720+0+0+1))   is not equal 20833 Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Thanks a lot! I will try it. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP diff --git a/drivers/video/mxc/mxc_bt656if.c b/drivers/video/mxc/mxc_bt656if.c index 0ad5dee..800ac42 100644 --- a/drivers/video/mxc/mxc_bt656if.c +++ b/drivers/video/mxc/mxc_bt656if.c @@ -44,6 +44,7 @@ struct mxc_bt656if_data {   * vsync_len: not used, set to 1   */  static struct fb_videomode bt656if_modedb[] = { + { +  /* 1280x720 Progressive output */ +  "BT656-720P", 60, 1280, 720, 20833, +  25, 5, +  0, 0, +  732, 1, +  0, +  FB_VMODE_NONINTERLACED, +  FB_MODE_IS_DETAILED,},  };  static int bt656if_modedb_sz = ARRAY_SIZE(bt656if_modedb); Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang,     Thank you very much!      I have one question at last, how to add a config for 720p(1280x720) output? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP 1. The progressive patch had been added here at 2016-06-24. 2. Sample code to adjust pulse width had been given. I haven't tuned the BT656 interlaced mode VSYNC and HSYNC signals, you can try it by yourself. 3. I had shown you the sample code. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I have three questions below:        1. As you reply before, this patch can't support progressive well, if other change or patch are necessary?        2. After we use this patch, and test BT656 PAL interlace mode, we can measure external HSYNC on DI0_PIN2, and external VSYNC on DI0_PIN4, and the frequency is right, but pulse width is too small(only 1 pixel clock).        3. Our backend need the VSYNC can keep one or two HSYNC period, not only some pixel period. How to config?   Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP The followed is an example code to generate VSYNC and HSYNC signals for BT656 progressive mode. The HSYNC width is 20 pixel clocks, and the VSYNC width is 10 HSYNC width. For BT656 interlaced mode, since it has two fields, it is difficult to support VSYNC and HSYNC signals. diff --git a/drivers/mxc/ipu3/ipu_disp.c b/drivers/mxc/ipu3/ipu_disp.c index 4dfb194..1d71447 100644 --- a/drivers/mxc/ipu3/ipu_disp.c +++ b/drivers/mxc/ipu3/ipu_disp.c @@ -3123,11 +3123,11 @@ int32_t ipu_init_sync_panel(struct ipu_soc *ipu, int disp, uint32_t pixel_clk,    _ipu_di_sync_config(ipu,      disp,   /* display */      DI_BT656_SYNC_HSYNC,   /* counter */      h_total - 1,  /* run count */      DI_SYNC_CLK, /* run_resolution */      0,   /* offset */       DI_SYNC_NONE,  /* offset resolution */       0,   /* repeat count */       DI_SYNC_NONE,  /* CNT_CLR_SEL */ -     0,   /* CNT_POLARITY_GEN_EN */ +     1,   /* CNT_POLARITY_GEN_EN */       DI_SYNC_NONE,  /* CNT_POLARITY_CLR_SEL */ -     DI_SYNC_NONE,  /* CNT_POLARITY_TRIGGER_SEL */ +     DI_BT656_SYNC_BASECLK,  /* CNT_POLARITY_TRIGGER_SEL */       0,   /* COUNT UP */ -     0  /* COUNT DOWN */ +     2*20  /* COUNT DOWN */       );       vsync_cnt = DI_BT656_SYNC_IVSYNC;    /* COUNTER_3: VSYNC for each frame */    _ipu_di_sync_config(ipu,      disp,   /* display */      DI_BT656_SYNC_IVSYNC,   /* counter */      v_total - 1,  /* run count */      DI_BT656_SYNC_HSYNC, /* run_resolution */      0,    /* offset */       DI_SYNC_NONE,  /* offset resolution */       0,   /* repeat count */       DI_SYNC_NONE,  /* CNT_CLR_SEL */ -     0,   /* CNT_POLARITY_GEN_EN */ +     1,   /* CNT_POLARITY_GEN_EN */       DI_SYNC_NONE,  /* CNT_POLARITY_CLR_SEL */ -     DI_SYNC_NONE,  /* CNT_POLARITY_TRIGGER_SEL */ +     DI_BT656_SYNC_HSYNC,  /* CNT_POLARITY_TRIGGER_SEL */       0,   /* COUNT UP */ -     0  /* COUNT DOWN */ +     2*10  /* COUNT DOWN */       );       /* COUNTER_5: first active line */ Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP How to support external HSYNC and VSYNC for BT656? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP VSYNC and HSYNC signals are not supported. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang,     How to increase VSYNC wave width in BT656 interlace mode? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang, I solved the issue by setting correct xrandr display timings for DISP3 BG, and now lcd works fine. But I still have a question. Using this xrandr commands, I was able to set the interlace mode settings for TV encoder without introducing an interlace mode in mxc_lcdif ! Does mxc_lcdif mode only affects frame buffer devices ? When mode is set through x11, no need to introduce modes ? Thanks in Advance Anuradha Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP for xrandr -q, I only get following modes and info : Screen 0: minimum 240 x 240, current 800 x 600, maximum 8192 x 8192 DISP3 BG connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm U:800x600p-60 60.00* U:480x800p-57 80.32 U:800x480p-57 57.00 U:800x480p-60 60.00 60.00 U:480x800p-60 60.00 U:720x480p-60 60.00 U:640x480p-60 85.67 U:1280x120p-60 123.84 So I used following settings : export DISPLAY=:0.0 xrandr --newmode "1440x480i-60" 27 1440 1403 1459 1716 480 481 483 500 interlace +hsync +vsync xrandr --addmode "DISP3 BG" 1440x480i-60 xrandr --output "DISP3 BG" --mode 1440x480i-60 And then : echo U:1440x480i-60 > /sys/class/graphics/fb0/mode Can you please verify whether my xrandr settings look okay ? I have no issue running this without X11 acceleration. So i assume this must be an issue of xrandr settings ! Any insight would be appreciated ! Thanks  Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, now I am getting the following output on TV display. I already mentioned that I had modified xorg files in my previous comment The horizontal lines shown on the upper side of the LCD are from imxeglvivsink. So now the pipeline works with imxeglvivsink, no errors of X11. But why the video is corrupted ? I'm wondering whether I have missed something, apart from what you mentioned. I can run test sources with imxg2dsink and imxipuvideosink without any distortion !  Btw could you please kindly share your xorg.conf file settings ?  Thanks  Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP As I mentioned, you need modify the code in downloads/xserver-xorg-video-imx-viv-xxxxxx.tar.gz to make X11 support interlaced display. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi, you were right about g2dsink, it does not require X11 support. I made the changes you suggested at imx_display.c ! but I am getting following error when running gst test patterns with imxeglvivsink ! 0:00:00.139761000 492 0x1b6cda0 ERROR imxeglplatform_x11 egl_platform_x11.c:90:gst_imx_egl_viv_sink_egl_platform_create: could not open X display My TV only supports interlaced PAL and NTSC. What else can cause this issue ? Anuradha Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP If you are using Yocto, the package can be found at "downloads/xserver-xorg-video-imx-viv-xxxxxx.tar.gz" Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Can you please kindly tell me in which location I can find this source code ?  Thanks Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Aneradha, not sure for autovideosinks, but the g2d sink has no depends to Xserver. If you need Xserver for interlaced display, that modification is needed. You can also switch the framebuffer to BT656 progressive to try and double confirm it. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang,  I can run pipelines with imxg2dvideosink and autovidiosinks on encoder output. When running imxeglvivsink, the display doesn't come up. When debug mode is on in the pipeline, I get the message, 'cannot open X window'.  Since g2d and auto work, i guess Xserver setup for encoder display should be okay right ? In which directory we can access above source code ? If it has to be changes, then do we need to compile X11 vivante drivers from scratch ? Thanks in Advance Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Did you check if the xserver had set display mode to the fb0? If so, maybe the mode is not correct which caused BT656 display fail to work. And in xserver code, such as xserver-xorg-video-imx-viv-3.10.53-1.1.0\EXA\src\vivante_fbdev\imx_display.c For default, it doesn't support interlaced display mode, you need remove that code as followed: ModeStatus imxDisplayValidMode(VALID_MODE_DECL) { #ifndef XF86_SCRN_INTERFACE  ScrnInfoPtr pScrn = xf86Screens[arg]; #else  ScrnInfoPtr pScrn = arg; #endif - if (mode->Flags & V_INTERLACE) { -  if (verbose) { -   xf86DrvMsg(pScrn->scrnIndex, X_PROBED, -       "Removing interlaced mode \"%s\"\n", -       mode->name); -  } -  return MODE_BAD; - }  return MODE_OK; } Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Thanks for your reply Qiang ! I have two questions. Now when running RGB signals with TV encoder (let's assume this is assigned to fb0), can we use vivante acceleration to this frame buffer ? i.e (fb0 is for RGB and fb2 for HDMI) : Section "Device"       Identifier "i.MX Accelerated Framebuffer Device"       Driver "vivante"       Option "fbdev" "/dev/fb0"       Option "vivante_fbdev" "/dev/fb0"       Option "HWcursor" "false" EndSection Section "Device"       Identifier "Framebuffer Device2"       Driver "fbdev"       Option "fbdev" "/dev/fb2"       Option "HWcursor" "false" EndSection When I set like this, the pixel clock of the encoder gets a different value. Which means I cannot use accelerated frame buffer for the encoder ? Thanks in Advance Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes, it is supported. List all supported modes: # cat /sys/class/graphics/fb0/modes Switch the mode: # echo D:720x480i-60 > /sys/class/graphics/fb0/mode Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi, is this on-the fly switching possible to perform between two lcd entries defined in mxc_lcdif.c ? i.e. switching between PAL and NTSC timing modeS ? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang Li, Hi, I have a question about PAL-NTSC mode switching of the imx6 board. When we set uboot first for let's say BT656-NTSC (so adv outputs NTSC), can we change the mode to BT656-PAL without changing uboot parameters and rebooting ? I think ADV7391 has different i2c settings for different timing doesn't it ? Thanks Anuradha Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP iMX6S/DL can't support two BT656 output. For each BT656 output, the IPU need use 142 DC words logic to generate the signal. But on each IPU, there are total 256 DC words, so it is not enough to generate two BT656 signal. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang,      Whether  iMX6S/DL support double  adv739x simultaneous? Gordon Lin Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I apologize if this is a dumb question, but why do I not see any patches for the adv739x driver for the 3.14.52 kernel? Thanks! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Thanks for your efforts! Very expect Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Progressive mode IPU mocricode is under development now, it will be ready at about July. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP We have a joint project with D-Chip...need a progressive mode instead of a interlace mode..I checked the Reference Manual v4..it mentioned on section 37.4.6.2.1, progressive mode is supported by hardware. My question is, would you please confirm, hardware is OK for this, but firmware can not support this mode yet? If we want to make a patch for this target, do you have some suggestions, or some instruction sheet to change it? My contact is, [email protected] Thanks a lot.. Abel Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi qiang, "create an IPU microcode like _ipu_dc_setup_bt656_interlaced()" is to hard for me. do you help the plan to support the BT656 progressive mode? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP To support BT656 progressive mode, you need create an IPU microcode like _ipu_dc_setup_bt656_interlaced() which can create embeded EAV/SAV code into data line for BT656 progressive mode. For VSYNC/HSYNC mode, it means there no EAV/SAV data on data line, only video data are sent on data line, all timing signals are sent on VSYNC and HSYNC pins. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi,qiang, Can you give me some advice to let the imx6 to support BT656 progressive mode ? Or what's the means about " use VSYNC/HSYNC mode for that panel." ? I must use this LCD.please some help Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Wilson, your LCD is BT656 progressive mode, it can't be supported by this patch, you'd better use VSYNC/HSYNC mode for that panel. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi qiang,    I use a YUV LCD (the interface is YUV) TFTMD030011 , 8bit BT656 NTSC mode.  the patch is 27MHZ , but the LCD must be 54MHZ  : I found the https://community.freescale.com/message/443002#comment-443002  ,you said : For 8 bits BT656 interface, NTSC mode, the pixel clock is 27MHz.     For each line, calculated in pixel clock count: Total 1716 clocks = EAV code(4) + Blanking Video(67*4) + SAV code(4) + Active Video(720*2) = 276 + 1440, in NTSC mode, there are total 525 lines (19+240+3+20+240+3) for each frame, and frame rate is 30Hz, so the pixel clock frequency = 525 * 1716 * 30 =  27.027MHz. Now,I want to configure the refresh to 60HZ, so the pixel clock frequency will be 525 * 1716 * 60 =  54.054MHz. how should i configure the bsp bt656 code ? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Please make sure the function _ipu_dc_setup_bt656_interlaced() had been updated to last version L3.0.35_4.1.0_GA_bt656_output_patch_20160128 By the way, I haven't seen such issue. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Li Qiang:      After I applied this patch , CVBS can display OK, but screen blink (blink on the top of screen) when white color in the right of the screen. test case :  gst-launch-1.0 videotestsrc horizontal-speed=-3 ! imxv4l2sink And other case is the same issue (play a video file use gplay and gst-play) when white color in the right of the screen. Any idea to solve this problem ? Thanks ! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang Li, Thank you very much! Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP You can find it in drivers/mxc/ipu3/ipu_disp.c /*     Y = R *  1.200 + G *  2.343 + B *  .453 + 0.250;        U = R * -.672 + G * -1.328 + B *  2.000 + 512.250.;        V = R *  2.000 + G * -1.672 + B * -.328 + 512.250.;*/ static const int rgb2ycbcr_coeff[5][3] = { {0x4D, 0x96, 0x1D}, {-0x2B, -0x55, 0x80}, {0x80, -0x6B, -0x15}, {0x0000, 0x0200, 0x0200}, /* B0, B1, B2 */ {0x2, 0x2, 0x2}, /* S0, S1, S2 */ }; Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang Li, We have applied your patch to jb4.2.2_1.1.0. So, I think that the color space is converted from RGB to BT.656 in CSC function. Refer to 37.4.9.5 Color Space Conversion unit - CSC in IMX6DQRM (Rev.2). Could you tell me the conversion coefficient value of the color space (CSC_A0~A8, CSC_B0~B2, CSC_S0~2)? (We couldn't dump the register by debugger.) Best Regards, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I think you need porting it, but the IPU microcode can be re-used directly, it is not kernel version related. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang,      I use imx6q and L3.14.28 Yocto.     Do you have patches to support BT656 and BT1120  based on adv7391 TV encoder?     Best Regards! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP thank you for your response !! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi moowon, you can't use this patch, because iMX6SX has no IPU hardware. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi I use imx6sx and L3.10.53_1.1.0-ga Yocto. I am patching to support BT656. but I have problem. In mxc_ipuv3_fb.c, I add these in mxcfb_set_par func. ( static int mxcfb_set_par(struct fb_info *fbi)  )         if ((mxc_fbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT656) || (mxc_fbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT1120)) {                  if (mxc_fbi->dispdrv && mxc_fbi->dispdrv->drv->disable)                          mxc_fbi->dispdrv->drv->disable(mxc_fbi->dispdrv);         } result of compile: drivers/video/mxc/mxc_ipuv3_fb.c:510:4: error: too few arguments to function 'mxc_fbi->dispdrv->drv->disable'     mxc_fbi->dispdrv->drv->disable(mxc_fbi->dispdrv);     ^ make[3]: *** [drivers/video/mxc/mxc_ipuv3_fb.o] Error 1 so, I found "disable func " in mxc_dsipdrv.h 33 struct mxc_dispdrv_driver { 34         const char *name; 35         int (*init) (struct mxc_dispdrv_handle *, struct mxc_dispdrv_setting *); 36         void (*deinit) (struct mxc_dispdrv_handle *); 37         /* display driver enable function for extension */ 38         int (*enable) (struct mxc_dispdrv_handle *, struct fb_info *); 39         /* display driver disable function, called at early part of fb_blank */ 40         void (*disable) (struct mxc_dispdrv_handle *, struct fb_info *); 41         /* display driver setup function, called at early part of fb_set_par */ 42         int (*setup) (struct mxc_dispdrv_handle *, struct fb_info *fbi); 43 }; disable's function pionter has two arg. but  In patch, has one arg. How do I resolve that? Um... Is it right that I revise  below ?        if ((mxc_fbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT656) || (mxc_fbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT1120)) {                  if (mxc_fbi->dispdrv && mxc_fbi->dispdrv->drv->disable)                          mxc_fbi->dispdrv->drv->disable(mxc_fbi->dispdrv, fbi ); Thank you for reading. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang, Thank you for your reply. My customer tried to change the other IPU from current IPU for LVDS out. Their code was skipped the "ret = mxcfb_setup_overlay(pdev, fbi, res);" at the changing to "ipu_id = 1". They added the frame buffer creation, LVDS out could change the another IPU and output to display. Best Regards, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For iMX6DQ, since there are two IPUs, you can assign BT656 and other display to two IPUs. There is no such limitation for dual display case. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I appreciate for your great support. Let me clarify my understanding about "r13.4.1_bt656_output_patch_2013-09-04.zip". My customer attached this patch and modify the code to apply their custom board with i.MX6DQ. But, the frame buffer for overlay was not created with the influence of the custom modification. As the result. It wasn't possible to work. Is it necessary the frame buffer for overlay to output BT.656? (They tried to create the frame buffer, It could work correctly. So, we think that it is needed.) [read me.txt in "r13.4.1_bt656_output_patch_2013-09-04.zip"] >    4) In iMX6S/DL Android, there is only one IPU, in this case, the BT656 output should be the second display, >       the 0003-Enhance-dual-display-support-for-BT656-output.patch will assign IPU DC channel to main display, >       and BT656 will use IPU DP as fb2, the overlay will be fb1. Best Regards, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi qiang, now i can use CVBS+LVDS+HDMI the same time ,use this command: setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rootwait rw video=mxcfb1:dev=ldb,LDB-SVGA,if=RGB24 ldb=sin0 video=mxcfb2:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb0:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565'  that the CVBS is the fb0 device. when i want the CVBS to the fb2 device,use this command: setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rootwait rw video=mxcfb0:dev=ldb,LDB-SVGA,if=RGB24 ldb=sin0 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb2:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565' I start the board,it stop in the kernel,that's the log: .................................. ................................. JFFS2 version 2.2. (NAND)  2001-2006 Red Hat, Inc. msgmni has been set to 2822 alg: No test for stdrng (krng) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver ldb _regulator_get: get() with no identifier mxc_ldb mxc_ldb: change IPU DI1 to IPU DI0 for LDB channel0. imx-ipuv3 imx-ipuv3.1: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) Console: switching to colour frame buffer device 128x48 mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver hdmi mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1 fbcvt: 1920x1080@60: CVT Name - 2.073M9 mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver adv739x  (stop here and not continue) what 's the problem? Can you give me some advice? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes, you can study and understand the code in ipu_disp.c, function _ipu_dc_setup_bt656_interlaced(), the related IPU microcode commands can be found from iMX6 reference manual: Table 37-26. DC template's commands description. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes, you can, for example (HDMI is IPU1 DI1 display, LVDS is IPU2 DI1 display): video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb2:dev=adv739x,BT656-NTSC,if=BT656,fbpix=UYVY16 Note, in this case, since IPU DP had been used by another two layer display, the BT656 display's frame buffer must be YUV format, there is no on the fly CSC from RGB to YUV on BT656 display. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Is it possible to modify the microcode by user? (If it can be modified, how is it possible to change microcode?) In case of applying a changed microcode to BSP, is it possible to apply by replacing some file? Best Regards, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang_FSL​ Is it possible to move the bt656 output to fb4? The use case is a 3 displays system. 2 displays will be rendering video, hence overlay framebuffer is needed for HMI content. The display with bt656 is not intended for videoplayback so no overlay is needed. Display 1 -->  fb0 (background)  fb1(overlay) Display 2 -->  fb2 (background)  fb3(overlay) Display 3 -->  fb4 (bt656) Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi,qiang, Thank you for your quick reply! I have solved the problem. the third display is closed,I must turn on it Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For multi display resoure assignment, except the clock, the board file should also be checked. You can reference to How to config four-screen display -blog archive Each IPU can support two display device with three frame buffer, fb1 is the overlay. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I search the arch/arm/mach-mx6/clock.c I found : int __init mx6_clocks_init(unsigned long ckil, unsigned long osc, clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  /* For CVBS 27MHz clock */ clk_set_parent(&ipu1_di_clk[1], &pll5_video_main_clk); clk_set_parent(&ipu2_di_clk[0], &pll5_video_main_clk); clk_set_parent(&ipu2_di_clk[1], &pll5_video_main_clk); clk_set_parent(&ldb_di0_clk,&pll2_pfd_352M); clk_set_parent(&ldb_di1_clk,&pll2_pfd_352M); BT656 on IPU1 DI0, HDMI on IPU2 DI0,LVDS on IPU2 DI1。 above is ok? i also found other problem: when i use: setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rootwait rw video=mxcfb0:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb2:dev=ldb,LDB-SVGA,if=RGB24 ldb=sin0' if i want to draw green colors to the hdmi,i must use"  ./fb_green /dev/fb2 " ,but not the " ./fb_green /dev/fb1". why? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I search the arch/arm/mach-mx6/clock.c I found : int __init mx6_clocks_init(unsigned long ckil, unsigned long osc, clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  /* For CVBS 27MHz clock */ clk_set_parent(&ipu1_di_clk[1], &pll5_video_main_clk); clk_set_parent(&ipu2_di_clk[0], &pll5_video_main_clk); clk_set_parent(&ipu2_di_clk[1], &pll5_video_main_clk); clk_set_parent(&ldb_di0_clk,&pll2_pfd_352M); clk_set_parent(&ldb_di1_clk,&pll2_pfd_352M); BT656 on IPU1 DI0, HDMI on IPU2 DI0,LVDS on IPU2 DI1。 above is ok? i also found other problem: when i use: setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rootwait rw video=mxcfb0:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb2:dev=ldb,LDB-SVGA,if=RGB24 ldb=sin0' if i want to draw green colors to the hdmi,i must use"  ./fb_green /dev/fb2 " ,but not the " ./fb_green /dev/fb1". why? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP You should pay attention to clock source and IPU DI port assignment: For example: BT656 on IPU1 DI0, clock source pll3_pfd_540M. HDMI on IPU2 DI0, clock source pll5_video_main_clk. LVDS on IPU2 DI1, clock source pll2_pfd_352M. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi,qiang, I use the linux rootfs. when I use the command: setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rootwait rw video=mxcfb0:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb2:dev=ldb,LDB-SVGA,if=RGB24 ldb=sin0' I can draw something to the CVBS and HDMI ,this is work. but the lvds cannot,when I draw something to it's frame buffer ,nothing can see . also when I use this command: setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk0p1 rootwait rw video=mxcfb0:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565 video=mxcfb2:dev=ldb,LDB-SVGA,if=RGB24 ldb=sin0 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24 ' I can draw something to the CVBS and LVDS display.but the hdmi cannot. what's the problem. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP You need draw something to third display's frame buffer and unblank it. If you are using Android, the android framework supports two displays default. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP HI,Qiang. I want to use CVBS+HDMI+LVDS, but only when CVBS+HDMI or CVBS+LVDS could work,the thirth display cannot display anything. how can I do? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, We found the violation of BT.656 specification about F bit(field1/field2), V bit, H bit(SAV/EAV). I send you the result of analysis about violation of BT.656 specification by e-mail. [Q1] Is it possible to fix the patch to comply BT.656? (I want your answer asap.) [Q2] If Q1 yes, when will you release the fixed patch? Best Regards, Keita I send you the result of analysis about violation of BT.656 specification. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes, the SAV and EAV is same as BT656 specification. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Thank you for your quick reply! I have one more question. Does this patch support the Video timing reference code [F bit(field1/field2), V bit, H bit(SAV/EAV)] of BT.656? Best Regards, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Keita, I think HIZ should be OK for your use case. You can also try on your current board to check if there is still BT656 signal output after HIZ setting. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Now, our system can work the BT.656 output correctly in jb4.2.2_1.1.0 by your patch. And, we are considering the dual output source to single display for next product model. (i.e we would like to change the video source i.MX6 or HDMI Rx.) Refer to below system image. [Question] Q1. By the setting of DSE=Hi-z, is it possible to cut the bus of i.MX6 and HDMI Rx? (We would like to judge the whether or not external bus switcher is necessary.) Q2. Is the any special processing necessary except for DSE setting? Best Regards, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP It causes some flickering and distortions in the display output for time to time (once every few seconds). We think the PLL in the display module fails to derive the input clock and gets out of sync when it receives many consecutive zeros which happens during vertical blanking and this causes the flickering and sudden "jumps" in the display output. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes, you are right, for that blanking, we just let the data line keep in last data state. Will this impact your display? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I am getting sudden "jumps" in the output video. Using an FGPA to probe the display output, it seems the data during vertical blanking is not valid. Here is a screenshot: http://i.imgur.com/3wvuZFB.png Note the 000 and 2AC values during vertical blanking. I think it should be 200 and 040 respectively. The configuration I am using is BT1120-1080I50. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP HI Qiang, I'm running kernel 3.10.17 on iMX6Q with ADV7391. unzip "L3.10.17_1.0.0_GA_bt656_output_patch_2014-07-21.zip" but only get "0001-Support-BT656-and-BT1120-output-for-iMX6-ipuv3.patch" Should i use ADV7391 patch?  Where i can find the patch? Can i use old version "0002-Support-adv739x-TV-encoder-for-BT656-output.patch" of "L3.0.35_1.1.0_GA_bt656_output_patch_2013-08-09.zip" ? Thanks, Darren Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For iMX6Q, I think it can support two BT656 output, each IPU run one BT656 output. But I haven't tried such use case. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi, is it possible to have 2 separate BT.656 video outputs for SD PAL CVBS video (clk + 8 data lines, EAV/SAV, ADV7391)? No other video outputs are required. We are using Yocto with freescale kernel 3.10 on i.MX6Q automotive. Which pins should we connect the 2 ADV7391 to? Which patch or driver should we use? Regards, Mario Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP HI Qiang Can you answer me a question about Nand flash? https://community.freescale.com/message/456560#456560 Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I have this setup - ipu1 disp0 = lcd ipu1 disp1 = Not used ipu2 disp0 = hdmi ipu2 disp1 = Mipi Display After applying the patch the contents of the Mipi display is corrupted when I start playback on the HDMI output. LCD not used in this test scenario. Any ideas on what it could be ? I'm using L3.10.17_1.0.0_GA Any hints would be appreciated Thanks, /Otto Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang Li, Thanks for this patch. I couldn't apply it to my kernel automatically (Bluechip Technology's Yocto Layer) so made the changes by hand. It works nicely using mxcfb0:dev=adv739x,BT656-NTSC,if=BT656,fbpix=RGB24 and running mxc_v4l2_tvin.out set with an NTSC camera. But with PAL settings there is a flickering almost like the interlace order is wrong. I've also had the occasional IPU errors: imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x00000001 imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00080000 Once difference I've noticed between PAL and NTSC is in mxcfb_adv739x.c, adv739x_modedb has FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT set for NTSC and not PAL. Is this correct? Thanks in advance Jamie Whitham Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP HI Qiang: when do you update BT656 and BT1120 progressive support? The manual without obvious setting BT1120 progressive mode,I try to understand your patch, but I don't understand why you are so set the DC and DI register,Can you give me some advice and how to set up BT1120 progressive ? How to understand  Microcode ? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Isaac, there is no such plan, for progressive mode, another IPU microcode was needed, like the function _ipu_dc_setup_bt656_interlaced(), it is not a easy task, based on my experience, it needs about 6 weeks to implement such a code. So if you need it, I think you can check with Freescale marketing people wether it can be supported in software service way. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Any update on BT656/BT1120 progressive mode? We also have a tight deadline. If there isn't a schedule for the patch yet, can you provide some general description on what should be done in this patch? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Casper, you can port it from the current Linux patch, it is very simple since they are based on the same kernel version. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang,     Where I can find ADV7393 or BT656 patch for android-4.4.2_r1 ? Thanks, Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For 1, no BT656 and BT1120 progressive support. For 2, yes. For 3, the default BSP doesn't support YUV output, you can reference to "https://community.freescale.com/docs/DOC-100657" to add UYVY16 output on LCDIF, that patch was tested on 16bits LCD interface with UYVY16 1080i output in VSYNC and HSYNC mode. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP HI Qiang: 1.Do you update this patch to the BT1120 1080p now? 2.I have to use the HSYNC, VSYNC for the 1080p,because this patch don't support BT1120 1080p.I use the mxc_lcdif.c for my driver, is right? 3.if I use the mxc_lcdif.c for my driver, dose it support YUYV16? Or just support RGB? 4.Please help me to answer this question is"IPU DI LCD HDMI LVDS". please,thanks ! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Is there any plan to port to u-boot to support splash screen? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP hi,Qiang, There is two question for you,my env is as follow: platform: imx6q linux     : linux3.0.35 1.I want to use ipu1 for lvds in split mode(1080p) and use ipu2's DI0 for HDMI,and use ipu2's DI1 for BT656. Does the imx6q suport it? 2. what's the relation between mxcfb0/maxcfb1/mxcfb2(dev=mxcfb0/mxcfb1/mxcfb2 in bootarg) and ipu1/ipu2? Best Regards. wangzg Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hello Qiang, May we know more detail about "default LCD interface driver"? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Thank you for your reply. Let me clarify my understanding. >so for 720P output, please use VSYNC/HSYNC output mode. Is this meaning the default RGB data output with clock, HSYNC, VSYNC (not BT.656 and BT.1120)? Best Regards, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Keita, IPU microcode for progressive mode hasn't been implemented in this patch, so for 720P output, please use VSYNC/HSYNC output mode. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Is it possible to output the below dual display (BT.656 and BT.1120 simultaneously)? - IPU2 DI0 --> BT.656  w/1280 x 720p@30fps - IPU1 DI1 --> BT.1120  w/1280 x 720p@60fps BR, Keita Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I'm finding the i.MX6Q code to capture the BT656 progressive mode 720P from Camera Input. I found your patch, but I knew the patch was just for the interlaced mode not for progressive mode and just for video output. Do you have any update for progressive mode of IPU CSI? Best Regards, Eric. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP good Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang Li      I use the BSP of LTIB to develop our project.The kernel release is  L3.0.35_4.1.0.But it dose not have the driver of BT1120.Does the patch of L3.0.35_4.1.0_GA_bt656_output_patch can use for LTIB. Thank you. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang_FSL, There is an issue reported here Distorted Video i.MX6 gStreamer after this patchset is applied. The issue is that, if the movie being played has exactly the same resolution from the display, the playback is corrupted. I was not able to reproduce the same issue when using the 3.10.17-ga release. So it seems that this is caused by some patch from this patchset. Can you, please, help me on this? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Two limitations for the patch: 1. The android can only support RGB frame buffer, so "fbpix=UYVY16" can't be used in Android. 2. For single IPU system, only DP channel can support CSC from RGB frame buffer to YUV BT656 interface, so in the default patch, the BT656 was designed as second display, when frame buffer driver initializing, DC channel will be assigned to fb0, and DP channel will be assigned to fb1. So if the customer used BT656 as fb0, they need recover the modification in function mxcfb_probe(), and use "fbpix=BGR32" for BT656 output. if (((mxcfbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT656) || (mxcfbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT1120)) && (mxcfbi->ipu_id == 0) && cpu_is_mx6dl()) {   /* first user uses DC */ Change to if (0) {   /* first user uses DC */ Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Is it okay to modify drivers/video/mxc/mxc_ipuv3_fb.c as below for i.MX6 Solo? Original if (((mxcfbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT656) || (mxcfbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT1120)) && (mxcfbi->ipu_id == 0) && cpu_is_mx6dl()) Modified if (((mxcfbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT656) || (mxcfbi->ipu_di_pix_fmt == IPU_PIX_FMT_BT1120)) && (mxcfbi->ipu_id == 0) && !(cpu_is_mx6dl())) Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Customer found the screen will turn green if run on i.MX6 Solo with below kernel parameter. Is there anything we need to check? bootargs=console=ttymxc3,115200 init=/init nosmp no_console_suspend video=mxcfb0:dev=bt656,BT656-NTSC,if=BT656,fbpix=UYVY16 video=mxcfb1:off video=mxcfb2:off gpumem=96M fbmem=10M vmalloc=400M androidboot.console=ttymxc3 androidboot.hardware=freescale Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Is there any patch available for supporting 1080p  output from MX6Q LCD port? Or do you know any in-progress work about it? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP No, only interlaced mode was supported, for progressive mode, you can use the default LCD interface driver with VSYNC and HSYNC. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Does it support 480P? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Thank you very much. I'll try MXCFB_SET_FBFMT Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP After applied the patch to Linux BSP, the frame buffer can support YUV format, but if application only set bpp 16 to framebuffer driver, there will be problem, the driver can't know it is RGB565 or UYVY16, both of them are 16 bpp. In this case, you should use ioctl "MXCFB_SET_FBFMT" to set the framebuffer format. By the way, if you are using iMX6Q which has two IPUs, then you don't need support the YUV format frame buffer, because you can assgn the second IPU's DP channel to BT656/BT1120 display, it can support RGB frame buffer to YUV BT656/BT1120 display converting. In this case, you can un-mask the followed line in mxc_ipuv3_fb.c, function mxcfb_set_par(), then fbset will work as normal: // mxc_fbi->fb_pix_fmt = bpp_to_pixfmt(fbi->var.bits_per_pixel);  // If the OS(such as Android) can only support RGB framebuffer, un-mask this line. The limitation only happens on iMX6S/6DL which has only one IPU, and you need support dual display, in this case, if BT656/BT1120 was assigned as second display, then IPU DC channel will be assigned to it, for this IPU DC channel, it can't support RGB frame buffer to YUV BT656/BT1120 converting, so the frame buffer must be YUV format. Then the fbset will not work. It should be replaced with MXCFB_SET_FBFMT. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Li    My English is not good enough to explain the question I want to ask。    I guess you are Chinese from your name. I'll use Chinese to explain the question.    If you don't know Chinese. I'll try my best to explain it in English.    现状:      正常在使用过程中,如果想更改fb0的格式,可以直接使用fbset -g 1024 768 1024 768 32的命令来完成。      我做了两套环境,A.使用patch之前,B.使用patch之后。      在这两个环境中,我做这些操作,启动实机当前fb0为16位,启动某UI程序,关闭UI程序,fbset更改为32位,再次启动UI程序。      A环境中,通过fbset更改fb0格式前后,启动的UI程序,显示都正常。      B环境中,通过fbset更改fb0格式前,显示正常,更改后,显示不正常。将更改后的fb0的数据通过cat语句dump到文件中,           在PC上查看,显示为正常的32位数据,实机画面显示效果为宽度拉伸了2倍的效果。      如果通过uboot启动参数中,bpp=32来设置fb0,启动后32位显示正常,但是fbset更改16位以后,16位显示不正常。      总结的问题为,无法在实机启动以后,去更改fb0格式。    分析:      查看了一部分patch的代码,发现启动有对实机启动以后,更改fb格式的代码。如果uboot参数中,没有定义一些变量,那么无法更改fb格式。      但是具体更改哪些变量,我不太清楚。     问题:      1 这个现象在你的环境中是否存在?      2 如果想在实机启动后更改fb格式,如何进行?      3 如果无法在实机启动后更改fb格式,是否为bug,如何解决?    多谢Li Qiang。 Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Li Thanks for your hearful answer. 以上です、どうも宜しくお願い致します。 Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP The internal SYNC and external SYNC are just the name, if we don't ouput these signals from IPU DI pins, they are just internal signal, if we enabled output from IPU DI PINs for them, they will be external signal too. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Li Sorry for disturbing you again. As the question just like I took above. I can see thes two comments 1, /* COUNTER_2: HSYNC for each line */ 2, /* COUNTER_3: internal VSYNC for each frame */ My apologies, I am a newer about BT.656 and IPU. Could you please tell me, HSYNC/VSYNC which set by function ipu_init_sync_panel(). are internal SYNC or External SYNC? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP The patch was verified on iMX6S board too, the use case without external HSYNC/VSYNC is the only workable case for this patch, external VSYNC and HSYNC mode hasn't been fine tuned. I think you should check your hardware for which data pins are used for the BT656 interface, and add the IOMUX setting for these pins. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Li Thanks for your such useful patch to the iMX6 about BT656 functions. But here I have a problem about the patch into iMX6S customer board with AK8817 encoder chip. 1, Using no external HSYNC/VSYNC, just with BT656 itself . iMX6S can not send correct BT656 signal to AK8817 source like bellow //----------------------------------------------------------------------------------- /driver/video/mxc/mxc_bt656if.c static struct fb_videomode bt656if_modedb[] = {     {      /* NTSC Interlaced output */      "BT656-NTSC", 60, 720, 480, 37037,      19, 3,      20, 3,      276, 1,      FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,      FB_VMODE_INTERLACED,      FB_MODE_IS_DETAILED,},     ......     ...... }; //------------------------------------------------------------------------------------ /drivers/mxc/ipu3/ipu_disp.c /* COUNTER_2: HSYNC for each line */ /* COUNTER_2: HSYNC for each line */ _ipu_di_sync_config(ipu,         disp,         /* display */         DI_BT656_SYNC_HSYNC,         /* counter */         h_total - 1,     /* run count */         DI_SYNC_CLK,    /* run_resolution */         0,         /* offset */         DI_SYNC_NONE,     /* offset resolution */         0,         /* repeat count */         DI_SYNC_NONE,     /* CNT_CLR_SEL */         0,         /* CNT_POLARITY_GEN_EN */         DI_SYNC_NONE,     /* CNT_POLARITY_CLR_SEL */         DI_SYNC_NONE,     /* CNT_POLARITY_TRIGGER_SEL */         0,         /* COUNT UP */         2*div        /* COUNT DOWN */         ); /* COUNTER_3: internal VSYNC for each frame */ _ipu_di_sync_config(ipu,         disp,         /* display */         DI_BT656_SYNC_IVSYNC,         /* counter */         v_total - 1,     /* run count */         DI_BT656_SYNC_HSYNC,    /* run_resolution */         0,             /* offset */         DI_SYNC_NONE,     /* offset resolution */         0,         /* repeat count */         DI_SYNC_NONE,     /* CNT_CLR_SEL */         0,         /* CNT_POLARITY_GEN_EN */         DI_SYNC_NONE,     /* CNT_POLARITY_CLR_SEL */         DI_SYNC_NONE,     /* CNT_POLARITY_TRIGGER_SEL */         0,         /* COUNT UP */        0        /* COUNT DOWN */         ); 2, Using external HSYNC/VSYNC, just with BT656 itself . iMX6S can send correct BT656 signal to AK8817 //----------------------------------------------------------------------------------- /driver/video/mxc/mxc_bt656if.c static struct fb_videomode bt656if_modedb[] = {     {      /* NTSC Interlaced output */      "BT656-NTSC", 60, 720, 480, 37037,      19, 3,      20, 3,      276, 1,      0,      FB_VMODE_INTERLACED,      FB_MODE_IS_DETAILED,},     ......     ...... }; //------------------------------------------------------------------------------------ /drivers/mxc/ipu3/ipu_disp.c /* COUNTER_2: HSYNC for each line */ /* COUNTER_2: HSYNC for each line */ _ipu_di_sync_config(ipu,         disp,         /* display */         DI_BT656_SYNC_HSYNC,         /* counter */         h_total - 1,     /* run count */         DI_SYNC_CLK,    /* run_resolution */         0,         /* offset */         DI_SYNC_NONE,     /* offset resolution */         0,         /* repeat count */         DI_SYNC_NONE,     /* CNT_CLR_SEL */         0,         /* CNT_POLARITY_GEN_EN */         DI_SYNC_NONE,     /* CNT_POLARITY_CLR_SEL */         DI_SYNC_NONE,     /* CNT_POLARITY_TRIGGER_SEL */         0,         /* COUNT UP */         20*div        /* COUNT DOWN */         ); /* COUNTER_3: internal VSYNC for each frame */ _ipu_di_sync_config(ipu,         disp,         /* display */         DI_BT656_SYNC_IVSYNC,         /* counter */         v_total - 1,     /* run count */         DI_BT656_SYNC_HSYNC,    /* run_resolution */         0,             /* offset */         DI_SYNC_NONE,     /* offset resolution */         0,         /* repeat count */         DI_SYNC_NONE,     /* CNT_CLR_SEL */         0,         /* CNT_POLARITY_GEN_EN */         DI_SYNC_NONE,     /* CNT_POLARITY_CLR_SEL */         DI_SYNC_NONE,     /* CNT_POLARITY_TRIGGER_SEL */         0,         /* COUNT UP */        2*div        /* COUNT DOWN */         ); Could you please tell me, how to make correct BT656 signals from iMX6 to AK8817 without external HSYNC/VSYNC ? When use patch on iMX6 Sabre board, there is no such problem. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I've been using this patch for some time with 3.0.35 and am now updating to the 3.10.17_1.0.0_beta kernel.  Are you planning on creating a patch for that kernel?  Why is this support not part of the Freescale BSP? Thanks, Tim Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP PLL5 clock has been changed, clk_set_rate(&pll5_video_main_clk, 297000000);.  I get the same results.  I also tried to run the clock using PLL3 at 27MHz, just to see what would happen.  This also gave me 50MHz.  Is it possible that something is overriding the clock definitions?   Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Josh, you can set pll5 to 297MHz for 74.25MHz pixel clock. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I am setting clk_set_parent(&ipu1_di_clk[0], &pll5_video_main_clk);  In the line directly above this one I am setting the clock rate as clk_set_rate(&pll5_video_main_clk, 650000000); (line 5458).  Is this the correct value to set PLL5 in order to achieve a 74.25MHz clock?  I have also uploaded my kernel dmesg log to pastebin.com:  imx6 dmesg for BT.1120 - Pastebin.com.  I do not see anything directly defining any video settings.  Could you tell me what I should be looking for?  Lastly, should I move this question to a new thread?  It is starting to become long.  Thank you. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP The google drive can't be accessed from China, I had tried your video mode on my SabreSD board, it can get the 74.25MHz pixel clock correctly. Of cource, ipu1_di0 clock should be sourced from PLL5. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP By kernel boot log do you mean dmesg?  This is a link to dmesg when BT1120-1080I60 is set:  https://drive.google.com/file/d/0B1-NpS0YmbqNZEJJeDFvNFNwTGs/edit?usp=sharing I am also attaching a file named /var/log/boot:  https://drive.google.com/file/d/0B1-NpS0YmbqNZXJRbW90X054c28/edit?usp=sharing Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Can you attach your kernel boot log? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP With BT1120-1080I60 set using the recommended u-boot parameters, the output of /sys/class/graphics/fb0/mode is D:1920x1080i-30.  I believe this is the correct setting, but the clock is still running at 50MHz.  For BT1120-1080I50 I get D:1920x1080i-25.  I am running this on a SabreLite and a Wandboard quad; I do not have a SabreSD board.  I made the necessary additions to the board-xxx.c and defconfig files.  Can this patch be applied to ALL imx6 boards, or is it specific to the SabreSD?   Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I think you should check if the correct mode had been used or not? $ cat  /sys/class/graphics/fb0/mode Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Thanks for the response.  I copied the 1080i modes to the bottom of struct fb_videomode bt656if_modedb[] in mxc_bt656if.c and modified the u-boot parameters, but I am not getting the correct clock.  Before I load the kernel (still in uboot) the pixel clock is good at 74.25MHz.  After I load the kernel,the pixel clock is stuck at 50MHz.  Also I do not see anything on the HSYNC and VSYNC pins.  Is that supposed to happen or is that a sign something else is wrong?  In arch\arm\mach-mx6\clock.c I have clk_set_parent(&ipu1_di_clk[0], &pll5_video_main_clk);.  Is their anything else I have to set?  I back-ported the patch to run on kernel 3.0.35_4.0.0.  Are you aware of any conflicts that might occur with this? Thank you, Josh Kurland Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP If you just need iMX6 generate BT1120 signal, you can just add the 1080i video mode in file mxc_bt656if.c. The uboot parameters can be "video=mxcfb0:dev=bt656,BT1120-1080I60,if=BT1120,fbpix=UYVY16" or "video=mxcfb0:dev=bt656,BT1120-1080I60,if=BT1120,fbpix=RGB565". There is no 1080P support for BT1120 mode yet, but you can use VSYNC/HSYNC mode to support 1080P. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I am also interested in BT.1120 1080 capability.  Could you explain how to include this support into the kernel a little further?  I am using Yocto with kernel 3.0.35_4.0.0.  I have already changed the clock source back to 75MHz, but I do not know where to add the BT1120 parameters.  Should it be placed in drivers/video/mxc/mxc_bt656if.c?  I imagine the boot parameters would look something like mentioned above (video=mxcfb0:dev=bt656,BT1120-PAL-1080i,if=BT1120,fbpix=UYVY16).  Is this correct?  Lastly, is their any support for 1080p?  Thank you, Josh Kurland Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Checked with BT1120-8 protocol, I think you can try the followed parameter for 1080I60 and 1080I50: {   /* 1080I60 Interlaced output */   "BT1120-1080I60", 30, 1920, 1080, 13468,   20, 3,   20, 2,   280, 1,   FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,   FB_VMODE_INTERLACED,   FB_MODE_IS_DETAILED,}, {   /* 1080I50 Interlaced output */   "BT1120-1080I50", 25, 1920, 1080, 13468,   20, 3,   20, 2,   720, 1,   FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,   FB_VMODE_INTERLACED,   FB_MODE_IS_DETAILED,}, Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP HI li :          i  change the clock source on clock.c . and use :setenv bootargs console=ttymxc0,115200 init=/init rw video=mxcfb0:dev=bt656,BT1120-PAL-1080i,if=BT1120,fbpix=RGB565 . but my screen ids no signal.  you have said the margin data:         {          /* PAL Interlaced output */          "BT1120-PAL-1080i", 25, 1920,1080, 13468,          148, 484,          36, 4,          88, 5,          FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,          FB_VMODE_INTERLACED,          FB_MODE_IS_DETAILED,}, i guess is this parameter is error.  The patch code is no 1080i format, thoes code about 1080i  may be wrong,can your provide a 1080i parameter for me。 Thanks kai Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP In clock.c, the current clock setting is for 27MHz NTSC and PAL mode, for 1080i, you need the 74.25MHz clock, so you should change the clock source in clock.c. From clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  //for CVBS 27MHz clock To clk_set_parent(&ipu1_di_clk[0], &pll5_video_main_clk); By the way, audio data is not transfered on BT1120 interface, so the audio issue should be the TV chip's issue, non business with BT1120 driver. No matter what, you should not change the margin data in the video mode, those data is for BT656/BT1120 protocol. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi li :           Thanks for your reply, that  is a previous questions:i need sabresd board output parallel yuv4:2:2  display, thanks for your help ,720P format  display is OK . but you konw the interlaced is not support, i communitcte with the TV encoder fae,the chip is support the bt1120 mode,i used your patch ,the 576i format is display ok(but not audio, chip is not support well on bt1120 mode). this TV chip fae let me test 1080i format ,may be have audio,so i added the above code ,but the 1080i is not well,the screen is black. my screen have nothing and then ask for your help. i guess  the parameter is error.           and i always think the left_margin right_margin etc  through SAV and EAV in display data   is not well. and maybe because of this protocol data  the audio can not  insert the display data( on this chip the audio is insert  on display data gaps).  But anything is to project.           so can you support the parameter about 1080i, mxc_bt656if.c is only have 576i parameter. Beat Regard kai Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi sun, that driver can only support BT1120 mode 1080i, and the left_margin, right_margin, up_margin, down_margin in video mode is protocol data, they can't be changed. You also need make sure your TV encoder chip can support BT1120 input. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear li:              how to achieve 1080i? i add some code on mxc_bt656.c .but my screen not display. add some code like it: {   /* PAL Interlaced output */   "BT1120-PAL-1080i", 25, 1920,1080, 13468,   148, 484,   36, 4,   88, 5,   FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,   FB_VMODE_INTERLACED,   FB_MODE_IS_DETAILED,}, does some parameter is error? Beat Regards kai Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP The HSYNC and VSYNC pins are already enabled by the patch, they will output from DI0_PIN2 and DI0_PIN4. Since BT656 mode doesn't need VSYNC and HSYNC, these signals haven't been checked, just reserved. The followed DI config code are for them:     /* COUNTER_2: HSYNC for each line */     _ipu_di_sync_config(ipu,       disp,   /* display */       DI_BT656_SYNC_HSYNC,   /* counter */       h_total - 1,  /* run count */       DI_SYNC_CLK, /* run_resolution */       0,   /* offset */       DI_SYNC_NONE,  /* offset resolution */       0,   /* repeat count */       DI_SYNC_NONE,  /* CNT_CLR_SEL */       0,   /* CNT_POLARITY_GEN_EN */       DI_SYNC_NONE,  /* CNT_POLARITY_CLR_SEL */       DI_SYNC_NONE,  /* CNT_POLARITY_TRIGGER_SEL */       0,   /* COUNT UP */       2*div  /* COUNT DOWN */       );     /* COUNTER_4: VSYNC for field1 only */     _ipu_di_sync_config(ipu,       disp,   /* display */       DI_BT656_SYNC_VSYNC,   /* counter */       0,  /* run count */       DI_BT656_SYNC_HSYNC, /* run_resolution */       bt656_v_start_width_field0 + height / 2 + bt656_v_end_width_field0,  /*  offset */       DI_BT656_SYNC_HSYNC,  /* offset resolution */       1,   /* repeat count */       DI_BT656_SYNC_IVSYNC,  /* CNT_CLR_SEL */       0,   /* CNT_POLARITY_GEN_EN */       DI_SYNC_NONE,  /* CNT_POLARITY_CLR_SEL */       DI_SYNC_NONE,  /* CNT_POLARITY_TRIGGER_SEL */       0,   /* COUNT UP */       2*div  /* COUNT DOWN */       ); Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear li:            I add your patch,and use  uboot parameters : video=mxcfb0:dev=bt656,BT1120-PAL,if=UYVY16,fbpix=RGB565, but the vsync is error.it is not rule. and other question is how to change this pin:          IPU1_DI0_PIN2 connected to adv7391 HSYNC pin. (option)          IPU1_DI0_PIN4 connected to adv7391 VSYNC pin. (option) Thanks kai Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I create a thread to discuss my question, could you please leave your advice there, thanks. https://community.freescale.com/message/360506#360506 Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For Android, the frame buffer must be RGB format, so for BY656 output, before sending the frame buffer data to DI port, the IPU DP will be used to convert the RGB frame buffer to YUV422 format. If you use LCD as main display, the "0003-Enhance-dual-display-support-for-BT656-output.patch" will assign IPU DC for LCD, which has no hardware CSC and assign IPU DP to adv7391 which can support hardware CSC. From my test, video playback has no issue in Android on the two displays. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi  Qiang: i'm using imx6 dual lite ,android 4.2.2 1.1.0 BSP.and using this patch this patch fix rear monitor cvbs output to TV_BOX 's SYNC error, and it realy woks. but during blank opertion, your patch do retry by checking INT_STATE register, till there's no sync error. this may cost a lot of time , and during this period, front monitor(main lcd display) is ALSO be freezed. it's terrible. T_T so, if any suggest or new patch, please notice us, thks. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang,      Since ADV7391 only support YUV 4:2:2 input, no matter what kind of frame buffer data format, the BT656 interface output should be YUV 4:2:2 with EAV/SAV embedded, I believe BT656 driver is implemented to do so.      So, if I feel like to output Android desktop to ADV7391, what kind of data format will be filled in frame buffer? RGB,YUV or I cat assign the data format? Do I have to convert the data in frame buffer to fit YUV 4:2:2 output to ADV7391 by myself?      Furthermore, you said "I can try to paly video on it"! If I set LCD panel as main display, how to play video on ADV7391? I can't find gstream built in Android kernel, may I copy an Ubuntu version into Android kernel or any APK can achieve this? Thanks for your kindly help. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Oliver, If you had set "fbpix=UYVY16", that means the frame buffer is in YUV format, you should draw it in YUV format. You can try to play video on it, the video playback is OK to support YUV frame buffer. If you draw the YUV frame buffer with RGB data, there will be color issue. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, After change clock setting as you mentioned, I can see output from ADV7391 but the display color is grotesque. Since ADV7391 uses DISP1_DAT0~7 and these pins are also shared for boot setting, there is a 10k ohm resistor pull to ground. Would this affects ADV7391 data input accurate? Any suggestion for the hardware connection? Really thanks for your great support. Best regards, Oliver Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP There is no confirmed schedule yet. Address: 0x02400000 + 0x002000000 + 0x00180000: it is the IPU DC Template Memory, you can reference to reference manual "37.4.7 DC - Display Control" Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Dear Qiang Lin, When will you be able to provide it? If you need a long time to provide the patch for progressive output, we have to create it by ourselves because our schedule is very tight. In the case, we need a additional information about the register on the following address, because reference manual (IMX6DQRM Rev.1) doesn't provide the information about it even though the released patch access the address. Address: 0x02400000+0x00200000+0x00180000 Could you let us know the register information? Regards, Satoshi Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Can you check if the adv7391 IPU framebuffer driver is ready with the followed commands: # cat /sys/class/graphics/fb0/fsl_disp_dev_property By the way, since you are using BT656 interface on DI1 port, the arch\arm\mach-mx6\clock.c should also be adjusted: clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  //for CVBS 27MHz clock clk_set_parent(&ipu1_di_clk[1], &pll5_video_main_clk); should be changed to: clk_set_parent(&ipu1_di_clk[0], &pll5_video_main_clk); clk_set_parent(&ipu1_di_clk[1], &pll3_pfd_540M);  //for CVBS 27MHz clock Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, After apply 3 patches in "r13.4.1_bt656_output_patch_2013-09-04.zip", I still can't make adv7391 work properly on our custom board. We use LCD as primary display which connect to IPU1 DI0 (DISP0) and ADV7391 connect to IPU1 DI1. I can't find DISP1's pads definition from user manual; refer to IOMUX tool and iomux-mx6dl.h we connect ADV7391 to the pads as below. I make ADV7391 as main display to make sure it work properly, boot environment set "video=mxcfb0:dev=adv739x,BT656-NTSC,if=BT656,fbpix=UYVY16"; however no output from ADV7391 and lots of message  "mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq" posted on console. I can't measure clock output on IPU1_DI1_DISP_CLK, only 3.3V output. ADV7391 setting: static struct fsl_mxc_lcd_platform_data adv739x_data = {   .ipu_id = 0,   .disp_id = 1,   .default_ifmt = IPU_PIX_FMT_BT656, }; ADV7391 IOMUX: /* ipu1 di1 :: CVBS out */ MX6DL_PAD_GPIO_18__GPIO_7_13, /* CVBS_OUT_RST */ MX6DL_PAD_EIM_A16__IPU1_DI1_DISP_CLK, //MX6DL_PAD_EIM_D29__IPU1_DI1_PIN15, //MX6DL_PAD_EIM_EB3__IPU1_DI1_PIN3, MX6DL_PAD_EIM_DA9__IPU1_DISP1_DAT_0, MX6DL_PAD_EIM_DA8__IPU1_DISP1_DAT_1, MX6DL_PAD_EIM_DA7__IPU1_DISP1_DAT_2, MX6DL_PAD_EIM_DA6__IPU1_DISP1_DAT_3, MX6DL_PAD_EIM_DA5__IPU1_DISP1_DAT_4, MX6DL_PAD_EIM_DA4__IPU1_DISP1_DAT_5, MX6DL_PAD_EIM_DA3__IPU1_DISP1_DAT_6, MX6DL_PAD_EIM_DA2__IPU1_DISP1_DAT_7, Our target is to make LCD as primary display and ADV7391 as secondary output. Do you have any suggestion? Thanks for your kindly help. Oliver Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP For BT656/BT1120 progressive mode, a new IPU microcode was needed, it is not ready yet. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, Do you have a similar patch for MCIMX6Q-SDP with L3.0.35_4.0.0_130424_source BSP to output "progressive" BT656/1120? Regards, Satoshi Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP In "https://community.freescale.com/thread/295157", there is some kernel code modification in V4L2 capture driver to support BT1120 capture, although it is for iMX53 BSP, the same modification can also be applied on iMX6 BSP. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Is there a similar patch to support BT1120 for CAPTURE on imx6s? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP The old patch had used pll5 as clock source for both CVBS and other display (such as lcd and hdmi), so when use dual display mode for lcd+cvbs and hdmi+cvbs, then when the second display was enabled, the first display will be impacted, because pll5 frequency will be changed by second display. We need select different clock source for dual display. The new patch had added such code modification in arch\arm\mach-mx6\clock.c. LVDS + CVBS output had no such isssue, because lvds clock source is not pll5. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, How about the status of dual display with BT656 output on iMX6 Solo for Android build r13.4.1? I notice you have updated the package of Linux build on 2013-08-09, will you update Android build as well or I have to dig the patch and revise r13.4.1 accordingly by myself? BTW, we use LCD device as primary display and ADV7391 be second, after I apply r13.4.1 patch, LCD display becomes crushing, is it caused by dual display issue you mentioned on 2013-04-15? ADV7391 IOMUX setting: MX6DL_PAD_EIM_A16__IPU1_DI1_DISP_CLK, MX6DL_PAD_EIM_D29__IPU1_DI1_PIN15, MX6DL_PAD_EIM_EB3__IPU1_DI1_PIN3, MX6DL_PAD_EIM_DA9__IPU1_DISP1_DAT_0, MX6DL_PAD_EIM_DA8__IPU1_DISP1_DAT_1, MX6DL_PAD_EIM_DA7__IPU1_DISP1_DAT_2, MX6DL_PAD_EIM_DA6__IPU1_DISP1_DAT_3, MX6DL_PAD_EIM_DA5__IPU1_DISP1_DAT_4, MX6DL_PAD_EIM_DA4__IPU1_DISP1_DAT_5, MX6DL_PAD_EIM_DA3__IPU1_DISP1_DAT_6, MX6DL_PAD_EIM_DA2__IPU1_DISP1_DAT_7, Thanks, Oliver Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, We are working on an automotive project using the iMX.6 DL & iMX.6 Solo SOC with the Android 4.2 BSP. Is it possible to use ldb as the primary display and bt656 as a second one? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I'm not using Freescale Android R13.4.1 BSP but Freescale L3.0.35_1.1.0_GA_iMX6DQ BSP.... Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP If you are using iMX6Q which had two IPU, the BT656 is OK for dual display, you can reference to the OTT TVBox reference design, it is OK for HDMI + BT656 on IMX6Q. https://community.freescale.com/docs/DOC-94561 For iMX6S/DL, there is still some issue to enable the dual display with BT656 support, this update will be released at the end of July. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP You mean that this patch still not working? I'm using this on a sabrelite board with iMX6Quad...I forgot to tell you.... Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I planned to release the updated code for dual display support on BT656 at the end of July. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I'm using your the patch and the output to adv7391 is good. Now I want to use both HDMI and BT656 to adv7391 and I did the things you told in Update but I can see always BT656 not HDMI. The uboot paramaters remain the same? I put also video=mxcfb2:dev=hdmi,1920x1080M@50,if=RGB24 after your uboot params but I can see working only the ADV. Any suggestion?? Thank you Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP I planned to make dual display with BT656 work on iMX6S/DL before the end of June. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang, I want the patch of dual display mode with BT656 ouput support. When do you plan to release updated patch? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Yes, it can also work on iMX6S and iMX6DL. But there is issue for dual display mode with BT656 ouput support, I planed to give an update in this month to fix it. Currently single BT656/BT1120 output on iMX6S/DL is OK. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP Hi Qiang,      Could I use this patch for iMX6dl board ? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨,Qiang Thank you for your patient reply, now we understand how to implement it, thank you again! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Qiang_FSL‌ Hello. We use the L3.14.28 kernel and i.mx6q CPU. After manually applying the above L3.14.52_1.1.0_GA_bt656_output_patch_2016-06-27, if the clock configuration in arch/arm/mach-imx/clk-imx6q.c remains the original imx_clk_set_parent(clk[IMX6QDL_CLK_IPU1_DI0_PRE_SEL],clk[IMX6QDL_CLK_PLL5_VIDEO_DIV]); Then the BT1120 data can be output normally, the format is 1280*720@25, the clock frequency is 74.25MHz, but it cannot be dual-displayed with HDMI at this time; If the above configuration is changed to the patch mx_clk_set_parent(clk[IMX6QDL_CLK_IPU1_DI0_PRE_SEL], clk[IMX6QDL_CLK_PLL3_PFD1_540M]); Then BT1120 cannot output. Unfortunately, our current application must use dual display. If the clock source of IPU1_DI0 is selected as PLL3_PFD1_540M, is there any other configuration required to make BT1120 output correctly? Or if this clock source cannot achieve this frequency, is there any other way? Looking forward to your reply, thank you. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> There is too much Blank data in each row, which exceeds the maximum value supported by the register. You need to find a way to reduce the Blank data, such as lowering the pixel clock frequency. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> @Qiang Li - Mpu Se  Hello, our board uses the imx6q automotive-grade chip, which is used for security monitoring. The hardware of our board is modified by referring to the Inbet Sabrelite development board. The kernel version uses linux-3.0.35 version, and the board has two interfaces: CVBS output and HDMI output. The CVBS output uses the adv7391 chip. The temperature range of the ADV7391 chip is -40℃~85℃. I downloaded the L3.0.35_4.1.0_GA_bt656_output_patch_2017-03-10.zip version you released, followed the instructions in the patch, and applied the patch successfully. After the patch was applied, I modified the board-mx6q_sabrelite.c file and added support for adv7391 Support for IIC devices. Also initialize the pins. The pin initialization code is as follows: /* New code for DISPLAY RGB */ /*New Code for Board  The original development board Sabrelite interface uses MX6_PAD_DISP0_DAT0~MX6_PAD_DISP0_DAT23 24 bits The new board DIS0 is connected to ADV7391BCPZ and uses 8 -bit bus */ MX6Q_PAD_DI0_DISP_CLK__IPU1_DI0_DISP_CLK, /*DISP0_CLK*/ //MX6Q_PAD_DI0_PIN15__IPU1_DI0_PIN15,                /* DE */ MX6Q_PAD_DI0_PIN2__IPU1_DI0_PIN2, /* DISP0_HSYNC */ MX6Q_PAD_DI0_PIN3__IPU1_DI0_PIN3, /* DISP0_VSYNC */ MX6Q_PAD_DI0_PIN4__IPU1_DI0_PIN4, MX6Q_PAD_DI0_PIN4__GPIO_4_20,                     /* CVBS_nRST */ MX6Q_PAD_DISP0_DAT0__IPU1_DISP0_DAT_0, MX6Q_PAD_DISP0_DAT1__IPU1_DISP0_DAT_1, MX6Q_PAD_DISP0_DAT2__IPU1_DISP0_DAT_2, MX6Q_PAD_DISP0_DAT3__IPU1_DISP0_DAT_3, MX6Q_PAD_DISP0_DAT4__IPU1_DISP0_DAT_4, MX6Q_PAD_DISP0_DAT5__IPU1_DISP0_DAT_5, MX6Q_PAD_DISP0_DAT6__IPU1_DISP0_DAT_6, MX6Q_PAD_DISP0_DAT7__IPU1_DISP0_DAT_7, Modify line 62 of file linux3.0.35/drivers/mxc/ipu3/ipu_disp.c Change macro definition 23 to 7   #define BT656_IF_DI_MSB 7// 23 /* For 8 bits BT656: 23 for DISP_DAT23 ~ DISP_DAT16; 7 for DISP_DAT7 ~ DISP_DAT0 */ /* For 16 bits BT1120: 23 for DISP_DAT23 ~ DISP_DAT8; 15 for DISP_DAT15 ~ DISP_DAT0 */ Here is my personal patch record: linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0001-Support-BT656-and-BT1120-output-for-iMX6-ipuv3.patch patching file arch/arm/configs/imx6_defconfig patching file arch/arm/mach-mx6/board-mx6q_sabresd.c patching file arch/arm/mach-mx6/devices-imx6q.h patching file arch/arm/plat-mxc/include/mach/ipu-v3.h patching file drivers/media/video/mxc/output/mxc_vout.c patching file drivers/mxc/ipu3/ipu_common.c patching file drivers/mxc/ipu3/ipu_device.c patching file drivers/mxc/ipu3/ipu_disp.c patching file drivers/mxc/ipu3/ipu_regs.h patching file drivers/video/mxc/Kconfig patching file drivers/video/mxc/Makefile patching file drivers/video/mxc/mxc_bt656if.c patching file drivers/video/mxc/mxc_ipuv3_fb.c patching file include/linux/ipu.h patching file include/linux/mxcfb.h linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0002-Support-adv739x-TV-encoder-for-BT656-output.patch patching file arch/arm/mach-mx6/board-mx6q_sabresd.c patching file drivers/video/mxc/Kconfig patching file drivers/video/mxc/Makefile patching file drivers/video/mxc/mxcfb_adv739x.c linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0003-Enhance-dual-display-support-for-BT656-output.patch patching file arch/arm/mach-mx6/board-mx6q_sabresd.c patching file arch/arm/mach-mx6/clock.c patching file arch/arm/plat-mxc/include/mach/ipu-v3.h patching file drivers/media/video/mxc/capture/ipu_bg_overlay_sdc.c patching file drivers/media/video/mxc/capture/ipu_csi_enc.c patching file drivers/media/video/mxc/capture/ipu_fg_overlay_sdc.c patching file drivers/media/video/mxc/capture/ipu_prp_enc.c patching file drivers/media/video/mxc/capture/ipu_prp_vf_sdc.c patching file drivers/media/video/mxc/capture/ipu_prp_vf_sdc_bg.c patching file drivers/media/video/mxc/capture/ipu_still.c patching file drivers/mxc/ipu3/ipu_common.c patching file drivers/mxc/ipu3/ipu_device.c patching file drivers/mxc/ipu3/ipu_disp.c patching file drivers/mxc/ipu3/ipu_prv.h patching file drivers/video/mxc/mxc_ipuv3_fb.c linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0004-BT656-Display-updated-for-BT1120-1080i-support.patch patching file drivers/mxc/ipu3/ipu_disp.c patching file drivers/video/mxc/mxc_bt656if.c linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0005-Update-IPU-microcode-to-align-with-BT656.4-specifica.patch patching file drivers/mxc/ipu3/ipu_disp.c patching file drivers/video/mxc/mxc_bt656if.c patching file drivers/video/mxc/mxcfb_adv739x.c linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0006-Set-Y-range-16-235-U-V-range-16-240-for-BT656-displa.patch patching file drivers/mxc/ipu3/ipu_disp.c linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0007-Add-progressive-mode-support-for-BT656-and-BT1120-di.patch patching file drivers/mxc/ipu3/ipu_disp.c patching file drivers/video/mxc/mxc_bt656if.c patching file drivers/video/mxc/mxc_ipuv3_fb.c linux@ubuntu:~/workspace/mx6q/linux-3.0.35$ patch -p1 < 0008-Fixed-a-hard-coding-DC-macro-issue-for-progressive-m.patch patching file drivers/mxc/ipu3/ipu_disp.c linux@ubuntu:~/workspace/okmx6q/linux-3.0.35$   After all patches are completed and modifications are complete, the board can display video images normally and stably at room temperature, as shown below:   The board is tested at low temperature at -40℃. The image is shown below. The adv7391 driver is integrated into the kernel, which may cause the kernel to crash when it starts. If the adv7391 driver is removed, the kernel will not crash. If the environment variable parameter is changed to HDMI display, it will work normally. The following are some parameter configurations # cat /sys/class/graphics/fb0/fsl_disp_dev_property    arch\arm\mach-mx6\clock.c    配置成了 clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  //for CVBS 27MHz clock clk_set_parent(&ipu1_di_clk[1], &pll5_video_main_clk); The environment variables are configured "video=mxcfb0:dev=adv739x,BT656-PAL,if=BT656,fbpix=RGB565" The above are my parameters. 望指教!    Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> "Under the BT656 data line interface (8-bit data bus), does the current program support VSYNC/HSYNC mode for display output?" In the previous reply, suggestions on how to achieve this should have been given. EAV/SAV are output at blank time, which has no effect on HSYNC/VSYNC reception. You can actually measure the waveform to see that as long as blank does not exceed 255, it should be possible. This is the easiest to do under the current circumstances. IPU can also support non-BT656 8-bit UYVY+HSYNC/VSYNC output. The main thing is to modify the settings on the IPU side to let it output one pixel with 2 pixel clocks. However, there is no ready-made patch, you need to develop it yourself, which requires a very good understanding of the DI part of the IPU. The IPU code has nothing to do with the kernel version. The DE example just tells you that by encoding IPU DI, you can make IPU_DI_PIN output any waveform you need. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> The HSYNC and VSYNC output by the display are both pulse signals with a maximum value of 255. If you need to output a level signal, it is more complicated. You need to encode the DI logic of the IPU to make it output the level signal you need. Here is an example of DI encoding, using DI_PIN04 to output a DE signal. https://community.nxp.com/message/392943 Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Qiang_FSL ‌Thank you for your reply. My HDMI needs to use a resolution of 720 * 576. According to your description, it seems that PLL5 cannot be used as the clock for both BT1120 and HDMI. Can I use one of the following clocks as the output of IPU1_DI0 (BT1120 1280*720@25)? If so, how should I change it in clk-imx6q.c?       mmdc_ch0_axi 528MHz       pll3_usb_otg 480MHz       pll2_pfd0_352m       pll2_pfd2_396m       pll3_pfd1_540m I have tried to configure the clock source of IPU1_DI0 to pll3_pfd1_540m: mx_clk_set_parent(clk[IMX6QDL_CLK_IPU1_DI0_PRE_SEL], clk[IMX6QDL_CLK_PLL3_PFD1_540M]);, and then modify the output clock through pixclock in struct fb_videomode. I found that there will be BT1120 screen output, but the color is seriously distorted and the clock cannot be perfectly 74.25MHz . Thank you. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> You can use pll3_pfd1_540m for HDMI's 720*576 display and PLL5 for BT1120's 1280*720@25 . Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Thank you very much for your detailed reply, which has clarified many doubts for us. In short, in BT656 mode, the data stream is still in the BT656 standard format, but it can output HSYNC and VSYNC synchronization signals at the same time.   But in other posts, I saw you mentioned VSYNC/HSYNC mode, and there was the following explanation: For VSYNC/HSYNC mode, it means there no EAV/SAV data on data line, only video data are sent on data line, all timing signals are sent on VSYNC and HSYNC pins. Then I would like to know whether the current program supports VSYNC/HSYNC mode for display output under BT656 data line interface (8-bit data bus). If not, can it be patched to support it? Is this a lot of work? Because we still use pure UYVY data stream mode without EAV/SAV output.   In addition, you mentioned the output of DE signal. Could you explain it further in combination with the existing program? Is there any control of DE output in the current code? Which pin is used? The suggestion in your reply above to use different pins to output DE signal seems to be based on version 3.0.xx. Could you give an example of version 3.14.52? Finally, is the DE signal only available under the LCD interface? Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> No logs. Check IOMUX to see if it is set correctly. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Thank you very much for your reply. I will take a good look at the post this afternoon. Thank you!! Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Hi, Qiang, The following is the information printed by the kernel, using IPU2-DI0 and IPU1-DI1, which is correct. Clock source是设的pll3 寄件者: Qiang_FSL Date of delivery: March 11, 2020 11:40 Recipient: Allon Li(李新龍)(SZX) 主旨: Re: - Patch to Support BT656 and BT1120 Output For i.MX6 BSP NXP Community <> Patch to Support BT656 and BT1120 Output For i.MX6 BSP new comment by Qiang Li - Mpu Se<> View all comments on this document<> Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> From the phenomenon, the two IPUs are not separated clearly, so they will affect each other. If the PINs used on the two IPUs are different, for example, one is DATA0-7 and the other is DATA16-23, the BT656_IF_DI_MSB in ipu_disp.c should use different values for the two IPUs, but this will only affect the data, not the clock. The two BT656 clock sources can use the same one. For example, in clock.c, the two BT656 are IPU1_DI0 and IPU2_DI1:  clk_set_parent(&ipu1_di_clk[0], &pll3_pfd_540M);  /* For CVBS 27MHz clock */  clk_set_parent(&ipu1_di_clk[1], &pll5_video_main_clk);  clk_set_parent(&ipu2_di_clk[0], &pll2_pfd_352M);  clk_set_parent(&ipu2_di_clk[1], &pll3_pfd_540M);  /* For CVBS 27MHz clock */ In drver, you can print out ipu_id and ipu_di, and it will be easy to know where the problem is. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> If it is an iMX6DQ board, registered on 2 IPUs, there is no problem of DI being occupied. Re: Patch to Support BT656 and BT1120 Output For i.MX6 BSP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Take a look at the kernel startup log. If the kernel command line sets LVDS and HDMI display, it can override the device tree settings. You can also use the kernel command line to set up two BT656 displays: video=mxcfb0:dev=bt656,BT656-NTSC,if=BT656,fbpix=RGB32 video=mxcfb1:dev=bt656,BT656-NTSC,if=BT656,fbpix=RGB32
記事全体を表示
Session 1: MQX Architecture and initialization - lab guides This video presentation is the first installment of the Essentials of MQX RTOS Application Development training course. In this session, you will be introduced to the MQX architecture, learn how MQX is initialized, and understand how to schedule and prioritize tasks. This training was created by Embedded Access Inc., a Freescale sponsored training provider and proven partner. Session 1 Course Line Lab Topic Creating tasks Setting priorities Scheduling Synchronization concepts Introduction to drivers Creating the environment Creating source code Understanding results First, watch the video for Session 1: MQX Architecture and Initialization at the Freescale Website. Then, follow through with the interactive lab assignment below. SESSION 1: LAB ASSIGNMENT INTRODUCTION This lab walks you through the basics of starting a new project from scratch and then creating all of the tasks that we'll need for our application. For now the tasks will just print out a unique message but getting the environment set up and the shell of our application in place is an important first step. OBJECTIVE The objective of this lab is to download and run your first MQX application on target hardware. This objective will be accomplished by: Using the CodeWarrior New project wizard to create an MQX project Adding the stubs for all of the required tasks Modifying the task template to autostart all of the tasks New functions/ structures you will use:       Printf, _task_block, TASK_TEMPLATE_LIST ASSIGNMENT CREATING THE ENVIRONMENT Create a new MQX project. When asked about which libraries will be used you should add the shell library to your project. The code will run from flash, be sure to use "int flash debug PnE Multilink". This video has been deleted (view in My Videos) Import the BSP, PSP, and Shell for the tower K70 board and re-build these libraries. We now need to add .c files for the source code for each task. To do this we need a separate file for each task so in the source code folder you'll have HealthTask.c, DisplayTask.c, etc. At the end you'll have the new 8 files plus the main.c and main.h files created when the project was created. In CodeWarrior a new file should be added by right clicking on the source folder and selecting new > source. This will create a new file with a minimal amount of code to get you started including a function that prints a message to the default output stream and then aborts. Update the name of each function to be the function associated with this file (eg: Temp_task). If the tools you're using don't fill in a minimal amount of code when you create a new file create a simple 1 line function that prints out a message. /* * TempTask.c * Created on: Feb 6, 2014 * Author: Embedded Access Inc */ #include "main.h" /*TASK*---------------- * Task name : Temp_task * Comments : * This task prints "Hello World" *END*----------------*/ void Temp_task(uint_32_t initial_data) { printf("\n Temp: Hello World\n") } We'll need a function prototype for each of our new functions which can be added in main.h /* Example function prototype */ extern void Healt_task(uint32_t); Since we'll be using the printf () function you should include the stdint.h header file at the top of main.h. For a few reasons we will need a unique ID number for each task but of course just using a number is confusing and error prone so it's more practical to use a define with each set to a unique number. You can use a series of #define statements to do this but of course you can inadvertently assign two defines to the same number. This case can be avoided by using an enum structure and you'll see that throughout the course. Find the '#define MAIN_TASK 1' in the autogenerated code and replace it with an enum defining all 8 tasks HEALTH_TASK, DISPLAY_TASK, etc). To create the tasks you need to update the Task Template List found in main.c. The Template List will be covered in a later session of the course but essentially it is a table identifying all of the tasks that you'll have in your application and it provides MQX with some information about each task. The project generated source includes a starting task template list with a single task called "main_task." You don't need the main_task but you can use this entry as a guide for entering in the entries you need. Be sure to leave the entry of zeros in the template list to demark the end of the list. Create all 8 tasks that we'll have in our application: Health Task, Display Task, Accel Task, Temp Task, Input Task, CAN Task, UI Task, and Theft Task. All tasks should be set to priority 9, have a stack size of 1500, and be auto starting. /* EXAMPLE TASK TEMPLATE LIST ENTRY*/ {HEALT_TASK,  Healt_task,  1500,  9,  "Health_task",  MQX_AUTO_START_TASK}, Below the Template List in main.c you'll see the autogenerated code for a main_task. We don't have a task called main in our system so this can be removed. For each of our new tasks we need update the code a bit. Change the printf to 'printf("\n Function: Hello World \n");'. In your code, 'Function' will be the actual name of function in this file (e.g. Health, Display, Temp, etc). Replace the mqx_exit with the _task_block() function. Be sure to update any comments to reflect the name of this function. Also, each function should include the main.h header as this is where we'll have some defines and the function prototypes. Run the application to confirm that each task's message is printed out onto the console. Your print out souhld look like this Review the order of the print statements and explain why they came out in the order that they did. Explanation of the Result The tasks will be created and run in the order that they are listed in the Task Template List (TTL). So, the order of the print outs you see should match the order of the tasks listed in the TTL. Later in the course we'll look at what happens when tasks are at different priority levels, but for now, since all tasks are at the same priority level, they will start and run in the order that they are created in. Need more help? The full source code for this lab can be found in the 'Lab Source Code' folder here. Re: Session 1: MQX Architecture and initialization - lab guides Hello I am struggling to watch the video. The video is not running, I've copied the link and I got the following issue:  This video-svc.jivesoftware.com page can’t be found No webpage was found for the web address: https://video-svc.jivesoftware.com/videos/5bd5d2ca898ff/assets/8850941/play.mp4?player_profile=2016_1_0&auth_token=41cd81004941968141d394bebd6fc98a40296d91f1677603568e4ed316b4be21&logo_image_url=https%3A%2F%2Fcommunity.nxp.com%2Fservlet%2FJiveServlet%2FdownloadImage%2F1101-1-5287%2FFS_watermark1x1.png& HTTP ERROR 404 Is this video still working or it was removed? Thanks Angelico Corte
記事全体を表示
低功耗物联网应用传感器的使用技巧 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将详细介绍当今一些最流行的物联网传感应用,如资产跟踪、机器状态监控、活动监控、钥匙扣、智能门、智能球、吸入器、暖通空调等。这将涉及展示 NXP 的演示/参考设计来解释一些关键应用程序的执行。它还将介绍实现上述应用的低功耗技术。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将详细介绍当今一些最流行的物联网传感应用,如资产跟踪、机器状态监控、活动监控、钥匙扣、智能门、智能球、吸入器、暖通空调等。这将涉及展示 NXP 的演示/参考设计来解释一些关键应用程序的执行。它还将介绍实现上述应用的低功耗技术。
記事全体を表示
动力总成和车辆动力学:电气化——用于高压电池管理系统的 MC3377x 电池控制器 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 用于 HV BMS 的 MC33771x IC 产品培训。1- 简短的BMS市场介绍(包括。关键参与者、要求、竞争对手);2- 介绍 NXP BMS 路线图和关键产品(BCC14、BCC6 和 TPL);3- 关键 BMS 应用(14V、48V、HV 菊花链、HV CAN、无线),包括差异化和价值主张;4- 市场、应用、参考设计和产品展望;5- 功能安全方面 - 系统安全目标以及如何实现功能安全。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 用于 HV BMS 的 MC33771x IC 产品培训。1- 简短的BMS市场介绍(包括。关键参与者、要求、竞争对手);2- 介绍 NXP BMS 路线图和关键产品(BCC14、BCC6 和 TPL);3- 关键 BMS 应用(14V、48V、HV 菊花链、HV CAN、无线),包括差异化和价值主张;4- 市场、应用、参考设计和产品展望;5- 功能安全方面 - 系统安全目标以及如何实现功能安全。
記事全体を表示
HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Before you can start debugging an S32DS for Vision project for S32V234 Cortex-A53 APEX2/ISP Linux target on the S32V234-EVB, we must first setup the hardware connections and start the Linux BSP OS. 1) Connect (1) S32V234 USB Micro B port to (2) USB A port on your PC. This allow you to connect to the Linux BSP OS via a terminal program to issue commands and to obtain the IP address. 2) Insert microSDHC card (with U-boot, Linux kernel, devicetree, and root file system loaded*) into (3) the S32V234 SD card slot   3) Connect (1) Ethernet port on S32V234 daughter card to (2) LAN**. This will allow S32DS to communicate with the Linux BSP OS for flashing and GDB debugging.   4) Connect the power supply to (3) S234V234 EVB 5) Turn on the (4) power switch, this will start the Linux BSP OS *Instructions for preparing the SD card are provided in the VisionSDK document: ..\S32DS_Vision_v2.0\S234DS\s234v234_sdk\docs\vsdk\S32V234-EVB_SetupGuide.pdf or refer to https://community.nxp.com/docs/DOC-335023  **Ensure PC is connected to LAN as well (either hardwired or wireless) Re: HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Hi Mike, Thank you so much for these detailed explanation. I installed the version as you said and found one cable which works, so now I can run the demo on my board.  Best Regards, Yue Re: HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Hi [email protected]‌, While the S32DS for Vision 2018.R1 should work, I highly recommend that you instead use the S32 Design Studio v3.1. Our support for S32V devices will be included through the 3.x versions. Please note, it is v3.1 and NOT v3.2 you should use. We have not yet provided an updated release for the S32V support within v3.2. When we do provide this update, then you will want to move to the v3.2 release and take the new S32V package. It will support the latest VSDK release at this time as well. For now, it is just the S32 Design Studio v3.1 and then install the 'S32V2xx development package' (v3.1.1) and the Vision extension package for S32V2xx' (v1.0.0). This uses the VSDK v1.3. As for the HW connection issue, I have had some issues with the USB connection, but it is generally after some extensive use. Is the connection of the microUSB on the EVB a good one or does it seem to not fit well? If it does not fit well, then perhaps it is not making good connection. I hope this is not the issue you are having, but it is worth the effort to check.  At a minimum, when you connect the USB cable, you should see LED D16 flash a few times. It is red color. For me, when I connect it, WIndows incorrectly identifies it as a Mouse, as you can see below, but it still is assigned a COM port and so I can then connect with the terminal program. Hope it helps! Mike Re: HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Hi Mike, Thank you for your reply. I'm actually using S32DS.Vision.2018.R1, since I'll use S32V234EVB2 to develop some vision related project, do I need to change to v3.1? I'm also using VSDK v1.4.1, so I'll change to v1.3. I can't see it in windows device manager or terminal program, I tried two different USB-MicroUSB cable but still the same result, should I use certain type? Thanks in advance. Best Regards, Yue Re: HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Hello [email protected]‌, Please ensure the HW is connected to the power supply and the power is switched on. The SD card does not matter for the Windows OS on the PC to detect a connection to the USB port on the EVB. Could you see the USB connection in the Windows Device Manager? If you are using the S32 Design Studio, please ensure you are using v3.1. The version 3.2 does not yet support the Vision Extension Package. Also, you need to be sure to use the BSP contained within the Vision SDK v1.3, which was installed with S32 Design Studio v3.1. If you install a newer BSP to the SD card vs the version of Vision SDK you are using, then it will not work. Were you able to connect to the HW using the terminal program? Best Regards, Mike Re: HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Thank you Mike! I have another question now. I was preparing the board as below. When I got to step 3, I didn't get any infromation that the drivers have been installed, also the LED of UART0 was off. I prepared the SD card as the guide said and installed VSDK on my laptop. Could you tell me what might be the problem? Is it the microUSB cable that I used or the SD card was not prepared well? Thanks a lot in advance. Re: HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Hello [email protected]‌, There is 2 micro usb ports on s32v234-evb2 board, use the one labeled 'UART0'. Best Regards, Mike Re: HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP Thank you for sharing. I just bought it this month, and there's no micro usb port for s32v234-evb2 board. So guess I only need ethernet and sd card?
記事全体を表示
i.MX-RT:颠覆性的跨界 MCU <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
記事全体を表示
实践研讨会:使用全新低成本 S32V SOM 开发平台进行视觉/ADAS 处理_Lab.zip <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 实验室材料。本次会议介绍了 MicroSys 用于视觉处理的新型低成本 S32V 系统级模块 (SOM) 板。课程还通过实践的方式讲解了完整的硬件和软件生态系统。这些主板支持 QNX、LDW 演示和许多其他演示。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 实验室材料。本次会议介绍了 MicroSys 用于视觉处理的新型低成本 S32V 系统级模块 (SOM) 板。课程还通过实践的方式讲解了完整的硬件和软件生态系统。这些主板支持 QNX、LDW 演示和许多其他演示。
記事全体を表示
NXP MCU 和 MPU 语音和音频解决方案,面向 AI-IoT 市场 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍恩智浦针对物联网市场的完整语音和音频解决方案。其中包括语音通话、AI语音识别和音乐播放的解决方案。NXP 在其 MCU 和 MPU 产品上提供了完整且优化的音频框架,为物联网开发人员提供了现成且易于使用的语音和音频功能。在AI音箱、家电设备、语音控制节点等应用领域。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍恩智浦针对物联网市场的完整语音和音频解决方案。其中包括语音通话、AI语音识别和音乐播放的解决方案。NXP 在其 MCU 和 MPU 产品上提供了完整且优化的音频框架,为物联网开发人员提供了现成且易于使用的语音和音频功能。在AI音箱、家电设备、语音控制节点等应用领域。
記事全体を表示
DES-N2035 IAR 系统:物联网应用的调试技术 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 物联网应用通常具有一些共同的基本要求;应用程序本身需要小巧、快速、低能耗,同时上市时间应尽可能短。为了帮助您满足这些需求,实际上,您已经掌握了执行代码智能调试的各种可能性和技术。在本课程中,您将学习如何以智能的方式使用调试功能(如各种类型的复杂断点、宏、堆栈检查、事件日志、实时数据、分析和运行时代码分析)来全面调试您的代码。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 物联网应用通常具有一些共同的基本要求;应用程序本身需要小巧、快速、低能耗,同时上市时间应尽可能短。为了帮助您满足这些需求,实际上,您已经掌握了执行代码智能调试的各种可能性和技术。在本课程中,您将学习如何以智能的方式使用调试功能(如各种类型的复杂断点、宏、堆栈检查、事件日志、实时数据、分析和运行时代码分析)来全面调试您的代码。 设计 | 软件与服务
記事全体を表示