<?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>LPC MicrocontrollersのトピックRe: Watchdog and ISP mode</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-and-ISP-mode/m-p/2046673#M57711</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/112751"&gt;@abele_barbieri&lt;/a&gt;,&lt;BR /&gt;My suspect is that the watchdog is being triggered on the bootloader side. So I will suggest disabling the watchdog and any interruption before calling the ISP reinvoke. However as mentioned in the chapter 17.6.1 called Watchdog mode register "&lt;EM&gt;Once the WDEN, WDPROTECT, or WDRESET bits are set they cannot be cleared by software. Both flags are cleared by an external reset or a Watchdog timer reset&lt;/EM&gt;."&lt;BR /&gt;Could you try doing a software reset for the peripheral? The following API should help:&lt;BR /&gt;RESET_PeripheralReset(kWWDT_RST_SHIFT_RSTn);&lt;/P&gt;
&lt;P&gt;BR&lt;BR /&gt;Habib&lt;/P&gt;</description>
    <pubDate>Tue, 18 Feb 2025 21:24:30 GMT</pubDate>
    <dc:creator>Habib_MS</dc:creator>
    <dc:date>2025-02-18T21:24:30Z</dc:date>
    <item>
      <title>Watchdog and ISP mode</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-and-ISP-mode/m-p/2043468#M57678</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I'm using LPC51U68 for a customer board, and now I'tring to enter the ISP UART mode by calling from user code the&amp;nbsp;IAP_ReinvokeISP() function.&lt;BR /&gt;The LPC answers to "Syncronized" starting messages, and enters in ISP UART mode.&lt;BR /&gt;Unfortunately, after the programmed time, the Watchdog resets the board and the application code restart (causing exit from ISP mode).&lt;BR /&gt;There is a way to solve/handle this issue?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Abele&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2025 14:09:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-and-ISP-mode/m-p/2043468#M57678</guid>
      <dc:creator>abele_barbieri</dc:creator>
      <dc:date>2025-02-13T14:09:32Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog and ISP mode</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-and-ISP-mode/m-p/2046673#M57711</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/112751"&gt;@abele_barbieri&lt;/a&gt;,&lt;BR /&gt;My suspect is that the watchdog is being triggered on the bootloader side. So I will suggest disabling the watchdog and any interruption before calling the ISP reinvoke. However as mentioned in the chapter 17.6.1 called Watchdog mode register "&lt;EM&gt;Once the WDEN, WDPROTECT, or WDRESET bits are set they cannot be cleared by software. Both flags are cleared by an external reset or a Watchdog timer reset&lt;/EM&gt;."&lt;BR /&gt;Could you try doing a software reset for the peripheral? The following API should help:&lt;BR /&gt;RESET_PeripheralReset(kWWDT_RST_SHIFT_RSTn);&lt;/P&gt;
&lt;P&gt;BR&lt;BR /&gt;Habib&lt;/P&gt;</description>
      <pubDate>Tue, 18 Feb 2025 21:24:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-and-ISP-mode/m-p/2046673#M57711</guid>
      <dc:creator>Habib_MS</dc:creator>
      <dc:date>2025-02-18T21:24:30Z</dc:date>
    </item>
  </channel>
</rss>

