3 files changed, 47 insertions, 101 deletions
diff --git a/getting-started/machines/R-Car-Starter-Kit-gen3.md b/getting-started/machines/R-Car-Starter-Kit-gen3.md
index d75a52e..e18de67 100644
--- a/getting-started/machines/R-Car-Starter-Kit-gen3.md
+++ b/getting-started/machines/R-Car-Starter-Kit-gen3.md
@@ -1,9 +1,9 @@
-# AGL Kickstart on Renesas R-Car Starter Kit Gen3 (h3ulcb, m3ulcb)
+# AGL Kickstart on Renesas R-Car Starter Kit Gen3 V2.16 (h3ulcb, m3ulcb)
 
 Here is a non exhaustive list of hardware parts that could be used to setup the R-Car Starter Kit Gen3 board development environment:
 
 * Starter Kit Gen3 board with its power supply
-* mini USB-A cable for serial console
+* micro USB-A cable for serial console
 * USB 2.0 Hub
 * Ethernet cable
 * HDMI type D (Micro connector) cable and associated display
@@ -23,9 +23,9 @@ The following documents may also be helpful:
 
 Before setting up the build environment, you need to download the proprietary drivers.
 
-* Download Renesas graphics drivers with a "click through" license from Renesas website [Link][rcar demoboard]
+* Download Renesas graphics drivers with a "click through" license from Renesas website [Link][rcar Linux] and [Link][rcar Linux Drivers]
     * Under the Target hardware: **R-Car H3/M3** section.
-
+    
 #### Note:
 
 * You have to register with a free account on MyRenesas and accept the license conditions before downloading them the drivers.  
@@ -36,10 +36,10 @@ Here after is an example of the typical files downloaded at the time of writing:
 
 ```
 chmod a+r $XDG_DOWNLOAD_DIR/*.zip
-ls -l $XDG_DOWNLOAD_DIR
+ls -1 $XDG_DOWNLOAD_DIR
 total 8220
--rw-r--r-- 1 XXX XXX    4619114 14 sept. 05:02 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.tar.gz
--rw-r--r-- 1 XXX XXX    4619796 10 oct.  23:23 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.zip
+-rw-r--r--. 1 1664 agl-sdk 4.5M Dec  8 15:23 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170125.zip
+-rw-r--r--. 1 1664 agl-sdk 2.5M Dec  8 15:24 R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170125.zip
 ```
 
 ## Setting up the build environment:
@@ -73,12 +73,14 @@ In case of missing graphics drivers, you could notice an error message as follow
 [snip]
 --- fragment /home/working/workspace_agl_master/meta-agl/templates/machine/h3ulcb/50_setup.sh
 /home/working/workspace_agl_master /home/working/workspace_agl_master/build_gen3
-The graphics and multimedia acceleration packages for the R-Car Gen3 board can be download from :
-  <http://www.renesas.com/secret/r_car_download/rcar_demoboard.jsp>
-
-These 2 files from there should be store in your'/home/ronan/Téléchargements' directory.
-  R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.zip
-  R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20160906.zip
+The graphics and multimedia acceleration packages for 
+the R-Car Gen3 board can be downloaded from:
+ https://www.renesas.com/en-us/software/D6000821.html
+ https://www.renesas.com/en-us/software/D6000822.html
+
+These 2 files from there should be store in your'/home/devel/Téléchargements' directory.
+  R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170125.zip
+  R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170125.zip
 /home/working/workspace_agl_master/build_gen3
 --- fragment /home/working/workspace_agl_master/meta-agl/templates/base/99_setup_EULAconf.sh
 --- end of setup script
@@ -168,7 +170,8 @@ lsblk
   └─sdc2   8:34   1   788M  0 part
 ```
 
-**IMPORTANT NOTE**: This is a critical operation, each computer is different and removable devices can change from time to time: so you should repeat this operation each time you insert the microSD card to confirm the device name.
+**IMPORTANT NOTE**: This is a critical operation, each computer is different and removable devices can change from time to time: 
+so you should repeat this operation each time you insert the microSD card to confirm the device name.
 
 In the example above, we see:
 * the first SATA drive as 'sda'.
@@ -282,12 +285,12 @@ sudo $TAR --extract --numeric-owner --preserve-permissions --preserve-order --to
 Copy Kernel Image and Device Tree Blob file into the **boot** directory:
 * For machine h3ulcb:
 ```
-sudo cp Image-r8a7795-h3ulcb.dtb /tmp/agl/boot/
+sudo cp Image-r8a7795-h3ulcb.dtb $SDCARD/boot/
 ```
 
 * For machine m3ulcb:
 ```
