Forums - Yocto build failure due to missing proprietary packages in qcs610-le-1-0_ap_standard_oem

5 posts / 0 new
Last post
Yocto build failure due to missing proprietary packages in qcs610-le-1-0_ap_standard_oem
prabukumar
Join Date: 8 Feb 21
Posts: 3
Posted: Wed, 2021-04-07 06:28

Hi,

I am trying to build the image for the qcs610-odk-64 machine using the instructions provided in QCS610/QCS410 Linux Platform Development Kit Software Programming Guide (80-pl631-200_k_qcs610_qcs410_linux_platform_development_kit_software_programming_guide.pdf) 

However the build fails due to missing proprietary packages like xmllib, adsprpc etc (almost 15 packages till build failure i.e build continued after error) 

Where can I get the source for the missing packages, so as to avoid this issue ?

Source and other details:

Sources were cloned using the below command:

git clone --depth 1 https://chipcode.qti.qualcomm.com/qualcomm/qcs610-le-1-0_ap_standard_oem.git -b r00070.1
(Checked the latest version in git repo. Has the same issue )
 
Machine: qcs610-odk-64
Distros Tested: qti-distro-fullstack-perf, qti-distro-fullstack-debug
Image: qti-multimedia-image
  • Up1
  • Down0
clavin.rali
Join Date: 18 Jan 21
Posts: 2
Posted: Wed, 2021-04-07 20:32

Try installing these packages,

 

sudo apt-get install git android-tools-adb android-tools-fastboot gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat cpio python python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping libsdl1.2-dev xterm make xsltproc docbook-utils fop dblatex xmlto cmake python-git phablet-tools gdb-multiarch ninja-build

  • Up0
  • Down1
prabukumar
Join Date: 8 Feb 21
Posts: 3
Posted: Wed, 2021-04-07 23:28

I have already installed the pre-requisites. The missing packages I mentioned are source files that are required by qti proprietary recipes 

  • Up1
  • Down0
tamas.bari
Join Date: 9 Dec 20
Posts: 2
Posted: Mon, 2021-07-05 03:45

Hello there!

I have the exact same issue. Did you find a solution?

I'm thinking about using a newer release tag, but it takes ages to try them out.

--

 

  • Up0
  • Down0
m.billa
Join Date: 6 Oct 20
Posts: 1
Posted: Mon, 2021-07-26 05:48
Hi,
I have followed QCS610/QCS410 Linux platform Development Kit Quick Start Guide (80-PL631-300 Rev.G July 1,2020) and the build is successful
 
Here are steps
1.Try installing the following packages on Host system  
sudo apt-get install -y git android-tools-adb android-tools-fastboot gawk wget git-core diffstat unzip texinfo gcc-multilib
build-essential chrpath socat cpio python python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping libsdl1.2-
dev xterm git repo gdb-multiarch default-jdk libxml-simple-perl 
 
From the link Go to Files, select the release and download as zip file
 
3.Download open source software
repo init -u https://source.codeaurora.org/quic/le/le/manifest.git -b release -m LE.UM.4.2.3.r1-03900-QCS610.0.xml --repo-
url=git://codeaurora.org/tools/repo.git --repo-branch=caf-stable 
 
4.repo sync
 
5.cd qcs610-le-1-0_ap_standard_oem/apps_proc
   export SHELL=/bin/bash
   source poky/qti-conf/set_bb_env.sh
 
6.select qcs610_odk meta-qti-bsp from available machines and qti-distro-fullstack-perf meta-qti-bsp from the Available Distributions
   
7.Open <path/to/workspace>/build-qti-distro-fullstack-perf/conf/local.conf.
 
Add the followingg line in the file:
PREBUILT_SRC_DIR="qcs610-le-1-0_ap_standard_oem/apps_proc/prebuilt_HY11"
 
8.bitbake qti-multimedia-image
 
Regards
Mahalaxmi
 
 
  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.