ERAGON600: Added eInfochips ERAGON600 to Linaro release docs.

Signed-off-by: eInfochips Team <ei-qc8064@einfochips.com>
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>

1 files changed, 99 insertions, 21 deletions

diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index 0fcb153..68ef8dd 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -6,6 +6,7 @@ h4. What's new in this release
 * Upgrade to Mesa master branch as of 03/10/2015 (commit: 5750595c)
 * Hardware accelerated video playback support (using Linux kernel 3.4 from the Linaro 14.10 release), see instructions below
 * Upgrade images build to Docker-based infrastructure
+* Added support for eInfochips ERAGON600 Development board (based on ERAGON600 SOM), which will be available for purchase from eInfochips soon  ("Pre order at":http://einfochips.viewpage.co/pre-order-now-eragon600-qualcomm). For fetaures and release note please refer "Release Note":http://www.supportcenter.einfochips.com/ERAGON600_Ubuntu_Linux_ReleaseNote.pdf (Coming soon).
 
 The current Linaro member monthly builds for Snapdragon 600 processor provides a kernel based on the current Linux kernel ("www.kernel.org":https://www.kernel.org) available at the time of the release. The goals of the Linaro Linux releases for Snapdragon 600 processor are to align with the latest Linux Kernel, close the gaps in features provided and migrate from the existing 3.4 vendor kernel. Developers can continue to use the "Linaro Linux release 14.10 for Snapdragon 600 processor":http://releases.linaro.org/14.10/ubuntu/ifc6410/, which is based on Linux kernel v3.4 and Ubuntu 14.04 if needed.
 
@@ -14,7 +15,7 @@ h4. Features
 The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the following features:
 
 * Provides a working Ubuntu environment with access to Ubuntu repositories (apt-get) and updates. It is based on Ubuntu ##UBUNTU_REL## (aka ##UBUNTU_REL_NICK##).
-* It is based on proprietary firmware from ##INFORCE_VERSION##.
+* It is based on proprietary firmware from ##INFORCE_VERSION## for IFC6410 and ##EINFOCHIPS_VERSION## for ERAGON600.
 * The following prebuilt images are released:
 ** @boot@ image that includes prebuilt kernel and initrd
 ** @developer@ image that includes Ubuntu core packages as well as typical development packages
@@ -24,6 +25,7 @@ The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the followi
 * Support for the following Snapdragon 600 based boards:
 ** Inforce IFC6410 Rev P1 and A1
 ** Compulab Utilite2 (CM-QS600)
+** eInfochips ERAGON600 Development Board (based on ERAGON600 SOM)
 * The following Snapdragon 600 features are supported:
 ** Quad Core Krait 300 CPU (up to 1GHz)
 ** Adreno 320 GPU, powered by @freedreno@ Mesa/Gallium GPU driver
@@ -34,7 +36,7 @@ The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the followi
 ** UART, Ethernet, SD, eMMC, SATA
 ** USB2.0 (Mouse, Keyboard, Storage)
 ** Wifi using on-board QCA6234x
-** Bluetooth using on-board QCA6234x, on IFC6410 only, not on Compulab Utilite2
+** Bluetooth using on-board QCA6234x, on IFC6410 and ERAGON600 only, not on Compulab Utilite2
 ** CPU thermal sensors
 
 h4. Information about the IFC6410 board
@@ -45,6 +47,10 @@ h4. Information about the Compulab Utilite2 Board
 
 For more information about Compulab Utilite2 board, please check "Compulab website":http://www.compulab.co.il/utilite-computer/web/utilite2-overview.
 
+h4. Information about the eInfochips ERAGON600 Board
+
+For more information about eInfochips ERAGON600 board, please check "eInfochips website":http://einfochips.viewpage.co/pre-order-now-eragon600-qualcomm.
+
 h4. Download the release binaries
 
 To install this release on a Snapdragon 600 based board, you need to download the following files:
@@ -53,14 +59,20 @@ bc. firmware-qcom-snapdragon-##VERSION##.img.gz
 linaro-##UBUNTU_REL_NICK##-developer-qcom-snapdragon-##VERSION##.img.gz
 linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img.gz
 
-You also need to download the proper boot partition, based on the actual board you are using. For the Inforce IFC6410, please download:
+You also need to download the proper boot partition, based on the actual board you are using. 
+
+For the Inforce IFC6410, please download:
 
 bc. boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img.gz
 
-for the Compulab Utilite2, please download:
+For the Compulab Utilite2, please download:
 
 bc. boot-qcom-apq8064-cm-qs600-qcom-snapdragon-##VERSION##.img.gz
 
+For the eInfochips ERAGON600, please download:
+
+bc. boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img.gz
+
 The build id is in the form: @TIMESTAMP-BUILD_NUMBER@.
 
 All images downloaded from Linaro are compressed files and need to be uncompressed first:
@@ -99,24 +111,31 @@ On the board running the Linaro Linux release, you now need to install this debi
 
 bc. sudo dpkg -i linux-image-##KERNEL_VER##-linaro-qcom_##KERNEL_VER##-linaro-qcom-1_armhf.deb
 
-The final step until to complete the upgrade is to boot the new kernel. That requires to reboot the board into fastboot mode. You can use the standard instructions from next sections, which you have used when you installed the Linaro Linux release on your board. Of course you need to make sure to connect your board to the development host (USB for fastboot, UART for the serial console), and ensure that it is booted in fastboot mode, waiting for commands, then you can flash the images on Inforce IFC6410 with:
+The final step until to complete the upgrade is to boot the new kernel. That requires to reboot the board into fastboot mode. You can use the standard instructions from next sections, which you have used when you installed the Linaro Linux release on your board. Of course you need to make sure to connect your board to the development host (USB for fastboot, UART for the serial console), and ensure that it is booted in fastboot mode, waiting for commands, then you can flash the images 
+on Inforce IFC6410 with:
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 
-or on Compulab Utilite2:
+on Compulab Utilite2 with:
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-cm-qs600-qcom-snapdragon-##VERSION##.img
 
+on eInfochips ERAGON600 with:
+
+bc. sudo fastboot flash boot boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img
+
 Your system is now up-to-date, and you are running Linaro ##RELEASE## on your development board. If you have followed all the instructions above, and you are getting any error, please report them as bugs (see Support section below).
 
 h4. Managing the proprietary firmware
 
-To properly use this release, a set of proprietary firmware blobs must be acquired separately from "Inforce Techweb website":http://www.inforcecomputing.com/techweb/ as Linaro is not redistributing them in this release.
+To properly use this release, a set of proprietary firmware blobs must be acquired separately from respective board vendors. For IFC6410 firmware, use  "Inforce Techweb website":http://www.inforcecomputing.com/techweb/ and for eInfochips ERAGON600 firmware, use "eInfochips support centre":http://www.supportcenter.einfochips.com/ as Linaro is not redistributing them in this release.
 These firmware blobs are needed for audio, power management, video and graphics support. While it is possible to boot the release without the firmware installed, it is not recommended, as various errors can occur.
 
-For bootloader, kernel and firmware, this release is based on _##INFORCE_VERSION##_, which you need to download from Inforce Techweb. The ZIP file @##INFORCE_FILE##@ includes all the proprietary firmware blobs required to use this Ubuntu-based Linaro build.
+The Linaro release does not contain any proprietary software and thus provides an _empty_ firmware image. The provided firmware image is only a placeholder for users to install the firmware blobs downloaded from respective board vendor website. The empty firmware image can be flashed as per the instructions in the next sections; of course some functionality will not work without the proprietary firmware blobs. To install the firmware and get all the features of the release, you should extract the firmware from the respective BSP release, install them in the firmware image, and flash the updated firmware image as per the instructions in the next sections.
 
-The Linaro release does not contain any proprietary software and thus provides an _empty_ firmware image. The provided firmware image is only a placeholder for users to install the firmware blobs downloaded from Inforce website. The empty firmware image can be flashed as per the instructions in the next sections; of course some functionality will not work without the proprietary firmware blobs. To install the firmware and get all the features of the release, you should extract the firmware from the Inforce BSP release, install them in the firmware image, and flash the updated firmware image as per the instructions in the next sections.
+h5. For Inforce IFC6410
+
+For bootloader, kernel and firmware, this release is based on _##INFORCE_VERSION##_, which you need to download from Inforce Techweb. The ZIP file @##INFORCE_FILE##@ includes all the proprietary firmware blobs required to use this Ubuntu-based Linaro build.
 
 To install the firmware blobs, first locate the file @proprietary.tar.gz@ in the @source@ folder after extracting the Inforce BSP release ZIP file. Then follow the next instructions on how to _loop mount_ the empty firmware image included in the release and inject Inforce's proprietary firmware blobs.
 
@@ -128,20 +147,38 @@ rmdir image
 
 The firmware image @firmware-ifc640-##VERSION##@ has been updated, and now contains all the relevant proprietary firmware blobs.
 
+h5. For eInfochips ERAGON600
+
+For bootloader, kernel and firmware, this release is based on _##EINFOCHIPS_VERSION##_, which you need to download from "eInfochips support centre":http://www.supportcenter.einfochips.com (Coming Soon). The ZIP file @##EINFOCHIPS_FILE##@ includes all the proprietary firmware blobs required to use this Ubuntu-based Linaro build.
+
+To install the firmware blobs, first locate the file @firmware-eragon600-v1.0.img.gz@ in the @binaries@ folder after extracting the eInfochips ERAGON600 BSP release ZIP file. Then follow the next instructions to extract the firmware image.
+
+bc. gunzip  firmware-eragon600-v1.0.img.gz
+
+The firmware image @firmware-eragon600-v1.0.img@ contains all the relevant proprietary firmware blobs.
+
 h4. Installing the Gnome based image
 
 Connect your board to the development host (USB for fastboot, UART for the serial console), and make sure that it is booted in fastboot mode, and waiting for commands, then you can flash the images:
 
+for Inforce IFC6410
+
 bc. sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
+sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
 
-or
+for Compulab Utilite2
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-cm-qs600-qcom-snapdragon-##VERSION##.img
+sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
+
+for eInfochips ERAGON600
+
+bc. sudo fastboot flash boot boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img
+sudo fastboot flash cache firmware-eragon600-v1.0.img
 
 then:
 
-bc. sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
-sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img
+bc. sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img
 
 Note:
 * fastboot should be able to split large files automatically, but it does not work. As such, it is mandatory to add @-S 768M@, when flashing files larger than 768MB as a workaround.
@@ -189,15 +226,28 @@ Once you have a root prompt on the serial console, you have a functional Ubuntu
 
 bc. start gdm
 
-The login manager window should appear within a few seconds, and you can log with the user @linaro@, using the password @linaro@. If you want to boot directly to the login manager, you can boot the image with different bootargs (e.g. remove the keyword @text@). For example, if you are using the Inforce IFC6410 you can run the following command:
+The login manager window should appear within a few seconds, and you can log with the user @linaro@, using the password @linaro@. If you want to boot directly to the login manager, you can boot the image with different bootargs (e.g. remove the keyword @text@). 
+
+For Inforce IFC6410,  you can run the following command:
 
 bc. sudo fastboot boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
 
+For  eInfochips ERAGON600, you can run the following command:
+
+bc. sudo fastboot boot boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img -c "console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
+
 Finally, if you want to make the bootargs change persistent, you can modify the released boot image and reflash it into the @boot@ partition:
 
+for Infoce IFC6410
+
 bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
 sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 
+for eInfochips ERAGON600
+
+bc. abootimg -u boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
+sudo fastboot flash boot boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img
+
 Note: @abootimg@ is a tool to read/write/update Android boot partition, and is available in most standard Linux distribution; simply install the package using your Linux distribution methods. If you are using Ubuntu on your PC, simply run:
 
 bc. sudo apt-get install abootimg
@@ -206,16 +256,24 @@ h4. Installing the Developer based image
 
 Connect the board to the development host (USB for fastboot, UART for the serial console), and make sure that it is booted in fastboot mode, and waiting for commands, then you can flash the images:
 
+for Inforce IFC6410
+
 bc. sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
+sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
 
-or
+for Compulab Utilite2
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-cm-qs600-qcom-snapdragon-##VERSION##.img
+sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
+
+for eInfochips ERAGON600
+
+bc. sudo fastboot flash boot boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img
+sudo fastboot flash cache firmware-eragon600-v1.0.img
 
 then:
 
-bc. sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
-sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-developer-qcom-snapdragon-##VERSION##.img
+bc. sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-developer-qcom-snapdragon-##VERSION##.img
 
 Note:
 * the root file system must be flashed in the @userdata@ partition, and the boot image must be flashed in the @boot@ partition, otherwise the system will not boot.
@@ -295,24 +353,37 @@ export CROSS_COMPILE=<path to your GCC cross compiler>/arm-linux-gnueabi-
 make qcom_defconfig
 make -j4 zImage dtbs
 
-The DTB file needs to be appended to the @zImage@, as such, you can run the following command to prepare an image for the IFC6410:
+The DTB file needs to be appended to the @zImage@, as such, you can run the following command to prepare an image 
+
+for the IFC6410:
 
 bc. cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-ifc6410.dtb  > zImage-dtb
 
-or, similarly, for Utilite2:
+for Compulab Utilite2:
 
 bc. cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-cm-qs600.dtb  > zImage-dtb
 
+for eInfochips ERAGON600:
+
+bc. cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-eI_ERAGON600.dtb  > zImage-dtb
+
 To boot a custom kernel image, you can run the following @fastboot@ command:
 
 bc. sudo fastboot boot -c "console=ttyMSM0,115200,n8 root=/dev/mmcblk0p13 rootwait rw text" -b 0x80200000 zImage-dtb
 
 If you have followed these instructions, the root file system was flashed into the @userdata@ partition which is known as @/dev/mmcblk0p13@ from Linux kernel. The @-c@ arguments represent the @bootargs@ that will be passed to the kernel during the boot.
 
-If you want to permanently use a custom kernel image, you can update the boot image and reflash it into the @boot@ partition, for example, for IFC6410:
+If you want to permanently use a custom kernel image, you can update the boot image and reflash it into the @boot@ partition, for example, 
+
+for IFC6410:
 
 bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -k zImage
-sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img.img
+sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
+
+for ERAGON600:
+
+bc. abootimg -u boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img -k zImage
+sudo fastboot flash boot boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img
 
 h4. How to get and customize Ubuntu packages source code
 
@@ -339,9 +410,16 @@ It is very important to run the copy with admin privileges and with @-a@ in orde
 
 The SD card or USB drive is now ready to be plugged and used on the target. For USB drive it is recommended to use externally powered USB drive or through an externally powered USB HUB. When booting with the root file system on USB drive or SD card, the @boot@ partition from the eMMC is still being used for the kernel and initrd. As such you need to update the @boot@ image with the new bootargs, and reflash it. If using a USB or (m)SATA drive or SD card with a single partition, the device to boot from will be either @/dev/sda1@ for USB drive or @/dev/mmcblk1p1@ for SD card. For example, for USB drive, run:
 
+for Inforce IFC6410
+
 bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/sda1 rootwait rw text"
 sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 
+for eInfochips ERAGON600
+
+bc. abootimg -u boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/sda1 rootwait rw text"
+sudo fastboot flash boot boot-qcom-apq8064-eragon600-qcom-snapdragon-##VERSION##.img
+
 h4. Gstreamer video playback technology preview
 
 An initial version of Gstreamer video decoder plugin is now available. It is not included in the image by default, and this section provides detailed information to build and use the Gstreamer plugin.
@@ -410,7 +488,7 @@ h4. Known issues and limitations
 * The serial/uart driver does not support high speed transfer, and is limited to 115200 speed. Since UART is used between the on-boart Bluetooth devices and the SoC, this limits the bandwidth between Bluetooth device and the Snapdragon 600. Some use cases such as Bluetooth audio cannot work properly at such low speed. Some other use cases such as data transfer will work but slower than expected. Suppport for high speed UART is being implemented, and will be released in a future release.
 * In the Gnome login manager, 2 fallback sessions are proposed: using Metacity or Compiz. Compiz is not working, and there is no plan to fix that, as Compiz is obsolete. Metacity is working fine, and provides an alternative graphical interface that does not use GPU for composition.
 * Few software codecs are installed by default; you might install additional codecs such as  @gstreamer1.0-plugins-bad@ or @gstreamer1.0-plugins-ugly@.
-* Once you have flashed the boot partition with a valid boot image, the board will automatically boot that image when powered on. To avoid automatically booting you can jumper the board as explained in this "page":http://mydragonboard.org/2013/forcing-ifc6410-into-fastboot/. If you cannot use this method and still needs to reboot into fastboot mode, you can erase the boot partition on a running target using the following command @sudo cat /dev/zero > /dev/mmcblk0p7@
+* Once you have flashed the boot partition with a valid boot image, the board will automatically boot that image when powered on. To avoid automatically booting you can jumper the board as explained in this "page":http://mydragonboard.org/2013/forcing-ifc6410-into-fastboot/ for IFC6410. To boot the ERAGON600 board in fastboot mode, please refer @section 7.4.2 Fastboot mode@ on @Software Reference Manual@ at "eInfochips support centre":http://www.supportcenter.einfochips.com/. If you cannot use this method and still needs to reboot into fastboot mode, you can erase the boot partition on a running target using the following command @sudo cat /dev/zero > /dev/mmcblk0p7@
 * The developer image does not include the the Linaro Qualcomm overlay by default, unlike the Gnome image. If you need to install packages overlaid by Linaro, once you have booted the developer image, you need to create the file @/etc/apt/sources.list.d/linaro-maintainers-qcom-##UBUNTU_REL_NICK##.list@ with the following content:
 
 bc. deb http://ppa.launchpad.net/linaro-maintainers/qcom-overlay/ubuntu ##UBUNTU_REL_NICK## main