Overview
2
NET+Works with GNU Tools BSP Porting Guide
Overview
After you complete a system analysis that includes data throughput, I/O and
processing requirements and select the NET+ARM processor as the target processor,
you can begin two efforts: hardware design and software development.
Hardware design might require a complete new board design, reusing or modifying
a previous design, or using an off-the-shelf NET+ARM module. Target hardware
often is unavailable to software developers for weeks – and sometimes even
months. To minimize product time-to-market, you can begin software development
immediately by partitioning the effort into two distinct tasks: application
development and the board support package (BSP).
Application development
Application development involves piecing together hardware-independent, high-
level software components, while the BSP provides hardware-specific services along
a standardized application programming layer (API) to the application software.
By using a NET+ARM development board and its associated BSP, you can begin
software development immediately. NET+OS is delivered with BSPs to support all
NET+ARM development board platforms and all DIGI Connect products. Each BSP is
tailored to support the development board’s specific target processor (for example,
the NS9360 or NS7520) and the components that surround the processor (memory
and PHY).
The development board is ideal for prototyping general network services, including
Web pages, private management information bases (MIBs), FTP servers, SMTP clients,
or network startup characteristics such as DHCP or Auto IP. In addition, you can pro-
totype non-volatile system configuration, I/O protocols, field upgrade mechanisms,
or file system requirements effectively with a NET+ARM development board.
Alternatively, the BSP enables you to create the platform-specific software needed
to support a hardware platform. Because the BSP is hardware-specific, completing
this software requires the target hardware – and so must wait until the target
hardware is debugged and available.
When the hardware target becomes available, you can create the BSP and port the
application to the target hardware. Because application software maintains the
BSP standardized API, it reduces the effort required to port the application to the