<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: iMX6SX PXP Register Access in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2080229#M236295</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I'm still waiting for feedback from the team,&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Mon, 14 Apr 2025 21:26:45 GMT</pubDate>
    <dc:creator>JosephAtNXP</dc:creator>
    <dc:date>2025-04-14T21:26:45Z</dc:date>
    <item>
      <title>iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2071282#M235672</link>
      <description>&lt;P&gt;I am trying to set the PXP CSC2 registers in an IMX6SX, similar to &lt;A href="https://community.nxp.com/t5/i-MX-Processors/IMX8MP-LVDS-LCD-contrast-and-colour-saturation-control/td-p/1577867" target="_blank" rel="noopener"&gt;this post.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;To begin with I simply attempt to read the PXP_CTRL register at 0x2218000&lt;BR /&gt;My code looks like this:&lt;/P&gt;&lt;LI-CODE lang="python"&gt;import ctypes
import mmap

def read_word(address):
  with open('/dev/mem', 'rb') as f:
    mem = mmap.mmap(f.fileno(), mmap.PAGESIZE, mmap.MAP_SHARED, mmap.PROT_READ, offset=address&amp;amp;~(mmap.PAGESIZE-1))
    s = ctypes.c_uint32.from_buffer_copy(mem, address&amp;amp;(mmap.PAGESIZE-1))
    mem.close()
    return s

print(read_word(0x2218000))&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The result is that the kernel hangs with no error.&lt;/P&gt;&lt;P&gt;I am able to read other registers (for example GPIOs at 0x20E0014).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the PXP enabled and clocks configured in the device tree:&lt;/P&gt;&lt;BLOCKQUOTE&gt;pxp: pxp@2218000 {&lt;BR /&gt;compatible = "fsl,imx6sx-pxp-dma", "fsl,imx6sl-pxp-dma", "fsl,imx6dl-pxp-dma";&lt;BR /&gt;reg = &amp;lt;0x02218000 0x4000&amp;gt;;&lt;BR /&gt;interrupts = &amp;lt;GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH&amp;gt;;&lt;BR /&gt;clocks = &amp;lt;&amp;amp;clks IMX6SX_CLK_PXP_AXI&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;clks IMX6SX_CLK_DISPLAY_AXI&amp;gt;;&lt;BR /&gt;clock-names = "pxp-axi", "disp-axi";&lt;BR /&gt;power-domains = &amp;lt;&amp;amp;pd_disp&amp;gt;;&lt;BR /&gt;status = "okay";&lt;BR /&gt;};&lt;/BLOCKQUOTE&gt;&lt;P class=""&gt;Is there anything else I need to set up before I can read/set the PXP registers?&lt;/P&gt;</description>
      <pubDate>Mon, 31 Mar 2025 15:29:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2071282#M235672</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-03-31T15:29:45Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2071400#M235683</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thank you for your interest in NXP Semiconductor products,&lt;/P&gt;
&lt;P&gt;Could you try with memtool command?&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 31 Mar 2025 19:52:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2071400#M235683</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-03-31T19:52:46Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2071839#M235705</link>
      <description>&lt;P&gt;I added memtool to my image and tried the command:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;memtool -8 2218000 1&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The resulting output is:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;E&lt;/P&gt;&lt;P&gt;Reading 0x1 count starting at ad&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;And then the kernel hangs again.&lt;/P&gt;&lt;P&gt;I also tried with -16 and tried reading a couple of the other PXP registers.&lt;BR /&gt;The result was the same in all cases (even the same truncation of the output)&lt;/P&gt;&lt;P&gt;At least it seems like my code was probably fine, but there must be something I need to set up to enable the PXP module? Any ideas?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Apr 2025 08:14:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2071839#M235705</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-01T08:14:30Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2072974#M235793</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248156"&gt;@SamM&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Can you please share more details about your project,&amp;nbsp; are you using your own design with the i.MX6SX, or which board are you using?&amp;nbsp; how much&amp;nbsp; DDR memory has it?&amp;nbsp;&amp;nbsp; which BSP and version are you using?&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;Any other details that can help us to narrow the problem, like is there any warning or error during the boot up? if you can share a log, would be good to see if there is anything else that maybe pointing what would be the issue.&lt;/P&gt;
