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 <adrian....@gmail.com <javascript:>> > Reply-To: "beagl...@googlegroups.com <javascript:>" < > beagl...@googlegroups.com <javascript:>> > Date: Tuesday, September 2, 2014 at 9:09 AM > To: "beagl...@googlegroups.com <javascript:>" <beagl...@googlegroups.com > <javascript:>> > 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 <adrian....@gmail.com> >> Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com> >> Date: Monday, September 1, 2014 at 8:23 AM >> To: "beagl...@googlegroups.com" <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 <adrian....@gmail.com> >>> Reply-To: "beagl...@googlegroups.com" <beagl...@googlegroups.com> >>> Date: Sunday, August 31, 2014 at 2:30 AM >>> To: "beagl...@googlegroups.com" <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 = <100000>; 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 <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 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...@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...@googlegroups.com <javascript:>. > 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.
