NXP S32M27x
Contents
The S32M27x family from NXP includes a Cortex-M7 based MCU. The S32M27x family is supported since J-Link software version V7.94.
Internal Flash
Supported Regions
S32M276
| Flash Bank | Base address | Size | J-Link Support |
|---|---|---|---|
| Code flash 0 | 0x00400000 | Up to 512 KB | 
|
| Code flash 1 | 0x00480000 | Up to 512 KB |
|
| Data flash | 0x10000000 | Up to 64 KB |
|
| UTEST | 0x1B000000 | Up to 8 KB | 
|
ECC RAM
The ITCM and DTCM must be properly initialized with correct ECC before any read operation to avoid any code runaway or software malfucntion or core lockup. ITCM must be initialized with 64-bit writes whereas DTCM can be initialized with 32-bit or 64-bit writes. The following memory ranges are initialized by the J-Link on connect by default. Other ranges needs to be initialized by the application / boot ROM.
| Memory | Address | Size |
|---|---|---|
| DTCM0 | 0x20000000 | 32 KB |
| SRAM0 | 0x20400000 | 16 KB |
Main core
Init/Setup
- Initializes the ECC RAM, see ECC RAM
- Enables debugging
Reset
- Device specific reset is performed, see Reset
Attach
- Attach is not supported because the J-Link initializes certain RAM regions by default
Reset
The J-Link performs a device specific reset sequence.
The reset pin needs to be connected in order to guarantee a proper reset.
Limitations
SystemView
For the S32M27x, ECC RAM is initialized up on connect. So it is not possible to run a debug session in parallel with SystemView, as the connect from SystemView will reinitialize the ECC RAM init and overwrite the RTT buffers. To avoid this the following .JLinkScript file must be added to SystemView.
S32M27x_SystemView.JLinkScript
How to add a .JLinkScript to SystemView is explained here: J-Link_script_files#SystemView
Evaluation Boards
- TBD
Example Application
- TBD
