<?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: Integrate IPCF and VR5510 Watchdog functionality in S32G</title>
    <link>https://community.nxp.com/t5/S32G/Integrate-IPCF-and-VR5510-Watchdog-functionality/m-p/2251629#M15585</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/253785"&gt;@honeybee1881&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your post.&lt;/P&gt;
&lt;P&gt;For such kind of issues, it is highly related with the resource conflict issues between M and A part, like memory address, clock, pin, etc.&lt;/P&gt;
&lt;P&gt;I suggest firstly checking the resources used on M core side first and then to check if they are also used/initialized on A core part.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Chenyin&lt;/P&gt;</description>
    <pubDate>Mon, 01 Dec 2025 02:46:01 GMT</pubDate>
    <dc:creator>chenyin_h</dc:creator>
    <dc:date>2025-12-01T02:46:01Z</dc:date>
    <item>
      <title>Integrate IPCF and VR5510 Watchdog functionality</title>
      <link>https://community.nxp.com/t5/S32G/Integrate-IPCF-and-VR5510-Watchdog-functionality/m-p/2250946#M15576</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I am currently working with the RDB3 board and utilizing the example projects provided in S32 Design Studio.&lt;/P&gt;&lt;P&gt;My goal is to integrate IPCF functionality along with the external watchdog feature—specifically, to send a reset signal from the A core to the M core using IPCF as the communication medium. As I am relatively new to this topic, I started by integrating the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;IPCF_Example_S32G399A_M7_0&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;project into the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Wdg_VR5510_HLD_Example_S32G399A_M7. I have adapted the source code and configurations accordingly to successfully build the project.&lt;/P&gt;&lt;P&gt;I generated the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;.bin&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;file for the M core and compiled the IPCF source code from the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;ipc-shm&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;examples for the A core.&lt;/P&gt;&lt;P&gt;For executing the examples, I am using the S32G boot image from NXP with BSP version 40. The M core&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;.bin&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;file is being transferred via U-Boot as described in the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;IPCF_Example_S32G399A_M7_0&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;instructions.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Issue:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Upon booting the OS, the boot process appears to get stuck after displaying the following log:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;a core log stopping at 
  0.632631] 401cc000.serial: ttyLF1 at MMIO 0x401cc000 (irq = 47, base_baud = 7812500) is a FSL_LINFLEX
[    0.642399] 402bc000.serial: ttyLF2 at MMIO 0x402bc000 (irq = 68, base_baud = 7812500) is a FSL_LINFLEX
[    0.653367] s32cc_fccu 4030c000.fccu: FCCU status is 0 (normal)
[    0.661337] sja1110-sw@1 enforce active low on chipselect handle&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could help me to check where its going wrong?&lt;/P&gt;&lt;P&gt;&lt;LI-PRODUCT title="S32G3" id="S32G3"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;LI-PRODUCT title="S32G-VNP-RDB3" id="S32G-VNP-RDB3"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;LI-PRODUCT title="IPCF" id="IPCF"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;LI-PRODUCT title="VR5510" id="VR5510"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2025 08:18:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Integrate-IPCF-and-VR5510-Watchdog-functionality/m-p/2250946#M15576</guid>
      <dc:creator>honeybee1881</dc:creator>
      <dc:date>2025-11-28T08:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: Integrate IPCF and VR5510 Watchdog functionality</title>
      <link>https://community.nxp.com/t5/S32G/Integrate-IPCF-and-VR5510-Watchdog-functionality/m-p/2251629#M15585</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/253785"&gt;@honeybee1881&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your post.&lt;/P&gt;
&lt;P&gt;For such kind of issues, it is highly related with the resource conflict issues between M and A part, like memory address, clock, pin, etc.&lt;/P&gt;
&lt;P&gt;I suggest firstly checking the resources used on M core side first and then to check if they are also used/initialized on A core part.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Chenyin&lt;/P&gt;</description>
      <pubDate>Mon, 01 Dec 2025 02:46:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Integrate-IPCF-and-VR5510-Watchdog-functionality/m-p/2251629#M15585</guid>
      <dc:creator>chenyin_h</dc:creator>
      <dc:date>2025-12-01T02:46:01Z</dc:date>
    </item>
  </channel>
</rss>

