TIDUF89 September 2024
The IWRL6432AOP consumes very little power through the deep sleep modes, which achieve <0.5mW power consumption when the radar is not being used. While xWRL6432 Low Power Radar - Power Optimization Techniques, application note covers this in extensive detail, this section can focus specifically on the ways to reduce power that do not affect detection range or false alarm rate.
The IWRL6432AOP device can save power in deep sleep by reducing the amount of memory retained in the Deep Sleep mode. On the IWRL6432, memory instances consume approximately 45µW or 64kB in power-down retention mode. If memory within a cluster is not retained, IWRL6432 can consume approximately 20µW/64kB. To further save power when memory is not retained, some memory clusters on the IWRL6432 are grouped together, and power switches are deployed on the corresponding SRAM power rails. If all the clusters in a group are not retained during Deep Sleep, switches for the group are opened, completely powering off the group, causing the memory to consume 0µW/kB while completely powered off (no retention).
These switches can be set in sysconfig. Table 2-2 explains which clusters correspond to which sections in memory.
| Cluster No. | Memory Segment | Cluster Name | Size (kB) | Starting Memory Location | Notes |
|---|---|---|---|---|---|
| APPSS Cluster #1 | RAM_1 | RAM1A | 64 | 0x00400000 | |
| APPSS Cluster #3 | RAM_1 | RAM1B | 64 | 0x00410000 | |
| APPSS Cluster #4 | RAM_1 | RAM1C | 128 | 0x00420000 | |
| APPSS Cluster #2 | RAM_2 | RAM2A | 16 | 0x00440000 | |
| APPSS Cluster #5 | RAM_2 | RAM2B | 112 | 0x00444000 | |
| APPSS Cluster #5 | RAM_3 | RAM3 | 128 | 0x00460000 | |
| APPSS Cluster #6 | APP_SHMEM_1 | Shared RAM 1 | 128 | 0x00480000 | When accessed from HWA, starts at 0x60000000 |
| APPSS Cluster #6 | APP_SHMEM_2 | Shared RAM 2 | 128 | 0x004A0000 | When accessed from HWA, starts at 0x60000000 |
The linker.cmd file can be used to dictate where data is stored in memory. Efficient design can store the variables that get reset every frame, such as the major motion point cloud, in clusters that are NOT retained during deep sleep. However, other variables that are not reset every frame, such as the occupancy status in each detection zone, needs to be placed in memory banks that are retained during deep sleep. This is accomplished in the video doorbell demo by default.