&lt;P&gt;Right now,&amp;nbsp; I think it is a RAM issue, but maybe something else it is consuming your free memory or any other peripheral it is creating a big load to the memory.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 15:35:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2072974#M235793</guid>
      <dc:creator>jamesbone</dc:creator>
      <dc:date>2025-04-02T15:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073030#M235796</link>
      <description>&lt;P&gt;Hi James,&lt;/P&gt;&lt;P&gt;Thanks for getting back&amp;nbsp; to me.&lt;/P&gt;&lt;P&gt;It is a &lt;A href="https://www.embeddedartists.com/products/imx6-solox-com/" target="_self"&gt;COM board produced by embedded artists&lt;/A&gt;&lt;BR /&gt;It has 1GB DDR3 (and free says 741MB is currently available)&lt;/P&gt;&lt;P&gt;I'm using a custom BSP provided by embedded artists (slightly modified by me to adjust lvds device timings). It is on kernel version 6.6 and uses meta-imx rel_imx_6.6.23_2.0.0&lt;/P&gt;&lt;P&gt;It seems reasonable to test with the NXP BSP. I'll grab the 6.6.23 BSP and re-test with that.&lt;/P&gt;&lt;P&gt;Output from dmsg attached&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 16:40:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073030#M235796</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-02T16:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073521#M235832</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/10885"&gt;@jamesbone&lt;/a&gt;I have just tested an iMX6ULL-14x14-evk that I have on hand, with the NXP V6.6.52-2.2.0 BSP.&lt;/P&gt;&lt;P&gt;I get the same result reading the PXP_HW_PXP_CSC2_CTRL register on that board&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;memtool -16 21CC1D0 1&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Output is truncated and the kernel hangs&lt;/P&gt;&lt;P&gt;I also noted that the pxp_test.out unit test doesn't appear to do anything and the mxc_fb_test.out unit test hangs part way through.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 08:35:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073521#M235832</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-03T08:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073541#M235835</link>
      <description>&lt;P&gt;Sorry, mxc_fb_test.out does eventually terminate but it segfaults.&lt;/P&gt;&lt;P&gt;dmesg output from that board attached.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 08:48:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073541#M235835</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-03T08:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073823#M235857</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206442"&gt;@JosephAtNXP&lt;/a&gt; , can you please try to reproduced the issue from&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248156"&gt;@SamM&lt;/a&gt; ,&amp;nbsp; in the NXP board. &amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 15:39:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073823#M235857</guid>
      <dc:creator>jamesbone</dc:creator>
      <dc:date>2025-04-03T15:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073973#M235869</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/10885"&gt;@jamesbone&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248156"&gt;@SamM&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I can reproduce on i.MX6UL devices too, we are reviewing this issue and will provide feedback about the workarounds ASAP,&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 22:57:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2073973#M235869</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-04-03T22:57:04Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2075297#M235983</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206442"&gt;@JosephAtNXP&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any update on this?&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 15:02:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2075297#M235983</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-07T15:02:53Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2075333#M235992</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Please update the following:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;cat /sys/kernel/debug/clk/clk_summary | grep pxp&lt;/LI-CODE&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 16:04:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2075333#M235992</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-04-07T16:04:17Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2075339#M235993</link>
      <description>&lt;P&gt;Here is the output of&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;cat /sys/kernel/debug/clk/clk_summary | grep pxp&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the iMX6ULL14x14-evk&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 16:24:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2075339#M235993</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-07T16:24:42Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2077238#M236126</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206442"&gt;@JosephAtNXP&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you have any more information for me?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Apr 2025 16:12:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2077238#M236126</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-09T16:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2079713#M236265</link>
      <description>&lt;P&gt;Morning &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206442"&gt;@JosephAtNXP&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Do you have any more details for me this week?&lt;/P&gt;</description>
      <pubDate>Mon, 14 Apr 2025 07:34:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2079713#M236265</guid>
      <dc:creator>SamM</dc:creator>
      <dc:date>2025-04-14T07:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2080229#M236295</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I'm still waiting for feedback from the team,&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 14 Apr 2025 21:26:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2080229#M236295</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-04-14T21:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2081040#M236352</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The clocks are not enabled and registers cannot be accessed as a consequence, team is reviewing clock enabling.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 15 Apr 2025 17:28:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2081040#M236352</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-04-15T17:28:06Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6SX PXP Register Access</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2081979#M236410</link>
      <description>&lt;P&gt;In PXP driver, runtime PM will dynamic open/close clock. For workaround, you can comment out 'clk_unprepare' in PXP relating driver.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2025 20:36:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6SX-PXP-Register-Access/m-p/2081979#M236410</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2025-04-16T20:36:22Z</dc:date>
    </item>
  </channel>
</rss>

