civilinfrastructureplatform:beagleboneblackboard
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
civilinfrastructureplatform:beagleboneblackboard [2017/06/05 21:06] sesa126914 |
civilinfrastructureplatform:beagleboneblackboard [2018/09/13 13:08] (current) rajmarshall |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Beaglebone Black Setup & Configuration (3/4) ====== | + | ====== Beaglebone Black Setup & Configuration (3/5) ====== |
| - | This set of instructions assumes you have already Setup and Configured the B@D Virtual Machine. If that is not the case please go back to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]]. | + | This set of instructions assumes you have already Setup and Configured the B@D Virtual Machine. If that is not the case please go back to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]]. If you are using the 1.0 release rather than the latest version for git you need to read an [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/beagleboneblackboard?rev=1508248464|older version]] of this page. |
| + | |||
| + | If you are using the Renesas IWG20M board see [[renesasboard|this page]]. | ||
| ===== Working with the Beaglebone Black ===== | ===== Working with the Beaglebone Black ===== | ||
| Line 7: | Line 9: | ||
| ==== Cabling to the Beaglebone Black ==== | ==== Cabling to the Beaglebone Black ==== | ||
| + | |||
| * The Beaglebone Black should be powered using the wall plug. | * The Beaglebone Black should be powered using the wall plug. | ||
| * The USB cable that comes with the BBB //can// power the board, but this is not recommended when loading a kernel. | * The USB cable that comes with the BBB //can// power the board, but this is not recommended when loading a kernel. | ||
| Line 38: | Line 41: | ||
| * Handshake: **None** | * Handshake: **None** | ||
| - | 4. The CIP Testing project uses the ''ser2net'' serial-to-network proxy program to allow communications with the BBB by assigning it an Ethernet port on the host machine. This way, a developer can communicate to the BBB over the serial port as if it had an IP Address. A typical use would be connecting to the BBB using the telnet program: ''telnet <Host's IP Address> <port#>'' | + | 4. The CIP Testing project uses the ''ser2net'' serial-to-network proxy program to allow communications with the BBB by assigning it an Ethernet port on the host machine. This way, a developer can communicate to the BBB over the serial port as if it had an IP Address. A typical use would be connecting to the BBB using the telnet program: ''telnet <Host's IP Address> <port#>'' |
| + | |||
| + | // Note that if you are using a Windows 10 host then you must use ser2net on the B@D Virtual machine. In **this** case follow steps 15/16 and **then** move back to step 9. // | ||
| 5. Verify on your host machine (if necessary installing ser2net first) the ''ser2net.conf'' configuration file to ensure the serial port is correct for the CIP B@D Virtual Machine. | 5. Verify on your host machine (if necessary installing ser2net first) the ''ser2net.conf'' configuration file to ensure the serial port is correct for the CIP B@D Virtual Machine. | ||
| Line 65: | Line 70: | ||
| ''user@host: **sudo systemctl restart ser2net.service**'' | ''user@host: **sudo systemctl restart ser2net.service**'' | ||
| - | 8. On the VM change localhost to host's IP Address (Machine that is connected serially to BBB): | + | 8. B@D now uses a private network so that the host IP address no longer needs setting in the device dictionary. If your local IP address settings are such that a change is necessary from the default 192.168.22.1, |
| + | edit mybbb.dat appropriately and then copy it into the device dictionary: | ||
| - | ''vagrant@guest: **sed -i 's/localhost/<host_ip>/g' mybbb.dat** '' | + | ''vagrant@guest:$ **<nowiki>sudo cp mybbb.dat /etc/lava-server/dispatcher-config/devices/bbb01.jinja2</nowiki>**'' |
| Note: If you have multiple IP addresses (e.g. due to WiFi and Ethernet both being active) then it is recommended that you disable all but one network interface. | Note: If you have multiple IP addresses (e.g. due to WiFi and Ethernet both being active) then it is recommended that you disable all but one network interface. | ||
| - | ==== Update the Beaglebone Black Device Dictionary ==== | + | // If you don't wish to change the root password of the board then edit the first line of mybbb.dat so that lavauser123 is replaced by your current board password. Or you can change it when logged in via telnet (see next step) // |
| - | 9. Update device dictionary: | ||
| - | ''vagrant@guest:$ **<nowiki>sudo lava-server manage device-dictionary --hostname bbb01 --import mybbb.dat</nowiki>**'' | + | 9. Connect to the BBB using the serial port. |
| - | 10. Connect to the BBB using the serial port. | + | '' vagrant@guest:~$ **telnet 192.168.22.1 8020** '' |
| - | + | ||
| - | '' vagrant@guest:~$ **telnet <host_ip> 8020** '' | + | |
| Trying ::1... | Trying ::1... | ||
| Line 101: | Line 104: | ||
| ==== Using an Ethernet Cable ==== | ==== Using an Ethernet Cable ==== | ||
| - | 11. Connect an Ethernet Cable from the Ethernet switch to the BBB's RJ-45 connector and connect to BBB using SSH. | + | 10. Connect an Ethernet Cable from the Ethernet switch to the BBB's RJ-45 connector and connect to BBB using SSH. |
| ''[host@user ~]$ **ssh debian@10.0.0.50**'' | ''[host@user ~]$ **ssh debian@10.0.0.50**'' | ||
| Line 117: | Line 120: | ||
| - | 12. Exit the ''debian'' login and login as ''root'' | + | 11. Exit the ''debian'' login and login as ''root'' |
| debian@beaglebone:~$ exit | debian@beaglebone:~$ exit | ||
| logout | logout | ||
| Line 130: | Line 133: | ||
| root@beaglebone:~# | root@beaglebone:~# | ||
| - | 13. Change the root password to ''lavauser123'' | + | 12. Change the root password to ''lavauser123'' |
| - | ''root@beaglebone:~# passwd'' | + | ''root@beaglebone:~# **passwd** '' |
| Changing password for root. | Changing password for root. | ||
| Line 140: | Line 143: | ||
| - | 14. Next, you will test the B@D Virtual Machine Setup with the Beaglebone Black and the CIP Linux Kernel on the [[ciptestingreferencetestcases|B@D Reference Test Cases wiki page]]. | + | 13. Next, before you test the B@D Virtual Machine Setup with the Beaglebone Black and the CIP Linux Kernel, you will need to [[cipsystembuildhowto|create an initramfs with BusyBox for the Beaglebone Black]]. |
| + | |||
| + | ------- | ||
| + | |||
| + | 14. **Next 2 steps are Windows 10 Only** | ||
| + | On the Windows host, run VirtualBox, select the VM and enable the FTDI filter - see screenshot:{{:civilinfrastructureplatform:usb-subset.png?200|}} | ||
| + | |||
| + | 15. On the VM change localhost to the VM's IP Address (use ''ip addr'' and the IP address associated with eth1): | ||
| + | |||
| + | ''vagrant@guest: **sed -i 's/localhost/<vm_ip>/g' mybbb.dat** '' | ||
| + | |||
| + | |||
| + | Now move back to step 9. | ||
| Back to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]] | Back to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]] | ||
civilinfrastructureplatform/beagleboneblackboard.1496696761.txt.gz · Last modified: 2017/06/05 21:06 by sesa126914
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
