<?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: VBUS assignment to ISP_1?</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513439#M173</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rjm on Thu Oct 29 08:01:32 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; As explained above, the part enters the ISP mode via USB when ISP_1 is high and not Low.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, but under the assumption that ISP0 is low.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And - under this assumption - when the part is powered up without USB connected, it would go into the well known UART boot mode.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But that's not what I want. I have ISP_0 on hi using a pull-up. It is intended that the device starts the user program upon reset. It will automatically enter a boot mode, when no user code is present. And when both ISP-pins are hi, USB boot can still be entered from user code execution (as is documented).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Therefore, it is a quite logical choice to have both ISP-pins to high on reset. Hence my desire to assign VBus elsewhere. But when the bootloader code uses ISP_1 as VBUS detect, I have no choice, indeed. But - this way my board would never start in user code when the board is powered externally. Do I overlook something, or is this analysis OK?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 17:06:52 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T17:06:52Z</dc:date>
    <item>
      <title>VBUS assignment to ISP_1?</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513437#M171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rjm on Wed Oct 28 04:45:31 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;The user manual UM10736 states in Table 91, that ISP_1 defaults to PIO1_11. That's clear from other parts of the documentation. However, USB_VBUS is declared as movable function, and the associated register defaults to 0xFF. But this should mean that USB_VBUS is not assigned by default to a pin at all. So, the init sequence should be responsible for this. Is that correct?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another question: Why is it stated that VBUS should be assigned to the ISP_1 pin for ISP usability over USB?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;A sample schematic (the LPCXpresso eval kit with LPC1549) shows that no Pull-Up is present on ISP_1. When I would not use a USB cable, the MCU would reset in an ISP-Boot-mode.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hence I'm tempted to leave ISP_1 without any connection except a pull-up resistor (as is the case with ISP_0 in my own board, and then assign VBUS to another pin.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please clarify these issues.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:06:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513437#M171</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: VBUS assignment to ISP_1?</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513438#M172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcmunich on Thu Oct 29 06:02:57 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi rjm,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Please find my comments in-lined below.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The user manual UM10736 states in Table 91, that ISP_1 defaults to PIO1_11. That's clear from other parts of the documentation. However, USB_VBUS is declared as movable function, and the associated register defaults to 0xFF. But this should mean that USB_VBUS is not assigned by default to a pin at all. So, the init sequence should be responsible for this. Is that correct?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; Yes, the Boot code (in ROM) takes care of necessary initialization.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another question: Why is it stated that VBUS should be assigned to the ISP_1 pin for ISP usability over USB?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; Please refer the Table-89 in UM10736. The ISP_1 is used to detect the USB cable connectivity (through VBUS).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Normally the ISP_1 is low (no USB cable connected). But when the USB cable is connected, the ISP_1 goes high since the VBUS signal is high.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;A sample schematic (the LPCXpresso eval kit with LPC1549) shows that no Pull-Up is present on ISP_1. When I would not use a USB cable, the MCU would reset in an ISP-Boot-mode.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; As explained above, the part enters the ISP mode via USB when ISP_1 is high and not Low.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hence I'm tempted to leave ISP_1 without any connection except a pull-up resistor (as is the case with ISP_0 in my own board, and then assign VBUS to another pin.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; If you would like to use ISP via USB, you shouldn't connect a pull-up on ISP_1.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:06:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513438#M172</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: VBUS assignment to ISP_1?</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513439#M173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rjm on Thu Oct 29 08:01:32 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; As explained above, the part enters the ISP mode via USB when ISP_1 is high and not Low.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, but under the assumption that ISP0 is low.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And - under this assumption - when the part is powered up without USB connected, it would go into the well known UART boot mode.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But that's not what I want. I have ISP_0 on hi using a pull-up. It is intended that the device starts the user program upon reset. It will automatically enter a boot mode, when no user code is present. And when both ISP-pins are hi, USB boot can still be entered from user code execution (as is documented).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Therefore, it is a quite logical choice to have both ISP-pins to high on reset. Hence my desire to assign VBus elsewhere. But when the bootloader code uses ISP_1 as VBUS detect, I have no choice, indeed. But - this way my board would never start in user code when the board is powered externally. Do I overlook something, or is this analysis OK?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:06:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513439#M173</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:06:52Z</dc:date>
    </item>
    <item>
      <title>Re: VBUS assignment to ISP_1?</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513440#M174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcmunich on Fri Oct 30 05:56:09 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, but under the assumption that ISP0 is low.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And - under this assumption - when the part is powered up without USB connected, it would go into the well known UART boot mode.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&amp;gt; ISP0 is normally high (pulled up). Hence it won't enter the UART boot mode.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Please refer the Boot Process Flow chart in the UM for more details.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If the watchdog flag is set or valid user code is found, it will always jump to execute the code from internal flash.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Connect the ISP0 and ISP1 as shown in our LPCXpresso board schematic, link below.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.lpcware.com%2Fsystem%2Ffiles%2FLPC1549_LPCXpresso%2520v2_schem_Rev_C.pdf" rel="nofollow" target="_blank"&gt;https://www.lpcware.com/system/files/LPC1549_LPCXpresso%20v2_schem_Rev_C.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And the boot code will manage the rest, we have tested it here and it works fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:06:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/VBUS-assignment-to-ISP-1/m-p/513440#M174</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:06:52Z</dc:date>
    </item>
  </channel>
</rss>

