summaryrefslogtreecommitdiffstats
path: root/getting-started
diff options
context:
space:
mode:
Diffstat (limited to 'getting-started')
-rw-r--r--getting-started/machines/R-Car-Starter-Kit-gen3.md15
-rw-r--r--getting-started/setup-sdk-environment.md4
-rw-r--r--getting-started/source-code.md4
-rw-r--r--getting-started/troubleshooting.md38
4 files changed, 36 insertions, 25 deletions
diff --git a/getting-started/machines/R-Car-Starter-Kit-gen3.md b/getting-started/machines/R-Car-Starter-Kit-gen3.md
index bd59990..c40fcb4 100644
--- a/getting-started/machines/R-Car-Starter-Kit-gen3.md
+++ b/getting-started/machines/R-Car-Starter-Kit-gen3.md
@@ -1,4 +1,4 @@
-# AGL Kickstart on Renesas R-Car Starter Kit Gen3 V2.23 (h3ulcb, m3ulcb)
+# AGL Kickstart on Renesas R-Car Starter Kit Gen3 V2.23 (h3ulcb, m3ulcb, salvator-x)
Here is a non exhaustive list of hardware parts that could be used to setup the R-Car Starter Kit Gen3 board development environment:
@@ -14,6 +14,9 @@ For more information and latest news, please check :
* [elinux page for h3ulcb][R-car h3ulcb]
* [elinux page for m3ulcb][R-car m3ulcb]
+* [elinux page for salvator-x][R-car salvator-x]
+
+Note that the Salvator-X has NDA restrictions, so less documentation is available both here and elsewhere.
The following documents may also be helpful:
@@ -60,6 +63,11 @@ export MACHINE=h3ulcb
export MACHINE=m3ulcb
```
+* for machine **h3-salvator-x**:
+
+ ```bash
+export MACHINE=h3-salvator-x
+
Now, init your build environment:
```bash
@@ -101,6 +109,8 @@ grep -w -e "^MACHINE =" $AGL_TOP/build/conf/local.conf
MACHINE = "h3ulcb"
or
MACHINE = "m3ulcb"
+or
+ MACHINE = "h3-salvator-x"
```
Configure for Release or Development:
@@ -151,7 +161,7 @@ Follow the documentation on the [eLinux.org wiki][R-car loader update] for the e
### Update the firmware stack
-As an AArch64 platform both the **h3ulcb** and **m3ulcb** have a firmware stack that consists of multiple parts. In both cases we have **ARM Trusted Firmware**, **OP-Tee** and **U-Boot** in use. Starting with Eel you must update the firmware to at least the version referenced here. For the exact steps required to flash the device see the eLinux.org wiki for **[h3ulcb][R-car h3ulcb firmware update]** or **[m3ulcb][R-car m3ulcb firmware update]** respectively. In both cases the files listed in the table will be found in the *\$AGL_TOP/build/tmp/deploy/images/$MACHINE* directory as specified in previous steps.
+As an AArch64 platform both the **h3ulcb** and **m3ulcb** have a firmware stack that consists of multiple parts. In both cases we have **ARM Trusted Firmware**, **OP-Tee** and **U-Boot** in use. Starting with Eel you must update the firmware to at least the version referenced here. For the exact steps required to flash the device see the eLinux.org wiki for **[h3ulcb][R-car h3ulcb firmware update]** or **[m3ulcb][R-car m3ulcb firmware update]** respectively. In both cases the files listed in the table will be found in the *\$AGL_TOP/build/tmp/deploy/images/$MACHINE* directory as specified in previous steps. The Salvator-X firmware update process is not documented on eLinux.
## Prepare the SD-card on the host
@@ -507,6 +517,7 @@ Detailed guides on how to build AGL for Renesas boards and using AGL SDK inside
[R-car m3ulcb firmware update]: https://elinux.org/R-Car/Boards/M3SK#Flashing_firmware
[R-car h3ulcb]: http://elinux.org/R-Car/Boards/H3SK
[R-car h3ulcb firmware update]: https://elinux.org/R-Car/Boards/H3SK#Flashing_firmware
+[R-car salvator-x]: https://elinux.org/R-Car/Boards/Salvator-X
[R-car loader update]: http://elinux.org/R-Car/Boards/Kingfisher#How_to_update_of_Sample_Loader_and_MiniMonitor
[R-car yocto]: http://elinux.org/R-Car/Boards/Yocto-Gen3
[rcar Linux Drivers]: https://www.renesas.com/solutions/automotive/rcar-demoboard.html
diff --git a/getting-started/setup-sdk-environment.md b/getting-started/setup-sdk-environment.md
index 3479a21..8ef742c 100644
--- a/getting-started/setup-sdk-environment.md
+++ b/getting-started/setup-sdk-environment.md
@@ -45,10 +45,10 @@ A pre-built image is available on automotivelinux download public site and can b
First, download and load the image in your local Docker instance:
```bash
-wget -O - https://download.automotivelinux.org/AGL/snapshots/sdk/docker/docker_agl_worker-3.0.tar.xz | sudo docker load;
+wget -O - https://download.automotivelinux.org/AGL/snapshots/sdk/docker/docker_agl_worker-latest.tar.xz | sudo docker load;
docker images;
REPOSITORY TAG IMAGE ID CREATED SIZE
- docker.automotivelinux.org/agl/worker 3.0 42009148bc03 6 days ago 926.9 MB
+ docker.automotivelinux.org/agl/worker 5.0 42009148bc03 6 days ago 926.9 MB
jenkins latest 55720d63e328 5 weeks ago 711.9 MB
hello-world latest c54a2cc56cbb 5 months ago 1.848 kB
```
diff --git a/getting-started/source-code.md b/getting-started/source-code.md
index 567128b..9bf1d96 100644
--- a/getting-started/source-code.md
+++ b/getting-started/source-code.md
@@ -122,11 +122,11 @@ You can choose your source release
### Download Latest Stable Release
-To download all layers for the for the latest stable release, dab 4.0.2:
+To download all layers for the for the latest stable release, eel 5.0.2:
```bash
cd $AGL_TOP
-repo init -b dab -m dab_4.0.2.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
+repo init -b eel -m eel_5.0.2.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
repo sync
```
diff --git a/getting-started/troubleshooting.md b/getting-started/troubleshooting.md
index 95a08ac..a9dcaff 100644
--- a/getting-started/troubleshooting.md
+++ b/getting-started/troubleshooting.md
@@ -107,29 +107,29 @@ If you don’t want to touch the ligthmediascanner service, you can also add a f
## Configuring the Audio hardware
AGL uses alsa as Audio configuration master. If the correct HW is not setup, the Audio system will fail to start what will also fails the demo Home Screen launch.
You need to configure Audio in 2 places
- * alsa
- * 4A HAL
+* alsa
+* 4A HAL
### alsa
The file /etc/asound.conf (at the beginning) tells which hardware will be used.
For example on an Intel Minnow or UP board your need to enter the following configuration.
-```json
- pcm.Speakers {
- type dmix
- slave {pcm "hw:PCH,3"}
- ipc_key 1001 # ipc_key should be unique to each dmix
-}
+```bash
+ pcm.Speakers {
+ type dmix
+ slave {pcm "hw:PCH,3"}
+ ipc_key 1001 # ipc_key should be unique to each dmix
+ }
```
The correct value (here hw:PCH,3) can be obtained with the command:
```bash
-aplay -l
-**** List of PLAYBACK Hardware Devices ****
-card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
- Subdevices: 1/1
- Subdevice #0: subdevice #0
-card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
- Subdevices: 1/1
- Subdevice #0: subdevice #0
+ aplay -l
+ **** List of PLAYBACK Hardware Devices ****
+ card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
+ Subdevices: 1/1
+ Subdevice #0: subdevice #0
+ card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
+ Subdevices: 1/1
+ Subdevice #0: subdevice #0
```
Using hw:PCH rather than hw:0 will avoid you many trouble.<br>
NOTE that the device number is not always 0. If you give no device number, alsa will assume device 0 (and the not the first available device), what can fail your configuration.<br>
@@ -143,11 +143,11 @@ For info HW device for common configuration are:
### 4A HAL configuration
AGL 4A needs to know which HAL shall be used. This is configured in the file:
-```
+```bash
/usr/agl-service-audio-4a/ahl-agl-service-audio-4a-config.json
```
At the beginning of that file you will find the slected HAL (note the there is no correct default value).
-```json
+```bash
{
"version": "0.2.0",
"policy_module": "AudioPolicy_v1",
@@ -189,5 +189,5 @@ Once that you have built your image on the SD card, uncompress the desired map i
(YourMountPoint will vary with your build system).<br>
You can also use the script from the image to install the Mapdata on your SD card but there is little adavange in using that method. e.g.
- * download_mapdata_jp.sh /YourMountPoint
+* download_mapdata_jp.sh /YourMountPoint