Sure I can help. Reasonable rates, but I need more info. Bill(dot)pretty(at)xplornet(dot)com
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of andrew otis Sent: Saturday, June 27, 2015 12:06 PM To: [email protected] Subject: Re: [beagleboard] Need GPIO pin voltage disabled at boot Would you be able to offer expertise for compensation? I'm working on a project and this requirement must be met, and it exceeds my skillset. Please, if you're interested and can help, email me! On Sat, Jun 27, 2015 at 11:19 AM, evilwulfie <[email protected]> wrote: > you must use a tristate buffer to do this in hardware it cannot be > done in software > > > On 6/27/2015 8:14 AM, andrew otis wrote: > > I'm a n00b, but I have a requirement to make a few of my GPIO pins not > output any voltage during boot. > > I've got a new beaglebone black. > > I can disable them through the /sys/class/gpio/export just fine but > doing so in a bash script on boot leaves current through the pin for > about 4-5 seconds before it runs my script. > > So next, I looked into modifying the boot loader. I tried commenting > out the bottom section of beagle.c: > > > /* Set GPIO states before they are made outputs > writel(GPIO23 | GPIO10 | GPIO8 | GPIO2 | GPIO1, > &gpio6_base->setdataout); > writel(GPIO31 | GPIO29 | GPIO28 | GPIO22 | GPIO21 | > GPIO15 | GPIO14 | GPIO13 | GPIO12, > &gpio5_base->setdataout); */ > > /* Configure GPIOs to output > writel(~(GPIO23 | GPIO10 | GPIO8 | GPIO2 | GPIO1), &gpio6_base->oe); > writel(~(GPIO31 | GPIO29 | GPIO28 | GPIO22 | GPIO21 | > GPIO15 | GPIO14 | GPIO13 | GPIO12), &gpio5_base->oe); > */ > > dieid_num_r(); > > and recompiled and tested and there is still voltage coming from pin > 11 during boot. > > Would someone that has experience doing this at least point me in the > right direction? It would be so much appreciated! > -- > 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/d/optout. > > > -- > 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/3n-sPYdIJbA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout. ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.6037 / Virus Database: 4365/10108 - Release Date: 06/27/15 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.6037 / Virus Database: 4365/10102 - Release Date: 06/26/15 -- 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/d/optout.
