diff options
author | Ronan Le Martret <ronan.lemartret@iot.bzh> | 2018-06-22 11:45:20 +0200 |
---|---|---|
committer | Ronan Le Martret <ronan.lemartret@iot.bzh> | 2018-06-22 11:45:20 +0200 |
commit | 5f3571d3c7b3303d9b503a79706c84f773994e66 (patch) | |
tree | 40e711fbcd9915514ed16855187e2ef3d5c34533 /getting-started/troubleshooting.md | |
parent | c9702a645726424ebfe0fa88a7d773db9a3e9626 (diff) |
Update getting started documentation:
* Fix markdown lint warring.
* Update AGL current version.
* Update Renesas documentation.
Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
Diffstat (limited to 'getting-started/troubleshooting.md')
-rw-r--r-- | getting-started/troubleshooting.md | 43 |
1 files changed, 30 insertions, 13 deletions
diff --git a/getting-started/troubleshooting.md b/getting-started/troubleshooting.md index a9dcaff..d3ad889 100644 --- a/getting-started/troubleshooting.md +++ b/getting-started/troubleshooting.md @@ -31,14 +31,14 @@ tar --extract --xz --numeric-owner --preserve-permissions --preserve-order --tot ## meta-rust -Due to a known bug in the upstream of meta-rust the Yocto/OE recipe for rust-cross may fail while building RVI SOTA Client or another application written in the Rust programming language. +Due to a known bug in the upstream of meta-rust the Yocto/OE recipe for rust-cross may fail while building RVI SOTA Client or another application written in the Rust programming language. Until the complete resolution of the issue the workaround is to disable all use of the CXX11 ABI by applying the following lines to **conf/local.conf**: ```bash LD_CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0" TARGET_CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0" CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0" - + BUILD_CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" TARGET_CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" ``` @@ -96,6 +96,7 @@ To disable IVI-Shell and revert to the "plain old" weston desktop, you can follo * Reboot your target and you should then be able to start apps on the standard weston screen using afm-util ## Adding media files to play with MediaPlayer + AGL include the default MediaPlayer sample app which can be used to play music. The `lightmediascanner.service` by default will search for media under the `/media` folder. So if you plug in any USB stick containing music, they would be recognized and showed in the playlist of the MediaPlayer app menu. The current supported format is OGG. Please convert your files to ogg to play with MediaPlayer. @@ -105,14 +106,18 @@ In case you want to store music in another place, modify the `/usr/lib/systemd/u If you don’t want to touch the ligthmediascanner service, you can also add a folder named "Music" under `/home/root` and put your music files there. ## 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 + 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. + ```bash pcm.Speakers { type dmix @@ -120,7 +125,9 @@ You need to configure Audio in 2 places 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 **** @@ -131,22 +138,28 @@ The correct value (here hw:PCH,3) can be obtained with the command: 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> + +Using hw:PCH rather than hw:0 will avoid you many trouble.\ +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.\ As the default is hw:0 (card 0 device 0), it will always fail on a Minnow or UP board. For info HW device for common configuration are: + * for USB Audio -> hw:AUDIO,0 * for Intel Analog output -> hw:PCH,0 (not available on Minnow, Joule, Up boards, ...) * for Intel via -> HDMI hw:PCH,3 * for MOST Unicens -> hw:ep016ch,0 ### 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). + ```bash { "version": "0.2.0", @@ -156,7 +169,9 @@ At the beginning of that file you will find the slected HAL (note the there is n "hal_list": ["intel-minnow"], "audio_roles": [ ``` + Here you see "intel-minnow" but common values are: + * Intel laptop -> intel-pc * Intel via HDMI -> intel-minnow * Renesas -> Rcar-M3 @@ -166,28 +181,30 @@ Here you see "intel-minnow" but common values are: More HAL can be found on Gerrit (search projects named as 4a-hal*) ## Installing the Map for the Navigation Application + While the Navigation App is installed with all other demo Apps at first boot, the Maps required to be installed manually. -### a) Method 1 on target download. +### a) Method 1 on target download 1. Install the new image on the target 2. boot a first time to install the demo Apps 3. via ssh or serial connection, execute the script - * /usr/AGL/apps/download_mapdata_uk.sh <br> + * /usr/AGL/apps/download_mapdata_uk.sh\ or - * /usr/AGL/apps/download_mapdata_jp.sh + * /usr/AGL/apps/download_mapdata_jp.sh ### b) At image creation Download on your build machine the desired maps and uncompress them on your target image before 1st boot. This method is quicker and does not require to have the network enabled on the target device. Map can be found here. - * http://agl.wismobi.com/data/japan_TR9/navi_data.tar.gz - * http://agl.wismobi.com/data/UnitedKingdom_TR9/navi_data_UK.tar.gz -Once that you have built your image on the SD card, uncompress the desired map in on the SD card at the position /YourMountPoint/var/mapdata <br> -(YourMountPoint will vary with your build system).<br> +* <http://agl.wismobi.com/data/japan_TR9/navi_data.tar.gz> +* <http://agl.wismobi.com/data/UnitedKingdom_TR9/navi_data_UK.tar.gz> + +Once that you have built your image on the SD card, uncompress the desired map in on the SD card at the position /YourMountPoint/var/mapdata\ +(YourMountPoint will vary with your build system). 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 |