Difference between revisions of "NXP i.MX 8M Plus"
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | The '''NXP i.MX 8M Plus''' are embedded multi-core processors consisting of one Cortex-M7, up to four Cortex-A53 and one Tensilica HiFi 4 DSP. |
||
__TOC__ |
__TOC__ |
||
| + | ==External Boot Devices== |
||
| − | The '''NXP i.MX 8M Plus''' is an embedded multi-core processor consisting of one Cortex-M7, four Cortex-A53. |
||
| + | Programming of external boot media(eMMC, SDHC, QSPI/NAND Flash) is supported natively through USB Serial interface. |
||
| + | ==Multi-Core Support== |
||
| − | == Debugging == |
||
| + | Before proceeding with this article, please check out the generic article regarding Multi-Core debugging [[Multi-Core_Debugging | here]].<br> |
||
| − | J-Link supports debugging for the Cortex-M4. During connect the M7 is set to execute an endless loop at 0x1FFE0000 (TCML RAM) and afterwards halted. |
||
| + | The i.MX 8M Plus family comes with a variety of multi-core options listed in the following table:<br> |
||
| + | {| class="seggertable" |
||
| + | |- |
||
| + | ! Core || J-Link Support |
||
| + | |- |
||
| + | | 4 x Cortex-A53 ||style="text-align:center;"| {{YES}} |
||
| + | |- |
||
| + | | 1 x Cortex-M7 ||style="text-align:center;"| {{YES}} |
||
| + | |- |
||
| + | | 1 x HIFI4 DSP ||style="text-align:center;"| {{NO}} |
||
| + | |- |
||
| + | |} |
||
| + | In below, the debug related multi-core behavior of the J-Link is described for each core: |
||
| − | === Reset === |
||
| + | ===Cortex-A53 core(s)=== |
||
| − | J-Link currently does not support device reset. |
||
| + | ====Init/Setup==== |
||
| + | The core(s) are enabled after boot. |
||
| + | ====Reset==== |
||
| + | Core reset is not performed. |
||
| + | ====Attach==== |
||
| + | Attach is supported. |
||
| + | |||
| + | ===Cortex-M7 core(s)=== |
||
| + | ====Init/Setup==== |
||
| + | The core(s) are enabled after boot. |
||
| + | During connect the M7 is set to execute an endless loop at 0x00000000 (TCM RAM). |
||
| + | ====Reset==== |
||
| + | Reset is performed by using device-specific registers, than target CPU is halted. |
||
| + | ====Attach==== |
||
| + | Attach is not supported by default because the J-Link initializes certain RAM regions. |
||
| + | |||
| + | ==Device Specific Handling== |
||
| + | ===Connect=== |
||
| + | After the boot stage J-Link writes an "infinite loop" code to the start of the M7s TCM RAM. |
||
| + | After the boot stage J-Link can be attached to a running target. |
||
| + | By default only the main A53 core is enable, the other cores can be enabled by the bootloader or operating system kernel. |
||
| + | In order to have read/write accesse to system memory, MMU should be configured accordingly. |
||
| + | |||
| + | ==Evaluation Boards== |
||
| + | *[[NXP_8MPLUSLPD4_EVK | 8MPLUSLPD4-EVK]] |
||
| + | |||
| + | ==Example Application== |
||
| + | *[[File:NXP_8MPLUSLPD4_EVK_M7_TestProject_ES_8V10.zip]] |
||
Latest revision as of 10:29, 8 April 2024
The NXP i.MX 8M Plus are embedded multi-core processors consisting of one Cortex-M7, up to four Cortex-A53 and one Tensilica HiFi 4 DSP.
Contents
External Boot Devices
Programming of external boot media(eMMC, SDHC, QSPI/NAND Flash) is supported natively through USB Serial interface.
Multi-Core Support
Before proceeding with this article, please check out the generic article regarding Multi-Core debugging here.
The i.MX 8M Plus family comes with a variety of multi-core options listed in the following table:
| Core | J-Link Support |
|---|---|
| 4 x Cortex-A53 | 
|
| 1 x Cortex-M7 |
|
| 1 x HIFI4 DSP | 
|
In below, the debug related multi-core behavior of the J-Link is described for each core:
Cortex-A53 core(s)
Init/Setup
The core(s) are enabled after boot.
Reset
Core reset is not performed.
Attach
Attach is supported.
Cortex-M7 core(s)
Init/Setup
The core(s) are enabled after boot. During connect the M7 is set to execute an endless loop at 0x00000000 (TCM RAM).
Reset
Reset is performed by using device-specific registers, than target CPU is halted.
Attach
Attach is not supported by default because the J-Link initializes certain RAM regions.
Device Specific Handling
Connect
After the boot stage J-Link writes an "infinite loop" code to the start of the M7s TCM RAM. After the boot stage J-Link can be attached to a running target. By default only the main A53 core is enable, the other cores can be enabled by the bootloader or operating system kernel. In order to have read/write accesse to system memory, MMU should be configured accordingly.
