Re: Navigation app is not launching on RaspberryPi3 with EEL 5.1.0

[José Bollo <jose.bollo@xxxxxxx>]

On Fri, 12 Oct 2018 16:20:28 +0530
Madhu B <madhu1313b@xxxxxxxxx> wrote:

> Hi all,
>           Finally I've expanded the root partition to 6GB using
> GParted. This time luckily,root partition data is not
> corrupted.Successfully downloaded Japan map data in the root
> directory. Launching Navigation application shows, the layout of
> Japan Map.

Hi Madhu,

A good thing at the end, your effort paid.

> Earlier, I was assumed that the navigation application is equivalent
> to Google maps, but it is not like that. Suppose, if I want India Map
> on navigation application, first I need to download the India Map on
> AGL system. If my understanding is correct, why the navigation
> application is not implemented like Google maps? or still development
> is going on for navigation app.

I'm not the expert but... AGL is an open source project. The current
navigation application was given to AGL. If some one offers an other
open-source navigation application it is cool.

About "like google map", a connected car is not always connected. So AGL
better have to bring a solution that can work without connectivity.

> AGL system crashes after some time of launching Navigation
> application with the following journalctl log:

The segfault is linked to disconnection of the compositor. After that
the binder complains to be in an unexpected state indefinitely. The
latest version, FF, the binder will exit when it encounter that state
that it can't recover. This happens when a systemd callback crashes
(the SEGV). Binders try to recover but the main loop of libsystemd is
in an unrecoverable state.

Best regards
José Bollo

