Device connection

Table of Contents

• • You will need
  • Powering the device
• SSH connections
• Necessary cables and adapters
• Connecting via SSH
• For Serial Port connections
  • Necessary cables and adapters
• Connecting via Serial Port
  • Windows
• Summary
• Previous step
• Next step

You will need

• D7 SDK for Linux or Windows
• D7 target device
• AMPSEAL 770680-1 Receptacle Housing, 23 Position for power and CAN/J1939, analog video in, audio out, serial
• AMPSEAL 776164-1 Receptacle Housing, 35 Position for analog and digital IO
• AMPSEAL 1.3 mm contacts
• USB-C cable to flash the device to begin development
• 1/16" allen key or hex bit to access: bootloader microswitches (for flashing and recovery), microSD holder, SIM card holder, debug UART
• USB-C stick or (microSD to USB-C adapter) for Application Software Updates
• M12 X-Coded ethernet cable for SSH via Gigabit Ethernet
• M12 NMEA 2000 cable for isolated CAN (if applicable)
• SKEDD and USB-UART - optional for debug console

For most of the development cycle, you will likely want a very tight edit-build-run-debug loop. To that end, the development image running on the device has a built-in SSH server as well as access to a console via serial port.

This page will describe the different ways available to get a console onto the target device.

Note

Due to security reasons, on the release image the SSH server is disabled. Please refer to the page on differences between the release and development images.

There is no password for root on the development image. On the release image, shell access is unavailable, meaning it is not possible to log in as any user.

Warning

Do not use the development image in production.

Powering the device

In order to power the D7 you will need to provide between 6 and 36 Volts on Pin 1 of its AMPSEAL 23-way connector. Pin 3 is ground.

You will need TE part number 770680-1 for 16-20 AWG or 2371884-1 for 20-24 AWG. Plus 1.3mm contacts.

AMPSEAL 23-way Connector

If the D7 is currently using a development image, you can choose either one of the options for connecting: SSH or serial debug port.

On a release image, only the serial debug port is available for getting a console onto the device.

SSH connections

Necessary cables and adapters

The D7 has a gigabit ethernet interface on the M12 X-Coded connector. In order to connect the device to the network,you will need a M12 X-Coded to RJ45 cable or adapter.

M12 X-Coded to RJ-45 Pin assignments

Note: If you do not have a M12 X-Coded to RJ45 cable readily available, it may also be possible to use an Ethernet to USB-C adapter to connect the D7 to the network.

There is no official compatibility list for Ethernet to USB-C chipsets, but most Realtek ones should work. Support for them is built into the kernel and in our custom images we do not modify the drivers for them.

Connecting via SSH

To get a console on the D7 via SSH, you need to connect the D7 to the network, find its IP address and run:

ssh root@${device_ip}

A D7 that doesn't have a user application on it should by default display the board's serial number and its up-to-date IP address.

Like many other Linux machines, the D7 has a DHCP client running by default so as soon as a cable is plugged into the M12 X-Code port, it should automatically detect if it can connect to a network and once it does, it will display its IP address.

For Serial Port connections

Necessary cables and adapters

Required:

• USB extension cable.
• USB-to-UART adapter board running at 3V.
• 1/16" hex bit or key for the cap screws.
• SKEDD 6 contact 2 row IDC connector cable.

Steps:

1. Connect your workstation to the USB-to-UART bridge using the USB extension cable.
2. Make sure the USB-to-UART bridge is running at 3V.
3. Follow the picture below to uncover the device's debugging serial port.

Remove the highlighted screws

Remove the cap and put it to the side

Move the foam and battery to the side without disconnecting the battery

Plug in the SKEDD IDC connector

The SKEDD connector only goes in one way.

TX and RX pins on the SKEDD connector

Connecting via Serial Port

The default settings for the serial port on the device are:

Setting	Value
Baud rate	115200
Flow control	None
Databits	8
Parity	None

Note: Remember to logout of the session on the device before disconnecting from the serial console. Not logging out before disconnecting will leave the user shell running.

Except for the baudrate, the values above are the defaults for picocom. As such, for the best experience we recommend using it.

You will need to identify the serial port on which the device is mounted. Usually, this will be /dev/ttyUSB0, but if you have multiple USB serial devices attached to your workstation, it may be /dev/ttyUSB1 or higher.

To install picocom and connect to the serial console on the device:

sudo apt install -y picocom
sudo picocom -b 115200 /dev/ttyUSB0 # Replace this with the port your device is mounted on

Remarks

To exit the picocom session type: "Ctrl-a" followed by "Ctrl-x", without the quotes.

Alternatively, GNU Screen is available as well for most distributions.

sudo apt install -y screen
sudo screen -fn /dev/ttyUSB0 115200 cs8 # Replace /dev/usbTTY0 with the port your device is mounted on

Remarks

To exit screen type: "Ctrl-a" followed by ":", then "quit", without the quotes.

Windows

For Windows it is recommended to use PuTTY.

To figure out which port the D7 is connected to, you can check in Device Manager.

Device Manager

To connect to the device via serial follow the instructions below.

1. Select the Serial radio button
2. Enter the COM port label found in Windows Device Manager
3. Set baudrate to 115200
4. Click Open

PuTTY

Summary

In this section we have described the available methods for connecting in order to obtain a shell into the device.

Note

As mentioned above, this is still subject to change in future releases.

Previous step

Setting up the development environment: D7 SDK user walkthrough - Development Environment.

Next step

The next step is Preparing the D7 device.