Difference between revisions of "Board Support Package"

From SEGGER Wiki
Jump to: navigation, search
(Blanked the page)
(Tag: Blanking)
Line 1: Line 1:
  +
Every embOS port shipment comes with board support packages for different devices and evalboards.
  +
Each board support package comes with all required initialization code and a project for the IDE of your choice.
  +
  +
=== What is an embOS board support package? ===
  +
A embOS board support package consists of two parts:
  +
* The necessary device and board specific software routines
  +
* A project for a specific IDE with which embOS runs on a specific hardware out of the box.
  +
  +
Most of the routines are device specific. These are for example:
  +
* Startup code and vector table
  +
* Interrupt controller initialization
  +
* Hardware timer initialization
  +
  +
The board specific routines are for example:
  +
* LED initialization/control
  +
* External memory initialization
  +
* Uart initialization for a specific board connector (used for embOSView)
  +
  +
An embOS BSP can easily be used on another hardware with the same device since most of the routines are device but not board specific.
  +
The embOS BSP code is implemented as source code in the files ''RTOSInit.c' and ''BSP.c''.
  +
Further BSP files like ''BSP_Uart.c'' are optional.
  +
  +
=== What is included? ===
  +
All necessary initialization code to run embOS
  +
  +
=== What is not included? ===
  +
The embOS board support package does not include any code for additional peripherals like I2C or SPI.
  +
But silicon vendor device hardware abstraction layer like STM32Cube HAL can easily be used with embOS.
  +
  +
=== What can I do when no BSP for my hardware exists? ===
  +
when no BSP for your hardware exists you can choose to:
  +
* Create the BSP on your own or use a BSP for another hardware but same device
  +
* Ask SEGGER to create the BSP
  +
  +
In the latter case please send us detailed information about your hardware.
  +
The hardware can be an evalboard or even your custom hardware.
  +
  +
=== Conclusion ===
  +
If you like to run embOS a specific device and hardware please select the according embOS port first.
  +
This embOS port must support the core of your device and the compiler of your choice.
  +
You can then check if an according BSP is already included.
  +
  +
In case of doubt please don't hesitate to contact us.

Revision as of 14:28, 5 June 2020

Every embOS port shipment comes with board support packages for different devices and evalboards. Each board support package comes with all required initialization code and a project for the IDE of your choice.

What is an embOS board support package?

A embOS board support package consists of two parts:

  • The necessary device and board specific software routines
  • A project for a specific IDE with which embOS runs on a specific hardware out of the box.

Most of the routines are device specific. These are for example:

  • Startup code and vector table
  • Interrupt controller initialization
  • Hardware timer initialization

The board specific routines are for example:

  • LED initialization/control
  • External memory initialization
  • Uart initialization for a specific board connector (used for embOSView)

An embOS BSP can easily be used on another hardware with the same device since most of the routines are device but not board specific. The embOS BSP code is implemented as source code in the files RTOSInit.c' and BSP.c. Further BSP files like BSP_Uart.c are optional.

What is included?

All necessary initialization code to run embOS

What is not included?

The embOS board support package does not include any code for additional peripherals like I2C or SPI. But silicon vendor device hardware abstraction layer like STM32Cube HAL can easily be used with embOS.

What can I do when no BSP for my hardware exists?

when no BSP for your hardware exists you can choose to:

  • Create the BSP on your own or use a BSP for another hardware but same device
  • Ask SEGGER to create the BSP

In the latter case please send us detailed information about your hardware. The hardware can be an evalboard or even your custom hardware.

Conclusion

If you like to run embOS a specific device and hardware please select the according embOS port first. This embOS port must support the core of your device and the compiler of your choice. You can then check if an according BSP is already included.

In case of doubt please don't hesitate to contact us.