Skip to main content

5.1.1 Environment Preparation

TogetheROS.Bot supports installation on Ubuntu systems for both RDK and X86 platforms. Installing via DEB packages on Ubuntu is simple and fast. Users who are getting started are recommended to use this installation method.

The following sections describe environment preparation details for RDK and X86 platforms respectively.

RDK Platform

System Installation

Before installing tros.b, it is recommended to upgrade the RDK system image to the latest version. Ubuntu image flashing method:

Note
  • If you are using RDK X3 with a 1.x version system, you need to upgrade the system to 2.x version.
  • For system version checking methods and detailed instructions, please refer to FAQs.

If the image is already installed, you can upgrade using the commands sudo apt update and sudo apt upgrade.

Note

If the sudo apt update command fails or reports an error, please refer to the FAQ section Q10: How to handle apt update command failure or error? for resolution.

Note

If the sudo apt update command fails or reports an error, please refer to the FAQ section Q10: How to handle apt update command failure or error? for resolution.

Note

If the sudo apt update command fails or reports an error, please refer to the FAQ section Q6: How to handle apt update command failure or error? for resolution.

Note

If the sudo apt update command fails or reports an error, please refer to the FAQ section Q6: How to handle apt update command failure or error? for resolution.

System Configuration

After the image is successfully flashed, you need to configure the RDK IP address for daily use. Login username: root, password: root.

Note

To ensure smooth installation and use of tros.b, please log in using the root account.

During experience and development, commands such as scp/ssh are frequently used to access the RDK via IP address. Dynamic configuration is recommended here. Refer to:

Try pinging Baidu server

root@ubuntu:~# ping www.baidu.com
PING www.a.shifen.com (180.101.49.11) 56(84) bytes of data.
64 bytes from 180.101.49.11 (180.101.49.11): icmp_seq=1 ttl=52 time=4.10 ms
64 bytes from 180.101.49.11 (180.101.49.11): icmp_seq=2 ttl=52 time=4.34 ms
64 bytes from 180.101.49.11 (180.101.49.11): icmp_seq=3 ttl=52 time=4.28 ms
64 bytes from 180.101.49.11 (180.101.49.11): icmp_seq=4 ttl=52 time=4.21 ms
64 bytes from 180.101.49.11 (180.101.49.11): icmp_seq=5 ttl=52 time=4.19 ms
64 bytes from 180.101.49.11 (180.101.49.11): icmp_seq=6 ttl=52 time=4.98 ms
^C
--- www.a.shifen.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 4.100/4.348/4.978/0.291 ms

A normal ping response indicates that internet access and DNS configuration are both correct.

Upgrade the system image and source information: sudo apt update sudo apt upgrade

Test ssh: ssh root@RDK IP address. Here the RDK IP address is 10.64.61.228, so enter ssh root@10.64.61.228. The first ssh login will show the following prompt:

 ssh root@10.64.61.241
The authenticity of host '10.64.61.241 (10.64.61.241)' can't be established.
ECDSA key fingerprint is SHA256:5NQuzIkfNYZftPkxrzCugbQs5Gy5CEC5U3Nhtu+sJs8.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes

Enter yes and press Enter, then enter password: root, to access the RDK normally.

ssh root@10.64.61.241
The authenticity of host '10.64.61.241 (10.64.61.241)' can't be established.
ECDSA key fingerprint is SHA256:5NQuzIkfNYZftPkxrzCugbQs5Gy5CEC5U3Nhtu+sJs8.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '10.64.61.241' (ECDSA) to the list of known hosts.
root@10.64.61.241's password:
Permission denied, please try again.
root@10.64.61.241's password:
Welcome to Ubuntu 20.04.4 LTS (GNU/Linux 4.14.87 aarch64)

* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
Last login: Sat Apr 2 05:57:05 2022 from 10.64.37.219
root@ubuntu:~#

X86 Platform

Install Ubuntu 20.04 64-bit on an X86 physical machine and configure the network environment. You can also use a virtual machine or Docker, but runtime efficiency may be lower.