BSP Requirements

The intention of this page is to collect requirements/suggestions/ideas to be included in a generic BSP requirements document. This document shall be the strting point for new BSP developments to be carried out by the software development department or external software partners alike.

Things to consider when adding to the list:

• architecture agnostic
• sufficiently detailed

• Naming convention for archives to be published on website
  • E.g.: TQ-BSP-<MODULE-NAME>-Rev.1234-<BSP-PART>.<EXT>
    with
    <MODULE-NAME> = TQMa28 | TQMa335x | TQMa53 | TQMa6x | TQMLS102xA | ARM¹⁾
    <BSP-PART> = bin | bsp | licenses | pkg
    <EXT> = tar.gz | ???

• Show boot source/device (mmc0/1, spi, etc.) in boot messages
• Provide unififed update “commands” (i.e. U-Boot variables) as for platform MBa335x (cf. BSP Rev.0115 )

• Use LTS Kernel if possible
• Consider kernel upgrades (preferrably to LTS versions) during product marketing window +2 years (for late entrants)
• Provide extra kernels (on demand), e.g. Vendor-Kernel (NXP, TI, etc.), RT-PREEMPT, Xenomai, …

• Define all interfaces (device definition and pin muxing groups) available on the corresponding starterkit (even if only a subset can be used at the same time; if necessary disable nodes conflicting with the default pin multiplexing)