Difference between revisions of "i.MX7Dual"
(→Multi-core support for iMX7D) |
|||
| Line 1: | Line 1: | ||
== Multi-core support for iMX7D == |
== Multi-core support for iMX7D == |
||
| − | J-Link script files are necessary to connect to both |
+ | J-Link script files are necessary to connect to both A7 cores and the M4 core of the iMX7D MCU. |
*A7 core0: [[File:NXP_iMX7D_Connect_CortexA7_0.JLinkScript]] |
*A7 core0: [[File:NXP_iMX7D_Connect_CortexA7_0.JLinkScript]] |
||
| Line 13: | Line 13: | ||
Startup procedure is: |
Startup procedure is: |
||
| − | 1) Start debug session that connects to |
+ | 1) Start debug session that connects to A7_0 |
| − | 2) Start debug session that connects to |
+ | 2) Start debug session that connects to A7_1 |
3) Start debug session that connects to M4 |
3) Start debug session that connects to M4 |
||
[...] |
[...] |
||
x) Close debug session that connects to M4 |
x) Close debug session that connects to M4 |
||
| − | x + 1) Close debug session that connects to |
+ | x + 1) Close debug session that connects to A7_1 |
| − | x + 2) Close debug session that connects to |
+ | x + 2) Close debug session that connects to A7_0 |
'''Important!''' |
'''Important!''' |
||
| − | On the iMX7D the |
+ | On the iMX7D the A7_1 core cannot be independently debugged without enabling the core by either having something running on the A7_0 or M4 that enables the A7_1 or as part of the A7_0 J-Link script file. In the example script file above, we chose the later case to enable the A7_1 core from within the A7_0 J-Link script file. |
Revision as of 16:09, 17 January 2017
Multi-core support for iMX7D
J-Link script files are necessary to connect to both A7 cores and the M4 core of the iMX7D MCU.
- A7 core0: File:NXP iMX7D Connect CortexA7 0.JLinkScript
- A7 core1: File:NXP iMX7D Connect CortexA7 1.JLinkScript
- M4 core: File:NXP iMX7D Connect CortexM4.JLinkScript
Example package for J-Link Commander:
How to use script files: Please refer to J-Link User Guide (UM08001), chapter 5.10 "J-Link script files"
Startup procedure is:
1) Start debug session that connects to A7_0 2) Start debug session that connects to A7_1 3) Start debug session that connects to M4 [...] x) Close debug session that connects to M4 x + 1) Close debug session that connects to A7_1 x + 2) Close debug session that connects to A7_0
Important!
On the iMX7D the A7_1 core cannot be independently debugged without enabling the core by either having something running on the A7_0 or M4 that enables the A7_1 or as part of the A7_0 J-Link script file. In the example script file above, we chose the later case to enable the A7_1 core from within the A7_0 J-Link script file.
