Open cordlandwehr opened 4 months ago
I'd guess that you are trying to boot the apq8096-db820c image (which uses the apq8096-db820c.dtb
) on a phone which has strict DTB requirements. Please open conf/machine/qcom-armv8a.conf
, add qcom/msm8996-oneplus3.dtb
to the KERNEL_DEVICETREE
list, build the image and boot using boot-msm8996-oneplus3-qcom-armv8a.img
. Note, there are two different models: OnePlus 3 and 3T, please choose the correct DTB.
Thanks a lot for the hint! Yet this seems not to work or to not work entirely. I tried with the specific oneplus3 dtb (after confirming that this really is a non-3T variant) and am getting the exact same output as before.
@cordlandwehr you might need to add and/or fix bootloader properties like qcom,msm-id
, qcom-board-id
and qcom,pmic-id
, check them in the downstream tree.
Another suggestion is to ask this quesiton on the #linux-msm channel on OFTC.
Hi, I am trying to ran a meta-qcom build on a spare OnePlus-3 device. I took latest version of meta-qcom as well as a recent version of poky:master branch. From the generated artifacts I try to boot the device via:
So you have any hint why a dtb might not be landed in the img file? The overall Yocto process though complained (warnings) about missing adreno and furth qcom firmware but succeeded without error.