<?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: Programming RT1050 via serial bootloader in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848301#M1778</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;You can also try this tool, with this tool, You can flash bare image into various boot devices easily and don't need to care about headers (ivt, boot data...)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;A class="" href="https://github.com/JayHeng/nxp-sec-boot-ui" style="color: #2989c5; text-decoration: none;" title="https://github.com/JayHeng/nxp-sec-boot-ui"&gt;GitHub - JayHeng/nxp-sec-boot-ui: A one-stop GUI tool to work with NXP MCU (Kinetis, i.MXRT, LPC) ROM bootloader, It can…&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 23 Dec 2018 06:03:25 GMT</pubDate>
    <dc:creator>jay_heng</dc:creator>
    <dc:date>2018-12-23T06:03:25Z</dc:date>
    <item>
      <title>Programming RT1050 via serial bootloader</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848300#M1777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After designing the first RT1050-based board, I discovered a huge mistake (JTAG.MOD pin disconnected) so I have no JTAG/SWD interface&lt;/P&gt;&lt;P&gt;To remedy somehow, I am attempting to do some tests by downloading a firmware via SDPHOST.&lt;/P&gt;&lt;P&gt;Unfortunately, doing so triggers unexpected errors when attempting to write in the OCRAM area.&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;sdphost.exe -p com7 -- write-register 0x20200000 8 0x00&lt;BR /&gt;unexpected write response 0x89232389.&lt;BR /&gt;Status (HAB mode) = 1450735702 (0x56787856) HAB disabled.&lt;BR /&gt;Reponse Status = 2300781449 (0x89232389) REENUM Ack&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Moreover, when attempting to read more than 4 bytes from the same location, another error occurs:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;sdphost.exe -p com7 -- read-register 0x20200000 8 8&lt;BR /&gt;getStatusResponse.readPacket error 5.&lt;BR /&gt;Status (HAB mode) = 1450735702 (0x56787856) HAB disabled.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Of course the write-file command fails as well...&lt;/P&gt;&lt;P&gt;Any suggestions from you fellow engineers?&lt;/P&gt;&lt;P&gt;Please forgive me if I am asking stupid question or doing stupid errors. I am really new to RT1050.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jul 2018 09:26:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848300#M1777</guid>
      <dc:creator>giuseppescarpi</dc:creator>
      <dc:date>2018-07-04T09:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: Programming RT1050 via serial bootloader</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848301#M1778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;You can also try this tool, with this tool, You can flash bare image into various boot devices easily and don't need to care about headers (ivt, boot data...)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;&lt;A class="" href="https://github.com/JayHeng/nxp-sec-boot-ui" style="color: #2989c5; text-decoration: none;" title="https://github.com/JayHeng/nxp-sec-boot-ui"&gt;GitHub - JayHeng/nxp-sec-boot-ui: A one-stop GUI tool to work with NXP MCU (Kinetis, i.MXRT, LPC) ROM bootloader, It can…&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Dec 2018 06:03:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848301#M1778</guid>
      <dc:creator>jay_heng</dc:creator>
      <dc:date>2018-12-23T06:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: Programming RT1050 via serial bootloader</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848302#M1779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@Giuseppe, I'm getting started with a 'RT1020, and I see similar results using imx_usb_loader.&amp;nbsp; I know the connection is up 'cause I do get 0x56787856 response to a status request; plus I am able to read a few registers that are as they should be; however, most other reads return 0x89232389.&amp;nbsp;&amp;nbsp;I'm guessing there must be additional initialization that must be done, but have not stumbled on it as of yet.&amp;nbsp; What did you find?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Feb 2020 21:25:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848302#M1779</guid>
      <dc:creator>EdSutter</dc:creator>
      <dc:date>2020-02-19T21:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: Programming RT1050 via serial bootloader</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848303#M1780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ed, unfortunately I can't be of help, because in the end we were able to put MOD to ground and enable SWD for programming.&lt;/P&gt;&lt;P&gt;It is worth of mention that NXP modified the MOD pin that has now a pull-down instead than a pull-up, so when MOD is not connected, JTAG does not start in boundary scan (same behaviour than the majority of MCUs...)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Feb 2020 16:02:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848303#M1780</guid>
      <dc:creator>giuseppescarpi</dc:creator>
      <dc:date>2020-02-26T16:02:23Z</dc:date>
    </item>
    <item>
      <title>Re: Programming RT1050 via serial bootloader</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848304#M1781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok thanks for responding anyway... I've kinda concluded that the 0x89232389 must be some kind of valid-but-undocumented return code that is generated when attempting to access invalid addresses through the ROM serial loader.&amp;nbsp; That value "x89232389" is too similar in format to others (like x56787856).&amp;nbsp; I can't find any documentation on it, so I don't know for sure but when I changed my addresses a bit I found I did have some success with reading and writing through that interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Feb 2020 16:09:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Programming-RT1050-via-serial-bootloader/m-p/848304#M1781</guid>
      <dc:creator>EdSutter</dc:creator>
      <dc:date>2020-02-26T16:09:43Z</dc:date>
    </item>
  </channel>
</rss>

