After setting up connections of Core 3588E, you can log in to it on Windows, macOS, or Ubuntu using Android Debug Bridge (ADB), a serial communication tool, or SSH.
This document describes how to log in to Core 3588E using a serial communication tool. For details about login using the ADB tool and via SSH, refer to the following documents:
Preparations
- A USB to TTL convertor
- A computer: Windows, macOS, or Ubuntu
- A Core 3588E board
- A carrier board that is compatible with Jetson TX2 NX (Leetop A206 is used in this document)
On Windows
Step 1. Connect hardware
1.1 Connect the GND, TXD, and RXD pins of the USB to TTL converter to the GND, RXD, and TXD pins of Core 3588E, respectively.
1.2 Connect the USB to TTL converter to your computer.
Step 2. Download and install a driver
2.1 Download a driver according to the USB to TTL converter that you are using.
2.2 Unzip the driver zip file and select the corresponding file (.exe) to install based on the computer architecture (32-bit or 64-bit).
On your computer, open Device Manager and find the board’s COM port.
Take note of the COM port for the device named “Ports (COM & LPT)” (such as “COM4”). You will use it in the next step.
Step 3. Install and configure PuTTY
PuTTY is one of the serial communication tools generally used on Windows, and is used for illustration in this document.
3.1 Select the PuTTY file (.exe or .msi) to install based on the computer architecture (32-bit or 64-bit).
3.2 Open PuTTY and configure Connection type, Serial line, and Speed as shown in the following figure. Then click Open.
When the screen terminal opens, it will probably be blank. Hit Enter and you should see the login prompt once the system finishes booting up. Enter the default username and password of your Core 3588E.
On macOS
Step 1. Connect hardware
1.1 Connect the GND, TXD, and RXD pins of the USB to TTL converter to the GND, RXD, and TXD pins of Core 3588E, respectively.
1.2 Connect the USB to TTL converter to your computer.
Step 2. Install Picocom
Picocom is one of the serial communication tools generally used on macOS, and is used for illustration in this document.
(Optional) 2.1 Install Homebrew if it is not installed yet by running the following command:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"2.2 Install Picocom by running the following command:
brew install picocomStep 3. Connect to Core 3588E
-b is to set the baud rate and must be set to 1500000.
sudo picocom -b 1500000 /dev/tty.usbserial-0The command output is as follows:
picocom v3.1
port is : /dev/tty.usbserial-AQ043YF8
flowcontrol : none
baudrate is : 1500000
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
hangup is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no
Type [C-a] [C-h] to see available commands
Terminal readyPress Enter and you are directed to the console of Core 3588E.
Step 4. Exit
4.1 Press CTRL+A.
4.2 Keep pressing CTRL and press Q.
On Ubuntu
Step 1. Connect hardware
1.1 Connect the GND, TXD, and RXD pins of the USB to TTL converter to the GND, RXD, and TXD pins of Core 3588E, respectively.
1.2 Connect the USB to TTL converter to your computer.
Step 2. Install and configure Minicom
Minicom is one of the serial communication tools generally used on Ubuntu, and is used for illustration in this document.
2.1 Install Minicom by running the following commands:
sudo apt update
sudo apt upgrade
sudo apt install minicom2.2 Start Minicom by running the following command:
sudo minicom -s2.3 Configure Minicom.
2.3.1 On the interface that is displayed, select Serial port setup using the direction key.
+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
| Exit from Minicom |
+--------------------------+ 2.3.2 On the interface that is displayed, configure the settings as follows:
- Input A to change Serial Device to /dev/ttyUSB0.
- Input E to change Bps/Par/Bits to 1500000 8N1.
- Input F to change Hardware Flow Control to No.
+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 1500000 8N1 |
| F - Hardware Flow Control : No |
| G - Software Flow Control : No |
| H - RS485 Enable : No |
| I - RS485 Rts On Send : No |
| J - RS485 Rts After Send : No |
| K - RS485 Rx During Tx : No |
| L - RS485 Terminate Bus : No |
| M - RS485 Delay Rts Before: 0 |
| N - RS485 Delay Rts After : 0 |
| |
| Change which setting? |
+-----------------------------------------------------------------------+
2.3.3 Press Enter to save the settings and select Save setup as dfl. Configuration saved is prompted.
2.3.4 Select Exit.
+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
| Exit from Minicom |
+--------------------------+ The Minicom tool interface is displayed. Press Enter. The console of Core 3588E is displayed, as shown in the following figure.
Welcome to minicom 2.8
OPTIONS: I18n
Port /dev/ttyUSB0, 18:15:29
Press CTRL-A Z for help on special keys
root@mixtile-desktop:~#
Step 3. Exit
3.1 Press CTRL+A.
3.2 In the box that is displayed, click Yes.
What you can do next
After login to Core 3588E, you can perform operations based on your requirements, such as checking device information, installing or uninstalling software, editing configuration files, and starting or stoping services.
Check device information
cat /etc/os-releasecat /var/log/syslogdmesgInstall or uninstall software
sudo apt update
sudo apt upgrade
sudo apt install [software name]sudo apt uninstall [software name]Edit configuration files
vi [file path]Start or stop services
sudo systemctl start [service name]sudo systemctl stop [service name]