Module | Supported CPUs | SysConfig Support | OS support | Key features tested | Key features not tested / NOT supported |
Clock | M4F | YES | FreeRTOS, NORTOS | Tick timer at user specified resolution, timeouts and delays | - |
CycleCounter | M4F | NA | FreeRTOS, NORTOS | Measure CPU cycles using CPU specific internal counters | - |
Debug | M4F | YES | FreeRTOS, NORTOS | Logging and assert to any combo of: UART, CCS, shared memory | - |
Heap | M4F | NA | FreeRTOS, NORTOS | Create arbitrary heaps in user defined memory segments | - |
Hwi | M4F | YES | FreeRTOS, NORTOS | Interrupt register, enable/disable/restore | - |
MPU | M4F | YES | FreeRTOS, NORTOS | Setup MPU and control access to address space | - |
Semaphore | M4F | NA | FreeRTOS, NORTOS | Binary, Counting Semaphore, recursive mutexs with timeout | - |
Task | M4F | NA | FreeRTOS | Create, delete tasks | - |
Timer | M4F | YES | FreeRTOS, NORTOS | Configure arbitrary timers | - |
Event | M4F | YES | FreeRTOS | Setting, getting, clearing, and waiting of Event bits | - |
Peripheral | Supported CPUs | SysConfig Support | Key features tested | Key features not tested / NOT supported |
EDMA | M4F | YES | Basic memory copy, DMA/QDMA channels, Interrupt/Polled, Manual/Event trigger, Chaining | - |
ESM | M4F | YES | Group and Error number selection, Tested ESM notifier with watchdog module | - |
GPIO | M4F | YES | Basic input/output, GPIO as interrupt | - |
HWA | M4F | YES | FFT, CFAR and compression/decompression, Interrupt/Polled, Manual/DMA trigger | - |
I2C | M4F | YES | Master mode, basic read/write, polling and interrupt mode | Slave mode not supported. |
MCAN | M4F | YES | RX, TX, interrupt and polling mode | - |
MCSPI | M4F | YES | Master/Slave mode, basic read/write, polling, interrupt and DMA mode | - |
Pinmux | M4F | YES | Tested with multiple peripheral pinmuxes | - |
QSPI | M4F | YES | Read direct, Write indirect, Read/Write commands | - |
SOC | M4F | YES | Lock/unlock MMRs, get CPU clock, CPU name, clock enable, set frequency | - |
UART | M4F | YES | Basic read/write, polling, interrupt mode, CPU/DMA mode | - |
WATCHDOG | M4F | YES | Window size and Expiry time selections, Reset mode, Digital windowed | - |
POWER | M4F | YES | Device LPDS Entry and Exit using sleep counter/SYNCIN IO. Device Idle3 entry and exist using frame timer | - |
LIN | M4F | YES | LIN Internal loopback, LIN external DIG/ANA loopback | LIN PHY Verification, Only Polling mode supported |
ID | Head Line | Module | Applicable Releases | Applicable Devices | Workaround |
MMWLPSDK-244 | HWA decompression output minor deviations | HWA driver | 5.01.00.03 | xWRL6432 | None |
MMWLPSDK-243 | Limited configuration support. | Motion and Presence detection OOB demo | 5.01.00.03 | xWRL6432 | None |
MMWLPSDK-229 | In low Power mode when the configuration is such that there is no enough time to entry-exit deep sleep, demo is halted. | Motion and Presence detection OOB demo | 5.01.00.03 | xWRL6432 | Change the configuration providing sufficient time for deep sleep entry-exist (i.e. increase frame periodicity) |
MMWLPSDK-238 | Debug multicore (APPIMAGE) demo application image doesn't boot. | Motion and Presence detection OOB demo | 5.01.00.03 | xWRL6432 | Load empty APPIMAGE and boot in functional mode and then load debug demo application. |
MMWLPSDK-173 | Memory Usage fault due to unaligned memory access with Demo and RPMF examples. | Motion and Presence detection OOB demo and Power Example | 5.01.00.03 | xWRL6432 | Disable trapping unaligned accesses by writing zero to "UNALIGN_TRP" field of Configuration and Control Register (CCR). |
MMWLPSDK-164 | Garbage to UART on Demo application startup with TeraTerm. | Motion and Presence detection OOB demo | 5.01.00.03 | xWRL6432 | Reconnect TeraTerm after loading Demo application. |
MMWLPSDK-174 | Timer configuration (APSS_RTI) does not enable source clock. | RTI Driver | 5.01.00.03 | xWRL6432 | Enable RTI clock field in "APP_RCM:IPCFGCLKGATE0" register and configure clocksource in "APP_RCM:APP_RTI_CLKCTL" register. |
This section lists changes which could affect user applications developed using older SDK versions. Read this carefully to see if you need to do any changes in your existing application when migrating to this SDK version relative to previous SDK version. Also refer to older SDK version release notes to see changes in earlier SDKs.