Difference between revisions of "S32K14x series"
(Created page with "TBD") |
|||
| Line 1: | Line 1: | ||
| + | __TOC__ |
||
| + | |||
| + | The NXP S32K14x series is a scalable family of 32-bit ARM Cortex-M4 based MCUs targeted for general purpose automotive and high-reliability industrial applications. |
||
| + | |||
| + | = Requirements = |
||
| + | There are some special requirements that need to be fulfilled in order to use the device series with J-Link: |
||
| + | * Reset pin of MCU needs to be connected to reset pin of J-Link. If this is not the case, proper target connection cannot be guaranteed |
||
| + | |||
| + | = ECC protected internal RAM = |
||
| + | The device series provide ECC protected internal RAM. By default, J-Link resets the MCU on connect and initializes the RAM contents to 0x00. This is done for the following reasons: |
||
| + | * If a memory window in the debugger is open during the debug session and points to a non-initialized RAM region, on the next single step etc. a non-maskable ECC error interrupt would be thrown |
||
| + | * J-Link temporarily uses some portions of the RAM during flash programming and accesses to non-initialized RAM areas would throw non maskable ECC error interrupts |
||
| + | |||
| + | = Example projects = |
||
TBD |
TBD |
||
| + | |||
| + | <references/> |
||
Revision as of 10:45, 6 September 2018
The NXP S32K14x series is a scalable family of 32-bit ARM Cortex-M4 based MCUs targeted for general purpose automotive and high-reliability industrial applications.
Requirements
There are some special requirements that need to be fulfilled in order to use the device series with J-Link:
- Reset pin of MCU needs to be connected to reset pin of J-Link. If this is not the case, proper target connection cannot be guaranteed
ECC protected internal RAM
The device series provide ECC protected internal RAM. By default, J-Link resets the MCU on connect and initializes the RAM contents to 0x00. This is done for the following reasons:
- If a memory window in the debugger is open during the debug session and points to a non-initialized RAM region, on the next single step etc. a non-maskable ECC error interrupt would be thrown
- J-Link temporarily uses some portions of the RAM during flash programming and accesses to non-initialized RAM areas would throw non maskable ECC error interrupts
Example projects
TBD
