PDK/PDK TDA Directory Structure

Overview

The PDK contain a number of software components. These components are all installed in one common install path specified when running the installer.

NOTE

Not all components are applicable for all platforms.

Software Component Directories

The PDK package includes the following components:

• docs - This folder contains various collateral like test reports, MISRAC and static analysis reports.

• binary - The generated executable and obj files are placed in this directory. The generated library is placed in an appropriate path under component specific directory

• build - This folder will contain the Makefile required to build libraries (drivers, system_config, platform, utils, i2clib, etc.) and example applications (Uart, mcspi, hsi2c etc.). The PDK only supports Makefile based build

• examples - Each of the components contains the example folder having sample demo application to demonstrate the capabilities of the component

• boot/sbl_auto - This contains the TDA secondary bootloader
  • sbl_lib: This layer contains APIs needed for parsing and loading multicore App Image and booting the slave cores. This library is used by both bootloader application and master application
  • sbl_utils: This layer is used only by the bootloader application and contains APIs for communicating between boot media and master core
  • qspiflash: This folder contains source code for QSPI flash library. This provides API’s to configure and access the QSPI flash. The initialization API takes in device type as parameter and configures the flash to be read in one bit or 4 bit mode
    - API’s are provided to read and write from the flash in cfg port mode, memory mapped mode (using CPU and EDMA).
    - API’s are provided to erase the flash (single block or entire flash)
  • norflash: This folder contains source code for NOR flash library. Generic API’s are provided top configure, read and write to the NOR flash
    - Supports AMD and Intel based NOR flash commands
  • sbl_apps: This contains the bootloader application that loads and boots the application image.
  • prebuilt_binaries: Prebuild binaries for SBL.
  • tools: PC tools to generate SBL images

• csl - This directory contains the Chip Support Library register (CSL-RL) and functional (CSL-FL) API source files for supported peripherals as well as examples. Refer to CSL page for details.

• diag - This folder contains APIs for diagnostics of Safety IPs. The DiagLib provides APIs for ADC, CRC, McSPI, DCAN & ECC (EMIF, OCMC & IPU) modules. Refer to DIAGLIB page for details.

• drv - This folder contains the TI RTOS driver and libraries for various modules
  • bsp_lld: This folder contains the driver and libraries for I2C, McSPI and UART.Refer to BSP LLD page for details.
    
    • i2c: This folder contains the GIO/IOM SYSBIOS I2C driver files and APIs to control IO expanders. I2C could be used to read / write into any of the video on-board devices such as SII9022a, TVP7002, IO Expanders or sensors such as MT9V022, etc.
      
    • mcspi: This folder contains GIO/IOM SYSBIOS McSPI driver to configure McSPI Controller. SPI is a high-speed synchronous serial input/output port that allows a serial bit stream of programmed length (one to 16 bits) to be shifted into and out of the device at a programmed bit-transfer rate. SPI is normally used for communication between the micro-controller and external peripherals or another micro-controller.
      
    • uart: This folder contains GIO/IOM SYSBIOS UART driver. This module contains the interfaces, data types and symbolic definitions that are needed by the application to utilize the services of the UART device driver.
  • fw_l3l4: This folder contains the driver to configure L3 and L4 firewall.
  • ipc_lite: This module is built on top for mailbox CSL-FL to abstract functionality of mailboxes and makes it usable in software stack with or without operating system. IPC-Lite supports event multiplexing, which means application writers can register multiple callbacks for one remote core using single mailbox queue. It supports 32bit value to be transferred across from sender core to receiver core. IpcLib does not use any dynamic memory allocation or shared memory to transferring messages. Refer to IPCLITE page for details.
  • pm: The power management (PM) software enables optimal power consumption and thermal management scalable across TDA2xx, TDA2px, TDA2ex, TDA2ex_17x17 and TDA3xx. It is divided into three layers namely.
    - PRCM Database (DB): abstracts the SoC specific PRCM details regarding the registers, the partitioning of the device and the clock tree details.
    - Power Manager Hardware Abstraction Layer (PMHAL): abstracts the programming sequence of atomic power management actions like configuring a PD, CD, PLL, bandgap thermal sensors etc.
    - Application Interface Layer (PM Library - PMLIB): abstracts all PRCM architecture details to the application where the developer provides top level requests of switching on or off a module or configuring a certain module clock to a certain desired frequency and putting CPUs to low power. Refer to PM page for details.
  • stw_lld: This folder contains the drivers/libraries for fatlib, i2clld, uart console modules.
  • vps: This folder contains all the driver implementations for video peripherals - VIP, VPE, ISS, CAL and DSS. This folder also contains routines for VIP, VPE, ISS and DSS core drivers and HAL layer routines. The VPS drivers are segregated into VIP, DSS, ISS, FVID2, VPS OSAL and VPW drivers. Refer to VPS page for details.