www.arrivetechnologies.

com

CodeChip SDK Product Overview

CodeChip SDK is a portable, modular software package that is used for developing applications on top of Arrive CodeChip
products. The SDK is delivered with complete source code, sample code, build instruction and detail documentation; it
enables software developers to fully utilize the Arrive CodeChip capabilities without deep knowledge of hardware registers.

Software Structure

Device Driver Overiew

Platform independent via a Hardware Abstraction
Layer (HAL) module
Operating System independent via Operating System
Abstraction Layer (OSAL) module
Modular device driver allowing transparent interface
to higher level application layer
Compliant to telecommunications specifications by
various standard bodies: IEEE, MEF, ITU-T, IETF
Supports interrupt handler for time-sensitive events
Compliant to ANSI-C
Includes a command line for debugging during product
development phase
Comprehensive documentation and guidelines
Extensive support for time-critical
protocol/application: Synchronous Ethernet (SyncE),
IEEE 1588v2, IEEE 802.1Q/ITU-T Y.1731 Ethernet OAM,
RFC5860 MPLS-TP OAM.

Application Programming Interface Overview

All software components provided in the CodeChip

SDK is implemented in ANSI-C compliant C-language
using object-oriented design. This design creates a
modular and flexible device driver that is adaptable
with the highly- customizable nature of the
CodeChip.

2013 Arrive All Rights Reserved

In the south-bound direction, the SDKs core device

driver and any associated software component are
implemented in OS-independent manner through the
OS Abstraction Layer (OSAL). The layer provides
interfaces for common software operations such as
memory management, semaphores/mutex, timer, etc.
In the north-bound direction, the device driver
interface with application through two set ofAPIs:
Data-Plane API and Control-Plane API.
Data-Plane API gives application full control over the
data-path in the CodeChip. Data-Plane API provides
methods for setting/getting configuration, retrieval of
device status/statistics.
On the other hand, Control-Plane API provides
mechanism for sending and retrieval of Layer 2/2.5/3
control packets, which is crucial for integrating thirdparty protocols into the SDK.
Detail API usage is described in the API programming
guide that is part of each SDK release.

PRELIMINARY VERSION

Page 1 of 5

www.arrivetechnologies.com

Data-Plane API Overview

The device driver provide management of the data-plane through a set of managed entities. These managed entities
abtract the underlying hardware resources into a more manageable and intuitive-to-use form.
The Switch Ports logically separate the underlying transport facilities and the packet processing and forwarding
features of the Carrier Ethernet CodeChip device. A Switch Port can be mapped one- to-one to an 802.3 Ethernet
Physical interface (ETY1G/ETY10G) or an 802.1AX Link Aggregation Group (LAG).
The Flow Points serves as service access points in the CodeChip. Through Flow Points, Ethernet frames, IP packets,
or MPLS packets that share the same characteristics can be grouped together for processing and forwarding.
A Forwarding Domain binds two or more Flow Points and thus create a man for frame forwarding among two or
more Switch Ports. Each Forwarding Domain have its own switching/routing table that is completely independent of
others.
The Maintenance Points provide Ethernet-based and/or MPLS-TP-based OAM functions. Their operation are fully
compliant with OAM functions that are defined in IEEE 802.1Q (2011) and ITU-T Y.1731 (2011).
These basic building blocks provides flexible ways for building various L2/L2.5/L3 applications:
Layer3 802.1Q (2011) Bridging service
Layer2 ETH Connection/Bridge Domain (E-LINE/E-LAN/E-TREE service)
ETH Connection over IP/MPLS or MPLS-TP (VPWS services)
ETH Bridge Domain over IP/MPLS or MPLS-TP (VPLS services)
IP-over-VLAN service
Layer3 IP/MPLS routing service
Layer3 IP over L3VPN tunnel (L3VPN service)

Control-Plane API Overview

2013 Arrive All Rights Reserved

PRELIMINARY VERSION

Page 2 of 5

www.arrivetechnologies.com

Control-Plane API Overview

Control-Plane/Data-Plane Interaction

Control-Plane API

Network Protocol Support

Both Data-plane and Control-plane API provides interface for three types of protocols:
Hardware-based: The protocol states are fully implemented in hardware. The effort to integrate these protocols into
target system is minimal.
Hardware-assisted: The protocol is partly implemented in hardware, and it requires some software to be fully
operational. The goal of hardware-assistedprotocol to move the not-so-critical part of a protocol to software
domain in order to save hardware resource.
Software-based: the protocol is implemented in software, the device driver only provides the mechanism for
sending/retrieval control packets. software-based protocols are usual from third-parties.

Sample Application - E-LINE Service

2013 Arrive All Rights Reserved

PRELIMINARY VERSION

Page 3 of 5

www.arrivetechnologies.com

Sample Application - E-LINE Service

Sample Application - E-LAN Service over MPLS-TP

Sample Application - Service OAM Support

2013 Arrive All Rights Reserved

PRELIMINARY VERSION

Page 4 of 5

www.arrivetechnologies.com

Sample Application - Service OAM Support

Software Development Support

Complete source code of the SDK are released with Programming Guide, Application Note(s), and Sample Codes. In
addition, on-site software integration support is also provided on demand.

About Arrive
Arrive is a broadband semiconductor solutions company with a broad portfolio of highly integrated systems-on-a-chip
products combining voice, data, Internet and multimedia content for worldwide telecommunications companies.
Our CodeChip replaces inflexible fixed-silicon ASICs with a programmable carrier-class FPGA solution. It includes a SoC
FPGA Image with a full software development kit, including APIs and Drivers, and is backed by the integration and testing
experience of Arrive.
For more information on our CodeChip product, go to: www.arrivetechnologies.com
Product brief version: PRELIMINARY - 2013/08/05
(*) The Arrive Logo and CodeChip are trademarks of Arrive Inc.
(*) IEEE is a trademark of the Institute of Electrical and Electronics Engineers.

2013 Arrive All Rights Reserved

PRELIMINARY VERSION

Page 5 of 5