[Angstrom-devel] Can't build
OE Build Configuration: BB_VERSION= "1.13.2" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "beagleboard" DISTRO= "angstrom" DISTRO_VERSION= "v2011.07-core" TARGET_FPU= "hard" meta-angstrom = "master:1849db8c997a97399bcae5cf7c6dad59dc825092" meta-oe meta-efl meta-gpe meta-gnome= "master:ed90232e311fa36eabd3f51bbf6aaaf99a7d24e2" meta-texasinstruments = "master:8b25edb480146f426cbb5958968a2ff4ef3093a8" meta-efikamx = "master:70cff8742d629fd32463e3ef1bddb83f04d08dc5" meta-nslu2= "master:9b283241fe7fc5b34b1fcf4482ba021de472dfe7" meta-htc meta-nokia meta-openmoko meta-palm meta-zaurus = "master:8506c4ce9d2f8b9fca173ae9351eff4bacf57b9d" meta-sugarbay meta-crownbay meta-emenlow meta-fishriver meta-jasperforest meta-n450 = "master:96c247dad88b9fc0159b2a929216876d9fbb06dc" meta = "master:6ca80453618fa308cc2d6329450aaf5dfdf2d610" NOTE: package udev-172-r0: task do_unpack: Failed Log file attached. -- Gary Thomas | Consulting for the MLB Associates |Embedded world Cloning into /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/udev-172-r0/git... done. error: pathspec 'git.kernel.org[0:' did not match any file(s) known to git. ERROR: Function '(u'Fetch command export HOME="/home/gthomas"; export SSH_AGENT_PID="3545"; export SSH_AUTH_SOCK="/tmp/ssh-isaeFz3476/agent.3476"; export GIT_CONFIG="/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/etc/gitconfig"; export PATH="/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/bin/crossscripts:/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/sbin:/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin:/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/sbin:/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux//bin:/local/new-angstrom/sources/openembedded-core/scripts:/local/new-angstrom/sources/bitbake/bin:/opt/amltd/bin:/usr/java/jdk1.5.0_17/bin:/home/gthomas/Android/android-sdk-linux/tools:/home/gthomas/bin:/opt/amltd/bin:/usr/java/jdk1.5.0_17/bin:/home/gthomas/Android/android-sdk-linux/tools:/home/gthomas/bin:/opt/amltd/bin:/usr/java/jdk1.5.0_17/bin:/home/gthomas/Android/android-sdk-linux/tools:/home/gthomas/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/local/new-angstrom/sources/openembedded-core/scripts"; git checkout git.kernel.org[0: failed with signal 1, output:\nerror: pathspec \'git.kernel.org[0:\' did not match any file(s) known to git.\n', None)' failed ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH v2] narcissus: Create UBIFS image in a tmp directory and delete it later
A UBIFS might be required more than once, so we keep it in a tmp directory and
delete it later
This fixes a bug introduced by commit at [1] discussed in [2]
[1]
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/narcissus/commit/?id=912be148348a796f2613ebf97ee11f2a0e96530e
[2]
http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2011-July/004793.html
Signed-off-by: Joel A Fernandes
---
* The old diff was against a different commit, please use this version of the
patch. Thanks
conf/host-config |2 ++
scripts/assemble-image.sh | 15 +--
2 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/conf/host-config b/conf/host-config
index ab60c30..f30c3af 100644
--- a/conf/host-config
+++ b/conf/host-config
@@ -15,6 +15,8 @@ export CACHEDIRIPK="${CACHEDIR}/ipk"
export TARGET_DIR="${WORKDIR}/work/${MACHINE}/${IMAGENAME}"
+export UBIFS_TMP_DIR="${TARGET_DIR}-ubi-tmp"
+
# Choose between pseudo and fakeroot
export PSEUDO_LOCALSTATEDIR="${TARGET_DIR}-pseudo"
export PSEUDO_BINDIR=${WORKDIR}/bin
diff --git a/scripts/assemble-image.sh b/scripts/assemble-image.sh
index 2940d9a..df9b4ed 100755
--- a/scripts/assemble-image.sh
+++ b/scripts/assemble-image.sh
@@ -146,9 +146,9 @@ if [ -e ${WORKDIR}/conf/${MACHINE}/sd ] ; then
echo "tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz
-C /mnt/narcissus/sd_image2"
tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz -C
/mnt/narcissus/sd_image2
- if [ -e ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ] ; then
+ if [ -e ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi ] ; then
echo "Copying UBIFS image to file system:"
- mv ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi
/mnt/narcissus/sd_image2/boot/fs.ubi
+ cp ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi
/mnt/narcissus/sd_image2/boot/fs.ubi
fi
touch /mnt/narcissus/sd_image2/narcissus-was-here
@@ -187,16 +187,19 @@ function do_tar()
function do_ubifs()
{
echo "creating ubi volume"
+ mkdir -p ${UBIFS_TMP_DIR}
( cd ${TARGET_DIR}/../
echo \[ubifs\] > ubinize.cfg
echo mode=ubi >> ubinize.cfg
- echo image=${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubifs >>
ubinize.cfg
+ echo image=${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubifs >>
ubinize.cfg
echo vol_id=0 >> ubinize.cfg
echo vol_type=dynamic >> ubinize.cfg
echo vol_name=${MACHINE}-rootfs >> ubinize.cfg
echo vol_flags=autoresize >> ubinize.cfg
- echo "running: ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg"
- ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg )
+ echo "running: ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg"
+ ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg )
+ echo "running: cp ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi"
+ cp ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi
}
function do_jffs2()
@@ -452,7 +455,7 @@ case ${SDK} in
esac
echo "removing target dir"
-rm -rf ${PSEUDO_LOCALSTATEDIR} ${OPKG_TMP_DIR} ${TARGET_DIR}
+rm -rf ${PSEUDO_LOCALSTATEDIR} ${OPKG_TMP_DIR} ${UBIFS_TMP_DIR} ${TARGET_DIR}
exit ${RETVAL}
--
1.7.0.4
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH] narcissus: Create UBIFS image in a tmp directory and delete it later
A UBIFS might be required more than once, so we keep it in a tmp directory and
delete it later
This fixes a bug introduced by commit at [1] discussed in [2]
[1]
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/narcissus/commit/?id=912be148348a796f2613ebf97ee11f2a0e96530e
[2]
http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2011-July/004793.html
Signed-off-by: Joel A Fernandes
---
conf/host-config |2 ++
scripts/assemble-image.sh | 15 +--
2 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/conf/host-config b/conf/host-config
index ab60c30..f30c3af 100644
--- a/conf/host-config
+++ b/conf/host-config
@@ -15,6 +15,8 @@ export CACHEDIRIPK="${CACHEDIR}/ipk"
export TARGET_DIR="${WORKDIR}/work/${MACHINE}/${IMAGENAME}"
+export UBIFS_TMP_DIR="${TARGET_DIR}-ubi-tmp"
+
# Choose between pseudo and fakeroot
export PSEUDO_LOCALSTATEDIR="${TARGET_DIR}-pseudo"
export PSEUDO_BINDIR=${WORKDIR}/bin
diff --git a/scripts/assemble-image.sh b/scripts/assemble-image.sh
index f136507..df9b4ed 100755
--- a/scripts/assemble-image.sh
+++ b/scripts/assemble-image.sh
@@ -146,9 +146,9 @@ if [ -e ${WORKDIR}/conf/${MACHINE}/sd ] ; then
echo "tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz
-C /mnt/narcissus/sd_image2"
tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz -C
/mnt/narcissus/sd_image2
- if [ -e ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ] ; then
+ if [ -e ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi ] ; then
echo "Copying UBIFS image to file system:"
- cp ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi
/mnt/narcissus/sd_image2/boot/fs.ubi
+ cp ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi
/mnt/narcissus/sd_image2/boot/fs.ubi
fi
touch /mnt/narcissus/sd_image2/narcissus-was-here
@@ -187,16 +187,19 @@ function do_tar()
function do_ubifs()
{
echo "creating ubi volume"
+ mkdir -p ${UBIFS_TMP_DIR}
( cd ${TARGET_DIR}/../
echo \[ubifs\] > ubinize.cfg
echo mode=ubi >> ubinize.cfg
- echo image=${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubifs >>
ubinize.cfg
+ echo image=${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubifs >>
ubinize.cfg
echo vol_id=0 >> ubinize.cfg
echo vol_type=dynamic >> ubinize.cfg
echo vol_name=${MACHINE}-rootfs >> ubinize.cfg
echo vol_flags=autoresize >> ubinize.cfg
- echo "running: ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg"
- ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg )
+ echo "running: ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg"
+ ${FAKEROOT} mkfs.ubifs -r ${IMAGE_ROOTFS} -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubifs ${MKUBIFS_ARGS} && ubinize -o
${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi ${UBINIZE_ARGS} ubinize.cfg )
+ echo "running: cp ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi"
+ cp ${UBIFS_TMP_DIR}/${IMAGENAME}-${MACHINE}.ubi
${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi
}
function do_jffs2()
@@ -452,7 +455,7 @@ case ${SDK} in
esac
echo "removing target dir"
-rm -rf ${PSEUDO_LOCALSTATEDIR} ${OPKG_TMP_DIR} ${TARGET_DIR}
+rm -rf ${PSEUDO_LOCALSTATEDIR} ${OPKG_TMP_DIR} ${UBIFS_TMP_DIR} ${TARGET_DIR}
exit ${RETVAL}
--
1.7.0.4
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
On 07/19/2011 01:25 PM, Gary Thomas wrote: What kind of "disk" space do you have available? You might be able to add a swap file to extend your 32MB of RAM. I understand that there is a lot of disk space, as an SD-card is used for the root file system. meminfo says: SwapTotal: 0 kB SwapFree: 0 kB though. Maybe I need to create a swap partition and activate it. But I have no idea how I can do this. -Michael ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
On 07/19/2011 06:30 AM, Michael Schnell wrote: On 07/19/2011 01:25 PM, Gary Thomas wrote: What kind of "disk" space do you have available? You might be able to add a swap file to extend your 32MB of RAM. I understand that there is a lot of disk space, as an SD-card is used for the root file system. meminfo says: SwapTotal: 0 kB SwapFree: 0 kB though. Maybe I need to create a swap partition and activate it. But I have no idea how I can do this. Try something like this: # dd if=/dev/zero of=/SWAP bs=1024 count=512M # mkswap /SWAP # swapon /SWAP This will generate a SWAP file (not partition) of 512MB which should be more than enough for you to run opkg. -- 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] AM1808
On 07/19/2011 01:37 PM, Koen Kooi wrote: If you attach a serial console and go into uboot you can do the following (hawkboard has a AM1808 as well): ... I'll try that ASAP. So that's almost a year ago. Trying to update thru opkg would upgrade everything, so I'd advice generating a brand new image or ask logicPD if they have something more recent OK. I'll see how that can be done. That version of angstrom lacks the opkg low-mem fixes, so it failing on 32M is expected. Of course a brand new installation will fix this. But as this is just a preliminary test (we will get a new board with an AM1808 quite soon), I'd rather just upgrade opkg. Is there a chance just to exchange a few files for doing this an do a normal upgrade afterward (delaying the need to do a brand new installation) ? A distribution generally just integrates what is already out there. Angstrom is a bit of a special case since a lot of the developers either work for a silicon or board vendor or are consultants for such companies. Sounds good. If I2S is present on one of the logicPD daughterboards chances are good drivers are already there, but only for the specific codec on the daughterboards. For other codecs you might need to write some small ASoC glue. The board has nothing to do with that. There is just a chip converting I²S to analog. It supposedly does not need any configuration. So the I²S Kernel driver just needs to know the chip (OMAP L138 (completely compatible with AM1808) ). The hardware-"codec" (audio byte stream to I²S - converter) is built in the the chip. Thanks to things like pinmuxing that line is less clear than you might think :( Of course you are right. But looking at pinmuxing we found that functions do share pins, but there are no function available on multiple pins. So this is a matter of selecting which function is on a pin. I don't suppose that the Logic-PD hardware on the PCB de-muxes any pins to multiple available functions, but I'm not sure, yet. So you suggest that X11 and (e.g.) GTK and whatever necessary are just packages that can be installed ? Exactly. 32M is going to be really tight for running any reasonable gui in X11, That is why the board we are going to design will get 256 MB :) . Narcissus has a few predefined choices and will show the packages it will install on the screen, so you can install them manually as well. For small memory systems, try gpe, matchbox or enlightenment, gnome is way too heavy for that. I did not yet think about the "Desktop" system at all. Thanks for the pointers ! X11vnc hooks into an existing server as a client and can the started at will, so it's more flexible than the Xvnc way of doing it you mention. I suppose that is what I will need. The program (and supposedly the Desktop system before) is supposed to start automatically when the system boots and I want to be able to attach vie VNC to monitor the GUI of the running program. -Michael ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
Op 19 jul 2011, om 13:14 heeft Michael Schnell het volgende geschreven: > On 07/19/2011 12:16 PM, Koen Kooi wrote: >> >> Over here at angstrom we suggest angstrom :) >> > Yep. As I am new to angstrom. I) wanted to make sure that it's suitable for > embedded controllers with AM1808 or AM 335x > >> Does it really only have 32M or is that artificially limited by uboot >> setting mem=32M? > The hardware is: > http://www.logicpd.com/products/system-modules/texas-instruments-omap-l138-som-m1#tabs-som-2 > > Here they say it's either 64 or 128 MB > > but on the command line I get > > root@da850-omapl138-evm:~# cat /proc/meminfo > MemTotal: 28120 kB [..] > So maybe it in fact memory artificially limited. What to do about this ? (I'm > new to uboot, too.) If you attach a serial console and go into uboot you can do the following (hawkboard has a AM1808 as well): U-Boot 2009.01-dirty (Nov 18 2009 - 23:30:48) DRAM: 128 MB NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xa1 (Micron NAND 128MiB 1,8V 8-bit) [..] hawkboard.org > print bootargs bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p1 rw rootwait mem=64M And here we see that while 128MB is installed (the DRAM: line) linux only gets to see 64M (the mem= part), to fix that, do: hawkboard.org > setenv bootargs 'bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p1 rw rootwait mem=128M' hawkboard.org > saveenv Saving Environment to NAND... Erasing Nand... Erasing at 0x0 -- 100% complete. Writing to Nand... done hawkboard.org > In your case you might see 'DRAM: 64MB' and need to pass in mem=64M, but you get the general idea. >> The board distributor and/or vendor installed angstrom on their own, so I >> don't know which version is on there and if there were some "improvements" >> made by the vendor. I'd suggest going to >> http://narcissus.angstrom-distribution.org/ >> And building a new image for the 'da850-omapl138-evm' machine (which matches >> your evm). > I'll try to do this. But I suppose this will not take care of any uboot > issues. Moreover I suppose I need to persuade uboot to install the new > Kernel. Right now I don't know how to do this. >>> (Question 2) How to use opkg on this device or upgrading the distribution >>> (including the Kernel)l and installing additional packages (like audio and >>> X)? >> Normally it's a matter of 'opkg update ; opkg install foo', > I did try both and got the said error message: > > root@da850-omapl138-evm:~# opkg install ppp > Upgrading ppp on root from 2.4.3-r9.5 to 2.4.3-r9.6... The r9.5 -> r9.6 shows that it tries to upgrade for a pretty old angstrom to a more recent one: koen@dominion:/OE/angstrom-2008/sources/openembedded$ git blame conf/distro/angstrom-2008.1.conf | grep DISTRO_PR 56a7be99 (Koen Kooi 2010-09-07 15:03:44 +0200 18) DISTRO_PR = ".6" So that's almost a year ago. Trying to update thru opkg would upgrade everything, so I'd advice generating a brand new image or ask logicPD if they have something more recent > Downloading > http://www.angstrom-distribution.org/feeds/unstable/ipk/glibc/armv5te/base/ppp_2.4.3-r9.6_armv5te.ipk. > Collected errors: > * gz_open: fork: Cannot allocate memory. > * opkg_install_pkg: Failed to unpack control files from > /tmp/opkg-GhmigW/ppp_2.4.3-r9.6_armv5te.ipk. > * opkg_install_cmd: Cannot install package ppp. That version of angstrom lacks the opkg low-mem fixes, so it failing on 32M is expected. > you can see which packages are available at: >> http://www.angstrom-distribution.org/repo/ > I did check this and found an impressive number :) . >> Note that not all angstrom releases have the same packages available, but we >> do try. > Obviously :) . That is why I at first tried to upgrade to the current version. >>> I found that "lsmod" shows no loaded modules. But as busybox is configured >>> to feature the module specific commands I suppose the distribution does >>> support modules >>> (Question 3) Can this system be enhanced with Kernel modules ? Why are no >>> modules loaded after starting ? >> Yes, and for the second question, I don't know about the "improvements" that >> were made on top of a standard angstrom. > I see. >>> We want to use I²S audio output. The kit does feature an I²S to analog >>> converter. >>> (Question 4) How to configure, use and test the audio output ? >> No idea on that, sorry. I think that's a question for logicPD. > Not exclusively. Of course a driver for the Chips I²S hardware is necessary. > But as same is not specific to the PCB, but just to the TI-chip, I did hope > it's included in one of the standard packages. AFAIK, the I²S to analog > hardware in the board does not need any software support. But on top of the > driver, I understand that I need to install the ALSA sub-system. And > additionally, I need some user program that can output a sound just for > testing. I hoped that these are standard issues that are covered by the > distribution. A dist
Re: [Angstrom-devel] AM1808
On 07/19/2011 05:22 AM, Michael Schnell wrote: On 07/19/2011 12:19 PM, David Abdurachmanov wrote: For installing additional packages I would suggest you building it yourself and installing on machine: opkg install opkg did load the .ipg files, but when trying to install them I get: root@da850-omapl138-evm:~# ls -l ppp* -rw-r--r-- 1 root root 1118 May 15 07:59 ppp-dialin_0.1-r7.6_all.ipk -rw-r--r-- 1 root root 146258 May 15 07:59 ppp_2.4.3-r9.6_armv5te.ipk root@da850-omapl138-evm:~# opkg install ppp_2.4.3-r9.6_armv5te.ipk Collected errors: * gz_open: fork: Cannot allocate memory. * pkg_init_from_file: Failed to extract control file from ppp_2.4.3-r9.6_armv5te.ipk. OpenEmbedded (OE) metadata is used for cross-compiling packages and building kernel, u-boot, x-load, rootfs images. Now they have changes directory structure, to oe-core, meta-oe, and of course there is Angstrom meta layer. There should some instructions how to combine every layer and setup Bitbake to build up-to-date Angstrom images and packages. As there is nothing relevant on this device, I could start with a completely new installation from the sources. But right now I did not look for instructions on how to do this. As I remember all modules are build-in into kernel, that's why there is no external ones. In other words, kernel doesn't depend on rootfs image (I think). I see. You can easily change kernel without changing any files on rootfs and vice versa. Because of the said memory problem, I suppose I can't unpack a Kernel package What kind of "disk" space do you have available? You might be able to add a swap file to extend your 32MB of RAM. -- 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] AM1808
On 07/19/2011 12:19 PM, David Abdurachmanov wrote: For installing additional packages I would suggest you building it yourself and installing on machine: opkg install opkg did load the .ipg files, but when trying to install them I get: root@da850-omapl138-evm:~# ls -l ppp* -rw-r--r--1 root root 1118 May 15 07:59 ppp-dialin_0.1-r7.6_all.ipk -rw-r--r--1 root root 146258 May 15 07:59 ppp_2.4.3-r9.6_armv5te.ipk root@da850-omapl138-evm:~# opkg install ppp_2.4.3-r9.6_armv5te.ipk Collected errors: * gz_open: fork: Cannot allocate memory. * pkg_init_from_file: Failed to extract control file from ppp_2.4.3-r9.6_armv5te.ipk. OpenEmbedded (OE) metadata is used for cross-compiling packages and building kernel, u-boot, x-load, rootfs images. Now they have changes directory structure, to oe-core, meta-oe, and of course there is Angstrom meta layer. There should some instructions how to combine every layer and setup Bitbake to build up-to-date Angstrom images and packages. As there is nothing relevant on this device, I could start with a completely new installation from the sources. But right now I did not look for instructions on how to do this. As I remember all modules are build-in into kernel, that's why there is no external ones. In other words, kernel doesn't depend on rootfs image (I think). I see. You can easily change kernel without changing any files on rootfs and vice versa. Because of the said memory problem, I suppose I can't unpack a Kernel package I hope this answered at least some of the questions. Thanks a lot !!! -Michael ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
On 07/19/2011 12:16 PM, Koen Kooi wrote: Over here at angstrom we suggest angstrom :) Yep. As I am new to angstrom. I) wanted to make sure that it's suitable for embedded controllers with AM1808 or AM 335x Does it really only have 32M or is that artificially limited by uboot setting mem=32M? The hardware is: http://www.logicpd.com/products/system-modules/texas-instruments-omap-l138-som-m1#tabs-som-2 Here they say it's either 64 or 128 MB but on the command line I get root@da850-omapl138-evm:~# cat /proc/meminfo MemTotal: 28120 kB MemFree: 11636 kB Buffers:1052 kB Cached: 8796 kB SwapCached:0 kB Active: 5336 kB Inactive: 6372 kB Active(anon): 2016 kB Inactive(anon):0 kB Active(file): 3320 kB Inactive(file): 6372 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty:16 kB Writeback: 0 kB AnonPages: 1888 kB Mapped: 2200 kB Shmem: 156 kB Slab: 2636 kB SReclaimable:924 kB SUnreclaim: 1712 kB KernelStack: 360 kB PageTables: 232 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit: 14060 kB Committed_AS: 6644 kB VmallocTotal: 985088 kB VmallocUsed: 400 kB VmallocChunk: 984612 kB So maybe it in fact memory artificially limited. What to do about this ? (I'm new to uboot, too.) The board distributor and/or vendor installed angstrom on their own, so I don't know which version is on there and if there were some "improvements" made by the vendor. I'd suggest going to http://narcissus.angstrom-distribution.org/ And building a new image for the 'da850-omapl138-evm' machine (which matches your evm). I'll try to do this. But I suppose this will not take care of any uboot issues. Moreover I suppose I need to persuade uboot to install the new Kernel. Right now I don't know how to do this. (Question 2) How to use opkg on this device or upgrading the distribution (including the Kernel)l and installing additional packages (like audio and X)? Normally it's a matter of 'opkg update ; opkg install foo', I did try both and got the said error message: root@da850-omapl138-evm:~# opkg install ppp Upgrading ppp on root from 2.4.3-r9.5 to 2.4.3-r9.6... Downloading http://www.angstrom-distribution.org/feeds/unstable/ipk/glibc/armv5te/base/ppp_2.4.3-r9.6_armv5te.ipk. Collected errors: * gz_open: fork: Cannot allocate memory. * opkg_install_pkg: Failed to unpack control files from /tmp/opkg-GhmigW/ppp_2.4.3-r9.6_armv5te.ipk. * opkg_install_cmd: Cannot install package ppp. you can see which packages are available at: http://www.angstrom-distribution.org/repo/ I did check this and found an impressive number :) . Note that not all angstrom releases have the same packages available, but we do try. Obviously :) . That is why I at first tried to upgrade to the current version. I found that "lsmod" shows no loaded modules. But as busybox is configured to feature the module specific commands I suppose the distribution does support modules (Question 3) Can this system be enhanced with Kernel modules ? Why are no modules loaded after starting ? Yes, and for the second question, I don't know about the "improvements" that were made on top of a standard angstrom. I see. We want to use I²S audio output. The kit does feature an I²S to analog converter. (Question 4) How to configure, use and test the audio output ? No idea on that, sorry. I think that's a question for logicPD. Not exclusively. Of course a driver for the Chips I²S hardware is necessary. But as same is not specific to the PCB, but just to the TI-chip, I did hope it's included in one of the standard packages. AFAIK, the I²S to analog hardware in the board does not need any software support. But on top of the driver, I understand that I need to install the ALSA sub-system. And additionally, I need some user program that can output a sound just for testing. I hoped that these are standard issues that are covered by the distribution. We want to use an LCD display (mainly for development and maintenance). The kit features a socket for the chip's LCD/Video pins. We are going to get an LCD panel to connect to the board or to find a converter that allows connecting some standard monitor. (Question 5) How to configure, use and test the LCD and/or Video output ? No idea on that, sorry. I think that's a question for logicPD. I know that the stock LCD is supported by angstrom out of the box. Sounds good. Again I don't suppose that Logic PD has anything to do with this, as the PCB just routes the TI-chip's appropriate pins to a socket. We want to be able to run software that has a GUI. (Question 6) How to install a system that allows for running GUI software (X11, QT or GTK or ???, ...) Se
Re: [Angstrom-devel] wifi integration on beagleboard using wpa_supplicant tool
Dear Venkat, please follow the netiquette [1]. Am Dienstag, den 19.07.2011, 15:55 +0530 schrieb venkat k raju: > i want to integrate the wiki to beagleboard using wpa_supplicant > > my wifi device ralink, i got the driver i had build and i am able to create > ra0. > please suggest me how to configure wifi. We still do not know if you have wpa_supplicant already installed or not. Please provide as much information as possible. Koen suggested in his reply that you should try a search machine to find answers to your question. That is why he wrote the link to the Google search engine. For example searching for »beagleboard angstrom install wpa supplicant« in Google returned for example an archived post from the BeagleBoard mailing list [2] which should get you further. People on this list expect people doing some information gathering before they post questions because there are only a few developers being very busy. If you find the solution it would be great and it is expected if you could follow up with the details/solution. Thanks, Paul [1] http://en.opensuse.org/openSUSE:Mailing_list_netiquette [2] http://markmail.org/message/bugsidscpvyjgli6 signature.asc Description: This is a digitally signed message part ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] wifi integration on beagleboard using wpa_supplicant tool
Hi Koen Kooi, i want to integrate the wiki to beagleboard using wpa_supplicant my wifi device ralink, i got the driver i had build and i am able to create ra0. please suggest me how to configure wifi. thanks in advance. On Tue, Jul 19, 2011 at 3:42 PM, venkat k raju wrote: > Hi Koen Kooi , > > i didn't get you what you are trying to say? > > please suggest me > > thanks in advance. > > > On Tue, Jul 19, 2011 at 3:37 PM, Koen Kooi wrote: > >> >> Op 19 jul 2011, om 12:05 heeft venkat k raju het volgende geschreven: >> >> > Hi all, >> > >> > please suggest me hoe to go ahead, and any reference links. >> >> www.google.com >> >> ___ >> Angstrom-distro-devel mailing list >> Angstrom-distro-devel@linuxtogo.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel >> > > > > -- > thanks&Regards > k.v.raju > -- thanks&Regards k.v.raju ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
Op 19 jul 2011, om 11:31 heeft Michael Schnell het volgende geschreven: > Hi experts. > > I am new to this list, so please pardon me, if I violate any rules or this is > off-topic here. > > > > We are starting to design a controller based on an AM1808 (or maybe an > upcoming AM 335x) chip. > > Right now, we just have a Development kit (by Logic PD) that features an OMAP > 138 Chip (that is pin-compatible with the AM1808 but additionally has a DSP) > > We started playing with this kit and now, I have several questions that you > might be able to answer. > > > > The board came with an "Angstrom" Linux distribution. > > (Question 1) Can you give us a hint, whether it's a good idea to use Angstrom > for an embedded controller or do you suggest to use another distributions > (binary and/or cross compilable-source-code) ? Over here at angstrom we suggest angstrom :) > I tried to update the Distribution via the "opkg" package manager. Lots of > files were downloaded, but when opkg tried to install them I get an error > message like "too small memory". The board has 32 MB RAM Does it really only have 32M or is that artificially limited by uboot setting mem=32M? > and the file system is close to empty. (At home I have another ARM hardware > (a SLUG) with (IIRC) only 32 MB RAM and here updating via "apt" works just > fine.) The board we are going to design will have 256 MB RAM, so I suppose > this problem will not be seen there. > > Moreover I tried to install an additional package via opkg: same error. The board distributor and/or vendor installed angstrom on their own, so I don't know which version is on there and if there were some "improvements" made by the vendor. I'd suggest going to http://narcissus.angstrom-distribution.org/ And building a new image for the 'da850-omapl138-evm' machine (which matches your evm). > (Question 2) How to use opkg on this device or upgrading the distribution > (including the Kernel)l and installing additional packages (like audio and X)? Normally it's a matter of 'opkg update ; opkg install foo', you can see which packages are available at: http://www.angstrom-distribution.org/repo/ Note that not all angstrom releases have the same packages available, but we do try. > I found that "lsmod" shows no loaded modules. But as busybox is configured to > feature the module specific commands I suppose the distribution does support > modules > > (Question 3) Can this system be enhanced with Kernel modules ? Why are no > modules loaded after starting ? Yes, and for the second question, I don't know about the "improvements" that were made on top of a standard angstrom. > We want to use I²S audio output. The kit does feature an I²S to analog > converter. > > (Question 4) How to configure, use and test the audio output ? No idea on that, sorry. I think that's a question for logicPD. > We want to use an LCD display (mainly for development and maintenance). The > kit features a socket for the chip's LCD/Video pins. We are going to get an > LCD panel to connect to the board or to find a converter that allows > connecting some standard monitor. > > (Question 5) How to configure, use and test the LCD and/or Video output ? No idea on that, sorry. I think that's a question for logicPD. I know that the stock LCD is supported by angstrom out of the box. > We want to be able to run software that has a GUI. > > (Question 6) How to install a system that allows for running GUI software > (X11, QT or GTK or ???, ...) See my answers to question 1 and 2 :) > We want to be able to run the system without a monitor connected. > > (Question 7) How to install and use VNC (or whatever) to remote-control the > GUI of a running program ? For X11 you can install x11vnc and qt has a vnc plugin you can use, configuring those is a bit out of scope for angstrom, but let us know if you run into any troubles. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
Hi, I am definitely not an expert, but here what I can tell. Angstrom is use for such SoC as Gumstix Overo, BeagleBoard, etc. without any significant problems. For example Gumstix Overo Fire (that's what I am using) has 256MB RAM and 256MB NAND, but they already moves to 512/512 configuration. For installing additional packages I would suggest you building it yourself and installing on machine: opkg install OpenEmbedded (OE) metadata is used for cross-compiling packages and building kernel, u-boot, x-load, rootfs images. Now they have changes directory structure, to oe-core, meta-oe, and of course there is Angstrom meta layer. There should some instructions how to combine every layer and setup Bitbake to build up-to-date Angstrom images and packages. As I remember all modules are build-in into kernel, that's why there is no external ones. In other words, kernel doesn't depend on rootfs image (I think). You can easily change kernel without changing any files on rootfs and vice versa. Then you build your kernel with Bitbake using OE metadata packages for linux modules are created. So you can grab ipk files and install them on your rootfs (NAND) and load them as you want. Example of modules packages: <...>./overo/kernel-module-stv6110_2.6.34-r97.6_overo.ipk./overo/kernel-module-usbtmc_2.6.34-r97.6_overo.ipk./overo/kernel-module-s2255drv_2.6.34-r97.6_overo.ipk./overo/kernel-module-twofish-common_2.6.34-r97.6_overo.ipk./overo/kernel-module-snd-seq-device_2.6.34-r97.6_overo.ipk./overo/kernel-module-sha1-generic_2.6.34-r97.6_overo.ipk<...> There are tons of different configurations (machine, distro, your local configuration, package configs, etc.). Let's say for console version of Angstrom I would build omap3-console-image image, for gnome dekstop version I would go for omap3-desktop-image. Those images builds OS images (kernel, rootfs, etc), but with different packages included. I hope this answered at least some of the questions. -david > Date: Tue, 19 Jul 2011 11:31:29 +0200 > From: mschn...@lumino.de > To: angstrom-distro-devel@linuxtogo.org > Subject: [Angstrom-devel] AM1808 > > Hi experts. > > I am new to this list, so please pardon me, if I violate any rules or > this is off-topic here. > > > > We are starting to design a controller based on an AM1808 (or maybe an > upcoming AM 335x) chip. > > Right now, we just have a Development kit (by Logic PD) that features an > OMAP 138 Chip (that is pin-compatible with the AM1808 but additionally > has a DSP) > > We started playing with this kit and now, I have several questions that > you might be able to answer. > > > > The board came with an "Angstrom" Linux distribution. > > (Question 1) Can you give us a hint, whether it's a good idea to use > Angstrom for an embedded controller or do you suggest to use another > distributions (binary and/or cross compilable-source-code) ? > > > > I tried to update the Distribution via the "opkg" package manager. Lots > of files were downloaded, but when opkg tried to install them I get an > error message like "too small memory". The board has 32 MB RAM and the > file system is close to empty. (At home I have another ARM hardware (a > SLUG) with (IIRC) only 32 MB RAM and here updating via "apt" works just > fine.) The board we are going to design will have 256 MB RAM, so I > suppose this problem will not be seen there. > > Moreover I tried to install an additional package via opkg: same error. > > (Question 2) How to use opkg on this device or upgrading the > distribution (including the Kernel)l and installing additional packages > (like audio and X)? > > > > I found that "lsmod" shows no loaded modules. But as busybox is > configured to feature the module specific commands I suppose the > distribution does support modules > > (Question 3) Can this system be enhanced with Kernel modules ? Why are > no modules loaded after starting ? > > > > We want to use I²S audio output. The kit does feature an I²S to analog > converter. > > (Question 4) How to configure, use and test the audio output ? > > > > We want to use an LCD display (mainly for development and maintenance). > The kit features a socket for the chip's LCD/Video pins. We are going to > get an LCD panel to connect to the board or to find a converter that > allows connecting some standard monitor. > > (Question 5) How to configure, use and test the LCD and/or Video output ? > > > > We want to be able to run software that has a GUI. > > (Question 6) How to install a system that allows for running GUI > software (X11, QT or GTK or ???, ...) > > > > We want to be able to run the system without a monitor connected. > > (Question 7) How to install and use VNC (or whatever) to remote-control > the GUI of a running program ? > > > > Thanks in advance for any answers, tips and tricks. > > > Have fun, > -Michael > > ___ > Angstrom-distro-devel mailing l
Re: [Angstrom-devel] wifi integration on beagleboard using wpa_supplicant tool
Hi Koen Kooi , i didn't get you what you are trying to say? please suggest me thanks in advance. On Tue, Jul 19, 2011 at 3:37 PM, Koen Kooi wrote: > > Op 19 jul 2011, om 12:05 heeft venkat k raju het volgende geschreven: > > > Hi all, > > > > please suggest me hoe to go ahead, and any reference links. > > www.google.com > > ___ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel > -- thanks&Regards k.v.raju ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] wifi integration on beagleboard using wpa_supplicant tool
Op 19 jul 2011, om 12:05 heeft venkat k raju het volgende geschreven: > Hi all, > > please suggest me hoe to go ahead, and any reference links. www.google.com ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] wifi integration on beagleboard using wpa_supplicant tool
Hi all, please suggest me hoe to go ahead, and any reference links. -- thanks&Regards k.v.raju ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] AM1808
Hi experts. I am new to this list, so please pardon me, if I violate any rules or this is off-topic here. We are starting to design a controller based on an AM1808 (or maybe an upcoming AM 335x) chip. Right now, we just have a Development kit (by Logic PD) that features an OMAP 138 Chip (that is pin-compatible with the AM1808 but additionally has a DSP) We started playing with this kit and now, I have several questions that you might be able to answer. The board came with an "Angstrom" Linux distribution. (Question 1) Can you give us a hint, whether it's a good idea to use Angstrom for an embedded controller or do you suggest to use another distributions (binary and/or cross compilable-source-code) ? I tried to update the Distribution via the "opkg" package manager. Lots of files were downloaded, but when opkg tried to install them I get an error message like "too small memory". The board has 32 MB RAM and the file system is close to empty. (At home I have another ARM hardware (a SLUG) with (IIRC) only 32 MB RAM and here updating via "apt" works just fine.) The board we are going to design will have 256 MB RAM, so I suppose this problem will not be seen there. Moreover I tried to install an additional package via opkg: same error. (Question 2) How to use opkg on this device or upgrading the distribution (including the Kernel)l and installing additional packages (like audio and X)? I found that "lsmod" shows no loaded modules. But as busybox is configured to feature the module specific commands I suppose the distribution does support modules (Question 3) Can this system be enhanced with Kernel modules ? Why are no modules loaded after starting ? We want to use I²S audio output. The kit does feature an I²S to analog converter. (Question 4) How to configure, use and test the audio output ? We want to use an LCD display (mainly for development and maintenance). The kit features a socket for the chip's LCD/Video pins. We are going to get an LCD panel to connect to the board or to find a converter that allows connecting some standard monitor. (Question 5) How to configure, use and test the LCD and/or Video output ? We want to be able to run software that has a GUI. (Question 6) How to install a system that allows for running GUI software (X11, QT or GTK or ???, ...) We want to be able to run the system without a monitor connected. (Question 7) How to install and use VNC (or whatever) to remote-control the GUI of a running program ? Thanks in advance for any answers, tips and tricks. Have fun, -Michael ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
