-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
info: flash core-image-minimal into rb3gen2 qcs6490 #616
Comments
Update: Fixing the following issue from: recipes-kernel/images/linux-qcom-uki.bb
I'm able to bitbake esp-qcom-image using that image I can flash efi partition given by the vendor bsp using:
Unfortunately now I'm getting some issue from the kernel that has no bootargs.
I will continue tomorrow :) |
Hi All, Finally I'm able to run the core-image-minimal, below some steps. First of all I flash the qcom yocto image into the the qcs6490rb3gen2 board, or flash the prebuild images. Then:
core-image-minimal logs:
Question:
Thanks in advance, |
@Scott31393 For uki image you should be able to run Regarding HDMI. Unfortunately the HDMI support wasn't backported yet, you can try combining the logic in #593 and the patch at https://lore.kernel.org/linux-arm-msm/[email protected]/ |
Regarding wayland. This question is off-topic for the meta-qcom (it is purely a BSP and doesn't provide any higher-level integration). As a part of the RPB effort we have been providing the RPB-weston image, but this image hasn't been tested for quite a while. |
Hi @lumag,
I will work on fix that, thanks.
Thanks for sharing. Will do a try on this. What about a new machine qcs6490.conf or rb3gen2.conf that inherit from generic qcom-armv8a.conf and put here some board specific customization like: KERNEL_CMDLINE_EXTRA and others? Do you agree on that or I'm completely wrong? Thanks, |
The meta-qcom idea is to have a generic machines only. The rootfs should work on every supported board without the need to further customize it (such customizations often end up being poorly designed or not really fitting).
|
Already saw that, thanks the same. Regards, |
#616 (comment) can anyone provide a more detailed yocto build for qualcomm robotics RB3 gen 2 vision kit |
There is the downstream BSP which was released earlier this month (https://docs.qualcomm.com/bundle/publicresource/topics/80-70014-115/overview.html?product=1601111740013072 and https://github.com/quic-yocto/meta-qcom-hwe / https://github.com/quic-yocto/qcom-manifest). BSP is kirkstone based at the moment (work ongoing to have an updated version). |
can anyone give me the correct machine name for robotics rb3 gen 2 |
how to check pre build images in the qualcomm robotics rb3 gen 3 |
qcm6490 on the downstream BSP. |
For the BSP: https://artifacts.codelinaro.org/artifactory/qli-ci/flashable-binaries/qimpsdk/qcm6490/x86/qcom-6.6.28-QLI.1.1-Ver.1.1_qim-product-sdk-1.1.3.zip -> qcm6490/qcom-multimedia-image. As described at https://docs.qualcomm.com/bundle/publicresource/topics/80-70014-253/ubuntu_host.html?product=1601111740013072 |
I'm encountering an issue where no login page is shown while following the steps described at Qualcomm Documentation. How can I flash the prebuilt images, and where can I find prebuilt images for the Qualcomm Robotics RB3 Gen 2 Vision Kit? |
Would you mind sending your question at https://mysupport.qualcomm.com/supportforums/s/topic/0TO4V000000Ey0jWAC/qualcomm-linux? That would be the proper location for debugging issues with qualcomm linux itself. |
how to remove existing image and flash new image |
Hi All,
Sorry for bothering. I'm working on top of your meta-qcom
My target is to run mainline linux kernel into rb3gen2 (6490) board. I want ask if you can share some guide to flash the yocto images generated with this layer. I'm able to build/flash the qcom bsp based on the following yocto manifest: https://github.com/quic-yocto/qcom-manifest/blob/qcom-linux-kirkstone/qcom-6.6.28-QLI.1.1-Ver.1.1.xml using qdl tool.
My plan is to do a test on mainline linux kernel. I think to flash those images into the board you are using a different partitioning schema with a different approach. When I'm trying to flash the bsp using the following cmd I'm getting:
Qcom bsp is providing efi partition once I flash all the images using qdl.
Maybe I need to build another image?
Do you have some tips/guide to share? :)
Many thanks in advance!
Thanks & Regards,
Tommaso
The text was updated successfully, but these errors were encountered: