 |
|
| |
|
|
| |
|
| |
Hilscher GmbH
Rheinstraße 15
65795 Hattersheim
Germany
Telephone:
+49 (0)6190 9907-0
Facsimile:
+49 (0)6190 9907-50
E-mail:
info@hilscher.com |
|
| |
|
|
|
|
|
|
netX - networX on chip |
|
| further Information |
|
netX Datasheet |
|
|
|
The netX is a highly integrated network controller with a new system architecture optimized on communication and maximum data transfer.
|
|
| Overview of netX 500 and interfaces |
Each communication channel consists of three freely configurable ALUs, which, with their command set and their infrastructure can carry out the most varied field bus and Real-Time Ethernet systems. Together with the integrated 32Bit / 200 MHz ARM CPU, netX is:
- The universal communication platform
- The migration strategy from field bus to Real-Time Ethernet
- The single-processor solution with integrated communication controllers
- The open technology for own applications
The netX is part of a system solution which also includes software, tools and design services. The customer determines the delivery and scope of performance depending on the strategy, know-how or resources.
Various network controllers
The netX is supplied for various classes of performance and with various peripheral functions, designed on the individual fields of application.
| netX 5 |
Communication interface with two channels for external CPU |
| netX 50 |
Communication interface with two channels
IO link Gateway and IOs
Protocol stack and smaller applications
|
| netX 100 |
Communication interface with three channels
Complex IOs / motion controller / Ident systems / controls
Several protocol stacks and/or comprehensive applications
|
| netX 500 |
Communication interface with four channels
Terminals Several protocol stacks and/or comprehensive applications
|
|
|
| Application features of the individual netX controllers |
| |
netX 5 |
netX 50 |
netX 100 |
netX 500 |
| CPU |
|
ARM 966E / 200 MHz |
ARM 926EJ-S / 200MHz
MMU / Cache |
ARM 926EJ-S / 200 MHz
MMU / Cache |
| SRAM / ROM |
64K |
112K / 64K |
152K / 32K |
152K / 32K |
| Dual-Port Memory |
X |
X |
X |
X |
| communication channels |
2 |
2 |
3 |
4 |
| Real-Time-Ethernet |
Switch / Hub
IEEE 1588 |
Switch / Hub
IEEE 1588 |
Switch / Hub
IEEE 1588 |
Switch / Hub
IEEE 1588 |
| fieldbus |
x |
x |
x |
x |
| USB |
|
x |
x |
x |
| UARTs |
|
3+2 |
3+3 |
3+4 |
| SPI |
x |
x |
x |
x |
| I2C |
|
x |
x |
x |
| Real-Time-Clock |
|
|
|
x |
| LCD-Controller |
|
|
|
x |
| IO-Link Controller |
|
x |
|
|
| AD-converter |
|
|
x |
x |
| PWM |
|
|
x |
x |
| Encoder |
|
|
x |
x |
| EAs |
16 |
40+54 |
47+53 |
47+53 |
performance of the netX Controller
Only few external components
The netX as an optimized network controller requires only a quartz, external memory and the physical network interface. In the case of Ethernet, the PHYs (analogue Ethernet drivers) are integrated, so that there are only small costs for a few passive components.
Complete design documentation are available in the netX download area.
|
|
| Block circuit diagram communication interface for Real-Time Ethernet |
Software architecture
The netX is basically conceived as an open solution. There are various, fixedly defined interfaces on to which own applications can be placed or the netX can be used as a communication module with fixedly defined Dual-Port Memory and a loadable Firmware.
| Configurator |
Master protocols must be made available for the whole of the network configuration. This can be carried out via the SYCON.net network configurator based on the standardized FDT/DTM technology.
Alternatively, interfaces to other tools are defined.
|
| driver |
Dual-Port memory drivers for various operating systems are available for the netX with loadable standard Firmware.
Own drivers can be created based on a Toolkit.
|
| Operating system |
All protocols run on the Hilscher own rcX Real-Time-Kernel. This is provided license-free.
Board Support Packages for various other operating systems are available.
|
| Protocol stack |
Protocol stacks are supplied as loadable standard Firmware, linkable object modules or in source code for the rcX Real-Time Kernel.
The source code needs to be ported for use in other operating systems.
|
| Hardware Abstraction Layer |
Data exchange with the communication ALUs
is carried out through an abstraction layer. This is provided with C source code and defines a mutual interface for all netX controllers. |
| Micro Code |
The configuration of the communication channels on the individual networks is achieved by a micro code that is made available as a binary file. This is transferred to the communication ALUs from the protocol stack in the initialisation phase.
The micro code cannot be changed or created by the customer.
|
|
|
| Principal netX software structure |
| Protocol |
|
Status |
Remark |
| AS-Interface |
Master |
Development not started yet |
|
| CANopen |
Slave |
Release |
|
| |
Master |
Release |
|
| CC-Link |
Slave V1.1 |
Release |
|
| DeviceNet |
slave |
ß-Release |
Release in 03/2008 |
| |
Master |
ß-Release |
Release in 03/2008 |
| EtherCAT |
Slave |
Release |
|
| |
Master |
Release |
|
| Ethernet/IP |
Adapter |
Release |
|
| |
Scanner |
Release |
|
| IO-Link |
Master |
|
ß-Release in 01/2008 |
| IDA |
Server |
Release |
|
| MPI |
|
Release |
|
| EtherNET Powerlink |
Controlled Node |
ß-Release |
Release in 01/2008 |
| PROFIBUS |
Slave |
Release |
|
| |
Master |
Release |
|
| PROFINET |
Device |
Release |
|
| |
Controller |
Release |
|
| SERCOS |
Slave |
Release |
|
| |
Master |
development projected |
ß-Release in 05/2008 |
Overview of the deliverable protocol stacks
Tools and Evaluation Boards
As also with many other controllers, the ARM 926 and ARM 966 CPUs are used in the netX. Thus, all the ARM development tools on the market can be used over the standardised JTAG and ETM (Embedded Trace Macrocel)Interface.
The Hitex Company offers the HiTOP development environment with integrated GNU compiler and the helpful Tantino JTAG debugger. The access to the rcX objects was implemented in close cooperation with HiTOP
A quick and economical entry into the netX technology is achieved with the netSTICK and the NXHX starter and software development board. Both contain a USB debug interface and are provided with the HiTOP development environment. This permits evaluation of the protocol interfaces and the rcX Real-Time kernel as well as development of own application software which can be tested on these boards.
Further development and evaluation boards for special applications are available.
|
|
| Quick and economical entry into the netX technology with the netSTICK and the NXHX starter and software development board. |
Design Services
Hilscher offers the whole Design Flow from the concept phase to the tested and certified board as a service. We can offer the whole production with our modern SMD line and the mostly standardised production and test procedures at interesting conditions.
Further services such as customer-specific variants of the netX or configuration and diagnostic DTMs designed according to your wishes are offered via our companies Hilscher SoC Technology / Berlin or Hilscher Development and Testcenter / Varna.
|
|
| Development, test and production up to customer-specific ASIC variants from one source. |
Price model
In the simplest fashion, the pricing model takes into account the high development effort of Master stacks and understands the various support efforts as a chargeable service.
- netX as a “module” and customer develops his own software
All the required documentation for this is available on the Internet including the micro code for Ethernet and CAN. For complex communication systems such a EtherCat, this can be obtained for a one-off payment (compared to IPs for FPGA).
Support is exclusively via the FAQ forum and no further contracts need be entered into.
- netX as “communication module with Firmware”
The protocol stack is obtained as an unchangeable, loadable Firmware against a one-off payment. There are no further licences for Slave Stacks. A licence is required per controller for Master Stacks. In both cases a licence must be obtained within the framework of the netX Basis Support Agreement or the netX Technology User Agreement. An annual fee is charged for this.
- netX as “application platform with protocol stack” and customer develops his own Firmware”
The protocol stack is provided as a linkable object module or as source code for a one-off payment. A further licence must be paid for per controller for Master Stacks.
A condition is the signing of the netX Technology User Agreement which also takes into account aspects such as ESCROW agreements and strategic information for further development of the netX technology.
|
| |
|
|
|
