G3 Quick Start Guide

Important: Considerations when connecting a G3 module to a network.

Addressing security concerns when connecting any device to a network is crucial. Many IT departments forbid connecting devices not directly in their control. There are two options for dealing with this:

• Add a second network interface to the host PC (a USB dongle).
• Remove the PC from the main network and set up an isolated network (i.e., air-gapped from the main corporate network) for end-product application development.

No matter which option you choose, the development host and the G3 module must effectively have static IP addresses to allow communications for on-target debugging and migrating applications and associated data between the host and the G3 module without reconfiguring each time. You can do this by:

• Assigning the IP addresses manually.
• Configuring a DHCP server to use host reservations for the development host and the G3 module, which is equivalent to manually setting static IP addresses.

G3 Developer VM Settings for Windows

Adjusting some virtual machine settings allows you to use your development host hardware.

TIP: You can only adjust VM settings when the VM is stopped.

Before making any changes, complete these physical connections:

• Debug Interface Port.
• Ethernet Port (J3).
• “Y” power/RS-232 cable (J2), but do not power up the G3 module yet.

Settings You Must Change

You must change these configuration settings, or the G3 Developer VM cannot communicate with and control the G3 module target device.

Serial Port Configuration

When you plug the USB connector from the Debug Interface Cable into your Windows 10/11 host, Windows will set up a new COM port for it. You may have to use the Device Manager to install the required driver the first time you do this. Search the network for the driver and pull the required one directly from Microsoft. When the driver is installed, your Device Manager should look something like this:

• Once this process is complete, open the VM settings dialog and switch to the USB panel. It should look something like this:

• Click the blue USB connector button with the green + on it to list the available USB devices as shown below:

• Click the FTDI USB-RS232 Cable [0600] entry to add the filter for the Debug Interface Cable. The VM USB settings panel should now look like this:

TIP: Remove all USB to serial converters and insert only the Debug Cable to make adding the filter easy. You cannot see the converter serial number until you add the filter.

• With the filter entry selected in the list, you can click the blue USB connector button with the orange gear on it to popup the device details dialog as shown below:

TIP: The main USB settings panel does not display the device serial numbers. They show up in the details dialog. So, if you have several similar USB devices (e.g., multiple USB to serial converters), the entries in the filter list will all look the same. Thus, you cannot tell which is which on quick inspection.

When first adding the filter, change the filter’s name on the details dialog for better identification in the main USB filter panel.

Testing

From the G3 Developer VM

Once you have configured the serial ports, launch the VM and log in as “Joe Developer.” The password is developer. Now, open a terminal window in the VM, then:

You can now see any messages and log in to the target in your terminal window.

Power on the target. You should see several lines of output as the target boots. Then, you will see a login prompt. Enter root; there is no password.

If you do not see any output, try any other available /dev/ttyUSB* ports listed by the above ls command. If there is no response, see Troubleshooting in the G3 Manual or seek assistance from a system administrator.

Ethernet Connection to the Target

This procedure applies to either the Linux desktop or within the G3 Developer VM. Start by opening a terminal window, then:

If there is no response, see Troubleshooting in the G3 Manual or seek assistance from a system administrator.