connection_guide
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| connection_guide [2014/03/01 00:17] – created cedric.eloy | connection_guide [2018/05/22 10:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== Physical interfaces ===== | ||
| + | ==== Serial port ==== | ||
| + | |||
| + | The QuimBox features multiple mini-USB ports to connect to the different modules of the box. They all integrate a serial-to-usb converter for easy connection with a development station. | ||
| + | |||
| + | The serial port settings should be as follows: | ||
| + | * Baudrate: 115200 bps | ||
| + | * Data Bits: 8 | ||
| + | * Parity: None | ||
| + | * Stop bits: 1 | ||
| + | * Flow control: None | ||
| + | |||
| + | Using Minicom on Linux, typical settings are: | ||
| + | |||
| + | < | ||
| + | A - Serial Device | ||
| + | B - Lockfile Location | ||
| + | C - | ||
| + | D - Callout Program | ||
| + | E - Bps/ | ||
| + | F - Hardware Flow Control : No | ||
| + | G - Software Flow Control : No | ||
| + | </ | ||
| + | |||
| + | ==== WiFi ==== | ||
| + | |||
| + | By default, the QuimBox will generate an //ad-hoc// Wifi network with SSID '' | ||
| + | The QuimBox '' | ||
| + | |||
| + | * IP address: 192.168.0.2 | ||
| + | * Mask: 255.255.255.0 | ||
| + | |||
| + | In order to reach the box, you should configured your workstation with an IP address in the same subnet as the QuimBox (ie. 192.168.0.x ). Once connected to the //ad-hoc// network, you should be able to ping the box. | ||
| + | |||
| + | <code - Workstation> | ||
| + | % ifconfig wlan0 | ||
| + | wlan0 Link encap: | ||
| + | inet addr: | ||
| + | UP BROADCAST RUNNING MULTICAST | ||
| + | RX packets: | ||
| + | TX packets: | ||
| + | collisions: | ||
| + | RX bytes: | ||
| + | |||
| + | % ping 192.168.0.2 | ||
| + | PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. | ||
| + | 64 bytes from 192.168.0.2: | ||
| + | 64 bytes from 192.168.0.2: | ||
| + | 64 bytes from 192.168.0.2: | ||
| + | |||
| + | </ | ||
| + | |||
| + | ==== RJ45 ==== | ||
| + | |||
| + | If you want to use the USB-to-Ethernet dongle, you should plug it in one of the front USB ports before powering on the QuimBox. During startup, the dongle will be detected and a '' | ||
| + | |||
| + | By default, this interface is configured with a Dynamic IP, received from a DHCP server (typically your router). | ||
| + | |||
| + | You can check which IP@ it obtained from the Linux shell: | ||
| + | |||
| + | <code - QuimBox> | ||
| + | root@buildroot: | ||
| + | eth0 Link encap: | ||
| + | inet addr: | ||
| + | UP BROADCAST RUNNING MULTICAST | ||
| + | RX packets: | ||
| + | TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 | ||
| + | collisions: | ||
| + | RX bytes: | ||
| + | </ | ||
| + | |||
| + | |||
| + | ===== Linux shell ===== | ||
| + | |||
| + | Two users are configured by default in the QuimBox linux environment: | ||
| + | |||
| + | * the Linux superuser | ||
| + | * Username: root | ||
| + | * Password: admin | ||
| + | * a default user | ||
| + | * Username: default | ||
| + | * No password | ||
| + | |||
| + | When you want to connect to the Linux shell, you have to login as one of these users. | ||
| + | |||
| + | When you have IP connectivity to the QuimBox, we encourage to use ssh to login on the box. | ||
| + | |||
| + | <code - Workstation> | ||
| + | # say you are connected to the wifi | ||
| + | # the QuimBox static IP address is 192.168.0.2 | ||
| + | % ssh root@192.168.0.2 | ||
| + | root@192.168.0.2' | ||
| + | root@buildroot: | ||
| + | bin etc lib linuxrc | ||
| + | dev home | ||
| + | root@buildroot: | ||
| + | </ | ||
| + | |||
| + | ===== File transfers ===== | ||
| + | |||
| + | Once you have IP connectivity with the QuimBox, standard file transfers protocols are available to load your executable or configuration files. | ||
| + | |||
| + | ==== TFTP ==== | ||
| + | |||
| + | TFTP is a very simple, still popular, file transfer protocol. | ||
| + | |||
| + | On the QuimBox, the TFTP server root is / . | ||
| + | |||
| + | <code - Workstation> | ||
| + | # put my_file to /my_file on the QuimBox | ||
| + | ~ % tftp 192.168.0.2 | ||
| + | tftp> mode binary | ||
| + | tftp> put my_file.txt | ||
| + | Sent 5 bytes in 0.0 seconds | ||
| + | tftp> quit | ||
| + | </ | ||
| + | |||
| + | ==== NFS ==== | ||
| + | |||
| + | The QuimBox has a built-in NFS server. That way, it can export its full filesystem to your workstation. | ||
| + | |||
| + | Make sure you have the required packages (nfs-common, | ||
| + | |||
| + | <code - Workstation> | ||
| + | # create a mount point | ||
| + | ~ % mkdir -p mnt/quimbox | ||
| + | # mount | ||
| + | ~ % sudo mount 192.168.0.2:/ | ||
| + | [sudo] password for cedric: | ||
| + | ~ % cd mnt/quimbox | ||
| + | ~/ | ||
| + | bin/ etc/ | ||
| + | dev/ home/ lib32@ | ||
| + | </ | ||
| + | |||
| + | If your workstation runs a NFS server, you can mount it in the QuimBox to access your workstation filesystem from the QuimBox embedded Linux. | ||
| + | |||
| + | ==== CAN ==== | ||
| + | |||
| + | The QuimBrain communicates with external boards via CAN. | ||
| + | |||
| + | The CAN interface can be enabled as follow: | ||
| + | < | ||
| + | ip link set can0 type can bitrate 1000000 | ||
| + | ip link set up can0 | ||
| + | </ | ||
