Changes between Version 1 and Version 2 of ArtemisInstall


Ignore:
Timestamp:
Feb 11, 2011, 12:47:04 AM (7 years ago)
Author:
pespin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ArtemisInstall

    v1 v2  
    1717== Configuring stuff ==
    1818
    19 From now on, we'll conside that """/OE""" is the root path of your OE tree.
     19From now on, we'll conside that ''/OE'' is the root path of your OE tree.
    2020
    2121=== Setting machine ===
    2222
    23 in """/OE/conf/local.conf""", add (or replace in case you arelady have some MACHINE var):
     23in ''/OE/conf/local.conf'', add (or replace in case you arelady have some MACHINE var):
    2424{{{
    2525MACHINE="htcartemis"
     
    2929== Creating new branch ===
    3030
    31 As we will be modifying some OE stuff, it's better to create a separate git branch for it. For instance, in /OE/shr-unstable/openembedded/ we'll do:
     31As we will be modifying some OE stuff, it's better to create a separate git branch for it. For instance, in ''/OE/shr-unstable/openembedded/'' we'll do:
    3232{{{
    3333$ git branch artemis master # creates a branch for all the artemis stuff we'll add
     
    4545
    4646
    47 How to apply patches? It's easy. Move to """/OE/shr-unstable/openemebedded""", download all the patches above and then run:
     47How to apply patches? It's easy. Move to ''/OE/shr-unstable/openemebedded'', download all the patches above and then run:
    4848{{{
    4949$ for p in `ls *.patch`; do git apply $p; done
     
    5252=== Bitbaking image and kernel ===
    5353
    54 just run this in """/OE/shr-unstable""":
     54just run this in ''/OE/shr-unstable'':
    5555{{{
    5656. ./setup-env
     
    6262=== Getting the generated image and kernel ===
    6363
    64 Once it has finished without errors, you'll find them in """/OE/shr-unstable/tmp/deploy/images/htcartemis/"""
     64Once it has finished without errors, you'll find them in ''/OE/shr-unstable/tmp/deploy/images/htcartemis/''
    6565
    6666Kernel image has usually a .bin extension.
     
    9090== Filling the vfat partition ==
    9191
    92 Let's suppouse your vfat partition is mounted in """/media/sd1""":
     92Let's suppouse your vfat partition is mounted in ''/media/sd1'':
    9393
    9494You'll finish having something similar to this:
     
    101101
    102102=== Writing haret settings ===
    103 in /media/sd1/default.txt, write:
     103in ''/media/sd1/default.txt'', write:
    104104{{{
    105105set MTYPE 1462
     
    116116You can download it from [http://pespin.espeweb.net/artemis/images/vfat/haret-0.5.2.exe here].
    117117
    118 Put it in """/media/sd1/haret-0.5.2.exe""".
     118Put it in ''/media/sd1/haret-0.5.2.exe''.
    119119
    120120=== Acquiring initramfs ===
     
    122122At the moment I haven't tried to generate initramfs using OpenEmbedded. You can get one from [http://pespin.espeweb.net/artemis/images/vfat/initramfs.cpio.gz here] thought.
    123123
    124 Put it in """/media/sd1/initramfs.cpio.gz"""
     124Put it in ''/media/sd1/initramfs.cpio.gz''
    125125
    126126
     
    129129Get it from your tmp/deploy/images/htcartemis/zImage-htcartemis-... once it has been built by OE.
    130130
    131 Rename it to zImage and put it in /media/sd1
     131Rename it to zImage and put it in as ''/media/sd1/zImage''
    132132
    133133
     
    136136Extracting SHR image into root filesystem.
    137137
    138 Let's suppouse you mounted the ext partition (2nd partion in your SD) into """/media/sd2""".
     138Let's suppouse you mounted the ext partition (2nd partion in your SD) into ''/media/sd2''.
    139139
    140140Simply extract the tarball to it as root (very important) For instance,if the shr-image was downloaded in /home/user/Downloads/full-htcartemis.tar.gz do: