Difference between revisions of "Kinetis KE1xZ 48 MHz series"
(→MTB trace) |
|||
| Line 12: | Line 12: | ||
= MTB trace = |
= MTB trace = |
||
| − | The KE1xZ 48 MHz series devices incorporate an ARM MTB on-chip trace buffer that allows instruction backtrace. For more information about MTB in general, please refer to [[MTB specifics | |
+ | The KE1xZ 48 MHz series devices incorporate an ARM MTB on-chip trace buffer that allows instruction backtrace. For more information about MTB in general, please refer to here: [[MTB specifics | Article MTB]]. |
= Example projects = |
= Example projects = |
||
| + | TBD |
||
| − | There are sample projects available that demonstrate how to use J-Link with the ARM CoreLink SSE-200 prototyping platform. |
||
| − | |||
| − | == SEGGER Embedded Studio (multi-core) == |
||
| − | The sample project for SEGGER Embedded Studio is a RAM based project and also demonstrates multi-core debugging. |
||
| − | The sample is actually split into 2 projects: |
||
| − | * [[Media:ARM_SSE-200-MPS3_MPS3_LEDBlinkCore0_ES.zip | ARM_SSE-200-MPS3_MPS3_LEDBlinkCore0_ES.zip]] |
||
| − | * [[Media:ARM_SSE-200-MPS3_MPS3_LEDBlinkCore1_ES.zip | ARM_SSE-200-MPS3_MPS3_LEDBlinkCore1_ES.zip]] |
||
| − | |||
| − | ''' ARM_SSE-200-MPS3_MPS3_LEDBlinkCore0_ES ''' |
||
| − | |||
| − | Loaded into internal SRAM and executed by core 0. Controls LED1 and LED2 on the MPS3 board. LED1 is always toggled, LED2 is toggled as long as core 1 is running its application and sending commands to core 0 |
||
| − | |||
| − | ''' ARM_SSE-200-MPS3_MPS3_LEDBlinkCore1_ES ''' |
||
| − | |||
| − | Loaded into internal SRAM and executed by core 1. Sends commands to core 0 that instruct the main application to toggle LED2 |
||
| − | |||
| − | === Usage === |
||
| − | * Start SEGGER Embedded Studio twice |
||
| − | * Open ARM_SSE-200-MPS3_MPS3_LEDBlinkCore0_ES and ARM_SSE-200-MPS3_MPS3_LEDBlinkCore1_ES accordingly |
||
| − | * Start debug session with project for core 0 |
||
| − | * Let CPU run as soon as main() has hit |
||
| − | * Start debug session with project for core 1 |
||
| − | * Let CPU run as soon as main() has hit |
||
| − | * LED1 and LED2 will blink |
||
| − | * Now halt core 1 (issue halt request in debug session for core 1) |
||
| − | * LED2 stops blinking, LED1 continues to blink |
||
=== Requirements === |
=== Requirements === |
||
The following are the min. requirements to run the example project: |
The following are the min. requirements to run the example project: |
||
| − | * SEGGER Embedded Studio |
+ | * SEGGER Embedded Studio Vxxx or later |
| − | * J-Link software V6. |
+ | * J-Link software V6.35g or later. (Install after Embedded Studio and let J-Link installer update the Embedded Studio installation) |
| − | * |
+ | * xxx board |
<references/> |
<references/> |
||
Revision as of 11:49, 25 September 2018
The NXP Kinetis KE1xZ 48 MHz series is deigned for white goods and industrial applications. It incorporates an ARM Cortex-M0+ core.
J-Link support
The KE14Z32, KE14Z64, KE15Z32, KE15Z64, KE16Z32, KE16Z64 are supported in V6.35g and later versions of the J-Link software.
Watchdog support
Debugging and flash programming with the watchdog (WDOG) being enabled (in non-windowed mode) is supported. Windowed mode of the watchdog is not supported for debugging and flash programming.
MTB trace
The KE1xZ 48 MHz series devices incorporate an ARM MTB on-chip trace buffer that allows instruction backtrace. For more information about MTB in general, please refer to here: Article MTB.
Example projects
TBD
Requirements
The following are the min. requirements to run the example project:
- SEGGER Embedded Studio Vxxx or later
- J-Link software V6.35g or later. (Install after Embedded Studio and let J-Link installer update the Embedded Studio installation)
- xxx board
