Forums - Building image for Snapdragon 855 devkit

2 posts / 0 new
Last post
Building image for Snapdragon 855 devkit
max.kolesin
Join Date: 26 Jan 21
Posts: 1
Posted: Tue, 2021-01-26 07:43

Hello,

 

I'm trying to build Android image for Snapdragon 855 devkit. Wasnt able to find a lot of docs online, here's what I've tried so far.

According to device target that board reports when trying to flash it, which is msmnile, I've tried cloning source code from codeaurora with a manifest LA.UM.9.1.r1-08300-SMxxx0.0.xml (according to https://wiki.codeaurora.org/xwiki/bin/QAEP/release)

> repo init -u git://codeaurora.org/platform/manifest.git -b release -m LA.UM.9.1.r1-08300-SMxxx0.0.xml

That results in an error:
Downloading Repo source from https://gerrit.googlesource.com/git-repo
remote: Counting objects: 3, done
remote: Finding sources: 100% (152/152)
remote: Total 152 (delta 107), reused 152 (delta 107)
Receiving objects: 100% (152/152), 109.38 KiB | 3.65 MiB/s, done.
Resolving deltas: 100% (107/107), completed with 62 local objects.
Downloading manifest from git://codeaurora.org/platform/manifest.git
remote: Enumerating objects: 212, done.
remote: Counting objects: 100% (212/212), done.
remote: Compressing objects: 100% (182/182), done.
remote: Total 146702 (delta 85), reused 0 (delta 0), pack-reused 146490
Checking out files: 100% (20880/20880), done.
fatal: manifest 'LA.UM.9.1.r1-08300-SMxxx0.0.xml' not available

fatal: manifest LA.UM.9.1.r1-08300-SMxxx0.0.xml not found
In attempt to find what other manifest to use, I've found a telegram channel that reports releases for targets. Latest message for msmnile target there has links to two manifests:

system: https://source.codeaurora.org/quic/la/la/system/manifest/tree/LA.QSSI.11.0.r1-09100-qssi.0.xml
vendor: https://source.codeaurora.org/quic/la/la/vendor/manifest/tree/LA.UM.9.1.r1-08300-SMxxx0.0.xml

I've cloned both manifests, combined these in a single repo and trying to build via
> lunch msmnile-userdebug
> make -j8 dist

This fails with

$ lunch msmnile-userdebug
device/qcom/msmnile/msmnile.mk:102: warning: "Compiling with full value-added framework"
device/qcom/msmnile/msmnile.mk:116: warning: "Enabling codec2.0 non-audio SW only for non-generic odm build variant"

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=11
TARGET_PRODUCT=msmnile
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a9
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-64-generic-x86_64-Ubuntu-18.04.5-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=RKQ1.201217.002
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=hardware/google/av hardware/google/interfaces
============================================

$ make -j8 dist
device/qcom/msmnile/msmnile.mk:102: warning: "Compiling with full value-added framework"
device/qcom/msmnile/msmnile.mk:116: warning: "Enabling codec2.0 non-audio SW only for non-generic odm build variant"
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=11
TARGET_PRODUCT=msmnile
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a9
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-64-generic-x86_64-Ubuntu-18.04.5-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=RKQ1.201217.002
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=hardware/google/av hardware/google/interfaces
============================================
[ 70% 126/180] test android/soong/cc/config
Clang SA is not enabled
PASS
[ 92% 166/180] test android/soong/cc
Clang SA is not enabled
PASS
[ 92% 167/180] test android/soong/bpf
Clang SA is not enabled
PASS
[ 94% 170/180] test android/soong/rust
Clang SA is not enabled
PASS
[ 96% 174/180] test android/soong/java
Clang SA is not enabled
PASS
[ 97% 175/180] test android/soong/sysprop
Clang SA is not enabled
PASS
[ 97% 176/180] test android/soong/aidl
Clang SA is not enabled
PASS
[ 98% 177/180] test android/soong/apex
Clang SA is not enabled
PASS
[ 98% 178/180] test android/soong/sdk
Clang SA is not enabled
PASS
[100% 180/180] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
Clang SA is not enabled
error: vendor/qcom/opensource/vibrator/aidl/Android.bp:4:1: "vendor.qti.hardware.vibrator.impl" depends on undefined module "libsoc_helper"
error: vendor/qcom/opensource/commonsys/fm/fm_hci/Android.bp:3:1: "libfm-hci" depends on undefined module "[email protected]"
12:41:42 soong bootstrap failed with: exit status 1
Does this error mean I'm missing something and need extra bits for the repo? If yes where should i get these missing targets from? If not what could be the problem?
 
Thanks in advance.

 

  • Up0
  • Down0
yps.gamer
Join Date: 4 Mar 21
Posts: 1
Posted: Thu, 2021-03-04 21:33

Please make sure your AOSP source code have bleow folder:

vendor/qcom/proprietary

above folder should copy from NONHLOS's LINUX/android/vendor/qcom/proprietary

You need to download nonhlos part from Qualcomm and copy it to AOSP.

 

  • 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.