diff options
Diffstat (limited to 'doc/book-enea-linux-user-guide/doc/using_enea_linux.xml')
-rw-r--r-- | doc/book-enea-linux-user-guide/doc/using_enea_linux.xml | 119 |
1 files changed, 112 insertions, 7 deletions
diff --git a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml index a6a0ed6..fbd6d28 100644 --- a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml +++ b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml | |||
@@ -27,7 +27,7 @@ | |||
27 | <programlisting>$ mkdir enea-linux | 27 | <programlisting>$ mkdir enea-linux |
28 | $ cd enea-linux | 28 | $ cd enea-linux |
29 | $ repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \ | 29 | $ repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \ |
30 | -b refs/tags/Enea_Linux_8.0 -m $MACHINE/default.xml | 30 | -b refs/tags/Enea_Linux_8.1 -m $MACHINE/default.xml |
31 | $ repo sync</programlisting> | 31 | $ repo sync</programlisting> |
32 | </step> | 32 | </step> |
33 | 33 | ||
@@ -106,7 +106,7 @@ $ cd <build_dir>/tmp/deploy/images/<target>/ # Here are the build b | |||
106 | <programlisting>$ mkdir enea-linux | 106 | <programlisting>$ mkdir enea-linux |
107 | $ cd enea-linux | 107 | $ cd enea-linux |
108 | $ repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \ | 108 | $ repo init -u git@git.enea.com:linux/manifests/el_manifests-standard.git \ |
109 | -b refs/tags/Enea_Linux_8.0 -m $MACHINE/default.xml | 109 | -b refs/tags/Enea_Linux_8.1 -m $MACHINE/default.xml |
110 | $ repo sync</programlisting> | 110 | $ repo sync</programlisting> |
111 | </step> | 111 | </step> |
112 | 112 | ||
@@ -274,7 +274,7 @@ label device01 | |||
274 | <para>Copy <filename>pxelinux.0</filename> and | 274 | <para>Copy <filename>pxelinux.0</filename> and |
275 | <filename>vesamenu.c32</filename> from the build directory, e.g. | 275 | <filename>vesamenu.c32</filename> from the build directory, e.g. |
276 | from | 276 | from |
277 | <filename><build_dir>tmp/work/corei7-64-enea-linux/syslinux/6.03-r0/image/usr/share/syslinux/</filename>.</para> | 277 | <filename><build_dir>tmp/work/corei7-64-enea-linux/syslinux/6.04-pre2-r0/image/usr/share/syslinux/</filename>.</para> |
278 | </listitem> | 278 | </listitem> |
279 | 279 | ||
280 | <listitem> | 280 | <listitem> |
@@ -308,6 +308,111 @@ label device01 | |||
308 | during BIOS power up tests. Look up the manufacturer's documentation for | 308 | during BIOS power up tests. Look up the manufacturer's documentation for |
309 | your board model to find the appropriate key.</para> | 309 | your board model to find the appropriate key.</para> |
310 | </section> | 310 | </section> |
311 | |||
312 | <section id="boot_from_ram"> | ||
313 | <title>Boot from RAM</title> | ||
314 | |||
315 | <para>This example requires that a TFTP server is set up at IP address | ||
316 | <literal><tftp_server_ip></literal>, and that the server stores | ||
317 | the Enea Linux image files, kernel image, device tree blob and root | ||
318 | filesystem, in <literal>/tftpboot/<download_directory>.</literal> | ||
319 | Please refer to <xref linkend="prebuiltprereq" /> for more details on | ||
320 | how to install and configure the TFTP server.</para> | ||
321 | |||
322 | <para>Once you have that in place, run the following commands on the | ||
323 | target:</para> | ||
324 | |||
325 | <programlisting>## set tftp server IP | ||
326 | U-Boot> setenv serverip <tftp_server_ip> | ||
327 | |||
328 | ## tftp the image files on the target machine | ||
329 | U-Boot> tftpboot 0x01000000 Image | ||
330 | U-Boot> tftpboot 0x02000000 Image-bcm2837-rpi-3-b.dtb | ||
331 | U-Boot> tftpboot 0x03000000 enea-image-standard-raspberrypi3-64.ext2.gz.u-boot | ||
332 | |||
333 | ## add any other bootargs values if necessary | ||
334 | U-Boot> setenv bootargs "8250.nr_uarts=1 root=/dev/ram rw ramdisk_size=500000 ip=dhcp \ | ||
335 | console=ttyS0,115200" | ||
336 | |||
337 | ## Start boot sequence | ||
338 | U-Boot> booti 0x01000000 0x03000000 0x02000000</programlisting> | ||
339 | </section> | ||
340 | |||
341 | <section id="boot_from_sd"> | ||
342 | <title>Boot from SD card</title> | ||
343 | |||
344 | <para>Copy the | ||
345 | <filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename> image | ||
346 | to the SD card using the Linux dd tool or Win32DiskImager in Windows, | ||
347 | and insert it into the RPi. The Raspberry Pi will not start without a | ||
348 | properly formatted SD Card, containing the bootloader, kernel image and | ||
349 | rootfs.</para> | ||
350 | |||
351 | <para>Below you can find two methods of how to format an SD Card:</para> | ||
352 | |||
353 | <itemizedlist> | ||
354 | <listitem> | ||
355 | <para><emphasis role="bold">Format and copy images to the SD card | ||
356 | using the Linux dd command line</emphasis></para> | ||
357 | |||
358 | <para>The <command>dd</command> command copies a file, converting | ||
359 | the format of the data in the process, according to the operands | ||
360 | specified:</para> | ||
361 | |||
362 | <programlisting>sudo dd bs=4M if=enea-image-standard-sdk-raspberrypi3-64.rpi-sdimg of=/dev/sdg</programlisting> | ||
363 | |||
364 | <note> | ||
365 | <para>Use <command>dd</command> cautiously - improper usage or | ||
366 | entering the wrong values could inadvertently wipe, destroy, or | ||
367 | overwrite the data on your hard drive.</para> | ||
368 | </note> | ||
369 | </listitem> | ||
370 | |||
371 | <listitem> | ||
372 | <para><emphasis role="bold">Format the SD card using the | ||
373 | Win32DiskImager program</emphasis></para> | ||
374 | |||
375 | <orderedlist> | ||
376 | <listitem> | ||
377 | <para>Download and unzip <ulink | ||
378 | url="https://sourceforge.net/projects/win32diskimager/">Win32DiskImager</ulink></para> | ||
379 | </listitem> | ||
380 | |||
381 | <listitem> | ||
382 | <para>Run <filename>Win32DiskImager.exe</filename></para> | ||
383 | </listitem> | ||
384 | |||
385 | <listitem> | ||
386 | <para>Select the drive of your SD card</para> | ||
387 | </listitem> | ||
388 | |||
389 | <listitem> | ||
390 | <para>Select the image | ||
391 | <filename><filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename></filename></para> | ||
392 | </listitem> | ||
393 | |||
394 | <listitem> | ||
395 | <para>Click "Write" and wait for the write to complete</para> | ||
396 | </listitem> | ||
397 | |||
398 | <listitem> | ||
399 | <para>Exit the imager and eject the SD Card</para> | ||
400 | </listitem> | ||
401 | |||
402 | <listitem> | ||
403 | <para>Plug the card into your Raspberry Pi</para> | ||
404 | </listitem> | ||
405 | </orderedlist> | ||
406 | |||
407 | <note> | ||
408 | <para>Be careful to select the correct drive. If you choose the | ||
409 | wrong one you may destroy your HDD data. If you are using an SD | ||
410 | Card slot and can't see the drive in the Win32DiskImager window, | ||
411 | try using an affordable external adapter in a USB slot.</para> | ||
412 | </note> | ||
413 | </listitem> | ||
414 | </itemizedlist> | ||
415 | </section> | ||
311 | </section> | 416 | </section> |
312 | 417 | ||
313 | <section id="custom_enealinux"> | 418 | <section id="custom_enealinux"> |
@@ -412,8 +517,8 @@ BBLAYERS ?= " \ | |||
412 | <para>As a result, <filename>BBLAYERS</filename> shall be extended with | 517 | <para>As a result, <filename>BBLAYERS</filename> shall be extended with |
413 | the bsp-layer/s layer for your target and any other additional layer/s. | 518 | the bsp-layer/s layer for your target and any other additional layer/s. |
414 | For details on how to do this, see the <ulink | 519 | For details on how to do this, see the <ulink |
415 | url="http://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#understanding-and-creating-layers">Yocto | 520 | url="http://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#understanding-and-creating-layers">Yocto |
416 | 2.5 Dev Manual, section "Understanding and Creating Layers".</ulink> If | 521 | 2.7 Dev Manual, section "Understanding and Creating Layers".</ulink> If |
417 | needed replace the Yocto version.</para> | 522 | needed replace the Yocto version.</para> |
418 | 523 | ||
419 | <para>Layers can be added when you initialize the build environment. The | 524 | <para>Layers can be added when you initialize the build environment. The |
@@ -440,9 +545,9 @@ BBLAYERS ?= " \ | |||
440 | <title>Adding a Recipe</title> | 545 | <title>Adding a Recipe</title> |
441 | 546 | ||
442 | <para>Study the <ulink | 547 | <para>Study the <ulink |
443 | url="https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#new-recipe-single-c-file-package-hello-world">Hello | 548 | url="https://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#new-recipe-single-c-file-package-hello-world">Hello |
444 | World recipe</ulink> in the Yocto Project Development Manual. If needed | 549 | World recipe</ulink> in the Yocto Project Development Manual. If needed |
445 | replace the example version (2.5) with the Yocto version in your Enea | 550 | replace the example version (2.7) with the Yocto version in your Enea |
446 | Linux distribution.</para> | 551 | Linux distribution.</para> |
447 | </section> | 552 | </section> |
448 | 553 | ||