SPRACY5 July 2021 AM67 , AM67 , AM67A , AM67A , AM68 , AM68 , AM68A , AM68A , AM69 , AM69 , AM69A , AM69A , DRA821U , DRA821U , DRA821U-Q1 , DRA821U-Q1 , DRA829J , DRA829J , DRA829J-Q1 , DRA829J-Q1 , DRA829V , DRA829V , DRA829V-Q1 , DRA829V-Q1 , TDA4AEN-Q1 , TDA4AEN-Q1 , TDA4AH-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4AP-Q1 , TDA4APE-Q1 , TDA4APE-Q1 , TDA4VE-Q1 , TDA4VE-Q1 , TDA4VEN-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VM , TDA4VM-Q1 , TDA4VM-Q1 , TDA4VP-Q1 , TDA4VP-Q1 , TDA4VPE-Q1 , TDA4VPE-Q1
Code Composer Studio is a trademark of Texas Instruments Incorporated.
Arm and Cortex are registered trademarks of Arm Limited (or its subsidiaries) in the US and/or elsewhere.
All trademarks are the property of their respective owners.
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.
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. |
|
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. |
|
Lauterbach | JTAG | Y(2) | Y | Y |
|
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. |
|
DFU | USB | Y | Y | Y |
Trace32/Lauterbach is a powerful tool when it comes to Arm®-based SoCs.
Trace32 can also be used to flash various memory types. JTAG interface needs to be pinned out on the board to use this approach. This enables customers who have Trace32 to flash boot images to eMMC and SPI memories.
Process of flashing involves CMM scripting that Lauterbach comprehends and a one time installation on Linux PC to connect to the TDA4. Using Trace32/Lauterbach to flash avoids dependency on a secondary boot media like UART/SD to burn images to the flash parts on the custom board.
Some custom boards only have a JTAG interface along with OSPI/QSPI flash. In absence of Trace32/Lauterbach, there is a Code Composer Studio™-based software flash writer application to flash the on-board flashes.
The solution provides an application that runs on MCU R5 and then provides a user-friendly menu to write and erase to the OSPI/QSPI flash.
OSPI and eMMC flashes on popular choice of external flashes used on TDA4 boards. Figure 2-1 depicts the default layout for the flash in the SDK, which can be changed in case the custom applications need a different layout.
Figure 2-2 is useful to decide which software tools can be used to flash the OSPI flash or eMMC boot partitions given the hardware constrains on the TDA4 custom board.
For example, in a case where the customer wants to flash OSPI but has no MAIN UART, USB or SD card interface, Figure 2-2 clearly directs the customer to use JTAG with CCS or Lauterbach or to use UNIFLASH tool.