SWRS202C May 2017 – January 2022 AWR1443
PRODUCTION DATA
Refer to the PDF data sheet for device specific package drawings
The Main (Control) System includes ARM’s automotive grade Cortex-R4F processor clocked at 200 MHz, which is user programmable. User applications executing on this processor control the overall operation of the device, including Radar Control via well-defined API messages, radar signal processing (assisted by the radar hardware accelerator) and peripherals for external interface.
The Main (Control) System plays a big role in enabling autonomous operation of AWR1443 as a radar-on-a-chip sensor. The device includes a quad serial peripheral interface (QSPI) which can be used to download customer code directly from a serial flash. A (classic) CAN interface is included that can be used to communicate directly from the device to a CAN bus. An SPI/I2C interface is available for power management IC (PMIC) control when the AWR1443 is used as an autonomous sensor.
For more complex applications, the device can operate under the control of an external MCU, which can communicate with AWR1443 device over an SPI interface. In this case, it is possible to use the AWR14xx as a radar sensor, providing raw detected objects to the external MCU. External MCU could reduce the application code complexity residing in the device and makes more memory available for radar data cube inside the AWR1443. This configuration also eliminates the need for a separate serial flash to be connected to the AWR1443.
Furthermore, the external MCU can provide faster interfaces, such as CAN-FD or Ethernet, for the radar sensor to connect to a central processing unit (CPU). In such a distributed configuration, multiple AWR1443 devices mounted around the vehicle can connect to the CPU, providing a surround view. The external MCU itself is low-cost, because the low-level radar signal processing is accomplished inside the AWR1443, using the hardware accelerator, while the higher-layer intelligence and complex algorithms reside in the common CPU, making the overall solution cost-effective.
Note that although four interfaces – one CAN, one I2C and two SPI interfaces – are present in the AWR1443 device for external communication and PMIC control, only two of these interfaces are usable at any point in time.
The total memory (RAM) available in the Main subsystem is 576 KB. This is partitioned between the R4F program RAM, R4F data RAM and radar data memory. The maximum usable size for R4F is 448 KB and this is partitioned between the R4F’s tightly coupled interfaces TCMA (320 KB) and TCMB (128 KB). Although the complete 448 KB is unified memory and can be used for program or data, typical applications use TCMA as program and TCMB as data memory.
The remaining memory, starting at a minimum of 128 KB, is available to be used as radar data memory for storing the ‘radar data cube’. It is possible to increase the radar data memory size in 64 KB increments, at the cost of corresponding reduction in R4F program or data RAM size. The maximum size of radar data memory possible is 384 KB. A few example configurations supported are listed in #GUID-0A28B289-8932-43E0-8103-1C305498357E/T4362547-31.
OPTION | R4F PROGRAM RAM | R4F DATA RAM | RADAR DATA MEMORY |
---|---|---|---|
1 | 320KB | 128KB | 128KB |
2 | 256KB | 128KB | 192KB |
3 | 256KB | 64KB | 256KB |
4 | 128KB | 64KB | 384KB |
The Main Subsystem, Cortex-R4F memory map is shown in #GUID-0A28B289-8932-43E0-8103-1C305498357E/T4362547-33.
Name | Frame Address (Hex) | Size | Description | |
---|---|---|---|---|
Start | End | |||
CPU Tightly Coupled Memories | ||||
TCMA ROM | 0x0000_0000 | 0x0001_FFFF | 96KiB | Program ROM |
TCM RAM-A | 0x0020_0000 | 0x0024_FFFF | 128–320KiB | Memory size is dependant on the allocation done in #GUID-0A28B289-8932-43E0-8103-1C305498357E/T4362547-31, R4F RAM |
TCM RAM-B | 0x0800_0000 | 0x0802_FFFF | 64–128KiB | |
System Peripherals | ||||
Mail Box MSS<->RADARSS | 0xF060_1000 | 0xF060_17FF | 2KiB | RADARSS to MSS mailbox memory space |
0xF060_2000 | 0xF060_27FF | 2KiB | MSS to RADARSS mailbox memory space | |
0xF060_8000 | 0xF060_80FF | 188B | MSS to RADARSS mailbox Configuration Registers | |
0xF060_8060 | 0xF060_86FF | 188B | RADARSS to MSS mailbox Configuration Registers | |
PRCM & Control Module | 0xFFFF_E100 | 0xFFFF_E2FF | 756B | TOP Level Reset, Clock management registers |
0xFFFF_FF00 | 0xFFFF_FFFF | 256B | MSS Reset, Clock management registers | |
0xFFFF_EA00 | 0xFFFF_EBFF | 512KiB | IO Mux module registers | |
0xFFFF_F800 | 0xFFFF_FBFF | 352B | General-purpose control registers | |
0x5000_0400 | 584B | TPCC,TPTC,ADC buffer configuration, status registers | ||
GIO | 0xFFF7_BC00 | 0xFFF7_BDFF | 180B | GIO module configuration registers |
DMA | 0xFFFF_F000 | 0xFFFF_F3FF | 1KiB | DMA-1 module configuration registers |
VIM | 0xFFFF_FD00 | 0xFFFF_FEFF | 512B | VIM module configuration registers |
RTI-A | 0xFFFF_FC00 | 0xFFFF_FCFF | 192B | RTI-A module |
RTI-B | 0xFFFF_EE00 | 0xFFFF_EEFF | 192B | RTI-B module register space |
Serial Interfaces and Connectivity | ||||
QSPI | 0xC000_0000 | 0xC07F_FFFF | 8MB | QSPI –Flash Memory space |
0xC080_0000 | 0xC0FF_FFFF | 116B | QSPI module configuration registers | |
MIBSPI | 0xFFF7_F400 | 0xFFF7_F5FF | 512B | MIBSPI-A module configuration registers |
SPI | 0xFFF7_F600 | 0xFFF7_F7FF | 512B | SPI module configuration registers |
SCI-A/UART | 0xFFF7_E500 | 0xFFF7_E5FF | 148B | SCI-A module configuration registers |
SCI-B/UART | 0xFFF7_E700 | 0xFFF7_E7FF | 148B | SCI-B module configuration registers |
CAN | 0xFFF7_DC00 | 0xFFF7_DDFF | 512B | CAN module configuration registers |
I2C | 0xFFF7_D400 | 0xFFF7_D4FF | 112B | I2C module configuration registers |
ADC Buffer | 0x5200_0000 | 16KiB | ADC ping pong buffer memory space | |
CBUF_FIFO | 0x5202_0000 | 16KiB | Common buffer memory space | |
Hardware FFT accelerator | 0x5008_0000 | 0x5008_07FF | 512B | FFT Accelerator PARAM memory |
0x5008_0800 | 0x5008_0FFF | 264B | FFT accelerator Configuration registors | |
0x5008_1000 | 4KiB | FFT accelerator Window registers | ||
0x5203_0000 | 0x5203_7FFF | 32KiB | FFT accelerator Memory -1 space | |
0x5203_8000 | 32KiB | FFT accelerator Memory -2 space | ||
L3 Memory | ||||
L3 Shared Memory | 0x5100_0000 | 384KiB | L3 Shared memory space | |
Interconnects | ||||
PCR | 0xFFF7_8000 | 0xFFF7_87FF | 1KiB | PCR-1 interconnect configuration port |
PCR-2 | 0xFCFF_1000 | 0xFCFF_17FF | 1KiB | PCR-2 interconnect configuration port |
128 bit SCR | 0x5207_0000 | 128B | 128 bit SCR configuration port | |
Safety Modules | ||||
CRC | 0xFE00_0000 | 0xFEFF_FFFF | 16KiB | CRC module configuration registers |
PBIST | 0xFFFF_E400 | 0xFFFF_E5FF | 464B | PBIST module configuration registers |
STC | 0xFFFF_E600 | 0xFFFF_E7FF | 284B | STC module configuration registers |
DCC-A | 0xFFFF_EC00 | 0xFFFF_ECFF | 44B | DCC-A module configuration registers |
DCC-B | 0xFFFF_F400 | 0xFFFF_F4FF | 44B | DCC-B module configuration registers |
ESM | 0xFFFF_F500 | 0xFFFF_F5FF | 156B | ESM module configuration registers |
CCMR4 | 0xFFFF_F600 | 0xFFFF_F6FF | 136B | CCMR4 module configuration registers |
Peripheral Memories (System & Non System) | ||||
CAN RAM | 0xFF1E_0000 | 0xFF1F_FFFF | 128KB | CAN RAM memory space |
DMA RAM | 0xFFF8_0000 | 0xFFF8_0FFF | 4KB | DMA RAM memory space |
VIM RAM | 0xFFF8_2000 | 0xFFF8_2FFF | 2KB | VIM RAM memory space |
MIBSPIA-TX RAM | 0xFF0E_0000 | 0xFF0E_01FF | 0.5KB | MIBSPIA-TX RAM memory space |
MIBSPIA- RX RAM | 0xFF0E_0200 | 0xFF0E_03FF | 0.5KB | MIBSPIA- RX RAM memory space |
Debug Modules | ||||
Debug Sub System | 0xFFA0_0000 | 0xFFAF_FFFF | 244KiB | Debug subsystem memory space and registers |