<?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 56f83xxx bootloader question in Digital Signal Controllers</title>
    <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1596351#M2672</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I saw in the documentations that it is possible to run the bootloader from the user application firmware. Anyone know how to do it?&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;</description>
    <pubDate>Thu, 09 Feb 2023 08:00:02 GMT</pubDate>
    <dc:creator>Ben</dc:creator>
    <dc:date>2023-02-09T08:00:02Z</dc:date>
    <item>
      <title>56f83xxx bootloader question</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1596351#M2672</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I saw in the documentations that it is possible to run the bootloader from the user application firmware. Anyone know how to do it?&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 08:00:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1596351#M2672</guid>
      <dc:creator>Ben</dc:creator>
      <dc:date>2023-02-09T08:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: 56f83xxx bootloader question</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1596936#M2676</link>
      <description>&lt;P&gt;Hi, Ben,&lt;/P&gt;
&lt;P&gt;On PC side, you can use blhost.exe to communicate with the bootloader on MC56F83xxx through uart.&lt;/P&gt;
&lt;P&gt;You can download blhost from the website:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/webapp/sps/download/license.jsp?colCode=blhost_2.6.7&amp;amp;appType=file1&amp;amp;DOWNLOAD_ID=null" target="_blank"&gt;https://www.nxp.com/webapp/sps/download/license.jsp?colCode=blhost_2.6.7&amp;amp;appType=file1&amp;amp;DOWNLOAD_ID=null&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Hope it can help you&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;XiangJun Rong&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 02:00:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1596936#M2676</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2023-02-10T02:00:51Z</dc:date>
    </item>
    <item>
      <title>Re: 56f83xxx bootloader question</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597709#M2677</link>
      <description>&lt;P&gt;Thanks Rong, but I mean, is it possible to access the FOPT register from my application while it is running to set the register that next reset will run the bootloader, or the only way to change the reg. value is through the sdk programming / debugging?&lt;/P&gt;</description>
      <pubDate>Sat, 11 Feb 2023 21:44:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597709#M2677</guid>
      <dc:creator>Ben</dc:creator>
      <dc:date>2023-02-11T21:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: 56f83xxx bootloader question</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597791#M2678</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;As you know that the FOPT register is loaded from the flash configuration field at address 0x40D in flash memory after Reset, so it is impossible that you write the FOPT directly in order to run from flash directly after next Reset. Instead, you have to write the FOPT location in flash configuration field.&lt;/P&gt;
&lt;P&gt;For detailed inf, pls refer to section 6.3.2 Start-up Process in the MC56F83xxxRM.pdf.&lt;/P&gt;
&lt;P&gt;In the SDK example, we provide flash_config.c and Flash_config.h, as the following screenshot, pls change the macro&lt;/P&gt;
&lt;P&gt;#define FCF_FLASH_OPTION_BYTE 0xFFU&lt;/P&gt;
&lt;P&gt;to&lt;/P&gt;
&lt;P&gt;#define FCF_FLASH_OPTION_BYTE 0x7EU&lt;/P&gt;
&lt;P&gt;The flash configuration field corresponding FOPT location will be changed.&lt;/P&gt;
&lt;P&gt;the DSC will start running from flash directly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="xiangjun_rong_0-1676256388978.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/210578i9771CFA85F8B0DE1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="xiangjun_rong_0-1676256388978.png" alt="xiangjun_rong_0-1676256388978.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;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;6.3.2 Start-up Process&lt;BR /&gt;Any of the following conditions will force the hardware to start the Bootloader:&lt;BR /&gt;• FOPT [7:6] is set to 2'b11. This forces the ROM to run out of reset.&lt;BR /&gt;• A user applications running on flash or RAM calls into the Bootloader entry point&lt;BR /&gt;address in ROM, 0x780E7 for this device, to start Bootloader execution.&lt;BR /&gt;The FOPT register determines the boot source. The FOPT register is loaded from the&lt;BR /&gt;flash configuration field at address 0x40D in flash memory. The value of&lt;BR /&gt;FOPT[7:6]&amp;amp;(~SIM_BOOT_MODE_OVERRIDE[BOOT_OVERRIDE]) determines the&lt;BR /&gt;boot option: value 11b means booting from ROM, while any other value means booting&lt;BR /&gt;from flash. Flash memory defaults to all 1s when erased, and&lt;BR /&gt;SIM_BOOT_MODE_OVERRIDE[BOOT_OVERRIDE] is 00b after power on reset, so a&lt;BR /&gt;blank chip will automatically boot to ROM. See the "FTFE_FOPT Register" section in&lt;BR /&gt;the "Chip Configuration" chapter for more details.&lt;BR /&gt;When the ROM is executed out of reset, vector fetches from the CPU are redirected to&lt;BR /&gt;the ROM's vector table in ROM memory at offset 0x07_8000. This ensures that any&lt;BR /&gt;exceptions will be handled by the ROM.&lt;BR /&gt;After the Bootloader has started, the following procedure starts bootloader operations&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope it can help you&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;XiangJun Rong&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 02:52:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597791#M2678</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2023-02-13T02:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: 56f83xxx bootloader question</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597990#M2679</link>
      <description>&lt;P&gt;in the chip RM it is written: "Multiple options for executing the bootloader either at system start-up or under&lt;BR /&gt;application control at runtime". How do activate the bootloader "under application control at runtime"?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 08:09:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597990#M2679</guid>
      <dc:creator>Ben</dc:creator>
      <dc:date>2023-02-13T08:09:32Z</dc:date>
    </item>
    <item>
      <title>Re: 56f83xxx bootloader question</title>
      <link>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597995#M2680</link>
      <description>&lt;P&gt;sorry, I did not see your last answer below. thank you for the support and for the detailed answer.&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 08:15:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Digital-Signal-Controllers/56f83xxx-bootloader-question/m-p/1597995#M2680</guid>
      <dc:creator>Ben</dc:creator>
      <dc:date>2023-02-13T08:15:41Z</dc:date>
    </item>
  </channel>
</rss>

