<?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>S32 Design StudioのトピックRe: error code is 102.</title>
    <link>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/1452000#M8513</link>
    <description>&lt;P&gt;Hello Youngdae,&lt;/P&gt;
&lt;P&gt;It is difficult to determine the cause from the limited information you have provided, however, some common causes for connection issues are:&lt;/P&gt;
&lt;P&gt;1) S32 Debug Probe is not powered. Usually occurs when ethernet connection is used, it is easy to forget that ethernet does not provide power.&lt;/P&gt;
&lt;P&gt;2) EVB is not powered. Sometimes it is necessary to change jumper settings and the board should be powered off when these are changed, but it is easy to forget to turn the power switch back on afterward. It should be noted, the power switch on the RDB2 board has 3 positions, only one of which is correct to power the board, please check that you are selecting the correct switch position.&lt;/P&gt;
&lt;P&gt;3) JTAG cable is not fully seated on the connector at either the S32 Debug Probe device end or the EVB end.&lt;/P&gt;
&lt;P&gt;4) The probe tip which connects the JTAG cable to the S32 Debug Probe device is not fully seated on the connector to the S32 Debug Probe device.&lt;/P&gt;
&lt;P&gt;5) The EVB is setup to boot from SD card and the SD card is loaded with Linux BSP and installed to the SD card slot. The Linux BSP can interfere with the S32 Debug Probe communications with the target.&lt;/P&gt;
&lt;P&gt;6) The S32 Debug Probe has specific voltage requirements (specified in the included S32 Debug Probe user guide). If a different power supply is used vs. the one included in the RDB2 kit, then it is possible that the voltage on the JTAG line is not correct for S32 Debug Probe usage.&lt;/P&gt;
&lt;P&gt;I would recommend that you try to use the button 'Test Connection' from within the Debug Configuration menu to confirm that the HW setup and communication settings are correct. This is much quicker than using the 'Debug' button for only checking the connection status.&lt;/P&gt;
&lt;P&gt;If you confirm all of the above, and it is still not working, please let us know.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Mike&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 02 May 2022 20:20:57 GMT</pubDate>
    <dc:creator>mikedoidge</dc:creator>
    <dc:date>2022-05-02T20:20:57Z</dc:date>
    <item>
      <title>error code is 102.</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/1450464#M8499</link>
      <description>&lt;P&gt;I have S32G-VNP-RDB2 board and S32 Debug probe.&lt;/P&gt;&lt;P&gt;I try to debug after build to example project.&lt;/P&gt;&lt;P&gt;but debug is fail with the following error code(Error code is 102.).&lt;/P&gt;&lt;P&gt;What could be the cause?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="youngdae_0-1651127942343.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/178280i711C018F3A150D0B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="youngdae_0-1651127942343.png" alt="youngdae_0-1651127942343.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 06:43:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/1450464#M8499</guid>
      <dc:creator>youngdae</dc:creator>
      <dc:date>2022-04-28T06:43:53Z</dc:date>
    </item>
    <item>
      <title>Re: error code is 102.</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/1452000#M8513</link>
      <description>&lt;P&gt;Hello Youngdae,&lt;/P&gt;
&lt;P&gt;It is difficult to determine the cause from the limited information you have provided, however, some common causes for connection issues are:&lt;/P&gt;
&lt;P&gt;1) S32 Debug Probe is not powered. Usually occurs when ethernet connection is used, it is easy to forget that ethernet does not provide power.&lt;/P&gt;
&lt;P&gt;2) EVB is not powered. Sometimes it is necessary to change jumper settings and the board should be powered off when these are changed, but it is easy to forget to turn the power switch back on afterward. It should be noted, the power switch on the RDB2 board has 3 positions, only one of which is correct to power the board, please check that you are selecting the correct switch position.&lt;/P&gt;
&lt;P&gt;3) JTAG cable is not fully seated on the connector at either the S32 Debug Probe device end or the EVB end.&lt;/P&gt;
&lt;P&gt;4) The probe tip which connects the JTAG cable to the S32 Debug Probe device is not fully seated on the connector to the S32 Debug Probe device.&lt;/P&gt;
&lt;P&gt;5) The EVB is setup to boot from SD card and the SD card is loaded with Linux BSP and installed to the SD card slot. The Linux BSP can interfere with the S32 Debug Probe communications with the target.&lt;/P&gt;
&lt;P&gt;6) The S32 Debug Probe has specific voltage requirements (specified in the included S32 Debug Probe user guide). If a different power supply is used vs. the one included in the RDB2 kit, then it is possible that the voltage on the JTAG line is not correct for S32 Debug Probe usage.&lt;/P&gt;
&lt;P&gt;I would recommend that you try to use the button 'Test Connection' from within the Debug Configuration menu to confirm that the HW setup and communication settings are correct. This is much quicker than using the 'Debug' button for only checking the connection status.&lt;/P&gt;
&lt;P&gt;If you confirm all of the above, and it is still not working, please let us know.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Mike&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 May 2022 20:20:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/1452000#M8513</guid>
      <dc:creator>mikedoidge</dc:creator>
      <dc:date>2022-05-02T20:20:57Z</dc:date>
    </item>
    <item>
      <title>Re: error code is 102.</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/1585217#M9664</link>
      <description>&lt;P&gt;Tips to fix-&lt;/P&gt;&lt;P&gt;Turn Windows Firewall Features ON or OFF&amp;nbsp;&lt;BR /&gt;Check your Proxy Server Settings&amp;nbsp;&lt;BR /&gt;Change your Windows Adapter Settings&amp;nbsp;&lt;BR /&gt;Run a Full Scan of your Windows PC&amp;nbsp;&lt;BR /&gt;Clear your Internet Browser Cookies &amp;amp; Cache&amp;nbsp;&lt;BR /&gt;Clear your DNS Resolver Cache in CMD&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rachel Gomez&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 06:17:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/1585217#M9664</guid>
      <dc:creator>RachelGomez123</dc:creator>
      <dc:date>2023-01-19T06:17:53Z</dc:date>
    </item>
    <item>
      <title>Re: S32 Debug Probe error code is 102.</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/2257095#M13960</link>
      <description>&lt;P&gt;Hi ，&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;when I use S32 Debug Probe,The same problem occurred.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="zhipeng_1-1765187216931.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/368948iEE3715274655E92E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="zhipeng_1-1765187216931.png" alt="zhipeng_1-1765187216931.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1. Power supply is OK&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. JTAG&amp;nbsp;Schematic ↓&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="zhipeng_0-1765187074548.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/368947i5A33706C19BBD59D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="zhipeng_0-1765187074548.png" alt="zhipeng_0-1765187074548.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;3. SD&amp;nbsp;&lt;SPAN&gt;Selection &lt;/SPAN&gt;&lt;SPAN&gt;Schematic&amp;nbsp;tried both pull-up and pull-down&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="zhipeng_0-1765187679813.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/368952iDD47CC2442E65FCB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="zhipeng_0-1765187679813.png" alt="zhipeng_0-1765187679813.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;Where could the problem be? Thank you.&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2025 09:55:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/error-code-is-102/m-p/2257095#M13960</guid>
      <dc:creator>zhipeng</dc:creator>
      <dc:date>2025-12-08T09:55:47Z</dc:date>
    </item>
  </channel>
</rss>

