<?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: PT2001 SPI in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1985339#M26158</link>
    <description>Hello, the configuration of my SPI is as follows: Clock polarity: 0, Clock phase: 1, Bit order: MSB. PT2001 has a normal 12V power supply. My SPI line is interconnected between the PT2001 development board and the klz25 development board through the self-provided pin headers. The data format is: control_word (bit 15) r_w: read (1)/write (0) operations; control_word (bits 14 to 5) offset: start address; control_word (bits 4 to 0) number: number of operations. The register address of the command code bit is: 0x101. However, I am unaware of the message framework. I did not find the message framework in the protocol of the PT2000 data manual, so I sent a randomly chosen 0x03. I am unable to confirm whether the sent command is correct. But by capturing the waveform, I can confirm that my data was sent completely. Additionally, I am unable to view the PT2001 data manual, and therefore I can only refer to the PT2000 data manual.</description>
    <pubDate>Thu, 31 Oct 2024 06:49:30 GMT</pubDate>
    <dc:creator>HK_gump</dc:creator>
    <dc:date>2024-10-31T06:49:30Z</dc:date>
    <item>
      <title>PT2001 SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1984517#M26143</link>
      <description>&lt;P&gt;I use spi to send data to PT2001, and the returned data is AAAA. Is this normal?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="HK_gump_0-1730273497529.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/307652i409CADB37B1F7047/image-size/medium?v=v2&amp;amp;px=400" role="button" title="HK_gump_0-1730273497529.jpeg" alt="HK_gump_0-1730273497529.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 07:41:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1984517#M26143</guid>
      <dc:creator>HK_gump</dc:creator>
      <dc:date>2024-10-30T07:41:37Z</dc:date>
    </item>
    <item>
      <title>Re: PT2001 SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1984691#M26150</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Do you have a logic analyzer to better analyze what is happening on the SPI bus?&amp;nbsp;The signals on the picture you shared are not very clear and difficult to analyze.&lt;/P&gt;
&lt;P&gt;I would recommend you to verify the SPI configuration and&amp;nbsp;ensure the SPI settings match the PT2001 requirements, including the clock polarity, clock phase and bit order (MSB/LSB).&lt;/P&gt;
&lt;P&gt;Also&amp;nbsp;verify that the PT2001 is properly powered and that all SPI lines (MOSI, MISO, SCK, CS) are connected without issues.&lt;/P&gt;
&lt;P&gt;Ensure the data format, command codes and message framing adhere to the PT2001 protocol. If incorrect or incomplete commands are sent, the PT2001 may not respond as expected.&lt;/P&gt;
&lt;P&gt;For details, please refer to the &lt;A href="https://www.nxp.com/webapp/sd/collateral/1677076616822733841912?version=9.2" target="_self"&gt;PT2001 full datasheet&lt;/A&gt;, section 13.2 - Serial Peripheral interface.&lt;/P&gt;
&lt;P&gt;BRs, Tomas&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 11:03:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1984691#M26150</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2024-10-30T11:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: PT2001 SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1985339#M26158</link>
      <description>Hello, the configuration of my SPI is as follows: Clock polarity: 0, Clock phase: 1, Bit order: MSB. PT2001 has a normal 12V power supply. My SPI line is interconnected between the PT2001 development board and the klz25 development board through the self-provided pin headers. The data format is: control_word (bit 15) r_w: read (1)/write (0) operations; control_word (bits 14 to 5) offset: start address; control_word (bits 4 to 0) number: number of operations. The register address of the command code bit is: 0x101. However, I am unaware of the message framework. I did not find the message framework in the protocol of the PT2000 data manual, so I sent a randomly chosen 0x03. I am unable to confirm whether the sent command is correct. But by capturing the waveform, I can confirm that my data was sent completely. Additionally, I am unable to view the PT2001 data manual, and therefore I can only refer to the PT2000 data manual.</description>
      <pubDate>Thu, 31 Oct 2024 06:49:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1985339#M26158</guid>
      <dc:creator>HK_gump</dc:creator>
      <dc:date>2024-10-31T06:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: PT2001 SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1985345#M26160</link>
      <description>According to the PT2000 data manual, after sending data, PT2001 should return AAA8, but it is returning AAAA.&lt;BR /&gt;My data format is the same as the SPI format provided in the PT2000 data manual, and I can also ensure that the data is sent completely.&lt;BR /&gt;I suspect that the control_word (bits 4 to 0) number: number of operations needs to be processed, but I cannot find the processing method in the manual. Please help me.&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Oct 2024 07:04:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1985345#M26160</guid>
      <dc:creator>HK_gump</dc:creator>
      <dc:date>2024-10-31T07:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: PT2001 SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1985370#M26161</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The PT2001 full datasheet is classified as a Secure File requiring an NDA.&lt;/P&gt;
&lt;P&gt;If your company has not signed the NDA with NXP yet, you can request it from:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/support/support:SUPPORTHOME" target="_blank"&gt;https://www.nxp.com/support/support:SUPPORTHOME&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If there is a valid NDA in place, you can download the datasheet from:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/products/power-management/motor-and-solenoid-drivers/powertrain-and-engine-control/programmable-gate-driver-for-solenoid-control:PT2001" target="_blank"&gt;https://www.nxp.com/products/power-management/motor-and-solenoid-drivers/powertrain-and-engine-control/programmable-gate-driver-for-solenoid-control:PT2001&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-10-31 090253.png" style="width: 678px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/307874i7615B414AD189E0B/image-dimensions/678x241?v=v2" width="678" height="241" role="button" title="Screenshot 2024-10-31 090253.png" alt="Screenshot 2024-10-31 090253.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;BRs, Tomas&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2024 08:03:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1985370#M26161</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2024-10-31T08:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: PT2001 SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1987821#M26235</link>
      <description>Hello, can you tell me why the PT2001 keeps returning AAA9? The data manual explains it as a byte mismatch, but there is no logical error in my code. I wonder what the actual reason is.</description>
      <pubDate>Tue, 05 Nov 2024 08:46:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/PT2001-SPI/m-p/1987821#M26235</guid>
      <dc:creator>HK_gump</dc:creator>
      <dc:date>2024-11-05T08:46:51Z</dc:date>
    </item>
  </channel>
</rss>

