“virtual” links that are interfaced through TCP sockets. Each SpaceWire link can be individually configured with respect of transmission bit rate. When a packet arrives to the GRESB bridge on any of the links (real or virtual) it is forwarded to the link specified in the routing table.
GRESB User's Manual 2. Installation 2.1. Power The GRESB is powered from an external +5V adapter, which should be connected to POWER in the back panel. 2.2. Ethernet The connection to the ethernet network should be done using a standard network cable, inserted in the RJ45 connector (ETHERNET) in the front panel.
SpaceWire link. While the GRESB is transmitting a packet to a virtual link (i.e sending data on one of the virtual receive TCP sockets) it will not process any new packets from the link on which the packet arrived.
Page 7
Virtual SpaceWire Figure 3.1, “GRESB routing” shows how the routing works in the four possible situations, virtual (TCP) link to SpW link, SpW to TCP, SpW to SpW and TCP to TCP. In separate routing table mode, each port (TCP and SpaceWire) has it own configurable routing table, the routing still works exactly the same. The...
Page 8
A packet with Destination Node Address (DNA) 35 is received on SpaceWire link 1. The destination link is looked up in the routing table. It is destined to virtual link 2 and the GRESB will start transmitting the packet on the appropriate socket.
(such as error end of packet and truncated packets) are indicated in the GRESB protocol header. Since this header is not added when forwarding to another SpaceWire link any possible error information is lost in SpaceWire to SpaceWire routing.
3.5. GRESB configuration It is possible to configure the GRESB through the socket interface. This is done in a similar manner to normal packet transmission but with the packet structure shown in Figure 3.5, “Configuration protocol format”. The configuration protocol has ID 1.
1=Enable 0=Disable 3.6. GRESB status query Information about the links, statistics and the routing table can be queried through the socket interface. A status query is sent in the same manner as a configuration packet but with procotol ID 2. The reply is sent back on the same socket.
GRESB User's Manual The link status reply consists of a single word. Table 3.7. Link status reply Byte 3 (MSB) Byte 2 Byte 1 Byte 0 (LSB) Clock divisor 1 - In run state 0 - Not in run state 3.6.2.
3.7. Send time-code Through the socket interface of the GRESB, it is possible to make the spacewire links send out a time-code. Sending timecode to the TCP links are not supported. A time-code packet is sent in the same manner as a configuration packet but with procotol ID 3.
3.10. Host software A host software package for communicating with the GRESB is provided with the unit on a CD. The software includes four programs: send, recv, set_clkdiv, set_route, get_route, get_status, get_linkstats, get_nodestats and sniff. The syntax of the programs is as follows: send <ip address>...
<ip address> <file name> The send command connects to a virtual link and transmits a file from the host to the GRESB where it is routed to the desired node. The file is sent in packets of size 32 KBytes. If another packet size is needed change the SPW_PACKETSIZE in send.c accordingly.
It is also possible to connect with GRMON using the USB port of the bridge. Use the -grusb switch instead of -gresb and leave out -ip and -sna. Before connecting through USB the bridge needs to be reset and the USB cable connected. Wait until the GRESB has booted (10 s) before starting GRMON.
3.11. GRESB embedded web server GRESB has an embedded web server (port 80) which allows the user to view status and configure various parameters. From the main page you can chose between status, network configuration, routing table config- uration and firmware upgrade.
Page 18
It is possible to update the GRESB’s firmware through the web interface. Updates will be made available on Gaisler Research’s web site. The firmware images are protected by a checksum and will be stored in RAM and validated before programmed to flash memory.
GRESB User's Manual 4. Optional CAN 2.0B interface 4.1. Overview When the bridge is equipped with a CAN controller it uses the ports listed in Table 4.1, “CAN tcp port allocation” in addition to the previously listed ports. Table 4.1. CAN tcp port allocation...
GRESB User's Manual After the protocol ID comes the option field which specifies what option to configure. The value to set for this option is specified in a 4 byte field which needs to be in network byte order when sent. Available options are listed in Table 4.4, “CAN options”.
GRESB User's Manual Name Description BTR1.6-4 TSEG2 Time segment 2 BTR1.3-0 TSEG1 Time segment 1 The CAN bus bit period is determined by the CAN system clock and time segment 1 and 2 as shown in the equations below: * (TSEG1+1)
Page 22
GRESB User's Manual Table 4.8. Bit interpretation of status register Name Description SR.7 Bus status 1 when the core is in bus-off and not involved in bus activities. SR.6 Error status At least one of the error counters have reached or exceeded 96.
GRESB User's Manual 5. Interfaces 5.1. Front panel The front panel of GRESB includes connectors for Ethernet and SpaceWire links. Figure 5.1. Front-panel Table 5.1. Front-panel connectors Name Function Type Description ETHERNET Ethernet RJ45 10/100/1000 Mbit/s Ethernet connector SPW0 SpaceWire 0...
GRESB User's Manual 5.3. Connector pin-out tables Table 5.3. Spacewire connectors (SPW0 - SPW2) Name Description DIN+ Data In +ve 6 DIN- Data In -ve SIN+ Strobe In +ve 7 SIN- Strobe In -ve SHIELD Inner Shield (connects to DGND)