Difference between revisions of "NXP MCXN10"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "__TOC__ The '''NXP MCXN1''' are dual core Arm Cortex-M33 microprocessors. ==Flash Banks== ===Internal Flash=== {| class="seggertable" |- ! Flash Bank || Base address !! Size...")
 
Line 1: Line 1:
 
__TOC__
 
__TOC__
The '''NXP MCXN1''' are dual core Arm Cortex-M33 microprocessors.
+
The '''NXP MCXN10''' are dual core Arm Cortex-M33 microprocessors.
   
 
==Flash Banks==
 
==Flash Banks==
Line 27: Line 27:
 
==ECC RAM==
 
==ECC RAM==
 
*Device has ECC RAM.
 
*Device has ECC RAM.
*A connect to devices MCXN945 & MCXN947 will initialize 64KB at 0x20000000.
+
*A connect to devices MCXN547 & MCXN947 will initialize 64KB at 0x20000000.
   
 
==Multi-Core Support==
 
==Multi-Core Support==
Line 34: Line 34:
 
===Main core CPU0(CM33)===
 
===Main core CPU0(CM33)===
 
====Init/Setup====
 
====Init/Setup====
*Initializes the ECC RAM for devices MCXN945 & MCXN947.
+
*Initializes the ECC RAM for devices MCXN547 & MCXN947.
 
*Enables debugging
 
*Enables debugging
 
====Reset====
 
====Reset====

Revision as of 10:50, 22 May 2023

The NXP MCXN10 are dual core Arm Cortex-M33 microprocessors.

Flash Banks

Internal Flash

Flash Bank Base address Size J-Link Support
Main flash (NS) 0x00000000 Up to 2 MB YES.png
Main flash (S) 0x10000000 Up to 2 MB YES.png

QSPI Flash

QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the QSPI Flash Programming Support article.
J-Link supports multiple pin configurations for [DEVICE]. The default loader is marked in bold.

Device Base address Maximum size Supported pin configuration
QSPI flash (NS) 0x80000000 256 MB *Default CS@P3.0 SCLK@P3.7 D0@P3.8 D1@P3.9 D2@P3.10 D3@P3.11
QSPI flash (S) 0x90000000 256 MB *Default CS@P3.0 SCLK@P3.7 D0@P3.8 D1@P3.9 D2@P3.10 D3@P3.11

ECC RAM

  • Device has ECC RAM.
  • A connect to devices MCXN547 & MCXN947 will initialize 64KB at 0x20000000.

Multi-Core Support

Before proceeding with this article, please check out the generic article regarding Multi-Core debugging here.
In below, the debug related multi-core behavior of the J-Link is described for each core:

Main core CPU0(CM33)

Init/Setup

  • Initializes the ECC RAM for devices MCXN547 & MCXN947.
  • Enables debugging

Reset

  • Device specific reset is performed.

Attach

  • Attach is NOT supported for MCXN945 & MCXN947, because the J-Link initializes RAM by default.
  • For all other devices attach is supported.

Secondary core CPU1(MICR-CM33)

Init/Setup

  • If the main core session has not been started / debugging is not enabled yet, the secondary core executes the enable debug sequence.
  • If the secondary core is not enabled yet, it will be enabled / release from reset.

Reset

  • No reset is performed, but will halt the CPU.

Attach

  • Attach is supported

Device Specific Handling

Reset

The J-Link performs a device specific reset sequence. The reset is executed for the main core, only. Reset of the main core, resets / disables the secondary core if used in parallel.

Evaluation Boards

Example Application