[beagleboard] Device Tree Overlay at Boottime
Hi there
My goal is to connect 16 PEC11 Encoders to the BeagleBone Black. I'm using
this Library https://github.com/guyc/py-gaugette. And I'm running the
newest debian on my beaglebone.
I created a new device tree overlay as Derek Moloy explained in this video
https://www.youtube.com/watch?v=wui_wU1AeQc setting my used gpios to mode7
and I've also read this
https://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/device-tree-overlays
article about exporting device tree overlays. But I don't know how to
manipulate the uEnv.txt correctly so that at Boottime my BBB uses only my
DTO.
This is my uEnv.txt:
##Video: Uncomment to override:
##see:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt
#kms_force_mode=video=HDMI-A-1:1024x768@60e
##Enable systemd
systemd=quiet init=/lib/systemd/systemd
##BeagleBone Cape Overrides
##BeagleBone Black:
##Disable HDMI/eMMC
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
##Disable HDMI
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
##Audio Cape (needs HDMI Audio disabled)
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI
#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02
##Example
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=
##WIP: v3.14+ capes..
#cape=ttyO1
#cape=
##note: the eMMC flasher script relies on the next line
mmcroot=UUID=fa05f7e9-337d-4eb2-bb58-5e2eee8baac7 ro
mmcrootfstype=ext4 rootwait fixrtc
##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
console=ttyO0,115200n8
kernel_file=zImage
initrd_file=initrd.img
loadaddr=0x8200
initrd_addr=0x8808
fdtaddr=0x8800
initrd_high=0x
fdt_high=0x
loadkernel=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadinitrd=load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file};
setenv initrd_size ${filesize}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
loadfiles=run loadkernel; run loadinitrd; run loadfdt
mmcargs=setenv bootargs console=tty0 console=${console} ${optargs}
${cape_disable} ${cape_enable} ${kms_force_mode} root=${mmcroot}
rootfstype=${mmcrootfsty$
uenvcmd=run loadfiles; run mmcargs; bootz ${loadaddr}
${initrd_addr}:${initrd_size} ${fdtaddr}
capemgr.enable_partno=DM-GPIO-Test
#
I'dont know where excalty i should add capemgr.enable_partno=DM-GPIO-Test. And
do I also have to disable any other DTO?
My Device-Tree-Overlay:
/*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Purpose License Version 2 as
* published by the Free Software Foundation
*
* Original from:
github.com/jadonk/validation-scripts/blob/master/test-capemgr/
*
* Modified by Derek Molloy for the example on www.derekmolloy.ie
* that maps GPIO pins for the example
*/
/dts-v1/;
/plugin/;
/{
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "DM-GPIO-Test";
version = "00A0";
fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
pinctrl_test: DM_GPIO_Test_Pins {
pinctrl-single,pins = <
0x090 0x17 /* P8_07MODE7 */
0x094 0x17 /* P8_08MODE7 */
0x09c 0x17 /* P8_09MODE7 */
0x098 0x17 /* P8_10MODE7 */
0x034 0x17 /* P8_11MODE7 */
0x030 0x17 /* P8_12MODE7 */
0x024 0x17 /* P8_13MODE7 */
0x028 0x17 /* P8_14MODE7 */
0x03c 0x17 /* P8_15MODE7 */
0x038 0x17 /* P8_16MODE7 */
0x02c 0x17 /* P8_17MODE7 */
0x08c 0x17 /* P8_18MODE7 */
0x020 0x17 /* P8_19MODE7 */
0x07c 0x17 /* P8_26MODE7 */
0x070 0x17 /* P9_11MODE7 */
0x078 0x17 /* P9_12MODE7 */
0x074 0x17 /* P9_13MODE7 */
0x048 0x17 /* P9_14MODE7 */
0x040 0x17 /* P9_15MODE7 */
0x04c 0x17 /* P9_16MODE7 */
0x15c 0x17 /* P9_17MODE7 */
0x158 0x17 /* P9_18MODE7 */
0x154 0x17 /* P9_21MODE7 */
Re: [beagleboard] Device Tree Overlay at Boottime
thanks a lot Robert you made my day ;-)
For those who have the same problem as i had:
you have to open the file* /etc/default/capemgr*
and add
*CAPE=DM-GPIO-TEST *
restart your bbb and your Device Tree Overlay will be loaded at Boot
Am Donnerstag, 21. August 2014 13:39:34 UTC+2 schrieb RobertCNelson:
>
> On Thu, Aug 21, 2014 at 4:36 AM, halfbrain > wrote:
> > Hi there
> >
> > My goal is to connect 16 PEC11 Encoders to the BeagleBone Black. I'm
> using
> > this Library https://github.com/guyc/py-gaugette. And I'm running the
> newest
> > debian on my beaglebone.
> >
> > I created a new device tree overlay as Derek Moloy explained in this
> video
> > https://www.youtube.com/watch?v=wui_wU1AeQc setting my used gpios to
> mode7
> > and I've also read this
> >
> https://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/device-tree-overlays
>
> > article about exporting device tree overlays. But I don't know how to
> > manipulate the uEnv.txt correctly so that at Boottime my BBB uses only
> my
> > DTO.
> >
> > This is my uEnv.txt:
> >
> > ##Video: Uncomment to override:
> > ##see:
> >
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt
>
> > #kms_force_mode=video=HDMI-A-1:1024x768@60e
> >
> > ##Enable systemd
> > systemd=quiet init=/lib/systemd/systemd
> >
> > ##BeagleBone Cape Overrides
> >
> > ##BeagleBone Black:
> > ##Disable HDMI/eMMC
> >
> #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
>
>
> >
> > ##Disable HDMI
> > #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> >
> > ##Audio Cape (needs HDMI Audio disabled)
> > #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI
> > #cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02
> >
> > ##Example
> > #cape_disable=capemgr.disable_partno=
> > #cape_enable=capemgr.enable_partno=
> >
> > ##WIP: v3.14+ capes..
> > #cape=ttyO1
> > #cape=
> >
> > ##note: the eMMC flasher script relies on the next line
> > mmcroot=UUID=fa05f7e9-337d-4eb2-bb58-5e2eee8baac7 ro
> > mmcrootfstype=ext4 rootwait fixrtc
> >
> > ##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
> > console=ttyO0,115200n8
> >
> > kernel_file=zImage
> > initrd_file=initrd.img
> >
> > loadaddr=0x8200
> > initrd_addr=0x8808
> > fdtaddr=0x8800
> >
> > initrd_high=0x
> > fdt_high=0x
> >
> > loadkernel=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
> > loadinitrd=load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file};
> > setenv initrd_size ${filesize}
> > loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
> >
> > loadfiles=run loadkernel; run loadinitrd; run loadfdt
> > mmcargs=setenv bootargs console=tty0 console=${console} ${optargs}
> > ${cape_disable} ${cape_enable} ${kms_force_mode} root=${mmcroot}
> > rootfstype=${mmcrootfsty$
> >
> > uenvcmd=run loadfiles; run mmcargs; bootz ${loadaddr}
> > ${initrd_addr}:${initrd_size} ${fdtaddr}
> > capemgr.enable_partno=DM-GPIO-Test
> > #
> >
> > I'dont know where excalty i should add
> capemgr.enable_partno=DM-GPIO-Test.
> > And do I also have to disable any other DTO?
>
> Explained here:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Loading_custom_capes
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
--
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.
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
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 > > Reply-To: > > Date: Sunday, May 18, 2014 at 2:42 AM > To: > > 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 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.
[beagleboard] Re: pin mode, kernel 3.8
Theres a similar thread about that I started a few days ago about device tree overlays which u need to use to change the pin modes. https://groups.google.com/forum/embed/?place=forum/beagleboard&showsearch=true&showpopout=true&showtabs=true&hideforumtitle=true&parenturl=http%3A%2F%2Fbeagleboard.org%2FCommunity%2FForums#!category-topic/beagleboard/newbies/r9vxklO0Etk I hope this helps you Am Freitag, 29. August 2014 12:15:06 UTC+2 schrieb Benedek: > > > Hi, > > I updated the newest image on my BBB, but I didn't check before, if > everything works with it. > So, do you know, if I can change the mode of pins using the kernel 3.8? > > Secondly, does the pinmode function works in bonescript with kernel 3.8? > > Thanks, > Benedek > -- 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.
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
how do u use the i2c2 pins? it doesn't work on my bbb if i only change the pinmode to mode 7 in my device tree. have u done additional changes or something like that elsewhere? Am Montag, 19. Mai 2014 12:20:03 UTC+2 schrieb Dhruv Vyas: > > Thanks John. Got it cleared. :) > > On Monday, May 19, 2014 1:49:16 AM UTC+5:30, john3909 wrote: >> >> >> From: Dhruv Vyas >> Reply-To: >> Date: Sunday, May 18, 2014 at 2:42 AM >> To: >> 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 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.
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
I'm using Derek Molloys device Tree overlays and I'm running debian... I
can't find the folder on my bbb .
But I found the "am335x-bone-common.dtsi
<https://github.com/derekmolloy/boneDeviceTree/blob/master/DTSource3.8.13/am335x-bone-common.dtsi>
" in
https://github.com/derekmolloy/boneDeviceTree/tree/master/DTSource3.8.13
which I have on my bbb. I've commented out the section you mentioned but
nothing changes. Without using or declaring the I2c2 pins in my Device Tree
Overlay I'm able to use all unallocated pins as GPIO Inputs as I declared
them in my Device Tree Overlay.
Did i change the wrong am335x-bone-common.dtsi
<https://github.com/derekmolloy/boneDeviceTree/blob/master/DTSource3.8.13/am335x-bone-common.dtsi>.?
Is there another one elsewhere on the debian distribution or do i have to
copy the changed file into a specific folder?
Am Sonntag, 31. August 2014 20:59:21 UTC+2 schrieb john3909:
>
>
> From: halfbrain >
> Reply-To: "beagl...@googlegroups.com " <
> beagl...@googlegroups.com >
> Date: Sunday, August 31, 2014 at 2:30 AM
> To: "beagl...@googlegroups.com " >
> Subject: Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
>
> how do u use the i2c2 pins? it doesn't work on my bbb if i only change the
> pinmode to mode 7 in my device tree. have u done additional changes or
> something like that elsewhere?
>
> If you look at /arch/arm/boot/dts/am335x-bone-common.dtsi you will see the
> i2c2 definition:
>
> &i2c2 { status = "okay"; pinctrl-names = "default"; pinctrl-0 =
> <&i2c2_pins>; clock-frequency = <10>; cape_eeprom0: cape_eeprom0@54 {
> compatible = "at,24c256"; reg = <0x54>; }; cape_eeprom1: cape_eeprom1@55 {
> compatible = "at,24c256"; reg = <0x55>; }; cape_eeprom2: cape_eeprom2@56 {
> compatible = "at,24c256"; reg = <0x56>; }; cape_eeprom3: cape_eeprom3@57 {
> compatible = "at,24c256"; reg = <0x57>; };};The line “pinctrl-0 =
> <&i2c2_pins>;” refers to the i2cs_pins label in the pinmux section:
>
> i2c2_pins: pinmux_i2c2_pins {
> pinctrl-single,pins = <
> 0x178 0x73 /* uart1_ctsn.i2c2_sda, SLEWCTRL_SLOW | INPUT_PULLUP | MODE3 */
> 0x17c 0x73 /* uart1_rtsn.i2c2_scl, SLEWCTRL_SLOW | INPUT_PULLUP | MODE3 */
> >;
> };
>
> So, as you can see, i2c2 is used to identify the capes plugged into the
> BBB. If you don’t need this feature, simply remove or comment out this
> section and then change the i2c2 pins to gpio pins.
>
> Regards,
> John
>
>
> Am Montag, 19. Mai 2014 12:20:03 UTC+2 schrieb Dhruv Vyas:
>>
>> Thanks John. Got it cleared. :)
>>
>> On Monday, May 19, 2014 1:49:16 AM UTC+5:30, john3909 wrote:
>>>
>>>
>>> From: Dhruv Vyas
>>> Reply-To:
>>> Date: Sunday, May 18, 2014 at 2:42 AM
>>> To:
>>> 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 fro
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
Thanks for your quick responses always.
I've tried the Instructions to build the Kernel
git clone https://github.com/RobertCNelson/bb-kernel.git
cd bb-kernel/
git checkout origin/am33x-v3.8 -b tmp
but if use the command ./build_kernel.sh . i get this message after the
"resolving deltas process". I've tried several times but it always freezes
at 96%. Do you have any Idea what went wrong?
this is what i get in the commandshell:
root@beaglebone:/bb-kernel# ./build_kernel.sh
+ Detected build host [Debian GNU/Linux 7.5 (wheezy)]
+ host: [armv7l]
+ git HEAD commit: [e496a19d1fed586a7e82c3cd74f0571491a526ca]
-
scripts/gcc: Using: gcc (Debian 4.6.3-14) 4.6.3
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
CROSS_COMPILE=
-
scripts/git: LINUX_GIT not defined in system.sh
cloning https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
into default location: /bb-kernel/ignore/linux-src
Cloning into '/bb-kernel/ignore/linux-src'...
remote: Counting objects: 3758162, done.
remote: Compressing objects: 100% (567907/567907), done.
remote: Total 3758162 (delta 3168580), reused 3749734 (delta 3160289)
Receiving objects: 100% (3758162/3758162), 794.38 MiB | 1.37 MiB/s, done.
error: index-pack died of signal 968580)
fatal: index-pack failed
root@beaglebone:/bb-kernel#
Am Montag, 1. September 2014 17:39:11 UTC+2 schrieb john3909:
>
>
> From: halfbrain >
> Reply-To: "beagl...@googlegroups.com " <
> beagl...@googlegroups.com >
> Date: Monday, September 1, 2014 at 8:23 AM
> To: "beagl...@googlegroups.com " >
> Subject: Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
>
> I'm using Derek Molloys device Tree overlays and I'm running debian... I
> can't find the folder on my bbb .
>
> But I found the "am335x-bone-common.dtsi
> <https://github.com/derekmolloy/boneDeviceTree/blob/master/DTSource3.8.13/am335x-bone-common.dtsi>
> " in
> https://github.com/derekmolloy/boneDeviceTree/tree/master/DTSource3.8.13
> which I have on my bbb. I've commented out the section you mentioned but
> nothing changes. Without using or declaring the I2c2 pins in my Device Tree
> Overlay I'm able to use all unallocated pins as GPIO Inputs as I declared
> them in my Device Tree Overlay.
>
> Did i change the wrong am335x-bone-common.dtsi
> <https://github.com/derekmolloy/boneDeviceTree/blob/master/DTSource3.8.13/am335x-bone-common.dtsi>.?
>
> Is there another one elsewhere on the debian distribution or do i have to
> copy the changed file into a specific folder?
>
> You need to follow:
>
>
> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
>
> After the kernel has built, you will see a KERNEL folder which includes
> the complete Linux Kernel. In that folder, go to /arch/arm/boot/dts and
> edit the am335x-bone-common.dtsi file. After that, return to the bb-kernel
> folder and run tools/rebuild.sh script. The build results will be in the
> deploy folder which you need to copy to your sdcard/“nfs folder”.
>
> Regards,
> John
>
>
>
> Am Sonntag, 31. August 2014 20:59:21 UTC+2 schrieb john3909:
>>
>>
>> From: halfbrain
>> Reply-To: "beagl...@googlegroups.com"
>> Date: Sunday, August 31, 2014 at 2:30 AM
>> To: "beagl...@googlegroups.com"
>> Subject: Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
>>
>> how do u use the i2c2 pins? it doesn't work on my bbb if i only change
>> the pinmode to mode 7 in my device tree. have u done additional changes or
>> something like that elsewhere?
>>
>> If you look at /arch/arm/boot/dts/am335x-bone-common.dtsi you will see
>> the i2c2 definition:
>>
>> &i2c2 { status = "okay"; pinctrl-names = "default"; pinctrl-0 =
>> <&i2c2_pins>; clock-frequency = <10>; cape_eeprom0: cape_eeprom0@54 {
>> compatible = "at,24c256"; reg = <0x54>; }; cape_eeprom1: cape_eeprom1@55
>> { compatible = "at,24c256"; reg = <0x55>; }; cape_eeprom2:
>> cape_eeprom2@56 { compatible = "at,24c256"; reg = <0x56>; };
>> cape_eeprom3: cape_eeprom3@57 { compatible = "at,24c256"; reg = <0x57>;
>> };};The line “pinctrl-0 = <&i2c2_pins>;” refers to the i2cs_pins label
>> in the pinmux section:
>>
>> i2c2_pins: pinmux_i2c2_pins {
>> pinctrl-single,pins = &l
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
Hi John I always get this even after reflashing my whole bbb with Debian. root@beaglebone:/home/debian/Desktop/bb-kernel# ./build_kernel.sh + Detected build host [Debian GNU/Linux 7.5 (wheezy)] + host: [armv7l] + git HEAD commit: [e496a19d1fed586a7e82c3cd74f0571491a526ca] - scripts/gcc: Using: gcc (Debian 4.6.3-14) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. - CROSS_COMPILE= - scripts/git: LINUX_GIT not defined in system.sh cloning https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git into default location: /home/debian/Desktop/bb-kernel/ignore/linux-src Cloning into '/home/debian/Desktop/bb-kernel/ignore/linux-src'... remote: Counting objects: 3758531, done. remote: Compressing objects: 100% (568127/568127), done. remote: Total 3758531 (delta 3168892), reused 3749886 (delta 3160438) Receiving objects: 100% (3758531/3758531), 794.38 MiB | 1.43 MiB/s, done. error: index-pack died of signal 968892) fatal: index-pack failed root@beaglebone:/home/debian/Desktop/bb-kernel# Do you have any Idea what went wrong or what could be wrong with my bbb. I tried the whole process several times and it took a very long everytime espacially the resolving Deltas process. And it always ends up with this Error. What am I doing wrong? Isn't there an easier way to do that? In my project I got 16 PEC11 Encoders that means I need 32 GPIO's. I already got 15 so i just need 2 more. Am Dienstag, 2. September 2014 19:12:40 UTC+2 schrieb john3909: > > > From: halfbrain > > Reply-To: "beagl...@googlegroups.com " < > beagl...@googlegroups.com > > Date: Tuesday, September 2, 2014 at 9:09 AM > To: "beagl...@googlegroups.com " > > Subject: Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ? > > Thanks for your quick responses always. > I've tried the Instructions to build the Kernel > git clone https://github.com/RobertCNelson/bb-kernel.git > cd bb-kernel/ > > git checkout origin/am33x-v3.8 -b tmp > > You need to be building this on your desktop, not on your BBB. > > Regards, > John > > > > > > > but if use the command ./build_kernel.sh . i get this message after the > "resolving deltas process". I've tried several times but it always freezes > at 96%. Do you have any Idea what went wrong? > > this is what i get in the commandshell: > > root@beaglebone:/bb-kernel# ./build_kernel.sh > + Detected build host [Debian GNU/Linux 7.5 (wheezy)] > + host: [armv7l] > + git HEAD commit: [e496a19d1fed586a7e82c3cd74f0571491a526ca] > - > scripts/gcc: Using: gcc (Debian 4.6.3-14) 4.6.3 > Copyright (C) 2011 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > - > CROSS_COMPILE= > - > scripts/git: LINUX_GIT not defined in system.sh > cloning https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > into default location: /bb-kernel/ignore/linux-src > Cloning into '/bb-kernel/ignore/linux-src'... > remote: Counting objects: 3758162, done. > remote: Compressing objects: 100% (567907/567907), done. > remote: Total 3758162 (delta 3168580), reused 3749734 (delta 3160289) > Receiving objects: 100% (3758162/3758162), 794.38 MiB | 1.37 MiB/s, done. > error: index-pack died of signal 968580) > fatal: index-pack failed > root@beaglebone:/bb-kernel# > > > > Am Montag, 1. September 2014 17:39:11 UTC+2 schrieb john3909: >> >> >> From: halfbrain >> Reply-To: "beagl...@googlegroups.com" >> Date: Monday, September 1, 2014 at 8:23 AM >> To: "beagl...@googlegroups.com" >> Subject: Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ? >> >> I'm using Derek Molloys device Tree overlays and I'm running debian... I >> can't find the folder on my bbb . >> >> But I found the "am335x-bone-common.dtsi >> <https://github.com/derekmolloy/boneDeviceTree/blob/master/DTSource3.8.13/am335x-bone-common.dtsi> >> " in >> https://github.com/derekmolloy/boneDeviceTree/tree/master/DTSource3.8.13 >> which I have on my bbb. I've commented out the section you mentioned but >> nothing changes. Without using or declaring the I2c2 pins in my Device Tree >> Overlay I'm able to use all unallocated pins as GPIO Inputs as I decl
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
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 >>>> Reply-To: >>>> Date: Sunday, May 18, 2014 at 2:42 AM >>>> To: >>>> 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 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.
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
What ran out of space the bbb? How do I use an x86desktop...btw whats and x86desktop :-)? a 32bit Computer? I'm sshing with Putty via Network from my Windows 7 64bit Pc. Is that a problem? Doesn't the whole process run on the bbb? Am Donnerstag, 4. September 2014 16:25:25 UTC+2 schrieb RobertCNelson: > > > > > On Thu, Sep 4, 2014 at 9:18 AM, halfbrain > wrote: > >> Hi John >> >> I always get this even after reflashing my whole bbb with Debian. >> >> root@beaglebone:/home/debian/Desktop/bb-kernel# ./build_kernel.sh >> >> + Detected build host [Debian GNU/Linux 7.5 (wheezy)] >> + host: [armv7l] >> + git HEAD commit: [e496a19d1fed586a7e82c3cd74f0571491a526ca] >> - >> scripts/gcc: Using: gcc (Debian 4.6.3-14) 4.6.3 >> Copyright (C) 2011 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> - >> CROSS_COMPILE= >> - >> scripts/git: LINUX_GIT not defined in system.sh >> cloning >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git into >> default location: /home/debian/Desktop/bb-kernel/ignore/linux-src >> Cloning into '/home/debian/Desktop/bb-kernel/ignore/linux-src'... >> remote: Counting objects: 3758531, done. >> remote: Compressing objects: 100% (568127/568127), done. >> remote: Total 3758531 (delta 3168892), reused 3749886 (delta 3160438) >> Receiving objects: 100% (3758531/3758531), 794.38 MiB | 1.43 MiB/s, done. >> error: index-pack died of signal 968892) >> fatal: index-pack failed >> root@beaglebone:/home/debian/Desktop/bb-kernel# >> > > Probably ran out of space. Realistically, just use an x86 desktop to run > the script. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- 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.
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
Ok... if i get that correctly i should ssh into the bbb from a linux pc? I'd like to do a project that needs 16 PCE-11 Encoders to change different parameter in a Pythonscript. I already got 15 GPIOs with the DeviceTree Overlay i did for the unallocated Pins but I need 2 more Pins. So i somehow would like to use some of the allocated Pins. But it seems more complicated than i thought. And to be honest i don't have any Idea what excatly I'm doing with allocated Pins, I just follow the Instructions here ;-) Am Donnerstag, 4. September 2014 21:09:50 UTC+2 schrieb William Hermans: > > What is wrong is that you're doing this on your bbb. You should be doing > this on a cross compile i386 PC. > > What is it you're trying to do ? > > > On Thu, Sep 4, 2014 at 5:46 AM, > wrote: > >> Hi John >> >> >> Sorry for asking you again but it still doesnt work :-( >> >> I've tried several times to build the kernel, also in the Desktop Folder. >> Yesterday i destroyed my image somehow :-). I reflashed the BBB again with >> the Debian form my uSD Card and started right with the Kernel building >> without doing anything else before except the >> sudo apt-get update >> sudo apt-get install bc lzma lzop libncurses5-dev >> >> which are necessary... >> >> but i get the same error everytime : >> >> >> root@beaglebone:/home/debian/Desktop/bb-kernel# ./build_kernel.sh >> + Detected build host [Debian GNU/Linux 7.5 (wheezy)] >> + host: [armv7l] >> + git HEAD commit: [e496a19d1fed586a7e82c3cd74f0571491a526ca] >> `/home/debian/Desktop/bb-kernel/system.sh.sample' -> >> `/home/debian/Desktop/bb-kernel/system.sh' >> >> - >> scripts/gcc: Using: gcc (Debian 4.6.3-14) 4.6.3 >> Copyright (C) 2011 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> - >> CROSS_COMPILE= >> - >> scripts/git: LINUX_GIT not defined in system.sh >> cloning >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git into >> default location: /home/debian/Desktop/bb-kernel/ignore/linux-src >> Cloning into '/home/debian/Desktop/bb-kernel/ignore/linux-src'... >> remote: Counting objects: 3758531, done. >> remote: Compressing objects: 100% (562572/562572), done. >> remote: Total 3758531 (delta 3168898), reused 3755444 (delta 3165993) >> Receiving objects: 100% (3758531/3758531), 793.01 MiB | 1.78 MiB/s, done. >> error: index-pack died of signal 968898) >> fatal: index-pack failed >> root@beaglebone:/home/debian/Desktop/bb-kernel# >> >> the whole process also takes very long espacially the resolving deltas >> process >> >> do you have any idea what I'm doing wrong or whats wrong with my bbb. I'm >> running my bbb over ssh with putty and without uSD Card. >> >> What am I doing excatly by following your Instructions? I mean i don't >> have any idea I'm just following your Instructions. Isn't there an easier >> more newbie-like way? In my Project I need to connect 16 PEC11-Encoders. >> That means 32 GPIOs. I already got 30 so I just need to more but it seems >> more complicated than i thought it would be :-) >> >> >> >> Am Dienstag, 2. September 2014 19:12:40 UTC+2 schrieb john3909: >>> >>> >>> From: halfbrain >>> Reply-To: "beagl...@googlegroups.com" >>> Date: Tuesday, September 2, 2014 at 9:09 AM >>> To: "beagl...@googlegroups.com" >>> Subject: Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs >>> ? >>> >>> Thanks for your quick responses always. >>> I've tried the Instructions to build the Kernel >>> git clone https://github.com/RobertCNelson/bb-kernel.git >>> cd bb-kernel/ >>> >>> git checkout origin/am33x-v3.8 -b tmp >>> >>> You need to be building this on your desktop, not on your BBB. >>> >>> Regards, >>> John >>> >>> >>> >>> >>> >>> >>> but if use the command ./build_kernel.sh . i get this message after the >>> "resolving deltas process". I've tried several times but it always freezes >>> at 96%. Do you have any Idea what went wrong? >>> >>> this is what i get in the commandshell: >>> >>>
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
Thank you Brandon and William for your answers and tips. It seems that you both write about the same method... changing some lines of code in the uEnv.txt etc I will try this one out as soon as possible and will hopefully give you a positive feedback then ;-) Am Donnerstag, 4. September 2014 22:30:54 UTC+2 schrieb Brandon I: > > 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 > 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 >>>>>> Reply-To: >>>>>> Date: Sunday, May 18, 2014 at 2:42 AM >>>>>> To: >>>>>> 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: >
Re: [beagleboard] Can "allocated pins" on BBB be used as GPIOs ?
it finally works :-))) Thanks so much guys for your tips and help, espacially william. I just added *optargs=capemgr.disable_partno=BB-BONE-EMMC-2G* in the uEnv.txt file to disable all the emmc Pins. now I have more than enough pins for my project. Am Donnerstag, 4. September 2014 22:48:05 UTC+2 schrieb William Hermans: > > From my own blog site: > > optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN > > This is both for hdmi video and audio. This was prior to later kernel > version "images" that now use two different uEnv.txt files. You have a > first stage uEnv.txt file and a second stage uEnv.txt file ( for loading > secondary environment variables ). > > here is an example of the secondary uEnv.txt file which sits in /boot/ on > the rootfs. > > *#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 >> <http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0>* >> >> *uname_r=3.8.13-bone62* >> >> *#dtb=* >> >> *cmdline=quiet init=/lib/systemd/systemd* >> >> *##Example* >> *#cape_disable=capemgr.disable_partno=* >> *#cape_enable=capemgr.enable_partno=* >> >> *##Disable HDMI/eMMC* >> >> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G* >> >> *##Disable HDMI* >> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN* >> >> *##Disable eMMC* >> *#cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G* >> >> *##Audio Cape (needs HDMI Audio disabled)* >> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI* >> *#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02* >> >> >> >> *##enable BBB: eMMC Flasher:* >> *##make sure, these tools are installed: dosfstools rsync* >> *#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh* >> > > I believe that came out of RCN's August 5th LXDE standalone image. > > > On Thu, Sep 4, 2014 at 1:39 PM, halfbrain > wrote: > >> Thank you Brandon and William for your answers and tips. It seems that >> you both write about the same method... changing some lines of code in the >> uEnv.txt etc >> >> I will try this one out as soon as possible and will hopefully give you a >> positive feedback then ;-) >> >> Am Donnerstag, 4. September 2014 22:30:54 UTC+2 schrieb Brandon I: >>> >>> 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 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 wik
