SPRACY5 July   2021 DRA821U , DRA821U , DRA829J , DRA829J , DRA829V , DRA829V , TDA4VM , TDA4VM , TDA4VM-Q1 , TDA4VM-Q1

 

  1.   Trademarks
  2. 1Introduction to Flashing Tools
    1. 1.1 Trace32/Lauterbach
    2. 1.2 CCS-Based Flash Writer
    3. 1.3 Other Software Tools
  3. 2Flash Devices on TDA4
    1. 2.1 Flashing OSPI and eMMC RAW Sectors
    2. 2.2 Flashing eMMC User Partition
  4. 3Prerequisites for Flashing TDA4
    1. 3.1 Boot Switch Settings
    2. 3.2 How to Generate a Tiny File System
    3. 3.3 Generating the eMMC tisdk-tiny-image.img
    4. 3.4 Running Until u-boot
      1. 3.4.1 UART Boot Mode
      2. 3.4.2 DFU Boot
      3. 3.4.3 SD Boot or any Other Boot Mode
    5. 3.5 Configuring Boot0 Partition and Partitioning eMMC
  5. 4OSPI Flashing
    1. 4.1 Flashing Bootloader Binaries
      1. 4.1.1 TI UNIFLASH Tool
        1. 4.1.1.1 Flashing Instructions
        2. 4.1.1.2 Linux Boot Binaries
        3. 4.1.1.3 RTOS Boot Binaries
    2. 4.2 dfu-util
      1. 4.2.1 Flashing Instructions
    3. 4.3 CCS/JTAG
      1. 4.3.1 Flashing Instructions
    4. 4.4 Trace32/Lauterbach
      1. 4.4.1 Flashing Instructions
    5. 4.5 u-boot
      1. 4.5.1 Flashing Instructions
  6. 5eMMC flashing
    1. 5.1 Flashing Bootloader Binaries
      1. 5.1.1 TI UNIFLASH Tool
        1. 5.1.1.1 Flashing Instructions
      2. 5.1.2 Trace32/Lauterbach
        1. 5.1.2.1 Flashing Instructions
      3. 5.1.3 dfu-util
        1. 5.1.3.1 Flashing Instructions
    2. 5.2 u-boot
      1. 5.2.1 Flashing Instructions
    3. 5.3 eMMC UDA Partition Flashing With tinyrootfs
      1. 5.3.1 dfu-util
      2. 5.3.2 u-boot + CCS/JTAG
        1. 5.3.2.1 Flashing Instructions

1 Introduction to Flashing Tools

For a particular boot media, given the hardware interfaces pinned out on the board, intent is to find a feasible solution to flash that particular boot media with bootloader and file system images.

Most software tools have some constraints that are listed in Table 1-1. From this, software tools that are supported for a particular boot media can be inferred.

Table 1-1 Software Tools Constraints
Software Tools Hardware Interface Boot Media Constraints
OSPI NOR eMMC QSPI NOR
UNIFLASH UART L(1)
Only bootloader images can be flashed. UBIFS cannot be flashed.		 L
Only eMMC boot0 (RAW) partition can be flashed.		 L
Only bootloader images can be flashed. UBIFS cannot be flashed.
  • Support for UART boot mode.
  • MCU_UART0 should be pinned out on the board.
  • Flashing of only raw sectors supported for eMMC
CCS JTAG L
Only bootloader images can be flashed. UBIFS cannot be flashed.		 L
Only eMMC user (UDA) can be flashed with tiny file system.
Bootloader images should be already flashed.		 L
Only bootloader images can be flashed. UBIFS cannot be flashed.
  • Presence of debugger interface.
  • Flashing speed depend on choice of JTAG.
Lauterbach JTAG Y(2) Y Y
  • Licensed software
u-boot UART, MMCSD, DFU boot Y
Using SD card, JTAG, Ethernet etc. with u-boot.		 Y
Using SD card, JTAG, Ethernet etc. with u-boot.		 Y
Using SD card, JTAG, Ethernet etc. with u-boot.
  • u-boot should be flashed using other interfaces first.
DFU USB Y Y Y
(1) L = Limited support
(2) Y = Full support
Note: UNIFLASH by default uses MCU_UART0.
Universal asynchronous receiver/transmitter (UART) boot to u-boot needs MCU_UART0 and one of the MAIN_UART to which u-boot will print.