<?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: LPC4350 Boot Pins P2_9, P2_8, P1_2, P1_1 in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1469914#M49071</link>
    <description>&lt;P&gt;Hello ,&lt;/P&gt;
&lt;P&gt;1)You said "&lt;SPAN&gt;If we reduce the 10K pull up resistor to about 7.5K then P1_1 is held high enough to boot correctly every time.&amp;nbsp;&lt;/SPAN&gt;", so how about use this method.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2)There is another suggestion from other thread， how about it:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;In "ancient" times, SBC and microcomputer designs used tristate line buffers or multiplexers with separate /OE pin to decouple the MCU/processor.&amp;nbsp; Not sure if that would be an option for you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/LPC-Microcontrollers/LPC54628-a-serious-problem-with-ISP-boot-pins-shared-with-SDRAM/m-p/1459255#M48793" target="_blank"&gt;https://community.nxp.com/t5/LPC-Microcontrollers/LPC54628-a-serious-problem-with-ISP-boot-pins-shared-with-SDRAM/m-p/1459255#M48793&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jun 2022 09:53:48 GMT</pubDate>
    <dc:creator>Alice_Yang</dc:creator>
    <dc:date>2022-06-07T09:53:48Z</dc:date>
    <item>
      <title>LPC4350 Boot Pins P2_9, P2_8, P1_2, P1_1</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1468919#M49029</link>
      <description>&lt;P&gt;We are using the LPC4350FET256 in a design which has been in production for several years and we have shipped several thousand devices.&amp;nbsp; The design normally boots from SPIFI but also has a jumper option to allow booting in DFU mode over USB0 for updating the SPIFI firmware image.&amp;nbsp; We recently received a return unit that would not boot up properly in SPIFI or DFU mode.&amp;nbsp; After examining the board, I determined that P1_1 was not being properly interpreted as being in a high logic level at reset which caused an unexpected boot mode to be entered.&amp;nbsp; The board uses a 10K resistor to pull P1_1 to 3.3V.&amp;nbsp; The user manual indicates that the internal pin pull up resistor is also enabled by default at reset which should reinforce the high logic level.&amp;nbsp; We have noticed that if we leave the board powered down for several hours and then power it up, sometimes P1_1 will follow the 3.3V supply up and everything works fine during power on.&amp;nbsp; If you power cycle the board multiple times after that with relatively short periods of no power, P1_1 seems to be held down below the high threshold and the board doesn't boot properly.&amp;nbsp; If we reduce the 10K pull up resistor to about 7.5K then P1_1 is held high enough to boot correctly every time.&amp;nbsp; We are using 2 external SRAM chips in this design so P1_1 is also used for the address bus EMC_A6 signal but that is all that P1_1 is connected to.&amp;nbsp; We have also noticed that the P2_8 signal that we feed from the jumper to select normal or DFU mode also exhibits this same issue.&amp;nbsp; A 10K resistor is also used in this case.&amp;nbsp; Reducing the 10K will solve this problem as well.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As I mentioned before, we have shipped several thousand of these boards over the past 6 years or so.&amp;nbsp; To my knowledge, this is the first time we have seen this issue.&amp;nbsp; Our customer says that they have others behaving the same way periodically.&amp;nbsp; I will try to receive these boards and analyze them also if possible.&amp;nbsp; We could probably fix this one board by changing resistor values, but other good boards do not show that we are even close to being marginal.&amp;nbsp; P1_1 follows the power supply all the way up to 3.3 volts on power up.&lt;/P&gt;&lt;P&gt;I have attached a zip file with several scope pictures which illustrate this issue on the bad board as well as one pic from a good board.&lt;/P&gt;&lt;P&gt;Any ideas on what may be going on here or suggestions for further analysis?&amp;nbsp; We have not attempted to cut traces going to the SRAM yet but may try this to isolate the issue to the LPC4350.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Greg Dunn&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2022 22:36:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1468919#M49029</guid>
      <dc:creator>gregdunn</dc:creator>
      <dc:date>2022-06-03T22:36:42Z</dc:date>
    </item>
    <item>
      <title>Re: LPC4350 Boot Pins P2_9, P2_8, P1_2, P1_1</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1469914#M49071</link>
      <description>&lt;P&gt;Hello ,&lt;/P&gt;
&lt;P&gt;1)You said "&lt;SPAN&gt;If we reduce the 10K pull up resistor to about 7.5K then P1_1 is held high enough to boot correctly every time.&amp;nbsp;&lt;/SPAN&gt;", so how about use this method.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2)There is another suggestion from other thread， how about it:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;In "ancient" times, SBC and microcomputer designs used tristate line buffers or multiplexers with separate /OE pin to decouple the MCU/processor.&amp;nbsp; Not sure if that would be an option for you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/LPC-Microcontrollers/LPC54628-a-serious-problem-with-ISP-boot-pins-shared-with-SDRAM/m-p/1459255#M48793" target="_blank"&gt;https://community.nxp.com/t5/LPC-Microcontrollers/LPC54628-a-serious-problem-with-ISP-boot-pins-shared-with-SDRAM/m-p/1459255#M48793&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 09:53:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1469914#M49071</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2022-06-07T09:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: LPC4350 Boot Pins P2_9, P2_8, P1_2, P1_1</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1469983#M49084</link>
      <description>&lt;P&gt;1) The reason that I don't want to just change to a 7.5K pull-up is because the LPC4350 documentation specifies that the P1_1 line should have an internal pull-up resistor enabled by default at reset which should allow the line to easily be pulled up to 3.3 volts at the end of reset.&amp;nbsp; The spec sheet shows -62uA typical for the pull-up current.&amp;nbsp; &amp;nbsp;All other boards we have tested show that P1_1 follows the 3.3 volt supply ALL THE WAY up on power up with the 10K.&amp;nbsp; Additionally these boards carry a UL approval for hazardous area installation and the bill of material is locked to the approved design.&amp;nbsp; Any design changes require significant time and cost for re-certification through UL.&amp;nbsp; This is the first board out of several thousand that we have seen this issue on.&amp;nbsp; I am mostly inquiring to see if there is some kind of known failure mode in the LPC4350 processor which could cause this.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) In this case, the boot pins (P1_1, P1_2, P2_8 and P2_9) are all shared and used as EMC address lines and are connected to the SRAM address inputs.&amp;nbsp; The SRAM chip should not get an any mode where these lines would be driven high or low by the SRAM, they are high impedance inputs to the SRAM.&amp;nbsp; In addition, we have circuitry that disables the SRAM CE input during reset.&amp;nbsp; I am not sure how a tri-state buffer would help in this case.&amp;nbsp; The SRAM chip seems to function normally when the board is forced to boot in the application.&amp;nbsp; We don't suspect the SRAM as being the issue.&amp;nbsp; As we proceed with our troubleshooting, we will probably cut the traces going to the SRAM just to rule it out completely as the cause.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 12:24:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1469983#M49084</guid>
      <dc:creator>gregdunn</dc:creator>
      <dc:date>2022-06-07T12:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: LPC4350 Boot Pins P2_9, P2_8, P1_2, P1_1</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1472169#M49126</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;OK , also recommend you&amp;nbsp;&lt;SPAN&gt;cut the traces going to the SRAM&amp;nbsp; , pull up ISP pins to check.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Alice&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 09:44:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4350-Boot-Pins-P2-9-P2-8-P1-2-P1-1/m-p/1472169#M49126</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2022-06-10T09:44:58Z</dc:date>
    </item>
  </channel>
</rss>

