Article of Russian Tea

Russian Tea

1.2 What makes it Russian
If you adhere to the above rules, you make tea. Not necessarily good tea, but real tea, nevertheless. These rules are universal, there's nothing Russian so far. What makes all the difference, is the so-called "zavarka", the tea concentrate. The Russian process of tea-making is a two stage one; First, you make the zavarka, then water it down with hot, boiled water ("kipyatok" in Russian).
...continue...

Install tools for Open Embedded

apt-get --yes install git-core subversion patch help2man diffstat texi2html makeinfo libncurses5-dev cvs gawk python-dev python-pysqlite2 unzip python-psyco dosfstools quilt build-essential

Format SDcard for Gumstix and Beagle

フォーマットするスクリプトで楽に。
２つのファイルを同じディレクトリにおいて、rootで実行。
sh fdisk_for_overoSD.sh
でフォーマットするdeviceを聞いてきます。
fdisk_for_overoSD.sh
inputs.sh

Format SDcard for Android storage

fdisk /dev/-sdcard-
- type "c" - WIN FAT 32 (LBA)
他はお好みで。
mkfs.vfat -F 32 /dev/-sdcard-1 -n FAT

Make Debian squeeze image for running debian on Android

echo 'deb http://ftp.jp.debian.org/debian squeeze main contrib non-free' > /etc/apt/sources.list
apt-get install debootstrap qemu-user-static binfmt-support
cd ~/control-project/Android-dual-head/project/src/qemu-ubuntus
wget http://kr.archive.ubuntu.com/ubuntu/pool/universe/q/qemu-kvm/qemu-kvm-extras-static_0.12.3+noroms-0ubuntu9_i386.deb
dpkg -c qemu-kvm-extras-static_0.12.3+noroms-0ubuntu9_i386.deb
*パッケージの確認
dpkg -x qemu-kvm-extras-static_0.12.3+noroms-0ubuntu9_i386.deb .
*カレントで展開
*build-arm-chrootを確認、シンボリックリンクになっているので、元を/usr/bin/build-arm-chrootにリンクを貼る。
dd if=/dev/zero of=debian.img-rc1 bs=1024 count=1950000
*おおよそ2GBのデビアン領域を作成
mkfs.ext2 -F debian.img-rc1
tune2fs -c0 debian.img-rc1
mkdir debian
mount -o loop debian.img-rc1 debian-rc1/
build-arm-chroot --verbose --arch=armel --foreign squeeze debian http://ftp.jp.debian.org/debian
mkdir debian/sdcard
mount -t proc none debian-rc1/proc/
mount -t sysfs sysfs debian-rc1/sys/
mount -t devpts devpts debian-rc1/dev/pts
chroot debian-rc1/ /bin/bash
export HOME=/root
export USER=root
export LC_ALL=C
echo 'deb http://ftp.jp.debian.org/debian squeeze main contrib non-free' > /etc/apt/sources.list
aptitude update
aptitude --yes install openssh-server
*他に必要ならAndroid上でもaptできるので後から。
aptitude clean
echo localhost > /etc/hostname
echo 'nameserver 4.2.2.2' > /etc/resolv.conf
exit
umount debian-rc1/proc
umount debian-rc1/dev/pts
umount debian-rc1/sys
umount debian-rc1/
終わり
debian.imgが目的のブツ

boot debian on chroot

export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
mkdir /sdcard/debian-rc1
losetup /dev/block/loop5 /sdcard/debian.img-rc1
mount -t ext2 /dev/block/loop5 /sdcard/debian-rc1
rm -rf /sdcard/debian-rc1/tmp
mkdir /sdcard/debian-rc1/tmp
mount -t devpts devpts /sdcard/debian-rc1/dev/pts
mount -t proc proc /sdcard/debian-rc1/proc
mount -t sysfs sysfs /sdcard/debian-rc1/sys
mount -o bind /dev /sdcard/debian-rc1/dev
busybox mount /sdcard /sdcard/debian-rc1/root/sdcard
sysctl -w net.ipv4.ip_forward=1
chroot /sdcard/debian-rc1 /bin/bash

framebuffer vgaなどの設定

/boot/grub/menu.lstの
kernel /boot/vmlinuz-2.9.53-7-686 root=/dev/sda1 ro vga=771
この値が、bootで選択するものとなる。
vgaの設定がないと、framebufferすら有効にならん。
vgaの値について
値 解像度 色
771 800x600 256色
773 1024x7682 256色
775 1280x1024 256色
788 800x600 6万5000色
791 1024x768 6万5000色
794 1280x1024 6万5000色
789 800x600 1600万色
792 1024x768 1600万色
795 1280x1024 1600万色

GUIの停止、x-serverによるGUIの停止

aptitude removeする方法
/etc/init.d/(g)dm stopする方法(x)dmだったり環境しだい。

Error when reading rootfs

Embedded linux on SD card, Hiding problems in many case as doubt.

• sometime kernel could not boot

Kernel panic - not syncing: No init found, Try passing init= option to kernel".

• sometime read SD card

SD card Buffer I/O error.

• sometime dd command could not done

read error or write error

Please consider it before doubt your embedded linux system.
1st,that kernel panic is evidence u-boot,grub,any boot system are maybe ok.
2nd,try mkfs against rootfs partition and write rootfs all again.
3rd,change SD card writer that using write rootfs.

In my experience mostly SD card writer are problem.
Error occur while dd command, Usually SD card problem. I used many SD card even famous brand.
But how do you believe it?

There is much much illegal copy brand.

It is little help to choice with R mark or not when you purchase SD card.
It is much case in dd command error that using without R mark SD card.
By the way how weak SD card...

Gumstix Overo Fire!!!

But it is not only for overo issue. I never think ANTENNA is so much important in very close range.
When I try check wifi chip RT2870, It is still not work completely.
Anyway Fire:88W8686 needs ANTENNA even 30cm radius from AP.

And headache cross compile RT2870.
Change Makefile like that,Hope it will help for another too.
I used bitbake, So better use that tool chain for cross compile. Because bitbake already gitted kernel headers and build tool chain.
For example, little change RT2870's Makefile.
in ~/tmp/work dir there is source for build and ~/tmp/cross dir there is Tool chain.
But end of line should be "arm-angstrom-linux-gnueabi-", compiler will attach on that end.

ifeq ($(PLATFORM),PC)
# Linux 2.6
LINUX_SRC = ~/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.31-r51/image/lib/modules/2.6.31-omap1/build
LINUX_SRC_MODULE = ~/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.31-r51/image/lib/modules/2.6.31-omap1/kernel/drivers/net/wireless/
CROSS_COMPILE = /home/tknv/overo-oe/tmp/cross/armv7a/bin/arm-angstrom-linux-gnueabi-
endif

'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n'
that version doesn't work in arm... still I am testing.

Bitbake how to rebuild easy

My proposal is TAKE SNAP SHOT.

When change foo.config for configure.
Bitbake does not rebuild include that reconfigure pkg.
For example, When add some recipes to ~/images/omap3-console-image.bb.
1st build,that added recipes include for deploy images.

But

,when need reconfigure again for that. 2nd times,never include what you want.(from my experience).
It is sure rebuild by rm -rf tmp, But it will make again soooooooooooooo long building time.
My Idea is use VM.(many people use it,when developing)
It is best use-case that TAKE SNAP SHOT since VM take snap shot history ever(maybe), Just build simple omap3-console-image then Take snap shot and after that easy to add recipes,reconfigure,rebuild... also faster.