MCUSW
Getting Started

MCUSW

SoC's such as AM62X/AM62A/AM62P integrate an MicroController Unit Subsystem (MCU SS) as an chip-in-chip. It operates using a separate voltage supply, clock sources and resets and includes the components needed for device management. This allows the MCUSS to function continuously regardless of the state of the rest of the device. MCU SS has one or more DUAL core Cortex R5F (number of instances varies on the variant of the device, please refer the device reference manual)

MCUSW consists of two main components, Microcontroller abstraction layer (MCAL) & Demonstration applications (MCUSS Demos). Its is expected to be hosted on Cortex R5F 0 in MCU Domain or other Cortex R5F in main domain. The table below lists SoC/Cores on which MCUSW can be hosted.

Supported Devices

Device Family Devices Also known by other names
Sitara MPU AM62AX -
Sitara MPU AM62X -
Sitara MPU AM62P -

Core Naming Conventions

SoC Family Cores Names Referred as Comments
AM62AX/AM62P MCU R5F Core 0 mcu 0 0 Please refer the "MCAL_SitaraMPU_release_notes.html" to determine if this release supports this platform. Note that all computing cores might not be supported in MCUSW
AM62X DM R5F Core 0 mcu 0 0 Please refer the "MCAL_SitaraMPU_release_notes.html" to determine if this release supports this platform. Note that all computing cores might not be supported in MCUSW

Getting access to MCAL

In case of Sitara MPU, MCUSW is released seperatly and is not part of SDK.

  1. Configurator and Compliance Support Package
    1. Configurator package is required to update/modify MCAL configurations
    2. For SMPU platforms, CSP and plugins will be present inside the release package not as separate installer.
  2. Refer (Installation Steps) for detailed installation steps

License for Configurator

  1. EB Tresos requires license to use it refer (Installing Elektrobit Tresos) for details
  2. EB provides limited-pool of license that could be shared by TI with its customers
    1. Classified as limited-period license & permanent license
    2. Limited-period license are expected to be used during development (typically 3 months, 6 months) and permanent license for production
    3. In cases where development is greater than license validity period, TI can provide additional licenses
  3. Login to MySecureSW, and Request Access to the EB Tresos Tool and License from here License Request
  4. Once license are received
    1. Follows steps listed in (Client License Administrator)
    2. IMPORTANT
      1. TI shares user details with EB on quarterly basis (name of organization and email id to whom license is released, fulfillment-id and user name). EB uses this data for license administration
      2. Share Fulfillment ID : Once license is activated, the "fulfillment-id" is to be shared with FAE/TI Engineer who provided license
  5. Third party (AUTOSAR Vendor / Other co-development organizations)
    1. TI can provide the EB licenses to other third party which is engaged by customers
    2. Steps and procedure will remain same as listed above
  6. Number of licenses
    1. Since TI receives finite-set of licenses from EB, TI will have to ration these among it's customers
    2. Based on customer needs / business needs number of license released to customer will be restricted
    3. Please request licenses on need basis

Back To Top

Package Contents

MCU Demos

Demonstrates usage of various drivers / software provided for MCU SS. These applications could employ FREERTOS as OS and use MCAL and/or PDK drivers.

Please note, these demos are currently not supported on Sitara MPU Family of Devices.

MCAL

MCAL is the lowest layer of the AUTOSAR Basic Software architecture. MCAL contains drivers with direct access to the μC internal peripherals. MCAL is a hardware specific layer that ensures a standard interface to the Basic Software.

This user guide details procedure that are common to all MCAL drivers, please refer driver specific user guide for finer details of driver.

Supported Drivers

Driver Comments Refer Supported SoC Supported Cores
Can Driver for built-in CAN peripheral (Can User Guide) AM62X/AM62AX/AM62P MCU 0 0
Cdd Ipc Driver for inter-processor communication (Cdd Ipc User Guide) AM62X/AM62AX/AM62P MCU 0 0
Eth Driver for built in CPSW 2G port (Eth & EthTrcv User Guide) AM62X/AM62AX/AM62P MCU 0 0
EthTrcv Driver for Ethernet Transceiver and tested with DP83867 (Eth & EthTrcv User Guide) AM62X/AM62AX/AM62P MCU 0 0
Fls Driver for external Flash Device (Fls User Guide) AM62X/AM62AX/AM62P MCU 0 0
Gpt Driver for General purpose timer (Gpt User Guide) AM62X/AM62AX/AM62P MCU 0 0
Spi Driver for Serial Peripheral Interface (Spi User Guide) AM62X/AM62AX/AM62P MCU 0 0
Dio Driver for control of GPIO (Dio User Guide) AM62X/AM62AX/AM62P MCU 0 0
Wdg Driver for built in WWDT(Windowed Watchdog Timer) (Wdg User Guide) AM62X/AM62AX/AM62P MCU 0 0
Mcu Driver for built in MCU (CLOCK hardware) (Mcu User Guide) AM62X/AM62AX/AM62P MCU 0 0

Back To Top

Dependencies

Dependencies can be categorized as listed below. Please note that depending on the intended use, the dependencies vary (e.g. for integration vs running demo applications only)

  1. Hardware Dependencies (Hardware Dependencies)
  2. Software Dependencies (Software Dependencies)

Hardware Dependencies

Please refer to the Sitara MPU Device SDK User Guides for Hardware Boot Mode details.

Built in emulator

Sitara MPU Device EVMs includes an on-board XDS110 USB emulator, which could be used with CCS. Please refer to ti.com or contact your FAE for documents describing the EVM.

Emulator

An external emulator such as Spectrum Digital XDS560V2 could be used, all steps remain identical to steps listed in (Built in emulator) with creation of Target Configuration being the exception.

While creating the target, please select the emulator that is being used.

Software Dependencies

For Sitara MPU Family of Devices:

Please refer to release notes for updated information on supported Compilers.

MCU+SDK

Get required MCU Plus SDK release version from below locations, and place it in same location as mcusw folder.

This is required for building and validating MCAL Applications.

  1. TI Website for AM62X
  2. TI Website for AM62AX
  3. TI Website for AM62PX

MCAL Example Application

  • Applications rely on SCI Client to request interrupt number as resource
  • Applications rely on Hwip to register MCAL modules interrupts
  • Applications rely on UART driver to print on console

Back To Top

MCAL Configurator : Elektrobit Tresos

Elektrobit Tresos (EB) is used to configure the MCAL modules, please refer (MCAL Configurator User Guide) for details.

This tool would be required to re configure the MCAL modules provided by TI.

Back To Top

IDE (CCS)

Code Composer Studio is an integrated development environment (IDE) that supports TI's Microcontroller and Embedded Processors portfolio.

Please refer to Release Notes to find the supported CCS Version. Please refer to SDK User Guides for CCS Setup instructions.

Back To Top