Exynos

From Tizen Wiki
Jump to: navigation, search

Exynos 3250

ARTIK5

Exynos 4210(C210) SoC

RD210

Exynos 4412 exynos4412-trats2 (Samsung)

  • Exynos 4412(PQ) SoC RdPq

Status :

M0 (exynos4412 , armv7l CPU + MALI GPU) is ARM reference setup

M0 installation guide for the Tizen:Common profile:

Prepared images ready to be flashed to the target phone (exynos4412-trats2)

Available at :

common-arm-09.06.2014.tar.lzma (uses exynos4412-trats2.dtb KVERS=3.10.39+)

This image includes a 3.10 Linux kernel (smack disabled); if you would like to use a different one, remove the boot.img from the TAR file.


MALI drivers (EGL acceleration)

The default image provided does not contain the MALI drivers; you need to download them on your own from https://source.tizen.org/mali-ddk-wayland?langredirect=1 those drivers depend on some Xorg RPMs (those will never be installed with the current Wayland subsystem, so you need to get them from the RD-PQ/Mobile repositories).

Once you have all the RPMs (mali and X11), place them in a directory somewhere on the target, and run the included tizen-mali.sh script (if you installed the acid-env rpm it will be in the /root directory) it takes just one argument the path to the directory with all the RPMs.

The list of additional RPMs is: libXfixes-5.0.1-2.2.armv7l.rpm libXext-1.3.2-1.2.armv7l.rpm libxcb-1.10-1.1.armv7l.rpm libXau-1.0.8-2.1.armv7l.rpm libX11-1.6.2-1.2.armv7l.rpm those are defined in the script, in case you want to use different versions please change those entries on top of the script and re-run it.

A prepared TAR that contains all this binary dependencies is available at:

https://drive.google.com/#folders/0BwL-0veMh-eoeUR2ODZtTkVOaEE (file name mali-drivers.tar.gz)


Additional useful RPMs:

Some additional RPMs that might help you using the M0 are located here:

 * https://drive.google.com/#folders/0BwL-0veMh-eoN0FkdVFBVWhDakE 

You can install them manually or specify an additional parameter to mic and they will be included in the image (the rpm acid-env-1.0.norach.rpm contains some additional M0 specific tools and firmware files for the 3.10 kernel, stuff like WiFi firmware and an /usr/bin/exynos.sh script):

# mic create loop my_kickstart.ks --local-pkgs-path=a_directory_with_additional_rpms -A armv7l -O output

Creating the image manually

Mirror the current Live repository with ARM rpms for Tizen common from http://download.tizen.org/snapshots/tizen/common/common-wayland-arm/latest/repos/common/armv7l/packages/ (you need the entire structure, just mirror that location somewhere on you disk)

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:

The repository metadata needs to be fixed (it is currently broken and MIC will refuse to build an image), you'll need 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.

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 for the profile you want to use (there currenly is no ARM kickstart image, but you should use the IA32 kickstart with little modifications), here is a prepared one that should work

 * https://docs.google.com/file/d/0BwL-0veMh-eoV05wblFWZ1oxa3M/edit

Change the repository path in the KS file to whatever location you downloaded in the first step for example (assuming that I downloaded the files to /media/porucznik/live/common/arm-wayland):

   repo --name=common-wayland_armv7l --baseurl=file:///media/porucznik/live/common/arm-wayland/ --ssl_verify=no

If you are using your own custom KS or you are reusing a KS from a different profile make sure that the below packages are installed (they appear in the %packages section of your KS):

   %packages
   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 (depending on the KS it might have a different name, if you are using the provided KS it will be platform.img, if it's a different file name rename it to platform.img) Run the below script to create a flashable TAR file:

#! /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


Exynos 5422 (Samsung)

SBC: ODROID-XU3

  • Samsung Exynos5422 Cortex™-A15 2.0Ghz quad core and Cortex™-A7 quad core CPUs
  • Mali-T628 MP6(OpenGL ES 3.0/2.0/1.1 and OpenCL 1.1 Full profile)

SBC: ARTIK10

Odroid

ARTIK

REFERENCES


RESOURCES