AIM-Linux/BSP/Qualcomm/RISC QCS Yocto LE1.1 ROM2860
Contents
Introduction
This document describes how to work with the RISC and Qualcomm LE GA1.1 Board Support Package (BSP) release.
Yocto Version
Yocto 4.0.18
Kernel Version
Kernel 6.6.28
Meta Build ID
QCM6490.LE.1.0-00218-STD.PROD-1
Docker Install and BSP Download
Pull docker images
$ sudo docker pull advrisc/u20.04-qcslbv2:latest
Run docker example
$ mkdir -p /home/bsp/myLinux $ sudo docker run --privileged -it --name qclinux -v /home/bsp/myLinux:/home/adv/BSP:rw advrisc/u20.04-qcslbv2 /bin/bash adv@7cc0fa834366:~$ sudo chown adv:adv -R BSP
Download BSP
You need to get the ADV_GIT_TOKEN by contacting the PM or AE of ROM-2860.
$ cd /home/adv/BSP $ git config --global credential.helper 'store --file ~/.my-credentials' $ echo "https://AIM-Linux:${ADV_GIT_TOKEN}@dev.azure.com" > ~/.my-credentials $ repo init -u https://dev.azure.com/AIM-Linux/risc_qcs_linux_le_1.1/_git/manifest -b main -m adv-6.6.28-QLI.1.1-Ver.1.1_robotics-product-sdk-1.1.xml $ repo sync -c -j12
Get and Unzip the Download Files
LIV11 yocto downloads file:[ downloads.qcs6490.le.1.1.r00041.0.tar ]
$ cd /home/adv/BSP $ tar -zxvf downloads.qcs6490.le.1.1.r00041.0.tar
Build Instructions
Source env
$ source scripts/env.sh
Build All Images
$ scripts/build_release.sh -all
- Output ufs images: build-qcom-robotics-ros2-humble/tmp-glibc/deploy/images/qcm6490/qcom-robotics-full-image
- Output emmc images: build-qcom-robotics-ros2-humble/tmp-glibc/deploy/images/qcm6490/qcom-robotics-full-image-emmc
Build All Images individually
1. Build ADSP Image
$ scripts/build_release.sh -adsp
2. Build AOP Image
$ scripts/build_release.sh -aop
3. Build CDSP Image
$ scripts/build_release.sh -cdsp
4. Build BOOT(XBL) Image
$ scripts/build_release.sh -boot
5. Build TZ Image
$ scripts/build_release.sh -tz
6. Generate Firmware Prebuilds
$ scripts/build_release.sh -common
7. Build YOCTO Image
$ scripts/build_release.sh -yocto
Build yocto images
$ cd /home/adv/BSP $ MACHINE=qcm6490 DISTRO=qcom-robotics-ros2-humble source setup-robotics-environment $ devtool modify qps615 $ ../qirp-build qcom-robotics-full-image
Recovery & Rescue
Using windows PCAT or Qualcomm Download (QDL) tool to flash software images to the device.
Get the official images and unzip
Release image URL: OS Support List(LE1.1 based on Yocto4.0)
Unzip command example:
$ sudo tar -zxvf 2860A1AIM38LIV11030_emmc_2024-11-18.tgz
Enter 9008 download mode
- Connect the Micro USB (EDL) to your host computer.
- Forced Recovery: The SW2 switch to 1-on.
- Flash EMMC: the SW1 switch to 1-off, 2-on
- Flash UFS: the SW1 switch to 1-on, 2-on
- Connect the adapter and power on the device
Use the windows PCAT to flash images
1. Download the Qualcomm Software Center
2. Open the Qualcomm Software Center
3. Search "PCAT" in the search bar
4. Click Qualcomm® Product Configuration Assistant Tool
5. Select Qualcomm® Product Configuration Assistant Tool version
Version: 2.33.2.119
6. Install Qualcomm® Product Configuration Assistant Tool 2.33.2.119
7. Search "QUTS" in the search bar
8. Click the Qualcomm® Unified Tools Services
9. Select Qualcomm® Unified Tools Services version
Version : 1.75.2.9
10. Install Qualcomm® Unified Tools Services 1.75.2.9
11. You will find the new application in your Windows system .
12. Unzip the UFS File and eMMC File
For example :
2860A1AIM37UIV10084_2024-08-08_ufs_debug.tgz
2860A1AIM37UIV10084_2024-08-08_emmc_debug.tgz
13 Connect your device via Micro USB.
USF Provision
2. Add the prog_firehose_ddr.elf and provision_ufs31.xml in UFS folder.
3. Then press "OK" , it will start to do USF Provision.
4. When the Provision finished , you can see the result in message window.
Flash UFS
1. Change the SW1 and SW2
Flash UFS: the SW1 switch to 1-on, 2-on
Forced Recovery : The SW2 switch to 1-on ,2 - on .
2. Turn on the power
3. Open " PCATApp" Tool
4. Click " Connect A Device"
5. Select "Qualcomm HS-USB QDLoader 9008 (COM6)
6. Click " Connect " device
7. When you connected successfully , it will show "green word" - Qualcomm HS-USB QDLoader 9008 (COM 6)
8. Select UFS Folder in PCAT Tool , the Tool will help load Files automatically and Select "MEMORY_TYPE_UFS"
9. Click " Download"
10. UFS Download Status
Flash eMMC
1. Turn off the Power
2. Change the SW1 and SW2
Flash eMMC: The SW1 switch to 1-off, 2-on
Forced Recovery : The SW2 switch to 1-on, 2-on
3. Turn on the power
4. Make sure the device connection status.
5. If the device disconnect with PCAT Tool , please connect it again.
6. Select eMMC Folder.
7. Make sure the setting ,then press " Download " button.
8. eMMC downlaoad status
' 9. eMMC D'onwload compeleted
10. When the eMMC installation finished . Close the PCAT tool ,
11. pleaes remove the mirco usb cable, turn off the power
12. eMMC boot up :
The SW1 switch to 1-off, 2-on , 2-on
The SW2 switch to 1-off , 2-on
13. Connect debug cable and open the terminal , turn on the power .
14. When the systme boot up , you need to type " qcm6490 login: root " , " Password: oelinux123"
15. After type the long in and password , and you also can chek the image information about date , kernel version etc..
Fastboot
- Micro USB: ROM-ED92 USB0
Connect the ROM-ED92 USB0 to host computer and set the Micro USB to peripheral mode.
# echo "peripheral" > /sys/devices/platform/soc/a600000.ssusb/mode
Enter the fastboot mode
adv@adv-desktop:~$ adb devices List of devices attached 2e8c656e device adv@adv-desktop:~$ adb root restarting adbd as root adv@adv-desktop:~$ adb reboot bootloader adv@adv-desktop:~$ fastboot devices 2e8c656e fastboot
Use the fastboot to flash the kernel boot image
adv@adv-desktop:~$ fastboot flash boot_a qti-ubuntu-robotics-image-qcs6490-odk-boot.img target reported max download size of 805306368 bytes sending 'boot_a' (24420 KB)... OKAY [ 0.790s] writing 'boot_a'... OKAY [ 0.144s] finished. total time: 0.935s adv@adv-desktop:~$ fastboot flash boot_b qti-ubuntu-robotics-image-qcs6490-odk-boot.img target reported max download size of 805306368 bytes sending 'boot_b' (24420 KB)... OKAY [ 0.827s] writing 'boot_b'... OKAY [ 0.133s] finished. total time: 0.960s
Use the fastboot to flash the kernel dtbo image
adv@adv-desktop4:~$ fastboot flash dtbo_a dtbo.img target reported max download size of 805306368 bytes sending 'dtbo_a' (12330 KB)... OKAY [ 0.427s] writing 'dtbo_a'... OKAY [ 0.070s] finished. total time: 0.497s adv@adv-desktop4:~$ fastboot flash dtbo_b dtbo.img target reported max download size of 805306368 bytes sending 'dtbo_b' (12330 KB)... OKAY [ 0.422s] writing 'dtbo_b'... OKAY [ 0.061s] finished. total time: 0.483s