halfbrain, > - If I used the EMMC pins I would need to boot from SD Card everytime?
Correct. You'll use the beaglebone white/sd card images. The beaglebone will automatically boot from the SD card since it wont be able to find the EMMC. > - And if I used the HMDI Pins it wouldn't be possible to connect the uHdmi Cable to the bbb and connect some screen to it? Because they are connected to the same pins? No HDMI if you disable HDMI, but you can still ssh/vnc in. The way I'm suggesting is the proper way to disable built in overlays that are loaded at boot. For some reason, only the hdmi and emmc interfaces are added as overlays that can be disabled at boot. i2c and the likes are hard coded in the dts file. Why? I don't know. Maybe there's a good reason, probably not. --Brandon On Thu, Sep 4, 2014 at 7:28 AM, halfbrain <adrian.mitev...@gmail.com> wrote: > Thanks for your Answer Brandon > > Just a few questions for my Information: > - If I used the EMMC pins I would need to boot from SD Card everytime? > - And if I used the HMDI Pins it wouldn't be possible to connect the uHdmi > Cable to the bbb and connect some screen to it? Because they are connected > to the same pins? > > The way you unallocated the pins and the way john recommend me to > unallocate the pins seem to be very different. To be honest I don't > understand the difference of the two ways. Which way is the easier one and > can this way be used to unallocate every pin on the bbb? I just wan't to > make things trickier than they are :-) But i'm very thankful for your help > so far ;-) > > Am Mittwoch, 3. September 2014 22:00:16 UTC+2 schrieb Brandon I: > >> halfbrain, I forgot to mention, you should tie the eMMC cmd and clock >> pins low on P8.20 and P8.21, as suggested by the wiki: http://elinux.org/ >> Beagleboard:BeagleBoneBlack#Onboard_eMMC >> >> On Wednesday, September 3, 2014 12:58:09 PM UTC-7, Brandon I wrote: >>> >>> halfbrain, >>> >>> If you're using angstrom or debian, you can disable the emmc by adding >>> this to the optargs in uEnv.txt on the usb mass storage >>> partition: capemgr.disable_partno=BB-BONE-EMMC-2G >>> >>> If you're not using hdmi, you can free up those >>> too: capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT- >>> HDMIN,BB-BONE-EMMC-2G >>> >>> >>> On Saturday, August 23, 2014 1:11:22 AM UTC-7, halfbrain wrote: >>>> >>>> Would be nice if you could explain how to disable eMMC on debian. I ran >>>> out of GPIO's in my project. Tried to use P9_19 and P9_20 (both I2C's) in >>>> the device tree overlay but since i did that the overlay doesn't work >>>> correctly anymore. >>>> >>>> Am Sonntag, 18. Mai 2014 22:19:16 UTC+2 schrieb john3909: >>>>> >>>>> >>>>> From: Dhruv Vyas <dhruv....@gmail.com> >>>>> Reply-To: <beagl...@googlegroups.com> >>>>> Date: Sunday, May 18, 2014 at 2:42 AM >>>>> To: <beagl...@googlegroups.com> >>>>> Subject: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ? >>>>> >>>>> Hello, >>>>> >>>>> I recently started working on my BBB A6A. I went through necessary >>>>> getting started guides and it works like a charm. Now as a part of my >>>>> project, I need to use some of the GPIOs on P8/P9 header. While googling >>>>> how to use them as a GPIO, and how to set pinmux and etc, I went through >>>>> this guide. http://derekmolloy.ie/gpios- >>>>> on-the-beaglebone-black-using-device-tree-overlays/ and he explained >>>>> everything very clearly. >>>>> >>>>> Now my question is : is there any way i can use allocated pins as >>>>> GPIOs other than available pins ? If yes, how ? If no, why ? >>>>> >>>>> For example, P9_19 and P9_20 are Allocated to (Group: >>>>> pinmux_i2c2_pins) and hence it can not be used as GPIOs ? >>>>> >>>>> If pins are also connected to circuitry on the board that cannot be >>>>> disabled then you cannot use those pins for GPIO. For example, pins used >>>>> for the eMMC can be used for GPIO as long as eMMC is disabled. Same for >>>>> LCD >>>>> pins, but then you cannot use LCD or HDMI. I2C2 isn't connected to other >>>>> circuity on the board so you can use it for GPIO. >>>>> >>>>> Regards, >>>>> John >>>>> >>>>> >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> >>>>> -- >>>>> 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. >>>>> 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/amEtmzQoyyc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > 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. For more options, visit https://groups.google.com/d/optout.
