Skip to content

Commit

Permalink
formatting odroid and rpi image section
Browse files Browse the repository at this point in the history
  • Loading branch information
amamory committed Jan 14, 2018
1 parent 6c121a8 commit 287930e
Show file tree
Hide file tree
Showing 2 changed files with 47 additions and 12 deletions.
22 changes: 11 additions & 11 deletions docs/source/odroid/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,8 @@ Download Image

Oficial Ubuntu MATE 16.04 for Odroid XU4:

* ``https://wiki.odroid.com/odroid-xu4/os_images/linux/start``
* `<https://wiki.odroid.com/odroid-xu4/os_images/linux/start>`_
* `https://wiki.odroid.com/odroid-xu4/os_images/linux/start<https://wiki.odroid.com/odroid-xu4/os_images/linux/start>`_
* https://wiki.odroid.com/odroid-xu4/os_images/linux/start
* ``https://odroid.in/ubuntu_16.04lts/``
* https://odroid.in/ubuntu_16.04lts/

Unzip the Image file and go on to the next part.

Expand All @@ -28,16 +25,14 @@ Write the Image to the SDCard

The procedure is the same compared to procedure for Raspberry Pi

* :doc:`builds`
* :ref:`our steps for webhook creation <webhook-creation>`
* :ref:`Write the Image using Linux<burn-with-linux>`
* :ref:`Write the Image using Windows<burn-with-windows>`


Load Image to the eMMC memory
-----------------------------

One of the nice features of Odroid XU4 is that it has the `eMMC memory module<http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145628174287>`_.
One of the nice features of Odroid XU4 is that it has the `eMMC memory module <http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145628174287>`_.
According to them, the eMMC 5.0 storage is ~7x faster than the MicroSD Class-10 card in read tests.
When using it, one can realise that the boot is clearly faster than SD cards.

Expand All @@ -48,7 +43,7 @@ Using eMMC Module Reader

This method requires the `eMMC Module Reader <http://www.hardkernel.com/main/products/prdt_info.php?g_code=G135415955758>`_

.. image:: ./source/odroid/images/emmc-board.png
.. image:: ./images/emmc-board.png
:align: center

Then, the procedure to write the Image is the same for SDCards.
Expand Down Expand Up @@ -83,8 +78,7 @@ However, it is transparant to the user.
Backing up Image from the eMMC memory
-----------------------------

A similar procedure as described in the previous section can be used for backing up the Image in the eMMC module.
:
A similar procedure as described in the previous section can be used for backing up the Image in the eMMC module. Follow these steps:

* Load the Image on a SDCard as described above
* Set the memory Switch to select SDCard
Expand All @@ -101,7 +95,13 @@ Setting Up ROS
-----------------------------

There is no special procedure to install ROS dor Odroid.
Just follow the same procedure for :doc:`Raspberry Pi 3 </rpi/ros>`., using Ubuntu Mate 16.04.
Just follow the same procedure for :doc:`Raspberry Pi 3 </rpi/ros>`, using Ubuntu Mate 16.04.

:doc:`Raspberry Pi 3 1 <rpi/ros>`

:doc:`Raspberry Pi 3 2 </rpi>`

:doc:`Raspberry Pi 3 3 <rpi>`

Setting Up GAMS/Madara
-----------------------------
Expand Down
37 changes: 36 additions & 1 deletion docs/source/rpi/os-install.rst
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Unzip the Image file and go on to the next part.
Write the Image using Windows
------------

Use `Win32DiskImager<https://sourceforge.net/projects/win32diskimager/>` for writing and reading Image files.
Use `Win32DiskImager<https://sourceforge.net/projects/win32diskimager/>`_ for writing and reading Image files.

.. _burn-with-linux:

Expand Down Expand Up @@ -60,12 +60,17 @@ Expand the Image Size to Match the SDCard Size

For Raspberry Pi, execute

.. code:: bash
$ sudo raspi-config
and select 'Expand Filesystem'.

or, in the command line


.. code:: bash
$ sudo raspi-config --expand-rootfs
$ sudo reboot
Expand Down Expand Up @@ -93,11 +98,17 @@ Shutdown the embedded computer, take the SDCard to a Linux PC computer and proce

Open a Terminal instance and enter the following Linux command where the SDCard is mounted;


.. code:: bash
$ df -h
Example:


.. code:: bash
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7,8G 0 7,8G 0% /dev
Expand All @@ -117,23 +128,38 @@ The last two are important: ``/dev/sdb1`` and ``/dev/sdb2``.

Next we 'unmount', the Raspberry Pi SDcard:


.. code:: bash
$ sudo umount /dev/sdb1 /dev/sdb2
Now we make a backup copy of the Raspberry Pi image.


.. code:: bash
$ sudo dcfldd if=/dev/sdb of=~/MyImage.img
If ``dcfldd`` is not installed, then install it and reexecute the last command.


.. code:: bash
$ sudo apt-get update
$ sudo apt-get install dcfldd
Next we use the sync command to force a synchronise of any outstanding input or output


.. code:: bash
$ sudo sync
Let's take a look at the backed up image file. The file size should match the SDCard size.


.. code:: bash
$ ls -lsah ~/MyImage.img
That's all !
Expand All @@ -153,9 +179,14 @@ Fortunalty, there are some scripts that perform these steps automatically. I per
- Take the SDcard from the embedded computer and mount it on the Linux PC computer
- download the `PiShrink script <https://github.com/Drewsif/PiShrink>` and follow the instructions


.. code:: bash
$ wget https://raw.githubusercontent.com/Drewsif/PiShrink/master/pishrink.sh
.. code:: bash
$ chmod +x ../pishrink.sh
ale@gaphl40:~/img$ sudo ../pishrink.sh image.img
[sudo] password for ale:
Expand Down Expand Up @@ -186,9 +217,13 @@ Generating checksum
Finally, it is recommended to generate a checksum file for the image file.
This is usefull to check whether the file was correcpted during some data transfer.

.. code:: bash
$ md5sum image.img > image.md5
It results in a text file like this one. Save this file with the image file.

.. code:: bash
$ cat image.md5
75e87507e672de53241df4d724a0aac4 image.img

0 comments on commit 287930e

Please sign in to comment.