Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following sections will provide a starting point to explore ATDM’s features.

Table of Contents
minLevel1
maxLevel7

Unboxing and Bring-up

Your ATDM will have a Toradex iMX8QM 4GB system-on-module (SOM) installed with our Yocto 5.7.0 Linux image pre-loaded, including the display graphics and touch drivers. This system requires 12V power to be provided to the red (positive) and black (negative) wires from the provided harness to power ON the display and the ATDM. When 12V is applied, the ATDM automatically boots into the pre-loaded Linux image, with video output going via FPDLink to the displayTorizon image.

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFBDAD

At this time with our sample A boards, the first “cold boot” (where 12V is applied for the first time) will not properly initialize the touch module. This is fixed with a simple “reboot” command via console or pressing the reset switch next to the two female Micro-USB ports.

...

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFBDAD

We recommend attaching a USB hub to utilize a mouse and keyboard to interface with ATDM for development. The USB host is exposed at the top of ATDM’s enclosure.

...

Debug Terminal and Basic Usage

The ATDM includes its a built-in USB serial adapter that , which can be accessed via the “J5” micro-USB port, as shown below.

...

This chip is based on Silicon Labs CP210x based and requires drivers from this link. This chip It is powered via the 12V wiring harness, not the USB host (computer it’s plugged into). This means that your ATDM will already have to be powered on to be recognized by the host computer.

...

In Putty, we select serial under “Connection type:” then Then we use the COM device we found from Device Manager and enter it under the “Serial line” entry. Next, we enter the Toradex modules module baud - rate (115200) and open it. If a black console window with no error messages opens, everything should be set up correctly. Typing in root should log you into the ATDM's root user of the ATDM; from here, you can issue any Yocto Linux commands you wish.

Basic Ethernet Accessibility

The ATDM behaves as a standard Yocto Linux machine would, meaning it’ll communicate with your router's DHCP server to get a valid local IP address that can be used to access your machine over the same network. You can plug an Ethernet cable from the ATDM straight into your Windows computer, and it will assign IP addresses for each device automatically.

...

Now that we have obtained the our ATDM's IP address of our ATDM, we can use that IP to access its console via the SSH protocol, which is enabled on port 22 by default.

...

In Putty, we enter our IP address, port 22, and SSH connection type. If everything is good, you will get prompted to accept a security certificate issued by the device.

Basic Cellular Connection Verification

Connect the modem to the ATDM that will be used to bolster the SIM.

...

Through the active console on your ATDM, insert the command mmcli -L to list modem connections that the ATDM has, as well as the index it is located.

...

Enable this modem with the command mmcli -m [Modem index] -e.

...

Use the command mmcli -m [Modem index] to list the details of the modem to find the Bearer index

...

Now that the modem is connected to the ATDM and we know the Bearer location insert the command mmcli -b [Bearer index] to list the properties of the bearer and find the APN.

...

Use this APN in the command mmcli -m 0 --simple-connect="apn=[APN name]" to enable the cellular connection.

the ATDM's modem connection”.

Basic GPS Connection Verification

Connect to the active console on the ATDM with a cellular connection.

Insert the command mmcli -m mmcli—m 0 --location-status to list the data the GPS is running collecting through a cellular connection.

...

If you want to test what location is present for the ATDM, insert the command mmcli -m 0 --location-get.

Basic SocketCAN Interface

ATDM utilizes the following CAN interface from SocketCAN:

...

The last interface listed is can0.

Code Block
~$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 10
    link/can 

An alternative way to investigate CAN interfaces is to use ifconfig <canx>:

Code Block
~$ ifconfig can0
can0: flags=128<NOARP>  mtu 16
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Before enabling the SocketCAN interface, you can configure it:

Code Block
~$ ip link set can0 type can bitrate 500000

To enable the CAN interface:

Code Block
~$ ip link set up can0

To display a list of received messages on the bus in realtime, use the candump utility:

Code Block
~$ candump can0