Commit 0bc1182f authored by Thanassis Tsiodras's avatar Thanassis Tsiodras
Browse files

Restructured a bit, improved phrasing.

parent 9ebd7f81
...@@ -6,40 +6,47 @@ or a more normal setup involving an Ethernet switch. ...@@ -6,40 +6,47 @@ or a more normal setup involving an Ethernet switch.
Things to do first: Things to do first:
1. If you check the [GR740 board's user manual](https://www.gaisler.com/doc/gr740/GR-CPCI-GR740-UM.pdf), ## GR740 board setup
you will see that on page 17, Figure 4-8, there's a diagram indicating that the
ETH1 interface is only connected if J22 is connected. Note that connector J22
exists at the bottom side of the PCB - so flip your GR740 and look at the PCB:
if you see the same picture as that shown in Figure 4-9, you must move the
configuration plug to the middle location (J22).
2. On your Linux machine - the one that will run the `binaries/x86_partition` - you If you check the [GR740 board's user manual](https://www.gaisler.com/doc/gr740/GR-CPCI-GR740-UM.pdf),
need to make sure that the network configuration mirrors the values input in you will see that on page 17, Figure 4-8, there's a diagram indicating that the
the DeploymentView: ETH1 interface is only connected if J22 is connected. Note that connector J22
exists at the bottom side of the PCB - so flip your GR740 and look at the PCB:
if you see the same picture as that shown in Figure 4-9, you must move the
configuration plug to the middle location (J22).
After that, you can power up the board and connect it with the Linux machine via
an Ethernet cable plugged-in **at the bottom right Ethernet jack** (looking at the
board face-front).
## Linux ethernet configuration
On your Linux machine - the one that will run the `binaries/x86_partition` - you
need to make sure that the network configuration mirrors the values input in
the DeploymentView:
$ grep 192 DeploymentView.aadl $ grep 192 DeploymentView.aadl
Deployment::Configuration => "{devname ""eth1"", address ""192.168.0.151"", port 5116 }"; Deployment::Configuration => "{devname ""eth1"", address ""192.168.0.151"", port 5116 }";
Deployment::Configuration => "{devname ""greth1"", address ""192.168.0.42"", Deployment::Configuration => "{devname ""greth1"", address ""192.168.0.42"",
gateway ""192.168.0.1"", netmask ""255.255.255.0"", version ipv4, port 5118 }"; gateway ""192.168.0.1"", netmask ""255.255.255.0"", version ipv4, port 5118 }";
Put simply, the default configuration assumes that in your Linux machine, there's Put simply, the default configuration assumes that in your Linux machine, there's
a second Ethernet interface (`eth1`) that has the IP address 192.168.0.151. a second Ethernet interface (`eth1`) that has the IP address 192.168.0.151:
So in addition to connecting the GR740 board with the Linux machine via an Ethernet
cable plugged-in at the bottom right Ethernet jack of the GR740 board, make sure
that the Ethernet interface is also set up:
$ sudo ifconfig eth1 192.168.0.151 up $ sudo ifconfig eth1 192.168.0.151 up
...otherwise, if you use a different configuration, edit this line in the DeploymentView If you use a different configuration, edit this line in the DeploymentView AADL
AADL file and change it to mirror yours. You can change the 192.168.0.151, provided that file and change it to mirror yours. You can change the 192.168.0.151 - but you must
you stay in the 192.168.0.x subnet. stay in the 192.168.0.x subnet.
The reason for that is because you can't change the 192.168.0.42 address of the
GR740 side of the Ethernet setup. This address is currently hardcoded in the
PolyORB Ethernet driver. The PolyORB team is investigating ways to improve
this; in older versions of RTEMS it was possible to modify the IP address after
bootstrapping, but in RTEMS5.1 apparently this is not possible anymore.
3. Don't change the 192.168.0.42 address of the GR740 side of the Ethernet, however, ## Build and run
because this address is currently hardcoded in the PolyORB Ethernet driver.
The PolyORB team is investigating ways to improve this; in older versions of
RTEMS it was possible to modify the IP address after bootstrapping, but in
RTEMS5.1 apparently this is not possible anymore.
That should do it - you should be able to launch the `x86_partition` in your Linux machine, That should do it - you should be able to launch the compiled `x86_partition`
and the `gr740_partition` in your GRMON, and see the setup work. in your Linux machine, and then the `gr740_partition` in your GR740's GRMON;
and see it all work.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment