I haven't really followed any already existing WIKI pages, i just
followed my experience. Below is a quick guide on how i got that running:
Mirror the current Live repository with ARM rpms for Tizen common:
http://download.tizen.org/live/Tizen:/Common/arm-wayland/
Once that's done you need to make sure that the package mic-bootstrap is
in the repository (once it was missing from the downloaded repository, i
copied some other ARM profile on download.tizen.org)
The repository needs to be rebuilt, download two XML files:
http://download.tizen.org/snapshots/tizen/common/common-wayland-ia32/latest/repos/common/ia32/packages/repodata/group.xml
http://download.tizen.org/snapshots/tizen/common/common-wayland-ia32/latest/repos/common/ia32/packages/repodata/patterns.xml
and place them in the repodata directory of the downloaded structure.
# cp patterns.xml group.xml repodata/
I had to edit the patterns.xml and remove the <rpm:entry
name="intel-gpu-tools"/> tag (it causes a dependency problem for mic
later on)
To rebuild the repository data, cd into the directory that you
downloaded and run (you need the createrepo package)
# createrepo -g repodata/groups.xml .
# modifyrepo repodata/patterns.xml .
Download the .ks file from the common profile and edit the initial
section, there are 2 entries you need to modify:
(i used the i586 wayland kickstart from
http://download.tizen.org/snapshots/tizen/common/common-wayland-ia32/latest/images/common-wayland-mbr-i586/common-wayland-mbr-i586.ks,
but i guess any would work)
repo: change the baseurl to the directory you downloaded the files to:
repo --name=common-wayland_armv7l
--baseurl=file:///media/porucznik/live/common/arm-wayland/ --ssl_verify=no
packages: i had to add some M0 specific packages to later get the USB
connection up and running in network mode:
%packages
@Common Base
@Common Console Tools
@Common Packaging
@Common Wayland
@Common Adaptation
@Common Middleware
@Common Applications
@Common Bluetooth
@Common Desktop Applications
@Common Qt5
usb-server
usbutils
sdbd
security-server
%end
Run mic as root or via sudo (replace KICKSTART_FILE with the path to you
kickstart and OUTPUT_DIRECTORY to a directory where you want the
resulting image to placed)
# mic create loop KICKSTART_FILE -A armv7l -o OUTPUT_DIRECTORY
This will create a .img file tizen-common.img, rename it to
platform.img, cd into the directory the resulting platform.img gile is
in and run this small script (as root)
#! /bin/bash
for imgfile in *.img; do
echo -en "$imgfile: "
echo -en "fsck "
e2fsck -p -f $imgfile > /dev/null
size=$(resize2fs -P $imgfile 2>/dev/null | awk '{ print $NF }')
size=$((size*110/100))
echo -en "resize2fs ($size)"
resize2fs $imgfile $size 1>/dev/null 2> /dev/null
echo
done
echo "Tar"
tar cf image.tar *.img
echo "Done"
ls -al image.tar
This will produce a file image.tar you can lthor to your device:
# lthor image.tar
(it will overwrite the / partition only, you should leave the 3.10
kernel and modules that were on the device).
That's it. To build the kernel use the 3.10 repository from tizen.org,
but to get that working is a different set of instructions to follow.
best regards.
On 05/22/2014 04:35 PM, Dominig ar Foll wrote:
Roman,
could you please point me on the wiki page which explain how you
created the image and how you install it on the M0 device.
That would be very useful.
Regards
Dominig
Le 22/05/2014 11:34, Roman Kubiak a écrit :
I was able to build a working image for the M0 target (Samsung
GalaxyIII wannabe), minor issues i faced
- the gpu-intel tools is part of command line utils in patterns of
the original common image i had to remove that
- crosswalk is not there and is part of the patterns file for common
(had to remove that)
It works on FBDEV with kernel 3.10 from tizen.org. The user display
has to be part of the video group to be able to access the device.
On 05/20/2014 06:32 PM, Dominig ar Foll (Intel OTC) wrote:
Hello,
we are facing some difficulties in re-boot strapping Tizen3 Common
for ARM.
We did an initial bootstrap using Tizen Mobile and that has allowed
us to build almost all Tizen3 Common packages (only 8 out of 738 are
still not building).
But now in order to get a clean built, we want to self-re-bootstrap
the ARMrepoand we are facing difficulties with glibcand a few other
packages.
We would need help to fix the glibc build issue first as we expect
that the same fix will work for the other packages.
Our configuration uses OBS workers with KVM.
Our build issue can be seen here:
https://build.tizen.org/package/live_build_log?arch=armv7l&package=glibc&project=Tizen%3ACommon&repository=arm-wayland
<https://build.tizen.org/package/live_build_log?arch=armv7l&package=glibc&project=Tizen%3ACommon&repository=arm-wayland>
The error is very strange:
/home/abuild/rpmbuild/BUILD/glibc-2.18/cc-base/iconv/iconvconfig:
error while loading shared libraries:
/home/abuild/rpmbuild/BUILD/glibc-2.18/cc-base/iconv/iconvconfig:
failed to map segment from shared object: Operation not permitted
We think that the error is due to a package that is missing in a
alternative architecture (e.g. IA32) during the boot strap process
and the sharelib load fails due to the Arch mismatch but we might be
wrong.
We have no clue on how to correct the issue.
Do you have any idea how to progress ?
Does someone know how to bootstrap ARM on an OBS ?
Thanks in advance for your help.
--
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
--
--------------
Roman Kubiak
--------------
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
--
Dominig ar Foll
Senior Software Architect
Intel Open Source Technology Centre
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
--
--------------
Roman Kubiak
--------------
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
