| |
We have worked on myriad
technologies across the embedded domain: |
 |
|
 |
Microsoft: Win CE 4.1, 4.2, 5.0, Platform
Builder 4.x. |
|
Sun: Java 2 Micro Edition (J2ME),
CLDC 1.0-2.0, MIDP 1.0-2.0. |
|
RTOS (Nucleus), Embedded Linux |
|
Symbian, BREW, PPSM. |
| |
|
|
| |
| |
We have developed solutions
based on major industry vendors and
OEM’s for different hardware platforms,
including: |
|
|
|
strongARM |
|
Sierra |
|
Sharps |
|
Aruba NEC |
|
CEPC |
| |
|
|
|
| ADI has undertaken development at the
application and system level for multiple
embedded platforms, processors and boards. |
| |
| |
At the systems level
we have experience in: |
|
|
|
Creating Board Support Packages &
boot loaders |
|
Implementing device drivers (USB,
keyboard, display, mouse, touch panel,
WLan 802.11 |
|
Implementing & integrating protocol
stacks |
|
Driver optimization and performance
tuning |
| |
|
|
| |
| |
At the application
level we have skills and experience
in: |
|
|
|
Developing low memory footprint solutions
|
|
Creating innovative solutions making
the best use of available device resources
& functionality |
|
Porting of existing applications from
one device to another (including porting
subset from desktop) |
| |
|
|
| |
Some of our significant involvements with
embedded solutions can be broadly listed out
under the following sub-domains:
All board hardware-specific code is commonly
referred to as Board Support Package (BSP).
A BSP typically contains a boot loader,
the OEM adaptation layer (OAL), and board-specific
device drivers. We at ADI have been involved
with BSP development across the Win CE platform.
We provide the expertise needed to create
a totally new BSP from scratch or to develop
a new one by cloning an existing BSP designed
for similar hardware. Additionally, we also
offer migration support for updating an
existing BSP to a fully compatible Win CE.NET
4.2 feature set BSP.
|
| |
| |
| |
| |
Our BSP expertise spans
across the following key-areas: |
|
|
|
Developing boot loader programs |
|
Developing an OAL |
|
Creating device drivers |
|
Modifying platform configuration
files |
| |
|
|
| |
These include embedded solutions which require
developing low level hardware drivers for
small devices based on the Win CE and Nucleus
embedded platform. Some of these drivers have
been used for interfacing peripherals like
Keyboard, USB (keyboard and mouse), Scanners,
Printers, and PCMCIA cards.
Read more about these solutions under the
CEApps project profile.
For the WLAN device driver developed for Nucleus,
please refer to the “Elettra’
project profile. |
| |
|
| |
We have been involved with application development
for some very interesting devices under the
home appliance domain (like Audio equipment)
and the industrial domains (such as IR Cameras
and Signal Processors). These devices offer
limited sets of controls and provide interesting
development challenges. Our work has involved
developing application modules that maximize
the utilization of base hardware functionalities.
With small displays and restricted screen
resolutions, user interface (UI) development
in such devices plays a major role in the
usability of the device. We have done significant
work in UI development for embedded solutions,
where base hardware functionalities and the
application modules were successfully linked
to meticulously designed and fine-tuned UI’s
across various devices. |
| |
|
| |
ADI has vast expertise in managing huge
code bases and complex build operations and
has successfully delivered a number of cross
platform porting solutions. With various small
device hardware platforms floating around,
there has been a stable demand for porting
embedded solutions across platforms. Our team
of expert developers has a strong hand at
understanding system architecture and complex
code bases, writing optimized and platform
independent code, thus enabling us to carry
out porting operations efficiently.
ADI has keen insights into writing loosely
coupled, platform independent modules, through
the provision of suitable device abstraction
layers. This allows for a ‘pick-and-choose’
approach for quick integration onto target
handsets. This leads to significant time savings
during the integration process. |
| |
| |
Key achievements on
the porting or integration projects
executed so far: |
|
|
|
Understanding the capabilities of
a platform |
|
Comparison with other platforms |
|
Identifying the most suitable and
effective approach for porting |
| |
|
|
