UFS provisioning helps divide the storage into several logical unit numbers (LUNs), allowing you to store different types of data separately. This improves access efficiency and system organization.
Note
To download the provision XML file and check the applicability of UFS provisioning for different SoCs, see the UFS Provisioning table in the Software Release Notes.
Ensure that the device is in EDL mode. For more information, see Force device into emergency download mode.
Based on the required SoC, download the respective provision from the UFS Provisioning table in the Software Release Notes.
On Ubuntu host computer
To download the provision file, do the following:
mkdir <provision_download_path>cd <provision_download_path>wget https://artifacts.codelinaro.org/artifactory/codelinaro-le/Qualcomm_Linux/QCS6490/provision.zipunzip provision.zip
To provision UFS, run the following commands:
cd <provision_download_path><qdl_tool_path>/QDL_2.3.9_Linux_x64/qdl --storage ufs prog_firehose_ddr.elf <Provision file>
Example
On windows host computer
Download the provision file by pasting the following link into a browser:
https://artifacts.codelinaro.org/artifactory/codelinaro-le/Qualcomm_Linux/QCS6490/provision.zip
Unzip the downloaded provision file.
Provision UFS by running the following command from the unzipped provision directory:
.<unzipped-QDL-directory-path>\qdl.exe --storage ufs prog_firehose_ddr.elf <Provision file>
Example
.<unzipped-QDL-directory-path>\qdl.exe --storage ufs prog_firehose_ddr.elf provision_1_2.xml
On macOS host computer
Download the provision file by pasting the following link into a browser:
https://artifacts.codelinaro.org/artifactory/codelinaro-le/Qualcomm_Linux/QCS6490/provision.zip
Unzip the downloaded provision file by running the following command:
unzip provision.zip
Move all provision files into the QDL directory or move the QDL tool and associated libraries into the provision directory.
Note
All required QDL binaries and supporting libraries must be present in the execution directory.
Provision UFS by running the following command from the execution directory:
./qdl --storage ufs prog_firehose_ddr.elf <Provision file>Example
./qdl --storage ufs prog_firehose_ddr.elf provision_1_2.xmlAfter successful UFS provision, the following message appears on the screen:
UFS provisioning succeeded
Run the following command from the ADB shell:
adb shell reboot edl
Note
By default, ADB is not enabled on the device. For information on enabling ADB, see How do you install and connect to the android debug bridge (ADB) ?.
A firmware update to the USB controller may solve USB or Ethernet connectivity issues on the Dragonwing RB3 Gen 2 device.
Prerequisites
Ensure that you upgrade the software as described in Update the software before updating the Renesas firmware.
Ensure that you install the ADB tool. Fastboot comes installed along with it.
Connect the device to the Ubuntu host computer using a USB Type-C cable.
Procedure
Download the firmware from https://www.renesas.com/us/en/products/interface/usb-switches-hubs/upd720201-usb-30-host-controller#design_development, register and log in to https://www.renesas.com/.
Rename the downloaded firmware file to renesas_usb_fw.mem .
Connect device to host computer through a USB cable for adb.
Push firmware to device using one of the following commands:
adb push renesas_usb_fw.mem /lib/firmwareOR
scp renesas_usb_fw.mem root@<ip-address-of-device>:/lib/firmwareExample:
scp renesas_usb_fw.mem root@10.92.175.138:/lib/firmware
To activate the firmware, do either of the following options.
Option A: Reboot target for USB type A ports.
Option B: Manually bind the Renesas xHCI driver.
echo "0001:04:00.0" > /sys/bus/pci/drivers/xhci-pci-renesas/bind
Note
To retrieve the device ID, use the following command:
sh-5.3# lspciIn the following sample output,
0001:04:00.0is the device ID.0001:00:00.0 PCI bridge: Qualcomm Technologies, Inc SM8250 PCIe Root Complex [Snapdragon 865/870 5G] 0001:01:00.0 PCI bridge: Toshiba Corporation Device 0623 0001:02:01.0 PCI bridge: Toshiba Corporation Device 0623 0001:02:02.0 PCI bridge: Toshiba Corporation Device 0623 0001:02:03.0 PCI bridge: Toshiba Corporation Device 0623 0001:04:00.0 USB controller: Renesas Electronics Corp. uPD720201 USB 3.0 Host Controller (rev 03) 0001:05:00.0 Ethernet controller: Toshiba Corporation Device 0220 0001:05:00.1 Ethernet controller: Toshiba Corporation Device 0220
Verify firmware enumeration.
dmesg
Install QUD on the host computer to detect the Dragonwing RB3 Gen 2 device.
Note
For Ubuntu 22.04, you may face an issue while installing QUD. To ensure a successful installation, you may need to enroll the public key on your Linux host computer. For more details, follow the steps provided in the README file available in the /opt/QUIC/sign/signReadme.txt directory.
To clone the GitHub repository, run the following commands:
sudo apt install git
sudo git clone https://github.com/quic/quic-usb-drivers.git
cd quic-usb-drivers
To provide executable permissions to the file, run the following command:
sudo chmod +x QcDevDriver.sh
To install the QUD driver, run the following command:
sudo ./QcDevDriver.sh install
To detect the device, run the following command:
lsusb
Sample output
Bus 002 Device 099: ID 05c6:901d Qualcomm, Inc. QCM6490_e05d8b80
Some Qualcomm proprietary tools require an ADB. ADB is a command-line tool that allows communication with the Dragonwing RB3 Gen 2 device. The adb command facilitates various device actions, such as debugging, capturing kernel logs, and pushing applications and files to the device.
Enable ADB on the device
Boot up the device and log in to the serial shell.
Create the following file to enable USB debugging:
touch /etc/usb-debugging-enabled
Choose one of the following options to start ADB:
Option 1: Reboot the device.
Option 2: Start the ADB service without reboot:
systemctl start android-tools-adbd
Note
Once enabled, ADB remains active across reboots. To disable ADB, remove the /etc/usb-debugging-enabled file and then reboot the device.
Install ADB on the host computer
Run the following command on the Linux host computer:
sudo apt install git android-tools-adb android-tools-fastboot wget
To verify the ADB version on the Linux host computer, run the following command:
adb --version
Sample output
Android Debug Bridge version 1.0.39 Version 1:8.1.0+r23-5ubuntu2
Connect to ADB
Figure: Location of the USB Type-C port
Using the USB Type-C cable, connect the Dragonwing RB3 Gen 2 device with the host computer. Ensure that the device displays as an ADB device.
adb devicesSample output
List of devices attached 68f592a device
To enter the shell, run the following command:
adb shellSample output
#
The Vision mezzanine supports interfacing cameras to the Dragonwing RB3 Gen 2 device through two, second-generation gigabit multimedia serial link (GMSL2) camera inputs and five CAM/CSI camera ports. This mezzanine also provides four DMICs, an IMU, compass/magnetometer, and a pressure sensor.
Figure: Vision mezzanine
For more information, see Vision mezzanine.
Follow these steps to connect the Vision mezzanine to the Core Kit. Flash the CDT to update the device configuration based on the new mezzanine. It’s essential to follow these steps because the Core and Vision kits have different CDTs and software.
Flash the Vision Kit CDT, see Flash CDT.
Download and flash the Vision Kit software for your respective host computer, see Update the software.
Note
Ensure that the host computer isn’t running the ModemManager tool, as it interferes with QDL flashing.
If you’re using a Linux distribution with systemd, stop the ModemManager tool using the following command:
sudo systemctl stop ModemManager
If you need ModemManager, restart it after the flashing is complete.
If flashing fails, do the following and retry the flashing procedure:
Power off the device.
Disconnect the device from the host computer.
Restart the host computer.
To disconnect from the current network, run the following command:
nmcli c down QualcommWiFiConnection ‘QualcommWiFi’ successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/1)
To verify the disconnect status, run the following command:
nmcli -p device![]()
To connect to a different Wi-Fi network, run the following command:
nmcli dev wifi connect QualcommAP password XXXXXXXXXDevice ‘wlan0’ successfully activated with ‘6159ac7c-58c2-44fa-938f-45dcb544fac3’.
Minicom is a serial communication program that allows an admin user to interact with the Dragonwing RB3 Gen 2 device through the serial port.
To install Minicom on the Linux host computer, run the following commands:
sudo apt update
sudo apt install minicom
To verify the USB port, run the following command:
ls /dev/ttyUSB*
Sample output
/dev/ttyUSB0
To open Minicom, run the following command:
sudo minicom -s
Select the Down arrow key to select the Serial port setup option.
To set up the serial device configuration, do the following:
Select A on your keyboard to set up the serial device name such as
/dev/ttyUSB0.Select Enter to save the changes.
Select E on your keyboard to set the baud rate. If the baud rate isn’t set to 115200, select the E key again. Select Q on your keyboard to set the configuration to 8N1.
Select Enter to save the changes.
Select F on your keyboard to set the Hardware Flow Control to No.
Note
Ensure that the letters A, E, Q, and F are in uppercase.
![]()
Select Enter to save the changes.
Select the Save setup as dfl option and select Enter.
Select Exit to open the UART console.
Open the serial device and select ENTER to bring up the authentication prompt.
To sign in to the UART console, specify the following:
Sign in: root
Password: oelinux123
Note
If the authentication console doesn’t display as expected, verify the USB connection. If necessary, disconnect and then reconnect the Micro-USB cable.
By default, root users can sign in using the oelinux123 password.
Sign in as a root user.
To change the root password, run the following command:
passwd
Note
This command prompts you to enter a new password.
Sign out using the exit command.
Sign in as root using your new password.
Note
By default, you can sign in as the root user.
To create a non-root user account, run the following command in the shell.
adduser guest
Note
This command prompts you to enter a new password.
Sign out using the exit command.
Sign in to the shell using your new user account credentials.