Yes it is allowed. The pins default to inputs after reset. Gerald
On Sat, Dec 28, 2013 at 9:57 AM, Satz Klauer <[email protected]>wrote: > Thanks. > > And just to verify my second question: When SYS_RESETn is high but the > GPIOs are not multiplexed since the firmware is not fully started: is > it allowed to have a HIGH-signal on a GPIO pint that is not already > programmed as input? > > On Thu, Dec 26, 2013 at 4:51 PM, Gerald Coley <[email protected]> > wrote: > > The reset line is roughly 10mA. When it is LOW, do not connect any > signal to > > the pins. No voltage of any kind can be driven into the pins until reset > > goes high. > > > > Gerald > > > > > > On Mon, Dec 23, 2013 at 6:05 AM, Satz Klauer <[email protected]> > > wrote: > >> > >> > >> Hi, > >> > >> just to verify some things before I order design of my capes: according > to > >> http://elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Usageit is > >> not allowed to have an input signal on any of the GPIO-pins during > power-up > >> or during boot. Resulting from that I think about using SYS_RESETn as > signal > >> to enable my capes. So my question: > >> > >> - which current can be pulled out ot SYS_RESETn / how much GPIO-inputs > can > >> I drive with this signal? > >> > >> - when SYS_RESETn is HIGH the GPIOs may not be programmed as input > >> (because firmware is not fully started at this point) but the > Cape-hardware > >> possibly sets an input signal to them (because SYS_RESETn already > enabled > >> it). Is this a problem? Can I use SYS_RESETn to enable input signals > too or > >> should I use an additional GPIO as output which enables such signals > much > >> later than SYS_RESETn would do that? > >> > >> Thanks for clarification! > >> > >> -- > >> 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 [email protected]. > >> > >> For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > > For more options, visit http://beagleboard.org/discuss > > --- > > You received this message because you are subscribed to a topic in the > > Google Groups "BeagleBoard" group. > > To unsubscribe from this topic, visit > > https://groups.google.com/d/topic/beagleboard/aLQo68EGT68/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > > [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
