<?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: RT1062 software reset in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1263035#M13838</link>
    <description>&lt;P&gt;Hello Mark,&lt;/P&gt;&lt;P&gt;the EA examples I've used have the following proprieties:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Code is running in external flash&lt;/LI&gt;&lt;LI&gt;evkmimxtr1060_flexspi_nor_config.c is configured for ATXP032&lt;/LI&gt;&lt;LI&gt;Samples running without debugger, after powering up or hardware reset&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;To test the Flash configuration, I replaced the flash section of the sample binary with the one from uTaskerSerialLoader_i.MX-RT1062_OEM_USB-MSD_Kboot-HID_SREC-UART_SD-Card_AES256.bin. A software reset is also not possible with the patched example.&lt;/P&gt;&lt;P&gt;Are there some prerequisites before calling NVIC_SystemReset() ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Apr 2021 18:40:35 GMT</pubDate>
    <dc:creator>Svenifax</dc:creator>
    <dc:date>2021-04-15T18:40:35Z</dc:date>
    <item>
      <title>RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1261869#M13800</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm trying to reset the RT1062 MCU via software. Some tests with different methods failed:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;NVIC_SystemReset();&lt;/LI&gt;&lt;LI&gt;SRC_DoSoftwareResetARMCore0(SRC);&lt;/LI&gt;&lt;LI&gt;WDOG_TriggerSystemSoftwareReset(WDOG1);&lt;/LI&gt;&lt;LI&gt;wdog_config_t wdog_config;&lt;BR /&gt;WDOG_GetDefaultConfig(&amp;amp;wdog_config);&lt;BR /&gt;wdog_config.timeoutValue = 0x0U; /* Timeout value is (0x0 + 1)/2 = 0.5 sec. */&lt;BR /&gt;WDOG_Init(WDOG1, &amp;amp;wdog_config);&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;After calling one of the them, the MCU hangs, maybe in the ROM bootloader.&lt;/P&gt;&lt;P&gt;The firmware image resides in the external NOR flash. The internal ROM bootloader loads the boot image into OCRAM and will be executed from this location.&lt;/P&gt;&lt;P&gt;How is a software reset performed on RT1062 MCUs?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Apr 2021 09:13:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1261869#M13800</guid>
      <dc:creator>Svenifax</dc:creator>
      <dc:date>2021-04-14T09:13:34Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262030#M13807</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Does you application change FlexRAM layout?&lt;BR /&gt;If so the ROM loader doesn't seem to be able to handle resets and you need to set the FlexRAM back to its original state before using any of the methods.&lt;/P&gt;&lt;P&gt;Try some 1062 references at&lt;BR /&gt;&lt;A href="https://www.utasker.com/iMX/RT1060.html" target="_blank" rel="noopener"&gt;https://www.utasker.com/iMX/RT1060.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.utasker.com/iMX/iMX_RT1062_OEM.html" target="_blank" rel="noopener"&gt;https://www.utasker.com/iMX/iMX_RT1062_OEM.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.utasker.com/iMX/Teensy_4_0.html" target="_blank" rel="noopener"&gt;https://www.utasker.com/iMX/Teensy_4_0.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.utasker.com/iMX/Teensy_4_1.html" target="_blank" rel="noopener"&gt;https://www.utasker.com/iMX/Teensy_4_1.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;which have command line menus of UART, USB-CD and/or Telnet. In the administrator menu there are commands to perform software resets and test watchdog resets. The applications run in ITC for maximum speed and solve the typical iMXT RT problems like this.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;BR /&gt;&lt;EM&gt;[uTasker project developer for Kinetis and i.MX RT]&lt;/EM&gt;&lt;BR /&gt;&lt;FONT color="#999999"&gt;Contact me by personal message or on the uTasker web site to discuss professional training, solutions to problems or rapid product development requirements&lt;BR /&gt;&lt;BR /&gt;For professionals searching for faster, problem-free Kinetis and i.MX RT 10xx developments the uTasker project holds the key: &lt;A href="https://www.utasker.com/iMX/RT1064.html" target="_blank" rel="noopener"&gt;https://www.utasker.com/iMX/RT1064.html&lt;/A&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 11:42:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262030#M13807</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-04-15T11:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262643#M13825</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;Does you application change FlexRAM layout?&lt;BR /&gt;If so the ROM loader doesn't seem to be able to handle resets and you need to set the FlexRAM back too its original state before using any of the methods.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;No, my application doesn't change the FlexRAM layout.&lt;/P&gt;&lt;P&gt;@ NXP: Any ideas?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 08:27:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262643#M13825</guid>
      <dc:creator>Svenifax</dc:creator>
      <dc:date>2021-04-15T08:27:29Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262735#M13827</link>
      <description>&lt;P&gt;Hello Svenifax,&lt;/P&gt;&lt;P&gt;do you use the NXP Evaluation-board or an own design? If you are using your own design which Flash model do you use?&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 09:59:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262735#M13827</guid>
      <dc:creator>Masmiseim</dc:creator>
      <dc:date>2021-04-15T09:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262754#M13828</link>
      <description>&lt;P&gt;Hello&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor-V lia-component-message-view-widget-author-username"&gt;&lt;A href="https://community.nxp.com/t5/user/viewprofilepage/user-id/56740" target="_self"&gt;&lt;SPAN class=""&gt;&amp;nbsp;Masmiseim,&lt;/SPAN&gt;&lt;/A&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor-V lia-component-message-view-widget-author-username"&gt;&lt;SPAN class=""&gt;we are using the Embedded Artists iMX RT1062 OEM board.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor-V lia-component-message-view-widget-author-username"&gt;&lt;SPAN class=""&gt;&lt;A href="https://www.embeddedartists.com/products/imx-rt1062-oem/" target="_blank" rel="noopener"&gt;https://www.embeddedartists.com/products/imx-rt1062-oem/&lt;/A&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor-V lia-component-message-view-widget-author-username"&gt;&lt;SPAN class=""&gt;The Flash used on SOM is a ATXP032 (4 MByte EcoXiP from Adesto)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor-V lia-component-message-view-widget-author-username"&gt;&lt;SPAN class=""&gt;&lt;A href="https://www.dialog-semiconductor.com/sites/default/files/ds-atxp032.pdf" target="_blank" rel="noopener"&gt;https://www.dialog-semiconductor.com/sites/default/files/ds-atxp032.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor-V lia-component-message-view-widget-author-username"&gt;&lt;SPAN class=""&gt;Software reset doesn't work ether on our custom board using the OEM board or the Embedded Artists developer board.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor-V lia-component-message-view-widget-author-username"&gt;&lt;SPAN class=""&gt;Regards, Sven&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 10:30:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262754#M13828</guid>
      <dc:creator>Svenifax</dc:creator>
      <dc:date>2021-04-15T10:30:13Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262783#M13830</link>
      <description>&lt;P&gt;Hi Sven&lt;/P&gt;&lt;P&gt;Try this on your board:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.utasker.com/iMX/iMX_RT1062_OEM.html" target="_blank"&gt;https://www.utasker.com/iMX/iMX_RT1062_OEM.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It contains commands in it administration menu to reset and test watchdog - if it works on your HW it points to a SW issue. I can then give you the exact code to avoid difficulties.&lt;/P&gt;&lt;P&gt;Se also &lt;A href="https://www.youtube.com/watch?v=o7hQbOqhJoc" target="_blank"&gt;https://www.youtube.com/watch?v=o7hQbOqhJoc&lt;/A&gt; for a complete secure loader concept for Embedded Artist users.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 11:48:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262783#M13830</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-04-15T11:48:36Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262952#M13833</link>
      <description>&lt;P&gt;Hello Mark,&lt;/P&gt;&lt;P&gt;the binaries you pointed out are working well. Reset functionality controlled by the menu works as expected.&lt;/P&gt;&lt;P&gt;So it seems to be a software issue in my application.&lt;/P&gt;&lt;P&gt;I tested the NXP eaimxrt1062_freertos_hello example, a reset does also &lt;EM&gt;&lt;STRONG&gt;not&lt;/STRONG&gt; &lt;/EM&gt;work. Maybe an configuration issue in Flash or DCD config?&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Sven&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 15:38:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262952#M13833</guid>
      <dc:creator>Svenifax</dc:creator>
      <dc:date>2021-04-15T15:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262961#M13834</link>
      <description>&lt;P&gt;Hi Sven&lt;/P&gt;&lt;P&gt;Are the references that you are testing running from RAM or are they programmed in QSPI flash?&lt;/P&gt;&lt;P&gt;&lt;U&gt;If they run I RAM it may be normal&lt;/U&gt; that they don't work because, as you suggest, they have no valid flash configuration and so will cause the ROM loader to be entered after each reset.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;EM&gt;P.S. In case you need a complete solution for your EA based development (Ethernet, TCP/IP, WiFi, file systems in SD card and Adesto EcoXiP flash, TFT and touch, Modbus, dual HSUSB host/device classes, secure OTA and field programming, fastest operation with lowest power consumption and lowest radiation, FreeRTOS option, i.MX RT 1062 based project simulation in Visual Studio and one-on-one developer support) also consider the uTasker project as fast, reliable and complete product development route.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 15:51:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262961#M13834</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-04-15T15:51:24Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262994#M13836</link>
      <description>&lt;P&gt;Hello Svenifax,&lt;/P&gt;&lt;P&gt;this is what I thought. The .MX RT1xxx boot ROM needs to reset the Flash via JEDEC-Reset on boot otherwise it loses synchronization and the controller hangs. To solve this, a i.MX RT1xxx boot ROM option must be enabled to automatically apply a JEDEC reset to the Adesto Flash right after the MCU reset. Adesto has published an application note for this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://cdn2.hubspot.net/hubfs/5196899/AN106A1.pdf" target="_blank" rel="noopener"&gt;https://cdn2.hubspot.net/hubfs/5196899/AN106A1.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 16:43:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1262994#M13836</guid>
      <dc:creator>Masmiseim</dc:creator>
      <dc:date>2021-04-15T16:43:06Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1263007#M13837</link>
      <description>&lt;P&gt;Sven&lt;/P&gt;&lt;P&gt;DCD should be of no relevance but if you are booting example SDK projects from EcoXiP you need to see whether they can boot themselves (without debugger) first to see whether they are operational (and therefore can also handle a SW reset or watchdog case).&lt;BR /&gt;In some cases, when the flash configuration is not correct, a download with the debugger may work since it sets the SP and PC accordingly but the ROM loader fails since it doesn't configure the EcoXip as needed for it to boot.&lt;BR /&gt;Check the evkmimxtr1060_flexspi_nor_config.c and h that are being used and ensure that it has the following in it:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;" /* This is a Serial NOR Configuration Block definition for Adesto's EcoXiP &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;* flash (&lt;STRONG&gt;ATXP032&lt;/STRONG&gt;). Among other parameters it configues the system to operate&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;* with:&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;* - Octal-SPI&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;* - Double Data Rate (DDR)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;* - SCLK = 133MHz&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;*/"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Check also that your own application can start without the debugger and that your issue is not restricted to commanded and watchdog resets, but may be more general.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 17:24:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1263007#M13837</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-04-15T17:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1263035#M13838</link>
      <description>&lt;P&gt;Hello Mark,&lt;/P&gt;&lt;P&gt;the EA examples I've used have the following proprieties:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Code is running in external flash&lt;/LI&gt;&lt;LI&gt;evkmimxtr1060_flexspi_nor_config.c is configured for ATXP032&lt;/LI&gt;&lt;LI&gt;Samples running without debugger, after powering up or hardware reset&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;To test the Flash configuration, I replaced the flash section of the sample binary with the one from uTaskerSerialLoader_i.MX-RT1062_OEM_USB-MSD_Kboot-HID_SREC-UART_SD-Card_AES256.bin. A software reset is also not possible with the patched example.&lt;/P&gt;&lt;P&gt;Are there some prerequisites before calling NVIC_SystemReset() ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 18:40:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1263035#M13838</guid>
      <dc:creator>Svenifax</dc:creator>
      <dc:date>2021-04-15T18:40:35Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1263043#M13839</link>
      <description>&lt;P&gt;Sven&lt;/P&gt;&lt;P&gt;I think you have excluded that there is an issue with the flash configuration therefore the problem must be with the SW reset code.&lt;/P&gt;&lt;P&gt;- Check that it is not being optimised out&lt;/P&gt;&lt;P&gt;- put SW delays before and after the instructions (I have a number of users of the uTasker loader who need to reset SDK developed applications to it and remember at least one saying that the reset would only work if delays were added somewhere in the related code)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;uTasker applications on the EA boards reset to the loader via a RAM mailbox as follows (or standard SW reset if mailbox not set):&lt;BR /&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;*BOOT_MAIL_BOX = RESET_TO_SERIAL_LOADER;&lt;/STRONG&gt; // put a message in the boot mailbox and reset the board (if the serial loader is installed and uses the mailbox it will cause the loader to start)&lt;/FONT&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;fnResetBoard();&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;and uses&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;// This routine is called to reset the processor&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;//&lt;/FONT&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;extern void fnResetBoard(void)&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;{&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; uDisable_Interrupt();&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;APPLICATION_INT_RESET_CTR_REG = (VECTKEY | SYSRESETREQ);&lt;/STRONG&gt; // request cortex core reset, which will cause the software reset bit to be set in the mode controller for recognition after restart&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;IOMUXC_GPR_GPR16 = (IOMUXC_GPR_GPR16_RESERVED | IOMUXC_GPR_GPR16_INIT_ITCM_EN | IOMUXC_GPR_GPR16_INIT_DTCM_EN);&lt;/STRONG&gt; // set the FlexRAM layout back to that taken from the eFuse setting (default configuration) - although the reset is commanded before executing this line it still operates and avoids the RAM layout being changed when the code is still running&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;FOREVER_LOOP() {}&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;}&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The FlexRAM restore is only needed when using dynamically configured FlexRAM settings.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 19:45:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1263043#M13839</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-04-15T19:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1266566#M13908</link>
      <description>&lt;P&gt;Hello Mark,&lt;/P&gt;&lt;P&gt;could please tell me the predefined values of your sample code?&lt;/P&gt;&lt;P&gt;Is APPLICATION_INT_RESET_CTR_REG the SRC Control Register (SRC_SCR) / 400F_8000?&lt;/P&gt;&lt;P&gt;What's the value of VECTKEY? Is SYSRESETREQ bit 13 of SRC_SCR (core0_rst)?&lt;/P&gt;&lt;P&gt;What's the value of IOMUXC_GPR_GPR16_RESERVED?&lt;/P&gt;&lt;P&gt;Thanks, Sven&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 09:46:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1266566#M13908</guid>
      <dc:creator>Svenifax</dc:creator>
      <dc:date>2021-04-22T09:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1266649#M13915</link>
      <description>&lt;P&gt;Hi Sven&lt;/P&gt;&lt;P&gt;APPLICATION_INT_RESET_CTR_REG is the Cortex System Control Block register at 0xe000ed0c&lt;BR /&gt;VECTKEY is 0x05fa0000&lt;BR /&gt;and&lt;BR /&gt;SYSRESETREQ = 0x00000004&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;IOMUXC_GPR_GPR16_RESERVED is 0x00200000&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 12:33:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1266649#M13915</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-04-22T12:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1269618#M14011</link>
      <description>&lt;P&gt;Hello Mark,&lt;/P&gt;&lt;P&gt;unfortunately, all the methods doesn't work for me.&lt;/P&gt;&lt;P&gt;Are you reset the Flash via JEDEC-Reset (JESD252) before software reset?&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Sven&lt;/P&gt;</description>
      <pubDate>Wed, 28 Apr 2021 11:22:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1269618#M14011</guid>
      <dc:creator>Svenifax</dc:creator>
      <dc:date>2021-04-28T11:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1269727#M14013</link>
      <description>&lt;P&gt;Hi Sven&lt;/P&gt;&lt;P&gt;No, there is no flash reset performed.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Apr 2021 13:54:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1269727#M14013</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-04-28T13:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1270152#M14026</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;On my side, the NVIC_SystemReset() is good (My board is MIMXRT1060-EVK board).&lt;BR /&gt;According to your statement, you also use the Watchdog to reset.&lt;BR /&gt;in my opinion, it should work well.&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;
