Yocto linux build for de SC206E

IoT Modules Smart Module
1

Hello Quectel Team,

I am currently working with the QCM2290 Linux package (qcm2290_linux_r60_r004-SC206E_rl) from your GitLab.

I am new to Yocto and firmware development, and although I have received many PDF documents from your side, I could not find a clear and detailed explanation on how to properly compile the images using Bitbake, nor the specific requirements my host machine needs to meet before starting the process.

At the moment, I am using Ubuntu 22.04 LTS, but I have read in some places that certain Yocto versions might require Ubuntu 20.04 or lower to avoid compatibility issues.

Could you please confirm:

  1. Is Ubuntu 22.04 officially supported for this package? Or should I downgrade to Ubuntu 20.04 or 18.04?
  2. What are the required system dependencies and packages (apt install) that I must install on my host before running Bitbake and building the firmware for SC206E?

Thank you very much in advance for your guidance.

Best regards,

José

2

Ubuntu 22.04 is too high a version. We cannot currently support this high version of Ubuntu to compile SC206E
You can downgrade the host to Ubuntu 16.04 for compilation.

3
  1. What are the required system dependencies and packages (apt install) that I must install on my host before running Bitbake and building the firmware for SC206E?
    Reply:sudo apt-get install python-yaml git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev lib32z1 lib32ncurses5 x11proto-core-dev libx11-dev libxml-simple-perl libc6-dev libgl1-mesa-dev tofrodos python-markdown libxml2-utils xsltproc chrpath gawk texinfo.
4

Hello Quectel Team,

I’m working with the SC206E module using the Yocto distribution qti-distro-rb-debug for the machine qrbx210-rbx.The build completes successfully until it reaches the do_gen_ota_full_zip_ext4 task, which fails with the following error:

openssl dgst -sha256 -sign private.pem -out update.sig
Can't open private.pem for reading, No such file or directory
unable to load key file
OTA zip signing is failed

I have included private.pem in my .bbappend:

FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
SRC_URI += "file://private.pem"

And I have confirmed that:

  • The .bbappend is applied correctly
  • The layer is included in bblayers.conf
  • bitbake -e shows the SRC_URI contains file://private.pem

Yet, during the task, the private.pem file is still not found at runtime in the expected working directory:

.../tmp-glibc/work/qrbx210_rbx-oe-linux/qti-robotics-med-image/1.0-r0/

Can you help identify what I may be missing, or is there a recommended way to ensure private.pem is present at the point the OTA ZIP is signed?

Thanks in advance for your support!

5

Hello again

after lets say i succesfully get the full_update_ext4.zip and update.sig files using the provided OTA scripts. Please still answer the question about the bitbake OTA files

However, on my SC206E EVB, ADB is not available or is not functioning correctly, so I cannot push files via adb push.

I would like to ask:

  1. What is the correct method to update the system using full_update_ext4.zip from an SD card?
  2. Is update_engine included in the default system image? On my device, the update_engine binary is not found, and I can’t proceed with the OTA update.
  3. Are there other alternatives to apply the update via UART or directly from the SD card?

Any help or official guidance would be appreciated.

Best regards,