diff options
| -rw-r--r-- | docs/1-Architecture.md | 2 | ||||
| -rw-r--r-- | docs/2-Installation.md | 4 | ||||
| -rw-r--r-- | docs/3-Usage.md | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/docs/1-Architecture.md b/docs/1-Architecture.md index c7cdff32..ea0f0a15 100644 --- a/docs/1-Architecture.md +++ b/docs/1-Architecture.md @@ -22,4 +22,4 @@ It will provides valuable access to the CAN bus by aggregate signals or providin  -Last but not least, the low level binding can be shipped as binary only using OpenXC inspired [AGL low level CAN binding Generator](http://github.com/iotbzh/can-config-generator). +Last but not least, the low level binding can be shipped as binary only using OpenXC inspired [AGL low level CAN binding Generator](https://gerrit.automotivelinux.org/gerrit/gitweb?p=src/low-level-can-generator.git;a=summary). diff --git a/docs/2-Installation.md b/docs/2-Installation.md index 0d05f9b2..a9080692 100644 --- a/docs/2-Installation.md +++ b/docs/2-Installation.md @@ -7,7 +7,7 @@ framework version >= 0.6. 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). +* Make sure you already set up the AGL SDK using the following [SDK Quick Setup Guide](http://docs.automotivelinux.org/master/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/master/docs/devguides/en/dev/#guides). If you need to have the graphic stack inside your SDK, you have to prepare your environment with the **iotbzh**, or **Daring Dab** flavor using _prepare_meta_ tool. To do so, run the following command in your docker image in the step 4 in place of `... [ prepare build environment ] ...`: @@ -18,7 +18,7 @@ prepare_meta -f iotbzh -o /xdt -l /home/devel/mirror -p /home/devel/share/propri /xdt/build/m3ulcb/agl-init-build-env ``` -* (Optionnal) 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/)) if you want to connect to a real car through the OBD2 connector. +* (Optionnal) An [USB CAN adapter](https://shop.8devices.com/index.php?route=product/product&path=67&product_id=54) connected to connector through the [right cable](https://www.mouser.fr/ProductDetail/EasySync/OBD-M-DB9-F-ES?qs=pLQRQR43dtrcAQQLCUAIxA%3D%3D) if you want to connect to a real car through the OBD2 connector. <!-- pagebreak --> diff --git a/docs/3-Usage.md b/docs/3-Usage.md index 4c0f8206..bc38417d 100644 --- a/docs/3-Usage.md +++ b/docs/3-Usage.md @@ -141,7 +141,7 @@ afm-util run low-can-service@4.0 ``` You can find instructions to use afm-util tool -[here](http://docs.iot.bzh/docs/apis_services/en/dev/reference/af-main/afm-daemons.html#using-afm-util), +[here](http://docs.automotivelinux.org/master/docs/apis_services/en/dev/reference/af-main/1-afm-daemons.html#using-afm-util), as well as documentation about Application Framework. But you can't control nor interact with it because you don't know security |