-sudo cp Image-r8a7796-m3ulcb.dtb /tmp/agl/boot/
+sudo cp Image-r8a7796-m3ulcb.dtb $SDCARD/boot/
 ```
 
 Ensure the changes have been written to the disk:
@@ -320,9 +323,11 @@ After a few seconds, you'll see the AGL splash screen on the display and you'll
 This can be “screen”, “picocom”, “minicom”.  
 The lighter of the 3 is “picocom” (it has less dependencies).  
 
-## Plug a USB cable from your computer to the serial CP2102 USB port (mini USB-A).
+## Plug a USB cable from your computer to the serial CP2102 USB port (micro USB-A).
 
-With “dmesg” you can check the device created for the serial link. Usually, it's /dev/ttyUSB0 but the number may vary depending on other USB serial ports connected to the host. To get it, you must switch the board on.  
+With “dmesg” you can check the device created for the serial link. 
+Usually, it's /dev/ttyUSB0 but the number may vary depending on other USB serial ports connected to the host. 
+To get it, you must switch the board on. 
 For example:
 
 ```
@@ -442,13 +447,15 @@ Hit any key to stop autoboot:  0
 
 ## Configure U-boot parameters
 
+Follow the steps below to configure the boot from microSD card and to set screen resolution:
+
 * Turn the board on using the power switch.
 * Hit any key to stop autoboot (warning you have only few seconds).
-* Check if you have correct parameters for booting your board:
+* Type **print** to check if you have correct parameters for booting your board:
     * For machine m3ulcb:
-    
+
     ```
-=> print
+=> printenv
 	baudrate=115200
 	bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait rw rootfstype=ext4
 	bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
@@ -518,63 +525,6 @@ saveenv
 run bootcmd
 ```
 
-### U-Boot screen configuration
-
-Follow the steps below to configure the boot from microSD card and to set screen resolution:
-
-* Power up the board
-* Using your preferred terminal emulator, type a character to abort the boot and enter the U-boot menu
-* Type **print** to check the environment:
-
-```
-print
-```
-
-* Verify that the ethaddr environment variable is set to the same MAC address value shown on the label on top of the RJ45 Ethernet connector.
-* If not, set it using the following command:
-
-```
-setenv ethaddr <MAC address>
-```
-
-For example:
-
-```
-setenv ethaddr 2e:09:0a:00:75:b5
-```
-
-* Set the follow environment variables:
-
-```
-setenv bootargs_console 'console=ttySC6,38400 ignore_loglevel'
-setenv bootargs_video 'vmalloc=384M video=HDMI-A-1:1920x1080-32@60'
-setenv bootargs_root 'root=/dev/mmcblk0p1 rootdelay=3 rw rootfstype=ext4 rootwait'
-setenv bootmmc '1:1'
-setenv bootcmd_sd 'ext4load mmc ${bootmmc} 0x40007fc0 boot/uImage+dtb'
-setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} ${bootargs_root}; run bootcmd_sd; bootm 0x40007fc0'
-```
-
-**WARNINGS:**
-If no display shows up when booting, e.g. for a non-full HD screen, replace  **1920x1080** value in the **bootargs_video** variable with lower screen resolution such as **1024x768**.  
-  Unfortunately at the moment, there is no universally supported setting.
-
-For Renesas h3ulcb use screen resolution **1024x768** and set **bootmmc** to **2:1**.
-
-* Save the environment variables:
-
-```
-saveenv
-  Saving Environment to SPI Flash...
-  SF: Detected S25FL512S with page size 256 KiB, total 64 MiB
-  Erasing SPI flash...Writing to SPI flash...done
-```
-
-* Reboot:
-
-```
-reset
-```
-
 ## Console boot
 
 After booting, you should see the wayland display on the external monitor and a login prompt on the console, such as:
@@ -645,7 +595,8 @@ Generic guide on how to add a new service in the BSP.
 [R-car m3ulcb]: http://elinux.org/R-Car/Boards/M3SK
 [R-car h3ulcb]: http://elinux.org/R-Car/Boards/H3SK
 [R-car yocto]: http://elinux.org/R-Car/Boards/Yocto-Gen3
-[rcar demoboard]: https://www.renesas.com/en-eu/solutions/automotive/rcar-demoboard.html
+[rcar Linux]: https://www.renesas.com/en-us/software/D6000821.html
+[rcar Linux Drivers]: https://www.renesas.com/en-us/software/D6000822.html
 [Iot.bzh AGL-Kickstart-on-Renesas-Porter-Board]: http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Kickstart-on-Renesas-Porter-board.pdf
 [Iot.bzh AGL-Devkit-Image-and-SDK-for-Porter]: http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Devkit-Image-and-SDK-for-porter.pdf
 [Iot.bzh AGL-Devkit-Build-your-1st-AGL-Application]: http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Devkit-Build-your-1st-AGL-Application.pdf
diff --git a/getting-started/machines/intel.md b/getting-started/machines/intel.md
index 9c71d87..6e29ab5 100644
--- a/getting-started/machines/intel.md
+++ b/getting-started/machines/intel.md
@@ -4,18 +4,20 @@
 This documentation is aiming at people who want to run Automotive Grade
 Linux (AGL) on an Intel Hardware (HW).  
 While the reference HW used by AGL project is the Open Source Minnowboard.  
