<?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 Not able to Run the currently flashed program using (gdb) continue or (gdb) mon go command in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Not-able-to-Run-the-currently-flashed-program-using-gdb-continue/m-p/1479609#M191875</link>
    <description>&lt;P&gt;We've came across with one issue with flashing the built image in the EVK-MIMXRT685 target. To flash the image in the target&amp;nbsp;we are using following steps as mentioned in the section &lt;STRONG&gt;5.1-Build and Debug Arm Application&lt;/STRONG&gt; from the document "&lt;STRONG&gt;Getting Started with Xplorer for EVK-MIMXRT685&lt;/STRONG&gt;" which is available into docs folder of SDK EVK-MIMXRT685 v2.11.1.&lt;/P&gt;&lt;P&gt;1. After successful build (build steps not added here from document)&lt;BR /&gt;2. Launch the GDB server.&lt;BR /&gt;user@linux:/opt/JLink$ ./JLinkGDBServerCLExe -device MIMXRT685S_M33 -if SWD&lt;BR /&gt;3. Connect with GDB to the device and load Arm application.&lt;BR /&gt;user@jlinux:~/SDK/boards/evkmimxrt685/driver_examples/usart/dma_transfer/armgcc$ arm-none-eabi-gdb debug/usart_dma_transfer.elf&lt;/P&gt;&lt;P&gt;Reading symbols from debug/usart_dma_transfer.elf...&lt;BR /&gt;(gdb) target remote localhost:2331&lt;/P&gt;&lt;P&gt;(gdb) mon reset&lt;/P&gt;&lt;P&gt;(gdb) load&lt;/P&gt;&lt;P&gt;After executing the above 3 steps if we used (gdb) continue or (gdb) monitor go command then target is not executing current flashed program it is running previously flashed program. But if we pressed reset button from the board then currently flashed program is running, strange isn't it?&lt;/P&gt;&lt;P&gt;Note: Same is happening with debugging also if we use continue command or mon go command in debugging.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Second observation:&lt;/P&gt;&lt;P&gt;if we execute following commands&lt;BR /&gt;1. After successful build (build steps not added here from document)&lt;BR /&gt;2. Launch the GDB server.&lt;BR /&gt;user@linux:/opt/JLink$ ./JLinkGDBServerCLExe -device MIMXRT685S_M33 -if SWD&lt;BR /&gt;3. Connect with GDB to the device and load Arm application.&lt;BR /&gt;user@jlinux:~/SDK/boards/evkmimxrt685/driver_examples/usart/dma_transfer/armgcc$ arm-none-eabi-gdb debug/usart_dma_transfer.elf&lt;BR /&gt;Reading symbols from debug/usart_dma_transfer.elf...&lt;BR /&gt;(gdb) target remote localhost:2331&lt;BR /&gt;&lt;BR /&gt;(gdb) mon reset&lt;/P&gt;&lt;P&gt;(gdb) load&lt;BR /&gt;&lt;BR /&gt;(gdb) mon reset&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;and then executed (gdb) continue or (gdb) mon go command then currently flashed program is running on the target.&lt;/P&gt;&lt;P&gt;Note: Same is happening with debugging also.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could you please confirm on the steps which are mentioned in the "&lt;STRONG&gt;Getting Started with Xplorer for EVK-MIMXRT685&lt;/STRONG&gt;" document from SDK EVK-MIMXRT685 v2.11.1?&lt;/P&gt;&lt;P&gt;Also correct us if we are doing something wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Gopichand Sonawane&lt;/P&gt;</description>
    <pubDate>Fri, 24 Jun 2022 06:51:13 GMT</pubDate>
    <dc:creator>gopichand_gs</dc:creator>
    <dc:date>2022-06-24T06:51:13Z</dc:date>
    <item>
      <title>Not able to Run the currently flashed program using (gdb) continue or (gdb) mon go command</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Not-able-to-Run-the-currently-flashed-program-using-gdb-continue/m-p/1479609#M191875</link>
      <description>&lt;P&gt;We've came across with one issue with flashing the built image in the EVK-MIMXRT685 target. To flash the image in the target&amp;nbsp;we are using following steps as mentioned in the section &lt;STRONG&gt;5.1-Build and Debug Arm Application&lt;/STRONG&gt; from the document "&lt;STRONG&gt;Getting Started with Xplorer for EVK-MIMXRT685&lt;/STRONG&gt;" which is available into docs folder of SDK EVK-MIMXRT685 v2.11.1.&lt;/P&gt;&lt;P&gt;1. After successful build (build steps not added here from document)&lt;BR /&gt;2. Launch the GDB server.&lt;BR /&gt;user@linux:/opt/JLink$ ./JLinkGDBServerCLExe -device MIMXRT685S_M33 -if SWD&lt;BR /&gt;3. Connect with GDB to the device and load Arm application.&lt;BR /&gt;user@jlinux:~/SDK/boards/evkmimxrt685/driver_examples/usart/dma_transfer/armgcc$ arm-none-eabi-gdb debug/usart_dma_transfer.elf&lt;/P&gt;&lt;P&gt;Reading symbols from debug/usart_dma_transfer.elf...&lt;BR /&gt;(gdb) target remote localhost:2331&lt;/P&gt;&lt;P&gt;(gdb) mon reset&lt;/P&gt;&lt;P&gt;(gdb) load&lt;/P&gt;&lt;P&gt;After executing the above 3 steps if we used (gdb) continue or (gdb) monitor go command then target is not executing current flashed program it is running previously flashed program. But if we pressed reset button from the board then currently flashed program is running, strange isn't it?&lt;/P&gt;&lt;P&gt;Note: Same is happening with debugging also if we use continue command or mon go command in debugging.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Second observation:&lt;/P&gt;&lt;P&gt;if we execute following commands&lt;BR /&gt;1. After successful build (build steps not added here from document)&lt;BR /&gt;2. Launch the GDB server.&lt;BR /&gt;user@linux:/opt/JLink$ ./JLinkGDBServerCLExe -device MIMXRT685S_M33 -if SWD&lt;BR /&gt;3. Connect with GDB to the device and load Arm application.&lt;BR /&gt;user@jlinux:~/SDK/boards/evkmimxrt685/driver_examples/usart/dma_transfer/armgcc$ arm-none-eabi-gdb debug/usart_dma_transfer.elf&lt;BR /&gt;Reading symbols from debug/usart_dma_transfer.elf...&lt;BR /&gt;(gdb) target remote localhost:2331&lt;BR /&gt;&lt;BR /&gt;(gdb) mon reset&lt;/P&gt;&lt;P&gt;(gdb) load&lt;BR /&gt;&lt;BR /&gt;(gdb) mon reset&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;and then executed (gdb) continue or (gdb) mon go command then currently flashed program is running on the target.&lt;/P&gt;&lt;P&gt;Note: Same is happening with debugging also.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could you please confirm on the steps which are mentioned in the "&lt;STRONG&gt;Getting Started with Xplorer for EVK-MIMXRT685&lt;/STRONG&gt;" document from SDK EVK-MIMXRT685 v2.11.1?&lt;/P&gt;&lt;P&gt;Also correct us if we are doing something wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Gopichand Sonawane&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 06:51:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Not-able-to-Run-the-currently-flashed-program-using-gdb-continue/m-p/1479609#M191875</guid>
      <dc:creator>gopichand_gs</dc:creator>
      <dc:date>2022-06-24T06:51:13Z</dc:date>
    </item>
  </channel>
</rss>

