D3 | Application Note 4 |
Using Multiple NETdimm Modules | |
Author: Bernice Lau | Version 0.1 |
Abstract
On a dimmPCI backplane, there are several possible slots in which a dimmPCI may be inserted, the system slot or the peripheral slots. Once configuration has been completed, the NETdimm modules can successfully communicate with each other. This application note describes the use of the PCI bus sending ethernet packets to transfer a file between two NETdimm devices.
Introduction
After configuration of the NETdimm modules has been completed, they can communicate with each other in an ethernet fashion. Two variants of a simple file transfer program have been developed to demon- strate this ability.
The programs server.c and client.c can run once configuration is done. The programs inetServer.c and inetClient.c require modifications to /etc/services and /etc/inetd.conf since they interface with inetd. All the programs employ networking sockets in order to communicate.
Requirements
•dimmPCI backplane 1.1
•NETdimm 1.2 or higher for system slot on dimmPCI backplane
•NETdimm 1.3 for peripheral slot
•2.0.38 or higher kernel source and filesystem (SDK 2.05 or higher)
•sample programs in SDK, /opt/user_code/networking/filetransfer o client.c
o server.c
o inetClient.c o inetServer.c
Note: When two NETdimm units are used on the backplane, the system slot device will cause the peripheral device to reset as well. A NETdimm 1.3 is required since NETdimm 1.2 in the peripheral slot will not wait for the system slot device on reset and will not get initialised.
Configuration of the NETdimm modules must be completed beforehand, please refer to the application note ‘Configuring dimmPCI Modules for Communication for Kernel v.2.0’.
www.amctechcorp.com | 85 |