[Angstrom-devel] Koen Kooi : base-files 3.0.14: stage one of volatiles overhaul
Module: meta-angstrom
Branch: master
Commit: e52147584986b194868b6bef076b084f13684081
Author: Koen Kooi k...@dominion.thruhere.net
Date: Sat May 28 10:39:55 2011 +0200
base-files 3.0.14: stage one of volatiles overhaul
The default setup has too many different tmpfs mounts and no fallbacks for
volatiles-less usages. This adds the first set off fallbacks
Signed-off-by: Koen Kooi k...@dominion.thruhere.net
---
recipes-core/base-files/base-files_3.0.14.bbappend | 13 -
1 files changed, 12 insertions(+), 1 deletions(-)
diff --git a/recipes-core/base-files/base-files_3.0.14.bbappend
b/recipes-core/base-files/base-files_3.0.14.bbappend
index 90c451d..6e5e0a0 100644
--- a/recipes-core/base-files/base-files_3.0.14.bbappend
+++ b/recipes-core/base-files/base-files_3.0.14.bbappend
@@ -1,3 +1,14 @@
FILESEXTRAPATHS := ${THISDIR}/${PN}
-PRINC = 2
+PRINC = 3
+
+# Original: volatiles = cache run log lock tmp
+# We don't want all those in volatiles, so:
+volatiles = tmp
+dirs755 += ${localstatedir}/cache \
+${localstatedir}/run \
+${localstatedir}/log \
+${localstatedir}/lock \
+${localstatedir}/lock/subsys \
+
+
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] BeagleBoard (C3) won't boot
I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM)
Here were my steps:
$ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb
$ cd angstrom-bb
$ git checkout -b local-oe origin/oe-core
$ MACHINE=beagleboard ./oebb.sh config beagleboard
$ MACHINE=beagleboard ./oebb.sh bitbake console-image
It doesn't boot at all. I built a bootable SD from the deploy/images,
including MLO and U-Boot. Here's the boot sequence (I broke in to set
the console):
Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03)
Beagle Rev C1/C2/C3
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2011.03-00047-g494a7d2-dirty (May 27 2011 - 12:46:42)
OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
In:serial
Out: serial
Err: serial
Beagle Rev C1/C2/C3
timed out in wait_for_pin: I2C_STAT=0
No EEPROM on expansion board
Die ID #40420003040323090d017001
Hit any key to stop autoboot: 0
OMAP3 beagleboard.org # setenv console ttyO2,115200
OMAP3 beagleboard.org # printenv
baudrate=115200
beaglerev=Cx
bootcmd=if mmc rescan ${mmcdev}; then if run loadbootscript; then run
bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi;
fi; else run nandboot; fi
bootdelay=10
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
buddy=none
console=ttyO2,115200
defaultdisplay=dvi
dieid#=40420003040323090d017001
dvimode=1024x768MR-16@60
loadaddr=0x8200
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram}
omapfb.mode=dvi:${dvimode} omapfb.debug=y omap
dss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
mmcdev=0
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
mpurate=600
nandargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram}
omapfb.mode=dvi:${dvimode} omapfb.debug=y oma
pdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr}
28 40; bootm ${loadaddr}
nandroot=/dev/mtdblock4 rw
nandrootfstype=jffs2
usbtty=cdc_acm
vram=12M
Environment size: 1294/131068 bytes
OMAP3 beagleboard.org # run bootcmd
reading boot.scr
** Unable to read boot.scr from mmc 0:1 **
reading uImage
3329920 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 8200 ...
Image Name: Linux-2.6.39+
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:3329856 Bytes = 3.2 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux...
Looking around after it hangs, it seems that it didn't get
started at all. Normally, there will be some crumbs left
over in the system log buffer:
$ grep __log_buf
build/tmp-angstrom_2010_x-eglibc/work/beagleboard-angstrom-linux-gnueabi/linux-omap-2.6.39-r0/git/System.map
c067c3b4 b __log_buf
OMAP3 beagleboard.org # md 0x8067c3b4
8067c3b4: 0a000136 e4d93001 e2488001 e086651360H..e..
8067c3c4: e2855008 eaee e59dc020 e31200f0.P.. ...
8067c3d4: e58dc02c 1a19 e0832002 e3e03000, ...0..
8067c3e4: e1e03213 e58d3028 e59d2028 e1a0a009.2..(0..( ..
Any ideas what's wrong? Shouldn't this work out of the box? - I tried
to follow the directions on
http://www.angstrom-distribution.org/building-angstrom
closely, save the part of using the oe-core based script.
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
On 05/28/2011 04:35 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: It seems like every major component (MLO, U-Boot, Linux kernel) differs between my build and yours. So what did you do differently? Why is my build so different (and not work)? I used the stock conf/local.conf - did you make any changes to it? -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Angstrom 2008 setup scripts
Hi Developers, now, with the changes going for oe-core/oe-meta and some new version of angstrom, I wanted to ask if there is a stable branch of Angstrom setup scripts pointing to openembedded 2011.03 stable branch. Or at least, which is the last revision of setup scripts working to get the angstrom 2008 from the stable branch. ? Thanks, Maksym. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: Texas Instruments X-Loader 1.5.0 (May 23 2011 - 13:53:21) Beagle Rev C1/C2/C3 Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.03-rc1-0-g5ace684-dirty (May 15 2011 - 18:50:56) OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Beagle Rev C1/C2/C3 Recognized Tincantools Zippy board (rev 1 ) Die ID #40880003040323090d01c015 Hit any key to stop autoboot: 3 2 1 0 The user button is currently NOT pressed. SD/MMC found on device 0 reading uEnv.txt MMC: block number 0x1906 exceeds max(0x3af000) ** Unable to read uEnv.txt from mmc 0:1 ** Loading file /boot/uImage from mmc device 0:2 (xxa2) 3329956 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 8020 ... Image Name: Angstrom/2.6.39/beagleboard Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3329892 Bytes = 3.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.39+ (koen@dominion) (gcc version 4.5.3 (GCC) ) #2 Thu May 26 17:18:00 CEST 2011 [0.00] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f [0.00] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [0.00] Machine: OMAP3 Beagle Board [0.00] Beagle expansionboard: zippy [0.00] Reserving 12582912 bytes SDRAM for VRAM [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp ) [0.00] SRAM: Mapped pa 0x4020 to va 0xfe40 size: 0x1 [0.00] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz [0.00] Reprogramming SDRC clock to 33200 Hz [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 61952 [0.00] Kernel command line: console=ttyO2,115200n8 mpurate=auto buddy=zippy camera=lbcm3m1 vram=12M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] allocated 1048576 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.00] Memory: 244MB = 244MB total [0.00] Memory: 239680k/239680k available, 22464k reserved, 0K highmem [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] DMA : 0xffc0 - 0xffe0 ( 2 MB) [0.00] vmalloc : 0xd080 - 0xf800 ( 632 MB) [0.00] lowmem : 0xc000 - 0xd000 ( 256 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .init : 0xc0008000 - 0xc003d000 ( 212 kB) [0.00] .text : 0xc003d000 - 0xc062c7ec (6078 kB) [0.00] .data : 0xc062e000 - 0xc0679900 ( 303 kB) [0.00] NR_IRQS:410 [0.00] IRQ: Found an INTC at 0xfa20 (revision 4.0) with 96 interrupts [0.00] Total of 96 interrupts on 1 active controller [0.00] omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck. [0.00] OMAP clockevent source: GPTIMER12 at 32768 Hz [0.00] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms [0.00] Console: colour dummy device 80x30 [0.000244] Calibrating delay loop... 475.76 BogoMIPS (lpj=1855488) [0.044799] pid_max: default: 32768 minimum: 301 [0.045043] Mount-cache hash table entries: 512 [0.045532] Initializing cgroup subsys ns [0.045532] ns_cgroup deprecated: consider using the 'clone_children'
Re: [Angstrom-devel] Angstrom 2008 setup scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:54, Maksym Parkachov wrote: Hi Developers, now, with the changes going for oe-core/oe-meta and some new version of angstrom, I wanted to ask if there is a stable branch of Angstrom setup scripts pointing to openembedded 2011.03 stable branch. Yes, that's the 'master' branch :) The general idea behind the setup-scripts is that the default gives you something that builds and works by default and make it easy to switch to more dangerous stuff. To use .dev: go into sources/openembedded and do 'git master' and change the DISTRO setting in build/conf/local.conf To use oe-core: checkout the 'oe-core' branch of the setup-scripts. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN4N2AMkyGM64RGpERAhmPAJ9owX03G0Q6YqO+l04Qs+aWx6VN3wCfX8CJ EAXLMEN7fuNiOIzApd4WJkI= =5UA/ -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
(Adding beagle group to CC:) Op 28 mei 2011, om 12:46 heeft Gary Thomas het volgende geschreven: On 05/28/2011 04:35 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: It seems like every major component (MLO, U-Boot, Linux kernel) differs between my build and yours. So what did you do differently? Why is my build so different (and not work)? I used the stock conf/local.conf - did you make any changes to it? You're right, my FAT partition was a mess, I recreated the card using OE-core built stuff, log is further below. The one change I have is this one: http://patches.openembedded.org/patch/4677/ which might explain the problems Gary is seeing, but not the problems I'm encountering. I did some more experiments with some of the boards on my desk: B6 + zippy: uboot fails with mmc, know problem. kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 halts booting near the end (around the SR init and mmc messages) C3 (labeled 'very bad beagle' by gerald due to ehci capacitors) + zippy: uboot works kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 works (log below) C4: uboot works kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 halts booting near the end (around the SR init and mmc messages) C5 (preproduction sample): uboot misdetects ram as 128MiB kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 halts booting near the end (around the SR init and mmc messages) xM-C: uboot works kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 works So something in .39 is broken, my knee-jerk reaction is to blame the regulator setup, but I really don't know why it fails completely for Gary, not even producing output on serial. Maybe it's the overrides problem described above. Joel, can you borrow a C5 from Steve K and play around with that? Jason, can you try .39 on your C5 as well? Chase, which models are going to be tested for the sdk? In any case, it seems that my original test samples (C3 + xM-C) were an unlucky pick, since the other revisions are broken :( For rev B we can revert the mmc commit that gives the huge speedup, for C5 we'll probably need to hack x-loader to get the right amount of RAM setup. As for the kernel, I'll try to build one without all the fancy PM stuff applied. regards, Koen Texas Instruments X-Loader 1.5.0 (May 28 2011 - 09:55:17) Beagle Rev C1/C2/C3 Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.03-rc1-00128-gc797785-dirty (May 28 2011 - 09:55:17) OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Beagle Rev C1/C2/C3 Recognized Tincantools Zippy board (rev 1 ) Die ID #40880003040323090d01c015 Hit any key to stop autoboot: 3 2 1 0 The user button is currently NOT pressed. SD/MMC found on device 0 reading uEnv.txt ** Unable to read uEnv.txt from mmc 0:1 ** Loading file /boot/uImage from mmc device 0:2 (xxa2) ** File not found /boot/uImage Booting from nand ... NAND read: device 0 offset 0x28, size 0x40 4194304 bytes read: OK Wrong Image Format for bootm command ERROR: can't get kernel image! OMAP3 beagleboard.org # run loaduimagefat reading uImage 3329956 bytes read OMAP3 beagleboard.org # run mmcargs OMAP3 beagleboard.org # bootm ## Booting kernel from Legacy Image at 8020 ... Image Name: Angstrom/2.6.39/beagleboard Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3329892 Bytes = 3.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.39+ (koen@dominion) (gcc version 4.5.3 (GCC) ) #2 Thu May 26 17:18:00 CEST 2011 [0.00] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f [0.00] CPU: VIPT