&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Thu, 29 Apr 2021 07:32:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1270152#M14026</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2021-04-29T07:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1270292#M14030</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Svenifax&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I'm also using the same board as you and trying to do a software reset without any luck. My only difference is that I'm running code direct from Flash (XiP). Other than that&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;I seem to have tried everything you have.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The only success I've had is with the watchdog. Did you manage to get this working?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I believe&amp;nbsp;I still need to perform a software reset as I'm trying to use non initialised RAM to communicate with a bootloader and a watchdog reset seems to reset the RAM too.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Apr 2021 11:25:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1270292#M14030</guid>
      <dc:creator>Gra67</dc:creator>
      <dc:date>2021-04-29T11:25:44Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1271116#M14077</link>
      <description>&lt;P&gt;Hallo Gra67,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the watchdog does not reset the RAM.&lt;/P&gt;&lt;P&gt;Sadly, the schematics of the Embedded Artist board are not publicly available, but I guess they do it like it is done on the evaluation board of the iMXRT1060.&lt;/P&gt;&lt;P&gt;When the watchdog is triggered, the whole controller gets a power-on-reset. Compare the Schematics from the Evaluation-Board below. As a side-Effect you are also not able to read the reset-reason on start-up.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Masmiseim_0-1619983292151.png" style="width: 728px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/143773iABC5BE1D9B80D339/image-dimensions/728x343?v=v2" width="728" height="343" role="button" title="Masmiseim_0-1619983292151.png" alt="Masmiseim_0-1619983292151.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could try to configure the Pin GPIO_B1_13 to GPIO to avoid the POR. At least if it is done the same way as the evaluation-Board.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Masmiseim_1-1619983292157.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/143771iB1E464D1506BD387/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Masmiseim_1-1619983292157.png" alt="Masmiseim_1-1619983292157.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding the original problem. Check the application-Note AN106A1 from Adesto:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Masmiseim_2-1619983292172.png" style="width: 715px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/143772i6F981E7F24A4B2DF/image-dimensions/715x235?v=v2" width="715" height="235" role="button" title="Masmiseim_2-1619983292172.png" alt="Masmiseim_2-1619983292172.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Sun, 02 May 2021 19:37:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1271116#M14077</guid>
      <dc:creator>Masmiseim</dc:creator>
      <dc:date>2021-05-02T19:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: RT1062 software reset</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1271153#M14078</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Thanks for your reply.&lt;BR /&gt;I was wondering if you can upload your testing code and introduce the testing steps in brief, as I'd like to replicate the phenomenon.&lt;BR /&gt;Looking forward to your reply.&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;
&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 05:54:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1062-software-reset/m-p/1271153#M14078</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2021-05-03T05:54:08Z</dc:date>
    </item>
  </channel>
</rss>

