Update documentation

Change-Id: Ieea8476f65433ebd41da2ca992b9984310eb6c5f
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>

1 files changed, 36 insertions, 35 deletions

diff --git a/docs/2-Installation.md b/docs/2-Installation.md
index 655bfb0..fae56ea 100644
--- a/docs/2-Installation.md
+++ b/docs/2-Installation.md
@@ -1,10 +1,10 @@
 # Prerequisites
 
-* An AGL system installed with latest Chinook version \(>3.0.2\).
+* An AGL system installed with latest Daring Dab version.
 
 * Make sure you built the AGL generator else you will not be able to generate custom low-level CAN binding.
 
-It will produce a _configuration-generated.cpp_ file to paste in the source, _src/_, directory.
+It will produce a _application-generated.cpp_ file to paste in the source, _CAN-binder/low-can-binding/binding/_, directory.
 
 * Make sure you already set up the AGL SDK using the following [SDK Quick Setup Guide](http://docs.iot.bzh/docs/getting_started/en/dev/reference/setup-sdk-environment.html). Alternatively, please refer to official guides available on [AGL Developer Site](http://docs.automotivelinux.org/docs/devguides/en/dev/#guides).
 
@@ -13,8 +13,8 @@ To get the correct SDK version installed, you **must** prepare your environment
 > **NOTE** These commands assume that proprietary graphic drivers for Renesas Porter board are located in _/home/devel/share/proprietary-renesas-rcar_ directory.
 
 ```bash
-$ prepare_meta -f chinook-next -o /xdt -l /home/devel/mirror -p /home/devel/share/proprietary-renesas-rcar/ -t porter -e wipeconfig -e rm_work
-$ /xdt/build/agl-init-build-env
+prepare_meta -f iotbzh -o /xdt -l /home/devel/mirror -p /home/devel/share/proprietary-renesas-rcar/ -t m3ulcb -e wipeconfig -e rm_work -e cleartemp
+/xdt/build/m3ulcb/agl-init-build-env
 ```
 
 * An [USB CAN adapter](http://shop.8devices.com/usb2can) connected to connector through the [right cable](http://www.mouser.fr/ProductDetail/EasySync/OBD-M-DB9-F-ES/)).
@@ -35,15 +35,15 @@ $ /xdt/build/agl-init-build-env
 > **CAUTION** It is **very important** that you do not source the SDK environment file to compile this project because some build requirements aren't installed in the AGL SDK for now.
 
 ```bash
-$ export PATH=$PATH:/xdt/sdk/sysroots/x86_64-aglsdk-linux/usr/bin
-$ export WD=$(pwd)
-$ git clone https://github.com/iotbzh/CAN_signaling
-$ export GENERATOR=${WD}/CAN-signaling/CAN-config-generator
-$ cd ${GENERATOR}
-$ mkdir -p build
-$ cd build
-$ cmake -G "Unix Makefiles" ..
-$ make
+export PATH=$PATH:/xdt/sdk/sysroots/x86_64-aglsdk-linux/usr/bin
+export WD=$(pwd)
+git clone https://github.com/iotbzh/low-level-can-service
+export GENERATOR=${WD}/CAN-signaling/CAN-config-generator
+cd ${GENERATOR}
+mkdir -p build
+cd build
+cmake -G "Unix Makefiles" ..
+make
 ```
 
 ### Naming convention
@@ -86,9 +86,9 @@ engine.torque
 
 You can use some basic decoder provided by default by the binding which are:
 
-* decoder_t::noopDecoder : Default decoder if not specified, return raw value from signal's bitfield.
-* decoder_t::booleanDecoder : Coerces a numerical value to a boolean.
-* decoder_t::stateDecoder : Find and return the corresponding string state for a CAN signal's raw integer value.
+* ***decoder_t::noopDecoder*** : Default decoder if not specified, return raw value from signal's bitfield.
+* ***decoder_t::booleanDecoder*** : Coerces a numerical value to a boolean.
+* ***decoder_t::stateDecoder***s : Find and return the corresponding string state for a CAN signal's raw integer value.
 
 ### Generating JSON from Vector CANoe Database
 
@@ -96,21 +96,21 @@ You can use some basic decoder provided by default by the binding which are:
 
 If you use CANoe to store your `gold standard` CAN signal definitions, you may be able to use the OpenXC `xml_to_json.py` script to make your JSON for you. First, export the Canoe .dbc file as XML - you can do this with Vector CANdb++. Next, create a JSON file according to the format defined above, but only define:
 
-- CAN messages.
-- Name of CAN signals within messages and their generic_name.
-- Optionnaly name of diagnostic messages and their name.
+* CAN messages.
+* Name of CAN signals within messages and their generic_name.
+* Optionnaly name of diagnostic messages and their name.
 
 To install the OpenXC utilities and runs `xml_to_json.py` script:
 
 ```bash
-$ sudo pip install openxc
-$ cd /usr/local/lib/python2.7/dist-packages/openxc/generator
+sudo pip install openxc
+cd /usr/local/lib/python2.7/dist-packages/openxc/generator
 ```
 
 Assuming the data exported from Vector is in `signals.xml` and your minimal mapping file is `mapping.json`, run the script:
 
 ```bash
-$ python -m openxc.utils ./xml_to_json.py signals.xml mapping.json signals.json
+python -m openxc.utils ./xml_to_json.py signals.xml mapping.json signals.json
 ```
 
 The script scans `mapping.json` to identify the CAN messages and signals that you want to use from the XML file. It pulls the neccessary details of the messages (bit position, bit size, offset, etc) and outputs the resulting subset as JSON into the output file, `signals.json`.
@@ -122,7 +122,7 @@ The resulting file together with `mapping.json` will work as input to the code g
 To generate your config file you just have to run the generator using the `-m` option to specify your JSON file.
 
 ```bash
-$ ./can-config-generator -m ../tests/basic.json -o configuration-generated.cpp
+./can-config-generator -m ../tests/basic.json -o application-generated.cpp
 ```
 
 If you omit the `-o` option, then code is generated on the stdout.
@@ -142,37 +142,38 @@ This generator will follow OpenXC support status of the low level CAN signaling
 > **NOTE**: The `buses` item will not be supported by this generator because the binding use another way to declare and configure buses. Please refer to the binding's documentation.
 
 ## Compile and install the binding
+
 Clone the binding repository, copy the generated file and updated the git submodules.
 
 Execute the following commands from this repository:
 
 ```bash
-$ cd $WD/CAN_signaling/CAN-binder
-$ cp ${GENERATOR}/build/configuration-generated.cpp ../low-can-binding/binding
+cd $WD/low-level-can-service/CAN-binder
+cp ${GENERATOR}/build/application-generated.cpp ../low-can-binding/binding
 ```
 
 ### Installation
 
 ```bash
-$ cd $WD/CAN_signaling/CAN-binder
-$ mkdir build
-$ cd build
-$ cmake ..
-$ make
-$ make widget
+cd $WD/low-level-can-service/CAN-binder
+mkdir build
+cd build
+cmake ..
+make
+make widget
 ```
 
-To install it manually, you need to copy the _low-can-binding.wgt_ file on your target, then from it execute the following commands :
+To install it manually, you need to copy the _low-can-service.wgt_ file on your target, then from it execute the following commands :
 
 On your host, to copy over the network :
 
 ```bash
-$ scp low-can-project.wgt root@<target_IP>:~
+scp low-can-service.wgt root@<target_IP>:~
 ```
 
 On the target, assuming _**wgt**_ file is in the root home directory:
 
 ```bash
-# afm-util install low-can-binding.wgt
-{ "added": "low-can-project@0.1" }
+afm-util install low-can-service.wgt
+{ "added": "low-can-service@2.0" }
 ```