-This documentation [MinnowBoard wiki](http://wiki.minnowboard.org/MinnowBoard\_Wiki\_Home) 
-can be used to enable most of 64 bits Intel Architecture (IA) using UEFI as boot loader.  
+This documentation [MinnowBoard wiki](https://minnowboard.org/) 
+can be used to enable most of 64 bits Intel Architecture (IA) using UEFI as boot loader.<br>
+In addition to the MinnowBoard, support for the the [Joule Developer Kit](https://software.intel.com/en-us/iot/hardware/joule/dev-kit) has been added. 
 You need to run the 64 bits version of the UEFI boot.
-Minnowbaord Max and Turbo are both 64 bits capable.
+Minnowbaord Max and Turbo has well as the Joule are both 64 bits capable.
 
 **Note** :  
  * This page is more focused on please willing to create bespoke AGL image and BSP.  
 If you are more interested by Apps creation, please visit [ Developing Apps for AGL](https://wiki.automotivelinux.org/agl-distro/developer_resources_intel_apps)
 
-UEFI has evolved a lot recently and you likely want to check that your HW firmware is up-to-date, this is particularly important for the Minnowboard.
+UEFI has evolved a lot recently and you likely want to check that your HW firmware is up-to-date, this is mandatory for the Minnowboard and the Joule.
 
-[`https://firmware.intel.com/projects/minnowboard-max`](https://firmware.intel.com/projects/minnowboard-max)
+[`https://firmware.intel.com/projects/minnowboard-max`](https://firmware.intel.com/projects/minnowboard-max)<br>
+[`https://software.intel.com/en-us/flashing-the-bios-on-joule`](https://software.intel.com/en-us/flashing-the-bios-on-joule)
 
 ## Where to find an AGL bootable image
 
@@ -40,27 +42,18 @@ To install the repo tool.
   chmod a+x ~/bin/repo;
 ```
 
-#### Configuring for the current *(older)* stable (blowfish\_2.0.4) (BB)
+#### Configuring for the current *(older)* stable (Charming Chinook 3.0.x)
 
 ```bash
-  cd AGL-2.0.4;
-  repo init -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo -b blowfish -m default_blowfish_2.0.4.xml
+  cd AGL-3.0.x;
+  repo init -b chinook -m default.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
 ```
-#### Configuring for master (CC)
+#### Configuring for master (DD)
 
 ```bash
   cd AGL-master;
   repo init -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo;
 ```
-
-#### Only for developer working on virtualisation
-**Note :**:  
-This is WIP and most likely to fail most of the time)
-```bash
-  cd AGL-master-next;
-  repo init -b morty -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo;
-```
-
 Once that you repo is initialised either with the stable or WIP, you need to sync the repo to fetch the various git trees.
 
 #### Downloading the configured AGL source code
@@ -77,19 +70,21 @@ When running the command:
   source meta-agl/scripts/aglsetup.sh -h
 ```
 
-You will notice the Intel entry
+You will notice the Intel entries
 
 ```bash
   intel-corei7-64
+  joule
 ```
-Simply select that entry to replace porter in the -m option.
+Simply select that entry to replace porter in the -m option.<br>
 
 ```bash
   source meta-agl/scripts/aglsetup.sh \
   -m intel-corei7-64 \
   -b build \
-  agl-devel agl-demo agl-appfw-smack agl-netboot
+  agl-devel agl-demo agl-appfw-smack agl-netboot<br>
 ```
+**Note:** use the option "-m joule" when building for a Joule developer Kit target.
 
 Start the build **This can take several hours depending of your CPU and
 internet connection and will required several GB on /tmp as well as on your build directory**
diff --git a/getting-started/machines/porter.md b/getting-started/machines/porter.md
index fe585fc..f3f6d15 100644
--- a/getting-started/machines/porter.md
+++ b/getting-started/machines/porter.md
@@ -364,7 +364,7 @@ setenv ethaddr 2e:09:0a:00:75:b5
 ```
 setenv bootargs_console 'console=ttySC6,38400 ignore_loglevel'
 setenv bootargs_video 'vmalloc=384M video=HDMI-A-1:1920x1080-32@60'
-setenv bootargs_root 'root=/dev/mmcblk0p1 rootdelay=3 rw rootfstype=ext3 rootwait'
+setenv bootargs_root 'root=/dev/mmcblk0p1 rootdelay=3 rw rootfstype=ext4 rootwait'
 setenv bootmmc '1:1'
 setenv bootcmd_sd 'ext4load mmc ${bootmmc} 0x40007fc0 boot/uImage+dtb'
 setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} ${bootargs_root}; run bootcmd_sd; bootm 0x40007fc0'