> Oct 12 10:30:28 raspberrypi3 afbd-homescreen-2017@0.1[643]:
> "HomeScreen" Oct 12 10:30:42 raspberrypi3 afbd-navigation@0.1[867]:
> Event_TapShortcut application_name = Navigation
> Oct 12 10:30:42 raspberrypi3 afbd-navigation@0.1[867]: try to
> activesurface Navigation
> Oct 12 10:30:42 raspberrypi3 afbd-navigation@0.1[867]: Surface
> Navigation got syncDraw! Area: normal.full.
> Oct 12 10:30:42 raspberrypi3 afbd-navigation@0.1[867]:
> Layout:normal.full x:0 y:0 w:1080 h:1488
> Oct 12 10:30:42 raspberrypi3 afbd-homescreen-2017@0.1[643]:
> "Navigation" Oct 12 10:30:42 raspberrypi3 afbd-navigation@0.1[867]:
> Surface Navigation got visibled!
> Oct 12 10:30:42 raspberrypi3 afbd-navigation@0.1[867]: Surface
> Navigation got activated!
> Oct 12 10:30:42 raspberrypi3 afbd-navigation@0.1[867]: Surface
> Navigation got flushdraw!
> Oct 12 10:31:21 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> [2528161.341] [wm ERROR] [main.cpp, display_event_callback(),
> Line:61] >>> The compositor hung up, dying now.
> Oct 12 10:31:21 raspberrypi3 afbd-homescreen-2017@0.1[643]: The
> Wayland connection broke. Did the Wayland compositor die?
> Oct 12 10:31:21 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> ERROR: ALERT! signal 11 received: Segmentation fault
> [/usr/src/debug/af-binder/eel+gitAUTOINC+c7a0a6b6b2-r0/git/src/sig-monitor.c:225,on_signal_error]
> Oct 12 10:31:21 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> ERROR: BACKTRACE due to signal Segmentation fault/11:
> Oct 12 10:31:21 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> [/usr/src/debug/af-binder/eel+gitAUTOINC+c7a0a6b6b2-r0/git/src/sig-monitor.c:77,dumpstack]
> Oct 12 10:31:21 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> ERROR: sd_event_prepare returned an error (state: 3): Device or
> resource busy
> [/usr/src/debug/af-binder/eel+gitAUTOINC+c7a0a6b6b2-r0/git/src/jobs.c:276,evloop_run]
> Oct 12 10:31:21 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> ERROR: sd_event_prepare returned an error (state: 3): Device or
> resource busy
> [/usr/src/debug/af-binder/eel+gitAUTOINC+c7a0a6b6b2-r0/git/src/jobs.c:276,evloop_run]
> Oct 12 10:31:21 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> ERROR: sd_event_prepare returned an error (state: 3): Device or
> resource busy
> [/usr/src/debug/af-binder/eel+gitAUTOINC+c7a0a6b6b2-r0/git/src/jobs.c:276,evloop_run]
> Oct 12 10:31:22 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> ERROR: sd_event_prepare returned an error (state: 3): Device or
> resource busy
> [/usr/src/debug/af-binder/eel+gitAUTOINC+c7a0a6b6b2-r0/git/src/jobs.c:276,evloop_run]
> Oct 12 10:31:22 raspberrypi3 afbd-windowmanager-service-2017@0.1[647]:
> ERROR: sd_event_prepare returned an error (state: 3): Device or
> resource busy
> [/usr/src/debug/af-binder/eel+gitAUTOINC+c7a0a6b6b2-r0/git/src/jobs.c:276,evloop_run]
> 
> 
> Regards,
> -Madhu.
> 
> 
> On Fri, Oct 12, 2018 at 7:55 AM <I37546_CHIN@xxxxxxxxxxxxxx> wrote:
> 
> > Hi Madhu
> >
> >
> >
> > I’m not sure this could help,
> >
> > but as download_mapdata_jp.sh will download a tar file and then
> > extract it, maybe more than 4GByte is needed.
> >
> > If the installation was aborted for that reason, you can run the
> > script on your host build machine instead of your target board.
> >
> >
> >
> > Be careful that, the script accepts an argument for its target path
> > of extract and you need to set it to root of your target.
> >
> >
> >
> > Thanks/BR
> >
> > ChenWei
> >
> > *From:* Marc Murphy [mailto:marc.murphy@xxxxxxxxxxxxxx]
> > *Sent:* Thursday, October 11, 2018 10:07 PM
> > *To:* Madhu B
> > *Cc:* I37546 Chin I; jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0
> >
> >
> >
> > Hi Madhu
> >
> >
> >
> > You can also use fstab to use a file system folder as a mount point.
> >
> >
> >
> > In the example I sent you can see I have used it for some
> > NetworkManager settings
> >
> > /mnt/NetworkManager     /var/lib/NetworkManager         auto
> > defaults,nofail,nobootwait,bind 0 2
> >
> >
> >
> >
> >
> > /mnt/NetworkManager is the folder where I store the data in the
> > extra partition
> >
> > /var/lib/NetworkManager is the mount point created
> >
> >
> >
> > This is so we can have a read only file system with some folders
> > used for persistent storage over upgrades.  When you plan a file
> > system layout you need to consider what information you can afford
> > to lose and what you want to be able to update.  Using persistent
> > partitions and mount points allows you to update rootfs and still
> > keep data.
> >
> >
> >
> > Kind Regards
> >
> > Marc
> >
> >
> >
> >
> > ------------------------------
> >
> > *From:* Madhu B <madhu1313b@xxxxxxxxx>
> > *Sent:* 11 October 2018 13:54:45
> > *To:* Marc Murphy
> > *Cc:* I37546_CHIN@xxxxxxxxxxxxxx; jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0
> >
> >
> >
> > Hi Marc,
> >
> >             As the earlier image corrupted, I've flashed the image
> > once again. The SDcard have 4GB space on newly created partition.
> >
> > The Navigation application is expecting navi_data under home
> > directory, due to that I've created the symbolic link under home
> > directory.What you mean by "mounting /var/mapdata to a folder on
> > your new partition"? mapdata is a folder not a block device.
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > On Thu, Oct 11, 2018 at 6:07 PM Marc Murphy
> > <marc.murphy@xxxxxxxxxxxxxx> wrote:
> >
> > Have you cleaned out /var/mapdata from the last boot where you
> > attempted to download and it got to 12% ?
> >
> >
> >
> > have  a look at df to see what space you have.
> >
> >
> >
> > You could still have a full file system that the app needs to write
> > some data to.
> >
> >
> >
> > You cold try mounting /var/mapdata to a folder on your new
> > partition, that will give working space.
> >
> >
> >
> > Kind Regards
> >
> > Marc
> > ------------------------------
> >
> > *From:* Madhu B <madhu1313b@xxxxxxxxx>
> > *Sent:* 11 October 2018 13:07:29
> > *To:* Marc Murphy
> > *Cc:* I37546_CHIN@xxxxxxxxxxxxxx; jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0
> >
> >
> >
> > Hi Marc,
> >
> >              Now the boot failure issue resolved with the usage of
> > /dev/mmcblk instead of UUID in fstab file. Made an symbolic link to
> > /mnt/HDD/var/mapdata/navi_data folder under home directory, But
> > still launching navigation app returns to home screen.
> >
> >
> >
> > It's journal cat log is:
> >
> > Oct 11 11:59:06 raspberrypi3 afbd-navigation@0.1[810]: start gps
> > navi Oct 11 11:59:06 raspberrypi3 afbd-navigation@0.1[810]: NAVI
> > port = 1046 Oct 11 11:59:06 raspberrypi3 afbd-navigation@0.1[810]:
> > NAVI token = HELLO Oct 11 11:59:07 raspberrypi3
> > afbd-navigation@0.1[810]: navi - sample GPS Navigation Version
> > 0.0.7 (build 031 Oct  8 2018) Oct 11 11:59:07 raspberrypi3
> > afbd-navigation@0.1[810]: libEGL warning: MESA-LOADER: device is
> > not located on the PCI bus Oct 11 11:59:07 raspberrypi3
> > afbd-navigation@0.1[810]: MESA-LOADER: device is not located on the
> > PCI bus Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > MESA-LOADER: device is not located on the PCI bus
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]: NC_Initialize
> > error.
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:  user data
> > path(/home/navi_data/japan_TR9/Data)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:  map  db
> > path(/home/navi_data/japan_TR9/Map/JPN/)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > navi_config_path             (/home/navi_data/japan_TR9/)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > navi_config_map_db_path      (/home/navi_data/japan_TR9/Map/JPN/)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > navi_config_user_data_path   (/home/navi_data/japan_TR9/Data)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > navi_config_map_udi_data_path(/home/navi_data/japan_TR9/Data/MD/UDI/)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > navi_config_map_udi_info_file(/home/navi_data/japan_TR9/Data/MD/UDI/udi_info)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > navi_config_map_font_file
> > (/home/navi_data/japan_TR9/IPAfont00303/ipagp.ttf)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > EGL_VERSION    = 1.4 (DRI2)
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > EGL_VENDOR     = Mesa Project
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]:
> > EGL_CLIENT_APIS= OpenGL OpenGL_ES
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]: navi-core
> > version 0.0.7(Oct  8 2018) , api version 1.0.20160329-00
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]: Copyright (c)
> > 2016  Hitachi, Ltd.
> > Oct 11 11:59:07 raspberrypi3 afbd-navigation@0.1[810]: This program
> > is dual licensed under GPL version 2 or a commercial license.
> >
> >
> >
> > Prior to this, while running ownload_mapdata_jp.sh, I got the
> > following log.
> >
> > root@raspberrypi3:/mnt/HDD# /usr/AGL/apps/download_mapdata_jp.sh ./
> > no map data
> > start downloading...
> > Connecting to agl.wismobi.com (52.219.4.128:80)
> > navi_data.tar.gz      12%
> > |************
> > |   157M  - stalled -
> > map data directory does not exist
> > create a directory .//var/mapdata
> > navi_data/japan_TR9/Data/MD/UDI/24.png
> > navi_data/HMI/23.png
> > navi_data/japan_TR9/Map/JPN/Config/DataManagerConfig.ini
> > navi_data/japan_TR9/Map/JPN/Config/RouteCost/
> > navi_data/japan_TR9/Data/MD/UDI/2.png
> > navi_data/japan_TR9/Map/JPN/TTS/
> > navi_data/japan_TR9/Data/MD/UDI/86.png
> > navi_data/japan_TR9/Data/MD/UDI/10.png
> > navi_data/japan_TR9/Data/MD/UDI/67.png
> > navi_data/japan_TR9/
> > navi_data/japan_TR9/Data/MD/UDI/91.png
> > navi_data/japan_TR9/Data/MD/UDI/48.png
> > navi_data/japan_TR9/Map/JPN/Log/
> > navi_data/japan_TR9/Data/MD/UDI/72.png
> > navi_data/HMI/28.png
> > navi_data/
> > navi_data/japan_TR9/Data/MD/UDI/53.png
> > navi_data/HMI/
> > navi_data/HMI/3.png
> > navi_data/japan_TR9/Data/MD/UDI/34.png
> > navi_data/japan_TR9/Data/MD/UDI/7.png
> > navi_data/japan_TR9/Map/JPN/Polaris.db
> > tar: unexpected end of file
> > tar: short read
> > done..
> >
> >
> >
> > The above log shows that the installation of mapdata ended with some
> > errors(stalled).
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > On Thu, Oct 11, 2018 at 5:05 PM Marc Murphy
> > <marc.murphy@xxxxxxxxxxxxxx> wrote:
> >
> > Hi Madhu
> >
> >
> >
> > I have had issues on embedded systems in the past with UUID and
> > resorting to the /dev/mmcblk device made it work.
> >
> >
> >
> > Give it a try and see.  The use of /dev/mmcblk is also more
> > flexible for portability if you are to copy file system images.
> >
> >
> >
> > Kind Regards
> >
> > Marc
> >
> >
> > ------------------------------
> >
> > *From:* Madhu B <madhu1313b@xxxxxxxxx>
> > *Sent:* 11 October 2018 12:21:45
> > *To:* Marc Murphy
> > *Cc:* I37546_CHIN@xxxxxxxxxxxxxx; jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0
> >
> >
> >
> > Hi Marc,
> >
> >              I've used the UUID of the /dev/mmcblkxx instead of
> > it's name directly as specified in
> > https://www.raspberrypi.org/documentation/configuration/external-storage.md.
> > Is there any issue, if we use UUID instead of block device
> > name(/dev/mmcblkxx)?
> >
> >
> >
> > My /etc/fstab file is
> >
> >
> >
> > # stock fstab - you probably want to override this with a machine
> > specific one
> >
> > /dev/root            /                    auto       defaults
> > 1  1
> > proc                 /proc                proc       defaults
> > 0  0
> > devpts               /dev/pts             devpts     mode=0620,gid=5
> > 0  0
> > tmpfs                /run                 tmpfs
> > mode=0755,nodev,nosuid,strictatime 0  0
> > tmpfs                /var/volatile        tmpfs      defaults
> > 0  0
> >
> > # uncomment this if your device has a SD/MMC/Transflash slot
> > #/dev/mmcblk0p1       /media/card          auto
> > defaults,sync,noauto  0  0
> >
> > UUID=1195b956-784f-4ea3-8783-238ef368235a /mnt/HDD ext4
> > defaults,auto,umask=000,users,rw 0 0
> >
> >
> >
> > The last statement is for mounting the new partition.
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > ---------- Forwarded message ---------
> > From: *Marc Murphy* <marc.murphy@xxxxxxxxxxxxxx>
> > Date: Thu, Oct 11, 2018 at 4:40 PM
> > Subject: Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0 (Madhu B)
> > To: Madhu B <madhu1313b@xxxxxxxxx>
> > Cc: I37546_CHIN@xxxxxxxxxxxxxx <I37546_CHIN@xxxxxxxxxxxxxx>,
> > jasonr@xxxxxxxxxxxxxxxxxxx <jasonr@xxxxxxxxxxxxxxxxxxx>,
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx <
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >
> >
> >
> > Can you post your fstab?
> >
> >
> >
> > You shouldn't need to use the UUID, there should be a /dev/mmcblk
> > entry for the new partition, use that.
> >
> >
> >
> > Can be done like this:
> >
> > # <file system>         <mount pt>                      <type>
> > <options> <dump>  <pass>
> >
> > /dev/root               /                               ext4
> > rw,noauto 0       1
> >
> > /dev/mmcblk0p3          /mnt                            ext4
> > defaults 0       0
> >
> > proc                    /proc                           proc
> > defaults 0       0
> >
> > devpts                  /dev/pts                        devpts
> > defaults,gid=5,mode=620 0       0
> >
> > tmpfs                   /dev/shm                        tmpfs
> > mode=0777 0       0
> >
> > tmpfs                   /tmp                            tmpfs
> > mode=1777 0       0
> >
> > tmpfs                   /run                            tmpfs
> >  mode=0755,nosuid,nodev  0       0
> >
> > tmpfs                   /media                          tmpfs
> >  mode=0755,nosuid,nodev  0       0
> >
> > sysfs                   /sys                            sysfs
> > defaults 0       0
> >
> > /dev/mmcblk0p2          /home                           ext4
> > defaults 0       0
> >
> > /mnt/NetworkManager     /var/lib/NetworkManager         auto
> > defaults,nofail,nobootwait,bind 0 2
> >
> > /mnt/pgsql              /var/lib/pgsql                  auto
> > defaults,nofail,nobootwait,bind 0 2
> >
> > /dev/mmcblk0p4          /users                           ext4
> > defaults 0       0
> >
> >
> >
> > Cheers
> >
> > Marc
> > ------------------------------
> >
> > *From:* Madhu B <madhu1313b@xxxxxxxxx>
> > *Sent:* 11 October 2018 11:50:16
> > *To:* Marc Murphy
> > *Cc:* I37546_CHIN@xxxxxxxxxxxxxx; jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0 (Madhu B)
> >
> >
> >
> > No, it is not working. As I said earlier, it results in boot
> > failure.
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > On Thu, Oct 11, 2018 at 4:16 PM Marc Murphy
> > <marc.murphy@xxxxxxxxxxxxxx> wrote:
> >
> > So is it working properly now?
> >
> > I tend to use fdisk and mkfs for partition creation on the device.
> >
> >
> >
> > Kind Regards
> >
> > Marc
> > ------------------------------
> >
> > *From:* Madhu B <madhu1313b@xxxxxxxxx>
> > *Sent:* 11 October 2018 11:17:23
> > *To:* Marc Murphy
> > *Cc:* I37546_CHIN@xxxxxxxxxxxxxx; jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0 (Madhu B)
> >
> >
> >
> > Hi Marc,
> >
> >            I am able to mount it manually, ran the
> > download_mapdata_jp.sh there(mapdate extracted under /mnt/HDD/var
> > directory).  I've created a new partition of size 4GB(total SDcard
> > size is 16GB) with ext4 as file-system type using *GParted*.
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > On Thu, Oct 11, 2018 at 3:33 PM Marc Murphy
> > <marc.murphy@xxxxxxxxxxxxxx> wrote:
> >
> > Hi Madhu
> >
> > Have you tried to mount it manually to check and have you also
> > created a file system on the new partition?  If not you need to
> > format it.
> >
> >
> >
> > Kind Regards
> > Marc
> >
> >
> > ------------------------------
> >
> > *From:* Madhu B <madhu1313b@xxxxxxxxx>
> > *Sent:* 11 October 2018 10:58:31
> > *To:* Marc Murphy
> > *Cc:* I37546_CHIN@xxxxxxxxxxxxxx; jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0 (Madhu B)
> >
> >
> >
> > Hi all,
> >
> >          I've created a new partition on the SDcard and mounted it
> > to /mnt/HDD. For automatic mounting, modified the /etc/fstab file by
> > referring  link:
> > https://www.raspberrypi.org/documentation/configuration/external-storage.md.
> > This will causing the boot failure on the Raspberry Pi3.
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > On Thu, Oct 11, 2018 at 2:29 PM Marc Murphy
> > <marc.murphy@xxxxxxxxxxxxxx> wrote:
> >
> > You could look at creating an additional partition of 2GB to store
> > the navigation data.  Mount it and then use a symbolic file link to
> > reference it.
> >
> >
> >
> > Kind Regards
> >
> > Marc
> > ------------------------------
> >
> > *From:* automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx <
> > automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx> on behalf
> > of Madhu B <madhu1313b@xxxxxxxxx>
> > *Sent:* 11 October 2018 09:45:18
> > *To:* I37546_CHIN@xxxxxxxxxxxxxx
> > *Cc:* jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0 (Madhu B)
> >
> >
> >
> > Thanks ChenWei, I'll look into it.
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > On Thu, Oct 11, 2018 at 1:50 PM <I37546_CHIN@xxxxxxxxxxxxxx> wrote:
> >
> > Hi Madhu
> >
> >
> >
> > Original build image will just make a partition about 3GBytes for
> > my M3 board, so I’ve also experienced the same issue.
> >
> > But my data is luckily not broken when using the same GPARTED.
> >
> >
> >
> > I think there should be a configuration for that size but sorry to
> > say I don’t know how to change it.
> >
> >
> >
> > Thanks/BR
> >
> > ChenWei
> >
> > *From:* Madhu B [mailto:madhu1313b@xxxxxxxxx]
> > *Sent:* Thursday, October 11, 2018 3:30 PM
> > *To:* I37546 Chin I
> > *Cc:* jasonr@xxxxxxxxxxxxxxxxxxx;
> > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx; I25461 Momiyama
> > Yoshito *Subject:* Re:  Navigation app is not
> > launching on RaspberryPi3 with EEL 5.1.0 (Madhu B)
> >
> >
> >
> > Hi ChenWei,
> >
> >                   Execution of download_mapdata_jp.sh script stops
> > due to No space left on device. Expanded the root partition of the
> > SD card using gparted, but it results in losing of data on the root
> > partition. After that, Home screen don't showing remaining
> > application icons on display.
> >
> >
> >
> > How to expand the root partition of the SD card for AGL without
> > losing the data? Is there any utility on AGL like raspi-config on
> > Raspbian?
> >
> >
> >
> > Thanks,
> >
> > -Madhu.
> >
> >
> >
> > On Wed, Oct 10, 2018 at 1:16 PM <I37546_CHIN@xxxxxxxxxxxxxx> wrote:
> >
> > Hi Madhu
> >
> >
> >
> > download_mapdata_jp.sh
> >
> > is needed to download map data (about 1GByte) for the Navigation
> > App.
> >
> > Please run this script before starting the App.
> >
> >
> >
> > Usually it should be installed by recipes-demo-hmi/navigation/
> > navigation_git.bb.
> >
> > You can also find it in recipes-demo-hmi/navigation/navigation.
> >
> >
> >
> > Thanks/BR
> >
> > ChenWei
> >
> > *From:* automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx
> > [mailto: automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx]
> > *On Behalf Of *Madhu B
> > *Sent:* Wednesday, October 10, 2018 3:04 PM
> > *To:* jasonr@xxxxxxxxxxxxxxxxxxx
> > *Cc:* automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* Re:  Navigation app is not launching on
> > RaspberryPi3 with EEL 5.1.0 (Madhu B)
> >
> >
> >
> > Hi Jason,
> >
> >                My image have  QtLocation and QtPositioning folders
> > under /usr/lib/qt5/qml/ and it also have the folders you've
> > mentioned in
> > https://lists.linuxfoundation.org/pipermail/automotive-discussions/2018-September/006659.html .
> >
> >
> >
> > But it don't have the script
> > file /usr/AGL/apps/download_mapdata_jp.sh. How to get this file?
> > What is the necessary of that script file?
> >
> >
> >
> > Regards,
> >
> > -Madhu.
> >
> >
> >
> > On Wed, Oct 10, 2018 at 5:59 AM Jason Reich
> > <jasonr@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > Hi Madhu,
> >
> > I've seen a problem with the Nav app on M3+KF as well, and this
> > could be the problem with the RPi, but I don't have that setup to
> > test.
> >
> >
> >
> > On the M3 build, the FF image was missing the Qt libraries and
> > modules for navigation and positioning.  This allowed the Nav app
> > to start, but failed quickly.
> >
> >
> >
> > I posted about this on Sept 20, but did not receive any responses.
> > Here is my message:
> >
> >
> > https://lists.linuxfoundation.org/pipermail/automotive-discussions/2018-September/006659.html
> >
> >
> >
> > Take a look on your image, and see if /usr/lib/qt5/qml/ has
> > QtLocation or QtPositioning, or any of the other files I mention in
> > the email.  My app works once I manually copied those files from my
> > SDK docker image onto the board.
> >
> >
> >
> > Also, for the Nav app to work, you must load the maps onto your
> > image, using the /usr/AGL/apps/download_mapdata_jp.sh script.
> >
> >
> >
> > Hope that helps,
> >
> > Jason.
> >
> >
> > ------------------------------
> >
> > *From:* automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx <
> > automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx> on behalf
> > of automotive-discussions-request@xxxxxxxxxxxxxxxxxxxxxxxxx <
> > automotive-discussions-request@xxxxxxxxxxxxxxxxxxxxxxxxx>
> > *Sent:* Tuesday, October 9, 2018 3:02 AM
> > *To:* automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > *Subject:* automotive-discussions Digest, Vol 69, Issue 20
> >
> >
> >
> > Message: 2
> > Date: Tue, 9 Oct 2018 15:29:58 +0530
> > From: Madhu B <madhu1313b@xxxxxxxxx>
> > To: automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> > Subject:  Navigation app is not launching on
> >         RaspberryPi3    with EEL 5.1.0
> > Message-ID:
> >         <CAH5YvUs=
> > po4x2dpnu9K+iVJpjxVXVQd-772D43QYJY0scpyy_A@xxxxxxxxxxxxxx>
> > Content-Type: text/plain; charset="utf-8"
> >
> > I've build the AGL image for Raspberry Pi3 on Ubuntu 14.04.
> >  Whenever I am trying to launch Navigation application on
> > RaspberryPi3, it is not working as expected(returning to home
> > screen) and it's journalctl log is
> >
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]: start gps
> > navi Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]: NAVI
> > port = 1046 Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > NAVI token = HELLO Oct 09 04:59:35 raspberrypi3
> > afbd-navigation@0.1[862]: navi - sample GPS Navigation Version
> > 0.0.7 (build 031 Oct  8 2018) Oct 09 04:59:35 raspberrypi3
> > afbd-navigation@0.1[862]: libEGL warning: MESA-LOADER: device is
> > not located on the PCI bus Oct 09 04:59:35 raspberrypi3
> > afbd-navigation@0.1[862]: MESA-LOADER: device is not located on the
> > PCI bus Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > MESA-LOADER: device is not located on the PCI bus
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]: NC_Initialize
> > error.
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:  user data
> > path(/home/navi_data/japan_TR9/Data)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:  map  db
> > path(/home/navi_data/japan_TR9/Map/JPN/)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > navi_config_path             (/home/navi_data/japan_TR9/)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > navi_config_map_db_path      (/home/navi_data/japan_TR9/Map/JPN/)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > navi_config_user_data_path   (/home/navi_data/japan_TR9/Data)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > navi_config_map_udi_data_path(/home/navi_data/japan_TR9/Data/MD/UDI/)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> >
> > navi_config_map_udi_info_file(/home/navi_data/japan_TR9/Data/MD/UDI/udi_info)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > navi_config_map_font_file
> > (/home/navi_data/japan_TR9/IPAfont00303/ipagp.ttf)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > EGL_VERSION    = 1.4
> > (DRI2)
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > EGL_VENDOR     = Mesa Project
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]:
> > EGL_CLIENT_APIS= OpenGL OpenGL_ES
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]: navi-core
> > version 0.0.7(Oct  8 2018) , api version 1.0.20160329-00
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]: Copyright
> > (c) 2016 Hitachi, Ltd.
> > Oct 09 04:59:35 raspberrypi3 afbd-navigation@0.1[862]: This program
> > is dual
> > licensed under GPL version 2 or a commercial license.
> >
> > What is wrong with the navigation application?
> >
> >  

_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions