It just take on boot pin to mess up the boot process. If it is not powered on it still presents a load. It still affects the boot pins.
Key point…DO NOT PUT ANYTHNING on GPIO pins that share the boot function on power up. Gerald From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On Behalf Of Mike Brandon Sent: Friday, November 30, 2018 3:07 PM To: BeagleBoard <beagleboard@googlegroups.com> Subject: Re: [beagleboard] Beaglebone Black won't boot when gpio connections made Gerald, Thanks for pointing me to that information but I don't see where I am utilizing one of the 16 boot pins on the expansion header. Also, my external device that is connected to the GPIO listed above is not powered up at boot. Am I missing another key point in the reference you pointed me to? Mike On Friday, November 30, 2018 at 3:54:42 PM UTC-5, gcoley1 wrote: Yep, you are changing the boot mode of the processor. A big no no. https://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pin_Usage Gerald From: beagl...@googlegroups.com<javascript:> [mailto:beagl...@googlegroups.com<javascript:>] On Behalf Of Mike Brandon Sent: Friday, November 30, 2018 2:52 PM To: BeagleBoard <beagl...@googlegroups.com<javascript:>> Subject: [beagleboard] Beaglebone Black won't boot when gpio connections made I have a device plugged in via GPIO to the following gpio pins: 48 49 115 117 If my device is connected at boot, the BB will not boot. I am booting from eMMC. Any idea why this is occurring? I am using the attached custom overlay which is essentially the univ-emmc overlay with some modifications on GPIOs not listed above. Mike -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com<javascript:>. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/bbf65703-a19c-446f-a962-6baa15deff82%40googlegroups.com<https://groups.google.com/d/msgid/beagleboard/bbf65703-a19c-446f-a962-6baa15deff82%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com<mailto:beagleboard+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/338ac43f-50e8-4130-83d6-a4e85050a802%40googlegroups.com<https://groups.google.com/d/msgid/beagleboard/338ac43f-50e8-4130-83d6-a4e85050a802%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/178633782848495caa6ca61ffe512dde%40winhexbeus11.winus.mail. For more options, visit https://groups.google.com/d/optout.
